ENB (LTE) Feature Description For Release

802 eNB (LTE)
Feature Description
for SLR 7.0.2_2
Describes the concept, software release, dependency & limitation for each feature
and its interconnection with the telecommunication network as a high-level design.
Radio Access Network
Document Version 1.0

January 2018
Document Number: 2600-00LPGMGAP

© 2018 SAMSUNG Electronics Co., Ltd.
All Rights Reserved. The contents of this document/presentation contain proprietary information that
must be kept confidential. No part of this document shall be photocopied, reproduced, stored in a
retrieval system, or transmitted, in any form or by any means whether, electronic, mechanical, or
otherwise without the prior written permission of SAMSUNG Electronics Co., Ltd.
No warranty of accuracy is given concerning the contents of the information contained in this
publication. To the extent permitted by law no liability (including liability to any person by reason of
negligence) will be accepted by SAMSUNG Electronics Co., Ltd., its subsidiaries or employees for
any direct or indirect loss or damage caused by omissions from or inaccuracies in this document.
SAMSUNG Electronics Co., Ltd. reserves the right to change details in this publication without
notice.
This manual should be read and used as a guideline for properly installing and/or operating the
product.
This manual may be changed for system improvement, standardization and other technical
reasons without prior notice.
Updated manuals are available at:
https://systems.samsungwireless.com/
For questions on the manuals or their content, contact

NetSys Tech Writer@sea.samsung.com
Confidential
Contents
Preface viii
Relevance .......................................................................................................................................viii
Conventions in this Document .......................................................................................................viii
New and Changed Information ....................................................................................................... ix
Revision History................................................................................................................................ x
Organization of This Document ...................................................................................................... xi
Related Documentation .................................................................................................................. xi
Chapter 1 Air Performance Enhancement 1
LTE-ME2019, DL SU 2 × 2 MIMO (TM3 and TM4) ............................................................................ 1
LTE-ME2020, Rx Diversity................................................................................................................. 6
LTE-ME2022, DL SU 4 × 4 MIMO (TM3 and TM4) .......................................................................... 11
LTE-ME2023, DL SU 4 × 2 MIMO (TM3 and TM4) .......................................................................... 17
LTE-ME2030, UL MU MIMO for 4R Configuration ......................................................................... 22
LTE-ME3601, Uplink CoMP (JR) ...................................................................................................... 27
LTE-ME3603, Inter-Site UL CoMP (Non-Ideal Backhaul) ................................................................ 32
LTE-ME3605, Inter-Site L1 UL CoMP .............................................................................................. 37
LTE-ME4003, FeICIC ....................................................................................................................... 43
LTE-ME4001, ICIC ........................................................................................................................... 51
LTE-ME4005, IRC ............................................................................................................................ 55
LTE-ME4007, Interference Avoidance in IDC ................................................................................. 58
LTE-ME4008, Network Assisted Interference Cancellation and Suppression (NAICS) ................... 67
LTE-ME5010, Best Cell Aggregation ............................................................................................... 74
LTE-ME5801, FDD DL 2CC Carrier Aggregation .............................................................................. 82
LTE-ME5801-A, FDD DL 2CC Carrier Aggregation with 4x4 MIMO ................................................. 85
LTE-ME5804, FDD DL 5CC Carrier Aggregation ............................................................................ 100
LTE-ME5901, FDD UL 2CC Carrier Aggregation ............................................................................ 103
LTE-ME6010, Downlink CoMP ...................................................................................................... 105
LTE-ME6018, CRS-IC Support ....................................................................................................... 111
Chapter 2 Call Control 116
LTE-SW0100, Support UE Category 0 ........................................................................................... 116
LTE-SW0101, Support for UE Category 1, 2, 3, and 4................................................................... 121
LTE-SW0105, Support for UE Category 5 ..................................................................................... 124
LTE-SW0106, Support for UE Category 6 ..................................................................................... 127
LTE-SW0111, UE Counting per Category ...................................................................................... 130
LTE-SW0112, Battery Saving Option Depending on UE Type ....................................................... 133
LTE-SW0114, Enhancements for Diverse Data Applications ........................................................ 137
LTE-SW0314, Multi-Frequency Band Indicator support ............................................................... 142
LTE-SW0315, Extended Access Barring (SIB14) ............................................................................ 148
LTE-SW0316, Network Signaling (NS) Support ............................................................................. 154
LTE-SW0318, SIB Broadcast (SIB16) ............................................................................................. 158
LTE-SW0319, RAN Assisted WLAN Interworking .......................................................................... 161
LTE-SW0320, RRC Connection Management ............................................................................... 168
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 iii

Copyright © 2018, All Rights Reserved.
Confidential
Contents
LTE-SW0321, UE Context Management ....................................................................................... 178

LTE-SW0322, E-RAB Management ............................................................................................... 186
LTE-SW0325, User Inactivity Timer Control ................................................................................. 194
LTE-SW0326, Connection Setup Time Enhancement ................................................................... 203
LTE-SW0327, SIPTO Support ........................................................................................................ 207
LTE-SW0329, Device Aware Call Control ...................................................................................... 216
LTE-SW0331, VoLTE-aware Inactivity Timer ................................................................................ 221
LTE-SW0332, UE Category Aware Call Control ............................................................................. 227
LTE-SW0334, SDL (Supplemental Downlink) Support .................................................................. 232
LTE-SW0501, S1 Interface Management...................................................................................... 235
LTE-SW0502, NAS Signaling Transport ......................................................................................... 251
LTE-SW0503, MME Overload Control .......................................................................................... 254
LTE-SW0504, MME Selection and Load Balancing ....................................................................... 258
LTE-SW0505, Random Delayed S1 Setup for Load Distribution ................................................... 263
LTE-SW0506, eNB Configuration Update ..................................................................................... 267
LTE-SW0508, Traffic Load Reduction for MME Overload Control ............................................... 270
LTE-SW0510, Geo Redundancy of MME ...................................................................................... 273
LTE-SW0513, User Location Report at Call Release ..................................................................... 282
LTE-SW0514, Dedicated Core Network Support .......................................................................... 284
LTE-SW0521, X2 Interface Management ..................................................................................... 290
LTE-SW0522, UE Radio Capability Match Request ....................................................................... 301
LTE-SW0531, Control Plane Optimization Support ...................................................................... 311
LTE-SW0532, User Plane Optimization Support........................................................................... 317
LTE-SW3001, AM, UM and TM Data Transfer at RLC Layer ......................................................... 328
LTE-SW3010, PDCP Sublayer Support .......................................................................................... 332
LTE-SW3011, Header Compression ROHCv1 (RTP, UDP, IP) ........................................................ 336
LTE-SW3013, ROHC IPv6 Support................................................................................................. 341
LTE-SW3051, Integrity Protection: Null/SNOW3G/AES ............................................................... 345
LTE-SW3052, Ciphering: Null/SNOW3G/AES ............................................................................... 348
LTE-SW4101, Capacity Based Call Admission Control .................................................................. 351
LTE-SW4102, QoS Based Call Admission Control ......................................................................... 365
LTE-SW4103, Preemption ............................................................................................................ 378
LTE-SW4104, Cell Barring ............................................................................................................. 385
LTE-SW4105, Access Class Barring ............................................................................................... 389
LTE-SW4106, Call Admission Control per QCI .............................................................................. 406
LTE-SW4107, ARP based Call Admission Control ......................................................................... 409
LTE-SW4201, Standard QCI Support ............................................................................................ 412
LTE-SW4202, Operator Specific QCIs Support ............................................................................. 416
LTE-SW4203, QCI to DSCP Mapping ............................................................................................. 421
LTE-SW4204, GBR and MBR Support ........................................................................................... 426
LTE-SW4206, UE-AMBR Support .................................................................................................. 431
LTE-SW4207, Max 8 Bearers per UE............................................................................................. 433
LTE-SW4208, QCI-based Non-GBR Throughput Differentiation................................................... 435
LTE-SW4210, SPID-based Throughput Differentiation for Non-GBR UEs..................................... 439
LTE-SW4211, Application Aware QoS .......................................................................................... 443
LTE-SW5500, CA Call Control ....................................................................................................... 448
LTE-SW5503, UL CA Call Control .................................................................................................. 478
LTE-SW5505, Inter-eNB Carrier Aggregation ............................................................................... 484
LTE-SW6301, NB-IoT Call Control Support ................................................................................... 499
LTE-SW6311, Paging Optimization for Low Complexity and Coverage Enhanced UE .................. 510
Chapter 3 Load Control 518
LTE-SW2001, Intra-LTE Mobility Load Balancing.......................................................................... 518
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 iv

Confidential
Contents
LTE-SW2003, Idle UE Distribution ................................................................................................ 534

LTE-SW2008, Blind Offloading to eHRPD ..................................................................................... 542
LTE-SW2009, Multi-carrier Load Balancing with CA..................................................................... 548
LTE-SW2020, Load Distribution over Backhaul Links ................................................................... 553
LTE-SW2007, Load based Redirection to Different Carrier .......................................................... 556
LTE-SW2033, Redistribution of Idle-mode UEs ............................................................................ 561
LTE-SW2102, eNB Overload Control (Adaptive Access Barring) .................................................. 565
LTE-SW2103, UL Congestion Prevention ...................................................................................... 582
LTE-SW2104, eNB Overload Protection ....................................................................................... 588
LTE-SW2106, Delay Tolerant Access Processing for eNB Overload Control ................................ 593
LTE-SW2107, MME Overload Protection ..................................................................................... 598
LTE-SW2108, Smart Congestion Mitigation ................................................................................. 602
LTE-SW2109, Application Specific Congestion Control for Data Communication ....................... 606
LTE-SW2301, Resource Pooling between Cells ............................................................................ 611
Chapter 4 Mobility Control 615
LTE-SW1001, Paging ..................................................................................................................... 615
LTE-SW1002, Idle Mobility Support ............................................................................................. 618
LTE-SW1003, Intra-eNB Handover ............................................................................................... 635
LTE-SW1004, S1 Handover ........................................................................................................... 643
LTE-SW1005, X2 Handover ........................................................................................................... 657
LTE-SW1006, Data Forwarding..................................................................................................... 669
LTE-SW1007, Inter-Frequency Handover ..................................................................................... 679
LTE-SW1008, Inbound Mobility to HeNB (CSG/Hybrid Cells) ....................................................... 724
LTE-SW1010, Intra-LTE Redirection.............................................................................................. 731
LTE-SW1014, RLF Triggered Handover ......................................................................................... 736
LTE-SW1015, Frequency-Priority-based HO ................................................................................. 760
LTE-SW1017, Inter-Frequency Handover for CA .......................................................................... 778
LTE-SW1019, Uplink Quality Based Inter-frequency HO .............................................................. 784
LTE-SW1101, Idle Mobility to CDMA Network (HRPD/1xRTT) ..................................................... 805
LTE-SW1102, Non-Optimized Handover to HRPD ........................................................................ 814
LTE-SW1103, Optimized Handover to HRPD ................................................................................ 819
LTE-SW2011, Service based Intra-LTE Handover ......................................................................... 828
LTE-SW2014, SPID based Dedicated Priority................................................................................ 836
LTE-SW3014, ROHC Context Continuation................................................................................... 846
LTE-SW5005, Inter-PLMN Handover ............................................................................................ 849
LTE-SW6001, HetNet Mobility Enhancement .............................................................................. 855
Chapter 5 Operation and Maintenance 861
LTE-OM8001, Convention for eNB/Cell Identifier and Name ...................................................... 861
Chapter 6 RAN Sharing 864
LTE-SW5001, Multi-PLMN Support .............................................................................................. 864
LTE-SW5002, Flexible Radio Resource Configuration for RAN Sharing ........................................ 870
LTE-SW5004, Frequency Relocation Handover ............................................................................ 880
LTE-SW5012, Operator Specific Feature Activation ..................................................................... 887
Chapter 7 Radio Scheduler 901
LTE-ME0501, Cell-Specific Reference Signal ................................................................................ 901
LTE-ME0506, Synchronization Signal ........................................................................................... 906
LTE-ME0507, Demodulation Reference Signal ............................................................................. 910
LTE-ME0508, Sounding Reference Signal ..................................................................................... 915
LTE-ME0601, RACH Preamble Format 0 to 3 ............................................................................... 921
LTE-ME0603, Random Access Procedures ................................................................................... 927
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 v

Confidential
Contents
LTE-ME1001, Variable Number of OFDM Symbols for PDCCH..................................................... 934

LTE-ME1002, CCE Aggregation for PDCCH ................................................................................... 939
LTE-ME1005, Basic DCI Formats ................................................................................................... 942
LTE-ME1101, PDSCH Resource Allocation .................................................................................... 946
LTE-ME1503, PUSCH Frequency Hopping .................................................................................... 951
LTE-ME1504, PUCCH Format........................................................................................................ 956
LTE-ME3001, Power Control ........................................................................................................ 961
LTE-ME3002, Residual BLER Aware UL Power Control................................................................. 972
LTE-ME3004, Power Boosting for DL Control Channels ............................................................... 975
LTE-ME3005, DL Power Allocation ............................................................................................... 977
LTE-ME3006, AMPR (Additional Maximum Power Reduction) .................................................... 983
LTE-ME3101, HARQ in DL and UL ................................................................................................. 987
LTE-ME3201, Basic Link Adaptation ............................................................................................. 995
LTE-ME3203, Aperiodic CQI Reporting....................................................................................... 1000
LTE-ME3205, CQI Correction ...................................................................................................... 1003
LTE-ME3206, Periodic Channel Status Reporting ....................................................................... 1009
LTE-ME3207, Power Restriction for PDCCH Region ................................................................... 1012
LTE-ME3301, Uplink Scheduler Enhancement ........................................................................... 1015
LTE-ME3304, Scheduling with QoS Support............................................................................... 1018
LTE-ME3305, Semi-persistent Scheduling .................................................................................. 1023
LTE-ME3306, DL Frequency Selective Scheduling ...................................................................... 1031
LTE-ME3307, UL Sub-frame Bundling ........................................................................................ 1035
LTE-ME3308, UL Frequency Selective Scheduling ...................................................................... 1042
LTE-ME3309, Resource Allocation Enhancement for SIB ........................................................... 1045
LTE-ME3310, VoLTE Concurrent Rank Adaptation..................................................................... 1052
LTE-ME3312, PRB Randomization .............................................................................................. 1058
LTE-ME3314, Unified PF Scheduling for CA ................................................................................ 1063
LTE-ME3401, Paging DRX ........................................................................................................... 1067
LTE-ME3402, Active DRX ............................................................................................................ 1071
LTE-ME3410, Extended DRX for Idle Mode ................................................................................ 1080
LTE-ME3501, UL Resource Allocation Type1 (Multi-Cluster PUSCH) ......................................... 1087
LTE-ME6006, PUCCH Over-Dimensioning/PUCCH Blanking ....................................................... 1092
Chapter 8 Radio Transmission 1096
LTE-ME0103, FDD 5MHz Bandwidth .......................................................................................... 1096
LTE-ME0104, FDD 10 MHz Bandwidth ....................................................................................... 1102
LTE-ME0201, Frame Structure Type 1 (FDD) .............................................................................. 1119
LTE-ME0218, Normal CP ............................................................................................................ 1121
LTE-ME0219, Extended CP ......................................................................................................... 1125
LTE-ME0401, Downlink QPSK, 16 QAM, 64 QAM Support ......................................................... 1128
LTE-ME0402, Uplink QPSK, 16 QAM Support ............................................................................. 1131
LTE-ME0403, Uplink 64 QAM Support ....................................................................................... 1134
LTE-ME0404, DL 256 QAM ......................................................................................................... 1137
LTE-ME3010, Timing Advance Control ....................................................................................... 1144
LTE-ME6301, NB-IoT L1/L2 Support ........................................................................................... 1157
LTE-ME6302, NB-IoT Enhanced Link Adaptation ....................................................................... 1163
Chapter 9 SON 1166
LTE-SO0101, Self-establishment ................................................................................................ 1166
LTE-SO0201, Intra-LTE ANR ........................................................................................................ 1176
LTE-SO0202, Inter-RAT ANR (HRPD) ........................................................................................... 1210
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 vi

Confidential
Contents
LTE-SO0301, PCI AutoConfiguration .......................................................................................... 1223

LTE-SO0401, RACH optimization ................................................................................................ 1239
LTE-SO0402, NB-IoT RACH Optimization.................................................................................... 1262
LTE-SO0403, eMTC RACH Optimization ..................................................................................... 1267
LTE-SO0501, Intra-LTE MRO ....................................................................................................... 1274
LTE-SO0505, UE Level Ping-pong HO Minimization ................................................................... 1295
LTE-SO0601, Sleeping Cell Detection ......................................................................................... 1303
LTE-SO0603, Sick Cell Detection................................................................................................. 1311
LTE-SO0801, PA Bias Control ...................................................................................................... 1316
LTE-SO0802, Cell On/Off in Multi-carrier Sites .......................................................................... 1326
LTE-SO0804, DL MIMO TX Branch On/Off .................................................................................. 1335
LTE-SO0807, Dynamic PA on/off ................................................................................................ 1344
LTE-SO0811, Channel Card On/Off ............................................................................................. 1347
LTE-SO0901, Minimization Drive Test Optimization .................................................................. 1351
Chapter 10 Services 1363
LTE-ME3317, UL allocation enhancement for VoLTE ................................................................. 1363
LTE-SV0101, IMS based Emergency Call Support ....................................................................... 1367
LTE-SV0105, eMPS (Enhancements for Multimedia Priority Service) support .......................... 1370
LTE-SV0201, CMAS (Commercial Mobile Alert Service) ............................................................. 1373
LTE-SV0301, A-GNSS (LPP) ......................................................................................................... 1379
LTE-SV0302, Enhanced Cell ID .................................................................................................... 1382
LTE-SV0303, OTDOA ................................................................................................................... 1387
LTE-SV0401, Vocoder Rate Adaptation ...................................................................................... 1397
LTE-SV0404, VoLTE Quality Enhancement ................................................................................. 1403
LTE-SV0406, VoLTE Coverage Enhancement .............................................................................. 1412
LTE-SV0501, eMBMS Basic Function .......................................................................................... 1417
LTE-SV0503, Multicell and Multicast Coordination (MCE) ......................................................... 1433
LTE-SV0504, eMBMS Resource Allocation ................................................................................. 1442
LTE-SV0511, eMBMS QoS .......................................................................................................... 1455
LTE-SV0513, eMBMS Service Continuity (SIB15)........................................................................ 1458
LTE-SV0514, Adaptive Delay Reduction for eMBMS .................................................................. 1464
LTE-SV0517, eMBMS Service Restoration .................................................................................. 1469
LTE-SV0520, eMBMS Trace ........................................................................................................ 1473
LTE-SV1100, TCP Optimization ................................................................................................... 1476
LTE-SV1101, TCP DL AQM (Active Queue Management) ........................................................... 1480
LTE-SV1400, TCP UL Congestion Control.................................................................................... 1484
LTE-SV1500, eMTC ..................................................................................................................... 1488
Chapter 11 System Test and Analysis 1521
LTE-OM9001, Cell Traffic Trace .................................................................................................. 1521
LTE-OM9002, Subscriber and Equipment Trace......................................................................... 1527
LTE-OM9003, UE Throughput and RF information Trace ........................................................... 1532
LTE-OM9004, CSL (Call Summary Log) Report ........................................................................... 1542
LTE-OM9010, VoLTE Monitoring ................................................................................................ 1545
LTE-OM9100, Key Performance Indexes .................................................................................... 1550
LTE-OM9101, L1 and L2 Counters .............................................................................................. 1554
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 vii

Confidential
Preface
This document provides detailed descriptions of each feature in the SLR 7.0.2_2
software release.
Some features, commands, parameters, or counters are not supported by all

software releases or approved for all markets.
Relevance
This manual applies to the following products/software.
Name Type
SLR 7.0.2_2 Software
Conventions in this Document

Samsung Networks product documentation uses the following conventions.
Symbols
Symbol Description
Indicates a task.
Indicates a shortcut or an alternative method.
Provides additional information.
Provides information or instructions that you should follow to avoid service

failure or damage to equipment.
Provides information or instructions that you should follow to avoid personal
injury or fatality.
Provides antistatic precautions that you should observe.
Menu Commands
menu | command
This indicates that you must select a command on a menu, where menu is the
name of the menu, and command is the name of the command on that menu.
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 viii

Confidential
Preface
File Names and Paths

These are indicated by a bold typeface. For example:
Copy filename.txt into the /home/folder1/folder2/bin/ folder.
User Input and Console Screen Output Text

Input and output text is presented in the Courier font. For example,
context <designated epc-context-name>
CLI commands are presented in bold small caps. For example,
Type the RTRV-NE-STS command in the input field.
New and Changed Information

This section describes information that has been added/changed since the previous
publication of this manual.
• The following table shows the new and enhanced features for SLR 7.0.2_2
compared to SLR 7.0.2_1:
Types Feature ID, Name
New features • LTE-ME3603, Inter-Site UL CoMP (Non-Ideal Backhaul)
• LTE-ME3605, Inter-Site L1 UL CoMP
• LTE-ME4003, FeICIC
• LTE-ME4008, Network Assisted Interference Cancellation and
Suppression (NAICS)
• LTE-ME5804, FDD DL 5CC Carrier Aggregation
• LTE-ME6301, NB-IoT L1/L2 Support
• LTE-ME6302, NB-IoT Enhanced Link Adaptation
• LTE-SO0402, NB-IoT RACH Optimization
• LTE-SW0319, RAN assisted WLAN interworking
• LTE-SW0334, SDL(Supplemental Downlink) Support
• LTE-SW0531, Control Plane Optimization Support
• LTE-SW0532, User Plane Optimization Support
• LTE-SW1019, Uplink Quality Based Inter-frequency HO
• LTE-SW2008, Blind Offloading to eHRPD
• LTE-SW2009, Multi-carrier Load Balancing with CA
• LTE-SW5505, Inter-eNB Carrier Aggregation
• LTE-SW6001, HetNet Mobility Enhancement
• LTE-SW6301, NB-IoT Call Control Support
Enhanced features • LTE-ME2030, UL MU MIMO for 4R Configuration
• LTE-ME3402, Active DRX
• LTE-ME3410, Extended DRX for Idle Mode
• LTE-ME4001, ICIC
• LTE-ME4007, Interference Avoidance in IDC
• LTE-OM9101, L1 and L2 Counters
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 ix

Confidential
Preface
Types Feature ID, Name

• LTE-SO0301, PCI AutoConfiguration
• LTE-SO0501, Intra-LTE MRO
• LTE-SO0802, Cell On/Off in Multi-carrier Sites
• LTE-SO0811, Channel Card On/Off
• LTE-SV0404, VoLTE Quality Enhancement
• LTE-SV0513, eMBMS Service Continuity(SIB15)
• LTE-SW0503, MME Overload Control
• LTE-SW0504, MME Selection and Load Balancing
• LTE-SW0514, Dedicated Core Network Support
• LTE-SW1004, S1 Handover
• LTE-SW2106, Delay Tolerant Access Processing for eNB
Overload Control
• LTE-SW2107, MME Overload Protection
• LTE-SW3010, PDCP Sublayer Support
• LTE-SW5002, Flexible Radio Resource Configuration for RAN
Sharing
• LTE-SW5012, Operator Specific Feature Activation
• LTE-SW6311, Paging Optimization for low complexity and
coverage enhanced UE
Revision History
The following table lists all versions of this document.
Document Version Publication Date Remarks
1.0 January 2018 First Version
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 x

Confidential
Preface
Organization of This Document

Section Title Description
Chapter 1 Air Performance Enhancement This chapter describes LTE features related to
Air Performance Enhancement.
Chapter 2 Call Control This chapter describes LTE features related to
Call Control.
Chapter 3 Load Control This chapter describes LTE features related to
Load Control.
Chapter 4 Mobility Control This chapter describes LTE features related to
Mobility Control.
Chapter 5 Operation and Maintenance This chapter describes LTE features related to
Operation and Maintenance.
Chapter 6 RAN Sharing This chapter describes LTE features related to
RAN Sharing.
Chapter 7 Radio Scheduler This chapter describes LTE features related to
Radio Scheduler.
Chapter 8 Radio Transmission This chapter describes LTE features related to
Radio Transmission.
Chapter 9 SON This chapter describes LTE features related to
SON.
Chapter 10 Services This chapter describes LTE features related to
Services.
Chapter 11 System Test and Analysis This chapter describes LTE features related to
System Test and Analysis.
Related Documentation
• eNB (OAM) Feature Description for SLR 7.0.2_2
• eNB (Transport) Feature Description for SLR 7.0
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 xi

Confidential
Chapter 1 Air Performance

Enhancement
LTE-ME2019, DL SU 2 × 2 MIMO (TM3 and TM4)

INTRODUCTION
Downlink 2x2 single-user MIMO can be configured in case of two transmit
antennas on an eNB and two receive antennas on the UE. When an eNB transmits
data to the UE using multiple antennas technique, each receiver antenna receives a
composite signal made up of transmitted signals modified by their channels. Under
specific channel conditions, the transmitter can structure the transmitted signals to,
either send modified copies of the same transmission (transmit diversity) or, send
different transmission (spatial multiplexing). Transmit diversity provides signal
robustness and spatial multiplexing provides increase in data rate.
BENEFIT
• Provides improvement in cell capacity and throughput as UEs with good
channel conditions can benefit from the multiple streams transmission.
• Serves improved throughput and reliable communication by using multiple
streams transmission.
DEPENDENCY
• Related Radio Technology: E-UTRAN (LTE)
• Prerequisite Features: LTE-ME0501, Cell-specific Reference Signal
LIMITATION
None
SYSTEM IMPACT
This section describes how this feature impacts the network functions and
capabilities.
Interdependencies between Features
None
Performance and Capacity
This feature will increase the UE downlink throughout by 2-layer spatial
multiplexing according to the feedback rank information. Moreover, Transmission
eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 1

Confidential
Chapter 1 Air Performance Enhancement
Mode 3 (TM3) and Transmission Mode 4 (TM4) rank adaptation will provide the
more appropriate precoder in time-varying channel.
Coverage
None
Interfaces
When transmission mode is changed, eNB will send RRC Connection
Reconfiguration message for UE to be changed Transmission Mode IE.
FEATURE DESCRIPTION
Samsung supports the DL SU-MIMO Spatial Multiplexing (SM) in both TM3
(open loop SM) and TM4 (closed loop SM) employing either 2x2 antenna
configuration, that is, two transmit eNB antennas and two receive UE antennas. To
enable DL SU 2x2 MIMO, set DL_CRS_PORT_COUNT (CHG-CELL-IDLE) to 2
and DL_ANT_COUNT (CHG-CELL-IDLE) to n2TxAntCnt.
Transmit Diversity
Transmit diversity is default MIMO mode in LTE. This redundancy leads to
increase in signal-to-noise ratio and therefore, signal robustness. TM2 provides
transmit diversity by transmitting a single PDSCH codeword using two antennas.
Spatial Multiplexing
In spatial multiplexing, there is no signal redundancy; antenna ports transmit
different symbols. Two modes that provide spatial multiplexing are TM3 and
TM4. TM3 uses a predetermined CDD-based precoding and is favorable to high
speed UEs. TM4 uses a codebook-based precoding and is favorable to low speed
UEs because the scheduler adopts the best precoder per UE based on the precoder
feedback by UE. For both TM3 and TM4, rank adaptation based on the feedback,
Rank Information (RI) is supported so that the most appropriate number of
transmission layers (and codewords) can be adopted.
Mode Description Antenna Ports Layer Codewords Channel Rank UE Feedback
TM3 Open loop spatial 2 2 2 2 CQI and RI
multiplexing with cyclic
delay diversity.
TM4 Closed loop spatial 2 2 2 2 CQI, RI, and
multiplexing with PMI
precoding matrix.
Transmission Mode 3 (DL_MIMO_MODE as 2 (ci_tm3))

TM3 is spatial multiplexing scheme that uses pre-determined precoding matrix.
The process of applying pre-coding is defined in 3GPP specification TS 36.211.
Open loop spatial multiplexing uses Channel Quality Information (CQI) and Rank
Indication (RI) information feedback from UE.
Codewords and layers mapping in open loop spatial multiplexing (TM3) for two
antenna ports are tabulated as follows.
Confidential
Number of Number of CW and Layer mapping Layer Transmission

Codewords Layers
1 1 TM2 (Tx-Diversity Mode)
2 2

TM4 is spatial multiplexing scheme that uses PMI index feedback from UE, to
construct downlink PDSCH codeword to maximize signal to noise ratio at UE
receiver.
A PMI index is a pointer to a set of pre-coding weights that are applied to
downlink codewords prior to transmission. The process of applying pre-coding is
defined in 3GPP specification TS 36.211. TM 4 is suitable for scenarios when the
UE is in slow time-varying channel because there is a delay associated with a PMI
report from UE and a corresponding downlink transmission that utilizes the
reported PMI index. A stationary or pedestrian speed UE in good RF coverage
scenario will get the most benefit from this mode.
Codewords and layers mapping in closed loop spatial multiplexing (TM4) for two
Number of Number of CW and Layer Mapping Layer Transmission
Codewords Layers
1 1
2 2
SYSTEM OPERATION
This section describes how to configure the feature in Samsung system and
provides associated key parameters, counters, and KPIs.
How to Activate
This section provides the information that you need to configure the feature.

Confidential
Preconditions
Ensure that the following condition is met before enabling this feature:
• DL_ANT_COUNT should be set equal to or greater than n2TxAntCnt.
Activation Procedure
To activate this feature, do the following:
• Run CHG-CELL-IDLE and set DL_CRS_PORT_COUNT to 2 to enable 2x2
SU-MIMO.
Deactivation Procedure
To deactivate this feature, do the following:
• Run CHG-CELL-IDLE and set DL_CRS_PORT_COUNT to other value.
Key Parameters
This section describes the key parameters for activation, deactivation, and
configuration of the feature.
Activation/Deactivation Parameters
To activate or deactivate the feature, run the associated commands and set the key
parameters.
Parameter Description of CHG-CELL-IDLE/RTRV-CELL-IDLE
Parameter Description
DL_ANT_COUNT This parameter is the number of Tx antennas used by an operating cell.
DL_CRS_PORT_COUN This parameter is the number of downlink CRS ports that are supported by the
T system.
Configuration Parameters
To configure the feature setting, run the associated commands and set the key
parameters.
Parameter Description of CHG-DL-SCHED/RTRV-DL-SCHED
CELL_NUM This parameter indicates the user-defined cell ID.
DL_MIMO_MODE This parameter specifies the transmission mode. Each one is corresponding to a
particular multiple antenna technique.
• TM1: Single-antenna port (port 0), DCI format 1 or 1A is used.
• TM2: Transmit diversity, DCI format 1 or 1A is used.
• TM3: Open-loop spatial multiplexing, DCI format 2A or 1A is used.
• TM4: Closed-loop spatial multiplexing, DCI format 2 or 1A is used.
• TM5: MU-MIMO, DCI format 1D or 1A is used. It is a test mode and it is not
supported.
• TM6: Closed-loop rank-1 precoding, DCI format 1B or 1A is used. It is a test
mode and it is not supported.
• TM7: Single-antenna port (port 5), DCI format 1 or 1A is used. It is supported for
only 8T8R TDD.
• TM8: Dual layer transmission, or Single-antenna port (port 7/port 8), DCI format
2B or 1A is used. It is supported for only 8T8R TDD.

Confidential
• TM9: UE specific RS based Transmission (Rel-10)
[Related Specifications] 3GPP TS 36.213
ALPHA Fairness weight in PF scheduler. If alpha is increased, scheduling fairness
increases, such as Round Robin scheduling.
BETA Channel quality weight in PF scheduler. If beta is increased, scheduling efficiency
increases, such as Maximum C/I.
GAMMA Priority weight in PF scheduler.
Counters and KPIs

There are no specific counters or Key Performance Indicators (KPIs) associated
with this feature.
REFERENCE
[1] 3GPP TS 36.201: Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical layer; General description
Physical Channels and Modulation
Multiplexing and channel coding
Physical layer procedures
Physical layer; Measurements
[6] 3GPP TS 36.300: Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall
description; Stage 2

Confidential
LTE-ME2020, Rx Diversity
INTRODUCTION
Receive (Rx) Diversity techniques are one of interference mitigation schemes via
Rx combining weight, based on Zero-Forcing (ZF) or Minimum Mean Squared
Error (MMSE) algorithm. Rx diversity makes better quality on uplink received
signal. Samsung eNB supports Rx diversity using Minimum Mean Squared Error
(MMSE) combining with Interference Rejection Combining (IRC) receiver.
BENEFIT
Rx diversity improves the quality and reliability on uplink received signal.
DEPENDENCY
Radio Technology: E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
The implementation of this feature does not have any impact on the network.
FEATURE DESCRIPTION
In Rx diversity, the receiver combines multiple streams from different antenna into
a single stream by choosing the appropriate weight for each received signals, as
depicted in the following figure.
There are multiple ways to choose the weight of receiver. Samsung eNB uses
Linear Minimum Mean Squared Error (LMMSE) receiver with IRC to suppress
inter-cell interference, the following figure represents the physical meaning of
LMMSE receiver. This feature is activated when IRC_ENABLE (CHG-PUSCH-
IDLE) is set to 1 (TRUE).

Confidential
h2 h2
Signal Signal
ZF vector
MRC vector
Reduce
signal power
Interference Interference
h1 h1
h2
MMSE-IRC Signal
vector
ZF vector
Interference suppression MRC vector Signal matching

Reduce
signal power
Interference
h1
LMMSE Receiver with IRC

To obtain receive diversity, Samsung eNB considers LMMSE criterion with IRC.
This advanced receiver employing IRC is effective in improving the cell-edge user
throughput. The IRC receiver utilizes the covariance of interference and noise
factors of multiple receiver branches, and combines the received signals for
multiple receiver branches so that the Mean Square Error (MSE) between the
combined signal and the desired signal is minimized, instead of Maximal Ratio
Combining (MRC).
The specific combining criterion is as follows:
• The channel estimator of the eNB receiver estimates the channel of the desired
signal, and generates the covariance matrix of interference and noise.
o Estimate the channel matrix of the desired signal
estimated channel matrix

o Estimate the covariance matrix of interference and noise
desired signal
vector
• Using the estimated channel and the covariance matrix, MMSE weight is
calculated to perform IRC.
o Minimum Mean Squared Error (MMSE) criterion

Confidential
• MMSE criterion achieves the optimal balance the noise enhancement and
interference suppression
Combined weight
• Interference rejection is achieved by MMSE combining at the eNB receiver.
IRC scheme based on MMSE criterion achieves an optimal balance of noise

enhancement and interference suppression. Hence, IRC provides the enhanced
performance to UEs at the cell boundary that experience serious interference from
other cell. The receive diversity can be obtained from combining the calculated
weight with received signals for each receiver path.
SYSTEM OPERATION
How to Activate
Preconditions
There are no specific preconditions to activate this feature.
• Run CHG-PUSCH-IDLE and set IRC_ENABLE to True (IRC on)
(IRC_ENABLE = 1) for desired cell number.
• Run CHG-PUSCH-IDLE and set IRC_ENABLE to False (IRC off)
(IRC_ENABLE = 0) for desired cell number.
Key Parameters
This section describes the key parameters for activation and deactivation of the
feature.
To activate or deactivate the feature, run the associated command and set the key
parameter.
Parameter Descriptions of CHG-PUSCH-IDLE/RTRV-PUSCH-IDLE
Confidential
IRC_ENABLE This parameter is used to enable to use IRC.
• 0: False (IRC off)
• 1: True (IRC on)
Counters and KPIs

The following are counters or Key Performance Indicators (KPIs) associated with
this feature.
Family Display Name Type Name Type Description
MCS ULReceivedMcs0~31 The cumulated number of received PUSCH
per MCS
ULSchedulerMcs0~31 The cumulated number of PRBs assigned to
PUSCH per MCS
AIR_MAC_BYTES AirMacULThruAvg The calculated number that indicates the
average per second size of MAC PDUs,
which were successfully received through
PUSCH during the collection interval.
AirMacULEfctivThruAvg The overall calculated size of MAC PDUs,
UL_SINR_DISTRIBUTION SinrDistULWbPreComp_Bin0~19 The cumulated number of Uplink SINR
before Outer-loop compensation
• Bin0 (-10 to -8 dB)
• Bin1 (-8 to -6 dB)
• Bin2 (-6 to -4 dB)
• Bin3 (-4 to -2 dB)
• Bin4 (-2 to 0 dB)
• Bin5 (0 to 2 dB)
• Bin6 (2 to 4 dB)
• Bin7 (4 to 6 dB)
• Bin8 (6 to 8 dB)
• Bin9 (8 to 10 dB)
• Bin10 (10 to -12 dB)
• Bin11 (12 to -14 dB)
• Bin12 (14 to -16dB)
• Bin13 (16 to -18 dB)
• Bin14 (18 to -20 dB)
• Bin15 (20 to -22 dB)
• Bin16 (22 to -24 dB)
• Bin17 (24 to -26 dB)
• Bin18 (26 to -28 dB)
• Bin19 (28 to -30 dB)
SinrDistULWbPostComp_Bin0~19 The cumulated number of Uplink SINR after
Outer-loop compensation
• Bin0 (-10 to -8 dB)
• Bin1 (-8 to -6 dB)
• Bin2 (-6 to -4 dB)
• Bin3 (-4 to -2 dB)

Confidential

• Bin4 (-2 to 0 dB)
• Bin5 (0 to 2 dB)
• Bin6 (2 to 4 dB)
• Bin7 (4 to 6 dB)
• Bin8 (6 to 8 dB)
• Bin9 (8 to 10 dB)
• Bin10 (10 to -12 dB)
• Bin11 (12 to -14 dB)
• Bin12 (14 to -16 dB)
• Bin13 (16 to -18 dB)
• Bin14 (18 to -20 dB)
• Bin15 (20 to -22 dB)
• Bin16 (22 to -24 dB)
• Bin17 (24 to -26 dB)
• Bin18 (26 to -28 dB)
• Bin19 (28 to -30 dB)
REFERENCE
[1] 3GPP TS 36.201: Evolved Universal Terrestrial Radio Access (E-UTRA); LTE
physical layer; General description
[2] Goldsmith, A. J. Wireless communications; Cambridge University Press, 2005

Confidential

INTRODUCTION
Downlink 4 × 4 single-user MIMO can be configured in case of four transmit
antennas on an eNB and four receive antennas on the UE. When an eNB transmits
BENEFIT
• Improves cell capacity and throughput as UEs with good channel conditions
can benefit from the multiple streams transmission.
• Provides a reliable communication by using multiple streams transmission.
DEPENDENCY
• HW dependency: 4T4R RRU is required
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
DL SU 4 × 4 MIMO functionality supports 4-layer spatial multiplexing such that
increases peak rate and capacity of cell/UE compared to DL SU 2x2 MIMO. The
operator can select transmission mode for 4 × 4 MIMO by DL_MIMO_MODE.
Coverage
None
Interfaces
None
Confidential
FEATURE DESCRIPTION
Samsung plans to support the DL SU-MIMO Spatial Multiplexing (SM) in both
Transmission Mode 3 (open loop SM) and Transmission Mode 4 (closed loop SM)
employing 4 × 4 antenna configuration that is 4 transmit eNB antennas and 4
receive UE antennas. To enable DL SU 4 × 4 MIMO, set DL_CRS_PORT_COUNT
(CHG-CELL-IDLE) to 4 and DL_ANT_COUNT (CHG-CELL-IDLE) to
n4TxAntCnt.

TM 3 is spatial multiplexing scheme that uses pre-determined precoding matrix.
Open loop spatial multiplexing uses Channel Quality Information (CQI) and Rank
Indication (RI) information feedback from UE.
Codewords and layers mapping in open loop spatial multiplexing (TM3) for four
Number of Number CW and Layer Mapping Layer Transmission
Codewords of Layers
2 Only used for retransmission of rank 3

or 4
2 2

Confidential

Codewords of Layers
4

TM 4 is spatial multiplexing scheme that uses PMI index feedback from UE, to
receiver.
requested PMI index.
Codewords and layers mapping in close loop spatial multiplexing (TM4) for four
Codewords of Layers
1 1
2 Only used for retransmission of rank 3

or 4
2 2

Confidential

Codewords of Layers
3
SYSTEM OPERATION
How to Activate
Preconditions
• DL_ANT_COUNT should be set equal to or greater than n4TxAntCnt.
• Run CHG-CELL-IDLE and set DL_CRS_PORT_COUNT to Four to enable 4
× 4 SU-MIMO.
• Run CHG-DL-SCHED and set the downlink transmission mode. ci_tm3 is
TM3 and ci_tm4 is TM4.
• Run CHG-CELL-IDLE and set DL_CRS_PORT_COUNT to another value.
Key Parameters
parameters.

Confidential

DL_CRS_PORT_COUNT This parameter is the number of downlink CRS ports that are supported by the
system.
parameters.
CELL_NUM This parameter is the number of cells. This value must not exceed the
maximum number of cells supported by the system. It is determined by
FA/Sector. For example, if the maximum capacity provided to the carrier per
system is 1 FA/3 Sector, up to three cells are supported.
DL_MIMO_MODE This parameter specifies transmission mode. Each one is corresponding to
certain multiple antenna techniques.
• TM1: Single-antenna port (port 0), DCI format 1 or 1A is used.
• TM2: Transmit diversity, DCI format 1 or 1A is used.
• TM3: Open-loop spatial multiplexing, DCI format 2A or 1A is used.
• TM4: Closed-loop spatial multiplexing, DCI format 2 or 1A is used.
• TM5: MU-MIMO, DCI format 1D or 1A is used. It is a test mode and it is not
supported.
• TM6: Closed-loop rank-1 precoding, DCI format 1B or 1A is used. It is a test
mode and it is not supported.
• TM7: Single-antenna port (port 5), DCI format 1 or 1A is used. It is
supported for only 8T8R TDD.
• TM8: Dual layer transmission, or Single-antenna port (port 7/port 8), DCI
format 2B or 1A is used. It is supported for only 8T8R TDD.
• TM9: UE specific RS based Transmission (Release 10)
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.201 Evolved Universal Terrestrial Radio Access (E-UTRA);

Confidential

[6] 3GPP TS 36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and

Confidential

INTRODUCTION
Downlink 4x2 single-user MIMO can be configured in case of four transmit
antennas on an eNB and two receive antennas on the UE. When an eNB transmits
BENEFIT
• Provides improvement in the cell capacity and throughput, as UEs with good
channel conditions can benefit from the multiple streams transmission.
• Serves improved throughput and reliable communication by using multiple
streams transmission.
DEPENDENCY
• HW dependency: 4T4R RRU is required
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
This feature increases the UE downlink throughput by 2-layer spatial multiplexing
according to the feedback rank information. Moreover, TM3 and TM4 rank
adaptation provide the more appropriate precoder in time-varying channel.
Coverage
None

Confidential
Interfaces
When transmission mode is changed, the eNB sends the RRC Connection
Reconfiguration message for UE to be changed Transmission Mode IE.
FEATURE DESCRIPTION
Samsung supports the DL SU-MIMO Spatial Multiplexing (SM) in both
Transmission Mode 3 (TM3: open loop SM) and Transmission Mode 4 (TM4:
closed loop SM) employing either 4x2 antenna configuration that is 4 transmit
eNB antennas and 2 receive UE antennas. To enable DL SU 4x2 MIMO, set
DL_CRS_PORT_COUNT (CHG-CELL-IDLE) to 4 and DL_ANT_COUNT (CHG-
CELL-IDLE) to n4TxAntCnt. If DL_CRS_PORT_COUNT (CHG-CELL-
IDLE) is set to 2 and DL_ANT_COUNT (CHG-CELL-IDLE) is set to
n4TxAntCnt, the eNB transmit the signals with SM and Cyclic Delay Diversity
(CDD) technique (2CRS + CDD). As shown in the bottom figure, the Spatial
Multiplexing signal A/B and its CDD version A'/B' are transmitted to UE using
4TX over the air for the increase of diversity gain.
Transmit Diversity
Transmit diversity is default MIMO mode in LTE. This redundancy leads to
increase in signal-to-noise ratio and therefore, signal robustness. Transmission
Mode 2 provides transmit diversity by transmitting a single PDSCH codeword
using 4 antennas.
Spatial Multiplexing
In spatial multiplexing, there is no signal redundancy as with transmit diversity;
antenna ports transmit different symbols. Two modes that provide spatial
multiplexing are TM3 and TM4. TM3 uses a predetermined CDD-based precoding
and favorable to high speed UEs. TM4 uses a codebook-based precoding and
favorable to low speed UEs because scheduler adopts the best precoder per UE
based on the precoder feedback by UE. For both TM3 and TM4, rank adaptation
based on feedback rank information is supported so that the most appropriate
number of transmission layers (and codewords) can be adopted.

Confidential
Mode Description Antenna Layer Codewords Channel UE

Ports Rank Feedback
TM3 Open loop spatial 4 2 2 2 CQI and RI
multiplexing with
cyclic delay
diversity.
TM4 Closed loop spatial 4 2 2 2 CQI, RI,
multiplexing with and PMI
precoding matrix.

TM3 is spatial multiplexing scheme that uses pre-determined precoding matrix.
Open loop spatial uses Channel Quality Information (CQI) and Rank Indication
(RI) information feedback from UE.
Codewords, layers mapping in open loop spatial multiplexing (TM3) for four
antenna ports are shown in the table below.
Codewords Layers
2 2

TM4 is spatial multiplexing scheme that uses PMI index feedback from UE, to
receiver.
reported PMI index. A stationary or pedestrian speed UE in good RF coverage
scenario gets the most benefit from this mode.
Codewords, layers mapping in closed-loop spatial multiplexing (TM4) for four
antenna ports are shown in the table below.

Confidential

Codewords Layers
1 1
2 2
SYSTEM OPERATION
How to Activate
Preconditions
Ensure that this condition is met before enabling this feature:
• DL_ANT_COUNT must be set equal to or greater than n4TxAntCnt.
• Run CHG-CELL-IDLE and set DL_CRS_PORT_COUNT to 4 to enable 4x2
SU-MIMO.
• Run CHG-CELL-IDLE and set DL_CRS_PORT_COUNT to another value.
Key Parameters
parameters.

Confidential

system.
parameters.
CELL_NUM This parameter is the number of cells. This value must not exceed the maximum
number of cells supported by the system. It is determined by FA/Sector. For
example, if the maximum capacity provided to the carrier per system is 1 FA/3
Sector, up to three cells are supported.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.201 ‘Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical layer; General description’
Physical Channels and Modulation’
Multiplexing and channel coding’
Physical layer procedures’
Physical layer; Measurements’
[6] 3GPP TS 36.300 ‘Evolved Universal Terrestrial Radio Access (E-UTRA) and

Confidential
LTE-ME2030, UL MU MIMO for 4R Configuration

INTRODUCTION
With multiple receive antennas at eNB, spatial multiplexing in uplink can be used
to multiplex data transmissions from different users in the spatial domain. This
technique is commonly referred to as Spatial Division Multiple Access (SDMA).
In an LTE network, this is also referred to as Multi-User Multiple-Input Multiple-
Output (MU-MIMO) in uplink transmission. UL MU-MIMO can also be viewed
as a virtual MIMO system where multiple data streams come from different users
instead of being transmitted by a single user.
BENEFIT
This feature improves cell throughput as UEs with good channel conditions can
benefit from multiple streams transmission.
DEPENDENCY
• HW dependency: LCA or later channel card is required.
LIMITATION
Even though an eNB has four-receiver antennas, the UL MU-MIMO feature
supports only up to 2-layer.
SYSTEM IMPACT
FEATURE DESCRIPTION
The UL MU-MIMO feature is supported in the release 8 version of the 3GPP
specifications. The concept of UL MU-MIMO is depicted in figure below, where
two UEs are paired and transmit their own PUSCH in the same resources to the
eNB with four-received antennas. This is similar to Single User MIMO (SU-
MIMO) except that each layer of transmission originates from a different UE.
Only a single transmit antenna is required at each UE so there is no impact upon
UE implementation complexity. UL MU-MIMO is transparent to the UE. None of
the UE is aware that any other UE has been allocated the same set of resource
blocks.

Confidential
Samsung eNB provides two-type UL MU-MIMO operations as follows:

• Type I (UL MU-MIMO without blacklist management): Type I provides
MIMO allocation by basic rule of MIMO scheduler without considering cross-
correlation between MIMO pairing UEs.
• Type II (UL MU-MIMO with blacklist management): Type II is the modified
version of Type I. This determines whether MIMO allocation can be permitted
by blacklist rule, that is, function with considering cross-correlation between
MIMO pairing UEs as well as basic rule of MIMO scheduler.
This feature can be enabled or disabled by setting UL_MIMO_MODE to 1 (TRUE)
or 0 (FALSE) by using CHG-UL-SCHED per cell through the eNB or the LSM.
UL MU-MIMO without Blacklist Management (Type I)

This type can be enabled by setting UL_MU_MIMO_CORR_ON_OFF_FLAG to 0
(FALSE) by using CHG-UL-SCHED per cell through the eNB or the LSM.
Figure below depicts the basic operation of Type I UL MU-MIMO.
UE B @ Cell X
4. Each antenna elements receives Layer 2

each transmission
Layer 1
1. eNB determines whether MIMO allocation is h_b
permitted by DL/UL SINR, UE buffer status, etc. UE A @ Cell X
2. eNB B (UL scheduler) allocates the same
Resource Blocks to multiple UEs during the same frequency
subframe UE B
h_a
eNB B 3. UE transmits using same Resource

(Cell x) Blocks during same subframe
5. eNB separates and decodes

transmissions via MMSE-SIC UE A
To perform this feature, the following operations are considered:

• Determining MIMO capable UEs: For candidate UEs with non-GBR bearer,
the eNB determines MIMO capable UEs. They should have good channel
conditions in terms of DL/UL SINR over pre-defined value and heavy buffer
status.
• Selecting MIMO pairing UEs: The eNB assigns RB allocation to PF priority.

Confidential
When MIMO capable UE k is scheduled, the eNB checks whether the MIMO
capable UE k can be paired in the same resources with other MIMO capable
UE, already scheduled at the first layer.
• Allocating DM-RS CS: To guarantee the channel orthogonality between
MIMO pairing UEs, the eNB allocates a different Cyclic Shift (CS) for
Demodulation Reference Signal (DM-RS). This helps the eNB to separate
MIMO pairing UEs through channel estimation with use of DM-RS CS
orthogonality. The larger DM-RS CS difference provides greater
orthogonality. Orthogonality is achieved when each UE is allocated the same
number of resource blocks. Orthogonality is lost if each UE is allocated a
different number of resource blocks. This constraint reduces the flexibility of
resource block scheduling. The release 8 and 9 versions of the 3GPP
specifications define only CS to differentiate between DM-RSs.
• Transferring the scheduled information on PDCCH DCI format 0.
• Separating and decoding from each UE: At the eNB, transmissions from the
multiplexed users are treated as independent spatially multiplexed streams.
The eNB detects each individual user transmission using the Minimum Mean-
Squared Error-Success Interference Cancelation (MMSE-SIC) receiver to try
to decode each data stream separately.
UL MU-MIMO with Blacklist Management (Type II)

In correlated channels, MIMO gain of Type I UL MU-MIMO can degrade due to
high inter-layer interference between MIMO pairing UEs. The higher correlated
channels, the inter-layer interference can be larger. Therefore, the eNB determines
whether MIMO allocation is permitted or not by considering the cross-correlation
between MIMO paring UEs. Type II UL MU-MIMO supports cross-correlation
estimator, called blacklist management, as well as basic operation of Type I UL
MU-MIMO.
To perform this feature, the following operations are considered:
• Determining MIMO capable UEs: This operation is the same with Type I UL
MU-MIMO.
• Selecting MIMO pairing UEs: Unlike Type I UL MU-MMO, Type II UL MU-
MIMO selects MIMO pairing UEs by additionally considering cross-
correlation as well as basic operation of Type I UL MU-MIMO. To do this, the
eNB calculates the cross-correlation estimation metric. When this metric is
larger than the predefined value, the eNB does not permit MIMO allocation.
• Allocating DM-RS CS: This operation is the same with Type I UL MU-
MIMO.
• Transferring the scheduled information on PDCCH DCI format 0.
• Separating and decoding from each UE: This operation is the same with Type I
UL MU-MIMO.
Counters for UL MU-MIMO

Counters for total number of UL TTIs in which UL MU-MIMO is used
Confidential
(TotULMuMimoUtilizedTti), total number of UL TTIs (TotULTti), and total

number of UL MU-MIMO-paired UEs (TotULMuMimoPairedUE) are provided.
Using these counters, other counters for UL MU-MIMO TTI usage ratio
(ULMuMimoTtiUsage = (TotULMuMimoUtilizedTti / TotULTti) * 100) and UL
MU-MIMO-paired UEs per TTI (ULMuMimoPairedUEperTti =
TotULMuMimoPairedUE / TotULMuMimoUtilizedTti) are also provided.
Modified MIMO Exception Check Function

When MIMO-pairs with different UE category, MIMO-pairs with over-allocating
the supportable MaxTBS of UE category is not accepted.
SYSTEM OPERATION
How to Activate
Preconditions
There are no specific preconditions to activate this feature
To activate UL MU-MIMO without blacklist management, do the following:
• Run CHG-UL-SCHED and set UL_MIMO_MODE to 1 (TRUE) and set
UL_MU_MIMO_CORR_ON_OFF_FLAG to 0 (FALSE) for desired cell
number.
To activate UL MU-MIMO with blacklist management, do the following:
• Run CHG-UL-SCHED and set UL_MIMO_MODE to 1 (TRUE) and set
UL_MU_MIMO_CORR_ON_OFF_FLAG to 1 (TRUE) for desired cell number.
To deactivate UL MU-MIMO, do the following:
• Run CHG-UL-SCHED and set UL_MIMO_MODE to 0 (FALSE) for desired
cell number.
• When UL_MIMO_MODE is set to 0 (FALSE), the value of
UL_MU_MIMO_CORR_ON_OFF_FLAG is no longer be used.
Key Parameters
parameters.

Confidential
Parameter Descriptions of CHG-UL-SCHED/RTRV-UL-SCHED

CELL_NUM This parameter is a cell index number as an identifier. This value must not exceed
the maximum number of cells supported by the system.
UL_MIMO_MODE The parameter indicates whether to activate UL MU-MIMO.
• 0: UL MU-MIMO is de-activated
• 1: UL MU-MIMO is Activated
• 2 to 8: Reserved
UL_MU_MIMO_CORR_ This parameter enables or disables UL MU-MIMO with blacklist management.
ON_OFF_FLAG • 0: UL MU-MIMO with blacklist management is de-activated.
• 1: UL MU-MIMO with blacklist management is activated.
There are no configuration parameters associated with this feature.
Counters and KPIs

this feature.
UL_MU_MIMO ULMuMimoTtiUsage The ratio of uplink MU-MIMO utilized subframes.
ULMuMimoPairedUEperTti The average number of uplink MU-MIMO utilized UEs
per uplink MU-MIMO utilized subframes.
TotULMuMimoUtilizedTti The cumulated number of uplink MU-MIMO utilized
subframes during collection interval.
TotULTti The cumulated number of uplink subframes during
collection interval.
TotULMuMimoPairedUE The cumulated number of uplink MU-MIMO utilized
UEs during collection interval.
REFERENCE
[1] 3GPP TS 36.201 Evolved Universal Terrestrial Radio Access (E-UTRA); LTE
Physical channels and modulation

Confidential
LTE-ME3601, Uplink CoMP (JR)

INTRODUCTION
The increasing demand for high quality of service, coupled with the wireless
spectrum shortage, requires advanced wireless communications techniques to
enhance the cell-edge throughput. LTE release 11 standard introduces UL CoMP
(Coordinated multipoint) JR scheme, which utilizes multiple receive antennas
from multiple antenna site locations.
Samsung’s Intra-eNB UL CoMP implementation is not dependent on Release 11.
In the UL CoMP JR scheme, PUSCH transmitted by the UE is received jointly at
multiple points and combined using IRC at a time to improve the received signal
quality.
BENEFIT
This feature utilizes multiple Rx antennas from multiple points, which belong to
the same Channel Card, to enhance the received UL signal quality especially for
cell-edge UEs.
The following figure shows benefit of UL CoMP JR.
DEPENDENCY
Related Radio Technology: E-UTRAN (LTE)
LIMITATION
• This feature supports up to 4Rx combining for 2Rx antenna configuration
system or up to 8Rx combining for 4Rx antenna configuration system.
• This feature is not supported for Pico eNB.

Confidential
• (Rel10 support HW only limitation) When UL CoMP JR is enabled, the

maximum number of cells that eNB supports can be reduced.
• (Rel10 support HW only limitation) When UL CoMP support inter-modem
chip UL CoMP JR within a channel-cards, some parameters (Rx antenna count
and channel BW) should be set to the same value among the modem chips.
• This feature is not supported at massive MIMO cell.
SYSTEM IMPACT
capabilities.
None
UL CoMP JR improves cell-edge user throughput by diversity reception from
multiple points.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
UL CoMP JR architecture is based on joint processing of the signals received at
multiple points to improve especially cell-edge user throughput by diversity
reception, as depicted in the following figure.
In Samsung UL CoMP JR, the received data at each reception point within UL
CoMP Set are transferred to the serving cell for joint processing. This results in
radio gains especially for UEs at cell edge.
Feature Operation
UL CoMP JR is implemented in modem and uses IRC to combine uplink PUSCH
signals.

Confidential
Samsung UL CoMP JR operates within the group of cells called UL CoMP Set.
The UL CoMP Set is consisted of the predefined cells according to the type of
channel card.
Feature Activation/Deactivation
UL CoMP JR feature can be activated and deactivated on per cell basis (CHG-
ULCOMPJR-IDLE, UlCompJrOnOff).
UL CoMP Enhancement
The gain in the PUSCH SINR due to UL CoMP JR can be utilized in two ways
based on the configuration (CHG-ULCOMPJR-IDLE,
UlCompJrEnhancementFlag):
• UE Battery Saving Preferred Mode (default): The gain of UL CoMP JR is
used to reduce the Tx power of UE.
• UE UL Throughput Enhancement Preferred Mode: The gain of UL CoMP JR
is used to enhance the UL throughput of UE.
Cell-based Path Selection
UL CoMP JR can be done using the cell based path selection which is described as
below. The UE transmits data to all receive points and the receive points forward
the received data to the serving cell before decoding it.
The system decides the best points among the receive points of UL CoMP Set and
perform Rx combining (IRC) including the serving points and the best points. The
best points are selected on the basis of PUSCH SINR cell based selection using
average SINR of each cell.
The process of the cell based selection could be described briefly as follows:
• All paths of the serving cells are selected for combining
• Additional path for the combining required is selected after performing a
search. Cell based selection algorithm performs the best neighbor cell search
of all the neighbor cells within UL CoMP set belongs to the serving cell.
o The SINR for the neighboring cells are calculated.
o Neighbor Cell with largest average PUSCH SINR of all its paths is chosen.
• Combining is done for all the paths of the serving cell and the all the paths of
the chosen neighbor cell.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-ULCOMPJR-IDLE and set UL_COMP_JR_ON_OFF to 1 for
desired cell number.
• Run CHG-ULCOMPJR-IDLE and set UL_COMP_JR_ON_OFF to 0 for
desired cell number.
Key Parameters
This section describes the key parameters for activation, deactivation and
parameters.
Parameter Descriptions of CHG-ULCOMPJR-IDLE/RTRV-ULCOMPJR-IDLE
CELL_NUM The cell number. This value must not exceed the maximum number of cells
supported by the system. It is determined by FA/Sector. For example, if the
maximum capacity provided to the carrier per system is 1 FA/3 Sector, up to 3
cells are supported
UL_COMP_JR_ON_OFF The parameter indicates whether to activate UL CoMP JR.
• 0: UL CoMP JR is de-activated
• 1: UL CoMP JR is Activated
Counters and KPIs

this feature.
UL_COMP_JR ULCoMPActivatedUEperTti The average number of uplink CoMP activated UEs
per uplink subframes.
TotULCoMPActivatedUE The cumulated number of uplink CoMP activated UEs
during collection interval.
TotULTti The cumulated number of uplink subframes during
REFERENCE
[1] 3GPP TS 36.101 Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) radio transmission and reception

Confidential

Radio Resource Control (RRC); Protocol specification
[7] 3GPP TR 36.814 Evolved Universal Terrestrial Radio Access (E-UTRA);
Further advancements for E-UTRA physical layer aspects
[8] 3GPP TR 36.819 Coordinated multi-point operation for LTE physical layer
aspects
[9] 3GPP TR 36.913 Requirements for Evolved UTRA (E-UTRA) and Evolved
UTRAN (E-UTRAN)

Confidential
LTE-ME3603, Inter-Site UL CoMP (Non-Ideal

Backhaul)
INTRODUCTION
The Inter-Site UL CoMP (Non-ideal Backhaul) feature provides coordinative UL
reception across cells even belonging to non-collocated eNBs connected with non-
ideal backhaul.
BENEFIT
• Improvement of UL VoLTE quality (for example, packet loss)
• Enhancement of UL coverage
DEPENDENCY
• HW dependency: This feature is supported only between specific Samsung
eNBs (except channel card based on S8000 and S8300 modem)
LIMITATION
• This feature is applicable for D-RAN macro system with non-ideal backhaul.
• A maximum of three candidate eNBs for inter-site UL CoMP can be pre-
defined.
• Samsung eNB supports a maximum of 18 cells in eNB for inter-site UL CoMP
functionality.
SYSTEM IMPACT
capabilities.
Independencies between Features
None
The eNB provides enhancement for packet loss and residual error for UL VoLTE
UE.
Coverage
The uplink coverage for VoLTE can be increased.
Interface
New Samsung proprietary X2 interface is defined between Samsung eNBs.

Confidential
FEATURE DESCRIPTION
Inter-Site UL CoMP coordinates the antennas of multiple cells to receive signals
from a UE, as depicted in figure below.
Serving Cell Target Cell

(PCID A) (PCID B)
Signal Signal
BH
Serving Target
eNB eNB
EPC
eNB A
(Serving eNB)
eNB B
Joint Reception Cell (PCID A-1) (Target eNB)
(Combining) Selective Reception
UE3
UE1 Signal Signal
UE2
Cell (PCID A-2) Cell (PCID B-1)
Cell (PCID A-3)
Selection Combining
BH
Intra-CC UL CoMP
Serving Target
eNB eNB
EPC
SYSTEM OPERATION

Confidential
How to Activate
Precondition
Ensure that the following conditions are met before enabling this feature:
• A valid license key for LTEME3603 is required to activate this feature.
• Run CHG-ULCOMPJR-IDLE and set
INTER_SITE_UL_COMP_JR_ON_OFF to s INTER_SITE_UL_COMP_ON
per cell basis to enable Inter-Site Ul CoMP.
• Run CHG-NBR-ENB and set STATUS of CHG-NBR-ENB to EQUIP to
register eNB ID for inter site Ul CoMP.
• Run CHG-INTERSITECOMP-GROUP and set INTER_SITE_COMP_USAGE
to Active and register eNB_ID for Inter Site CoMP.
• Run CHG-INTERSITECOMP-INFO and set INTER_SITE_COMP_ON_OFF
to IS_COMP_ON.
• Run CHG-INTERSITECOMP-INFO and set INTER_SITE_COMP_ON_OFF
to IS_COMP_OFF.
Key Parameters
parameters.
CELL_NUM The cell number. This value must not exceed the maximum number
of cells supported by the system. It is determined by FA/Sector. For
example, if the maximum capacity provided to the carrier per system
is 1 FA/3 Sector, up to 3 cells are supported
INTER_SITE_UL_COMP_JR_ON_OF The parameter indicates whether to activate Inter-Site UL CoMP
F (Non-Ideal Backhaul).
• INTER_SITE_UL_COMP_OFF: Inter-Site UL CoMP is de-
activated
• INTER_SITE_UL_COMP_ON: Inter-Site UL CoMP is Activated
Parameter Descriptions of CHG-INTERSITECOMP-INFO/RTRV-

Confidential
INTERSITECOMP-INFO
INTER_SITE_COMP_ON_OFF Feature on/off state of Inter-site CoMP.
• IS_COMP_OFF (0): support inter-site CoMP functionality
• IS_COMP_ON (1): not support inter-site CoMP functionality
Parameter Descriptions of CHG-NBR-ENB/RTRV-NBR-ENB

NBR_ENB_INDEX This parameter specifies the index to change the neighbor eNB
information required for the operation of the NEI.
STATUS This parameter indicates the validity of the neighbor eNB. This
parameter must be set accurately since it determines the X2 link and
handover execution.
• N_EQUIP: The information is determined as invalid.
• EQUIP: The information is determined as valid.
To configure the feature settings, run the associated commands and set the key
parameters.
Parameter Descriptions of CHG-INTERSITECOMP-GROUP/RTRV-
INTERSITECOMP-GROUP
ENB_ID This parameter is the Target eNB ID for Inter-Site CoMP using
Non-Ideal backhaul. This is must be included Neighbor List and
can be changed when INTER_SITE_COMP_USAGE is
INACTIVE.
MCC This parameter is the PLMN information (MCC) of the eNB
where the EUTRAN neighbor cell, located around the eNB, is
belonged. Enter 3-digit number whose each digit range is 0-9.
This can be changed when INTER_SITE_COMP_USAGE is
INACTIVE.
MNC This parameter is the Broadcast PLMN list information (MNC) of
the neighbor cell. Enter a 2-digit or 3-digit number where each
digit ranges from 0 to 9.
This can be changed when INTER_SITE_COMP_USAGE is
INACTIVE.
INTER_SITE_COMP_USAGE Use of register enbId
• INACTIVE (0): not use Inter-Site CoMP for this eNB
• ACTIVE (1): use Inter-Site CoMP for this eNB
ENB_COMM_STATE It is the (read only) parameter for check the stat of Inter-Site
CoMP Group setup procedure.
Counters and KPIs

with this feature.

Confidential
REFERENCE
None

Confidential
LTE-ME3605, Inter-Site L1 UL CoMP

INTRODUCTION
The Inter-Site L1 UL CoMP feature provides coordinative UL reception across
cells belonging to non-collocated eNBs connected with Inter-BBU Switch (IBS).
BENEFIT
This feature uses multiple Rx antennas from multiple points to enhance the UL
throughput especially for cell-edge UEs.
DEPENDENCY
• HW dependency: Support of LCC1/LCC2 (Inter-CC, Intra-CC) and LCC4
(Inter-DU, Inter-CC, Intra-CC) are required.
LIMITATION
A maximum of eight eNBs can be connected within the same IBS switch.
SYSTEM IMPACT
capabilities.
None
The Inter-Site L1 UL CoMP feature improves cell-edge user throughput by
diversity reception from multiple points.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Inter-Site L1 UL CoMP coordinates the receive antennas of multiple cells to
especially improve cell-edge user’s UL throughput by soft-value combination, as
depicted in figure below.

Confidential
Serving Cell (PCID A) Target Cell (PCID B)
Signal Signal
Soft-value 2) PuschSINR, Target eNB

Combining Undecoded data
Serving eNB IBS

1) Scheduling Info.
Inter-Site L1 UL CoMP operates within the group of cells, called Inter-Site L1 UL

CoMP group. All UEs attached to cells within this group can be candidates for
soft-value combination.
Figure below depicts the operational procedure of the Inter-Site L1 UL CoMP
feature.
Serving Cell (PCID A) Target Cell (PCID B)
Signal Signal
MR (A3 event) trigger
Inter-Site L1 UL CoMP Group

Management
Inter-Site L1 UL CoMP
Request Control
Scheduling Info.
Inter-Site L1 UL CoMP
Admission Control & PUSCH
Demodulation Process
PuschSINR, Undecoded data
Combining JR Process
Inter-Site L1 UL CoMP Group Management

Each cell has own Inter-Site L1 UL CoMP group, which is comprised of cells with
the same UL carrier frequency and system bandwidth within inter-eNBs, which

Confidential
should be connected with IBS switching
Inter-Site L1 UL CoMP Request Control

The serving cell selects UL CoMP capable UEs and target cells based on MR (A3
event), and determines the requesting priority by using UL signal strength and
MR.
The serving cell chooses some UEs with higher requesting priority out of UL
CoMP capable UEs.
The serving cell transmits the cell-specific (for example, PCID) and UE-specific
information (for example, scheduled PRBoffset, PRBsize, and MCS) of the
selected UL CoMP UEs to the target cell via IP communication through 10G
Ethernet.
Inter-Site L1 UL CoMP Admission Control

The target cell aggregates UL CoMP UEs information requested from multiple
serving cells, and determines the admission priority by using UL signal strength
and MR.
The target cell chooses some UEs with higher admission priority out of the
requested UL CoMP UEs.
PUSCH Demodulation Process

The target cell tries to demodulate PUSCH with use of cell-specific (for example,
PCID) and UE-specific information (for example, scheduled PRBoffset, PRBsize,
and MCS) of the selected UL CoMP UE.
After PUSCH demodulation, the target cell transmits the soft-values of UL CoMP
UE to the serving cell via 10G Ethernet.
Combining JR Process
The serving cell combines JR between own and target cell’s soft-values.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-INTERL1ULCOMP-INFO and set

INTERSITE_L1_UL_COMP_ON_OFF to 1 for the desired cell number.
• Run CHG-ULCOMPJR-IDLE and set INTERSITE_L1_UL_COMP_ON_OFF
to 1 for the desired cell number.
• Run CHG-INTERL1ULCOMP-INFO and set
INTERSITE_L1_UL_COMP_ON_OFF to 0 for the desired cell number.
• Run CHG-ULCOMPJR-IDLE and set INTERSITE_L1_UL_COMP_ON_OFF
to 0 for the desired cell number.
Key Parameters
parameters.
Parameter Descriptions of CHG-INTERL1ULCOMP-INFO/RTRV-
INTERL1ULCOMP-INFO
INTERSITE_L1_UL_COMP_ON_OFF The parameter indicates whether to activate Inter-Site L1 UL CoMP per
eNB.
• 0: Inter-Site L1 UL CoMP is de-activated.
• 1: Inter-Site L1 UL CoMP is activated.
CELL_NUM The cell number. This value must not exceed the maximum number of
cells supported by the system. It is determined by FA/Sector. For
example, if the maximum capacity provided to the carrier per system is 1
FA/3 Sector, up to 3 cells are supported.
INTERSITE_L1_UL_COMP_ON_OFF The parameter indicates whether to activate Inter-Site L1 UL CoMP per
cell.
• 0: Inter-Site L1 UL CoMP is de-activated.
• 1: Inter-Site L1 UL CoMP is activated.
To configure the Inter-Site L1 UL CoMP Group, run the associated commands and
set the key parameters.
Parameter Descriptions of CHG-INTERL1ULCOMP-INFO/RTRV-
INTERL1ULCOMP-INFO

Confidential
NUM_PEER This parameter is the maximum number of peer eNBs that can be
registered in same IBS while working as C-RAN.
• When numPeer = 0, work as C-RAN.
• When numPeer = 0, work as D-RAN.
Parameter Descriptions of CHG-INTERL1ULCOMP-GROUP/RTRV-

INTERL1ULCOMP-GROUP
ENB_ID This parameter is the target eNB ID for Inter-Site L1 UL CoMP Group in C-
RAN. The eNB ID can be selected among eNB registered in Neighbor List.
The target eNB should be registered as neighbor eNB in CHG-NBR-
ENB/RTV-NBR-ENB. It can be changed when
INTERSITE_L1_UL_COMP_USAGE is Inactive.
This parameter is valid only in case INTERSITE_L1_UL_COMP_USAGE is
Active.
INode_ID This parameter is iNodeId of target eNB for Inter-Site L1 UL CoMP Group.
INTER_SITE_L1_UL_COMP_USAGE This parameter indicates whether to use registered enbId or not.
• Inactive (0): Not use about registered eNB ID
• Active (1): Use about registered eNB ID
ENB_COMM_STATE This parameter shows connection state between eNBs.
• 0 (Unknown): It does not connect to pairing eNB
• 1 (Enable): It can connect to pairing eNB
• 2 (NoResponse): It does not response to pairing eNB even if pairing eNB
tries to connect
• 4 (VersionMismatch): It does not connect to pairing eNB due to different
PKG Version
INTERSITE_L1_UL_COMP_Set_Size This parameter is the number of cells in InterSite L1 UL CoMP Set.
REFERENCE
User Equipment (UE) radio transmission and reception’

Confidential
description; Stage 2’
Radio Resource Control (RRC); Protocol specification’
[7] 3GPP TR 36.814 ‘Evolved Universal Terrestrial Radio Access (E-UTRA);
Further advancements for E-UTRA physical layer aspects’
[8] 3GPP TR 36.819 ‘Coordinated multi-point operation for LTE physical layer
aspects’
[9] 3GPP TR 36.913 ‘Requirements for Evolved UTRA (E-UTRA) and Evolved
UTRAN (E-UTRAN)’

Confidential
LTE-ME4003, FeICIC
INTRODUCTION
Further enhanced Inter-Cell Interference Coordination (FeICIC) is an interference
management feature defined in 3GPP release 10 / 11. In a heterogeneous network,
the macro-cells cause strong interference for the UEs connected to pico-cells. To
alleviate inter-cell interference and improve offloading performance, 3GPP R10
introduces enhanced Inter-Cell Interference Coordination (eICIC) feature, which is
based on Almost Blank Subframes (ABSs) and Cell-Range Expansion (CRE).
Moreover, to increase the benefit of eICIC, 3GPP R11 introduces the FeICIC
feature, which adds the requirement of CRS interference cancellation at UE
receivers.
BENEFIT
• Enhances Pico-cell-edge UE throughput using ABSs (applicable to all UEs).
• Offloads traffic using CRE (applicable to 3GPP R10+ UEs).
• Cancels CRS interference (applicable to 3GPP R11+ UEs).
DEPENDENCY
• Interfaces & Protocols: X2 I/F (3GPP TS 36.423 X2 Application Protocol)
LIMITATION
In operator's network, when macro-eNB vendor and pico-eNB vendor are
different, it is required to discuss about FeICIC operation between both vendors.
SYSTEM IMPACT
capabilities.
Inter-dependencies between features
None
FeICIC increases cell-edge user throughput of pico-cells by using ABS in which
macro-cell transmits only CRS and no data. As a result, UEs at the edge of pico-
cell do not face macro-cell's interference and experience higher throughput.
Coverage
FeICIC uses CRE in which both macro and pico-cell's ranges can be increased by
managing the handover triggering threshold settings for CRE UEs.

Confidential
Interfaces
Macro and pico-cells exchange load and ABS pattern information over the X2
interface using Load Information, Resource Status Request, Resource Status
Response, and Resource Status Update messages. They also exchange handover
triggering thresholds over the X2 interface using Mobility Change Request,
Mobility Change Acknowledge, and Mobility Change Failure messages.
FEATURE DESCRIPTION
The eICIC feature, which is first defined in 3GPP R10, has two main functions:
• Coordinating interference between macro-cell and pico-cell to mitigate
interference for pico-cell edge UE.
• Reducing traffic load imbalance in heterogeneous networks.
Accordingly, this feature is composed of three different functions: use of ABSs,
CRE, and CRS-IC. ABSs are used to mitigate interference for pico-cell edge UEs
while CRE is used to reduce traffic imbalance between macro and pico-cells. To
increase the benefit of eICIC, 3GPP R11 introduces the FeICIC feature, which
adds the requirement of CRS interference cancellation at UE receivers.
Almost Blank Subframes

In ABS, almost no control or data signal is transmitted. Macro-cell informs pico-
cell of ABS pattern via X2 interface. Pico-cell UE experiences CRS interference in
ABS.
Conventional FeICIC
ABS pattern
Macro Micro Macro Micro
Micro Coverage Micro Coverage

Rx. Power
Rx. Power
Low High
SINR SINR
Macro Power reduced

(No traffic)
Almost Blank Subframe

Macro
ABS pattern norma norma ABS norma norma norma norma norma
Cell Range Expansion

Typically, the pico cell has a small coverage due to low transmission power. Its

Confidential
range is expanded by handing over UEs from macro-cell to pico-cell although

pico-cell signal is not stronger than macro-cell signal. The CRE function enables
the load balancing between macro-cell and pico-cell.
Cell Range Expansion
Macro Micro
RSRP
Macro-to-Micro handover triggering condition:
CellIndiviaulOffsetmicro - A3Offset A3Offset RSRPmicro + CellIndiviaulOffsetmicro > RSRPmacro + A3Offset
Cell Reference Signal Interference Cancellation

CRS is always transmitted even in ABS. Pico-cell provides UEs with CRS
assistance information of Macro cell via RRC signaling. Pico-cell UE achieves
more improved SINR by cancelling interference of Macro’s CRS.
CR
Sm
arc
o
DATA
S
's CR Micro
Macro ation
inform
Macro
Mitigate interference from CRSmacro
UE removes
CRSmacro
-
+
UE receives UE detects
DATA + CRSmacro DATA!!
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-DL-EICIC and set partnerCellIdentity to the Cell Identity
of Macro cell in Pico cell.
• Run CHG-DL-EICIC and set eicicFlag to True in both Macro and Pico
cells.
To deactivate this feature and eICIC partnership establishment, do the following:
• Run CHG-DL-EICIC and set EICIC_FLAG of any of the eICIC partners to
False.
Key Parameters
parameters.
Parameter Descriptions of CHG-dl-eicic/RTRV-dl-Eicic
CELL_NUM The cell number. This value must not exceed the maximum number
of cells supported by the system. It is determined by FA/Sector. For
example, if the maximum capacity provided to the carrier per system
is 1 FA/3 Sector, up to 3 cells are supported
EICIC_FLAG This parameter is ON/OFF value of eICIC function.
PARTNER_CELL_IDENTITY This parameter is the cell identity value of the macro eNB cell in
which the pico eNB will establish partnership. This parameter defines
cell identity (28bit) part of E-UTRAN CGI as specified in 3GPP TS
36.443 section 9.2.3.11 (pico or small cell dedicated parameter).
parameters (common parameters for macro and pico cells).
CRE_FALG CRE function on/off
MAX_CRE_CIO_CHANGE_WAI This parameter specifies the number of times that satisfies CRE
Offloading decision continuously.
EICIC_BOUNDARY Specify CIO value for expansion of maximum eICIC UE
supportable CRE area. (EICIC_BOUNDARY value should be less
than or equal to FEICIC_BOUNDARY value.)
FEICIC_BOUNDARY Specify CIO value for expansion of maximum FeICIC UE
supportable CRE area. (FEICIC_BOUNDARY value should be
greater than or equal to EICIC_BOUNDARY value.)

Confidential
Parameters for macro cells

Parameter Descriptions of RTRV-MACEICIC-CTRL/CHG-MACEICIC-CTRL
T_ABS_PATTERN_UPDATE The period for the ABS pattern update
Parameters for macro cells

MAX_NUM_OF_PARTNER The maximum the number of Pico Cells which can be made a
partnership in one macro cell. (macro cell dedicated parameter)
T_CRE_STATUS_UPDATE This parameter is the term for CRE status update. (macro cell
dedicated parameter)
THR_CRE_ACT_MACRO When the status of CRE deactivated, this parameter checks CRE
activation at CRE status update intervals. At this time, specify
Macro cell load threshold for CRE activation. To activate CRE, the
Macro cell load should be above the threshold. (macro cell
dedicated parameter)
THR_CRE_ACT_PICO When the status of CRE deactivated, this parameter checks CRE
activation at CRE status update intervals. At this time, specify Pico
cell load threshold for CRE activation. To activate CRE, the Pico
cell load should be lower than the threshold. (macro cell dedicated
parameter)
THR_CRE_UE_RATIO When the status of CRE deactivated, this parameter checks CRE
activation at CRE status update intervals. At this time, specify
macro CRE UE ratio threshold for CRE activation. To activate
CRE, the macro CRE UE ratio that offloading available should be
higher than the threshold. (macro cell dedicated parameter)
THR_CRE_DEACT_ABS_FULL In case of CRE Active State, a Macro cell checks to execute CRE
deactivation each of CRE state update period. This parameter is
to configure threshold of * ABS Full for CRE deactivation
condition. ABS Full should be lower than this parameter value to
be CRE deactivation. (macro cell dedicated parameter)
* ABS Full = Number of RBs usage for Pico CRE UEs / (Number
of RBs usage for Macro UEs + Number of RBs usage for UEs of
all Pico partners) * 100
Parameters for pico cells

PARTNER_MCC[4] This parameter is the Mobile Country Code (MCC) as the PLMN
information that represents the macro eNB Cell in which the Pico eNB
will establish a partnership (pico or small cell dedicated parameter).
PARTNER_MNC[4] This parameter is Mobile Network Code (MNC) as the PLMN
information that represents the macro eNB Cell in which the Pico eNB
will establish a partnership (pico or small cell dedicated parameter).
T_PARTNERSHIP_GUARD This parameter is the waiting time to re-establish partnership in case
of failure to repeat the specified number of transfers trying to
establish a partnership (pico or small cell dedicated parameter).
T_PARTNERSHIP_RETRY This parameter is the transmission time to establish partnership, in

Confidential
case of failure in partnership establishment (pico or small cell
dedicated parameter).
PARTNERSHIP_TX_COUNT This parameter is the transmission count to establish partnership, in
case of failure in the partnership establishment (pico or small cell
dedicated parameter).
Counters and KPIs

Table below outlines the main counters associated with this feature.
Family Display name Type Name Type Description
EICIC PartnershipCount The average count of Partner Cell in
Partnership
PartnershipCountTot Sum of PartnershipCount collected
PartnershipCountCnt Count of PartnershipCount collected
EICICCapaUECount The count of UE supported FGI 115
EICIC_PARTNERSHIP CompositeAvailCapa The average Capacity Value of
Composite Availability Capacity
CompositeAvailCapaTot Sum of CompositeAvailCapa collected
CompositeAvailCapaCnt Count of CompositeAvailCapa
collected
DLABSstatus The average ratio of used ABS
resource
DLABSstatusTot Sum of DLABSstatus collected
DLABSstatusCnt Count of DLABSstatus collected
CREUECount The average count of CRE UE per
partner Cell
CREUECountTot Sum of CREUECount collected
CREUECountCnt Count of CREUECount collected
EICICHOAtt The number of HO attempts of eICIC
UE after the HO is triggered by CRE
Offloading
EICICHOSucc The number of successful HOs of
eICIC UE that were triggered by CRE
Offloading.
EICICPartnershipCnt Collection count of eICIC Partnership
EICICPartnershipCid pcID of which collection is requested
FeICICHOAtt The number of HO attempts of FeICIC
UE after the HO is triggered by CRE
Offloading
FeICICHOSucc The number of successful Hos of
FeICIC UE that were triggered by CRE
Offloading.
EICICCIOAvg Average eICIC CIO value for Pico
partner cell
EICICCIOMin Minimum eICIC CIO value for Pico
partner cell
EICICCIOMax Maximum eICIC CIO value for Pico
partner cell

Confidential

EICICCIOTot Total eICIC CIO value for Pico partner
cell
EICICCIOCnt Count of collecting eICIC CIO for Pico
partner cell
FeICICCIOAvg Average FeICIC CIO value for Pico
partner cell
FeICICCIOMin Minimum FeICIC CIO value for Pico
partner cell
FeICICCIOMax Maximum FeICIC CIO value for Pico
partner cell
FeICICCIOTot Total FeICIC CIO value for Pico
partner cell
FeICICCIOCnt Count of collecting FeICIC CIO for
Pico partner cell
EICIC_ABS AvgABSNum This counter indicates the average of
the number of ABS pattern usage in
the FDD cell during the collection
cycle.
ABSBin’X’ This counter indicates the usage rate
of the ABS pattern whose ABS rate is
x/40 among the ABS (Almost Blank
Subframe) patterns that are applied to
the FDD cell during the collection
cycle.
ABSBin’X’UsedCnt This counter indicates the accumulated
number of times for which the ABS
pattern whose ABS rate is X/40 is used
in the FDD cell that was collected
periodically.
REFERENCE
[5] 3GPP TS36.300, Evolved Universal Terrestrial Radio Access (E-UTRA) and
[6] 3GPP TS36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
Resource Control (RRC) Protocol specification
[7] 3GPP TS36.423 Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); X2 application protocol (X2AP)

Confidential
[8] 3GPP TR 36.814 Evolved Universal Terrestrial Radio Access (E-UTRA);

[9] 3GPP TR 36.819 Coordinated multi-point operation for LTE physical layer
aspects
[10] 3GPP TR 36.913 Requirements for Evolved UTRA (E-UTRA) and Evolved
UTRAN (E-UTRAN)

Confidential
LTE-ME4001, ICIC
INTRODUCTION
In an LTE network, there is no intra-cell interference as the UEs are assigned
orthogonal Physical Resource Blocks (PRBs). However, cell-edge UEs receive
strong inter-cell interference from the neighbor cells. Inter-cell interference is not
very strong for UEs located close to cell-center as they are quite far away from the
neighbor cells. Inter-Cell Interference Coordination (ICIC) can be used to lower
the inter-cell interference for cell-edge UEs.
BENEFIT
Increase in cell-edge UE performance due to decrease in inter-cell interference.
DEPENDENCY
• Interface & Protocols: X2 interface (X2 I/F)
LIMITATION
Currently, this feature is operated only for DL.
SYSTEM IMPACT
capabilities.
This feature cannot simultaneously operate with FeICIC or DL smart features.
This feature coordinates inter-cell interference in the network. Therefore, cell-edge
UEs performance is enhanced when this feature is enabled.
Coverage
None
Interfaces
This feature uses RNTP IE in X2 LOAD INFORMATION message for
exchanging power allocation information with neighbor cells.
FEATURE DESCRIPTION
ICIC supports the interference coordination by using power allocation pattern
(RNTP) of neighbor cells, which is exchanged via X2 IF. ICIC operation is based
on the following information:
Confidential
• DL SINR of the UEs: Based on the SINR, which is calculated by reported

CQI, an eNB performs UE categorization whether the UEs are at cell-edge or
at cell-center.
• RNTP information: This is exchanged between neighbor cells using X2 IF
message including transmit power level for each PRB index.
Cell 1 Cell 2
Tx power
Tx power
RNTP UE B UE C RNTP
threshold UE B UE A UE A UE D threshold UE D UE C
RNTP 11 … 1100 … 00 PRB RNTP 00 … 0011 … 11 PRB

bitmap bitmap
X2 interface
DL ICIC Operation
This feature can be operated by using DL_ICIC_TYPE (CHG-SON-DLICIC).
• DL-ICIC via X2 IF is operated by setting DL_ICIC_TYPE (CHG-SON-
DLICIC) to sonIcicDlDynamicStd.
o The eNB performs the UE categorization using DL SINR based reported
CQI. If SINR of the UE calculated by CQI > DL_SINR_THRESHOLD
(CHG-SON-DLICIC), the UE is categorized by the cell-center UE and
this UE should use low level transmit power. Otherwise, the UE is
categorized by the cell-edge UE and this UE should use high level transmit
power. eMTC UEs always use high level transmit power.
o The eNB determines the total load per each UE category.
o Considering neighbor cells’ RNTP bitmaps and the load, the eNB
coordinates its RNTP bitmap and PRB allocation to mitigate inter-cell
interference. When eMTC VoLTE and frequency hopping functions are
used, PRBs included in eMTC VoLTE and frequency hopping
narrowbands always have RNTP = 1 (that is, these PRBs have high level
transmit power).
Due to above DL ICIC via X2 IF operation, the frequency bands with high level
power is non-overlapped among neighbor cells. Therefore, the cell-edge UEs will
not face strong inter-cell interference.
• DL-ICIC without X2 IF is operated by setting DL_ICIC_TYPE (CHG-SON-
DLICIC) to sonIcicDlDynamicSamsung.
o The eNB performs the UE categorization using DL SINR based reported
CQI. If SINR of the UE calculated by CQI > DL_SINR_THRESHOLD
(CHG-SON-DLICIC), the UE is categorized by the cell-center UE and
this UE should use low level transmit power. Otherwise, the UE is
categorized by the cell-edge UE and this UE should use high level transmit

Confidential
power.
Although DL-ICIC function without X2 IF cannot coordinate the power allocation
pattern considering neighbor cell information, the interference can be reduced by
low level Tx power.
Counters
Samsung eNB supports DL_ICIC_RNTP counter family, which has counters for
average, minimum, and maximum number of PRBs with unrestricted TX power
for RNTP.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-SON-DLICIC and RTRV-SON-DLICIC to configure the ICIC
feature, or to verify the configuration.
• Set DL_ICIC_TYPE to sonIcicDlDynamicStd to operate DL-ICIC via
X2 IF.
• Set DL_ICIC_TYPE to sonIcicDlDynamicSamsung to operate DL-
ICIC without X2 interface.
• Set DL_ICIC_TYPE to sonIcicDlNone.
Key Parameters
parameter.
Parameter Description of CHG-SON-DLICIC/RTRV-SON-DLICIC
DL_ICIC_TYPE This parameter specifies Downlink Inter-Cell Interference Coordination (DL-ICIC)

Confidential
type.
• IcicDlNone: The DL ICIC function is not performed.
• IcicDlDynamicStd: The dynamic ICIC function by X2 IF is performed. This
function considers neighbor cells interference.
• IcicDlDynamicSamsung: The DL power allocation based on the UE channel
condition is performed. This function does not consider neighbor cells
interference.
parameters.
Parameter Description of CHG-SON-DLICIC/RTRV-SON-DLICIC
DL_SINR_THRESHOLD This parameter is UE SINR when p-a value changes for dynamic ICIC operation.
Counters and KPIs

DL ICIC RNTP UnresTxPowerAvg The average number of PRBs with unrestricted TX
Information power for RNTP per PRB during the collection interval.
UnresTxPowerCount The total number of PRBs with unrestricted TX power
during the collection interval.
RNTPCount The number of RNTP per PRB during the collection
interval.
UnresTxPowerMax The maximum number of PRBs with unrestricted TX
power for RNTP per PRB during the collection interval.
UnresTxPowerMin The min number of PRBs with unrestricted TX power
for RNTP per PRB during the collection interval.
UnresTxPowerMaxCnt The cumulated update count of RNTPMax.
UnresTxPowerMinCnt The cumulated update count of RNTPMin.
REFERENCE
[1] 3GPP TS36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and

Confidential
LTE-ME4005, IRC
INTRODUCTION
Advanced receivers provide an implementation method to enhance further the
capacity of LTE system. A typical example is the Minimum Mean squared Error
(MMSE) receiver with Interference Rejection Combining (IRC). The ability of
IRC receiver to suppress interference is a function of many factors including the
number and strength of the interfering signals and the number of receive antennas.
Samsung eNB supports interference rejection combining based on MMSE criterion
to provide the improved performance at cell boundary users that experience
serious interference from other cells.
BENEFIT
An operator can achieve the better quality of signal and improve system
performance by cancelling the interference at eNB receiver.
DEPENDENCY
None
LIMITATION
This feature is not supported for Indoor Pico.
SYSTEM IMPACT
FEATURE DESCRIPTION
The advanced receiver employing IRC is effective in improving the cell-edge user
throughput. The IRC receiver utilizes the correlation of the interference of multiple
receiver branches, and combines the received signals for multiple receiver
branches so that the Mean Square Error (MSE) between the combined signal and
the desired signal is minimized instead of Maximal Ratio Combining (MRC). In
uplink, the eNB receiver utilizes IRC scheme, which is based on MMSE criterion
to support interference cancellation function.
Interference Rejection Combining (IRC)

The eNB receiver performs interference rejection combining to support
interference cancellation as follows:
• The channel estimator of eNB receiver estimates the channel of desired signal,
and generates the covariance matrix of interference and noise.

Confidential
o Estimate the channel matrix of the desired signal
estimated channel matrix

o Estimate the covariance matrix of interference and noise
desired signal vector

• Using the estimated channel and the covariance matrix, MMSE weight is
calculated to perform IRC.
o Minimum Mean Squared Error (MMSE) criterion
o MMSE criterion achieves the optimal balance the noise enhancement and
interference suppression
o Combined weight
• Interference rejection is achieved by MMSE combining at eNB receiver.
The IRC scheme based on MMSE criterion achieves an optimal balance of noise
enhancement and interference suppression. Therefore, the IRC provides the
enhanced performance to UEs at the cell boundary that experience serious
interference from other cell.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-PUSCH-IDLE and set IRC_ENABLE to True (IRC on)
(IRC_ENABLE = 1).
• Run CHG-PUSCH-IDLE and set IRC_ENABLE to False (IRC off)
(IRC_ENABLE = 0).

Confidential
Key Parameters
feature.
parameter.
IRC_ENABLE This parameter is used to enable to use IRC
• 0: False (IRC off)
• 1: True (IRC on)
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME4007, Interference Avoidance in IDC

INTRODUCTION
As diverse data applications are used extensively in a UE, multiple radio
transceivers like LTE, WiFi, Blue tooth, GPS, and GNSS receivers are
implemented in the UE. To avoid interference from these transceivers, RAN
enhancements are performed for FDM, TDM, and UE Autonomous Denial Mode.
FDM Mode is to move LTE signal away from the ISM band, thereby minimizing
the interference from in-device. Inter-frequency handover and removing SCells
from the set of serving cells are two solutions used to move LTE signal away from
ISM band. The TDM mode is to ensure that transmission of a radio signal does not
coincide with reception of another radio signal.
LTE DRX mechanism is used to provide TDM patterns (periods during which the
LTE UE may or may not be scheduled) to resolve the IDC issues. The DRX-based
TDM solution should be used in a predictable way, that is, the eNB should ensure
a predictable pattern of unscheduled periods by means of DRX mechanism. In the
UE Autonomous Denial Mode, the eNB configures a long-term denial rate for UE
UL subframe transmission through dedicated RRC signaling message to limit the
amount of LTE UL autonomous denials when there is in-device interference.
BENEFIT
• Interference avoidance for in-device coexistence between multiple radio
transceivers.
• Improvements in system efficiency.
DEPENDENCY
• Others: Release 11 UE to support InDeviceCoexIndication
LIMITATION
• The DRX proposal of the UE in TDM solution is not applied when the UE
uses VoLTE (QCI #1) service because the DRX pattern might collide with
SPS or TTI bundling function. Once the eNB releases the DRX pattern
proposed by UE, it does not get back to that DRX pattern before the UE
proposes it again.
• When ANR DRX is configured for the UE, the eNB stops applying the DRX
pattern proposed by the UE or does not accept the DRX pattern proposal. Once
the eNB releases the DRX pattern proposed by UE, it does not get back to that
DRX pattern before the UE proposes it again.

Confidential
SYSTEM IMPACT
capabilities.
• Interdependent feature: LTE-SW1007 Inter-Frequency Handover
If the FDM-based method is used, the inter-frequency handover can be used to
handover UE to a different frequency to reduce interference.
• Interdependent feature: LTE-SW5500 CA Call Control
If the FDM-based solution is used, the impacted SCell can be released to
reduce interference.
• Interdependent feature: LTE-ME3402 Active DRX
If the TDM-based solution is used, different DRX pattern can be used for UE
active DRX setting.
This feature potentially can release SCell, so the system throughput can be
impacted.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
To access various networks and services ubiquitously, the UE is equipped with
multiple radio transceivers like LTE, WiFi, Bluetooth transceivers, and GNSS
receivers. Due to extreme proximity of these multiple transceivers within the same
UE operating on adjacent frequencies or sub-harmonic frequencies, the
interference power coming from a transmitter of the collocated radio may be much
higher than the actual received power level of the desired signal for a receiver.
This situation causes In-Device Coexistence (IDC) interference.
The following are some interference scenarios:
• LTE and BT earphone (VoIP and Multimedia Service)
• LTE and WiFi Portable router
• LTE and WiFi Offload
• LTE and GNSS receiver

Confidential
When the UE experiences a level of IDC interference that cannot be solved by the
UE itself and a network intervention is required, the UE sends an IDC indication
via dedicated RRC signaling to report the problems.
When notified of IDC problems through an IDC indication from the UE, the eNB
proposes the following three solutions:
• Frequency Division Multiplexing (FDM)
• Time Division Multiplexing (TDM)
• UE Autonomous Denial
The operator can enable or disable each of the IDC solutions by using:
• IDC_SUPPORT (CHG-IDC-PARAM)
• FDM solution by FDM_SOLUTION_OPTION (CHG-IDC-PARAM)
• TDM solution by TDM_SOLUTION_OPTION (CHG-IDC-PARAM)
• UE's autonomous denial of subframes by AUTO_DENY_SUBFRAME and
AUTO_DENY_VALIDITY (CHG-IDC-PARAM)
When both FDM and TDM solutions are enabled, the eNB applies the FDM
solution first. If the FDM solution is not applicable to the UE, for example,
because multi-carriers are not present or FDM solution is not proposed by the UE,
then the TDM solution is applied.
The UE can propose a preferred DRX operation by setting the
noBenFromBatConsumpOpt flag ON or by sending an IDC indication message
that requests TDM solution. When the eNB receives both DRX related requests,
the eNB processes them in the order of reception. Therefore, the latest DRX
proposal is applied to the UE.
The DRX proposal of the UE in TDM solution is not applied when the UE uses
VoLTE (QCI #1) service because the DRX pattern might collide with SPS or TTI
bundling function. Once the eNB releases the DRX pattern proposed by UE, it
does not get back to that DRX pattern before the UE proposes it again.
When ANR DRX is configured for a UE, the eNB stops applying the DRX pattern
proposed by the UE or does not accept the DRX pattern proposal. Once eNB
releases the DRX pattern proposed by UE, it does not get back to that DRX pattern

Confidential
before the UE proposes it again.
FDM-based Solution
The FDM solution is to move the LTE signal away from the ISM band by either
performing inter-frequency handover within E-UTRAN or removing SCells from
the set of serving cells.
Performing an Inter-Frequency Handover
• The eNB sends an RRC connection reconfiguration message to UE, which is

configured for notifying IDC indication (through OtherConfig-r9 à IDC-
Config-r11 à IDC-Indication-r11 IE).
• The UE responds with RRC connection reconfiguration complete.
• When the UE experiences a level of IDC interference that cannot be solved by
the UE itself and a network intervention is required, the UE sends an
InDeviceCoexIndication message to the eNB with setting
affectedCarrierFreqList/ affectedCarrierFreqCombList-r11.
• Based on the operator configuration, if the value of the flag
FDM_SOLUTION_OPTION (CHG-IDC-PARAM) is set to 1 or 3 (IFHO or
Both), the eNB decides for the need of measurement and responds by sending
the RRC connection reconfiguration message requesting for Measurement
config.
• Upon receiving the message, the UE responds by RRC connection
reconfiguration complete message.

Confidential
• The UE performs measurement and responds to eNB with measurement report

message.
• Based on the received measurement report and the event type, the eNB decides
and performs inter-frequency handover.
Removing SCells (Secondary Cells) from the Set of Serving Cells
• The eNB sends the RRC connection reconfiguration message to UE, which is
configured for notifying IDC indication if the UE is capable for IDC reporting
(through OtherConfig-r9 à IDC-Config-r11 à IDC-Indication-r11 IE).
the UE itself and a network intervention is required, the UE sends the
InDeviceCoexIndication message to eNB with setting affectedCarrierFreqList.
• Based on the operator configuration, If the value of the flag
FDM_SOLUTION_OPTION (CHG-IDC-PARAM) is set to 2 or 3
(SCellRelease or Both), the eNB responds by sending the RRC connection
reconfiguration message with one or more Scells to be removed from the set of
serving cells. If UL CA with IDC is enabled and
affectedCarrierFreqCombList-r11 received, the eNB avoids considering the
carrier frequency combinations indicated in AffectedCarrierFreqCombList-r11
as UL CA candidate combination until a new IDC indication message received
without the affected UL combination. In case the
AffectedCarrierFreqCombList-r11 is empty and victim system is GNSS, the
eNB performs release all UL Scell or ignores the
AffectedCarrierFreqCombList-r11 IE based on the configuration.
• Upon receiving the message, the UE releases the set of secondary cells, and
thereby, minimizing interference.

Confidential
TDM-based Solution
Perform a DRX-based Mechanism
InDeviceCoexIndication message to eNB with setting tdm-AssistanceInfo-r11
include drx-CycleLength, drx-Offset and drx-ActiveTime.
TDM_SOLUTION_OPTION (CHG-IDC-PARAM) is set to 1 or 3
(DRXSupport or Both support), the eNB responds to UE a DRX configuration
mechanism from the appropriate values received from the UE (drx-
ActiveTime -- sf20, sf30 and so on, drxCycleLength -- sf40, sf64 and so on,
drxOffset = [(SFN * 10) + subframe number] modulo (drx-CycleLength)).
Perform a Subframe Reservation Pattern to UE

Confidential

InDeviceCoexIndication message to eNB with setting tdm-AssistanceInfo-
r11which includes idc-SubframePatternList. This subframe pattern explains
subframe pattern that includes a HARQ timeline.
TDM_SOLUTION_OPTION (CHG-IDC-PARAM) is set to 2 or 3
(SubframePatternSupport or Both support), the eNB performs subframe
pattern reservation to UE as per spec TS 36.213[23] (8.0, 7.3, 8.3, and 9.1.2).
For example, if the subframe is set to 1 in the subframe pattern, also the
corresponding subframes carrying the potential UL grant [23, 8.0], the UL
HARQ retransmission [23, 8.0] and the DL/UL HARQ feedback [23, 7.3, 8.3,
9.1.2] shall be set to 1. If UL CA is configured, the subframe pattern applies to
both Pcell and Scell carriers.
UE Autonomous Denial Solution
• Based on the operator configuration, AUTO_DENY_SUBFRAME and

AUTO_DENY_VALIDITY (CHG-IDC-PARAM), the eNB configure a long-
term denial rate through the RRCconnectionreconfiguration message to UE to
limit the amount of LTE UL autonomous denials (through OtherConfig-r9 à
IDC-Config-r11 à autonomousDenialParameters-r11 IE).
• The UE responds with RRC connection reconfiguration complete. Further, the
UE denies any UL transmission from the received UL subframe value and the
period provided by eNB.
SYSTEM OPERATION
How to Activate

Confidential
Preconditions
• Run CHG-IDC-PARAM and set IDC_SUPPORT to a specific value instead of
Not_Support.
• Run CHG-IDC-PARAM and set IDC_SUPPORT to Not_Support.
Key Parameters
parameter.
Parameter Descriptions of CHG-IDC-PARAM/RTRV-IDC-PARAM
IDC_SUPPORT This parameter indicates whether to use Interference Avoidance in IDC function.
• Not_Support: Interference Avoidance in IDC function is not supported.
• IdcIndicationSupport: IDC Indication is supported.
• AutoDenySupport: The setting of autonomousDenialParameters is supported.
• BothSupport: IDC Indication and the setting autonomousDenialParameters are
supported.
parameters.
Parameter Descriptions of CHG-IDC-PARAM/RTRV-IDC-PARAM
IDC_INDEX index
IDC_SUPPORT This parameter indicates whether to use Interference Avoidance in IDC function.
• Not_Support: Interference Avoidance in IDC function is not supported
• IdcIndicationSupport: IDC Indication is supported.
• AutoDenySupport: The setting of autonomousDenialParameters is supported.
• BothSupport: IDC Indication and the setting autonomousDenialParameters are
supported.
AUTO_DENY_SU Indicates the maximum number of the UL subframes for which the UE is allowed to deny
BFRAME any UL transmission. (TS36.331)
• n2: 2subframes, n5: 5subframes and so on
It is used when IDC_SUPPORT is set to autoDenySupport or bothSupport.
AUTO_DENY_VA Indicates the validity period over which the UL autonomous denial subframes is counted.
LIDITY (TS36.331)

Confidential
• sf200: 200 subframes, sf500: 500 subframes and so on.
It is used when IDC_SUPPORT is set to autoDenySupport or bothSupport.
FDM_SOLUTION It is option of FDM_SOLUTION
_OPTION • Not_Support: FDM_SOLUTION is not used.
• IFHO: Perform the IFHO (Inter Frequency Handover) to the other Carrier to minimize
interference.
• SCellRelease: Perform the SCell Release to minimize interference.
• Both: Perform both IFHO and SCell Release.
TDM_SOLUTION It is option of TDM_SOLUTION
_OPTION • Not_Support: TDM_SOLUTION is not used
• DRXSupport: Support DRX operation to minimize interference.
• SubframePatternSupport: Support subframe reservation pattern to minimize
interference.
• BothSupport: Support both DRX and SubframePattern.
IDC_MEAS_GAP Indicates a holding time for the IDC Inter-Frequency Handover measurement Gap
_TIMER operations.
Parameter Descriptions of CHG-EUTRA-A5CNF/RTRV-EUTRA-A5CNF

PURPOSE It is used for Handover for interference avoidance in IDC.
A5_THRESHOLD This parameter is the A5_Threshold1 value of Event A5 during ReportConfigEutra
1_RSRP configuration. This value used when the TRIGGER_QUANTITY is set to RSRP. The
actual RSRP measurement value must be set to A5_THRESHOLD1_RSRP-140 (dBm).
A5_THRESHOLD This parameter is the A5_Threshold2 value of Event A5 during ReportConfigEutra
2_RSRP configuration. This value used when the TRIGGER_QUANTITY is set to RSRP. The
actual RSRP measurement value must be set to A5_THRESHOLD2_RSRP-140 (dBm).
Counters and KPIs

with this feature.
REFERENCE
description; Stage 2. Release 11.
Resource Control (RRC) protocol specification. Release 11.
[3] 3GPP TS36.816 Evolved Universal Terrestrial Radio Access (E-UTRA); Study
on signaling and procedure for interference avoidance for in-device coexistence.
Release 11.
[4] 3GPP TS36.816 Evolved Universal Terrestrial Radio Access (E-UTRA);
Requirements for support of radio resource management. Release 11.

Confidential
LTE-ME4008, Network Assisted Interference

Cancellation and Suppression (NAICS)
INTRODUCTION
CRS and PDSCH transmission by cells causes interference to UEs in the
neighboring cells. This interference is severe for cell-edge UEs. In 3GPP Rel-12,
the UEs can cancel this interference by using Network Assisted Interference
Cancellation and Suppression (NAICS) information sent by the network.
BENEFIT
This feature improves the DL performance because the UE can cancel PDSCH
interference from neighboring cells.
DEPENDENCY
• Interface & Protocols:
o TS 36.331: The UE should be able to receive NAICS assistance
information.
o TS 36.423: eNBs should be able to exchange NAICS assistance
information over X2 interface.
LIMITATION
None
SYSTEM IMPACT
capabilities.
Interdependencies between features
This feature affects LTE-ME6018, CRS-IC Support feature. Since CRS-IC
assistance information is a subset of NAICS assistance information, CRS-IC
assistance information is not sent separately to UEs when this feature is used.
Performance and capacity
This feature allows UEs to cancel PDSCH interference from neighbor cells by
providing information required for interference cancellation (that is, NAICS
assistance information) through RRC signaling to UEs. NAICS is more effective
for cell-edge UEs. Due to NAICS, DL air throughput, DL residual BLER, and DL
MCS allocation will improve. This improvement can be observed using the
available counters, which are described in LTE-OM9101 (L1 and L2 Counters)
feature.

Confidential
Coverage
None
Interfaces
This feature uses Neighbor Relation Table (NRT) to gather NAICS assistance
information of neighboring cells. NRT is prepared by adding neighbor relations
through X2 interface. NRT should be available before this feature can be used. The
gathered information is provided to UEs through dedicated
RrcConnectionReconfiguration messages.
FEATURE DESCRIPTION
CRS and PDSCH transmission by cells causes interference to UEs in the
neighboring cells. This interference is particularly severe for cell-edge UEs.
However, UEs with interference cancellation-capable receivers can cancel
neighbor cell interference if they know some interference parameters. For
interference cancellation, UEs blindly detect some dynamically varying parameters
while the remaining semi-statically varying parameters are provided to them by
eNB as NAICS assistance information. Using this feature, an eNB can provide
NAICS assistance information of each serving cell (that is, PCell or SCell) to a
UE. This feature can be enabled or disabled by setting NAICS_ENABLE (CHG-
NAICS-CONF) ON or OFF, respectively.
Figure below depicts the NAICS operation.
PD
B
H
1. Cells A and B exchange NAICS assistance

SC
SC
information via X2 interface.

PD
HA
2. Cell A provides NAICS assistance information

of cell B to UE A.
Cell A Cell B 3. UE A cancels interference from PDSCHB.
UE A UE B
X2 signaling
The eNB provides NAICS assistance information for each serving cell through the
RRC Connection Reconfiguration message. This information is included in
NeighCellsInfo-r12 IE. One IE can be provided for each serving cell.
Table below outlines the contents of the NAICS assistance information in
NeighCellsInfo-r12 IE.
Fields in NeighCellsInfo-r12 IE Description Implementation
physCellId-r12 Physical cell ID (PCID) of neighbor PCID of neighbor cell
cell
crs-PortsCount-r12 Number of CRS antenna ports used Number of CRS antenna ports used
by neighbor cell by serving cell
mbsfn-SubframeConfig-r12 MBSFN subframe configuration of MBSFN subframe configuration of

Confidential
Fields in NeighCellsInfo-r12 IE Description Implementation

neighbor cell serving cell
p-aList-r12 PA parameter list of neighbor cell Obtained from Dynamic DL
transmission information IE
(explained later)
p-b-r12 PB parameter of neighbor cell Obtained from Dynamic DL
transmission information IE
(explained later)
transmissionModeList-r12 List of transmission modes used by Obtained from Dynamic DL
neighbor cell transmission information IE
(explained later)
resAllocGranularity-r12 Resource allocation and precoding resAllocGranularity-r12 = 1
granularity in terms of number of
PRB pairs
A serving cell and all its neighbor cells use the same CRS port configuration and
the same MBSFN configurations. So, for these fields, serving cell configuration is
used instead of neighbor cell configuration. This may lead to some performance
degradation at CRS and MBSFN boundaries. The remaining neighbor cell
information is obtained by serving cell through X2 interface.
Figure below depicts the procedure of NAICS assistance information transfer over
the X2 interface.
eNB-1 eNB-2
X2 setup
LOAD INFORMATION
1 (Invoke indication = Start NAICS information)
LOAD INFORMATION
(Dynamic DL transmission information)
2
LOAD INFORMATION
(Dynamic DL transmission information)
3
LOAD INFORMATION
4 (Invoke indication = Stop NAICS information)
1 After X2 setup, eNB-1 requests eNB-2 to provide NAICS assistance

information for its cells.
2 eNB-2 provides information to eNB-1 using Dynamic DL Transmission
Information IE.
3 If eNB-2 information is changed, it sends updated information to eNB-1.
4 (Optional) If eNB-1 does not need eNB-2 information, it requests eNB-1 to
Confidential
stop sending this information.

The contents of Dynamic DL Transmission Information IE are given below. The
resAllocGranularity-r12 IE is not included in this IE. This feature uses
resAllocGranularity-r12 = 1, which is the same as Samsung's resource allocation
and precoding granularity.
Table below outlines the contents of the Dynamic DL Transmission Information
IE.
IE/Group Name Presence Range IE Type and Reference Semantics Description
CHOICE NAICS
M
Information
>NAICS Active
The set bits indicate some or all
transmission modes: 1, 2, 3, 4,
6, 8, 9, 10, as defined in TS
36.213 [23, 7.1]. The first/
>>Transmission Modes O BIT STRING (SIZE(8))
leftmost bit is for transmission
mode 1, the second bit is for
transmission mode 2, and so
on.
>>P_B O INTEGER (0..3) See TS 36.213 [23, Table 5.2-1]
0 ..
>>P_A_list <maxno
ofPA>
ENUMERATED (dB-6, See PA TS 36.213 [23, 5.2].
dB-4dot77, dB-3, dB- Value dB-6 corresponds to -6
>>>P_A M
1dot77, dB, dB-4dot77 corresponds to -
dB0, dB1, dB2, dB3,...) 4.77 dB etc.
>NAICS Inactive NULL
X2 interface-based NAICS assistance information exchanged between Samsung

and non-Samsung eNBs is controlled by OTHER_VENDOR_SUPPORT (CHG-
NAICS-CONF). If this parameter is set to OFF, information exchange is not
supported, and vice-versa. By default, it is set to OFF. It should be set to ON only
when inter-operation of this feature with non-Samsung eNBs is checked and
confirmed.
For each UE, the eNB of Pcell selects and updates NAICS assistance information
in the following two steps:
• NAICS serving cell list selection and update
• Neighbor cell list selection and update for each serving cell in NAICS serving
cell list
NAICS Serving Cell List Selection and Update
The eNB of Pcell performs the following:
• Selects NAICS serving cell list after initial attach, idle-to-active transition,
incoming HO, and RRC Connection Re-establishment.
• Includes all serving cells of the UE in this list except Scells of other eNBs
when inter-eNB CA is used:
Confidential
o NAICS assistance information of these Scells is available with their eNBs.

o These eNBs cannot send this information to the eNB of Pcell as there is no
X2 message to exchange such information.
• Updates NAICS serving cell list after Scell addition, modification, or release.
Figure below depicts the procedure of NAICS serving cell list selection.
UE configuration: {PCell, SCell-1, SCell-2}
PCell and SCell-1 are eNB-1's cells.

NAICS serving cell list
- SCell-2 is eNB-2's cell (inter-eNB CA).

- It is excluded from NAICS serving cell list.
PCell PCID-a1 PCID-a2 ... PCID-a8
SCell-1 PCID-b1 PCID-b2 ... PCID-b8
8 neighbor cells selected for each serving cell
Neighbor Cell List Selection and Update for each Serving Cell in NAICS
Serving Cell List
The eNB of Pcell performs the following:
• Selects and updates one neighbor cell list for each serving cell in NAICS
serving cell list.
• Receives NRT-based CRS-IC lists from LTE-ME6018 (CRS-IC Support)
feature. If LTE-ME6018 is OFF, the eNB of Pcell generates the NRT-based
CRS-IC lists using the same method as used in LTE-ME6018.
• Adds the remaining NAICS parameters for each neighbor cell in the CRS-IC
lists.
o Conditions for neighbor cell list update: NAICS serving cell list update,
NAICS information update through Load Information message, NRT
update.
• Sends NAICS assistance information to the UE in an RRC Connection
Reconfiguration message.

Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-NAICS-CONF and set naicsEnable to ci_On.
• Run CHG-NAICS-CONF and set naicsEnable to ci_Off.
Key Parameters
parameters.
Parameter Descriptions of CHG-NAICS-CONF/RTRV-NAICS-CONF
naicsEnable This parameter is used for NAICS feature On/Off.
parameters.
Parameter Descriptions of CHG-NAICS-CONF/RTRV-NAICS-CONF
otherVendorSupport This parameter indicates NAICS feature working with other vendor eNB. Set
this parameter to ci_On only when NAICS operation is confirmed with the
other vendors' neighbor eNBs.
Counters and KPIs

with this feature.

Confidential
REFERENCE
[1] 3GPP TS 36.300: E-UTRA and E-UTRAN; Overall description; Stage 2
[2] 3GPP TS 36.331: Radio Resource Control (RRC); Protocol specification
[3] 3GPP TS 36.423: X2 Application Protocol (X2AP)

Confidential
LTE-ME5010, Best Cell Aggregation

INTRODUCTION
LTE Network operators provide Carrier Aggregation (CA) service using multiple
carrier frequencies of various bands to improve user throughput and radio resource
usage.
Component Carriers (CCs) used for CA have different propagation characteristics,
which makes coverage mismatch between the CCs.
Since eNB supporting legacy CA [see LTE-SW5500] configures only one
collocated SCell on an SCC to all the CA UE connected with a PCell, UE
throughput is not enhanced enough in areas where the coverages of CCs are
mismatched.
Samsung eNB provides a Best Cell Aggregation (BCA) feature to maximize CA
UE throughput even in case of coverage mismatch between CCs.
BCA is an advanced CA feature to enable the CA UEs connected a PCell to be
scheduled not only on the collocated SCell but also on other SCell on the SCC.
BENEFIT
BCA maximizes downlink UE throughput even in case of coverage mismatch
between CCs by adding and scheduling on the strongest cell among all SCell
candidates detected on the SCC.
BCA can further improve the performance of Carrier Aggregation feature as
follows:
• Operator can enhance the utilization of frequency resource and obtain load
balance effects, and so on for scheduling.
• UE can improve throughput and reduce file download delay
DEPENDENCY
• HW dependency
o Support Channel Cards: The channel card or unified board, which can
support the equivalent CA throughput, is required.
LIMITATION
• The device needs to support this feature.
• Support for band combination within carrier aggregation combination.

Confidential
SYSTEM IMPACT
capabilities.
Related Feature: LTE-SW5500, CA Call Control
In the feature CA Call Control, CA operation mode 1 and 2 is described, where
CA operation is done only in the co-located SCell. Whereas in "Best Cell
Aggregation", CA operation mode 3 and 4 is described, where CA operation is
possible in both co-located and non-collocated SCells.
A PCell supports multiple numbers of SCells and a SCell supports multiple
numbers of PCells. The supported number differs depending on HW configuration.
Coverage
Because it is possible to support CA even at non-collocated SCells, CA coverage
can be enlarged compared to non-BCA area. However, it does not mean the
change of network cell coverage itself.
Interfaces
None
FEATURE DESCRIPTION
To support BCA, eNB supports the following operating modes (Mode 3 and 4) in
addition to legacy CA modes (Mode 1 and 2).
CA Operation Mode Mode 3 Mode 4
Desirable Deployment Scenario #1,#2,#3,#4,#5 #1,#2,#3,#4,#5
Characteristics Refer to the bestNeighCell Initial SCell Addition based
(Candidate Cell) on PCell-SCell Paired, and
information at fully MR- MR at HO in (Co-located
based paired at initial initial Addition+ SCell
connection. Change MR)
Measurement Configured frequency • SCell Conf. SCell Conf.
Configuration State • Event A2 Conf. (for SCell • N/A
(per carrier-frequency) release) • Event A6 Conf. (for SCell
• Event A6 Conf. (for SCell replacement)
replacement)
Non-configured Event A4 Conf. (for SCell N/A
frequency addition)
• Mode 3: PCell does not add SCell unconditionally when the cell is connected
and HO is led in, checks the radio quality of neighbor cells, and adds the best
candidate as a SCell. After that, when the quality of another cell is good, the
change in SCell is allowed.
• Mode 4: PCell adds Scell unconditionally when the collocated Scell
designated to PCell is connected, and changes the best candidate SCell when

Confidential
the quality of another cell is better than current serving SCell.
BCA can be activated and deactivated on per cell basis (CHG-CACELL-INFO and
CA_OPERATION_MODE).
• Mode 3 and Mode 4: BCA activation
• Mode 1 and Mode 2: BCA deactivation
Since it is essential to utilize Event A6 in BCA, the configuration for use of Event
A6 for CA shall be followed according to BCA activation (CHG-EUTRA-A6CNF,
PURPOSE (0), ACTIVE_STATE).
• ACTIVE_STATE (1): USE of Event A6 for CA
• ACTIVE_STATE (0): NO USE of Event A6 for CA
Check Blocks for SCell Addition

Samsung eNB considers the following conditions when SCell is added for CA.
Check Description
C1. PCell CA ON/OFF This flag is configurable per PCell. If it is 0, OFF; if it is 1, ON.
Check
C3. CA Band Capability • If the supported BandCombinations and BandwidthCombinationsets received
Check from UE radio capacity are supported by the eNB, success.
• This check is carried out for every supported BandCombination of UE.
C4. Cell Capacity Check • This step decides the allowed SCell addition based on the number of UEs of
PCell and SCell.
• If a UE requests SCell addition beyond the maximum number of SCell added
calls which allows the setting of SCell addition per PCell, the request is rejected.
C5. SCell Availability This step is to check the service availability of the SCell requested by SCell
Check addition as follows:
• SCell cell release: If the state of the cell requested as SCell is cell released,
impossible to add SCell.
• SCell shutting down state: If the state of the cell requested as SCell is shutting
down, impossible to add SCell.
• SCell barring or reserving: Decides the possibility of adding SCell considering all
cells barred and reservedforOperatorUse of SCell.
C6. Co-Schedulability This step is to check whether co-scheduling of PCell and SCell is allowed or not.
Check By using IDs set in expansion to cell configuration, set the SchedulableUnit as a
parameter and if the cell requested as SCell is in the SchedulableUnit same as
PCell, success; otherwise, failure.
C7. UE FGI 111 Check If FGI bit 111 is 1, success; if it is 0, failure.
C8. UE FGI 112 Check If FGI bit 112 is 1, success; if it is 0, failure.
The C4 checking is moved to the SCell activation stage.
Basic Operation for BCA

Basic operations are based in LTE SW-5500, CA Call Control.

Confidential
At the Initial Context Setup

The eNB performs the following operations to determine the CA availability on
accepting the UE capability according to the current CA operation mode.
In case of Mode 3:
• C1. PCell CA ON/OFF Check
• C3. CA Band Capability Check
If these conditions are met, the eNB configures the event A4 measurement for
SCell addition at the SCCs that meets C3 condition.
In case of Mode 4:
• C1. PCell CA ON/OFF Check
• C3. CA Band Capability Check
• C5. SCell Availability Check
If these conditions are met for the paired SCell, the eNB configures UE to add the
paired SCell that meets C3 condition.
If the following condition checks are met, set the event A6 measurement for
changing SCell for which the SCC of the added SCell is MO:
• C7. UE FGI bit 111
If neither of the conditions is met, the eNB performs the conventional initial
context setup procedure as it is, that is, the UE does not perform the CA-related
operations.
At Reception of Event A4 Measurement for SCell Addition Trigger (Mode 3)
The eNB performs the following on receiving Event A4 MR for SCell addition
trigger from SCell not added UE:
In case of Mode 3:
• C6. Co-Schedulability Check
If all of the above conditions are met, the eNB:
• Configures SCell addition with the neighbor cell-triggering event A4 as SCell.
• Releases event A4 measurement on the SCC of the added SCell.
• Configures the event A2 measurement for releasing SCell for which the SCC
of the added SCell is MO.
• Sets the event A6 measurement for changing SCell for which the SCC of the
added SCell is MO, if the C7. UE FGI bit 111 is met.
At Reception of Event A6 MR for SCell Change Trigger (Mode 3, 4)
The eNB performs the following on receiving event A6 MR for SCell change
trigger from SCell added UE.
In case of Mode 3:

Confidential
• C6. Co-Schedulability Check

If all the above conditions are met, the eNB performs:
• SCell release on the SCC corresponding to MO of the triggered event A6.
• SCell addition as neighbor cell triggering the event A6 MR.
• Configuration of event A6 measurement for SCell change at SCC of the added
SCell is MO.
At Reception of Event A2 MR for SCell Release Trigger (Modes 3)
The eNB indicates the following to UE on receiving the event A2 MR for SCell
release trigger in case of Mode 3:
• SCell release in the SCC corresponding to MO of the triggered event A2.
• Release of event A2 measurement for SCell release at SCC of the released
SCell is MO.
• Configuration of event A4 measurement for SCell addition at SCC of the
released SCell is MO.
• Release if event A6 measurement for SCell change at SCC of the released
SCell is MO is configured.
For other behavior of BCA, refer to the legacy LTE SW-5500, CA Call Control.
SYSTEM OPERATION
How to Activate
Pre-condition
• The CA_AVAILABLE_TYPE must be set ci_DL_only or ci_DL_and_UL
in CHG-CACELL-INFO.
• The COLOCATED_CELL_NUM must be set collocated CELL_NUM in CHG-
CA-COLOC.
• Run CHG-CACELL-INFO and set CA_OPERATION_MODE to ci_Mode3 or
ci_Mode4.
• Run CHG-EUTRA-A6CNF and set PURPOSE to 0.

Confidential
• Run CHG-EUTRA-A6CNF and set ACTIVE_STATE to 1.
• Run CHG-CACELL-INFO and set CA_OPERATION_MODE to ci_Mode1 or
ci_Mode2.
• Run CHG-EUTRA-A6CNF and set PURPOSE to 0.
• Run CHG-EUTRA-A6CNF and set ACTIVE_STATE to 0.
Key Parameters
parameters.
Parameter Descriptions of CHG-CACELL-INFO/RTRV-CACELL-INFO
CA_AVAILABLE_TYPE This parameter indicates whether to support carrier aggregation (CA).
CA_OPERATION_MODE CA Operation mode:
• Mode1: PCell and SCell are collocated and the SCell is added during initial
attachment.
• Mode2: PCell and SCell are collocated and initial attachment will try SCell
addition.
• Mode3: BCA (fully MR-based SCell add/release/change)
• Mode4: Best Cell Aggregation (initially collocated SCell add, MR based SCell
change)
parameters.
A6_OFFSET As the A6_Offset value of Event A6 during ReportConfigEutra configuration,
this parameter uses the unit defined in the 3GPP TS36.331 and it is set to -
30~30. The actual measurement value must be set to A6_OFFSET*0.5 (dB).
When the signal of SCell is larger than A6_OFFSET, the UE transmits the A6
measurement report.
A6_REPORT_ON_LEAVE As the ReportOnLeave value of Event A6 during ReportConfigEutra
configuration, it is set to True/False. If the REPORT_ON_LEAVE is set to
True, A UE generates an Event A6 because the UE satisfies the A6
threshold. If the UE satisfies a leaving condition and the A6 threshold is not
met, it generates Event A6 and stops Event A6. If the REPORT_ON_LEAVE
is False, it does not transmit A6 in the leaving condition status.
HYSTERESIS As a parameter used to configure the hysteresis value of Event A6 during
ReportConfigEutra configuration, it is used to determine the entering
condition [(measurement result - Hysteresis) Threshold] and leaving condition

Confidential
[(measurement result + Hysteresis) Thresh]. The hysteresis uses the unit
defined in the TS36.331 and its range is 0-30. The actual value is converted
into hysteresis*0.5 dB.
TIME_TO_TRIGGER As a parameter used to configure the timeToTrigger of Event A6 during
ReportConfigEutra configuration, its unit is ms. The event A6 occurs only
when a specific threshold is met during the period of TIME_TO_TRIGGER
and the TIME_TO_TRIGGER can be set to a value 0-5120 ms as defined in
the standard
TRIGGER_QUANTITY This parameter is used to set up the TriggerQuantity of Event A6 during
ReportConfigEutra configuration. The TRIGGER_QUANTITY can be set to
RSRP/RSRQ. According to the TRIGGER_QUANTITY, the UE transmits
Event A6 if the RSRP or RSRQ meets a specific A6_OFFSET.
REPORT_QUANTITY This parameter is used to set up the ReportQuantity of Event A6 during
ReportConfigEutra configuration. The REPORT_QUANTITY can be set to
sameAsTriggerQuantity/both. A UE transmits both RSRP/RSRQ if the
REPORT_QUANTITY is set to both for the measurement result when
transmitting Event A6. If it is set to sameAsTriggerQuantity, the UE transmits
only the result corresponding to the TRIGGER_QUANTITY.
MAX_REPORT_CELL This parameter is used to set up the maxReportCells of the Event A6 during
the ReportConfigEutra configuration. This parameter is the maximum number
of neighbor cells that can be included in a measurement report for the Event
A6. When transmitting a measurement report for the Event A6, the UE can
add the measurement result of a EUTRA neighbor cell as many as
MAX_REPORT_CELL if there is a measurement result of EUTRA neighbor
cell.
REPORT_INTERVAL This parameter is used to set up the reportInterval of Event A6 during
ReportConfigEutra configuration. The REPORT_INTERVAL must transmit a
measurement report at the interval of REPORT_INTERVAL as many times as
specified in the REPORT_AMOUNT if it meets the event A6 condition. This
applies only when the REPORT_AMOUNT is larger than 1. The
REPORT_INTERVAL can be set to 120 ms-30 min.
REPORT_AMOUNT This parameter is used to set up the reportAmount of Event A6 during the
ReportConfigEutra configuration. The REPORT_AMOUNT is the number of
measurement report transmissions when the Event A6 conditions are met. If
the REPORT_AMOUNT is larger than 1, the measurement report is
transmitted as many times as REPORT_AMOUNT according to the interval
specified in REPORT_INTERVAL. The REPORT_AMOUNT is set to 1-
infinity. If it is set to infinity, a measurement report is transmitted at the
interval of REPORT_INTERVAL until the A6 leaving condition is met.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User

Confidential

[7] 3GPP TR 36.814: Evolved Universal Terrestrial Radio Access (E-UTRA);

Confidential
LTE-ME5801, FDD DL 2CC Carrier Aggregation

INTRODUCTION
The FDD DL 2CC Carrier Aggregation enables an eNB to aggregate two LTE
Component Carriers (CCs). The purpose of multiple CCs aggregation is to have
wider channel bandwidth, which helps operators to increase bitrates for end-users.
BENEFITS
With this feature, an operator can combine individual CCs from different band and
bandwidths. This ensures that all the spectrum resources are utilized effectively
across the network for improving efficiency and achieving higher peak
throughputs.
DEPENDENCY
• Prerequisite Features: LTE-SW5500, CA Call Control
• Others: The UE needs to support this feature.
LIMITATION
Peak throughput of UE depends on UE category capability and channel card type.
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-SW5500, CA Call Control
For FDD DL 2CC carrier aggregation, the operation mode and the system
configuration are performed by using LTE-SW5500 feature. For the configuration
associated with this feature, see LTE-SW5500.
FDD DL 2CC carrier aggregation increases the system capacity for end-users by
utilizing the available spectrum resources effectively across the network. For key
parameter and detailed information on counters associated with this feature, see
LTE-SW5500.
Coverage
FDD DL 2CC carrier aggregation allows end users to access the network through
multiple component carriers. Thus, the cell coverage can be increased for those
CA users compared with the single-carrier users.
Interfaces
None
Confidential
FEATURE DESCRIPTION
The Samsung eNB supports a combination of two FDD CCs in downlink. Each
aggregated carriers is referred to as CC.
Figure below depicts the three FDD carriers aggregated LTE channels.
FDD
DL CC#1
FDD DL
2 CC CA
FDD
DL CC#2
This feature can be used as the following three types of carrier allocation based on
the spectrum usage:
• Intra-band Contiguous CA
• Intra-band Non-contiguous CA
• Inter-band Non-contiguous CA
For detailed description of CA functionality and its operational procedures, see
LTE-SW5500, CA Call Control feature description document.
SYSTEM OPERATION
Refer to the System Operation section of LTE-SW5500, CA Call Control feature
for configuration, key parameter, and detailed information on counters associated
with this feature.
REFERENCE
Confidential
[8] 3GPP TR 36.912 ‘Feasibility study for Further Advancements for E-UTRA
(LTE-Advanced)’

Confidential
LTE-ME5801-A, FDD DL 2CC Carrier

Aggregation with 4x4 MIMO
INTRODUCTION
This feature enables an eNB to aggregate with [20 or 15 or 10 or 5 or 3] + [20 or
15 or 10 or 5 or 3] MHz LTE Component Carriers (CCs) with 4x4 MIMO
capability of each component carrier. The purpose of multiple CCs aggregation
and multiple layers MIMO is to have wider channel bandwidth and more spectral
efficiency, which helps operators to increase bitrates for end-users.
BENEFITS
A UE can achieve higher throughput by four streams transmission for FDD
component carriers while UE is served with FDD carrier aggregation. This ensures
that all the spectrum resources are utilized effectively across the network for
improving efficiency and achieving higher peak throughputs.
DEPENDENCY
• HW dependency: The channel card or unified board, which can support the
equivalent CA throughput, is required.
• Others: The device needs to support this feature.
LIMITATION
• Transmission mode for DL 4x4 SU MIMO supported in this feature need to be
discussed with customer.
• TM3 and TM4 are possible options for this feature.
SYSTEM IMPACT
capabilities.
For FDD DL 2CC carrier aggregation, the operation mode and system

Confidential
LTE-SW5500.
Coverage
Interfaces
None
FEATURE DESCRIPTION
The Samsung eNB supports a combination of FDD (20 or 15 or 10 or 5 or 3) + (20
or 15 or 10 or 5 or 3) CC with 4-layer MIMO in downlink.
FDD
(20, 15, 10, 5, or 3)
FDD-FDD
First Carrier + Second Carrier CA
FDD
(20, 15, 10, 5, or 3)

LTE-SW5500, CA Call Control feature.
SYSTEM OPERATION
with this feature.
REFERENCE

Confidential

(LTE-Advanced)’

Confidential

INTRODUCTION
The FDD DL Carrier Aggregation enables an eNB to aggregate three LTE
Component Carriers (CCs). The purpose of multiple CCs aggregation is to have
wider channel bandwidth, which helps operators to increase bitrates for end-users.
BENEFITS
With this feature, an operator can combine individual CCs from different band and
bandwidths. This ensures that all the spectrum resources are utilized effectively
across the network for improving efficiency and achieving higher peak
throughputs.
DEPENDENCY
• HW dependency: CA can be restricted depending on the HW configuration.
• Others: The UE needs to support this feature.
LIMITATION
The UE peak throughput depends on UE category capability and channel card
type.
SYSTEM IMPACT
capabilities.
For FDD DL 3CC carrier aggregation, the operation mode and system
LTE-SW5500.
Coverage

Confidential
Interfaces
None
FEATURE DESCRIPTION
The Samsung eNB supports a combination of three FDD CCs in downlink. Each
Figure below depicts the three FDD carriers aggregated LTE channels.
FDD DL CC#1
FDD DL CC#2 FDD DL 3CC CA
FDD DL CC#3
the spectrum usage.
SYSTEM OPERATION
with this feature.
REFERENCE

Confidential

(LTE-Advanced)’

Confidential

INTRODUCTION
The FDD DL 3CC Carrier Aggregation with 4x4 MIMO feature enables an eNB to
aggregate with three FDD Component Carriers (CCs) with DL 4x4 MIMO in
downlink transmission. The purpose of multiple CCs aggregation with DL 4x4
MIMO is to have wider channel bandwidth and higher order MIMO, which helps
operators to increase bitrates for end-users.
BENEFITS
An operator can combine individual three FDD CCs with DL 4x4 MIMO from
different downlink band and bandwidths using FDD DL 3CC Carrier Aggregation
with 4x4 MIMO feature. This ensures that all the DL spectrum resources are
utilized effectively across the network for improving efficiency and achieving
higher peak throughputs.
DEPENDENCY
• HW dependency: LCA, LCB, and LCC
LIMITATION
The UE needs to support this feature.
SYSTEM IMPACT
capabilities.
For FDD DL 3CC carrier aggregation with 4x4 MIMO, the operation mode and
system configuration are performed by using LTE-SW5500 feature. For the
configuration associated with this feature, see LTE-SW5500.
FDD DL 3CC carrier aggregation with 4x4 MIMO increases the system capacity
for end-users by utilizing the available spectrum resources effectively across the
network. For key parameter and detailed information on counters associated with
this feature, see LTE-SW5500.

Confidential
Coverage
FDD DL 3CC carrier aggregation with 4x4 MIMO allows end users to access the
network through multiple component carriers. Thus, the cell coverage can be
increased for those CA users compared with the single-carrier users.
Interfaces
None
FEATURE DESCRIPTION
The Samsung eNB supports a combination of three FDD CCs with 4x4 MIMO in
downlink. Each aggregated carriers is referred to as CC.
Figure below depicts the three FDD carriers aggregated LTE channels with 4x4
MIMO.
FDD DL CC#1
w/8X4 MIMO

w/8X4 MIMO with 8X4 MIMO
FDD DL CC#3
w/8X4 MIMO
the spectrum usage.
SYSTEM OPERATION
with this feature.
REFERENCE
Confidential

(LTE-Advanced)’

Confidential

INTRODUCTION
The FDD DL 4CC Carrier Aggregation enables an eNB to aggregate with Max. 4
Component Carriers (CCs) in LTE downlink. The purpose of multiple CCs
aggregation in DL is to have wider channel bandwidth, which helps operators to
increase DL bitrates for end-users.
BENEFITS
With this feature, an operator can combine individual CCs. This ensures that all
the spectrum resources are utilized effectively
DEPENDENCY
• HW dependency: The channel card, which supports the equivalent CA
throughput (LCC series).
• Related Radio Technology: E-UTRAN(LTE) Rel.10 Carrier Aggregation
LIMITATION
None
SYSTEM IMPACT
capabilities.
For carrier aggregation, the operation mode and system configuration are
performed by using the LTE-SW5500 feature. For the configuration associated
with the LTE-ME5803 feature, see LTE-SW5500 feature description section.
Carrier aggregation increases the system capacity for end-users by utilizing the
available spectrum resources effectively across the network. For key parameter
and detailed information on counters associated with the LTE-ME5803 feature, see
LTE-SW5500, CA Call Control.
Coverage
Carrier aggregation allows end users to access the network through multiple
component carriers. Thus, the cell coverage can be increased for those CA users
compared with the single-carrier users.

Confidential
Interfaces
None
FEATURE DESCRIPTION
The Samsung eNB supports a combination of four FDD CCs in downlink. Each
Figure below depicts the four FDD carriers aggregated LTE channels.
FDD DL CC#1
FDD DL CC#2
FDD DL 4CC
CA
FDD DL CC#3
FDD DL CC#4
the spectrum usage.
SYSTEM OPERATION
with this feature.
REFERENCE

Confidential

(LTE-Advanced)’

Confidential

INTRODUCTION
The FDD DL 4CC Carrier Aggregation with 4x4 MIMO feature enables an eNB to
aggregate with three FDD Component Carriers (CCs) with DL 4x4 MIMO in
downlink transmission. The purpose of multiple CCs aggregation with DL 4x4
MIMO is to have wider channel bandwidth and higher order MIMO, which helps
operators to increase bitrates for end-users.
BENEFITS
An operator can combine individual four FDD CCs with DL 4x4 MIMO from
different downlink band and bandwidths using FDD DL 4CC Carrier Aggregation
with 4x4 MIMO feature. This ensures that all the DL spectrum resources are
utilized effectively across the network for improving efficiency and achieving
higher peak throughputs.
DEPENDENCY
throughput (LCC series).
• Related Radio Technology: E-UTRAN(LTE) Rel.10 Carrier Aggregation
• Prerequisite Features: LTE-SW5500, CA Call Control and LTE-ME2022, DL
SU 4x4 MIMO (TM3 and TM4)
LIMITATION
None
SYSTEM IMPACT
capabilities.

For carrier aggregation, the operation mode and system configuration are
with the LTE-ME5803-A feature, see LTE-SW5500 feature description section.
Confidential
Coverage
Interfaces
None
FEATURE DESCRIPTION
The Samsung eNB supports a combination of four FDD CCs with 4x4 MIMO in
downlink. Each aggregated carriers is referred to as CC.
Figure below depicts the four FDD carriers aggregated LTE channels with DL 4x4
MIMO.
FDD DL CC#1
w/ DL 4x4 MIMO
FDD DL CC#2
w/ DL 4x4 MIMO
FDD DL 4CC CA
w/ DL 4x4 MIMO
FDD DL CC#3
w/ DL 4x4 MIMO
FDD DL CC#4
w/ DL 4x4 MIMO
the spectrum usage.
SYSTEM OPERATION
with this feature.

Confidential
REFERENCE
(LTE-Advanced)’

Confidential

INTRODUCTION
The FDD DL 5CC Carrier Aggregation feature enables an eNB to aggregate with a
maximum of five Component Carriers (CCs) in LTE downlink. The purpose of
multiple CCs aggregation in DL is to have wider channel bandwidth, which helps
operators to increase DL bitrates for end-users.
BENEFIT
With this feature, an operator can combine individual CCs. This ensures that all
the spectrum resources are utilized effectively
DEPENDENCY
throughput (LCC series), is required.
• Related Radio Technology: E-UTRAN (LTE) Rel.10 Carrier Aggregation
LIMITATION
None
SYSTEM IMPACT
capabilities.
For carrier aggregation, the operation mode and the system configuration are
with the LTE-ME5803 feature, see LTE-SW5500 feature description section.
Coverage

Confidential
Interfaces
None
FEATURE DESCRIPTION
Samsung eNB supports a combination of four FDD CCs in downlink. Each
Figure below depicts the aggregated LTE channels of four FDD carriers.
FDD DL CC#1
FDD DL CC#2
FDD DL CC#4
FDD DL CC#5
the spectrum usage:
For detailed description of CA functionality and its operational procedures, refer to
SYSTEM OPERATION
with this feature.
REFERENCE

Confidential

(LTE-Advanced)’

Confidential
LTE-ME5901, FDD UL 2CC Carrier Aggregation

INTRODUCTION
The FDD UL 2CC Carrier Aggregation enables an eNB to aggregate with two
LTE Component Carriers (CCs) in uplink transmission. The purpose of multiple
CCs aggregation in uplink is to have wider UL channel bandwidth, which helps
operators to increase uplink bitrates for end-users.
BENEFITS
With this feature, an operator can combine individual CCs from different uplink
band and bandwidths. This ensures that all the UL spectrum resources are utilized
effectively across the network for improving efficiency and achieving higher
uplink peak throughputs.
DEPENDENCY
• HW dependency: The channel card or unified board, which can support the
equivalent UL CA throughput, is required.
• Related Radio Technology: E-UTRAN(LTE) Rel.10 Carrier Aggregation and
Rel.11 Carrier Aggregation Enhancement
• Prerequisite Features: LTE-SW5500 CA Call Control and LTE-SW5503 UL
CA Call Control
LIMITATION
None
SYSTEM IMPACT
capabilities.
For UL carrier aggregation, the operation mode and system configuration are
performed by using UL CA Call Control (LTE-SW5503) feature. For the
configuration associated with this feature, see LTE-SW5503.
UL carrier aggregation increases the system UL capacity for end-users by utilizing
the available spectrum resources effectively across the network. For key parameter
and detailed information on counters associated with this feature, see LTE-
SW5503.
Coverage
UL carrier aggregation allows end users to access the network through multiple

Confidential
component carriers. Thus, the cell coverage can be increased for those UL CA
users compared with the single-carrier users.
Interfaces
None
FEATURE DESCRIPTION
The Samsung eNB supports a combination of 2CCs in uplink. Each aggregated
carriers is referred to as CC.
Figure shows the two carriers aggregated LTE uplink channels.
FDD CC UL
FDD 2CC UL
FDD CC UL
You can have the following three types of carrier allocation based on the spectrum
usage.
SYSTEM OPERATION
Refer to the System Operation section of LTE-SW5503, UL CA Call Control
feature for configuration, key parameter, and detailed information on counters
associated with this feature.
REFERENCE

Confidential
LTE-ME6010, Downlink CoMP

INTRODUCTION
In 3GPP Rel.11 standard, coordinated multi-point (CoMP) transmission and
reception is considered to improve the cell throughput in cell edge area. For
downlink CoMP, CoMP schemes, joint transmission (JT) and dynamic point
selection (DPS), are included for joint processing of multiple transmission points.
In this feature, transmission points use different physical cell IDs and they are
configured with the same frequency and bandwidth.
BENEFIT
Downlink CoMP can achieve the performance enhancement for downlink data
transmission in cell edge area.
DEPENDENCY
• HW Dependency:
o Support Channel Cards: LCA, LCB, and LCC
• Others: The UE supporting TM9 is required
LIMITATION
• Downlink CoMP JT/DPS can be supported between two cells on the same
frequency and bandwidth within a DU, and the two cells have the same
number of CRS ports.
• To support Downlink CoMP JT/DPS, the time synchronization between cells
should be less than +-1us.
• This feature performs Downlink CoMP JT/DPS with maximum 2 layers in cell
edge area.
• Downlink CoMP JT/DPS can be supported for PCells when both this feature
and CA are enabled.
• In SLR7.0 VZW PATCH2, this feature is supported for FDD system only.
• Downlink CoMP JT/DPS can be supported between two cells which have the
same NB-IoT cell configurations of In-band mode.
• When eMTC is enabled, eNB does not perform Downlink CoMP JT/DPS.
SYSTEM IMPACT
capabilities.

Confidential

None
This feature increases the cell edge throughput for user in cell edge area. For the
detailed information on the counters and KPIs, refer to the System Operation
section of this feature.
Coverage
This feature performs interference mitigation in cell edge area among neighboring
cells. Thus, the cell coverage can be improved with this feature.
Interfaces
None
FEATURE DESCRIPTION
3GPP Rel.11 specifications define coordinated multi-point (CoMP) transmission
and reception to enhance the cell throughput in cell edge area. For downlink
CoMP, this feature supports joint transmission (JT) and dynamic point selection
(DPS) of CoMP schemes, which are included for joint processing of multiple
transmission points. The transmission points on the same frequency and bandwidth
are configured with different physical cell IDs. For each cell, the DL CoMP mode
between JT and DPS can be selected by using parameter COMP_MODE (CHG-
DLCOMP-FUNC).
Downlink CoMP JT performs simultaneous data transmission from multiple
transmission points to a single UE or multiple UEs in a time-frequency resource.
Thus, data to a UE is simultaneously transmitted from multiple transmission points
to improve the received signal quality and/or data throughput at cell edge area.
The following figure shows an example of DL CoMP JT scenarios.
Cell1 (PCID A) Cell2 (PCID B)
Data Data
UE
DU
Joint Transmission (JT)
In downlink CoMP DPS, data transmission is performed from one transmission

point in a time-frequency resource. Hence, the transmitting point may change from
one subframe to another without handover. The following figure depicts an
example of DL CoMP DPS scenarios.

Confidential
Cell1 (PCID A) Cell2 (PCID B)
Data @ t Data @ t + 1
UE
DU
Dynamic Point Selection (DPS)
For TM9 based Downlink CoMP, both eNB and UE need to support the following
functions:
• Channel State Information - Reference Signal (CSI-RS)
• Transmission mode 9 (TM9)
• Demodulation - Reference Signal (DM-RS): UE Specific Reference Signal in
3GPP specification.
To configure the configuration of CSI-RS, the parameter CSI_RS_USAGE (CHG-
CSIRS-IDLE) should be set to CI_use.
To ensure that TM9 is set to TM9-capable UEs, parameter COMP_TM9_ENABLE
(CHG-DL-SCHED) needs to be set to TRUE.
This feature can be enabled for each cell by using parameter COMP_ENABLE
(CHG-DLCOMP-FUNC), which can be set to one of the following options:
• ci_Disable: Function Off
• ci_RequestEnable: Request to other cell is allowed, but accept for other cell's
request is not allowed
• ci_AcceptEnable: Accept for other cell's request is allowed, but request to
other cell is not allowed
• ci_Both_Enable: Both request and accept are allowed
In this feature, the decision whether UEs are in the cell edge area or not is
determined by using the measurement report sent from the UEs. When the
difference from serving cell power to neighbor cell power is less than threshold
EDGE_TH (CHG-DLCOMP-FUNC) (dB), the UE is regarded as edge UE. When
the difference from serving cell power to neighbor cell power is larger than
threshold NON_EDGE_TH (CHG-DLCOMP-FUNC) (dB), the UE is regarded as
non-edge UE. The eNB changes the transmission mode of the UE determined to be
at the cell edge to TM9, and supports CoMP transmission to the UE together with
the adjacent cell. In addition, this function operates considering the loading of
neighbor cell. The operation of this feature performed only when neighbor cell
loading is between parameters LOW_LOADING_TH and HIGH_LOADING_TH
(CHG-DLCOMP-FUNC).
When a UE receives data from multiple transmission points of UE’s serving cell
Confidential
and one of neighbor cells (target cell) by using DL CoMP JT/DPS, the
transmissions consume the DL PRBs of both the serving cell and the neighbor cell.
For this, the existing counter of the neighbor cell’s DL PRB usage excludes the DL
PRB used by the CoMP request from the serving cell. To collect the excluded DL
PRB usage, a new counter family PRB_TOTAL_DL_COMP is added in this
feature.
SYSTEM OPERATION
How to Activate
Preconditions
• TM9 (Transmission mode 9) should be set to TM9-capable UEs to operate the
feature. For this, the parameter COMP_TM9_ENABLE needs to be 1, which is
set by the command CHG-DL-SCHED/RTRV-DL-SCHED.
• CSI-RS should be transmitted to operate the feature. For this, the parameter
CSI_RS_USAGE needs to be set as CI_use, which is set by the command
CHG-CSIRS-IDLE/RTRV-CSIRS-IDLE.
• Run CHG-DLCOMP-FUNC and set COMP_ENABLE to
ci_RequestEnable/ci_AcceptEnable/ci_BothEnable.
• Run CHG-DLCOMP-FUNC and set COMP_ENABLE to ci_Disable.
Key Parameters
parameters.
Parameter Descriptions of CHG-DLCOMP-FUNC/RTRV-DLCOMP-FUNC
COMP_ENABLE This parameter determines the usage of inter-cell DL CoMP operation.
• ci_Disable: Function Off
• ci_RequestEnable: Request to other cell is allowed, but accept for other cell's

Confidential
request is not allowed
• ci_AcceptEnable: Accept for other cell's request is allowed, but request to
other cell is not allowed
• ci_Both_Enable: Both request and accept are allowed
parameters.
Parameter descriptions of CHG-DLCOMP-FUNC/RTRV-DLCOMP-FUNC
COMP_MODE Config aperiodic report mode.
• Release: aperiodic report mode is disable.
• Setup: aperiodic report mode is enable. When aperiodic CQI mode is setup,
sub-band CQIs for all sub-bands can be reported simultaneously. Thus, with
aperiodic CQI, frequency selective scheduling can be enhanced, while uplink
overhead is increased to report it.
EDGE_TH This parameter configures the threshold for the state change from non-edge UE
to edge UE.
If the difference from serving cell power to neighbor cell power is less than this
parameter (dB), the UE is regarded as edge UE.
NON_EDGE_TH This parameter configures the threshold for the state change from edge UE to
non-edge UE.
If the difference from serving cell power to neighbor cell power is larger than this
parameter (dB), the UE is regarded as non-edge UE.
LOW_LOADING_TH This parameter configures the threshold where a UE is not allowed to operate as
CoMP UE when target cell loading is below this parameter.
HIGH_LOADING_TH This parameter configures the threshold where a UE is not allowed to operate as
CoMP UE when target cell loading is above this parameter.
Counters and KPIs

PRB_TOTAL_DL_COMP TotCoMPServingPrbDLAvg The average number of DL PRB usage allocated
for serving cell while DL CoMP ON.
TotCoMPServingPrbDLUsed The cumulated number of DL PRBs allocated for
serving cell while DL CoMP ON.
TotPrbDLAvailable The cumulated number of PRBs available for
DL.
REFERENCE

Confidential

[8] 3GPP TR 36.819 ‘Coordinated multi-point operation for LTE physical layer
aspects’
[9] 3GPP TR 36.913 ‘Requirements for Evolved UTRA (E-UTRA) and Evolved
UTRAN (E-UTRAN)’

Confidential
LTE-ME6018, CRS-IC Support

INTRODUCTION
Cell-specific reference signals (CRS) are transmitted by eNB in every subframe
and in every resource block. Power boosting is also allowed for CRS transmission.
CRS transmission causes interference to UEs in neighboring cells. In 3GPP Rel-
11, a UE can cancel CRS interference from neighboring cells by using some
assistance information sent by its serving cell. Interference cancellation (IC)
improves downlink (DL) performance by increasing DL throughput.
BENEFIT
DL performance is improved because UE can cancel CRS interference from
neighboring cells.
DEPENDENCY
Interface & Protocols: The UE should be able to receive Rel-11 CRS assistance
information (TS 36.331).
LIMITATION
• Since serving cell's CRS antenna port count is used instead of the neighboring
cells', UEs' CRS-IC performance may be degraded at CRS boundary where the
neighboring cells use a different number of CRS antenna ports than the serving
cell.
• Since serving cell's MBSFN subframe configuration is used instead of the
neighboring cells', UEs' CRS-IC performance may be degraded at MBSFN
boundary where the neighboring cells use a different MBSFN subframe
configuration than the serving cell.
SYSTEM IMPACT
capabilities.
This feature is affected by LTE-ME4008 (NAICS). Since CRS-IC assistance
information is a sub-set of NAICS assistance information, CRS-IC assistance
information is not sent when NAICS is used.
This feature allows UEs to cancel CRS interference from neighbor cells by
providing information required for interference cancellation (CRS-IC assistance
information) through RRC signaling to UEs. CRS-IC is more effective for cell-
edge UEs. Due to CRS-IC, DL air throughput, DL residua BLER, and DL MCS
allocation will improve. This improvement can be observed using the available
Confidential
counters, which are described in LTE-OM9101 (L1 and L2 Counters) feature.

Coverage
None
Interfaces
This feature uses neighbor relation table (NRT) to gather CRS-IC assistance
information of neighboring cells. NRT is prepared by adding neighbor relations
through X2 interface. NRT should be available before this feature can be used. The
gathered information is provided to UEs through dedicated
RrcConnectionReconfiguration messages in NeighCellsCRS-Info-r11 IE.
FEATURE DESCRIPTION
Cell-specific reference signals (CRS) are transmitted by eNB in every subframe
and in every resource block. Power boosting is also allowed for CRS transmission.
CRS transmission causes interference to UEs in neighboring cells. This
interference is particularly severe for cell-edge UEs. However, UEs with
interference cancellation-capable receivers can cancel neighbor cell CRS
interference if they know some interference parameters. UEs indicate interference
cancellation capability by setting crs-InterfHandl-r11 IE = 'supported' in UE
Capability Information message. For the purpose of interference cancellation, UEs
blindly detect some dynamically varying parameters while the remaining semi-
statically varying parameters are provided to them by eNB as CRS-IC assistance
information. Using this feature, eNB can provide CRS-IC assistance information
of each serving cell (PCell, PSCell, or SCell) to a UE. This feature can be enabled
or disabled by turning the parameter CRS_IC_SUPPORT_ENABLE (CHG-
CRSIC-CONF) ON or OFF, respectively.
The following figure depicts the CRS interference scenario.
CRS
Neighbor Pico
Data CRS
Serving CRS Neighbor

Macro Macro
Neighbor Pico
The eNB provides CRS-IC assistance information for each serving cell through
RRC Connection Reconfiguration message. This information is included in
NeighCellsCRS-Info-r11 IE for PCell and NeighCellsCRS-Info-r13 IE for PSCell
and SCells. One IE can be provided for each serving cell.

Confidential
The table below outlines the CRS-IC assistance information in NeighCellsCRS-

Info-r11 (or -r13) IE.
Fields in NeighCellsCRS- Description Implementation
Info-r11 (or -r13) IE
physCellId-r12 Physical cell ID (PCID) of neighbor PCID of neighbor cell
cell
crs-PortsCount-r12 Number of CRS antenna ports used Number of CRS antenna ports used
by neighbor cell by serving cell
mbsfn-SubframeConfig-r12 MBSFN subframe configuration of MBSFN subframe configuration of
neighbor cell serving cell
A serving cell and all its neighbor cells use the same CRS port configuration and
the same MBSFN configurations. So, for these fields, serving cell configuration is
used instead of neighbor cell configuration. This may lead to some performance
degradation at CRS boundary and MBSFN boundary.
For each UE, PCell's eNB selects and updates CRS-IC assistance information in
two steps:
• CRS-IC serving cell list selection and update
• Neighbor cell list selection and update for each serving cell in CRS-IC serving
cell list
CRS-IC Serving Cell List Selection and Update

• PCell's eNB selects CRS-IC serving cell list after initial attach, idle-to-active
transition, incoming HO, and RRC Connection Re-establishment.
• PCell's eNB includes all serving cells of the UE in this list except:
o SCells of other eNBs when inter-eNB CA is used
♦ CRS-IC assistance information of these SCells is available with their
eNBs.
♦ These eNBs cannot send this information to PCell's eNB, as there is no
X2 message to exchange such information.
o (Conditional) SCG cells when dual connectivity is used
♦ CRS-IC assistance information of SCG cells is provided by SeNB to
PCell's eNB (MeNB) over X2 interface in SCG-Config IE.
♦ MeNB excludes CRS-IC assistance information of SCG cells if this
information is not received from SeNB.
• PCell's eNB updates CRS-IC serving cell list after PSCell / SCell addition,
modification, or release.
Neighbor Cell List Selection and Update for Each Serving Cell in CRS-IC Serving Cell List
• PCell's eNB selects and updates one neighbor cell list for each serving cell in
CRS-IC serving cell list.

Confidential
• Neighbor cell list selection:

o ◦PCell and intra-eNB SCells: PCell's eNB includes the first eight intra-
frequency cells (according to neighbor relation rank) from the neighbor
relation table (NRT) in neighbor cell lists. If NRT has less than eight intra-
frequency cells, all intra-frequency cells in NRT are included in neighbor
cell lists.
o SCG cells: PCell's eNB (MeNB) receives neighbor cell lists from SeNB in
SCG-Config IE.
• Conditions for neighbor cell list update:
o PCell and intra-eNB SCells: CRS-IC serving cell list update, NRT update
o SCG cells: CRS-IC serving cell list update, CRS-IC assistance information
update through SCG-Config IE
• PCell's eNB sends CRS-IC assistance information to the UE in an RRC
Connection Reconfiguration message.
Neighbor Cell List Selection and Update in SeNB

• For each SCG cell, SeNB selects a neighbor cell list from the NRT in the same
way as described in neighbor cell list selection for PCell and intra-eNB SCells.
• SeNB sends all the lists to PCell's eNB (MeNB) in SCG-Config IE.
• SeNB sends updated CRS-IC assistance information of SCG cells to MeNB
when an SCG SCell is added or NRT is updated.
Interoperation with Other Features

This feature supports inter-operation with LTE-ME6017 Smart CRS-IC and
LTE-ME4008 NAICS:
• LTE-ME6017: When LTE-ME6017 is ON, CRS-IC assistance information for
PCell is provided using LTE-ME6017. Otherwise, CRS-IC assistance
information for PCell is provided using this feature.
• LTE-ME4008: CRS-IC assistance information is a sub-set of NAICS
assistance information. So, when LTE-ME4008 is ON, CRS-IC assistance
information for serving cells is not provided separately using this feature.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-CRSIC-CONF, and set CRS_IC_SUPPORT_ENABLE to ON to
activate this feature.
• Run CHG-RRSIC-CONF, and set CRS_IC_SUPPORT_ENABLE to OFF to
activate this feature.
Key Parameters
parameters.
Parameter Descriptions of CHG-MME-CONF/RTRV-MME-CONF
CELL_NUM Cell Index
CRS_IC_SUPPORT_ENABLE This parameter is a switch of CRS-IC Support function.
• OFF: Disable CRS-IC Support
• ON: Enable CRS-IC Support
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.300: E-UTRA and E-UTRAN; Overall description; Stage 2
[2] 3GPP TS 36.331: Radio Resource Control (RRC); Protocol specification
[3] 3GPP TS 36.306: User Equipment (UE) radio access capabilities
[4] 3GPP TS 36.213: Physical layer procedures

Confidential
Chapter 2 Call Control
LTE-SW0100, Support UE Category 0

INTRODUCTION
The Samsung eNB supports UE category 0 (Cat 0), which is a low complexity UE,
and has reduced Tx and Rx capabilities compared to other UE categories. The Cat
0 UEs can access a cell only if the SIB1 message indicates that access of these
UEs is supported. Otherwise, the Cat 0 UEs consider the cell as barred.
BENEFIT
• Operators can offer IoT services.
• This feature reduces terminal modem complexity compared to category 1 UEs.
• This feature controls eNB overload traffic by barring the delay tolerant devices
such as Cat 0 UE.
DEPENDENCY
Others: The Cat 0 MTC device is required (with Rel-12 compliant).
LIMITATION
The paging period of Cat 0 UE should be set larger than 40 ms for type B half-
duplex FDD mode.
SYSTEM IMPACT
capabilities.
None
None
Coverage
None
Interfaces
Interface between the eNB and MME needs to be updated based on Rel-12 to
support this feature.

Confidential
FEATURE DESCRIPTION
LTE Cat 0 is low cost devices such as Machine-Type Communications (MTC). Its
characteristic is 1RX Antenna operation, type B half-duplex FDD mode and
reduced Transport Block Size(TBS). These Devices can receive or send a
maximum 1000 bits of unicast traffic per subframe which results in peak data rates
to 1Mbps in DL and UL. Due to this, within one TTI, a UE indicating Cat 0 can
receive up to:
• 1000 bits for a transport block associated with C-RNTI/P-RNTI/SI-RNTI/RA-
RNTI
• 2216 bits for another transport block associated with P-RNTI/SI-RNTI/RA-
RNTI
The Cat 0 UE supports TDD, FD-FDD and type B HD-FDD.
The Type B HD-FDD UE cannot receive both first and last DL subframes
(following / preceding UL subframes). Therefore, the Cat 0 UEs should be
removed from the candidate list for scheduling the TTI.
To allow access to Cat 0 devices, the eNB indicates its support of Cat 0 UE
through the SIB1 message, as depicted in figure below. The category0Allowed IE
in SIB1 is configurable by RTRV-CELL-INFO.
The Cat 0 UE sends RRCConnectionRequest or RRCConnectionEstablishment

message with a new LCID value as listed table below from TS 36.321
specification. The eNB recognizes the UE as Cat 0 when it receives LCID value as
01011. The LCID field size is 5 bits.
Index LCID Values
00000 CCCH (Other Category UEs)
00001-01010 Identity of the logical channel
01011 CCCH (Cat 0 UE )
The Cat 0 UEs can support a maximum TBS of 1000 bits for unicast traffic and
2216 bits for broadcast traffic. Therefore, the eNB supports resource allocation
with the consideration of 1000 bits for unicast traffic.
UE also indicates Cat 0 capability to eNB in UE CapabilityInformation. The UE-
RadioPagingInfo IE contains information used for paging of Cat 0 UEs. The UE
includes this field when the Cat 0 has been indicated by ue-Category-v1250 in UE-

Confidential
EUTRA-Capability as depicted in figure below.
The eNB forwards the UERadioPaging Information to MME. The MME replaces
the UE capability information, if stored previously, with the latest information. It
returns the updated information to the eNB in the paging message. The eNB uses
this paging IE to apply specific paging schemes.
Paging period for Cat 0 UE should be set larger than 40 ms for HD-FDD mode. In
TS 36.304, the "nB" can be {4T, 2T, T, T/2, T/4, T/8, T/16, T/32}. To configure
the nB as {T/4, T/8, T/16, T/32}, set the paging period larger than 40 ms. For TDD
and FD-FDD mode, the paging period is same as other normal UEs.

Confidential
Modified Cat 0 Signaling Details
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CELL-INFO and set CATEGORY0_ALLOWED to True.
• Run CHG-CELL-INFO and set CATEGORY0_ALLOWED to False.

Confidential
Key Parameters
Activation/Deactivation Parameter
parameters.
Parameter Descriptions of CHG-CELL-INFO/RTRV-CELL-INFO
CATEGORY0_ALLOWED This parameter indicates whether the cell allows access for Category 0 UEs.
• False: An operating cell does not allow category 0 UE access.
• True: An operating cell allows category 0 UE access.
Counters and KPIs

with this feature.
REFERENCE
description; Stage 2, Release 12
Resource Control (RRC) protocol specification, Release 12
[3] 3GPP TS36.306 Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) radio access capabilities, Release 12
[4] 3GPP TR36.888 Study on provision of low-cost Machine Type
Communications (MTC) User Equipment (UEs) based on LTE, Release 12
[5] 3GPP TS23.401 General Packet Radio Service enhancements for Evolved
Universal Terrestrial Radio Access Network, Release 12
Medium Access Control (MAC) protocol specification, Release 12

Confidential
LTE-SW0101, Support for UE Category 1, 2, 3,

and 4
INTRODUCTION
An eNB supports UE Category 1, 2, 3, and 4, which are defined in 3GPP
TS36.306. Different UE categories define different UE capability in terms of
throughput. The eNB has no limitation on supporting UE category 1, 2, 3, and 4,
which have up to two layers downlink and do not support uplink 64QAM. UE
Category 1 supports SISO and UE Category 2, 3, and 4 supports 2x2 MIMO.
BENEFIT
• The eNB supports different device types that are capable of DL 2x2 MIMO,
2RX diversity, or SISO.
• The UE can improve downlink throughput if it supports DL 2x2 MIMO.
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Table below outlines the modulation and the MIMO formats supported for each
UE categories.
Category 1 2 3 4
Modulation Downlink QPSK, 16QAM, 64QAM
Uplink QPSK, 16QAM
MIMO 2Rx diversity Assumed in performance requirements across all LTE UE
categories
2x2 MIMO Not supported Mandatory
4x4 MIMO Not supported
Table below outlines the DL throughput and the number of downlink layers per
UE Category, which are defined in 3GPP TS36.306 release 9. The maximum total
bits per Transmission Time Interval (TTI) in the downlink define the maximum

Confidential
downlink throughput. A single TTI corresponds to the 1ms subframe duration. The
maximum downlink throughput specified for the release 8 and 9 of the 3GPP
specifications is 300 Mbps. This is supported when transferring 2 transport blocks
per subframe on a single RF carrier.
UE Category Maximum number of Maximum number of Total number of Maximum number of

DL-SCH transport bits of a DL-SCH soft channel bits supported layers for
block bits received transport block spatial multiplexing in
within a TTI received within a TTI DL
Category 1 10296 10296 250368 1

Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Table below outlines the UL throughput and 64QAM support per UE category,
which are defined in 3GPP TS36.306 release 9. Similarly, the maximum total bits
per TTI in the uplink define the maximum uplink throughput. The maximum
uplink throughput specified for the release 8 and 9 of the 3GPP specifications is
75Mbps. This is supported when transferring 1 transport block per subframe on a
single RF carrier.
UE Category Maximum number of bits of an UL-SCH Support for

transport block transmitted within a TTI 64 QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No
Figure below depicts the message flow of UE capability information for signaling
UE category.

Confidential
SYSTEM OPERATION
How to Activate
This feature runs automatically, and it cannot be disabled.
Key Parameters
There are no specific parameters associated with this feature.
Counters and KPIs

UE Category UE_Category_1 Number of UEs in the UE Category 1
UE_Category_2 Number of UEs in the UE Category 2
REFERENCE
Equipment (UE) radio access capabilities
Radio Resource Control (RRC) Protocol specification

Confidential
LTE-SW0105, Support for UE Category 5

INTRODUCTION
The UE category is defined in the 3GPP TS33.306. This feature defines the
accessibility of category 5 UE at eNB side. When category 5 UE tries to access
eNB, the upper layer SW block notifies this information to scheduler and transmit
RRC message, which includes transmission mode according to the scheduler
decision.
BENEFIT
The eNB supports the operation for supporting UE-Category 5 device.
DEPENDENCY
LIMITATION
• Commercial release is subject to change considering commercial UE release to
support category 5 and it needs additional IOT with commercial UE.
• This feature defines the accessibility of category 5 UE and related counters.
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature defines the configuration and operation to support category 5 UE in
the perspective of upper layer SW.
Table below outlines downlink physical layer parameter values set by the UE-
Category field.
UE Category Maximum number of Maximum number of Total number of Maximum number of
DL-SCH transport bits of a DL-SCH soft channel bits supported layers for
block bits received transport block received spatial multiplexing in
within a TTI within a TTI DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

Confidential
Table below outlines uplink physical layer parameter values set by the UE
Category field.
UE Category Maximum number of bits of an UL-SCH Support for 64 QAM in UL
transport block transmitted within a TTI
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No
Category 5 75376 Yes
SYSTEM OPERATION
provides associated parameters, counters, and KPIs.
How to Activate
Preconditions
• Run CHG-PUSCH-CONF and set ENABLE_SIX_FOUR_QAM to True.
• Run CHG-PUSCH-CONF and set ENABLE_SIX_FOUR_QAM to False.
Key Parameters
parameter.
Parameter Descriptions of CHG-PUSCH-CONF/RTRV-PUSCH-CONF
ENABLE_SIX_FOUR_QAM Whether to support 64 QAM. Only the category 5 UEs capable of sending 64-
QAM using the uplink are affected by this parameter value.
• False: 64 QAM is not applied.
• True: 64 QAM when the eNB receives data is applied.

Confidential
parameters.
N_S_B The number of sub-bands in Type 2 PUSCH hopping.
HOPPING_MODE Hopping mode.
• ci_interSubFrame: Inter-subframe hopping.
• ci_intraAndInterSubFrame: Intra and inter-subframe hopping.
ENABLE_SIX_FOUR_QAM Whether to support 64 QAM. Only the category 5 UEs capable of sending 64-
QAM using the uplink are affected by this parameter value.
• False: 64 QAM is not applied.
• True: 64 QAM when the eNB receives data is applied.
GROUP_HOPPING_ENABL Whether to support group hopping.
E • False: Group hopping is not supported.
• True: Group hopping is supported.
GROUP_ASSINGNMENT_P The group assignment value in the PUSCH.
USCH
SEQUENCE_HOPPING_EN Whether to support sequence hopping.
ABLE • False: Sequence hopping is not supported.
• True: Sequence hopping is supported.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS36.300: Evolved Universal Terrestrial Radio Access (E-UTRA) and
description; Stage 2.

Confidential
LTE-SW0106, Support for UE Category 6

INTRODUCTION
Samsung eNB supports UE category 6, which is defined in release 10 version of
3GPP specifications. This category defines maximum total bits per Transmission
Time Interval (TTI) in the downlink and uplink.
BENEFIT
The eNB supports category 6 UE that are capable of improving downlink
throughput.
DEPENDENCY
LIMITATION
Category 6 UE terminal is required.
SYSTEM IMPACT
FEATURE DESCRIPTION
The UE category information defines a combined uplink and downlink capability.
The UEs, which are category 6, also support category 4. This allows the network
to treat the UE as category 4 device when the network does not support category 6.
Tables below outline the parameters for downlink and uplink physical layer
respectively.
Downlink
UE Category Maximum number of Maximum number of Total number of soft Maximum number of
DL-SCH transport bits of a DL-SCH channel bits supported layers for
block bits received transport block spatial multiplexing
within a TTI received within a in DL
TTI
Category 6 301,504 149,776 (4layers) 3,654,144 2 or 4

75376 (2layers)
Uplink

Confidential
UE Category Maximum number of UL- Maximum number of bits of Support for 64 QAM in UL
SCH transport block bits a UL-SCH transport block
received within a TTI received within a TTI
Category 6 10296 10296 No
The peak data rates of tables above are not user data rates that are achievable in a
regular loaded system. They represent a maximum rate the UE can be allocated by
the eNB in 1 ms scheduling interval and sometimes even represent the maximum
possible cell capacity. It means they can only be achieved in the event that these
resources are given to a single user and that this user experiences the best possible
channel state.
At initial attach, the UE will report its capabilities with RRC procedure depicted in
figure below. In addition to the following information are signaled: UE categories,
supported LTE release, supported access technologies and frequency band, and so
on.
Due to the ever-growing number of optionally supported features of different

releases, the message size has been growing significantly. If an MME receives the
information from the eNB, it stores the UE capabilities of all UEs registered in its
tracking area. After storing, the MME provides this information to the eNB each
time the UE is reconnected to the network.
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

Table below outlines the main counter associated with this feature.
Confidential

REFERENCE
[1] 3GPP TS 36.306 "Evolved Universal Terrestrial Radio Access (E-UTRA); UE
Radio Access Capabilities".
[2] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA)
Radio Resource Control (RRC) specification".

Confidential
LTE-SW0111, UE Counting per Category

INTRODUCTION
An eNB performs counting for each category of RRC_Connected UE and collects
the statistics per eNB.
BENEFIT
The UE counting per category helps to analyze the connected UEs status per
category.
DEPENDENCY
Others: If attach procedure or idle to connected transition is not complete after
eNB obtains UE Capability information, the statistics for category is counted but
the UE context release may be initiated in the eNB/MME.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature enables the operator to find out the number of each UE category in the
network. The eNB obtains the UE category information during two possible states
during attachment or during RRC_IDLE to RRC_CONNECTED transition.
The following figure shows when category statistics is counted during attachment,
the eNB saves UE category during UE Capability Enquiry/UE Capability
Information procedure and counts the statistics after obtaining UE category
information.

Confidential
The following figure shows when category statistics is counted during RRC_IDLE
to RRC_CONNECTED procedure, the eNB saves UE category during Initial
Context Setup Request/Initial Context Setup Response procedure and counts the
statistics after obtaining UE category information.
SYSTEM OPERATION
How to Activate
Key Parameters

Confidential
Counters and KPIs

UE_Category_m1 Number of UEs in the UE Category m1
REFERENCE
[1] The Vendor’s LTE solution shall support functionality to enquire UE capability
and record number of UEs per eNB and per cell for each UE category.
Equipment (UE) radio access capabilities (Release 9)
Resource Control (RRC); Protocol specification (Release 9)

Confidential
LTE-SW0112, Battery Saving Option Depending

on UE Type
INTRODUCTION
When an eNB requests UE capability information, a UE (CPE or dongle type
device) can set the value of deviceType-r9 to noBenFromBatConsumpOpt, so the
UE should not enable active DRX. In this case, the UE does not need NW-based
battery consumption optimization.
BENEFIT
The UE can always be connected to the network, which improves packet delivery
time.
DEPENDENCY
Requires Release 9 UE (noBenFromBatConsumpOpt support)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Figure below depicts how the eNB acquires the UE capability information in an
LTE network.
5 The eNB sends the UECapabilityEnquiry message during RRC Connection

setup procedures.
6 The UE responds with UECapabilityInformation message. If the UE (CPE or
dongle) does not need Active DRX function, it sets deviceType-r9 to
noBenFromBatConsumpOpt in UE-EUTRA-CAPABILITY IE.

Confidential
The following shows ASN.1 structure for noBenFromBatConsumpOpt in UE-

EUTRA-Capability IE.
-- ASN1START
…
UE-EUTRA-CAPABILITY-v920-Ies::=SEQUENCE {
phyLayerParameters-v920PhyLayerParameters-v920,
interRAT-ParametersGERAN-v920IRAT-ParametersGERAN-v920,
interRAT-ParametersUTRA-v920IRAT-ParametersUTRA-v920OPTIONAL,
interRAT-ParametersCDMA2000-v920IRAT-ParametersCDMA2000-1XRTT-v920OPTIONAL,
deviceType-r9ENUMERATED {noBenFromBatConsumpOpt}OPTIONAL,
csg-ProximityIndicationParameters-r9CSG-ProximityIndicationParameters-r9,
neighCellSI-AcquisitionParameters-r9NeighCellSI-AcquisitionParameters-r9,
son-Parameters-r9SON-Parameters-r9,
nonCriticalExtensionUE-EUTRA-CAPABILITY-v940-IEsOPTIONAL
}
…
-- ASN1STOP
The UE capability transfer procedures occur when the UE initially attaches to the
network. The UE-EUTRA-Capability IE acquired during this procedure is stored
in MME. When the UE transits from RRC_IDLE to RRC_CONNECTED state,
the eNB receives the UE-EUTRA-Capability IE from the MME in Initial Context
Setup Request message, instead of requesting to UE.
NW-based Battery Consumption Optimization Operation

The eNB performs the following procedures for UEs with
noBenFromBatConsumpOpt enabled:
• Normal DRX is not activated for noBenFromBatConsumpOpt selected UE if
BATTERY_SAVING_OPTION_USAGE (CHG-BATSAV-INFO) is enabled.

Confidential
Even if the UE sets noBenFromBatConsumpOpt, the connection can be released

when the inactivity timer expires due to no packet delivery during a specific
period.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-BATSAV-INFO and set BATTERY_SAVING_OPTION_USAGE to

USE.
• Run CHG-BATSAV-INFO and set BATTERY_SAVING_OPTION_USAGE to
NOT_USE.
Key Parameters
feature.
parameters.
Parameter Descriptions of CHG-BATSAV-INFO/RTRV-BATSAV-INFO
CELL_NUM The cell number to be changed.
BATTERY_SAVING_OPTION This parameter controls active DRX configuration to be set according to UE
_USAGE capability.
• NOT_USE: Function OFF. It means that active DRX is configured
regardless of the presence of deviceType = noBenFromBatConsumpOpt in
UE capability.
• USE: Function ON. It means that if deviceType =
noBenFromBatConsumpOpt is included in the UE capability, it will not
configure active DRX because NW-based battery consumption optimization
is not working. Otherwise, active DRX is configured.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS36.331: Evolved Universal Terrestrial Radio Access (E-UTRA);
Radio Resource Control (RRC) protocol specification

Confidential
LTE-SW0114, Enhancements for Diverse Data

Applications
INTRODUCTION
Multiple diverse data applications such as instant messaging, interactive content
pull, gaming, and HTTP video streaming are used in smart UEs. With the
increasing use of such applications, the UE suffers from low battery lifetime.
Therefore, it is necessary to optimize the power consumption of UE, and the eNB
is required to provide a better power efficient mode of operation.
BENEFIT
• Power consumption of particular UEs can be reduced due to the reduced
period of DRX duration or RRC connected mode.
• System efficiency of the eNB can be improved due to the reduced number of
RRC connected UEs.
DEPENDENCY
Release 11 UE to support UEAssistance Information: While transmitting
UEAssistance message to UE, if the UE sets powerPrefIndication to normal, the
UE starts or restarts the T340 timer with the powerPrefIndicationTimer value
received from eNB during RRCconnectionReconfiguration message.
LIMITATION
None
SYSTEM IMPACT
capabilities.
Interdependent feature: LTE-ME3402 Active DRX
This feature can be activated when LTE-ME3402 is activated if longDRX support
mode is selected.
As this feature can allow relatively longer DRX cycle than normal operation,
potentially additional delay for user traffic can happen.
Coverage
None

Confidential
Interfaces
None
FEATURE DESCRIPTION
The purpose of RAN Enhancements for Diverse Data Applications is used for the
eNB to provide power saving operation to a UE. Upon configuring the UE to
provide power preference indications, the eNB waits for the UE to provide its
power saving preference. Once the preference is known, the eNB provides
appropriate resolution based on operator configuration.
This feature is enabled based on the device type of UE. If UE device type is set to
noBenFromBatConsumpOpt received from UE in UE-EUTRA-CAPABILITY-
v920-IE, this feature is disabled as no DRX solution can be provided since the UE
does not need the network-controlled battery saving solution. The feature is
enabled if the UE device type is not set to noBenFromBatConsumpOpt received
from UE in UE-EUTRA-CAPABILITY-v920-IE.
1 If this feature is enabled, the eNB configures the UE to provide power
preference indication by sending RRC Connection Reconfiguration message
to UE with powerPrefIndicationConfig data structure set to setup. This
configuration message can be sent during any reconfiguration on the serving
cell or in the reconfiguration message during handover to E-UTRA.
powerPrefIndicationConfig-r11 is present in otherConfig-r9 structure. The
setup parameter part of the powerPrefIndicationConfig contains
powerPrefIndicationTimer-r11 parameter, which is a prohibit timer for power
preference indication reporting of UE. This prevents from frequent
PowerMode change (T340 timer) of the UE from normal to low.
2 The UE responds with RRC Connection Reconfiguration Complete message.
3 The UE further notifies to eNB with its power saving preference by sending
the UEAssistanceInformation message with either of the two possible values:
o powerPrefIndication is set to lowPowerConsumption
o powerPrefIndication is set to normal. The UE starts or restarts the T340
timer with the value set to powerPrefIndicationTimer received from eNB
during RRCconnectionReconfiguration message.
The UE should not change the PowerPreferenceMode from Normal to

lowPowerConsumption until the T340 timer expires.
The UE upon initiating RRCConnectionre-establishment procedure, should release

powerPrefIndicationConfig if configured and stop the T340 timer, if running.
4 If the eNB receives the message with powerPrefIndication set to

lowpowerconsumption, then based on the operator configuration, the eNB
responds to the UE with either:

Confidential
o A long value for long DRX cycle

Feature/Parameter Configuration Value/Description
DRX Long cycle length 80, 160, 320, 640, 1280, 2560 ms
o The RRC connection release message to save UE device power

consumption
With powerPrefIndication set to normal, the normal operation resumes.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-UEPWRSAVING-CCONF and set USED_FLAG to use.
• Run CHG-UEPWRSAVING-CCONF and set USED_FLAG to no_use.

Confidential
Key Parameters
parameter.
Parameter Descriptions of CHG-UEPWRSAVING-CONF/RTRV-UEPWRSAVING-
CONF
USED_FLAG This parameter shows whether UE power saving function is supported or not.
• no_use (0): UE power saving function is not supported.
• use (1): UE power saving function is supported.
parameters.
Parameter Descriptions of CHG-UEPWRSAVING-CONF/RTRV-UEPWRSAVING-
CONF
PREF_IND_TIMER This parameter shows prohibit timer (T340) for Power Preference Indication
reporting. This value represents in seconds. The value s0 means prohibit timer
is set to 0 second or not set, value s0.5 means prohibit timer is set to 0.5
second, value s1 means prohibit timer is set to 1 second, and so on.
{s0, s0dot5, s1, s2, s5, s10, s20, s30, s60, s90, s120, s300, s600}
SUPPORT_METHOD This parameter shows the method to support UE power saving.
• longDRX: Adjust longDRX for UE Power Saving
• RrcRelease: Adjust RRC Connection Release for UE Power Saving
Parameter Descriptions of CHG-UEPWRSAVING-DRXINFO/RTRV-

UEPWRSAVING-DRXINFO
QCI This parameter is the QoS Class Identifier (QCI). The QoS range is 0 to 255.
The standard QCI defined in the standard document is 1 to 9. 0 and 10 to 255
can be used by the operator optionally.
DRX_CONFIG_SETUP This parameter indicates whether to use the DRX for UE power saving.
• Release: DRX is not used.
• Setup: DRX profile is used
ON_DURATION_TIMER This parameter is onDurationTimer to monitor PDCCH in DRX mode.
(onDurationTimer specifies the number of consecutive PDCCH-subframes at
the beginning of a DRX Cycle.)
DRX_INACTIVITY_TIMER This parameter is drxInactivityTimer to monitor PDCCH in DRX mode. (drx-
InactivityTimer specifies the number of consecutive PDCCH-subframes after
successfully decoding a PDCCH indicating an initial UL or DL user data
transmission for this UE.)
DRX_RETRANSMISSION_T This parameter is drxRetransmissionTimer to monitor PDCCH in DRX mode.
IMER (drx-RetransmissionTimer specifies the maximum number of consecutive

Confidential
PDCCH-subframes for as soon as a DL retransmission is expected by the UE.)
LONG_DRXCYCLE_START The long DRX cycle and DRX start offset values to run onDurationTimer in
_OFFSET_TYPE DRX mode. In the case of UE power saving, longDRCCycle can have multiples
of sf80.
Counters and KPIs

with this feature.
REFERENCE
description; Stage 2, Release 11
[2] 3GPP TS36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); RRC
Control and Signaling, Release 11
[3] 3GPP TR 36.822 LTE Radio Access Network (RAN) enhancements for
diverse data applications, Release 11

Confidential
LTE-SW0314, Multi-Frequency Band Indicator

support
INTRODUCTION
A various bands are specified for the same physical frequency in 3GPP 36.101 (for
example, Band 5, Band 18, and Band 26 are specified for 800 MHz frequency).
Therefore, with 800 MHz frequency, some UEs are implemented and stored with
Band 5 in UE Capability even though other UEs may be implemented and stored
with Band 18 in UE Capability. If one of the various bands is designated and
called the operating band (for example, Band 5), other bands are called the
overlapping bands (for example, Band 18, Band 26). The Multi-Frequency Band
Indicator (MFBI) is introduced for eNB to accept UEs with the various bands, that
is, operating band and overlapping bands.
BENEFIT
The eNB can support UE of supporting the overlapping bands, as well as UEs of
supporting the operating band.
DEPENDENCY
Others: The UE that supports Multi-frequency band.
LIMITATION
The maximum number of additional frequency bands is eight.
SYSTEM IMPACT
FEATURE DESCRIPTION
A various bands are specified for the same physical frequency in 3GPP 36.101 (for
example, Band 5, Band 18, and Band 26 are specified for 800 MHz frequency).
With 800 MHz frequency, some UEs are implemented and stored with Band 5 in
UE Capability even though other UEs may be implemented and stored with B and
18 in UE Capability. If one of the various bands is designated and called the
operating band (for example, Band 5), other bands are called the overlapping
bands (for example, Band 18, Band 26). For the eNB to accept UEs with the
various bands, that is, operating and overlapping bands, the eNB broadcasts MFBI
in SIB. UEs with operating band and UEs with overlapping band can be aware that
it is possible to attach eNB which broadcasts MFBI.
The same physical frequency can have different EARFCN value depending on

Confidential
band.
Operation Band
The operating band can be different for each cell. In addition, the cell and the UE
can support different operating bands. Through the freqBandIndicator within SIB1,
the eNB informs all UEs of the operating band supported by the cell. The eNB can
determine the band supported by the UE through the SupportedBandListEUTRA
within the UE-EUTRA-CAPABILITY of the UE.
Overlapping Band
The overlapping band is same physical frequency as the operating band; however
the numbering values of those bands are different. Thus, the availability of the
overlapping band depends on the operating band. The eNB informs the UE of one
or more overlapping bands supported by the cell in the multiBandInfoList of SIB1
using configuration value of OVERLAPPING_BAND_DL (CHG-EUTRA-FA).
UE that Requires Overlapping Band Support

The UE does not operate with the operating band. Therefore, it operates with the
overlapping band in the MFBI cell. For this, the overlapping band should be
enabled in the MFBI cell and the UE should support the overlapping band and the
MFBI (the 31st bit of the FGI is set to 1).
MFBI Cell
An MFBI cell supports the overlapping band. The operating band supported by the
cell supports one or more overlapping bands. One or more overlapping bands for
the operating band must be enabled by OVERLAPPING_BAND_ENABLE_FLAG
(CHG-EUTRA-FA) in the PLDEutraFaPriorInfoFunc.
Non-MFBI Cell
A non-MFBI cell does not support the overlapping band. The operating band
supported by the cell does not support an overlapping band.
MFBI Function
The UE can access the eNB provided the broadcasted MultiBandInfoList includes
a band that the UE supports. If FGI bit #31 is present in UECapabilityInformation
received during connection setup procedures, the eNB identifies whether the UE
supports MFBI. If FGI #31 is true and the UE supports an overlapping band, the
eNB admits the UE by using EARFCN, which corresponds to high priority band
that the UE indicates. Otherwise, the UE fails to access the network.
When the UE connected to the network based on the overlapping band tries to
handover to a neighbor cell, the source eNB includes the DL EARFCN
information of the UE in IE sourceDl-CarrierFreq in
HandoverPreparationInformation message. The target eNB the includes dl-
CarrierFreq (EARFCN), ul-CarrierFreq (EARFCN), and
additionalSpectrumEmission information of the UE in
RRCConnectionReconfiguration (mobilityControlInfo) message.
If the multiBandInfoList is set to OVERLAPPING_BAND_DL (CHG-EUTRA-FA)
and the MFBI function is On by setting OVERLAPPING_BAND_ENABLE_FLAG
(CHG-EUTRA-FA) to 1, the MFBI eNB carries out the following operations:

Confidential
• Includes the freqBandIndicator configured with the operating band of the

MFBI eNB in SIB1.
• Includes the multiBandInfoList IE in SIB1 and SIB2 and the overlapping band
in the multiBandInfoList of SIB1. It also includes the
additionalSpectrumEmission for the overlapping band in the
multiBandInfoList of SIB2 in the same order as with SIB1 by using
ADDITIONAL_SPECTRUM_EMISSION (CHG-EUTRA-FA).
• If the UE is in an RRC_CONNECTED state, the eNB sets the downlink (DL)
EARFCN of the overlapping band with the highest priority supported by the
UE in the SupportedBandListEUTRA within the UE-EUTRA-CAPABILITY
to the carrierFreq within the measObject for the serving frequency.
• When the UE attempts a handover to an adjacent eNB, the source MFBI eNB
sets the DL EARFCN of the overlapping band allocated for the UE to the
sourceDl-CarrierFreq of the HandoverPreparationInformation message
• During the handover preparation for accepting the hand-in of UE, the target
MFBI eNB sets the overlapping band value with the highest priority supported
by the UE in the SupportedBandListEUTRA within the UE-EUTRA-
CAPABILITY to the dl-CarrierFreq, ul-CarrierFreq, and
additionalSpectrumEmission within the mobilityControlInfo of the
RRCConnectionReconfiguration message.
• When the eNB carries out Idle mode load balancing of UE, the
idleModeMobilityControlInfo is included in the RRCConnectionRelease
message. The eNB sets the DL EARFCN of the overlapping band of the MFBI
eNB with the highest priority supported by the UE in the
SupportedBandListEUTRA within the UE-EUTRA-CAPABILITY to the
carrierFreq within the instance of FreqPriorityEUTRA for the MFBI eNB of
the RRCConnectionRelease message.
Table below outlines the overlapping bands (multi-band environments) for each E-
UTRA band (Ref. TS36.307).
E-UTRA Operating Band Overlapping E-UTRA Operating Duplex Mode
Bands
2 25 FDD
3 9 FDD
4 10 FDD
5 18, 19, 26 FDD
9 3 FDD
10 4 FDD
12 17 FDD
17 12 FDD
18 5, 26, 27 FDD
19 5, 26 FDD
25 2 FDD
26 5, 18, 19, 27 FDD
27 18, 26 FDD

Confidential
E-UTRA Operating Band Overlapping E-UTRA Operating Duplex Mode

Bands
33 39 TDD
38 41 TDD
39 33 TDD
41 38 TDD
The eNB uses SIB1, SIB2, SIB5 and SIB6 to broadcast MultiBandInfoList
information. It can broadcast up to 8 band lists.
The UE considers the cell as barred if the frequency band indicated in the
freqBandIndicator is not part of the frequency bands supported by the UE.
SIB1-Band list
SystemInformationBlockType1-v8h0-IEs::=SEQUENCE {
multiBandInfoListOPTIONAL,-- Need OR
nonCriticalExtensionSystemInformationBlockType1-v9e0-IEsOPTIONAL-- Need OP
}
SIB2-AdditionalSpectrumEmission value of band list

SystemInformationBlockType2-v8h0-IEs::=SEQUENCE {
multiBandInfoListSEQUENCE (SIZE (1..maxMultiBands)) OF AdditionalSpectrumEmissionOPTIONAL,-- Need
OR
nonCriticalExtensionSystemInformationBlockType2-v9e0-IEsOPTIONAL-- Need OP
}
SIB5-MultiBandInforList of the neighbor eNB

InterFreqCarrierFreqInfo-v8h0::=SEQUENCE {
multiBandInfoListOPTIONAL-- Need OR
}
SIB6 - UTRA related Info.

CarrierFreqInfoUTRA-FDD-v8h0 ::= SEQUENCE {
multiBandInfoList SEQUENCE (SIZE (1..maxMultiBands)) OF FreqBandIndicator-UTRA-FDD OPTIONAL --
Need OR
}
SYSTEM OPERATION
How to Activate
• To support the MBI function, the following two conditions must be satisfied
Confidential
by UE and eNB:
o Provide the overlapping band-related information for the operating band to
UE through SIB in the cell.
o To support the MBI function if UE does not support the operating band,
overlapping band must be supported and the thirty-first bit of the feature
group indicator must be true.
• The eNB can support multiple overlapping bands for operating band by the
system parameter setting, and set an ON/OFF flag in MBI function by
overlapping band. To support the MBI function, its flag of one or more
overlapping bands for the operating band must be set to ON.
No. UE Capability MBI eNB
Operating band Overlapping Feature Group EARFCN setting for the UE
band Indicator, 31st bit a
1 supported Not supported True/False EARFCN allocated to the operating band
2 supported Supported True/False EARFCN allocated to the operating band
3 not supported supported True EARFCN of the designated band to the
top priority among the overlapping bands
supported by the UE
4 not supported supported False N/A
a The thirty-first bit in feature group indicator shows the support of MBI of UE (If it is true, MBI is
supported), and it may be confirmed by feature group indicators in the UE-EUTRA-CAPABILITY of UE in

eNB.
If eNB informs one or more overlapping bands, and if UE supports at least one of overlapping bands, it is
considered to be 'supported'.
• To support the MBI function, the eNB must meet the two conditions, and the
other separate activation procedures are not required. In #3 case in the table
above, the MBI function works by the following operation:
o Provide the overlapping band-related information for the operating band to
UE through SIB in the cell.
o During the course of confirming UE radio access capability between the
eNB and the UE, the eNB can determine whether UE works as an
operating band or an overlapping band. When eNB receives UE capability
information from them, compare the operating band (bandEUTRA) of the
SupportedBandListEUTRA in the UE-EUTRA-CAPABILITY and the
overlapping band supported by the cell. If UE supports one of the
overlapping bands supported by the cell without supporting the operating
band of the cell, the eNB activates the MBI function with which the UE
works as the overlapping band in the highest priority.
Key Parameters
This section describes the key parameters for configuration of the feature.

Confidential
To configure the feature settings, run the associated command and set the key
parameters.
Parameter Descriptions of CHG-EUTRA-FA/RTRV-EUTRA-FA
CELL_NUM The cell number. This value must not exceed the maximum
number of cells supported by the system. It is determined by
Carrier/Sector. For example, if the maximum capacity system is 1
Carrier/3 Sector, up to three cells are supported.
FA_INDEX EUTRA frequency index. Up to 8 FAs can be assigned per cell.
OVERLAPPING_EARFCN_UL Supported overlapping EarfcnUL.
OVERLAPPING_EARFCN_DL Supported overlapping EarfcnDL.
ADDITIONAL_SPECTRUM_EMISSION AdditionalSpectrumEmission of overlapping band.
To configure the feature settings for NB-IoT, run the associated commands and set
the key parameters.
Parameter Descriptions of CHG-NBEUTRA-FA/RTRV-NBEUTRA-FA
CELL_NUM The PLD index parameter of the cell number. This value must not
exceed the maximum number of cells supported by the system.
FA_INDEX The PLD index parameter of the FA index. This parameter is the
EUTRA frequency index. This value must not exceed the
maximum number of FA supported by the system.
OVERLAPPING_BAND_ENABLE_FLAG Multiple Frequency Band Indicator (MBI) supported flag array per
overlapping bandIndicator.
• 0: not support MBI.
• 1: support MBI.
OVERLAPPING_EARFCN_UL Array of supported Overlapping EarfcnUL listed in the same order
of overlappingBandEnableFlag[8]. This parameter value is valid
only if overlappingBandEnableFlag of the corresponding
Overlapping Band Idex is configured as 1.
OVERLAPPING_EARFCN_DL Array of supported Overlapping EarfcnDL listed in the same order
of overlappingBandEnableFlag[8]. This parameter value is valid
only if overlappingBandEnableFlag of the corresponding
Overlapping Band Idex is configured as 1.
Counters and KPIs

with this feature.
REFERENCE
Resource Control (RRC) protocol specification

Confidential
LTE-SW0315, Extended Access Barring (SIB14)

INTRODUCTION
The Extended Access Barring (EAB) restricts low priority UEs, such as Machine-
Type Communications (MTC), from accessing the network during RAN or Core
Network overload state. UEs configured for EAB are considered as more tolerant
to access restrictions than other UEs. To support this feature, barring information
is included in the SIB14 message, which is broadcasted to UEs.
BENEFIT
This feature mitigates RAN and Core Network (CN) overload by restricting access
attempts from UEs that are configured for EAB.
DEPENDENCY
Others: Requires release 11 UE.
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
None
Coverage
None
Interfaces
For the air interface:
• A new RRC SystemInformationBlockType14 message is introduced.
• A new eab-ParamModification-r11 IE in RRC Paging message is introduced.
FEATURE DESCRIPTION
Due to the diverse applications and services deployed in the LTE network, there
can be excess signaling traffic. This excess signaling traffic can overload RAN or
Core Network. The eNB reaches congestion state when:

Confidential
• The CPU load level of eNB exceeds overload threshold.

To configure CPU thresholds by its load level, refer to OAM-FM0201, Alarm
Parameter Configuration.
• Accepted UEs have reached its full capacity such as maximum number of UEs
per cell except the reserved resources.
To configure maximum call count, CALL_THRESH_FOR_SIB14_HIGH can
be configured by using CHG-CELL-CAC.
• All the MMEs connected to the eNB inform the eNB about the congestion
state through sending OVERLOAD START message to the eNB.
The following figure depicts the procedures performed by the eNB to apply EAB
when the eNB is overloaded or the CN is overloaded. When the congestion state
has reached or operator configures manually to start EAB, the eNB applies EAB.
The eNB broadcasts the access class bitmap and the UE category through the
SIB14 message to UEs. The UE determines whether it is subjected to barring
based on this information. If the idle UE determines that it is subjected to barring,
it refrains from sending a connection request.
To apply EAB manually, EAB_CTR_USAGE can be configured as

eabManualCtrl by CHG-CELL-ACS. Otherwise, to apply EAB based on
congestion state automatically, EAB_CTR_USAG can be configured as

Confidential
eabAutoCtrl by CHG-CELL-ACS.
The parameters for SIB14 message can be configured using EAB_PLMN_TYPE,
EAB_CATEGORY, and ACCESS_CLASS[10] parameters by CHG-EABENH-
PARA.
The UE acquires the SIB14 message upon receiving a PAGING message from the
eNB. If the UE has not stored a valid version of SIB14 upon entering into the
RRC_IDLE state, the UE acquires the SIB14 message. The eNB sets the SIB14
Flag as TRUE in the SIB1 message when the EAB is applied.
The UE refrains from access if all of these conditions are met, as depicted in the
following figure:
• The UE belongs to Access Class (0 to 9).
• The UE category is the same as received in SIB14.
• The UE access class is the same as received in SIB14.
The eNB removes the EAB through Paging message EAB parameter modification
indication, and broadcasting SIB1 indicating that SIB14 is not scheduled when it
comes back to normal state or receives the OVERLOAD STOP message from the
MME.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
• The SIB14_PERIOD of CHG-SIB-INF must be set to 0 to 6.
• Run CHG-CELL-ACS and set EAB_CTR_USAGE to the desired value
eabManualCtrl or eabAutoCtrl.
• Run CHG-EABENH-PARA and set EAB_PARAM_USAGE to 1 for the desired
CELL_NUM index, EAB_PLMN_TYPE index, and
EAB_BARRING_STATUS_TYPE index selected by EAB_CTR_USAGE.
If EAB_CTR_USAGE is set to eabManualCtrl, configure
EAB_CTR_USAGE as 1 for EAB_BARRING_STATUS_TYPE =
barManual.
Otherwise, configure EAB_CTR_USAGE as 1 for
EAB_BARRING_STATUS_TYPE = cpuCritical, cpuMajor,
cpuMinor, or cpuNormal.
• Run CHG-EABENH-PARA and set EAB_PARAM_USAGE to 0 for all the
EAB_BARRING_STATUS_TYPE index and EAB_PLMN_TYPE index for the
desired cell.
Key Parameters
parameter.
Parameter Descriptions of CHG-EABENH-PARA/RTRV-EABENH-PARA
EAB_PARAM_USAGE This parameter is the usage flag of EAB barring status.
• no_use
• use
parameters.
Parameter Descriptions of CHG-CELL-ACS/RTRV-CELL-ACS
EAB_CTR_USAGE This parameter represents which EAB mode to be used.

Confidential
• eabManualCtrl: Manual Mode
The eNB triggers EAB manually using eabBarManual parameter set.
• eabAutoCtrl: Auto Mode
The eNB automatically performs EAB based on triggering conditions (such as
CPU load, MME overload, and number of RRC connected UEs) using
eabBarAuto parameter set.
Parameter Descriptions of CHG-EABENH-PARA/RTRV-EABENH-PARA

CELL_NUM This index parameter is the cell number to identify each cell. This value must not
EAB_PLMN_TYPE This index parameter is the EAB barring status to be changed or retrieved for
each PLMN or the PLMN Common.
• eabPlmn0: EAB barring status for PLMN #0.
• eabCommon: eab barring status for all PLMNs.
EAB_BARRING_STATUS_ This index parameter is the EAB barring status to be changed or retrieved for
TYPE each PLMN or the PLMN Common.
• cpuNormal: The CPU of the main card is in Normal state.
• cpuMinor: The CPU of the main card is in Minor state.
• cpuMajor: The CPU of the main card is in Major state.
• cpuCritical: The CPU of the main card is in Critical state, or all the MME
overload state, or LTE UE capacity based EAB
• barManual: Manual Mode.
EAB_PARAM_USAGE This parameter is the usage flag of EAB barring status.
• no_use
• use
EAB_CATEGORY Indicates the category of UEs to which EAB applies.
• categoryA: corresponds to all UEs.
• categoryB: corresponds to the UEs that are neither in their HPLMN nor in a
PLMN that is equivalent to it.
• categoryC: corresponds to the UEs that are neither in the PLMN listed as most
preferred PLMN of the country where the UEs are roaming in the operator-
defined PLMN selector list on the USIM, nor in their HPLMN nor in a PLMN
that is equivalent to their HPLMN.
ACCESS_CLASS[10] This parameter indicates whether access class is barred or not barred. Index 0 to
9 correspond to access class 0 to 9.
• 1: Access class x barred. (x : 0 to 9)
• 0: Access class x not barred. (x : 0 to 9)
NUMBER_OF_RANDOM_ This parameter configures the number of barred EAB ACs to be randomly
EAB_ACS selected for SIB14 when the EAB is applied.
• 0: The eNB includes the parameter ACCESS_CLASS[10] in SIB14
corresponding to the current CPU load level and PLMN type.
• 1 - 10: The eNB bars the randomly selected access classes out of AC0 to AC9
as many as this parameter value ignoring the parameter Access_Class[10].

Confidential
To configure maximum call count based EAB triggering, run CHG-CELL-CAC

and set CALL_THRESH_FOR_SIB14_HIGH desired value.
Parameter Description of CHG-CELL-CAC
CALL_THRESH_FOR_SIB It is a percentage value to determine whether to apply EAB. If the current number
14_HIGH of RRC connected UEs in the cell exceeds MAX_CALL_COUNT *
CALL_THRESH_FOR_SIB14_HIGH, SIB14 is transmitted to the UE to apply
Extended Access Barring.
Counters and KPIs

with this feature.
REFERENCE
description; Stage 2. Release 11
Resource Control (RRC) protocol specification. Release 11
[3] 3GPP TS36.413 Evolved Universal Terrestrial Radio Access (E-UTRA); S1
Application Protocol (S1AP). Release 11
[4] 3GPP TS22.368 Service requirements for Machine-Type Communications
(MTC). Release 11
Universal Terrestrial Radio Access Network. Release 11

Confidential
LTE-SW0316, Network Signaling (NS) Support

INTRODUCTION
In some specific deployment scenario, the operator wants UEs to comply to
additional transmission requirements due to spectrum band specific regulation. For
this purpose, 3GPP standard defines a signaling mechanism enabled by the
network. This signaling value is referred to as Network Signaling (NS) value,
which is an integer between 1 and 32. TS 36.101 specifies a set of additional
requirements corresponding to each NS value. Depending on NS value, the
requirement can include additional spectrum mask, additional spurious emission,
and/or A-MPR (Additional Maximum Power Reduction). For detail, the reader is
referred to Table 6.2.4-1 in Section 6.2.4 of TS36.101.
The NS value is delivered to UE via AdditionalSpectrumEmission information
element, which is included in either broadcast (SIB2) or handover command
(MobilityControlInfo) message. Samsung eNB supports the configuration of
AdditionalSpectrumEmission value as cell-level parameter
ADD_SPECTRUM_EMISSION (CHG-CELL-INFO).
BENEFIT
This feature provides the way to inform UEs of additional requirement on
spectrum emission as defined in standard.
DEPENDENCY
• Prerequisite Features: LTE-ME3006, AMPR (Additional Maximum Power
Reduction) required when NS_07 needs to be used.
LIMITATION
The following features cannot be enabled when NS_07 is configured:
• LTE-ME3312, PRB Randomization
• LTE-ME3308, UL Frequency Selective Scheduling (FSS)
• LTE-ME3501, UL Resource Allocation Type1 (Multi-Cluster PUSCH)
SYSTEM IMPACT
FEATURE DESCRIPTION
There are two different ways of informing UE of NS value: one is
SystemInformationBlockType2 and the other is MobilityControlInfo IE included
Confidential
in handover command message.

SystemInformationBlockType2
SystemInformationBlockType2 ::= SEQUENCE {
...
freqInfo SEQUENCE {
ul-CarrierFreq ARFCN-ValueEUTRA OPTIONAL, -- Need OP
ul-Bandwidth ENUMERATED {n6, n15, n25, n50, n75, n100}
OPTIONAL, -- Need OP
additionalSpectrumEmission AdditionalSpectrumEmission
},
...
}
MobilityControlInfo IE
MobilityControlInfo ::= SEQUENCE {
targetPhysCellId PhysCellId,
carrierFreq CarrierFreqEUTRA OPTIONAL, -- Cond HO-toEUTRA2
carrierBandwidth CarrierBandwidthEUTRA OPTIONAL, -- Cond HO-toEUTRA
additionalSpectrumEmission AdditionalSpectrumEmission OPTIONAL, -- Cond HO-toEUTRA
...
}
Expected UE Behavior upon Receiving AdditionalSpectrumEmission

UEs translates the integer value informed by AdditionalSpectrumEmission into NS
value or NS_XX (that is, XX=01, 02, 03,..., 32). The following table (Table 6.2.4-
1 in TS 36.101) specifies the additional requirement for each NS value. All
subclause and other Tables are represented in the same standard document.
Network Requirements E-UTRA Channel bandwidth Resources A-MPR (dB)
Signaling value (subclause) Band (MHz) Blocks (NRB)
NS_01 6.6.2.1.1 Table 5.5-1 1.4, 3, 5, 10, 15, 20 Table 5.6-1 NA
NS_03 6.6.2.2.1 2, 4, 10, 23, 3 >5 ≤1
25, 35, 36
5 >6 ≤1
10 >6 ≤1
15 >8 ≤1
20 > 10 ≤1
NS_04 6.6.2.2.2 41 5 >6 ≤1
10, 15, 20 Table 6.2.4-4
NS_05 6.6.3.3.1 1 10, 15, 20 ≥ 50 ≤1
NS_06 6.6.2.2.3 12, 13, 14, 1.4, 3, 5, 10 Table 5.6-1 n/a
17
NS_07 6.6.2.2.3 13 10 Table 6.2.4-2
6.6.3.3.2
NS_08 6.6.3.3.3 19 10, 15 > 44 ≤3
NS_09 6.6.3.3.4 21 10, 15 > 40 ≤1
> 55 ≤2
NS_10 - 20 15, 20 Table 6.2.4-3
NS_11 6.6.2.2.1 23 1.4, 3, 5, 10, 15, 20 Table 6.2.4-5
NS_12 6.6.3.3.5 26 1.4, 3, 5 Table 6.2.4-6

Confidential
Network Requirements E-UTRA Channel bandwidth Resources A-MPR (dB)

Signaling value (subclause) Band (MHz) Blocks (NRB)
NS_13 6.6.3.3.6 26 5 Table 6.2.4-7
NS_14 6.6.3.3.7 26 10, 15 Table 6.2.4-8
NS_15 6.6.3.3.8 26 1.4, 3, 5, 10, 15 Table 6.2.4-9
Table 6.2.4-10
NS_16 6.6.3.3.9 27 3, 5, 10 Table 6.2.4-11, Table 6.2.4-12,
Table 6.2.4-13
NS_17 6.6.3.3.10 28 5, 10 Table 5.6-1 n/a
NS_18 6.6.3.3.11 28 5 ≥2 ≤1
10, 15, 20 ≥1 ≤4
NS_19 6.6.3.3.12 44 10, 15, 20 Table 6.2.4-14
NS_20 6.2.2 23 5, 10, 15, 20 Table 6.2.4-15
6.6.2.2.1
6.6.3.2
... - - - - -
NS_32 - - - - -
For instance, if it is intended to give additional spectrum emission requirement to

Band 41 UEs, NS_04 can be used.
SYSTEM OPERATION
How to Activate
Key Parameters
parameter.
CELL_NUM The cell number to be changed or retrieved.
ADD_SPECTRUM_EMISSION Additional spectrum emission used by the active cell. At maximum power,
UE can additionally reduce power (see 6.2.4 in 3GPP TS 36.101). This
information is broadcast to UE using SIB 2.
Counters and KPI

Confidential
with this feature.
REFERENCE
Resource Control (RRC) Protocol specification

Confidential
LTE-SW0318, SIB Broadcast (SIB16)

INTRODUCTION
SIB16 broadcasts UTC and GPS time information. This supports a kind of UEs,
which requires the accurate time information to synchronize contents playtime
with BM-SC.
BENEFIT
This feature delivers absolute time information to a UE.
DEPENDENCY
• Prerequisite Features: LTE-SV0501 (eMBMS Basic Function)
• Others: Broadcast SIB16 in the cells where eMBMS service is provided.
LIMITATION
Release 11 or later version of UE can receive the system messages.
SYSTEM IMPACT
FEATURE DESCRIPTION
SystemInformationBlockType16 contains information related to GPS time and
Coordinated Universal Time (UTC). The UE may use the parameters provided in
this system information block to obtain the UTC, the GPS and the local time.
The relationship between UTC and GPS time is as follows:
timeInfoUTC = GPS time-leapSeconds, where timeInfoUTC counts up by 10 ms
and leapSeconds counts by second.
-- ASN1START
SystemInformationBlockType16-r11::= SEQUENCE {
timeInfo-r11 SEQUENCE {
timeInfoUTC-r11 INTEGER (0..549755813887),
dayLightSavingTime-r11 BIT STRING (SIZE (2)) OPTIONAL, -- Need OR
leapSeconds-r11 INTEGER (-127..128) OPTIONAL, -- Need OR
localTimeOffset-r11 INTEGER (-63..64) OPTIONAL -- Need OR
} OPTIONAL, -- Need OR
lateNonCriticalExtension OCTET STRING OPTIONAL, -- Need OP
...
}
-- ASN1STOP

Confidential
SystemInformationBlockType16 field descriptions

• dayLightSavingTime: It indicates if and how daylight saving time (DST) is
applied to obtain the local time. The semantics is the same as the semantics of
the Daylight Saving Time IE in TS 24.301 [35] and TS 24.008 [49]. The
first/leftmost bit of the bit string contains the b2 of octet 3, that is, the value
part of the Daylight Saving Time IE, and the second bit of the bit string
contains b1 of octet 3.
• leapSeconds: Number of leap seconds offset between GPS Time and UTC.
UTC and GPS time are related, that is, GPS time-leapSeconds = UTC time.
• localTimeOffset: Offset between UTC and local time in units of 15 minutes.
Actual value = IE value * 15 minutes. Local time of the day is calculated as
UTC time + localTimeOffset.
• timeInfoUTC: Coordinated Universal Time corresponding to the SFN
boundary at or immediately after the ending boundary of the SI-window in
which SystemInformationBlockType16 is transmitted. The field indicates the
integer count of 10 ms units since 00:00:00 on 1 January, 1900. This field is
excluded when estimating changes in system information, that is, changes of
timeInfoUTC should neither result in system information change notifications
nor in a modification of systemInfoValueTag in SIB1.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-SIB-INF and set SIB16_PREIOD to 0 to 6.
• Run CHG-SIB-INF and set SIB16_PREIOD to 7.
Key Parameters
parameter.

Confidential
Parameter Descriptions of CHG-EAB-PARA/RTRV-EAB-PARA

SIB16_PREIOD This parameter is the broadcast interval for SIB 16.
• ms80: 80 ms.
• ms160: 160 ms.
……
• ms5120: 5120 ms.
• not_used: SIB10 is not transmitted.
parameters.
Parameter Descriptions of CHG-LTIME-INF/RTRV-LTIME-INF
DAY_LIGHT_SAVE_TIME This parameter is the dayLightSavingTime information. It indicates if and how
daylight saving time (DST) is applied to obtain the local time.
Value description:
• 0: No adjustment for Daylight Saving Time
• 1: +1 hour adjustment for Daylight Saving Time
• 2: +2 hour adjustment for Daylight Saving Time
LP_SEC LP_SEC value included in the CDMA 1XRTT mobility information.
Counters and KPIs

with this feature.
REFERENCE
Resource Control (RRC); Protocol specification

Confidential
LTE-SW0319, RAN Assisted WLAN Interworking

INTRODUCTION
To provide network selection and traffic routing between the LTE and the WLAN
based on radio conditions such as signal strength quality, an eNB provides
assistance parameters via broadcast signaling to the UE. The RAN assistance
parameters includes the eNB signal strength thresholds, the WLAN channel
utilization thresholds, the WLAN backhaul data rate thresholds, the WLAN signal
strength, and the Offload Preference Indicator (OPI). The eNB provides a list of
WLAN identifiers to the UE via broadcast signaling. The UE uses the RAN
assistance parameters in the evaluation of access network selection and traffic
steering rules.
BENEFIT
This feature provides better throughput efficiency for UE between the LTE and the
WiFi.
DEPENDENCY
• Required Network Elements: The ANDSF server support is required if the
traffic offloading is through ANDSF rules.
• Related Radio Technology: The E-UTRAN (LTE) WiFi support is required for
UE for traffic steering from RAN to WiFi and vice-versa.
• Others:
o Release 12 UE that supports RAN-WiFi interworking.
o The MME that supports NAS level notification of PDN connection offload
ability to UE.
LIMITATION
None
SYSTEM IMPACT
The implementation of this feature does not have any impact on the network
FEATURE DESCRIPTION
To provide network selection and traffic routing between the LTE and the WLAN
based on radio conditions such as signal strength, the eNB provides some data to
UE by broadcasted signaling to assist UE perform access network selection and
traffic steering between EUTRAN and WLAN.
Figure below depicts the procedure of RAN-assisted WLAN interworking feature.

Confidential
UE eNB MME WLAN AP
1) PDN connection “offloadabillity” by NAS

when PDN connection is established
2) RAN Assistance Parameters (SIB17)
3) Perform access
network selection and
traffic steering by RAN
or ANDSF rules
5 (RAN rule only) The MME notifies the UE by NAS signaling of which PDN
connection can be offloaded to WLAN when the PDN connection is
established via “offloadability’ indicator.
The MME determines the offloadability of the PDN connection based on
subscription data and locally configured policy. The MME can provide an
updated WLAN offloadability indication of the PDN connection to the UE via
session management NAS signaling (Ref 23.401, 4.3.23).
6 RAN assistance information Provision
The RAN provides the assistant information through broadcast signaling
SIB17. The RAN assistance information includes thresholds for Wi-Fi and
RAN signal strength, channel quality, and WLAN backhaul load. The RAN
also broadcasts a list of identifiers (SSIDs, BSSIDs and HESSIDs) of neighbor
WLANs, to be used in the WLAN selection process.
7 Access network selection & traffic steering
Based on RAN rule or ANDSF rule, the UE perform access network selection
and traffic steering. The UE performs handover between the LTE access and
the WLAN access using the handover procedures described in TS 23.402.
SIB17 is defined to provide RAN-assisted WLAN interworking data per PLMN,
including:
• 3GPP access threshold (RAN/ANDSF rule both)
o RSRPmeas
o RSRQmeas
• WLAN access threshold (RAN/ANDSF rule both)
o ChannelUtilizationWLAN
o BackhaulRateDlWLAN
o BackhaulRateUlWLAN
o BeaconRSSI
• An Offload Preference Indication (OPI) (ANDSF rule only)
o Bitmap definition is operator-specific, not defined in 3GPP specification

Confidential
• WLAN AP ID list (RAN rule only)

o The IDs should be the neighbor cells (collocated or neighbors), which are
configurable.
• A timer for RAN rule evaluation TsteeringWLAN (RAN rules only)
Access network selection of UE and traffic steering can be based on RAN or
ANDSF rules, as decided by operator. The ANDSF rule is out of eNB scope.
Table below outlines the parameters used in RAN rules.
EUTRAN to WLAN WLAN to EUTRAN
1 In the E-UTRAN serving cell 3 In the source WLAN
o RSRPmeas < ThreshServingOffloadWLAN, o ChannelUtilizationWLAN > ThreshChUtilWLAN,
LowP; High;
o RSRQmeas < ThreshServingOffloadWLAN, o BackhaulRateDlWLAN <
LowQ; ThreshBackhRateDLWLAN, Low;
2 In the target WLAN o BackhaulRateUlWLAN <
o ChannelUtilizationWLAN < ThreshChUtilWLAN, ThreshBackhRateULWLAN, Low;
Low; o BeaconRSSI < ThreshBeaconRSSIWLAN, Low;
o BackhaulRateDlWLAN > 4 In the target E-UTRAN cell
ThreshBackhRateDLWLAN, High; o RSRPmeas > ThreshServingOffloadWLAN,
o BackhaulRateUlWLAN > HighP;
ThreshBackhRateULWLAN, High; o RSRQmeas > ThreshServingOffloadWLAN,
o BeaconRSSI > ThreshBeaconRSSIWLAN, High; HighQ;
Access network selection and traffic steering trigger when the following
conditions, indicated in table above, are met for a time interval TsteeringWLAN:
• If conditions 1 and 2 are met during TsteeringWLAN, then steering traffic
from EUTRAN to WLAN.
• If conditions 3 and 4 are met during TsteeringWLAN, then steering traffic
from WLAN to EUTRAN.
Table below outlines the parameters necessity status for RAN and ANDSF rules,
respectively. These parameters are operator-configurable.
Parameters in SIB17 RAN Rule Necessity Release 12 ANDSF Rule Necessity
3GPP access threshold Mandatory Optional
WLAN access threshold Mandatory Optional
OPI N/A Optional
WLAN AP ID list Mandatory N/A
TsteeringWLAN Mandatory N/A
SYSTEM OPERATION
How to Activate
Confidential
Preconditions
• Run CHG-SIB-INF and set SIB17PERIOD other than NOT_USED to
activate SIB17.
• Run CHG-SIB-INF and set SIB17PERIOD to NOT_USED to disable/
deactivate SIB17.
Key Parameters
To activate or deactivate the feature, or retrieve information run the associated
commands and set the key parameters.
Parameter Descriptions of CHG-SIB-INF/RTRV-SIB-INF
SIB17PERIOD This parameter is the transmission period for the system information block
type 17 of each cell in eNB. It can also control whether to transmit SIB17 or
not. SIB17 contains information relevant for traffic steering between E-
UTRAN and WLAN.
• ms80: 80 ms.
• ms160: 160 ms.
..
• ms5120: 5120 ms.
Run the associated commands to set the key parameters.
Parameter Descriptions of CHG-WLOFFLOAD-INF/RTRV-WLOFFLOAD-INF
CELL_NUM Cell number
PLMN_IDX PLMN index
WLAN_OFFLOAD_CONFIG_ This parameter is usage status of the WLANoffloadConfigCommon in SIB17.
COMMON_USAGE
THRESHOLD_RSRP_USAGE This parameter is usage status of the thresholdRSRP in SIB17.
THRESHOLD_RSRP_LOW This parameter indicates the RSRP threshold (in dBm) used by the UE for
traffic steering to WLAN. Parameter: ThreshServingOffloadWLAN, LowP in TS 36.304
THRESHOLD_RSRP_HIGH This parameter indicates the RSRP threshold (in dBm) used by the UE for
traffic steering to E-UTRAN. Parameter: ThreshServingOffloadWLAN, HighP in TS
36.304

Confidential
THRESHOLD_RSRQ_USAGE This parameter is usage status of the thresholdRSRQ in SIB17.
THRESHOLD_RSRQ_LOW This parameter indicates the RSRQ threshold (in dB) used by the UE for
traffic steering to WLAN. Parameter: ThreshServingOffloadWLAN, LowQ in TS 36.304
THRESHOLD_RSRQ_HIGH This parameter indicates the RSRQ threshold (in dB) used by the UE for
traffic steering to E-UTRAN. Parameter: ThreshServingOffloadWLAN, HighQ in TS
36.304
THRESHOLD_RSRQ_WB_LO This parameter indicates the RSRQ threshold (in dB) used by the UE for
W traffic steering to WLAN. Parameter: ThreshServingOffloadWLAN, LowQ in TS 36.304
The field is mandatory present in SIB17 if q-QualMinWB-r11 is present in
SIB1 and thresholdRSRQ-r12 is present in SIB17; otherwise, it is not
present.
THRESHOLD_RSRQ_WB_HI This parameter indicates the RSRQ threshold (in dB) used by the UE for
GH traffic steering to E-UTRAN. Parameter: ThreshServingOffloadWLAN, HighQ in TS
36.304
The field is mandatory present in SIB17 if q-QualMinWB-r11 is present in
SIB1 and thresholdRSRQ-r12 is present in SIB17; otherwise it is not present.
THRESHOLD_CHANNEL_UTI This parameter is usage status of the WLAN channel utilization (BSS load)
LIZATION_USAGE threshold in SIB17.
THRESHOLD_CHANNEL_UTI This parameter indicates the WLAN channel utilization (BSS load) threshold
LIZATION_LOW used by the UE for traffic steering to WLAN. Parameter: ThreshChUtilWLAN, Low
in TS 36.304
THRESHOLD_CHANNEL_UTI This parameter indicates the WLAN channel utilization (BSS load) threshold
LIZATION_HIGH used by the UE for traffic steering to E-UTRAN. Parameter: ThreshChUtilWLAN,
High in TS 36.304
THRESHOLD_BH_BW_USAG This parameter is usage status of the backhaul available bandwidth

E threshold in SIB17.
THRESHOLD_BH_DL_BW_L This parameter indicates the backhaul available downlink bandwidth
OW threshold used by the UE for traffic steering to E-UTRAN. Parameter:
ThreshBackhRateDLWLAN, Low in TS 36.304. Value in kilobits/second. Value rN
corresponds to N kbps.
THRESHOLD_BH_DL_BW_HI This parameter indicates the backhaul available downlink bandwidth
GH threshold used by the UE for traffic steering to WLAN. Parameter:
ThreshBackhRateDLWLAN, High in TS 36.304. Value in kilobits/second. Value rN
THRESHOLD_BH_UL_BW_L This parameter indicates the backhaul available uplink bandwidth threshold
OW used by the UE for traffic steering to E-UTRAN. Parameter:
ThreshBackhRateULWLAN, Low in TS 36.304. Value in kilobits/second. Value rN
THRESHOLD_BH_UL_BW_HI This parameter indicates the backhaul available uplink bandwidth threshold
GH used by the UE for traffic steering to WLAN. Parameter:
ThreshBackhRateULWLAN, High in TS 36.304 [4]. Value in kilobits/second. Value rN
THRESHOLD_WLAN_RSSI_U This parameter is usage status of the WLAN RSSI threshold in SIB17.
SAGE
THRESHOLD_WLAN_RSSI_L This parameter indicates the WLAN RSSI threshold used by the UE for traffic
OW steering to E-UTRAN. Parameter: ThreshWLANRSSI, Low in TS 36.304. Value 0
corresponds to -128 dBm, 1 corresponds to -127 dBm and so on.
THRESHOLD_WLAN_RSSI_H This parameter indicates the WLAN RSSI threshold used by the UE for traffic
IGH steering to WLAN. Parameter: ThreshWLANRSSI, High in TS 36.304. Value 0
corresponds to -128 dBm, 1 corresponds to -127 dBm and so on.
OFFLOAD_PREFERENCE_IN This parameter is usage status of the offload preference indicator in SIB17.
DICATOR_USAGE

Confidential
OFFLOAD_PREFERENCE_IN This parameter indicates the offload preference indicator. Parameter: OPI in
DICATOR[2] TS 24.312. Only applicable to RAN-assisted WLAN interworking based on
ANDSF policies.
T_STREERING_WLAN_USAG This parameter is usage status of the t-SteeringWLAN in SIB17.
E
T_STREERING_WLAN This parameter indicates the timer value during which the rules should be
fulfilled before starting traffic steering between E-UTRAN and WLAN.
Parameter: TsteeringWLAN in TS 36.304. Only applicable to RAN-assisted
WLAN interworking based on access network selection and traffic steering
rules.
Parameter Descriptions of CHG-WLANID-CONF/RTRV-WLANID-CONF

PLMN_IDX PLMN index
WLAN_IDX This is index of the WLAN ID list.
WLAN_IDX_USAGE This parameter is usage status of the corresponding WLAN IDX.
SSID_USAGE This parameter is the usage status of SSID in SIB17.
SSID[32] Service Set Identifier (SSID) defined in IEEE 802.11-2012
BSSID_USAGE This parameter is the usage status of BSSID in SIB17.
BSSID[6] This is Basic Service Set Identifier (BSSID) defined in IEEE 802.11-2012.
HESSID_USAGE This parameter is the usage status of HESSID in SIB17.
HESSID[6] Homogenous Extended Service Set Identifier (HESSID) defined in IEEE
802.11-2012.
Counters and KPIs

with this feature.
REFERENCE
description; Stage 2. Release 12
Resource Control (RRC) protocol specification. Release 12
[3] 3GPP TS36.304 Evolved Universal Terrestrial Radio Access (E-UTRA); UE
Equipment Procedures in IDLE Mode. Release 12
[4] 3GPP TS24.312 ANDSF Policies. Release 12
Universal Terrestrial Radio Access Network. Release 12
[6] 3GPP TS23.402 Architecture enhancements for non-3GPP accesses. Release
12

Confidential

Confidential
LTE-SW0320, RRC Connection Management

INTRODUCTION
For a UE to access the LTE network, the RRC Connection Management feature
establishes RRC connection between the UE and an eNB. This feature performs
the following RRC procedures:
• RRC connection establishment: This procedure is used to establish a RRC
connection between the UE and the eNB.
• RRC connection reconfiguration: This procedure is used to setup, modify or
delete radio configuration of a RRC connection.
• RRC connection release: This procedure is used to release a RRC connection.
• RRC connection re-establishment: This procedure is used to re-establish a
RRC connection between the UE and the eNB.
BENEFIT
• An operator can provide radio connectivity to its subscribers within LTE
network.
• LTE users can have a radio connection with an eNB for LTE service.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
RRC connection management involves the following RRC procedures:
• RRC connection establishment
• RRC Connection Reconfiguration
• RRC connection release
• RRC connection re-establishment

Confidential
RRC Connection Establishment

The eNB performs the RRC connection establishment procedure based on the UE
request. The RRC connection establishment procedure is used for RRC connection
setup, and the eNB establishes signaling connection with the UE through this
procedure. When receiving the RRC connection request from the UE, the eNB
considers the current RRC connection configuration status to determine whether
RRC connection can be established. If it is possible, it allocates resources for
SRB1 (Signaling Radio Bearer) and sends them to the UE with the RRC
Connection Setup message. The UE responds to this message. When receiving the
RRC Connection Setup Complete message, it completes the RRC connection
establishment procedure and then performs subsequent procedures.
Figure below depicts the RRC connection establishment procedure.
The UE performs the following random access procedure with the eNB:
1 The UE transmits the RRC Connection Request message to the eNB.
The UE transmits the message from the Physical Channel PUSCH/Transport
Channel UL-SCH/Logical Channel CCCH using SRB0 in TM Mode.
2 The eNB determines whether RRC connection can be established. If RRC
connection can be established, the eNB transmit the RRC Connection Setup
message to the UE. Information required for SRB1 setup is included in this
message.
The eNB responds to UE with the message from the Physical Channel
PDSCH/Transport Channel DL-SCH/Logical Channel CCCH using SRB0 in
TM Mode (Transparent Mode).
If RRC connection cannot be established, the eNB transmit the RRC
Connection Reject message to the UE.
3 After setting up SRB1 according to the RRC Connection Setup message
received from the eNB, the UE responds with the RRC Connection Setup
Complete message.
The UE responds to the eNB with the message from the Physical Channel
PUSCH/Transport Channel UL-SCH/Logical Channel DCCH using SRB1 in
AM Mode (Acknowledged Mode).
The NAS message: Attach Request (ESM: PDN Connectivity Request) is
included in this message.
4 The eNB transmits the Initial UE message including the NAS message:
Attach Request (ESM: PDN Connectivity Request) received from the UE to
Confidential
the MME. A procedure to be followed depends on the MME’s operation.
RRC Connection Reconfiguration

The eNB performs the RRC connection reconfiguration procedure to set
up/change/release the radio configuration for controlling the connected UE. The
RRC connection reconfiguration procedure is used in various situations to set up
the call, to add the DRB, to change the radio resource configuration, to change the
measurement configuration, to change the security context, and so on.
Figure below depicts the RRC Connection Reconfiguration procedure for setting
up the E-RAB.
The eNB receives E-RAB Setup Request from the MME. The QoS information of
the E-RAB(s) to be added, an NAS message to be sent to the UE and
NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST are
included in the E-RAB Setup Request.
1 When receiving the E-RAB Setup Request from the MME, the eNB
determines whether new E-RAB(s) can be added. If it is possible, it
reallocates internal resources and transmits the RRC Connection
Reconfiguration to the UE.
Physical Channel PDSCH/Transport Channel DL-SCH/Logical Channel
DCCH using SRB1 in RLC AM Mode.
2 The UE sets up the additional DRB(s) specified by the RRC Connection
Reconfiguration and responds to the eNB with the RRC Connection
Reconfiguration Complete.
Physical Channel PUSCH/Transport Channel UL-SCH/Logical Channel UL
DCCH using SRB1 in RLC AM Mode.
3 The eNB responds to the MME with the E-RAB Setup response. The E-RAB
Setup response includes setup success/failure results for each E-RAB.
RRC Connection Release

The eNB performs RRC connection release procedures to release a call of the
connected UE, to redirect or to process the CSFB. When releasing the RRC
connection with the UE, the eNB transmits the RRC Connection Release message
to the UE. Then, the eNB releases the entire UE context.
Figure below depicts the RRC Connection Release procedure in case of the eNB
initiated UE context release.

Confidential
This procedure is made up of the following flows:

1 In case of eNB initiated UE context release procedure, the eNB transmits UE
Context Release request to the MME to request for call release. (for example,
Inactivity timer expired)
2 The MME transmits UE Context Release command to the eNB for S1
release.
3 The eNB transmits RRC Connection Release to the UE.
4 After performing the RRC Connection Release procedure with the UE, the
eNB responds to the MME with UE Context Release Complete.
Apart from the eNB initiated UE context release, the RRC connection can be
released when:
• The inactivity timer of UE expires. For UEs in RRC_CONNECTED mode, the
eNB monitors both signaling inactivity time and user data inactivity time, and
it triggers RRC Connection Release procedures when both inactivity timers are
expired. Both the timers are configurable. For more details, see LTE-SW0325,
User Inactivity timer Control.
• The eNB detects a failure of the S1 connection. The S1 connection failure
occurs when the eNB cannot communicate with the MME of the UE for a
certain period or when the eNB does not receive an ECHO Response message
for the SGW of the UE for a certain period. When the eNB detects the failure
in the connection with MME or SGW, the eNB releases all the UEs that have
S1 connection with the MME or the SGW.
RRC Connection Reestablishment

The eNB performs the RRC connection reestablishment procedure upon the UE’s
request to re-setup the RRC connection. This procedure is triggered upon detecting
Radio Link Failure (RLF), handover failure, mobility from E-UTRA failure,
integrity check failure from lower layers and upon RRC Connection
Reconfiguration failure.
The RRC connection reestablishment procedure helps to re-establish the SRB1
operation and re-activate the Security Algorithms (Security Algorithms are not
changed). This procedure is successful when eNB has a valid UE Context. If the
eNB does not have a UE context, then the UE moves to RRC IDLE state.

Confidential
Figure below depicts the RRC connection re-establishment procedure.
The UE performs the Random access procedure with the eNB for RRC connection
reestablishment.
1 The UE transmits the RRC Connection Reestablishment Request message to
the eNB.
2 The eNB checks whether the UE has the UE context. If it has the UE context,
the eNB transmits the RRC Connection Reestablishment message to the UE.
The information required for SRB1 setup and AS security context restoration
is included in this message. If RRC connection re-establishment is not
possible, the eNB transmit the RRC Connection Reestablishment Reject
message to the UE.
3 The UE restores the SRB1 setup and AS security context according to the
RRC Connection Reestablishment message received from the eNB and
responds with the RRC Connection Reestablishment Complete message.
4 The eNB performs the RRC connection reconfiguration procedure with the
UE to set up the SRB2 and DRB.
SYSTEM OPERATION
How to Activate
Key Parameters
Run CHG-TIMER-INF/RTRV-TIMER-INF to change or retrieve the following
RRC connection management related parameters.
Parameter Descriptions of CHG-TIMER-INF/RTRV-TIMER-INF

Confidential
RRC_CONNECTION_SE The time to wait for reception of the RrcConnectionSetupComplete message after
TUP sending the RrcConnectionSetup message from the eNB to the UE.
RRC_CONNECTION_RE The time to wait for reception of the RrcConnectionRecofigurationComplete
CONFIG message after sending the RrcConnectionRecofig message from the eNB to the
UE.
RRC_CONNECTION_RE The time to wait for reception of the RrcConnectionReestablishmentComplete
_ESTABLISH message after sending the RrcConnectionReestablishment message from the
eNB to the UE.
INTERNAL_RRC_RESET The time to wait for multiple UEs to be released after sending the RrcConnection-
Release to the UEs at eNB reset.
INTERNAL_SOLICIT_ME The time to wait for reception of the Measurement Report message from the UE
ASUREMENT_REP ORT according to the Solicit Measurement Report procedure.
RRC_SECURITY_MODE The time to wait for reception of the SecurityModeComplete message after
_COMMAND sending the SecurityModeCommand message from the eNB to the UE.
RRC_UE_CAPABILITY_ The time to wait for reception of the UeCapabilityInformation message after
ENQUIRY sending the UeCapabilityEnquiry message from the eNB to the UE.
RRC_CONNECTION_RE The time to wait for reception of the message from the PDCB block confirming
LEASE that the RrcConnectionRelease message was successfully sent after sending it
from the eNB to the UE.
RRC_HANDOVER_PRE The time to wait for reception of the RrcUL-HandoverPreparationTransfer
PARATION message after sending the RrcHandoverFromEU-TRAPreparationRequest
message from the eNB to the UE.
RRC_UE_INFORMATIO The time to wait for reception of the InformationResponse message after sending
N_REQUEST the InformationRequest message from the eNB to the UE.
Run CHG-PLMNSIGTIMER-INFO/RTRV-PLMNSIGTIMER-INFO to change

or retrieve following Inactivity Timer related parameter.
Parameter Descriptions of CHG-PLMNSIGTIMER-INFO/RTRV-
PLMNSIGTIMER-INFO
INTERNAL_SIGNALING_ This parameter is the inactivity timer information for a signaling message. An eNB
INACTIVITY_TIMER starts an inactivity timer for a signaling message after a UE is attached. Signaling
inactivity is reinitialized if a signaling message containing NAS PDU information is
received from a UE or an MME.
Run CHG-INACT-INTER/RTRV-INACT-TIMER to change or retrieve

following Inactivity Timer related parameter.
Parameter Descriptions of CHG-INACT-INTER/RTRV-INACT-TIMER
INTERNAL_USER_INAC This parameter is the User inactivity timer value per QCI. A different User
TIVITY inactivity timer value can be set for each QCI by executing this command. As User
inactivity timer is closely related to call release, if possible, use the default value
without changing it. It is a timer that operates in seconds. If the operating User
inactivity timer value is 65535, a call may not be detached for 65535 seconds.
This may cause serious problems for the battery usage of the UE. It is
recommended to use a value less than 30 seconds. If the operator set the User
inactivity timer to 0, then the user inactivity timer is not set, so that the call release
function based on this timer expiration is deactivated.

Confidential
Counters and KPIs

RRC_ESTAB ConnEstabAtt RRC CONNECTION REQUEST count

ConnEstabSucc RRC CONNECTION SETUP COMPLETE count
ConnEstabFail_CP_CC_TO RRC connection Establishment fails due to call
control timeout in the protocol blocks (MAC, RLC,
PDCP, GTP)
ConnEstabFail_CP_CC_FAIL RRC connection Establishment fails due to reset
notification (eNB failure or block restart) from ECMB
or by the ECCB block
ConnEstabFail_UP_MAC_FAIL RRC connection Establishment fails due to the
failure in the MAC block
ConnEstabFail_UP_PDCP_FAIL RRC connection Establishment fails due to the
failure in the PDCP block
ConnEstabFail_UP_RLC_FAIL RRC connection Establishment fails due to the
failure in the RLC block
ConnEstabFail_RRC_SIG_TO RRC connection Establishment fails due to RRC
signaling timeout (not received)
ConnEstabFail_S1AP_LINK_FAI RRC connection Establishment fails due to the S1
L SCTP link failure
ConnEstabFail_S1AP_SIG_FAIL RRC connection Establishment fails due to receiving
S1AP signaling
ConnEstabReject_CP_CC_FAIL A call is rejected due to cell status (e.g. barred) or
MME status (e.g. no available MMEs) during the
RRC connection establishment
ConnEstabReject_CP_CAPA_C A call is rejected due to CAC during the RRC
AC_FAIL connection establishment
ConnEstabReject_S1AP_MME_ A call is rejected due to MME overload during the
OVLD RRC connection establishment
RRC_RECONFIG ConnReconfigAtt RRC CONNECTION RECONFIGURATION count
ConnReconfigSucc RRC CONNECTION RECONFIGURATION
COMPLETE count
RRC_REESTAB ConnReEstabAtt RRC CONNECTION REESTABLISHMENT
REQUEST count
ConnReEstabSucc RRC CONNECTION REESTABLISHMENT
COMPLETE count
ConnReEstabFail_CP_CC_FAIL RRC connection Re-establishment fails due to reset
notification (eNB failure or block restart) from ECMB
or by the ECCB block
ConnReEstabFail_UP_MAC_FAI RRC connection Re-establishment fails due to the
L failure in the MAC block
ConnReEstabFail_UP_PDCP_F RRC connection Re-establishment fails due to the
AIL failure in the PDCP block
ConnReEstabFail_UP_RLC_FAI RRC connection Re-establishment fails due to the

Confidential

L failure in the RLC block
ConnReEstabFail_RRC_SIG_TO RRC connection Re-establishment fails due to RRC
signaling timeout (not received)
ConnReEstabFail_S1AP_LINK_F RRC connection Re-establishment fails due to the
AIL S1 SCTP link failure
ConnReEstabFail_S1AP_SIG_F RRC connection Re-establishment fails due to
AIL receiving S1AP signaling
ConnReEstabReject_CP_CC_FA A call is rejected due to cell status (e.g. barred) or
IL MME status (e.g. no available MMEs) during the
RRC connection reestablishment
ConnReEstabReject_CP_CAPA_ A call is rejected due to Capacity based CAC during
CAC_FAIL the RRC connection reestablishment
ConnReEstabReject_CP_QOS_ A call is rejected due to Air QoS based CAC during
CAC_FAIL the RRC connection reestablishment
RRC_RELEASE ConnRelease_CP_CC_NORMAL Normal release
ConnRelease_CP_CC_TO A call is released due to call control timeout in the
protocol blocks (MAC, RLC, PDCP, GTP)
ConnRelease_CP_CC_FAIL A call is released due to reset notification (eNB
failure or block restart) from ECMB or by the ECCB
block
ConnRelease_UP_GTP_FAIL A call is released due to the failure in the GTP block
ConnRelease_UP_MAC_FAIL A call is released due to the failure in the MAC block
ConnRelease_UP_MAC_UE_IN A call is released due to user inactivity
ACT
ConnRelease_UP_PDCP_FAIL A call is released due to the failure in the PDCP
block
ConnRelease_UP_RLC_FAIL A call is released due to the failure in the RLC block
ConnRelease_RRC_HC_TO A call is released due to HO preparation timeout (not
received HO command)
ConnRelease_RRC_SIG_FAIL A call is released due to receiving RRC signaling
ConnRelease_RRC_SIG_TO A call is released due to RRC signaling timeout (not
received)
ConnRelease_CP_BH_CAC_FAI A call is released due to Backhaul QoS based CAC
L
ConnRelease_CP_CAPA_CAC_ A call is released due to Capacity based CAC
FAIL
ConnRelease_CP_QOS_CAC_F A call is released due to Air QoS based CAC
AIL
ConnRelease_S1AP_CU_FAIL A call is released due to the S1AP specification
cause
ConnRelease_S1AP_LINK_FAIL A call is released due to the S1 SCTP link failure
ConnRelease_S1AP_RO_TO A call is released due to the S1AP relocoverall
timeout (not received)

Confidential
ConnRelease_S1AP_SIG_FAIL A call is released due to receiving S1AP signaling

ConnRelease_S1AP_SIG_TO A call is released due to S1AP signaling timeout (not
received)
ConnRelease_X2AP_CU_FAIL A call is released due to the X2AP specification
cause
ConnRelease_X2AP_LINK_FAIL A call is released due to the X2 SCTP link failure
ConnRelease_X2AP_RO_TO A call is released due to the X2AP relocoverall
ConnRelease_X2AP_SIG_FAIL A call is released due to receiving X2AP signaling
RRC_CONN ConnNo Average number of RRC connections during a time
period
ConnMax Maximum number of RRC connections during a time
period
ConnTot Summation of the collected ConnNo
ConnCnt Count of the collected ConnNo
ReleaseCallHoldingTime Average holding time of RRC connection.
This is collected when a call is released.
ReleaseCallHoldingTimeTot Summation of the collected ReleaseCallHoldingTime
ReleaseCallCnt Call Release Count
RRC_CONN_PLMN ConnNo_PLMN Average number of RRC connections per PLMN
during a time period
ConnMax_PLMN Maximum number of RRC connections per PLMN
during a time period
ConnTot_PLMN Summation of the collected ConnNo_PLMN
ConnCnt_PLMN Count of the collected ConnNo_PLMN
RRC_TIME ConnEstabTime Average RRC Connection setup time
ConnEstabTimeMax Maximum RRC Connection setup time
ConnEstabTimeTot Summation of the collected ConnEstabTime
ConnEstabTimeCnt Count of the collected ConnEstabTime
RRC_RESETUP_TIME ConnReEstabTime Average RRC Connection reestablishment time
ConnReEstabTimeMax Maximum RRC Connection reestablishment time
ConnReEstabTimeTot Summation of the collected ConnReEstabTime
ConnReEstabTimeCnt Count of the collected ConnReEstabTime
CALL_DROP CallDrop_ECCB_DSP_AUDIT_R Call drop (abnormal release) count due to no call in
LC_MAC_CALL_RELEASE RLC and MAC block
CallDrop_ECCB_RCV_RESET_ Call drop (abnormal release) count due to reset
REQUEST_FROM_ECMB request from ECMB
CallDrop_ECCB_RCV_CELL_RE Call drop (abnormal release) count due to cell
LEASE_IND_FROM_ECMB release indication from ECMB

Confidential
CallDrop_ECCB_RADIO_LINK_F Call drop (abnormal release) count due to radio link

AILURE failure
CallDrop_ECCB_DSP_AUDIT_M Call drop (abnormal release) count due to no call in
AC_CALL_RELEASE MAC block
CallDrop_ECCB_ARQ_MAX_RE Call drop (abnormal release) count due to ARQ
_TRANSMISSION failure (no ACK is received after maximum
retransmission)
CallDrop_ECCB_DSP_AUDIT_R Call drop (abnormal release) count due to no call in
LC_CALL_RELEASE RLC block
CallDrop_ECCB_TMOUT_rrcCon Call drop (abnormal release) count due to RRC
nectionReconfig signaling timeout (not received) during the RRC
Connection Reconfiguration
CallDrop_ECCB_TMOUT_rrcCon Call drop (abnormal release) count due to RRC
nectionReEstablish signaling timeout (not received) during the RRC
Connection Reestablishment
CallDrop_ECCB_S1_SCTP_OUT Call drop (abnormal release) count due to S1 failure
_OF_SERVICE
REFERENCE

Confidential
LTE-SW0321, UE Context Management

INTRODUCTION
The eNB maintains UE contexts while the UEs are in the RRC_CONNECTED
state, and supports Initial Context Setup, UE Context Release, and Modification
according to requests from the MME.
BENEFIT
An operator can maintain UE context for its subscribers in the
RRC_CONNECTED state.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Initial Context Setup

The eNB performs Initial Context Setup procedure when it receives INITIAL
CONTEXT SETUP REQUEST message from MME. Initial Context Setup
procedure is used for call setup. The eNB creates UE context for the UE so that it
can process UE associated signaling and data transmission/reception. On receiving
INITIAL CONTEXT SETUP REQUEST message from MME, eNB determines
whether the call setup is possible or not, based on the status of resources at that
moment. If there is available resource, eNB performs RRC Connection
Reconfiguration procedures with the UE for resource reconfiguration and transmits
INITIAL CONTEXT SETUP RESPONSE to the MME, according to 3GPP
TS36.413. The Initial Context Setup procedure includes E-RAB setup procedure.
In figure below, UE initiated Service Request triggers Initial Context Setup
procedure.

Confidential
The UE performs the following random access and RRC connection establishment
procedures with eNB for call setup:
1 The eNB transmits the Initial UE message to the MME to establish the
connection. The NAS message including SERVICE REQUEST received
from the UE is included in this message.
o The eNB uses the eNB-UE-S1AP-ID to uniquely identify the UE
o The UE Identity is specified is IMSI (If the UE is not registered with the
network) and Old GUTI (Subsequent attach requests identify the UE with
the Old GUTI).
2 If necessary, the NAS security setup or authentication procedures are
performed.
3 The MME transmits the Initial Context Setup request message to the eNB.
Information required for E-RAB(s) setup, UE contexts required by the eNB
to control the UE, the NAS message including SERVICE ACCEPT to be sent
to the UE are included in the Initial Context Setup request.
o S1AP: Initial Context Setup Request message contains a request to
establish a context between MME and eNB and the message containing
SGW tunneling information.
o NAS: Attach Accept Message acknowledges the successful Attach to the
UE, the eNB forwards this message to the UE.
Confidential
o NAS: Activate Default Bearer Request Message initiates the default bearer
setup on the UE and the eNodeB will pass this message to the UE.
4 The eNB determines whether the call can be setup based on the information
received from the MME. If possible, it performs the AS security activation
procedure with the UE.
5 The eNB reallocates internal resources for DRBs setup and transmits RRC
Connection Reconfiguration to the UE.
6 The UE sets up the additional DRBs specified by RRC Connection
Reconfiguration and responds to the eNB with RRC Connection
Reconfiguration Complete.
7 The eNB responds to the MME with the Initial Context Setup response. Setup
success/failure results for each E-RAB are included in the Initial Context
Setup response. If eNB detects a failure in the path to the S-GW, it responds
to the MME with Initial Context Setup Failure message.
o This message confirms the establishment of the GTP tunnel on the S1-U
Interface.
o The message contains information about the E-RABs that are being
established at startup.
o Each E-RAB will have an E-RAB ID, transport layer IP address on the
eNB and eNB GTP Tunneling ID (TEID) for the eNB side.
8 The MME performs the Bearer Modify procedure with the S-GW/P-GW.
When the path between eNB and Serving GW is in failure state, eNB responds
with INITIAL CONTEXT SETUP FAILURE message instead of INITIAL
CONTEXT SETUP RESPONSE message. It makes MME to disconnect the call of
the UE.
UE Context Modification
The eNB performs the UE context modification procedure upon the MME’s
request.
It can change the security context, UE AMBR and SPID through the UE context
modification procedure. When receiving the UE Context Modification request
from the MME, the eNB changes the UE context using the value included in the
message and transmits the UE Context Modification response to the MME. If the
security context was changed, it performs the RRC Connection Reconfiguration
procedure with the UE and then responds to the MME.
It uses the UE context modification procedure to change the UE context of the
connected UE. The following UE contexts can be changed through the UE context
modification procedure:
• UE Aggregate Maximum Bit Rate (UE AMBR)
• UE Security Capabilities
• Security Key
• Subscriber Profile ID for RAT/Frequency priority (SPID)

Confidential
• CSG Membership Status

• Registered LAI
Figure below depicts the UE context modification procedure.
In case of the HSS initiated UE context modification procedure, the HSS performs
the subscriber data modification procedure with the MME.
1 If UE context modification is required, the MME transmits the Context
Modification request to the eNB.
2 The eNB changes the UE context based on the information included in the
UE Context Modification Request message and transmits the UE Context
Modification Response message to the MME. If the security context was
changed, it performs the RRC Connection Reconfiguration procedure with
the UE and then responds to the MME.
UE Context Release
The eNB performs the UE context release procedure upon the MME’s request. The
UE context release procedure is used for releasing a call from the connected UE.
The MME initiated UE context release is performed based on the MME decision
or the eNB initiated UE context release is performed upon the request from the
eNB. When receiving the UE Context Release Command message from the MME,
the eNB performs the RRC Connection Release procedure with the UE and then
transmits the UE Context Release Complete message to the MME.
The UE context release procedure is used for call release (RRC_Connected to
RRC_IDLE transition).
Figure below depicts the UE context release procedure.

Confidential
In case of the eNB initiated UE context release procedure, the eNB transmits the
UE Context Release request to the MME to request for call release.
1 If S1 release is necessary, the MME performs the Release Access Bearer
procedure with the S-GW.
2 The MME transmits the UE Context Release command to the eNB for S1
release.
3 The eNB transmits RRC Connection Release to the UE.
4 The eNB performs the RRC Connection Release procedure with the UE and
then responds to the MME with the UE Context Release Complete.
SYSTEM OPERATION
How to Activate
Key Parameters
To configure the security algorithm, run the associated command and set the key
parameters.
Parameter Descriptions of CHG-SECU-INF/RTRV-SECU-INF
INTEGRITY_EA_PRI The integrity protection algorithm supported by the eNB.
OR • EIA0: NULL
• EIA1: SNOW 3G
• EIA2: AES

Confidential
CIPHER_EA_PRIOR The ciphering algorithm supported by the eNB.
• EEA0: NULL
• EEA1: SNOW 3G
• EEA2: AES
Counters and KPIs

ERAB_ESTAB EstabInitAttNbr INITIAL CONTEXT SETUP REQUEST count

EstabInitSuccNbr INITIAL CONTEXT SETUP RESPONSE count
ErabInitFailNbr_CP_CC_TO Initial E-RAB setup fails due to call control
timeout in the protocol blocks (MAC, RLC,
PDCP, GTP)
ErabInitFailNbr_CP_CC_FAIL Initial E-RAB setup fails due to reset
notification (eNB failure or block restart) from
ECMB or by the ECCB block
ErabInitFailNbr_UP_GTP_FAIL Initial E-RAB setup fails due to the failure in
the GTP block
ErabInitFailNbr_UP_MAC_FAIL Initial E-RAB setup fails due to the failure in
the MAC block
ErabInitFailNbr_UP_ PDCP_FAIL Initial E-RAB setup fails due to the failure in
the PDCP block
ErabInitFailNbr_UP_RLC_FAIL Initial E-RAB setup fails due to the failure in
the RLC block
ErabInitFailNbr_RRC_ SIG_FAIL Initial E-RAB setup fails due to receiving RRC
signaling
ErabInitFailNbr_RRC_ SIG_TO Initial E-RAB setup fails due to RRC signaling
ErabInitFailNbr_CP_BH_CAC_FAIL Initial E-RAB setup fails due to Backhaul QoS
based CAC
ErabInitFailNbr_CP_ Initial E-RAB setup fails due to Capacity based
CAPA_CAC_FAIL CAC
ErabInitFailNbr_CP_QOS_CAC_FAIL Initial E-RAB setup fails due to Air QoS based
CAC
ErabInitFailNbr_S1AP_ CU_FAIL Initial E-RAB setup fails due to the S1AP
specification cause
ErabInitFailNbr_S1AP_ LINK_FAIL Initial E-RAB setup fails due to the S1 SCTP
link failure
ErabInitFailNbr_S1AP_ SIG_FAIL Initial E-RAB setup fails due to receiving S1AP
signaling
ERAB_ERASE_ENB EraseAttbyEnb_CP_CC_TO eNB initiated UE Context Release fails due to
call control timeout in the protocol blocks
(MAC, RLC, PDCP, GTP)

Confidential
EraseAttbyEnb_CP_CC_FAIL eNB initiated UE Context Release fails due to

reset notification (eNB failure or block restart)
from ECMB or by the ECCB block
EraseAttbyEnb_UP_GTP_FAIL eNB initiated UE Context Release fails due to
the failure in the GTP block
EraseAttbyEnb_UP_MAC_FAIL eNB initiated UE Context Release fails due to
the failure in the MAC block
EraseAttbyEnb_UP_MAC_UE_INACT eNB initiated UE Context Release fails due to
user inactivity
EraseAttbyEnb_UP_ PDCP_FAIL eNB initiated UE Context Release fails due to
the failure in the PDCP block
EraseAttbyEnb_UP_RLC_FAIL eNB initiated UE Context Release fails due to
the failure in the RLC block
EraseAttbyEnb_RRC_HC_TO eNB initiated UE Context Release fails due to
HO preparation timeout (not received HO
command)
EraseAttbyEnb_RRC_SIG_FAIL eNB initiated UE Context Release fails due to
receiving RRC signaling
EraseAttbyEnb_RRC_SIG_TO eNB initiated UE Context Release fails due to
RRC signaling timeout (not received)
EraseAttbyEnb_S1AP_ CU_FAIL eNB initiated UE Context Release fails due to
the S1AP specification cause
EraseAttbyEnb_S1AP_ RO_TO eNB initiated UE Context Release fails due to
the S1AP relocoverall timeout (not received)
EraseAttbyEnb_S1AP_ SIG_TO eNB initiated UE Context Release fails due to
S1AP signaling timeout (not received)
EraseAttbyEnb_X2AP_ RO_TO eNB initiated UE Context Release fails due to
the X2AP relocoverall timeout (not received)
ERAB_ERASE EraseAtt UE CONTEXT RELEASE COMMAND count
EraseSucc UE CONTEXT RELEASE COMPLETE count
ERAB_TIME EstabTimeAvg Average time of Initial E-RAB set-up and
additional E-RAB setup
EstabTimeMax Max. time of Initial E-RAB set-up and
EstabTimeTot Total time of Initial E-RAB set-up and
EstabTimeCnt Counts of Initial E-RAB set-up and additional
E-RAB setup
ERAB_SESSION_UE SessionTimeUEAvg Average In-Session time
SessionTimeUETot Total In-Session time
SessionTimeUECnt Counts of In-session time
S1SIG S1ConnEstabAtt INITIAL UE MESSSAGE count
S1ConnEstabSucc INITIAL CONTEXT SETUP REQUEST count

Confidential
S1ConnEstabFail_CpCcFail S1 Connection Establishment fails due to reset

notification (eNB failure or block restart) from
ECMB or by the ECCB block
S1ConnEstabFail_S1apCuFail S1 Connection Establishment fails due to the
S1AP specification cause
S1ConnEstabFail_S1apLinkFail S1 Connection Establishment fails due to the
S1 SCTP link failure
S1ConnEstabFail_S1apSigFail S1 Connection Establishment fails due to
receiving S1AP signaling
S1ConnEstabFail_S1apSigTo S1 Connection Establishment fails due to
S1AP signaling timeout (not received)
REFERENCE
[3] 3GPP TS36. 413: Evolved Universal Terrestrial Access Network (E-UTRAN);
S1 Application Protocol (S1AP)

Confidential
LTE-SW0322, E-RAB Management

INTRODUCTION
E-RAB is a bearer connection between an eNB and a Serving GW. An MME
initiates E-RAB setup, modification and release procedures. And MME also can
request an eNB to modify E-RAB QoS characteristics. E-RAB Management
feature performs all those procedures according to 3GPP TS36.413.
This feature allows an eNB and an MME to setup an E-RAB connection so that the
eNB and the Serving GW transmit user packets uplink and downlink through GTP
tunnel. Each E-RAB bearer is distinguished by Tunnel Endpoint Identifier (TEID).
BENEFIT
Operators can provide EPS bearer service to their subscribers and manage E-RAB
resources for user data transport.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature has the following three main functions:
• E-RAB Setup
• E-RAB Modification
• E-RAB Release
E-RAB Setup
With this feature, the eNB can add E-RAB for a new service to a connected UE
through E-RAB setup procedure. When receiving the E-RAB setup request
message from MME, the eNB considers the current resource usage status and
determines whether the new bearer can be added. If the new E-RAB can be added,
the eNB performs the RRC Connection Reconfiguration procedure with the UE for
resource reconfiguration of the new DRB and transmits the E-RAB setup response
message to the MME.

Confidential
Each E-RAB includes an E-RAB ID, the transport layer IP address on the eNB, the
GTP TEID for the eNB side, the QCI to assign session priority, the maximum bit
rate for the E-RAB, and the guaranteed bit rate for the E-RAB.
Figure below depicts the E-RAB setup procedure.
1 The P-GW transmits the create bearer request to the S-GW to add the new E-
RAB.
2 The S-GW transmits the create bearer request to add the new E-RAB.
3 The MME transmits the E-RAB setup request to start the E-RAB setup
procedure. QoS information of the E-RABs to be added, the NAS message to
be sent to the UE, and Activate Dedicated EPS Bearer Context Request are
included in the E-RAB setup request.
4 When receiving the E-RAB setup request from the MME, the eNB
determines whether a new E-RAB can be added. If possible, the eNB
reallocates internal resources and transmits RRC Connection Reconfiguration
to the UE.
5 The UE adds the new DRB specified by RRC Connection Reconfiguration
and then replies to the eNB with RRC Connection Reconfiguration Complete.
6 The eNB responds to the MME with the E-RAB setup response. Setup
success/failure results for each E-RAB are included in the E-RAB setup
response.
7 The UE transmits the NAS message and Activate Dedicated EPS Bearer
Context Response.

Confidential
8 The eNB transmits the NAS received from the UE to the MME.
9 The MME transmits the create bearer response to the S-GW.
10 The S-GW transmits the create bearer response to the P-GW.
E-RAB Modification
With this feature, the eNB can change the QoS setting of a bearer (E-RAB) already
in service through E-RAB modification procedure. Using this procedure, you can
change UE AMBR for non-GBR bearer and E-RAB level QoS parameters (QCI,
ARP and GBR QoS information) for GBR bearer.
Figure below depicts the E-RAB modification procedure.
1 The P-GW transmits update bearer request to S-GW to change QoS setting.
2 The S-GW transmits update bearer request to MME to change QoS setting.
3 The MME starts the E-RAB modification procedure by transmitting E-RAB
Modify Request to the eNB. The E-RAB Modify Request has the QoS
information of E-RABs to change, NAS message to send to an UE, and
MODIFY EPS BEARER CONTEXT REQUEST.
4 When the eNB receives E-RAB modify request from the MME, it judges if it
is possible to change the QoS setting of the E-RABs. If possible, it re-
allocates internal resources and transmits RRC Connection Reconfiguration
to the MS.
5 The MS changes the QoS setting of DRBs that is specified in RRC
Connection Reconfiguration and replies RRC Connection Reconfiguration
Confidential
Complete to the eNB.

6 The eNB replies E-RAB modify response to the MME. The E-RAB modify
response has the success or failure of QoS setting change per E-RAB.
7 The UE transmits NAS message, Modify EPS Bearer Context Response.
8 The eNB transmits the NAS message received from the UE to the MME.
9 The MME transmits update bearer response to the S-GW.
10 The S-GW transmits update bearer response to the P-GW.
E-RAB Release
With this feature, the eNB can release specific bearer service of a connected UE
through E-RAB release procedure. This procedure is performed by MME of
requesting E-RAB Release Command (MME initiated E-RAB release) or MME
requests E-RAB release after receiving E-RAB Release Indication from eNB (eNB
initiated E-RAB release). When E-RAB Release Command message is received
from MME, the eNB performs RRC connection reconfiguration procedure with
UE to release the corresponding Data Radio Bearer (DRB). When the DRB is
released successfully, the eNB returns E-RAB Release response message to MME.
Figure below depicts E-RAB release procedure.

Confidential
1 If the eNB initiated E-RAB release procedure, the eNB transmits the E-RAB
release indication to the MME to notify the release of a specific E-RAB. The
MME transmits the Delete Bearer Command to the S-GW for E-RAB release.
2 The S-GW transmits the Delete Bearer command for E-RAB release. The P-
GW transmits the Delete Bearer Request to the S-GW for E-RAB release.
3 The S-GW transmits the Delete Bearer Request to the MME for E-RAB
release.
4 The MME initiates the E-RAB release procedure by transmitting the E-RAB
release command. IDs of the E-RABs to be released, the NAS message to be
sent to the UE, and Deactivate EPS Bearer Context Request are included in
the E-RAB release command.
5 When receiving the E-RAB release command from the MME, the eNB
transmits RRC Connection Reconfiguration to the UE.
6 The UE releases the DRBs specified by RRC Connection Reconfiguration
and then replies to the eNB with RRC Connection Reconfiguration Complete.
7 The eNB responds to the MME with the E-RAB release response.
8 The UE transmits the NAS message and Deactivate EPS Bearer Context
Response.
9 The eNB transmits the NAS received from the UE to the MME.
10 The MME transmits the delete bearer response to the S-GW.
11 The S-GW transmits the delete bearer response to the P-GW.
SYSTEM OPERATION
How to Activate
Preconditions
• For standard QCI E-RABs, this feature runs automatically, and it cannot be
disabled.
• For operator-specific QCIs, run CHG-QCI-VAL to equip new QCIs to be
used.
This feature does not need to be deactivated.

Confidential
Key Parameters
parameters.
Parameter Descriptions of CHG-QCI-VAL/RTRV-QCI-VAL
QCI QoS Class Identifier (QCI) index. The range is from 0 to 255. The QCI
defined in the standard is 1 to 9. The user can use QCI values 0 and 10-255.
STATUS Whether the QoS Class Identifier (QCI) is used:
• EQUIP: The QCI is used in the eNB.
• N_EQUIP: The QCI is not used in the eNB.
Parameter Descriptions of CHG-ENB-INF/RTRV-ENB-INF

ERAB_PROC_INTR_HO_EN This parameter is used to control the interworking of E-RAB management
ABLE procedures with coverage based handover events.
• Off: E-RAB modification procedure continues and Handover event (MR
from UE) is ignored, if eNB receives MR from UE while E-RAB procedure is
going on.
• On: Handover procedure is processed and ongoing E-RAB procedure is
failed, if Handover event is triggered before sending RRC Connection
Reconfiguration during E-RAB procedure.
Counters and KPI

ERAB_ESTAB_ADD EstabAddAttNbr E-RAB setup request count.
EstabAddSuccNbr E-RAB setup response count.
ErabAddFailNbr_CP_CC_TO E-RAB setup fails due to call control
timeout in the protocol blocks (MAC,
RLC, PDCP, and GTP).
ErabAddFailNbr_CP_CC_FAIL E-RAB setup fails due to reset
notification (eNB failure or block restart)
from ECMB or by the ECCB block.
ErabAddFailNbr_UP_GTP_FAIL E-RAB setup fails due to the failure in
the GTP block.
ErabAddFailNbr_UP_MAC_FAIL E-RAB setup fails due to the failure in
the MAC block.
ErabAddFailNbr_UP_PDCP_FAIL E-RAB setup fails due to the failure in
the PDCP block.
ErabAddFailNbr_UP_RLC_FAIL E-RAB setup fails due to the failure in
the RLC block.
ErabAddFailNbr_RRC_SIG_FAIL E-RAB setup fails due to receiving RRC
signaling.

Confidential

ErabAddFailNbr_RRC_SIG_TO E-RAB setup fails due to RRC signaling
timeout (not received).
ErabAddFailNbr_CP_BH_CAC_F E-RAB setup fails due to backhaul QoS
AIL based CAC.
ErabAddFailNbr_CP_CAPA_CAC E-RAB setup fails due to capacity-based
_FAIL CAC.
ErabAddFailNbr_CP_QOS_CAC_ E-RAB setup fails due to air QoS-based
FAIL CAC.
ErabAddFailNbr_S1AP_CU_FAIL E-RAB setup fails due to the S1AP
specification cause.
ErabAddFailNbr_S1AP_LINK_FAI E-RAB setup fails due to the S1 SCTP
L link failure.
ErabAddFailNbr_S1AP_SIG_FAIL E-RAB setup fails due to receiving
S1AP signaling.
ErabAddFailNbr_CP_CC_INTER E-RAB setup fails due to ongoing inter-
ACTION eNB handover.
ERAB_REL_ENB RelAttbyEnbNbr_CP_CC_TO eNB initiated E-RAB Release fails due
to call control timeout in the protocol
blocks (MAC, RLC, PDCP, and GTP).
RelAttbyEnbNbr_S1AP_CU_FAIL eNB initiated E-RAB Release fails due
to the S1AP specification cause.
ERAB_REL RelAttNbr E-RAB release command count.
RelSuccNbr ERAB release response count.
RelFailNbr_CP_CC_FAIL MME initiated E-RAB Release fails due
to reset notification (eNB failure or block
restart) from ECMB or by the ECCB
block.
RelFailNbr_S1AP_SIG_FAIL MME initiated E-RAB Release fails due
to receiving S1AP signaling.
RelFailNbr_S1AP_CU_FAIL MME initiated E-RAB Release fails due
to the S1AP specification cause.
RelActive Number of active E-RABs abnormally
released by eNB.
RelFailNbr_CP_CC_INTERACTI MME initiated E-RAB Release fails due
ON to ongoing inter-eNB handover.
RelActive_ECCB_RADIO_LINK_ Number of active E-RABs abnormally
FAIL released by eNB in case of radio link
fail.
RelActive_ECCB_ARQ_MAX_Re Number of active E-RABs abnormally
Transmission released by eNB in case of ARQ MAX
Retransmission.
RelActive_ECCB_TM_OUT_RRC Number of active E-RABs abnormally
_CONNECTION_RECONFIG released by eNB in case of time out
RRC Connection Reconfiguration.
RelActive_ECCB_TM_OUT_RRC Number of active E-RABs abnormally
_CONNECTION_REESTABLISH released by eNB in case of time out
RRC connection reestablishment.
ERAB_NUM UsageNbr Average number of E-RABs during a
period.

Confidential

UsageNbrMax Maximum number of E-RABs during a
period.
REFERENCE
[3] 3GPP TS36. 413 Evolved Universal Terrestrial Access Network (E-UTRAN);

Confidential
LTE-SW0325, User Inactivity Timer Control

INTRODUCTION
The User Inactivity Timer Control feature allows an eNB to set inactivity timer for
signaling data of an UE. When the timer expires, this feature releases the UE so
that the UE that has no long time traffic does not occupy resources in the active
status.
BENEFIT
An operator can optimize the system utilization by changing the user inactivity
timer. A longer inactivity timer allows UEs to keep their connections longer even
though there is no traffic flow over them, which reduces the amount of signaling
messages between network elements such as UE, eNB and EPC. On the other
hand, a shorter inactivity timer increases the number of UEs that the cell can serve
under the coverage.
DEPENDENCY
Others: The value of the inactivity timer may affect the KPI. As the timer value is
lower, resource efficiency is higher, but the UE is often released so that its
experience quality may become worse. If the timer value is higher, resource
efficiency is lower, but the UE is released in a rare occasion when the timer value
is low so that its experience quality may become better. If Inactivity timer is
disabled, the UE battery consumption becomes higher and resource efficiency
becomes lower.
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
The value of inactivity timer may affect resource efficiency and UE battery
consumption (for more details, see DEPENDENCY section).
Coverage
None
Interfaces
None
Confidential
FEATURE DESCRIPTION
With this feature, the eNB can control the inactivity timer of the signaling and user
data. It supports the following control functions:
• Inactivity Timer Start
• Inactivity Timer Reset/Initialization
• Inactivity Timer Stop
• Inactivity Timer Expiry
Inactivity Timer Start

Figure below depicts the inactivity timer control during RRC Connection Setup
procedure.

1 The eNB receives the RRC Connection Request from the UE.
2 The eNB transmits the RRC Connection Setup message to the UE.
3 If the eNB receives the RRC Connection Setup Complete message, the
signaling inactivity timer is started depending on
INTERNAL_SIGNALING_INACTIVITY_TIMER (CHG-
PLMNSIGTIMER-INFO) parameter. At this time, the User Data Inactivity
timer is set to the status of expired.
Starting point of signaling Inactivity timer starts at Service Request or Initial
Attach procedure is as follows:
If eNB receives Initial Context Setup Request message, it stops signaling
Inactivity timer stops. And eNB starts signaling Inactivity timer on reception
of RRC Connection Reconfiguration Complete.
Except for the above case, current operation for signaling Inactivity timer is

Confidential
retained.
4 If the uplink user data or downlink user data of the UE is transmitted and
received, the user data inactivity timer is started depending on
INTERNAL_USER_INACTIVITY (CHG-INACT-TIMER).
Inactivity Timer Reset/Initialization

When the RRC connection setup is completed, the eNB can control inactivity
timers as follows:
Signaling Inactivity Timer Control
If the signaling message specified by the UE or MME is received, then it resets the
signaling inactivity timer for the UE and initializes the existing set timer value for
new start.
User Data Inactivity Timer Control
If the eNB receives the user data of the UE, it stops the user data inactivity timer
for the UE and completes transmitting the user data. At this point, the user data
inactivity timer of the UE is initialized than being restarted.
Inactivity Timer Stop

The eNB stops the signaling inactivity timer and user data inactivity timer
corresponding to the UE after transmitting the RRC Connection Release message
to the UE. This process is the same as general resource collecting process.
Inactivity Timer Expiry

The eNB determines the UE is in the inactive status when the signaling inactivity
timer and user data inactivity timer expire. Then the eNB transmits the S1AP UE
Context Release Request message to the MME by performing the UE context
release procedure. (Cause value: user inactivity) The RRC connection
corresponding to the UE is released later.
Figure below depicts an overall message flow when the inactivity timer expires.

Confidential
1 When there is no user data between the eNB and the UE for a certain period,
the user data inactivity timer expires.
2 When there is no specified signaling message between the eNB and UE for a
certain period, the signaling inactivity timer expires.
3 If the signaling inactivity timer and user data inactivity timer expire, the eNB
releases the call by performing the UE context release procedure.
Inactivity Timer Procedure with Intra-LTE Handover

With this feature, the eNB control inactivity timer when intra-LTE handover
performs.
Calculating UE-InactiveTime IE
Calculation of the remaining timer at each stage is as follows:
[ue-InactiveTime IE calculation method]
ue-InactiveTime = MAX (Init.Signaling Inactivity Timer, Init.User Data Inactivity Timer)-MAX (Remaining
Signaling Inactivity Timer, Remaining User Data Inactivity Timer)
Remaining Signaling Inactivity Timer = Init. Signaling Inactivity Timer-ue-InactiveTime IE
Remaining User Data Inactivity Timer = Init. User Data Inactivity Timer-ue-InactiveTime IE
If the value of the Remaining Signaling Inactivity Timer or Remaining User Data
Inactivity Timer is 0 or less, the timer is considered as expired.
X2 Handover
Figure below depicts the inactivity timer procedure during X2 handover.

Confidential
1 The eNB receives the Measurement Report message from the UE and
determines the handover.
2 The source eNB calculates the UE-InactiveTime according to the operation of
the inactivity timer.
3 The source eNB transmits the UE-InactiveTime to the target eNB through the
X2AP Handover Request message.
4 The target eNB calculates and saves the remaining signaling inactivity time
and remaining user data inactivity time according to the operation of the
target eNB inactivity timer after receiving the X2AP Handover Request
message. At this point, the target eNB does not immediately run the user data
inactivity timer, but waits.
5 The target eNB separately runs the user data timer and signaling timer after
receiving the RRC Connection Reconfiguration Complete message.
S1 Handover
Figure below depicts the inactivity timer procedure during S1 handover.

1 The source eNB determines the handover after receiving the Measurement
Report message from the UE and calculates the ue-InactiveTime according to
the operation of the inactivity timer.
2 The source eNB transmits the ue-InactiveTime to the target eNB via the

Confidential
MME through the S1 handover procedure.

3 The target eNB calculates and saves the remaining signaling inactivity time
and remaining user data inactivity time according to the operation of the
target eNB inactivity timer after receiving the S1AP Handover Request
message. At this point, the target eNB does not start the user data timer, but
waits.
4 The target eNB separately runs the user data timer and signaling timer after
receiving the RRC Connection Reconfiguration Complete message.
Load Shedding using Inactivity Time Adjustment

The eNB periodically check if the number of RRC connected UE reaches the
threshold of triggering load shedding condition based on
UEOVERLOAD_TRIGGER (CHG-LSHD-CONF). The eNB selects candidate UEs
with non-GBR bearer to reduce Inactivity timer, and then eNB applies new
reduced Inactivity timer for the candidate UEs. The candidate UEs with non-GBR
bearer and reduced Inactivity timer are utilized by
UECANDIDATE_LOAD_SHEDDING,
LOAD_SHED_SIG_INACT_TIMER_RATIO, and
LOAD_SHED_DATA_INACT_TIMER_RATIO (CHG-LSHD-CONF).
The eNB repeats the operation depicted above periodically until the total number
of UEs in RRC Connected mode becomes below the threshold of exiting load
shedding condition.
New UE Existing UE Existing UE eNB
Idle to Active completion
If RRC Connected UE >

Threshold, Select UEs to
change inactivity Timer and
then Change Inactivity Timer.
RRC Connection
Release
If both Signaling
Inactivity Timer and
RRC Connection Release User Inactivity Timer
are expiry
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
• Run CHG-INACT-TIMER and set INTERNAL_USER_INACTIVITY to
larger than 0 to enable the user inactivity timer for target PLMN_IDX and
QCI.
• For target PLMN_IDX and QCI, run CHG-INACT-TIMER and set
INTERNAL_USER_INACTIVITY to 0 to disable the user inactivity timer.
Key Parameters
parameter.
Parameter Descriptions of CHG-INACT-TIMER/RTRV-INACT-TIMER
INTERNAL_USER_IN This parameter is the User inactivity timer value per QCI. A different User inactivity
ACTIVITY timer value can be set for each QCI by executing this command. As User inactivity
timer is closely related to call release, if possible, use the default value without
changing it. This timer operates in seconds. If the operating User inactivity timer
value is 65535, a call may not be detached for 65535 seconds. This may cause
serious problems for the battery usage of the UE. It is recommended to use a value
less than 30 seconds.
parameters.
QCI This parameter is the QoS Class Identifier (QCI). The range is 0-255. The standard
QCI defined in the standard document is 1-9. 0 and 10-255 can be used by the
operator optionally.
[Related Specifications] 3GPP TS 23.203 [Table 6.1.7] Standardized QoS
characteristics.
PLMN_IDX The PLMN index to be changed or retrieved. The PLMN ID corresponding to the
selected plmnIdx is mapped to the PLMN ID which is retrieved/changed by command
RTRV/CHG-ENBPLMN-INFO with the same plmnIdx number.)

Confidential

PLMNSIGTIMER-INFO
PLMN_IDX The PLMN index to be changed or retrieved. The PLMN ID corresponding to the
selected plmnIdx is mapped to the PLMN ID which is retrieved/changed by command
INTERNAL_SIGNALI This parameter is the inactivity timer information for a signaling message. An eNB
NG_INACTIVITY_TIM starts an inactivity timer for a signaling message after a UE is attached. Signaling
ER Inactivity is initialized if a message containing NAS PDU information is received from
the UE or the MME and a timer is expired if a message containing the NAS PDU
information is not received while timer is operating. When timer is expired, a call is
detached if the User inactivity timer is also expired. If the User inactivity timer is not
expired, the call is waiting until the User inactivity timer is expired. This timer
operates in the unit "seconds". It is recommended not to change it because the
default is a service provider requirement.
Parameter Descriptions of CHG-LSHD-CONF/RTRV-LSHD-CONF

CELL_NUM This parameter is the cell number to identify each cell. This value must not exceed
USE_FLAG This parameter is whether to use the load shedding function. When there is cell
overload, the load shedding function makes the signaling inactivity timer and user
inactivity timer values smaller to reduce the overload. When the overload is cleared,
the load shedding function is automatically stopped.
• no_use: The load shedding function is not used.
• use: The load shedding function is used.
UEOVERLOAD_TRIG This parameter is the overload judgment threshold value for load shedding operation.
GER The load shedding function is executed if the number of active UEs of the cell is
larger than (maximum number of UEs that can be accommodated by the cell *
UEOVERLOAD_TRIGGER (%)) value. If the number of active UEs of the cell is
smaller than (maximum number of UEs that can be accommodated by the cell *
UEOVERLOAD_TRIGGER), the load shedding is not working. The operator can set
up the overload judgment criteria, that is, how many attached-active UEs are
determined as overload. However, it is recommended to use the default value.
UEOVERLOAD_HYS This parameter is the hysteresis value used to judge overload clear after the load
TERESIS shedding function is executed. If the number of active UEs of the cell is smaller than
(maximum number of UEs that can be accommodated by the cell *
(UEOVERLOAD_TRIGGER-UEOVERLOAD_HYSTERESIS)) after the inactivity timer
value is changed once by the load shedding function, it is determined that the
overload is cleared. If the overload is cleared, the load shedding function is stopped.
If the number of active UEs of the cell is still larger than (maximum number of UEs
that can be accommodated by the cell * (UEOVERLOAD_TRIGGER-
UEOVERLOAD_HYSTERESIS)), the load shedding function is re-initiated.

Confidential
UECANDIDATE_LOA This parameter is maximum number of UEs for which inactivity timer must be
D_SHEDDING changed and applied. The criteria of selecting the number of UEs, when the inactivity
timer value must be changed because the load shedding function is initiated, is
(maximum number of UEs that can be accommodated by the cell *
UECANDIDATE_LOAD_SHEDDING (%)). This parameter changes the inactivity
timer for this number of UEs. The higher the UECANDIDATE_LOAD_SHEDDING
value, the more the UEs whose inactivity timer value must be changed.
LOAD_SHED_SIG_IN This parameter is the signaling inactivity timer ratio value that must be set up when
ACT_TIMER_RATIO the load shedding function is initiated during overload status. This parameter
changes the signaling inactivity timer as much as (Signaling inactivity timer init value
* LOAD_SHED_SIG_INACT_TIMER_RATIO (%)) value. It is recommended to use
the default value. If the operator changes this value, the operator must change the
LOAD_SHED_DATA_INACT_TIMER_RATIO value.
LOAD_SHED_DATA_I This parameter is the user inactivity timer ratio value that must be set up when the
NACT_TIMER_RATIO load shedding function is initiated during overload status. This parameter changes
the user inactivity timer as much as the (User inactivity timer init value *
LOAD_SHED_SIG_INACT_TIMER_RATIO (%)) value. It is recommended to use the
default value. If the operator changes this value, the operator must change the
LOAD_SHED_SIG_INACT_TIMER_RATIO value to the same value.
PRIORITY_UEOVERL This parameter is the reference Allocation and Retention Priority (ARP) value used to
OAD_RESTRICT select an inactivity timer target. This parameter changes the inactivity timer for a UE
that has an ARP which is larger than the PRIORITY_UEOVERLOAD_RESTRICT
value or a UE for which ARP is not set up when selecting a load shedding target UE.
(In the standard, "0" means a logical error, "1" means the highest, and "14" means
the lowest priority. "15" means no priority.) A lower value means the number of
selected load shedding target UEs becomes smaller.
Counters and KPIs

CSL [0x0341] The cumulated number of call release due to the
ECC_USER_INACTIVITY expiration of both Signaling Inactivity Timer and User
Inactivity Timer.
REFERENCE

Confidential
LTE-SW0326, Connection Setup Time

Enhancement
INTRODUCTION
Control plane latency in LTE systems is defined as the latency associated with
transition of UE from RRC-IDLE to RRC-CONNECTED state. This involves
exchange of different control signaling messages between a UE and an LTE
network such as:
• Random access (RACH)
• RRC connection request
• RRC connection Setup
• NAS security command
• RRC Connection Reconfiguration
LTE release 8 recommends a control plane latency of <= 100 ms and LTE-
advanced recommends a control plane latency of <= 50 ms [1, 2, 3]. Thus,
achieving a lower control plane latency is utmost important to meet the LTE
Release 8 and LTE-advanced standards.
Simultaneous transmission and exchange of NAS security mode command and
RRC Connection Reconfiguration messages between UE and eNB is the first step
towards this improvement. This has the potential to reduce the control plane
latency by several milliseconds.
BENEFIT
The LTE call setup time is reduced by achieving the lower control plane (idle-to-
active transition) latency.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Figure below depicts the call setup procedures in between the UE and the eNB:

Confidential
As depicted in the figure above, the control plane (idle-to-active transition) latency
involves the following four major parts:
Random Access
This part involves UE random access process by transmitting UL PRACH. The
eNB processes the PRACH and sends Random Access Response (RAR) in the DL.
UE now processes this RAR to start transmission of UL RRC messages. These
steps are indicated in steps 1 to 5 in figure above.
RRC Request and Setup
This part involves UE RRC connection request transmission in the UL. The eNB
processes this request and transmits the RRC connection setup message in the DL.
The UE now processes the RRC connection setup message and transmits the UL
RRC Connection Setup Complete and NAS Service Request messages. The UE
needs to transmit UL SR and BSR to acquire UL grants for this UL RRC
Connection Setup Complete and NAS Service Request messages. This is indicated

Confidential
in steps 6 to 18 in figure above.

Connection Setup
The eNB now processes the UL RRC Connection Setup Complete message and
exchanges the Connection Request/Connection Setup message with the MME.
This is indicated in steps 19 to 23 in figure above.
Security Mode Command and RRC Connection Reconfiguration
This part involves two major message exchanges, Security Mode Command and
RRC Connection Reconfiguration messages. Initially in Samsung systems, these
two messages were exchanged sequentially.
• In the first step, the eNB transmits Security Mode Command message in the
DL. The UE processes this message and sends the Security Mode Complete
message in the UL. The UE needs to request and acquire UL grants from the
eNB, by transmitting UL SR and BSR. This is indicated in steps 24 to 34 in
figure above.
• In the second step, the eNB processes the Security Mode Complete message
and transmits DL RRC Connection Reconfiguration message. The UE
processes this message and sends the RRC Connection Reconfiguration
Complete message in the UL. The UE needs to request and acquire UL grants
from the eNB, by transmitting UL SR and BSR. This is indicated in steps 35 to
46 in figure above.
Simultaneous Transmission of Security Mode Command and RRC Connection

Reconfiguration
A significant amount of latency can be reduced by simultaneous DL transmission
of Security Mode Command and RRC Connection Reconfiguration messages. The
UE can also respond by sending Security Mode Complete and RRC Connection
Reconfiguration Complete messages simultaneously. Thus, as depicted in figure
above, the step 24 and 36 and step 34 and step 46 can be merged together.
Moreover, steps 36 to 47 are no more required. This will remove the processing
and message exchange latencies associated with steps 36 to 47.
SYSTEM OPERATION
How to Activate
Key Parameters

Confidential
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TR 36.912: Technical Specification Group Radio Access Network:
Feasibility study for Further Advancements for E-UTRA (LTE-Advanced)
(Release 11)
[3] 3GPP TR 36.913: Technical Specification Group Radio Access Network:
Requirements for further advancements for Evolved Universal Terrestrial Radio
Access (E-UTRA) (LTE-Advanced) (Release 11)

Confidential
LTE-SW0327, SIPTO Support

INTRODUCTION
There is an ever increasing demand for higher bandwidth and low latency
application. This increase in traffic further loads the LTE Core network resulting
in increased CAPEX and OPEX for the operator. Traffic offloading has been
attracting attention from operators as one solution to the problem of increased
traffic. Traffic offloading is a technology to veer traffic from user plane directly to
the internet from LTE eNB. Selective IP Traffic Offload (SIPTO) mechanisms are
intended to minimize the amount of data traffic that traverses the Core Network,
thereby reducing the backhaul requirements. This feature enables the UE to
offload traffic to the nearest network node (PDN GW) from where UE is located.
E-UTRAN supports SIPTO at the Local Network with a standalone GW where S-
GW and L-GW are collocated.
BENEFIT
• Offloads Core Network from the specific traffic type desired by the operator.
• Overload Control Feature by offloading traffic to gateway.
• Reduces Operator CAPEX and OPEX
DEPENDENCY
• Required Network Elements: An MME to support MME-triggered S-GW
relocation without UE mobility through the E-RAB Modify Request message.
• Others:
o Release 12 UE to support SIPTO@LN for standalone GW.
o Standalone GW is needed.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
SIPTO Architecture
SIPTO service enables an operator to offload selected traffic towards a network
Confidential
close to the UE. It is based on an enhanced gateway selection function that has the
capability to select a mobile core network gateway close to the eNB. When a user
requests to access a service that the operator has defined to be offloaded locally
through SIPTO offload, the packet data network (PDN) connection will therefore
be established through a local PDN gateway (L-GW) defined for SIPTO traffic
offload. Samsung E-UTRAN supports SIPTO with standalone L-GW architecture
and is illustrated in below diagram. This architecture is called SIPTO above RAN
architecture. This feature can be activated and deactivated by SIPTO_ALLOWED
(CHG-SIPTO-CONF).
GW Selection
The Straightforward-Name Authority Pointer (S-NAPTR) based selection of the S-
GW (based on TAI) gives the shortest user plane path from the UE to the S-GW
from the S-NAPTR ordering. Topological naming should be employed to find the
shortest user plane path from the S-GW to the P-GW based on the topological
closeness. With this approach, EPC selects an S-GW and P-GW to achieve the
shortest user plane path to the UE for a SIPTO enabled APN. EPC selects P-GW
based on the TA information (in EPC local configuration)
SIPTO@LN with standalone GW (with S-GW and L-GW collocated, Release 12)
SIPTO@LN is supported using a standalone GW that is deployed in the local
network. The MME may decide to trigger S-GW relocation without UE mobility.
If a handover is performed, SIPTO@LN PDN connection is released. The eNB
must support signaling of its LHN ID to the MME in the Initial UE Message,
Uplink NAS Transport, Handover Notify and Path Switch Request messages. To
select an appropriate Local GW (L-GW) for SIPTO at the local network service,
the GW selection function in the MME uses the APN and the Local Home
Network ID during the DNS interrogation as specified in TS 29.303 to find the
GW identity of the L-GW to be selected.
The eNB should support for MME-triggered S-GW relocation without UE
mobility through the E-RAB Modify Request message. Local Home Network ID
(LHN ID) is configured locally by LHN_ID (CHG-SIPTO-CONF) in each eNB of
the Local Home Network. Based on the operator configuration, the LHN ID can be
retrieved. If operator configuration is not available, then LHN ID can be identified
in a PLMN-ID. The eNBs in the same LHN have the same LHN-ID.

Confidential
eNB Functions
LHN ID Support
In the SIPTO@LN with standalone GW architecture, there is the concept of Local
Home Network (LHN). LHN is a set of eNBs belonging to a local network with a
standalone local GW-which consists of a co-located Serving Gateway and a Local
Gateway. These eNBs have IP connectivity for SIPTO L-GW. There can be many
LHNs per PLMN. Each LHN is identified uniquely by its own LHN identifier ID
(LHN ID). With this feature, eNB supports configuration of the LHN ID on per
PLMN basis.
The LHN ID uniquely identifies a local home network. The syntax of LHN ID
FQDN is provided in the following format.
• lhn <LHN name>.lhn.epc.mnc.mcc.3gppnetwork.org
where the length and content is an operator choice. The LHN ID is transported
in S1AP messages as below and eNB supports configuration of LHN ID in a
string format of size 32 to 256 bytes.
When LHN ID IE is received in the Initial UE Message, Path Switch Request,
Handover Notify and Uplink NAS Transport message, the MME, if supported,
uses it for SIPTO@LN operation as specified in TS 23.401.

Confidential
ERAB Setup for SIPTO@LN

When the UE requests for a new PDN connection for which a local GW can be
selected, the MME selects the local SGW and new E-RAB is setup in the eNB.
From an eNB perspective, this may result in two separate scenarios, one involving
Initial Context Setup Request message and another with ERAB Setup Request
message. When MME receives the LHN ID from eNB in Initial UE Message, it is
used to select the appropriate GW for SIPTO@LN service with a stand-alone GW
(with S-GW and L-GW collocated). The PDN GW selection function in MME
uses the APN and the LHN ID during the DNS interrogation as specified in TS
29.303 to find the PDN GW identity. Upon selecting the S-GW co-located with
LGW, MME further provides the S-GW (with collocated L-GW) information for
the bearer that is allowed for SIPTO offloading in Initial Context Setup Request
message with Transport Layer address and GTP tunnel ID of the selected S-GW in
E-RAB to be setup item IEs. The figure below illustrates an example scenario.
When MME receives the LHN ID in Uplink NAS TRASPORT and if the UE is
requesting a new PDN connection for which a local GW selection is possible,

Confidential
MME may select a local SGW. If the UE is already connected to the same S-GW
for an existing PDN connection, this would result in a S1AP ERAB Setup Request
message with the SGW (collocated with LGW) information in E-RAB to be setup
item IEs. The figure below illustrates example scenario.
In the S1AP Uplink NAS Transport message, the eNB provides LHN ID
configured for the UE selected PLMN. When MME receives LHN ID in Uplink
NAS Transport message, it is used to determine if the UE has left its current local
network and if S-GW relocation is needed. In this example, UE has not left its
current LHN. Upon receiving the NAS PDN connectivity request, MME performs
GW selection using APN and LHN ID and selects an S-GW collocated with L-
GW. MME sends Create Session Request to S-GW with LHN ID and S-GW in
turn sends Create Session Request to L-GW. Once the UL GTP tunnel ID
information is available from S-GW/L-GW, MME sends S1AP ERAB Setup
Request message with S-GW/L-GW IP address and GTP-TEID information to
eNB and eNB setups the bearer and provides downlink GTP TEID information
back to MME, similar to regular ERAB setup procedure.
eNB Support for MME-Triggered S-GW Relocation
Macro S-GW may be allocated for PDN connection in the operator network. If a
new PDN connection is requested by the UE that requires that a local S-GW is
selected to provide for SIPTO at the Local Network, S-GW relocation from the

Confidential
macro S-GW to the local S-GW is performed as specified in clause 5.10.4 [TS
23.401]. The MME sends the Serving GW Relocation Notification (Serving GW
addresses and uplink TEIDs for user plane) message to eNB. The eNB starts using
the new Serving GW addresses and TEIDs for forwarding subsequent uplink
packets.

Confidential
The UE has a PDN connection for which the local GW is not involved. When a
UE requests for a PDN connection for which a local GW can be selected, MME
relocates the SGW to local GW even for the already existing bearer. SGW
relocation is triggered by UE mobility (Tracking Area Update or Intra-LTE
mobility), but in this case, the SGW relocation is not triggered by UE mobility. As
part of SGW relocation in this scenario, the transport layer address and GTP tunnel
ID for the existing bearer needs to be modified at eNB, and hence MME sends
S1AP ERAB Modify Request with new GW information to eNB along with S1AP
ERAB Setup Request for the new SIPTO bearer. The eNB receives S1AP ERAB
Modify Request to modify QoS parameters, but in this case the transport layer
address and GTP-TEID is modified.
SYSTEM OPERATION
How to Activate

Confidential
Preconditions
• Run CHG-SIPTO-CONF and set SIPTO_ALLOWED to True.
• Run CHG-SIPTO-CONF and set SIPTO_ALLOWED to False.
Key Parameters
parameter.
Parameter Descriptions of CHG-SIPTO-CONF/RTRV-SIPTO-CONF
SIPTO_ALLOWED It should decide whether to support the SIPTO feature in eNB. Normal
operation is able if Rel.12 MME exists only.
• False: LHN_ID is not transmitted to MME.
• True: LHN_ID is transmitted to MME.
parameters.
Parameter Descriptions of CHG-SIPTO-CONF/RTRV-SIPTO-CONF
LHN_ID It transmits the configured LHN ID to MME in case SIPTO_ALLOWED ==
TRUE (SIPTO support feature is True). Refer the TS 23.003 for detailed
configuration. LHN ID must be at least 32 characters long.
For example, for MCC = 999, MNC = 99, and LHN name SAMSUNGLTE, LHN
ID = lhnSAMSUNGLTE.lhn.epc.mnc099.mcc999.3gppnetwork.org
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP Evolved Universal Terrestrial Radio Access Network (E-UTRAN) TS
36.300 (Release 12)
[2] 3GPP Evolved Universal Terrestrial Radio Access Network (E-UTRAN) S1

Confidential
Application Protocol (S1AP) TS 36.413 (Release 12)

[3] 3GPP General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) Access TS 23.401
(Release 12)
[4] 3GPP Local IP Access and Selected IP Traffic Offload (LIPA-SIPTO) TR
23.829 (Release 12)
[5] 3GPP Domain Name System Procedures TS 29.303 (Release 12)

Confidential
LTE-SW0329, Device Aware Call Control

INTRODUCTION
This feature allows an eNB to control features for a certain types of devices using
Masked IMEISV sent from an MME. If the IMEISV of the device is in the list of
IMEISVs which are registered in eNB, the eNB can block the corresponding UE's
access to network, CSFB or VoLTE.
BENEFIT
Operators can perform call control based on device type (Masked IMEISV).
DEPENDENCY
Required Network Elements: The MME needs to support Release 12 masked
IMEISV.
LIMITATION
This feature is not applied to emergency call. Emergency call is always allowed.
SYSTEM IMPACT
FEATURE DESCRIPTION
The International Mobile station Equipment Identity and Software Version
Number (IMEISV) is composed as shown in the following figure.
The IMEISV consists of the following elements:

• Type Allocation Code (TAC). Its length is 8 digits.
• Serial Number (SNR) is an individual serial number uniquely identifying each
equipment within each TAC. Its length is 6 digits.
• Software Version Number (SVN) identifies the software version number of the
mobile equipment. Its length is two digits.
Table below outlines the Rel.12 Masked IMEISV is defined in 3GPP TS 36.413.

Confidential
IE/Group Presence Range IE type and Semantics description

Name reference
Masked M - BIT STRING Coded as the International Mobile station
IMEISV (SIZE (64)) Equipment Identity and Software Version Number
(IMEISV) defined in TS 23.003 [21] with the last 4
digits of the SNR masked by setting the
corresponding bits to 1.
The first to fourth bits correspond to the first digit
of the IMEISV, the fifth to eighth bits correspond
to the second digit of the IMEISV, and so on.
To register a masked IMEISV controlled by this feature via LSM, IMEI_TAC

(CHG-BLKIMEISV-CONF), IMEI_FIRST_2_DIGIT_SNR (CHG-
BLKIMEISV-CONF), and IMEI_FIRST_2_DIGIT_SNR (CHG-BLKIMEISV-
CONF) are used.
Figure below depicts the call controls based masked IMEISV
1~3) The RRC Connection Setup procedure is performed.

4~5) After the eNB receives the RRCConnectionSetupComplete, the eNB
receives Masked IMEISV from the MME through InitialContextSetupRequest.
6) The eNB performs device aware call control according to the pre-defined
configuration as follows:
• If the received Masked IMEISV is in terminal black list, the eNB releases the
corresponding RRCConnection.
CALL_REJECT (CHG-BLKIMEISV-CONF) is used to apply this for the
corresponding Masked IMEISV.

Confidential
• If blocking CSFB flag is set for the Masked IMEISV and the UE requests a
CSFB call, the eNB does not allow the CSFB.
DRB_REJECT (CHG-BLKIMEISV-CONF) is used to apply this for the
• If blocking VoLTE flag is set for the Masked IMEISV and the UE requests a
VoLTE call, the eNB does not allow the VoLTE call.
CSFB_REJECT (CHG-BLKIMEISV-CONF) is used to apply this for the
SYSTEM OPERATION
How to Activate
Preconditions
Ensure that the following condition is met before enabling this feature.
• You must know masked IMEISV in advance. Based on the known IMEISV,
run CHG-BLKIMEISV-CONF and set IMEI_TAC,
IMEI_FIRST_2_DIGIT_SNR, and IMEI_SVN to register blacklist of up to 40
masked IMEISVs.
• Run CHG-BLKIMEISV-CONF to equip at least one IMEISV by setting
STATUS = EQUIP for blacklist IMEISV reject corresponding blacklist
IMEISV.
• Run CHG-BLKIMEISV-CONF to make not equip all blacklist masked
IMEISVs by setting STATUS = N_EQUIP for all dbIndex.
Key Parameters
parameter.

Confidential
Parameter Descriptions of CHG-BLKIMEISV-CONF/RTRV-BLKIMEISV-CONF

STATUS Indicating whether to use the masked IMEISV.
• Equip: Use the masked IMEISV.
• N_Equip: Not used.
parameter.
Parameter Descriptions of CHG-BLKIMEISV-CONF/RTRV-BLKIMEISV-CONF
DB_INDEX This is a DB index for configuring of masked IMEISV.
STATUS Indicating whether to use the masked IMEISV.
• Equip: Use the masked IMEISV.
• N_Equip: Not used.
IMEI_TAC In TS 36.413/TS 36.423, it is the 8-digit decimal number that corresponds to
Type Allocation Code (TAC) of front 8 digits of masked IMEISV that is
included in Release 12.
eNB combines TAC specified by imeiTac, and SNR front part 2 digits that are
specified by [to] imeiFirst2DigitSnr + and SNR back part [latter half] 4 digits
masked by 1 for each bit + SVN 2 digits that are specified by imeiSvn, checks
[confirms] the masked IMEISV value that are received S1AP or X2AP.
(TS 36.413 v12.4.0, TS 36.423 v12.4.0, TS 23.003 v12.4.0)
IMEI_FIRST_2_DIGIT_SNR This is a decimal [number] corresponding to the first [front] two digits in the
six digits of Serial Number (SNR) of Masked IMEISV.
(TS 36.413 v12.4.0, TS 36.423 v12.4.0, TS 23.003 v12.4.0)
IMEI_SVN This is a two-digit decimal [number] corresponding to the Software version
Number (SVN) of Masked IMEISV.
(TS 36.413 v12.4.0, TS 36.423 v12.4.0, TS 23.003 v12.4.0)
CALL_REJECT This determines whether to allow or reject a call connection for masked
IMEISV.
That is, if callReject is No, it allow a call, and if callReject is Yes, then it does
not allow a call.
DRB_REJECT This is a parameter that determines whether to allow the individual bearer
request at QCI level for the masked IMEISV.
For QCI of 256, whether to allow [permit] of each QCI by masking in bit to bit,
configure the QCI. The bit masked QCI allowance is represented in decimal
format.
For example, QCI #0 = allowed (0), QCI #1 = allowed (0, this is drbReject =
False (0)), all of QCI other than are not allowed (1, this is drbRejec = True
(1)), It is "00111,,," (total of 256-digit binary number) of "Bit string" type.
This is expressed by dividing [cutting] each 8 digits, the first one for QCI0-
QCI7, 00111111 (BIN) = 0x3F (HEX) = 63 (DEC)

Confidential
The rest are all set to 11111111 (BIN) = 0xFF (HEX) = 255 (DEC).
That is, drbReject[0] = 63 (0x3F), drbReject[1] = 255 (= 0xFF),...,
drbReject[31] = 255 (= 0xFF)
By setting above, it can be set to allow only "QCI 0" and "QCI 1".
CSFB_REJECT Controls whether to allow the CSFB for its masked IMEISV.
Counters and KPIs

CSL [0x037B] The cumulated number when a call is released
Rrm_blacklistImeisvFail because eNB does not support connection setup,
bearer setup, CSFB setup for blacklistImeisv.
CSL [0x037C] The cumulated number when a call is released
Rrm_blacklistImeisvPrep because a call is released when target eNB does
Fail not support connection setup, bearer setup,
CSFB setup for blacklistImeisv during HO.
REFERENCE
[1] 3GPP TS36.413, Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); S1 Application Protocol (S1AP).

Confidential
LTE-SW0331, VoLTE-aware Inactivity Timer

INTRODUCTION
During a VoLTE-to-VoLTE call setup, the originating user moves to the idle state
if ringing time goes beyond the time for determining user inactivity with no traffic
transmission or reception, and it requires an unnecessary paging procedure to
continue the call. To prevent this problem, the eNB uses a longer data inactivity
timer during VoLTE setup. After the VoLTE call is setup, the eNB applies
VoLTE-specific data inactivity timer, which is defined according to the VoLTE
service characteristic.
BENEFIT
• An operator can provide a better quality of VoLTE service to their subscribers,
by reducing the number of VoLTE setup failures due to user inactivity and by
applying specific inactivity control for VoLTE service.
• Users can experience the better quality of VoLTE service.
DEPENDENCY
• Prerequisite Features: LTE-SW0325, User Inactivity Timer Control
LIMITATION
None
SYSTEM IMPACT
capabilities.
Related Feature: LTE-SW0325, User Inactivity Timer Control
The LTE-SW0325 feature introduces per-QCI data inactivity timer for data
inactivity monitoring. There is a dependency on LTE-SW0325 because the
VoLTE-aware Inactivity Timer feature reuses the per-QCI data inactivity timer.
The data inactivity timer for QCI #5 is used by VoLTE-aware Inactivity Timer
feature only in case of IMS packet. It may cause different aspects from User
Inactivity Timer Control feature.
When the data inactivity timer value for QCI #5 is the longest value, for example
30 s, this value is applied to all UEs with QCI #5 bearer by User Inactivity Timer
Control feature. However, in case of the VoLTE-aware Inactivity Timer feature,
this value is applied only to UEs that have IMS packet transmission and reception.

Confidential

None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
The eNB behavior for the user inactivity control except monitoring of data
inactivity, as described below, is same as the current mechanism according to
LTE-SW0325, User Inactivity Timer Control.
If this feature is activated (VOLTE_INACTIVITY_TIMER_ENABLE of CHG-
ENB-INF is set to TRUE), the eNB uses different data inactivity timers
(INTERNAL_USER_INACTIVITY per QCI per PLMN ID of CHG-INACT-
TIMER) according to the following:
• IT_IMS: The data inactivity timer value for QCI #5.
• IT_VoLTE: The data inactivity timer value for QCI #1.
• IT_data: The longest value among the data inactivity timer values per each
QCI for other E-RABs except QCI #5.
IMS Signaling Phase for VoLTE Setup

To avoid call release due to user inactivity during VoLTE setup, the eNB uses the
first dual inactivity timer for monitoring of data inactivity.
The first one is a data inactivity timer for IMS signaling bearer (IT_IMS) and the
second one is a data inactivity timer for other data bearers (IT_data).
IMS signaling bearer means an E-RAB (E-UTRAN Radio Access Bearer) with
QCI #5 and IT_IMS is the data inactivity timer for QCI #5. The IT_data is the
longest value among the data inactivity timers per each QCI for other E-RABs
except QCI #5.
These dual inactivity timers are applied for the UE when IMS signaling bearer
(QCI #5) is setup. The eNB uses the second timer (IT_data) when there is no IMS
signaling packet. When the IMS signaling packet occurs, the eNB uses the first
timer (IT_IMS).
By increasing IT_IMS, the problem of call release due to user inactivity during
VoLTE setup can be avoided. Even though increased IT_IMS, there are little
impacts on user stayed time in connected state or number of simultaneous RRC
connections because IT_IMS is used only in case IMS signaling packet is
occurred.

Confidential
After Completion of VoLTE Setup and During VoLTE Call

At VoLTE bearer (QCI #1) setup is successfully completed, the eNB uses the
second dual inactivity timers for IMS signaling bearer (IT_IMS) and VoLTE
bearers (IT_VoLTE) for monitoring of data inactivity. The eNB uses the first timer
(IT_IMS) during there is no VoLTE packet. Since when VoLTE packet is
occurred, eNB uses the second timer (IT_VoLTE).
After VoLTE call is Ended

After VoLTE bearer (QCI #1) is released, the eNB applies IT_data as data
inactivity timer. IT_data is the longest value among the data inactivity timer values
per each QCI for other E-RABs except QCI #5.
Figure below depicts the data inactivity monitoring procedure performed by the
eNB.

Confidential
At completion of initial context setup procedure and E-RAB with QCI #5 for IMS
signaling is established, the eNB applies the first dual inactivity timers, that is, one
is a data inactivity timer for IMS signaling bearer (IT_IMS) and the other is a data
inactivity timer for other data bearers (IT_data). IT_IMS is the data inactivity
timer value for QCI #5 and IT_data is the longest value among the data inactivity
timer values per each QCI for other E-RABs except QCI #5.
If UL/DL data packet with QCIs other than QCI #5 is occurred, the eNB starts
IT_data and uses IT_data for data inactivity monitoring during there is no IMS
signaling packet.
If IMS signaling packet (QCI #5) is occurred, the eNB changes the data inactivity
timer from IT_data to IT_IMS and uses IT_IMS for data inactivity monitoring.
When an E-RAB with QCI #1 for VoLTE is added, the eNB applies the second
Confidential
dual inactivity timers, that is, one is a data inactivity timer for IMS signaling
bearer (IT_IMS) and the other is a data inactivity timer for VoLTE (IT_VoLTE).
IT_VoLTE is applied when VoLTE packet is occurred.
When the E-RAB with QCI #1 for VoLTE is released, the eNB changes the data
inactivity timer from IT_VoLTE to IT_data and uses IT_data for data inactivity
monitoring. IT_data is the longest value among the data inactivity timer values per
each QCI for other E-RABs except QCI #5.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-ENB-INF and set VOLTE_INACTIVITY_TIMER_ENABLE to
ON.
• Run CHG-INACT-TIMER and set INTERNAL_USER_INACTIVITY to
larger than 0 to enable the user inactivity timer for target PLMN_IDX and QCI
(QCI = 1 for VoLTE bearer and QCI = 5 for IMS signaling).
• Run CHG-ENB-INF and set VOLTE_INACTIVITY_TIMER_ENABLE to
OFF.
• Run CHG-INACT-TIMER and set INTERNAL_USER_INACTIVITY to 0 to
disable the user inactivity timer for target PLMN_IDX and QCI.
Key Parameters
parameters.
VOLTE_INACTIVITY_ This parameter is used to control the VoLTE-aware Inactivity Timer function.

Confidential
TIMER_ENABLE • OFF (0): VoLTE-aware Inactivity Timer function off
• ON (1): VoLTE-aware Inactivity Timer function on

parameters.
QCI This parameter is the QoS Class Identifier (QCI). The range is 0 to 255. The
standard QCI defined in the standard document is 1 to 9. The value 0 and 10 to 255
characteristics.
PLMN_IDX The PLMN index to be changed or retrieved. PLMN ID corresponding to the selected
plmnIdx is mapped to the PLMN ID, which is retrieved/changed by command
Counters and KPIs

CSL [0x0341]ECC_USER_INACTIVI The cumulated number of Call Release due to
TY the expiration of both Signaling Inactivity Timer
and User Inactivity Timer.
REFERENCE
None

Confidential
LTE-SW0332, UE Category Aware Call Control

INTRODUCTION
This feature performs call control for specific UE category such as eMTC (Cat-
M1). If the number of corresponding UEs is greater than a predefined threshold,
the eNB does not admit the incoming call from the corresponding UEs.
BENEFIT
Operators can control the number of eMTC UEs that eNB can accept.
DEPENDENCY
• HW dependency: Control for eMTC can be provided on eNB HW
configuration which support eMTC.
• Others: The eMTC UE is required.
LIMITATION
None
SYSTEM IMPACT
capabilities.
Interdependency between Features
This feature is operated after LTE-SW4101 Capacity based Call Admission
Control for RRC Connection is passed.
None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
UE category aware call control operates as follows.

Confidential
The eNB can control eMTC UEs in terms of the number of UEs. If the number of
eMTC UEs is greater than a predefined threshold, the eNB does not admit
incoming eMTC UE. Also, this feature can reserve the number of UEs which can
be used for only eMTC UEs. (Reserved resources cannot be used for legacy LTE
UEs.)
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
• Run CHG-ENB-CAC and set CAT1_CAC_ENB_USAGE to USE to activate the
feature in eNB level.
• Run CHG-CELL-CAC and set CAT1_CAC_CELL_USAGE to USE to activate
the feature in cell level.
• Run CHG-ENB-CAC and set EMTC_CAC_ENB_USAGE to USE to activate the
feature in eNB level.
• Run CHG-CELL-CAC and set EMTC_CAC_CELL_USAGE to USE to activate
the feature in cell level.
• Run CHG-ENB-CAC and set CAT1_CAC_ENB_USAGE to NOT_USE to
deactivate the feature.
• Run CHG-CELL-CAC and set CAT1_CAC_CELL_USAGE to NOT_USE to
deactivate the feature in cell level.
• Run CHG-ENB-CAC and set EMTC_CAC_ENB_USAGE to NOT_USE to
deactivate the feature.
• Run CHG-CELL-CAC and set EMTC_CAC_CELL_USAGE to NOT_USE to
deactivate the feature in cell level.
Key Parameters
parameters.
Parameter Descriptions of CHG-ENB-CAC/RTRV-ENB-CAC
CAT1_CAC_ENB_USAGE Category 1 UE call admission control usage per eNB (per eNB).
EMTC_CAC_ENB_USAGE It is per-eNB level eMTC UE Call admission control usage on/off parameter.
(per eNB).
Parameter Descriptions of CHG-CELL-CAC/RTRV-CELL-CAC

Confidential
CAT1_CAC_CELL_USAGE Category 1 UE call admission control usage per cell.
EMTC_CAC_CELL_USAGE It is cell level eMTC UE admission control usage on/off parameter.
parameters.
CAT1_CAC_ENB_USAGE Category 1 UE call admission control usage per eNB (per eNB).
CAT1_CALL_COUNT_CAC Call count CAC threshold for Category 1 UE, which is not treated as emergency
_THRESH call (per eNB).
EMTC_CAC_ENB_USAGE It is per-eNB level eMTC UE Call admission control usage on/off parameter
(per eNB).

CAT1_CAC_CELL_USAGE Category 1 UE call admission control usage per cell.
CAT1_CALL_COUNT_CAC Call count CAC threshold for Category 1 UE which is not treated as emergency
_THRESH call. (per Cell)
CAT1_DRB_COUNT_CAC_ DRB count threshold for Category 1 UE CAC (per cell).
THRESH
CAT1_TOTAL_PRB_CAC_ Total PRB Category 1 UE CAC threshold for downlink (per cell).
THRESH_DL
CAT1_TOTAL_PRB_CAC_ Total PRB Category 1 UE CAC threshold for uplink (per cell).
THRESH_UL
EMTC_CAC_CELL_USAGE It is cell level eMTC UE admission control usage on/off parameter.
Counters and KPIs

RRC Connection Re- ConnReEstabRejec The cumulated number of RRCConnectionRe-
establishment t_CpCapaCacFail establishmentReject messages transmitted to the UE
since the RRC connection re-establishment procedure
has been judged unable to be performed by the Call
Admission Control (CAC) based on call count per cell
operation or the CAC based on DRB count per cell
operation after receiving RRCConnectionRe-
establishmentRequest from the UE.
E-RAB Setup ErabInitFailNbr_Cp The cumulated number when a call is released due to
CapaCacFail Capacity Call Admission Control for E-RAB in the
origination call.
E-RAB Setup Add ErabAddFailNbr_Cp The cumulated number when a call is released due to
CapaCacFail Capacity Call Admission Control for E-RAB in the
origination call.
Intra-eNB Handover IntraEnbPrepFail_C The cumulated number when preparation fails due to
the Call Admission Control (CAC) based on call count

Confidential

pCapaCacFail per cell operation or CAC based on DRB count per cell
operation during the intra HO preparation procedure.
X2 In Handover InterX2InPrepFail_ The cumulated number when preparation fails due to
CpCapaCacFail the Call Admission Control (CAC) based on call count
per cell operation or CAC based on DRB count per cell
operation during the inter X2 HO preparation procedure.
S1 In Handover InterS1InPrep_Fail The cumulated number when preparation fails due to
operation during the inter S1 HO preparation procedure.
Intra-eNB In Handover IntraEnbInPrepFail_ The cumulated number when preparation fails due to
operation during the intra HO preparation procedure.
REFERENCE
None

Confidential
LTE-SW0334, SDL (Supplemental Downlink)

Support
INTRODUCTION
Supplemental Downlink (SDL) uses unpaired spectrum to enhance the downlink
capability as Scell and SDL cell can be configured, for example, Band 66 AWS-3
(DL 2155 - 2180, UL 1755 - 1780).
BENEFIT
The SDL cell is used as an SCell at carrier aggregation over mobile broadband
networks, thereby much more traffic on the downlink can be serviced to UE.
DEPENDENCY
HW dependency: Band 66 AWS-3 RU
LIMITATION
• Required to lock the cell for enabling/disabling SDL.
• The measurement configuration of handover and the ANR for SDL cell
frequency are configured and the corresponding Measurement Report (MR)
can occur on serving cell with neighbor as SDL cell (frequency). It can have
an impact on UE throughput.
• SDL is not supported in TDD system.
• For configuration to SDL cell from normal cell, it is required to lock the cell.
When SDL is configured, eMTC operation is not available and turns off even
if the system parameter for eMTC is still ON. However, if an operator wants to
turn off the NB-IoT operation, NB-IoT is required to be de-grown because
NB-IoT can provide in-band or guard-band.
SYSTEM IMPACT
capabilities.
Interdependency between Features
None
Measurement gap and MR signaling by first limitation above can have an impact
on UE throughput.
Coverage
None
Confidential
Interfaces
None
FEATURE DESCRIPTION
The SDL uses downlink only without uplink spectrum. It allows a single carrier in
an unpaired carrier to be used along with the serving cell's paired downlink and
uplink carriers for enhancement of downlink capability such as carrier aggregation
feature.
This provides an efficient way of using spectrum because consumption of rich
content and other data heavy applications is asymmetric. There is much more
traffic on the downlink than on the uplink over mobile broadband networks.
The characteristic of downlink only has a benefit in view of the coverage, since the
coverage is usually limited by the uplink.
When a cell is configured as SDL with downlink only, the cell does not send SIBs
except for MIB and SIB1 with IE cellbarred set to barred. This results in barring
for UL access. The change notification of system information for SIB is not
provided because SDL cell does not require.
For SDL cell, the value of IE UL EARFCN is set to specific value (which is
internally determined) in X2 Setup Request/Response and eNB Configuration
Update messages.
If the cell perceives that neighbor cell is SDL cell through the X2 Setup procedure
and the eNB Configuration Update message, it does not trigger Handover
procedure against SDL cell. However, the measurement configuration of handover
and the ANR for SDL cell frequency are configured and the corresponding MRs
can occur on serving cell with neighbor as SDL cell (frequency).
The SDL cell rejects the incoming S1 and X2 handover request from neighbor cell.
SYSTEM OPERATION
How to Activate
This feature runs automatically if the cell belongs to E-UTRA Operating Band 32,
and it cannot be disabled.
Key Parameters
Counters and KPIs

with this feature.

Confidential
REFERENCE
UTRAN); User Equipment (UE) radio transmission and reception

Confidential
LTE-SW0501, S1 Interface Management

INTRODUCTION
S1 interface management feature manages the non UE-associated signaling
between eNB and MME. When eNB starts, eNB performs S1 setup procedures
with MME according to 3GPP TS36.413, and it manage the connection by
exchanging Keep Alive, S1 Reset, eNB/MME Configuration Update, and Error
Indication messages.
S1 interface management feature also includes path management between eNB
and SGW. Once eNB and MME setup an E-RAB connection, the eNB and the
Serving GW can transmit user packets uplink and downlink through GTP tunnel.
Each E-RAB bearer is distinguished by TEID (Tunnel Endpoint Identifier). The
eNB supports path management function based on 3GPP TS29.281.
BENEFIT
• The S1-MME interface between eNB and MME is managed by non UE-
associated signaling procedures.
• The S1-U interface between eNB and SGW is managed via GTP tunnel
management.
DEPENDENCY
• Required Network Elements: MME
LIMITATION
• The eNB can connect to up to 16 MMEs at the same time.
SYSTEM IMPACT
FEATURE DESCRIPTION
S1-U is based on GTP tunnel between eNB and SGW. The GTP tunnel is a UE-
associated connection and created when UE's state change to RRC connected
mode.
Through the GTP tunnel, the eNB delivers/receives user packets to/from SGW.
The GTP tunnel is maintained while the UE is in RRC connected mode and
released when the UE's state changes to RRC idle mode.
The following sub sections explain how to configure S1-MME and S1-U interface
with related parameters and how eNB and MME manage S1 interface via S1AP
Confidential
procedures defined in 3GPP TS 36.413.
S1 Setup
The S1 Setup procedure is the first S1AP procedure after a SCTP connection has
been established. When this procedure is performed, the application level
configuration data in eNB and MME is updated with the newly received data from
each other. During S1 setup procedure, the eNB sends its basic application level
configuration data such as Global eNB ID, Supported Tracking Area list, Default
paging DRX, and supported CSG ID. The MME sends its list of served
GUMMEIs, Relative MME capacity and so on.
The following figure describes successful S1 setup operation.
When the MME cannot accept S1 Setup request, it should respond with a S1 Setup
Failure and appropriate cause value. If the S1 Setup Failure message includes
Time to Wait IE, the eNB shall wait at least for the indicated time before
reinitiating the S1 Setup towards the same MME.
If the eNB fails to receive the S1 Setup Response message within certain amount
of time configured by S1_SETUP timer (configurable by CHG-TIMER-INF), it
retransmits the S1 Setup Request again to MME.
As the S1 management interface is essential for LTE service, the eNB retransmits
S1 Setup Request to the MME unlimitedly until it receives S1 Setup Response
successfully from MME.
The following figure describes unsuccessful S1 Setup operation.

Confidential
S1 Reset
When an abnormal situation occurs, the S1 interface of all or some UEs can be
re-initialized through reset procedure. However, the application level configuration
data, which is exchanged by S1 setup procedure, is not changed.
The eNB sends the Rest Acknowledge message to MMEs after receiving the Reset
message, and then sends the RRC Connection Release message to the target UEs.
Then the UE related resources, which are controlled by the eNB, are released.
Figure below depicts an S1 reset procedure triggered by MME.
Another example of S1 reset is, when the eNB decides a specific SW or HW

module is in an abnormal state and unable to provide the normal service, which
has resulted in the loss of some or all transaction reference information, it sends
the reset message to the MME.
When eNB determines the cell is abnormal, eNB sends S1 Reset to MME
including the list of UEs to be released.
The list of UEs, whose resources should be released, can be specified by MME UE
S1AP ID IE or eNB UE S1AP ID IE of the UE-Associated logical S1-connection
list IE in S1 Reset message.
The MME UE S1AP ID uniquely identifies a connected UE association among
many UE associations within the MME and eNB UE S1AP ID uniquely identifies
a connected UE association within the eNB.
Hence, by informing these IDs to MME or eNB, MME or eNB can easily identify
which UEs are impacted by this Reset message and releases them.
The following figure describes eNB triggered S1 reset.

Confidential
If the eNB fails to receive the S1 Reset Acknowledge message within certain
amount of time configured by S1_RESET timer, it retransmits the S1 Reset
message again to MME up to S1_RESET_RETRY_COUNT times.
Unlike Reset by MME, the eNB does not send RRC Connection Release to UE
right after Reset if Reset is triggered by the eNB.
In case of Reset by the eNB, the eNB is in an abnormal state and may not be able
to send RRC Connection Release to the corresponding UEs correctly.
Hence, instead of sending RRC Connection Release to UEs right away, the eNB
relies on each UE’s failure detection mechanism such as RLF (Radio Link Failure)
detection.
When the UE detects RLF due to eNB’s Reset, it tries to send RRC Connection
Reestablishment request to the eNB and if the eNB is able to accept this request,
the connection continues.
If it fails after several times of retries, the UE will release RRC connection by
itself and goes to Idle. Later when RRC connection is needed, the UE will send
RRC Connection Request to create new RRC connection.
Error Indication
When the received message cannot be processed normally and cannot be
responded with the appropriate failure message, eNB or MME can report this fact
to the peer with Error Indication procedure.
Currently, the eNB sends Error Indication only when it fails to decode the received
messages. It means whenever the eNB decides that it is impossible to parse and
interpret the bit stream of the received message, it sends the Error Indication with
Cause IE. However, it does not send Error Indication in case of sematic error or
logical errors and and so on. For example, if the eNB successfully decodes the
received message and it turns out to have a value out of range, the eNB does not
send Error Indication and instead, discards or ignores the received IE or message.
In case the Error Indication procedure is triggered at UE associated signaling
procedure, the MME UE S1AP ID and the eNB UE S1AP are included in the
ERROR INDICATION message as depicted in the following figure. Otherwise,
the Error Indication does not include MME UE S1AP ID and eNB UE S1AP ID.

Confidential
Following updates to Rel-10/Rel-11 of 3GPP 29.281, it is no longer required to

send an Error Indication message in the case that the incoming GTP-U PDU
contains a TEID with value of 'all zeros'.
The following figure describes eNB originated Error Indication.
Figure below depicts the error indication originated by MME.
eNB Configuration Update

When the eNB wants to update the application level data, the eNB sends the eNB
Configuration Update message to the MME with which the eNB has an established
S1 connection.
If the current TAC, eNB Name, or DefaultPagingDRX value set in the PLD is
changed during system operation, the eNB includes not only the changed
parameter values but also the unchanged parameter values in the eNB
Configuration Update message, and sends it to the MMEs.
At this time, the eNB sends the message to all MMEs with established S1
connection. When the eNB Configuration Update message is sent, a timer starts
configured by “S1_UPDATE” parameter (configurable by CHG-TIMER-INF)
and the eNB expects an eNB Configuration Update Acknowledge message to be
received before the timer expires.
When the MME cannot accept eNB Configuration Update request, it shall respond
with an eNB Configuration Update Failure including appropriate cause value. If
the eNB Configuration Update Failure message includes the Time to Wait IE, the
eNB waits at least for the indicated time before reinitiating the eNB Configuration
Update towards the same MME.
Both eNB and MME shall continue to operate the S1 with their respective
configuration data.
If the eNB configuration update acknowledge message is not received before the
“S1_UPDATE” timer expires, the eNB kills the timer, resends the eNB
configuration update message up to “S1_UPDATE_RETRY_COUNT” times
(configurable by CHG-TIMER-INF).

Confidential
The following figure describes successful eNB Configuration Update.
Figure below depicts an unsuccessful operation of eNB configuration update.
MME Configuration Update

Similar to eNB Configuration Update, when the MME wants to update the
application level data, the MME sends the MME Configuration Update message to
the eNB with which the eNB has an established S1 connection.
If the eNB sends MME Configuration Update failure, then there might be
mismatch in the Relative MME Capacity between the MME and the eNB. In some
cases, the eNB selects MME according to the old Relative MME Capacity.
The following figure describes successful MME Configuration Update.
Figure below depicts an unsuccessful operation of MME configuration update.

Confidential
Keep Alive between eNB and MME

For the SCTP parameter names of the following description, refer to COM-IP0401
SCTP.
The eNB and the MME monitors S1-MME connection by exchanging SCTP
HEARTBEAT/ HEARTBEAT ACK messages defined by SCTP protocol.
HEARTBEAT message is periodically transmitted and the period is configured as
‘SCTP_ASSOC_HEART_BEAT_INTERVAL’. When transmitting
HEARTBEAT message, the eNB delivers the current time in the Heartbeat
Information field, which is also included in the HEARTBEAT ACK message so
that the sender and receiver can calculate the Round Trip Time (RTT).
The following figure describes successful Keep Alive between eNB and MME.
When HEARTBEAT ACK message is not received, eNB tries to retransmit

HEARTBEAT message periodically. The maximum number of retransmission is
configured as ‘SCTP_PATH_MAX_RETRANS”.
The period of retransmission is ‘Heartbeat Retransmission Interval’ in the
following figure and calculated as ‘SCTP_ASSOC_HEART_BEAT_INTERVAL’
+ RTO + RTO * [-0.5, 0.5], where RTO is increased as exponential backoff if the
previous HEARTBEAT message is unanswered. The initial, minimum, and
maximum values are configured as ‘SCTP_RTO_INITIAL’, ‘SCTP_RTO_MIN’
and ‘SCTP_RTO_MAX’

Confidential
When HEARTBEAT ACK is not received after all the retransmission, the link
status is considered as abnormal.
If the MME SCTP connection is considered as abnormal, the
‘MME_FAILOVER_TIMER’ is triggered and the call is not released if the SCTP
connection is restored before the timer expiry.
However, when the ‘MME_FAILOVER_TIMER’ expires, all active calls on the
SCTP connection are released and ‘MME_COMMUNICATION_FAIL’ alarm is
generated.
While the “MME_COMMUNICATION_FAIL” alarm is on, eNB routes new call
attempts to another alive MMEs via S1-flex. For example, when there are three
MMEs (MME1, MME2, MME3), eNB normally maintains three S1 interfaces,
one for each MME1, MME2 and MME3 and distributes calls among them. In case
S1 interface to MME1 fails, eNB routes new call attempts to two remaining
MMEs (MME2 and MME3).
The following figure describes unsuccessful Keep Alive between eNB and MME.
In case of S1 setup procedure, the eNB transmits the INIT message to establish
SCTP association. If it fails to get the response of INIT ACK message, the eNB
transmits the INIT message once again after SCTP_RTO_INITIAL. If this INIT
message is also not answered, the eNB repeats this procedure with the period of
CONNECT_INTERVAL until the SCTP setup is successful.
Figure below depicts an unsuccessful SCTP setup procedure between the eNB and
the MME.

Confidential
Path Management between eNB and S-GW

According to 3GPP TS 29.281, eNB and S-GW can monitor S1-U path using
ECHO REQUEST/ECHO RESPONSE messages defined by GTP-U protocol.
Here, “S1-U Path” means a logical connection between an eNB and a S-GW. In
other words, only one “S1-U Path” exists between a certain eNB and a certain S-
GW even though there may be many S1 bearers between them. Hence, eNB
manages only one S1-U path for each S-GW by sending an Echo Request to find
out if it is alive.
The following figure describes successful path management procedures between
eNB and three S-GWs. In this case, there are three S1-U paths and for each path,
eNB sends the ECHO REQUEST message to S-GW periodically as per
"T3_TMR_LONG" (configurable by CHG-GTP-INF) and waits for ECHO
RESPONSE message.

Confidential
If the eNB fails to receive the ECHO RESPONSE message, it resends the ECHO
REQUEST message after "T3_TMR" (configurable by CHG-GTP-INF) up to the
configured maximum retransmissions ‘N3_REQUEST’ (configurable by CHG-
GTP-INF). When the eNB fails to receive the ECHO RESPONSE message even
after maximum resending, it will release all E-RAB connections with the failed S-
GW and triggers MME to release the related calls via S1-Reset procedure.
The following figure describes unsuccessful Keep Alive between eNB and S-GW.

Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• This feature runs automatically, and it cannot be disabled.
• The eNB can enable specific S1-MME interface by running CHG-MME-CONF
to configure MME by adding IP address and to set the status to be Equip and
unlock active state of the specific MME.
• The eNB can disable specific S1-MME interface by running CHG-MME-CONF
to make specific MME are Not Equipped.
Key Parameters
parameters.
Parameter Descriptions of RTRV-MME-CONF/CHG-MME-CONF (MME
Information)
MME_INDEX The index used to access the information. Since there are a total of 16 MMEs
that can be connected to an eNB, the index range is 0 to 15.
STATUS The EQUIP status information on the MME.
• N_EQUIP: The MME to connect does not exist.
• EQUIP: The MME to connect exists
ACTIVE_STATE The state information on the specified MME in operation. If there is an
undesired MME, this parameter value must be changed to Inactive. The
default is active. If the STATUS parameter is set to Equip, it is better not to
change this parameter value to inactive.
• Inactive: MME (S1 assigned) is not used.
• Active: MME (S1 assigned) is used.
IP_VER The IP address version of the MME. Either IPv4 or IPv6 is assigned.
MME_IPV4 Information on the IPV4 address of the MME. This parameter value is valid
only if the IP_VER parameter is set to IPv4. It is not used if the IP_VER
parameter is set to IPv6.

Confidential
MME_IPV6 Information on the IPV6 address of the eNB. This parameter value is valid
ADMINISTRATIVE_STATE The status of the MME link.
• Locked: A state where active calls connected to the MME are all dropped,
and new call connections are not possible.
• Unlocked: Connection to the MME is normal.
• Shutting down: A state where active calls connected to the MME are
maintained, but new call connections are not possible.
SECONDARY_MME_IPV4 The secondary IP address of the IPv4 type set in the MME node to support
the SCTP Multi Homing function. It is valid only if the IP_VER parameter is
set to IPv4.
This is for SCTP multi-homing
set to IPv6.
This is for IPv6.
S1_TUNNE_GROUP_ID This parameter defines IPSec Tunnel Group ID of the MME (valid only if
IPsec tunnel group function is supported).
parameters.
Parameter Descriptions of CHG-TIMER-INF/RTRV-TIMER-INF (S1
Management Timer/Count Information)
S1_SETUP Waiting duration for S1Setup Response or S1Setup Failure after eNB sends
S1Setup Request. (ms)
S1_UPDATE Waiting duration for eNB Configuration Update Acknowledge or eNB
Configuration Update Failure after eNB sends eNB Configuration Update
request. (ms)
S1_UPDATE_RETRY_COUN The retry count for the eNB configuration update procedure when the
T eNBConfigurationUpdateFailure message is received from the MME or when
time out occurs after sending the eNBConfigurationUpdate message from the
eNB.
S1_UPDATE_TIME_TO_WAI The TimetoWait value included in MMEConfigurationUpdateFailure
T transmission.
s1Reset Retrieve Only (Not Configurable)
Waiting duration for S1 Reset Acknowledge after eNB sends S1 Reset
Request (ms).
s1ResetRetryCount Retrieve Only (Not Configurable)
Maximum number of S1 Reset Retransmission:
• ci_RetryZero: no retransmission
• ci_RetryOne: 1 retransmission
• ci_RetryTwo: 2 retransmission
• ci_RetryThree: 3 retransmission
• ci_RetryTen: 10 retransmission
• ci_RetryInfinity: infinite retransmission

Confidential
Parameter Descriptions of CHG-MME-CONF/RTRV-MME-CONF (MME

Information)
that can be connected to the eNB, the index range is 0 to 15.
STATUS The EQUIP status information on the MME.
• EQUIP: The MME to connect exists.
ACTIVE_STATE The state information on the specified MME in operation. If there is an
undesired MME, this parameter value must be changed to Inactive. The
default is active. If the STATUS parameter is set to Equip, it is better not to
change this parameter value to inactive.
• Inactive: MME (S1 assigned) is not used.
• Active: MME (S1 assigned) is used.
IP_VER The IP address version of the MME. Either IPv4 or IPv6 is assigned.
MME_IPV4 Information on the IPV4 address of the MME. This parameter value is valid
MME_IPV6 Information on the IPV6 address of the eNB. This parameter value is valid
ADMINISTRATIVE_STATE The status of the MME link.
• Locked: A state where active calls connected to the MME are all dropped,
and new call connections are not possible.
• Unlocked: Connection to the MME is normal.
• Shutting down: A state where active calls connected to the MME are
maintained, but new call connections are not possible.
set to IPv4.
This is for SCTP multi-homing.
set to IPv6.
This is for IPv6.
S1_TUNNEL_GROUP_ID This parameter defines IPSec Tunnel Group ID of the MME
Refer to COM-IP0401 feature for parameter descriptions of CHG-SCTP-PARA

/RTRV-SCTP-PARA, CHG-ENBCONN-PARA/RTRV-ENBCONN-PARA.
Parameter Descriptions of CHG-GTP-INF/RTRV-GTP-INF (GTP Information)

T3_TMR The interval at which transmission of the ECHO-REQ message is repeated if
a response message to ECHO-REQ, which is sent for Keep Alive, is not
received. The range is between 0 and 60000 ms. The default is 5000 (5 s).
This timer runs only if KEEP_ALIVE is set to 1 (ms).
T3_TMR_LONG The interval at which the ECHO-REQ message is sent for periodic Keep
Alive. The range is between 60000 and 600000 msec. The default is 60000
(60 s). This timer runs only if KEEP_ALIVE is set to 1 (ms).

Confidential
N3_REQUEST The maximum retransmission number of the GTP ECHO-REQ message.
This timer runs only if KEEP_ALIVE is set to 1.
KEEP_ALIVE Whether the GTP ECHO-REQ message at specified intervals (Keep Alive) is
sent.
• 0: The ECHO-REQ message is not sent.
• 1: The ECHO-REQ message is sent (default).
SNN Whether the GTP sequence number is used.
• 0: The GTP sequence number in the eNB is not used.
• 1: The GTP sequence number in the eNB is used.
ECN Whether the Explicit Congestion Notification (ECN) function is used.
• 0: The ECN function in the eNB is not used.
• 1: The ECN function in the eNB is used.
Parameter Descriptions of RTRV-S1-STS (S1 Status, Retrieval only)

MME_INDEX MME Index
MME_ID MME Id
SCTP_STATE SCTP state
S1AP_STATE Interface state
MME_NAME MME name
IP_VER MME IP version (IPv4 or IPv6).
MME_IP_V4 MME IPV4 address
MME_IP_V6 MME IPV6 address
Parameter Descriptions of CHG-IP-ADDR/CRTE-IP-ADDR/DLT-IP-

ADDR/RTRV-IP-ADDR (IP Address Information)
IF_NAME The name of the interface to be set with the IP address. Enter the name of
the interface grown. For example, in case of IPsec outer IP with VLAN 100,
enter ge_0_0_0.100. In case of IPsec inner IP, it is vpn0, vpn1 or vpn2.
IP_ADDR The IP address to be set.
IP_PFX_LEN The prefix length of the IP address determining the network mask. If the
network mask is 255.255.255.0, the length is 24.
IP_GET_TYPE The IP address setting method.
• STATIC: The user manually enters the IP address.
• IPSEC: The IP address which is assigned by SeGW when VPN tunnel is
setup (RTRV ONLY)
TUNNEL_GROUP_ID The Group ID of IPSec Tunnel. (Retrieval only)
OAM Attribute of the IP address, whether to use the IP address entered for OAM.
• False: The IP address is not used for OAM.
• True: The IP address is used for OAM.
LTE_SIGNAL_S1 Attribute of the IP address. Whether to use the IP address entered for S1
signals.
• False: The IP address is not used for S1 signals.

Confidential
• True: The IP address is used for S1 signals.
LTE_SIGNAL_X2 Attribute of the IP address. Whether to use the IP address entered for X2
signals.
• False: The IP address is not used for X2 signals.
• True: The IP address is used for X2 signals.
LTE_BEARER_S1 Attribute of the IP address. Whether to use the IP address entered for S1
bearer.
• False: The IP address is not used for S1 bearer.
• True: The IP address is used for S1 bearer.
LTE_BEARER_X2 Attribute of the IP address. Whether to use the IP address entered for X2
bearer.
• False: The IP address is not used for X2 bearer.
• True: The IP address is used for X2 bearer.
Parameter Descriptions of CHG-SYS-SIGIP/RTRV-SYS-SIGIP (System

Signaling IP Information)
TUNNEL_GROUP_ID The Group Id of IPSec Tunnel
SIG_IPVER The IP version for Signal (Retrieval only)
S1_PRI_IPV4_ADDR The primary IPv4 address for S1 signal (Retrieval only). It is same as IPsec
inner IP.
S1_SEC_IPV4_ADDR The secondary IPv4 address for S1 signal (Retrieval only).
X2_PRI_IPV4_ADDR The primary IPv4 address for X2 signal (Retrieval only). It is same as IPsec
inner IP.
X2_SEC_IPV4_ADDR The secondary IPv4 address for X2 signal (Retrieval only).
S1_PRI_IPV6_ADDR The primary IPv6 address for S1 signal (Retrieval only).
S1_SEC_IPV6_ADDR The secondary IPv6 address for S1 signal (Retrieval only).
This is for IPv6.
X2_PRI_IPV6_ADDR The primary IPv6 address for X2 signal (Retrieval only).
This is for IPv6.
X2_SEC_IPV6_ADDR The secondary IPv6 address for X2 signal (Retrieval only).
This is for IPv6.
Counters and KPIs

with this feature.
REFERENCE
Confidential
UTRAN); S1 signaling transport

UTRAN); S1 Application Protocol (S1AP)
[4] 3GPP TS29.281, General Packet Radio System (GPRS) Tunneling Protocol
User Plane (GTPv1-U)
[5] IETF RFC4960, Stream Control Transmission Protocol

Confidential
LTE-SW0502, NAS Signaling Transport

INTRODUCTION
An eNB supports transfer of NAS signaling messages between an MME and a UE.
BENEFIT
This feature allows the eNB to transfer NAS signaling messages between the
MME and the UE.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The NAS Signaling Transport function provides means to transport the NAS
message (for example, NAS mobility management) for a specific UE on the S1-
MME interface. For this objective, eNB creates UE-associated logical S1
connection on the S1 interface, which means that the eNB allocates eNB UE S1AP
ID and the MME allocates MME UE S1AP ID to a specific UE. In addition, the
eNB relays NAS message of S1AP layer transparently between the UE and the
MME.
There are four types of NAS signaling transport messages between the eNB and
the MME.
Initial UE Message (eNB to MME)

If the eNB receives a UL NAS message from UE when there is no UE related
logical S1 connection, it transmits Initial UE Message to MME to create a new
UE-associated logical S1 connection.

Confidential
Downlink NAS Transport (MME to eNB)

After creation of logical UE-associated S1 connection, MME NAS signaling
message is encapsulated with NAS PDU IE of Downlink NAS Transport message
and transmitted to UE. For example, E-RAB Setup Request, E-RAB Modify
Request, or E-RAB RELEASE COMMAN from MME is encapsulated with
Downlink NAS Transport message and delivered to UE.
Uplink NAS Transport (eNB to MME)

Similar to Downlink NAS Transport, UE NAS Signaling message is encapsulated
with NAS PDU IE of Uplink NAS Transport message and transmitted to MME.
NAS Non-Delivery Indication (eNB to MME)

When eNB cannot process a message received from the MME, it adds the received
NAS message to the NAS PDU IE of NAS Non Delivery Indication and also an
appropriate cause value and then transmits the NAS Non Delivery Indication
message to the MME.

Confidential
Because this NAS Signaling Transport is performed on UE specific basis and eNB
relays the NAS messages transparently, this document does not describe the
details.
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TS36.412: Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); S1 signaling transport

Confidential
LTE-SW0503, MME Overload Control

INTRODUCTION
An eNB cooperates with MME to handle the overload situation of the MME. The
S1 overload control procedure is used as defined in the 3GPP standard. When an
overloaded MME sends an S1 Overload Start message to an eNB with Overload
Action IE, the eNB restricts the RRC connection requests towards the overloaded
MME.
BENEFIT
Signaling load can be reduced towards the overloaded MME.
DEPENDENCY
• Interface & Protocols: S1-AP
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature is a MME driven overload control and eNB helps MME reduce
signaling traffic in the overload status reactively.
The MME can inform the eNB of its overload status by sending the Overload Start
and the Overload Stop messages. In this section, how these messages are used to
control MME overload between the MME and the eNB is explained.
When the MME wants to reduce the signaling load, it sends the Overload Start
message to the eNB and the eNB receiving this message assumes that the MME
from which it receives the message as being in an overloaded state.
Figure below depicts the overload start procedure by MME.

Confidential
For overload control, the MME includes relevant overload action IE in

OVERLOAD START message as per its overload criteria.
The Overload Action IE value defines what sorts of Overload Action will be set
when the MME sends the Overload Start message to eNB. The eNB stores this
Overload Action for the concerned MME and processes new RRC connection
request based on this setting, so that the eNB ensures that only signaling traffic
corresponding to permit RRC connections is sent to the overloaded MME.
When the UE requests to establish an RRC connection by sending the
RRCConnectionEstablishmentRequest message, it sets one of five
EstablishmentCause (emergency, highPriorityAccess, mt-Access, mo-Signaling,
mo-Data, mo-VoiceCall, delayTolerantAccess).
Table below summarizes how the eNB decides to reject or permit this
RRCConnectionRequest based on the EstablishmentCause against the Overload
Action received from MME explained above. When the eNB rejects the UE
requested RRC connection, it includes waitTime in the RRCConnectionReject
message to inform UE of back off time to retry
RRCConnectionEstablishmentRequest. The waitTime is a configurable parameter
T302 by using CHG-TIME-INF.
Table below outlines the overload action codes of eNB-processing per MME.
Overload Action eNB Processing
Reject all RRC connection • The eNB rejects RRC connection establishment if the EstablishmentCause
establishments for non- is mo-Data, mo-VoiceCall, and delayTolerantAccess.
emergency MO DT • The eNB permits RRC connection establishment if the
EstablishmentCause is one of emergency, highPriorityAccess, mt-Access,
and mo-Signaling.
Reject all RRC connection • The eNB rejects RRC connection establishment if the EstablishmentCause
establishments for Signaling is mo-Data, mo-Signaling, mo-VoiceCall, and delayTolerantAccess.
• The eNB permits RRC connection establishment if the
EstablishmentCause is one of emergency, highPriorityAccess, and mt-
Access.
Permit Emergency Sessions • The eNB rejects RRC connection establishment if the EstablishmentCause
and mobile terminated is one of highPriorityAccess, mo-Signaling, mo-Data, mo-VoiceCall, and
services only delayTolerantAccess.
EstablishmentCause is emergency or mt-Access.
Permit High Priority Sessions • The eNB rejects RRC connection establishment if the EstablishmentCause
and mobile terminated is one of emergency, mo-Signaling, mt-Data, mo-VoiceCall, and
services only delayTolerantAccess.
EstablishmentCause is highPriorityAccess or mt-Access.
Reject delay tolerant access The eNB rejects RRC connection establishment only if the

Confidential
Overload Action eNB Processing

EstablishmentCause is delayTolerantAccess and otherwise, permits.
While the MME is overloaded, according to overload level change at MME, the
MME controls whether or not to send an additional Overload Start/Stop message
with its overload action to the eNBs that have already received the Overload Start
message before.
Figure below depicts the overload stop procedure by MME.
The eNB receiving the OVERLOAD STOP message assumes that the overload
situation at the MME from which it receives the message has ended and resumes
normal operation towards this MME.
After the eNB receives the Overload Stop message from the MME, it updates the
overload status of this MME as normal and transmits to this unloaded MME
regardless of EstablishmentCause of RRC connection request.
SYSTEM OPERATION
How to Activate
Key Parameters
parameter.
Parameter Descriptions of RTRV-TIME-INF/CHG-TIME-INF (MME
Information)
T302 This parameter is the timer value which the UE starts after receiving the RRC
Connection Reject message. It is released when the UE becomes the RRC
Connect status, or a cell is reselected.

Confidential
Counters and KPIs

with this feature.
REFERENCE
[3] 3GPP TS36.331: E-UTRAN; Radio Resource Control (RRC); Protocol
specification

Confidential
LTE-SW0504, MME Selection and Load

Balancing
INTRODUCTION
The MME Selection and Load Balancing feature allows an eNB to assign an MME
for a new attach request from UE, considering MME's capacity among the MMEs.
The UE that has already registered to the MME is assigned to the same MME.
BENEFIT
Load is evenly distributed over multiple MMEs according to their relative capacity
while the UE can keep assigned to the same MME.
DEPENDENCY
• Interface & Protocols: S1-AP and SCTP
• Prerequisite Features: LTE-SW0501, S1 Interface Management
LIMITATION
None
SYSTEM IMPACT
capabilities.
Related Feature: LTE-SW5001 Multi-PLMN Support
This feature is related to the LTE-SW5001 feature since the eNB selects the most
appropriate MME not only based on Relative MME Capacity (RMC) but also
based on matching result of served PLMN list of MME and selected PLMN by
UE.
None
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
When the eNB receives an RRC connection request message from UE, it searches
and selects MME that has served the UE before. The selection is based on S-TMSI
information from RRC Connection Request message or registered MME
information from RRC Connection Setup Complete message. Otherwise, the eNB
performs load-based MME selection function for a new call that has no such
information in RRC messages.
The eNB selects the MME by weighted round robin method where Relative MME
Capacity (RMC) is considered as a weight. The RMC is relative processing
capacity of MME with respect to other MMEs to load-balance MMEs.
The MME has responsibility in deciding its capacity (0 - 255) relative to other
MMEs and informs the eNB of its RMC via S1 Setup Response or MME
Configuration Update message and then, the eNB stores this value and uses for
load balancing.
Figure below depicts the MME selection and load balancing procedure for a new
call.
1 The UE transmits S-TMSI information in the RRC Connection Request

message or registered MME information in the RRC Connection Setup
Complete message during the RRC connection setup procedure.
The UE does not provide the registered MME information when it does power-on
or it wants to change the registered MME.

Confidential
For the idle to active, the UE provides the registered MME information.
2 The eNB performs MME selection when it receives the RRC Connection
Request or the RRC Connection Setup Complete message from the UE.
If S-TMSI of the RRC Connection Request message indicates a valid MME,
the eNB select that MME. Otherwise, the eNB selects the MME based on the
registered MME from Connection Setup Complete message.
Firstly, the eNB determines whether to allocate a new MME to the UE or to
find and allocate the MME which the UE had been allocated.
If it is necessary to allocate a new MME, the eNB selects MME in proportion
to the MME capacity to distribute loads.
This load balancing among MMEs is based on RMC information.
3 After the decision of the most proper MME, the eNB transmits Initial UE
Message to the specified MME to create UE-associated S1 connection. After
the UE-associated S1 connection is created with the MME successfully, all of
the following signaling messages are sent to this chosen MME.
If the MMEs indicated by S-TMSI or registered MME are not available, the
eNB operates in accordance with one of the following options:
o No MME relocation: The eNB just rejects or releases the RRC connection.
o MME relocation by loadBalancingTAU: The eNB releases RRC
connection with cause=loadBalancingTAUrequired.
o Direct MME relocation: The eNB selects appropriate MME based on UE's
selected PLMN after RRC connection setup complete.
The operation option of eNB is configured by MME_SELECTION_MODE using
CHG-OVLD-PTC.
Enhancement for eMTC and NB-IoT

• For the dedicated MME for eMTC or NB-IoT, the eNB selects a new MME
that its configured service purpose matches with UE type (LTE, eMTC, or
NB-IoT). The service purpose of the MME can be configured by
SERVICE_PURPOSE using CHG-MME-CONF.
• For the CIoT EPS Optimization, the eNB selects a new MME that its
configured CIoT EPS optimization capability matches best with CIoT EPS
optimization of UE support indication in the RRCConnectionSetupComplete
message. The CIoT EPS optimization of MME capability can be configured
by CP_OPTIMIZATION_SUPPORT, UP_OPTIMIZATION_SUPPORT, and
ATTACH_WITHOUT_PDN_CONNECTIVITY using CHG-MME-CONF.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
Activation Procedure/Deactivation Procedure
Key Parameters
parameters.
Parameter Descriptions of CHG-OVLD-PTC/RTRV-OVLD-PTC (MME
Information)
MME_SELECTION_MODE This parameter indicates MME selection mode during the
establishment.
The available MME selection modes are as below.
• NO_MME_RELOCATION: If the MME corresponding to MMEC of S-
TMSI and registeredMME is overload status then eNB immediately
sends RRCConnectionRelease with the release cause of other.
• LOAD_BALANCING_TAU: If the MME corresponding to MMEC of S-
TMSI and registeredMME is overload status then eNB immediately
sends RRCConnectionRelease with the release cause of
loadBalancingTAUrequired.
• DIRECT_MME_RELOCATION: If the MME corresponding to MMEC
of S-TMSI and registeredMME is overload status then eNB selects
one of available MMEs supporting the selected PLMN of UE.

Confidential
Parameter Descriptions of CHG-MME-CONF/RTRV-MME-CONF (MME

Information)
The visibility of those parameters depend on each system type that can support
whether NB-IoT/eMTC or not.
SERVICE_PURPOSE This parameter defines the service type of the MME.
CP_OPTIMIZATION_SUPPORT This parameter indicates that the MME can service control plane
optimization.
UP_OPTIMIZATION_SUPPORT This parameter indicates that the MME can service user plane
optimization.
ATTACH_WITHOUT_PDN_CONN This parameter indicates that the MME can service Attach without PDN
ECTIVITY Connectivity.
Counters and KPIs

with this feature.
REFERENCE
UTRAN); Radio Resource Control (RRC); Protocol specification.

Confidential
LTE-SW0505, Random Delayed S1 Setup for

Load Distribution
INTRODUCTION
With this feature, when an MME recovers from failure, an eNB calculates a
random back off time value and waits for back off timer value, and then sends the
first S1Setup Request after the successful SCTP association. The eNB then starts
the random back off timer. In case of no response for random back off timer
duration, the eNB retransmits S1 Setup Request. This process repeats until eNB
has sent the maximum number of S1 Setup Requests as configured by the operator.
The random back off time value exponentially delays and distributes the arrival of
S1 Setup Requests at the MME from various eNBs.
Do not enable this feature if the MME is performing S1AP randomization by

randomizing TIME TO WAIT IE for different eNBs.
BENEFIT
• Prevents MME overload due to simultaneous S1 Setup Request attempts.
• The eNBs attempting to establish S1 AP connection are serviced efficiently.
DEPENDENCY
• Prerequisite Features: LTE-SW0501, S1 Interface Management
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
Due to random backoff of each eNB for S1 Setup Request, it may experience
longer S1 Setup latency than the one without random backoff.

Confidential
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Normal Startup Operation

In the normal mode of startup operation (such as eNB initialization or reset), the
eNB after sending the first S1 Setup Request waits for the configured S1_SETUP
time (default value is 5 s) for S1 Setup Response or S1 Setup Failure message
from the MME.
If there is no response from the MME for S1_SETUP time, the eNB will
retransmit S1 Setup Request again without applying any additional delay. This
operation is performed whether Random delay distribution feature is enabled or
not.
Random Backoff method during MME Outage and no S1 Setup Response

During scenarios such as MME outage and recovery, if Random Delayed S1 Setup
for Load Distribution feature is enabled, the eNB will calculate a random back off
time value and start an additional Random Back off wait timer.
The eNB calculates the Random Back off time in units of milliseconds and as
function of eNB ID, current timestamp, configurable parameters
initialBackoffValue and an internal counter setupRetryCount. Following formula
is used to calculate the Random Back off time:
• The base random number is generated using the eNB ID and time stamps as
the seeds.
• The generated random number is further controlled by initialBackoffValue and
Setup Retry Count using a modulo operation.
• The eNB uses setupRetryCount as an internal counter and increases the
counter by 1 for every S1 Setup Request retry attempt with Random back off
time.
• The Setup retry counter exponentially increases the initial Back Off Value as
shown in the formula above.
• If the initialBackoffValue is set to zero then randomized back off timer
calculation is disabled. The default value of initialBackoffValue parameter is 2
and the range is 0 to 600.
• The parameter maxExponentialRange is used to limit Setup Retry Count. The
default value of maxExponentialRange is 6 and the range is 0 to 100.

Confidential
• The Setup retry internal counter is used to compare against the

maxExponentialRange parameter to determine the allowed number of retry
attempts. When Setup retry count reaches maxExponentialRange, Setup retry
count resets to 0 again and thus, S1 setup request is sent again with Backoff
time calculated by Setup retry count = 0.
Upon expiration of this timer, the eNB transmits the S1 Setup Request message.
After transmission, the eNB calculates an additional exponential Random backoff
wait timer. The eNB retransmits S1 Setup Request after expiration of this random
back off wait timer. This process is repeated until the maximum retransmission
count is reached. Hence, with this random backoff process, the S1 Setup Requests
arrival at MME is distributed, thereby reducing the chance of overload at MME.
In figure below, multiple eNBs are attempting to establish S1AP connection with
the MME at the same time, which results in overload at the MME. However, by
applying Random Backoff time, the S1 Setup Request arrival at the MME is
distributed.
Random back off time when eNB receives S1 Setup Failure during MME Outage
During an MME Outage, if the eNB receives S1 Setup Failure message without
TIME TO WAIT IE, the eNB starts Random Back off timer and waits for random
back off time for every re-transmission of S1 Setup Request. If the eNB receives a
S1 Setup Failure message with TIME TO WAIT IE, the eNB waits for time
specified by TIME TO WAIT IE for further retransmission of S1 Setup Request
and will not use Random Back off timer.
Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-S1SB-CONF and set S1_SETUP_BACKOFF_ENABLE to ON.
• Run CHG-S1SB-CONF and set S1_SETUP_BACKOFF_ENABLE to OFF.
Key Parameters
feature.
parameters.
Parameter Descriptions of CHG-S1SB-CONF/RTRV-S1SB-CONF
S1_SETUP_BACKOFF_ENA This parameter indicates ON/OFF state of S1 SETUP BACKOFF. It has a
BLE value of 0 or 1, the default is 1. The 0 means OFF state of S1 SETUP
BACKOFF, whereas the 1 means ON.
• 0: OFF
• 1: ON (default)
MAX_EXPONENTIAL_RANG This parameter indicates an increasable range of exponential. The range is 1
E to 100, and the default is 6.
INITIAL_BACKOFF_VALUE This parameter indicates initial backoff used in calculation of backoff time.
The range is 0 to 600, and the default is 2.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.413: Evolved Universal Terrestrial Access Network (E-UTRAN);
Confidential
LTE-SW0506, eNB Configuration Update

INTRODUCTION
The eNB Configuration Update procedure is to update application level
configuration data needed for two eNBs to interoperate correctly over the X2
interface.
BENEFIT
Update application level configuration data between two eNBs to interoperate
correctly over the X2 interface.
DEPENDENCY
• Required Network Elements: Neighbor eNB
• Prerequisite Features: This feature is available when the LTE-SW0521 (X2
Interface Management) feature is enabled.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
This function is used when application level data needs to be updated between two
eNBs interacting over the X2 interface. (Application level data includes served cell
information, neighbor information, and GU group ID list.)
If the eNB recognizes the PLD has been changed in the LSM, it checks whether
the changed PLD requires an update of the application level data. If necessary, it
performs the X2AP eNB Configuration Update procedure.
Successful Operation

Confidential
1 An eNB1 initiates the procedure by sending an ENB CONFIGURATION

UPDATE message to an eNB2. Such message contains served cell
information, neighbor information, MultibandInfoList, and GU group ID list
information, and so on.
2 When the eNB2 receives the ENB CONFIGURATION UPDATE message, it
stores the information contained and sends ENB CONFIGURATION
UPDATE ACKNOWLEDGE message back to the eNB1.
Unsuccessful Operation
If an eNB cannot accept the update, it shall respond with an ENB

CONFIGURATION UPDATE FAILURE message and appropriate cause value.
If the Time to Wait IE is included in ENB CONFIGURATION UPDATE
FAILURE, the eNB1 shall wait at least for the indicated time before reinitiating
the eNB Configuration Update procedure to the same eNB2.
If the eNB1 receives neither ENB CONFIGURATION UPDATE
ACKNOWLEDGE message nor ENB CONFIGURATION UPDATE FAILURE
message after sending ENB CONFIGURATION UPDATE message, the eNB1
reinitiates the eNB Configuration Update procedure toward the eNB2.
The operator can configure relevant parameters below for eNB Configuration
Update procedure using CHG-TIMER-INF.
• X2UpdateTimeToWait for 'Time to Wait' IE
• x2Update timer for waiting ENB CONFIGURATION UPDATE
ACKNOWLEDGE/FAILURE after transmitting the ENB CONFIGURATION
UPDATE message
• x2UpdateRetryCount for maximum number of retransmission of ENB
CONFIGURATION UPDATE message to the same peer eNB when the
x2Update timer expiration
SYSTEM OPERATION
How to Activate

Confidential
Key Parameters
The timer and retransmission counter for X2 eNB Configuration Update procedure
is configurable.
x2Update This parameter is the waiting time to receive the
ENBConfigurationUpdateAcknowledge message or ENBConfigurationUpdateFailure
message after the ENBConfigurationUpdate message is transmitted from the eNB to
another eNB that is designated as a neighbor.
x2UpdateRetryCount This parameter is the number of times that the X2 ENBConfigurationUpdate procedure
should be attempted again when Timeout occurs because the
ENBConfigurationUpdateFailure message is received or
ENBConfigurationUpdateAcknowledge message is not received from another eNB
after the X2 ENBConfigurationUpdate message has been transmitted from the eNB.
x2UpdateTimeToWait This parameter is the TimetoWait value included in the
ENBConfigurationUpdateFailure message transmitted by the eNB that has received
the ENBConfigurationUpdate message. The eNB that has received the TimeToWait
information re-transmits the ENBConfigurationUpdate message after waiting for the
TimeToWait time.
Counters and KPIs

with this feature.
REFERENCE
UTRAN); S1 application protocol (S1AP)

Confidential
LTE-SW0508, Traffic Load Reduction for MME

Overload Control
INTRODUCTION
The Traffic Load Reduction IE is introduced in 3GPP Rel-10 in the Overload Start
message. This message, from MME to eNB, controls how much portion of the
signaling traffic should be dropped based on the MMEs overload status. The value
of this IE, from 0 % to 99 %, indicates at which ratio the eNB is going to reduce
the signaling traffic by rejecting the signaling request.
BENEFIT
With this feature, the MME can inform the eNB precisely how much the eNB
should reduce the signaling load towards the concerned MME under load
condition.
DEPENDENCY
• Prerequisite Features: LTE-SW0503, MME Overload Control
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
When the MME is under overload status, it can inform the eNB to reduce the
signaling load towards the concerned MME through the Overload Start message.
Until Release 9, the Overload Start message has included only Overload Action,
which defines reject or permit action per each type of RRC Connection
Establishment request causes under MME overload status.
In Release 10, the Traffic Load Reduction Indication IE is introduced in the
Overload Start message from MME to eNB, as described in table below.

Confidential
IE/Group Presence Range IE type and Semantics Criticality Assigned

Name reference description Criticality
Message Type M - 9.2.1.1 - YES ignore
Overload M - 9.2.3.19 - YES reject
Response
GUMMEI List - 0..1 - YES ignore
> GUMMEI List - 1.. - EACH ignore
Item
>> GUMMEI M - 9.2.3.9 - - -
Traffic Load O - 9.2.3.36 - YES ignore
Reduction
Indication
The Overload Response IE and the GUMMEI IE are existing IEs, and the Traffic
Load Reduction Indication IE is newly added in Release 10.
The Overload Response IE is defined in table below.
IE/Group Name Presence Range IE type and reference Semantics
description
CHOICE Overload Response - - - -
> Overload Action - - - -
>> Overload Action M - 9.2.3.20 -
The Overload Action IE can have the following options, as specified in 3GPP TS
36.413:
• Reject RRC connection establishments for non-emergency MO DT
• Reject RRC connection establishments for Signaling
• Permit Emergency Sessions and mobile terminated services only
• Permit High Priority Sessions and mobile terminated services only
• Reject delay tolerant access
The Traffic Load Reduction Indication IE is defined in table below.
description
Traffic Load Reduction M - INTEGER (1..99) -
Indication
This indicates that the percentage of the type of traffic relative to the instantaneous
incoming rate at the eNB, as indicated in the Overload Action IE, to be rejected.
For example, if the eNB receives the Overload Start message with Overload action
= Reject RRC connection establishments for non-emergency MO DT and Traffic
Load Reduction Indication = 30 % from MME1, the following happens:
• The eNB does not reject all the RRC connection establishment requests for
non-emergency MO DT going to MME1.

Confidential
• The eNB rejects only 30 % of them based on Traffic Load Reduction

Indication received from MME1.
If the MME1 does not include the Traffic Load Reduction Indication IE in
Overload Start, the eNB considers only Overload Action in Overload Start. In this
case, the eNB rejects all of RRC connection establishment requests for non-
emergency MO DT going to MME1.
SYSTEM OPERATION
How to Activate
• When the MME supports Release-10 Traffic Load Reduction function, this
feature is activated by including Traffic Load Reduction Indication IE in S1AP
Overload Start message.
Key Parameters
Counters and KPIs

RRC connection ConnEstabReject_S1apMmeOvld A call cannot be accepted due to MME
establishments overload during RRC establishment.
REFERENCE
None

Confidential
LTE-SW0510, Geo Redundancy of MME

INTRODUCTION
This feature is a part of S1-flex of 3GPP complaint feature, which allows eNB to
interoperate with multiple MMEs for redundancy and high availability. It enables
an operator to configure a pool of active and standby MMEs. The eNB selects a
standby MME for new UEs when all the active MMEs are down.
BENEFIT
With this feature, the operator can explicitly configure a group of standby MMEs
to use only when all the active MMEs are out of service.
From SLR4.5, the eNB selects standby MMEs based on their Relative MME
Capacity (RMC) values. In addition, user can precisely control the frequent
selection of certain standby MMEs using their RMC value, thereby increasing the
service availability and reducing OPEX.
DEPENDENCY
Prerequisite Features: LTE-SW0504, MME Selection and Load Balancing
LIMITATION
• The eNB supports up to 16 MMEs including both active and standby MMEs.
• Load balancing between MMEs is based on relative capacity information that
the MMEs provide through S1AP interface.
SYSTEM IMPACT
FEATURE DESCRIPTION
The S1-flex feature of Samsung enables eNB to be connected with a pool of active
and standby MMEs. The eNB sets up a dedicated S1 connection with the active
MME when UE connects to the network. If all the active MMEs are down, S1-flex
provides high availability by allowing the eNB to route the UE signaling messages
to the standby MME. When the failed MMEs become active and take over the
functional role, the eNB establishes the new calls with the active MMEs and
maintains the ongoing calls with the standby MME.
Samsung eNB can have connections with up to 16 MMEs belonging to any MME
pool. Within the 16 MMEs, eNB can be eNB 11 of overlapping area and either
eNB 10 of MME Pool Area 1 or eNB 12 of MME Pool Area 2, as depicted in
figure below.

Confidential
In this scenario:
• The eNB 1 to 11 are connected to MME 1, MME 2, and MME 3 from MME
Pool Area 1.
• The eNB 11 to 16 are connected to MME 4, MME 5, and MME 6 from MME
Pool Area 2.
• The eNB 11 is at Overlapping Area and is active for both the pools.
Selecting a Standby MME

The eNB selects the active MMEs based on their RMC and backup mode
configuration. It receives the processing capacity relative to other MMEs from the
serving MME through RMC IE after setting up the dedicated S1-MME
connection.
Before SLR 3.1, the standby MME method was not included in the feature. To
support the standby MME configuration, the BACKUP_MODE (CHG-MME-CONF)
parameter is introduced in SLR 3.1. With this parameter, the operator can set the
backup mode of the MME to active or standby, among the connected MMEs.
In case of backward compatibility, the standby MME selection criteria from
multiple standby MMEs is enhanced.
Table below outlines a brief description of each selection criteria introduced after
SLR 3.1:
Software Release Standby MME Condition Standby MME Selection Scenario
Version Criteria
Before SLR 3.1 Prior to SLR 3.1 package, Not applicable In the Figure 1, eNB 11
Samsung eNB does not considers all six MMEs,
support the configuration of MME 1 to MME 6, as
standby MME, which equally active if their RMC
implies the eNB cannot value is greater than zero
continue services if all the and S1 SCTP connections
active MMEs are down. are active.

Confidential
Software Release Standby MME Condition Standby MME Selection Scenario

Version Criteria
SLR 3.1 The eNB decides whether • BACKUP_MODE (CHG- See section Standby MME
MME is operating as MME-CONF) = Standby Selection in SLR 3.1
standby based on either of
• RMC = 0
these conditions:
• BackupMode = Standby
• RMC = 0
SLR 4.5 The eNB decides whether • BACKUP_MODE (CHG- See section Standby MME
MME is operating as MME-CONF) of MME is Selection in SLR 4.5
standby under the standby
conditions:
• If there is no MME that
• At first, the eNB checks meets the first condition,
whether the backup then the eNB checks the
mode of MME is standby. RMC value is zero.
• If there is no MME that
meets the first condition,
then eNB checks whether
the RMC value is zero.
Selecting a Standby MME in SLR 3.1

Figure below depicts the a scenario where MME 1, MME 2, and MME 3 are
configured as active, while MME 4, MME 5, and MME 6 are configured as
standby at eNB 11. The standby MME is selected among MME 4, MME 5, and
MME 6 when all the active MMEs are down.

Confidential
Similarly, when there are multiple standby MMEs configured, the eNB selects the
final MME among the standby MMEs by round robin method.
Figure below depicts a scenario where eNB 11 selects the final standby MME by
round robin approach among the standby MMEs, MME 1, MME 2, and MME 5, if
all active MMEs, MME 3, MME 4, and MME 6 are down.

Confidential
Selecting a Standby MME in SLR 4.5

Figure below depicts a scenario where MME 3, MME 4, and MME 6 are
configured as active, while MME 1, MME 2, and MME 5 are configured as
standby at eNB 11. The standby MME is selected by weighted round robin
approach among MME 1, MME 2 and MME 5 when all of MM3, MME4, and
MME6 are down.

Confidential
Selecting a Standby MME within the MME Pool

This feature can be used to configure standby MMEs within the same MME pool.
Figure below depicts the scenario where MME 3 and MME 1 are configured as
standby MME at eNB 1 and eNB 10 respectively, belonging to same MME Pool
Area 1. eNB1 uses MME 3 only when both MME 1 and MME 2 are down and
eNB 10 uses MME 1 only when both MME 2 and MME 3 are down.

Confidential
Configuring Symmetric Standby MME

Samsung eNB allows configuration of standby MMEs from different MME pools
of other geographical zones. With this type of configuration, the operator can set
the standby MMEs for a pool of active MMEs, which are located at the different
zones.
Figure below depicts a typical scenario where MME Pool 1 and MME Pool 2
serve as standby MMEs for each other symmetrically.
SYSTEM OPERATION
How to Activate

Confidential
Preconditions
• To configure a specific MME as a standby MME (for geo redundancy backup-
mode), set BACKUP_MODE of the corresponding MME to Standby.
• To configure all MMEs as active (for geo redundancy backup-mode), set
BACKUP_MODE of the corresponding MME to Active.
Key Parameters
parameter.
BACKUP_MODE This parameter defines MME backup mode type.
parameters.
that can be connected to an eNB, the index range is 0 to 15.
STATUS The EQUIP status information on MME.
• EQUIP: The MME to connect exists
ACTIVE_STATE The state information on the specified MME in operation. Of the MMEs for
which the S1 Setup is established, if there is an undesired MME, this
parameter value must be changed to Inactive. The default is active. If the
STATUS parameter is set to Equip, it is better not to change this parameter
value to inactive.
• Inactive: MME is not used for S1.
• Active: MME is used for S1.
BACKUP_MODE This parameter defines MME's backup mode type.
Counters and KPIs


Confidential
with this feature.
REFERENCE

Confidential
LTE-SW0513, User Location Report at Call

Release
INTRODUCTION
When an E-RAB or a data session is dropped, an eNB can send the rough location
of UE to core network (MME) through S1 interface. The ECGI and TAI are
included in the message of E-RAB Release Response, E-RAB Release Indication,
and UE Context Release Complete. This feature is included in 3GPP Release 12.
BENEFIT
An operator can verify the user location (ECGI/TAI) when call is released. The
user location information can be used for call performance analysis, user QoE
analysis and proper billing reconciliation.
DEPENDENCY
• Radio Technology: E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
When the E-RAB or the data session is dropped, the most up-to-date user location
information is needed from the RAN side for call performance analysis, User QoE
analysis, and proper billing reconciliation. Therefore, in 3GPP release 12, addition
of User Location Information (E-UTRAN CGI and TAI) in the following
messages of three S1AP procedures is supported:
• E-RAB Release Response
• E-RAB Release Indication
• UE Context Release Complete

Confidential
E-RAB Release Procedure E-RAB Release Indication Procedure UE Context Release Procedure
eNB MME eNB MME eNB MME

E-RAB Release UE Context Release
Command E-RAB Release Command
E-RAB Release Indication UE Context Release
Response (User Location Complete
(User Location Information) (User Location
Information) Information)
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-CELLPLMN-INFO/RTRV-CELLPLMN-INFO
CELL_IDENTITY This parameter defines cell Identity.

TRACKING_AREA_CODE This parameter is the Tracking Area Code (TAC) used in an operating cell. It
is used for broadcasting and stopping warning messages while paging to the
UE. This information is broadcasted to the UE through SIB1.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.413 Release 12: Evolved Universal Terrestrial Radio Access
Network (E-UTRAN); S1 Application Protocol (S1AP)

Confidential
LTE-SW0514, Dedicated Core Network Support

INTRODUCTION
An operator can deploy Dedicated Core Networks (DCNs) to provide specific
services for specific types of UEs or subscribers, for example, Machine-Type
Communications (MTC) devices or subscribers belongs to a specific enterprise.
For routing or maintaining the specific subscribers to their respective DCNs, an
eNB supports an NAS message redirection procedure.
The eNB triggers the NAS message redirection procedure at receiving request
from MME. The MME provides the related information for eNB to select new
MME for the UE, that is, MME group ID (additional GUTI can be included
optionally). The eNB then selects a target MME among MMEs supporting the UE
selected PLMN for NAS message redirection using the provided information from
MME.
BENEFIT
The operator can allocate their subscribers to an appropriate DCN, and provide
specific services to the subscribers.
DEPENDENCY
• Required Network Elements: The MME should support Rel-13 NAS message
redirection procedure.
• Interface & Protocols: S1AP (3GPP TS 36.413 v13.1.0 and onwards)
• Prerequisite Features: LTE-SW0504, MME Selection and Load Balancing
LIMITATION
None
SYSTEM IMPACT
capabilities.
Related Feature: LTE-SW0504, MME Selection and Load Balancing
The MME selection and load balancing is a prerequisite feature of Dedicated Core
Network Support and its MME selection criteria is re-used by Dedicated Core
Network Support feature. However, there are differences between two features
because the provided information in the REROUTE NAS REQUEST message is
used and prioritized than the MME selection criteria in case of Dedicated Core

Confidential
Network Support feature.

None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
In case the operator deploys DCNs to provide specific services for specific types
of UEs or subscribers, for example, MTC devices or subscribers belongs to a
specific enterprise, the MME and the eNB need to support NAS message
redirection procedure for routing or maintaining the specific subscribers to their
respective DCNs.
If this feature is activated (DCN_ENABLE of CHG-ENB-INF is set to TRUE),
the eNB supports NAS message redirection procedure according to following.
NAS Message Redirection Procedure

When the first MME receives S1 INITIAL UE MESSAGE from eNB for a
subscriber, it decides whether to reroute the subscriber to an appropriate MME or
not. If rerouting is required, the MME sends an S1 REROUTE NAS REQUEST
message to the eNB with the related information for eNB to select the second
MME.
The eNB triggers the NAS message redirection procedure at receiving the request
from first MME, that is, S1 REROUTE NAS REQUEST message.
First, the eNB selects a new MME among MMEs supporting the UE selected
PLMN using the provided information from MME, that is, the MME Group ID
corresponding to an appropriate DCN for the UE and additional GUTI, if
available.
The eNB then sends S1 INITIAL UE MESSAGE to the second selected MME
and performs the remaining procedure according to MME’s response.

Confidential
eNB First MME Second MME
Initial UE Message {NAS PDU}
Reroute NAS Request MME group ID,

Additional GUTI (optional)
Select Second MME based on the

received MME info. MME group ID,
Additional GUTI (optional)
Initial UE Message
{NAS PDU} + MME group ID
1 After completion of RRC Connection Establishment procedure, the eNB

selects a MME for UE (refer to LTE-SW0504).
The eNB then sends S1 INITIAL UE MESSAGE to the first selected MME.
2 The eNB receives the S1 REROUTE NAS REQUEST message from the first
MME.
The S1 REROUTE NAS REQUEST message contains MME Group ID
corresponding to the DCN and original S1 Message. Also, the Additional
GUTI can be included in the message.
3 The eNB selects the second MME among MMEs supporting the UE selected
PLMN using the provided information from the first MME in step 2.
For eMTC UEs, the eNB selects an eMTC capable MME as the second MME.
The operator can configure whether each MME is eMTC capable or not (refer
to LTE-SW0504, MME selection and load balancing).
For NB-IOT UEs, the eNB selects an NB-IOT capable MME as the second
MME. The operator can configure whether each MME is NB-IOT capable or
not (refer to LTE-SW0504, MME selection and load balancing).
When selecting a new MME for NAS message redirection, the eNB excludes
the first MME.
If there are no candidate MMEs to be selected, the eNB selects the first MME
as the second MME for the NAS message redirection.
4 The eNB sends S1 INITIAL UE MESSAGE to the second selected MME.
5 If the eNB receives an appropriate first downlink S1 message from MME, it
performs the remaining procedure according to the received S1 message.
At this time, the eNB collects the counters for the results of S1 signaling
connection setup procedure, that is, the number of attempt/success and the
setup time.
MME Selection for NAS Message Redirection

1 Selecting MME identified by additional GUTI

Confidential
If the S1 REROUTE NAS REQUEST message contains additional GUTI and

all the following conditions are satisfied, the eNB selects the MME identified
by additional GUTI. If not, goes to step 2.
a The UE selected PLMN is the same as the PLMN identified by additional
GUTI.
b The received MME Group ID is the same as the MME Group ID identified
by additional GUTI.
c The MME identified by additional GUTI is selectable.
2 Selecting a MME based on the received MME Group ID
If the S1 REROUTE NAS REQUEST message does not contain additional
GUTI or MME selection cannot be possible in step 1, the eNB selects a MME
according to the following procedure/conditions. If MME selection cannot be
possible in this step, goes to step 3.
a The eNB has connected to any MMEs supporting the UE selected PLMN
within the MME group identified by the received MME Group ID.
b The eNB selects an appropriate MME among the MMEs with load-based
manner.
3 Selecting a MME from the default DCN (if available)
If MME selection cannot be possible in steps 1 and 2, the eNB selects an
appropriate MME from the default DCN associated to the UE selected PLMN,
if available.
If MME selection cannot be possible in this step, goes to step 4.
The operator can set specific MME groups or MMEs as the default DCN (up to
six) by using parameters (PLMN ID, MME Group ID, and MME code) of CHG-
DCN-CONF.
4 Selecting the first MME.

If MME selection cannot be possible in steps 1 through 3, the eNB selects the
first MME for NAS Message Redirection (refer to 3GPP TS 23.401, 5.19.1).
If multiple MMEs can be selected in step 2 or 3, the eNB selects a new MME
among the appropriate MMEs per each step, according to the load-based MME
selection rule (refer to LTE-SW0504 MME, Selection and Load Balancing).
Counters for NAS Message Redirection]

The eNB collects the results on the NAS Message Redirection procedure as
normal counter families for the establishment of UE associated logical S1
connection (S1SIG, S1SIG_TIME and S1AP_MSG).
SYSTEM OPERATION
Confidential
How to Activate
Preconditions
• Run CHG-ENB-INF and set DCN_ENABLE to 1.
• Run CHG-ENB-INF and set DCN_ENABLE to 0.
Key Parameters
parameters.
DCN_ENABLE This parameter is used to control the DCN function.
• 0: False
• 1: True
parameters.
Parameter Descriptions of CHG-DCN-CONF/RTRV-DCN-CONF
dcnIndex This parameter indicates the DCN index for an eNB. A maximum of six DCNs can
be configured for an eNB.
status This parameter indicates the validity status of the default DCN information.
• N_EQUIP: Invalid
• EQUIP: Valid
plmnIdx This parameter indicates the same PLMN index of RTRV-ENBPLMN-INFO.
mmeGroupId This parameter indicates the MME group ID, which is required for the default DCN.
mmeCode This parameter indicates the MME code, which is required for the default DCN.
When the operator does not want to set the MME code, it has to be set to -1.
Counters and KPIs


Confidential

S1AP_MSG S1apRerouteNASRequest The cumulated number of receive
S1apRerouteNASRequest Message from eNB.
REFERENCE
[4] 3GPP TS23.401 General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

Confidential
LTE-SW0521, X2 Interface Management

INTRODUCTION
X2 interface is for direct communication among neighbor eNBs for the handover.
The X2 handover is able to omit several S1 interface steps comparing to S1
handover and reduce the total handover time. It could reduce the handover time by
exchanging the handover messages directly between eNBs compared to
exchanging through the MME. Also, load and interference information can be
exchanged between neighbor eNBs via X2 interface.
The X2 interface has control plane and user plane.
The control plane uses X2AP interface based on SCTP protocol and supports
exchanging signaling messages such as X2 handover, load information and
interference information. The user plane uses the GTP tunnels to forward the user
data from the source eNB to the target eNB at handover.
When a neighbor cell is added to the eNB, the eNB automatically sets up X2
connection with the eNB, which includes the target cell as a neighbor. After
getting target IP using the ANR (Automatic Neighbor Relation) function, the eNB
makes X2 connection to the target eNB.
The X2 interface management function includes procedures for X2 setup, X2
connection monitoring and error handling to manage the X2 connection.
BENEFIT
• This feature enables operator to manage the signaling associations between
eNBs, surveying X2 interface and recovering from errors.
• X2 interface management helps to use radio resources efficiently.
DEPENDENCY
• Required Network Elements: Neighbor eNB
LIMITATION
• A maximum of 256 X2 connections are supported.
• X2-based handover between Home eNBs is allowed if no access control at the
MME is needed.
SYSTEM IMPACT
capabilities.

Confidential

LTE-SO0201 Intra-LTE ANR: ANR can set up X2 interface automatically among
eNBs.
None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
The X2 Interface Management function includes procedures such as X2 setup, X2
connection monitoring and error handling to manage the X2 connection.
X2 AP Setup
X2AP setup procedure is for setting up the X2 interface between two eNBs at first.
Assuming that eNB 1 triggers X2 setup, the following figure shows the X2 AP
setup procedures for successful case.
1 eNB 1 sends its global eNB ID, served cell information, neighbor
information, MultibandInfoList, and GU group ID list information to eNB 2
using the X2 Setup Request message. (In the perspective of HeNB, eNB 1
shall contain the CSG ID IE in the X2 SETUP REQUEST message for each
CSG or hybrid cell)
2 When the eNB 2 receives the X2 Setup Request message, it stores the
information contained. Then the eNB 2 sends its global eNB ID, served cell
information, neighbor information, and GU group ID list information to the
eNB 1 using the X2 Setup Response message. (In the perspective of HeNB,
eNB 2 shall contain the CSG ID IE in the X2 SETUP RESPONSE message
for each CSG cell or hybrid cell.) The eNB receiving the IEs shall take this
information into account when further deciding whether X2 handover
between the source cell and target cell may be performed.
The eNB includes GU group ID list IE in X2AP messages in Broadcast PLMN
index order only.(the related X2 messages: X2 setup request, X2 setup
response, X2 eNB configuration update)
The following figure is X2 AP Setup procedure for unsuccessful case.

Confidential
Where, Samsung eNB sends X2 Setup failures if:

• X2 setup is not allowed for the peer eNB by operator (NO_X2).
• X2 setup is not allowed for the primary PLMN of the peer eNB (refer to LTE-
SW5012 for details).
The operator can configure whether to allow X2 setup procedure for peer eNB
using CHG-NBR-ENB.
1 The eNB 1 receives the X2 setup failure message from eNB 2.

2 The eNB 1 waits as long as Time To Wait as included in the X2 setup failure
message and then resends the X2 setup request message to eNB 2.
The eNB retries SCTP init and X2 setup procedures after Max {Time To Wait
(nominal), lower bound (20s)} seconds when the SCTP session is down during
Time To Wait.
Since SCTP init procedure is triggered periodically according to Connection

Interval, additional time can be taken until the completion of X2 setup procedure
in this case.
X2 AP Reset
If an abnormal failure occurs with the X2 interface between two interacting eNBs,
the X2AP Reset procedure is performed to reconcile the resources between the two
eNBs.
Figure below depicts the X2 AP reset procedure.
1 The eNB 1 sends the X2 Reset Request message to eNB 2.

2 The eNB 2 sends the X2 Reset Response message to eNB 1. If there are any
procedures, which eNB 1 is carrying out through the X2 Interface, eNB 2
stops all ongoing procedures with eNB1 and deletes the related resources.

Confidential
If the eNB 1 fails to receive X2 Reset Response message, it does not

retransmit X2 Reset Request message and there is no further actions. Samsung
eNB sends X2 Reset Request message to its neighbor eNBs when its own cell
is going to be released.
Keep Alive Between eNBs

The eNB and the neighbor eNBs can monitor X2 connections by exchanging
SCTP HEARTBEAT/HEARTBEAT ACK messages defined by SCTP protocol.
The HEARTBEAT message is periodically transmitted and the period is
configured as HEART_BEAT_INTERVAL. When transmitting the
HEARTBEAT message, the eNB delivers the current time in the Heartbeat
Information field, which is also included in the HEARTBEAT ACK message so
that the sender and receiver can calculate the Round Trip Time (RTT). The SCTP
layer defines the HERATBEAT message.
When the HEARTBEAT ACK message is not received, the eNB tries to retransmit
HEARTBEAT message periodically. The maximum number of retransmission is
configured as NUM_PATH_RE_TX. The period of retransmission is heartbeat
retransmission interval and calculated as HEART_BEAT_INTERVAL + RTO
+ RTO * [-0.5, 0.5]. Where, RTO is increased as exponential backoff if the
previous HEARTBEAT message is unanswered. The initial, the minimum and the
maximum values are configured as RTO_INITIAL, RTO_MIN, and
RTO_MAX. If HEARTBEAT ACK is not received after all the retransmissions,
the link status is considered abnormal.

Confidential
In case of X2 setup procedure, the eNB transmits INIT message to establish SCTP
association. If it fails to get the INIT ACK message, the eNB retransmits INIT
message after 1 s. If it goes unanswered, the eNB repeats this procedure with the
period of CONNECT_INTERVAL until SCTP setup is successful, as depicted in
figure below.
The operator can manage the status of neighbor eNB link as follows:
• Locked: Cancels the relevant X2 handover procedure if there is any current X2
handover call, and blocks a new X2 handover out.
• Unlocked: Processes the X2 handover normally.
• shuttingDown: Processes the relevant X2 handover procedure normally if there
is any current X2 handover call, and blocks a new X2 handover out.

Confidential
To recover the X2 connection, you can do the following actions through LSM:
• Turn off/on x2 connection with each neighbor eNB manually.
• Send SCTP ABORT message only to neighbor eNBs whose current X2 status
is enabled.
• Send SCTP ABORT message to all neighbor eNBs regardless of the current
X2 interface status.
SYSTEM OPERATION
How to Activate
Preconditions
• The SCTP connection is established and the operational state is normal.
• Run CRTE-NBR-ENB or CHG-NBR-ENB and set NO_X2 to False.
• Run the CHG-NBR-ENB and set NO_X2 to True.
Key Parameters
parameters.
Parameter Descriptions of CRTE-NBR-ENB/DLT-NBR-ENB/CHG-NBR-
ENB/RTRV-NBR-ENB
NBR_ENB_INDEX This parameter specifies the index to change the neighbor eNB information
required for the operation of the neighbor eNB.
STATUS This parameter indicates the validity of the neighbor eNB. This parameter
must be set accurately since it determines the X2 link and handover
execution.
• N_EQUIP: The information is determined as invalid.
• EQUIP: The information is determined as valid.

Confidential
NO_X2 This parameter determines whether to execute X2 link setup with the
neighbor eNB. The parameter must be set accurately for X2 link setup to be
determined by the setting.
• False: X2 link setup to the neighbor eNB is executed.
• True: X2 link setup to the neighbor eNB is not performed.
NO_HO This parameter determines whether HO is possible with the neighbor eNB.
The parameter must be set accurately for Handover to be executed as
determined by the setting.
• False: Handover is done with the neighbor eNB.
• True: Handover is not done with the neighbor eNB.
ENB_ID This parameter is the eNB ID of the Neighbor eNB to which the Neighbor Cell
belongs. Depending on the Neighbor eNB type, the entry must be made in 20
bits for Macro eNB ID, and 28 bits for Home eNB. This information is used
during Handover.
The eNB ID of the Neighbor eNB must be configured accurately. If the
information does not match, the Handover is not executed.
ENB_TYPE This parameter is the eNB type of the neighbor eNB.
• Macro_eNB: Macro eNB.
• Home_eNB: Home eNB.
ENB_MCC This parameter is the PLMN information (MCC) of the eNB where the
EUTRAN neighbor cell, located around the eNB, belongs to. Enter 3-digit
number (each digit range is 0-9).
The MCC information must be entered accurately.
ENB_MNC This parameter is the PLMN information (MNC) of the eNB where the
EUTRAN neighbor cell, located around the eNB, belongs to. Enter 3-digit or
2-digit number (each digit range is 0-9).
IP_VER This parameter is the IP address version indicating the IP address of a
neighboring eNB. All neighboring eNB IP version information must be the
same.
• IPV4: Indicates IPV4 address.
• IPV6: Indicates IPV6 address.
NBR_ENB_IPV4 This parameter indicates the IP version 4 address of the neighbor eNB. This
information is used during X2 Link setup for the SCTP connection setup.
Accurately set the information to ensure proper X2 setup.
NBR_ENB_IPV6 This parameter indicates the IP version 6 address of the neighbor eNB. This
information is used during X2 Link Setup for the SCTP connection setup.
Accurately set the information to ensure proper X2 setup.
SECONDARY_NBR_ENB_IP This parameter indicates the secondary IPv4 address of the neighbor eNB.
V4 This information is used during SCTP multi-homing connection setup.
SECONDARY_NBR_NEB_IP This parameter indicates the secondary IPv6 address of the neighbor eNB.
V6 This information is used during SCTP multi-homing connection setup.
parameters.
Parameter Descriptions of CRTE-NBR-ENB/DLT-NBR-ENB/CHG-NBR-
ENB/RTRV-NBR-ENB
ADMINISTRATIVE_STATE This parameter is the neighbor eNB link status information. If the setting is

Confidential
set to shuttingdown or Locked, the S1 Handover is executed instead of the
X2 Handover.
• unlocked: Normal operation of the X2 Link state.
• shuttingDown: Restricts new X2 Handovers but the normal execution of the
current X2 Handover in progress.
• locked: Restricts both of the current X2 Handover in progress and the new
X2 Handover.
OWNER_TYPE This parameter defines how NRT is updated. This field can be classified as
Initial NRT, ANR by Server, ANR by UE, Created by User Command,
CreatedByUserUI, AnrByTnlReq, AnrByTnlReply, and AnrByX2Setup.
REMOTE_FLAG This parameter indicates whether the neighbor eNB is managed by the same
EMS or a different EMS.
CURRENT_X2_RANK The current X2 rank of corresponding EUTRAN neighbor eNB. Higher value
presents higher priority.
PREVIOUS_X2_RANK The previous X2 rank of corresponding EUTRAN neighbor eNB. Higher value
presents higher priority.
NO_REMOVE It shows whether it is possible to delete Neighbor eNB data.

X2_SETUP This parameter is the waiting time to receive the X2SetupResponse message
or X2SetupFailure message after the X2SetupRequest message is
transmitted from the eNB to another eNB. The X2 Setup procedure is a
procedure to exchange the eNB setup information with another eNB that is
designated as a neighbor. The eNB setup information includes the Global
eNB ID information, Global Unique (GU) Group ID List information, Serve
Cell information (Physical Cell ID, CellId, TAC, and PLMN), and so on. When
the X2SetupResponse message is received, the X2 setup is completed and
afterwards, if a handover is performed to an eNB where the X2 setup is
completed, an X2 handover can be performed. Enough time must be
guaranteed until a message is transmitted to another eNB and a response
message is received (minimum 100 ms).
X2_SETUP_RETRY_COUNT This parameter is the number of times that the X2SetupRequest procedure
should be attempted again when Timeout occurs because the
X2SetupFailure message is received or X2SetupResponse message is not
received from another eNB after the X2SetupRequest message has been
transmitted from the eNB.
• Zero: The X2SetupRequest re-transmission procedure is not executed.
• One: The X2SetupRequest re-transmission procedure is executed once.
• Two: The X2SetupRequest re-transmission procedure is executed twice.
• Three: The X2SetupRequest re-transmission procedure is executed three
times.
• Ten: The X2SetupRequest re-transmission procedure is executed 10
times.
• Infinity: The X2SetupRequest re-transmission procedure is executed
unlimited times.
X2_SETUP_TIME_TO_WAIT This parameter is the TimetoWait value included in the X2SetupFailure
message when the eNB that has received the X2SetupRequest message
transmits the X2SetupFailure message. The eNB that has received the
TimeToWait information re-transmits the X2SetupRequest message after
waiting for the TimeToWait time.
• 1: Transmits the X2SetupRequest message 1 second after the reception of

Confidential
the X2SetupFailure.
• 2: Transmits the X2SetupRequest message 2 seconds after the reception
of the X2SetupFailure.
• 5: Transmits the X2SetupRequest message 5 seconds after the reception
of the X2SetupFailure.
• 10: Transmits the X2SetupRequest message 10 seconds after the
reception of the X2SetupFailure.
X2_UPDATE This parameter is the waiting time to receive the
ENBConfigurationUpdateAcknowledge message or
ENBConfigurationUpdateFailure message after the ENBConfigurationUpdate
message is transmitted from the eNB to another eNB that is designated as a
neighbor. The procedure above is a procedure to update the changes of
information to another eNB when the Global Unique (GU) Group ID List
information and Serve Cell information (Physical Cell ID, CellId, TAC, PLMN)
is changed by the operator. Enough time must be guaranteed until a
message is transmitted to another eNB and a response message is received
(minimum 100 ms).
X2_UPDATE_RETRY_COUN This parameter is the number of times that the X2 ENBConfigurationUpdate
T procedure should be attempted again when Timeout occurs because the
ENBConfigurationUpdateFailure message is received or
ENBConfigurationUpdateAcknowledge message is not received from another
eNB after the X2 ENBConfigurationUpdate message has been transmitted
from the eNB.
• Zero: Does not perform the ENBConfigurationUpdate re-transmission
procedure.
• One: Performs the ENBConfigurationUpdate re-transmission procedure
once.
• Two: Performs the ENBConfigurationUpdate re-transmission procedure
twice.
• Three: Performs the ENBConfigurationUpdate re-transmission procedure
thrice.
• Ten: Performs the ENBConfigurationUpdate re-transmission procedure 10
times.
• Infinity: Performs the ENBConfigurationUpdate re-transmission procedure
infinitely.
X2_UPDATE_TIME_TO_WAI This parameter is the TimetoWait value included in the
T ENBConfigurationUpdateFailure message transmitted by the eNB that has
received the ENBConfigurationUpdate message. The eNB that has received
the TimeToWait information re-transmits the ENBConfigurationUpdate
message after waiting for the TimeToWait time.
• 1: Transmits the ENBConfigurationUpdate message 1 second after the
reception of the ENBConfigurationUpdateFailure.
• 2: Transmits the ENBConfigurationUpdate message 2 seconds after the

Confidential
X2_RESET This parameter is the time waiting to receive the ResetResponse message
after an eNB transmits the ResetRequest message to another eNB. The X2
Reset procedure is used to balance resources if there is abnormal failure
between neighbor eNBs. An eNB that received X2 Reset performs the
procedure of releasing all the call resources in the eNB. Basically, enough
time must be guaranteed until a message is transmitted to another eNB and
a response message is received (minimum 100 ms).
X2_RESET_RETRy_COUNT This parameter is the number of times that the X2 Reset procedure should be
attempted again when Timeout occurs because the ResetResponse
message is not received from another eNB after the X2 Reset message has
been transmitted from the eNB.
• Zero: The Reset re-transmission procedure is not executed.
• One: The Reset re-transmission procedure is executed once.
• Two: The Reset re-transmission procedure is executed twice.
• Three: The Reset re-transmission procedure is executed three times.
• Ten: The Reset re-transmission procedure is executed 10 times.
• Infinity: The Reset re-transmission procedure is executed unlimited times.
Parameter Descriptions of RTRV-X2-STS

NBR_ENB_INDEX This parameter is the index of the neighbor eNB.
NBR_ENB_ID This parameter is the ID of the neighbor eNB.
SCTP_STATE This parameter is the Stream Control Transmission Protocol (SCTP) status. It
is the physical connection status between the eNBs.
• disable_SD_PlmnTg_UA: shutdown by undecidable PLMN TGID.
• disable_SD_PlmnVr: shutdown by undecidable PLMN VRID.
• disable_SD_NoX2: shutdown by NO_X2 setting.
• disable_SD_Locked: shutdown by administrativeState locked setting.
• disable_OOS: out of service (all case without above case).
• enable_INS: in service.
X2AP_STATE This parameter is the X2AP status. It is the logical connection status between
the eNBs. If SCTP is disabled, X2AP cannot be enabled.
• disable_X2AP_SCTP_OOS: X2AP status is disabled because SCTP status
is Out-Of-Service (OOS).
• disable_X2AP_SETUP_TO: X2AP status is disabled. Because retry count
of X2 setup request is over than threshold.
• disable_X2AP_RESET_TO: X2AP status is disabled. Because retry count
of X2 reset is over than threshold.
• disable_X2AP_UPDATE_TO: X2AP status is disabled. Because retry count
of X2 update request is over than threshold.
• disable_X2AP_SETUP_FAIL: X2AP status is disabled. When X2 setup
failure is received and x2 setup retry count was is 0.
• disable_X2AP_UPDATE_FAIL: X2AP status is disabled. When X2 update
failure is received and x2 update retry count is 0.

Confidential
Counters and KPIs

with this feature.
REFERENCE
UTRAN); S1 application protocol (S1AP)

Confidential
LTE-SW0522, UE Radio Capability Match

Request
INTRODUCTION
Up to 3GPP Release 10, an MME determines whether to enable IMS voice over
PS session or not based only on consideration of UE’s radio capability and MME's
configuration. In this case, a mismatch between UE’s radio capability and an eNB
configuration can occur. The mismatch causes voice call loss and degradation of
user experience. To avoid this problem, 3GPP defined the UE Radio Capability
Match Request procedure in Release 11. Through the UE Radio Capability Match
Request procedure, the MME can request the eNB to check match status between
the UE radio capability and eNB configuration for voice continuity. If the eNB
determines that its configurations properly supports voice continuity, it sends a
voice support match indication to the MME. With this indicator, the MME can
determine IMS voice over PS session supportability more properly.
BENEFIT
Voice call loss and degradation of user experience from the mismatch between the
UE radio capability and eNB configuration can be avoided.
DEPENDENCY
Required Network Elements: The MME should support UE Radio Capability
Match procedure.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
When the MME determines IMS voice over PS session supportability for a
specific UE, it can trigger UE Radio Capability Match Request procedure to check
eNB configurations related to voice call continuity. Upon receiving UE Radio
Capability Match Request message, eNB determines and replies 'Voice Support
Match indication' after checking supportability of voice call continuity according
to UE capability and eNB configurations.
Operational Flow
Typically, the MME initiates UE Radio Capability Match Request procedure in
Confidential
following cases.
• Initial Attach procedure
• Tracking Area Update procedure with purpose of "first TAU following
GERAN/UTRAN Attach" or "UE radio capability update"
The following figure depicts a call flow of UE Radio Capability Match Request
procedure.
1 The MME requests Voice support match indicator to the eNB.

2 Upon receiving a UE Radio Capability Match Request from the MME, if the
eNB has not already received the UE radio capabilities from the UE or from
MME in step 1, the eNB requests the UE to upload the UE radio capability
information by sending the RRC UE Capability Enquiry.
3 The UE provides the eNB with its UE radio capabilities by sending the RRC
UE Capability Information.
4 The eNB checks whether the UE radio capabilities are compatible with the
network configuration for ensuring voice service continuity. The eNB sends
the Voice Support Match Indicator with value of either ‘Supported’ or ‘Not
Supported’ to the MME to indicate whether the UE capabilities and eNB
configurations are compatible for ensuring voice service continuity.
5 If eNB requested radio capabilities from UE in step 2 and 3, the eNB also
sends the UE radio capabilities to the MME using the S1-AP UE
CAPABILITY INFO INDICATION.
Voice Support Match Indicator Decision

When the eNB decides the Voice Support Match Indicator, it considers the
following factors.
• UE capabilities for voice handover
o Supported bands
o Supported voice handover features

Confidential
• The eNB configurations for voice service and handover capability

o Available Frequency Allocations (FA) in the FA list
The availability of a FA can be checked by STATUS configuration
parameter for each frequency index. The related commands are CHG-
EUTRA-FA for EUTRAN, CHG-UTRA-FA for UTRAN, CHG-GERAN-
FA for GERAN, and CHG-C1XRTT-FREQ for CDMA 1xRTT.
o Available cells in the neighbor cell list
The availability of a neighbor cell can be checked by STATUS and
IS_HOALLOWED configuration parameters for each neighbor cell. The
related commands are CHG-NBR-EUTRAN for EUTRAN, CHG-NBR-
UTRAN for UTRAN, and CHG-NBR-GERAN for GERAN.
• Operator's voice service policy per FA
o Voice support configuration per FA in the FA list
The supportability of voice service for each FA can be checked by
VOICE_SUPPORT0 configuration parameter. The related commands are
CHG-EUTRA-FA command for EUTRAN, CHG-UTRA-FA command for
UTRAN, CHG-GERAN-FA command for GERAN, and CHG-C1XRTT-
FREQ command for CDMA 1xRTT.
The eNB decides Voice Support Match is ‘Supported’, if the serving cell of the UE
supports voice service and one of the following voice call continuity methods is
available.
• Intra-frequency HO
• Inter-frequency HO within FDD or TDD
• inter-frequency HO between FDD and TDD
• SRVCC to UTRAN
• SRVCC to GERAN
• SRVCC to 1xRTT
Otherwise, the eNB decides Voice Support Match is ‘Not Supported’.
SYSTEM OPERATION
How to Activate
This feature runs automatically, and it cannot be disabled. If the MME sends UE
Radio Capability Match Request, the eNB responds with UE Radio Capability
Match Response.
The operator can control Voice Support Match Indicator IE in the UE Radio
Capability Match Response by controlling voiceSupport for serving PLMN IE.

Confidential
Key Parameters
parameters.
FA_INDEX This parameter is the EUTRA frequency index. This value must not exceed
the maximum number of FA supported by the system.
PREFERENCE0 This parameter is the preference of PLMN #0 for a FA.
VOICE_SUPPORT0 This parameter can configure voice service ability of the PLMN #0 in the
selected FA with FA_INDEX.
It can affect the configuration of the Voice Support Match Indicator IE in the
S1AP UE radio capability match response message.
It is noted that even though the Radio Capability of the UE supports voice
service, the mobility preference of the serving PLMN is preferred, and the
neighbor which can support voice service exists for this FA, the operator can
set Voice Support Match Indicator IE to Not Supported by set this parameter
to false.
to false.
to false.

Confidential
to false.
to false.
to false.
Parameter Descriptions of CHG-UTRA-FA/RTRV-UTRA-FA

FA_INDEX This parameter specifies the frequency index to change the UTRAN carrier
information.
Maximum 6 FAs can be set for each cell.
to false.

Confidential
to false.
to false.
to false.
to false.
to false.
Parameter Descriptions of CHG-GERAN-FA/RTRV-GERAN-FA

FA_INDEX GERAN frequency index. Up to 6 FAs can be assigned per cell.

Confidential
to false.
to false.
to false.
to false.
to false.

Confidential
to false.
Parameter Descriptions of CHG-C1XRTT-FREQ/RTRV-C1XRTT-FREQ

CARRIER_INDEX CDMA2000 1xRTT carrier index. Up to eight carriers can be assigned per
cell.
to false.
to false.
to false.

Confidential
to false.
to false.
to false.
Parameter Descriptions of CHG-NBR-UTRAN/RTRV-NBR-UTRAN/CRTE-

NBR-UTRAN/DLT-NBR-UTRAN
RELATION_IDX This parameter indicates the Index of the registered neighbor UTRAN cell.
VOIP_INCAPABLE Whether to support VoIP of GERAN neighboring cell.
• False: VoIP is supported.
• True: VoIP is not support.
Parameter Descriptions of CHG-NBR-GERAN/RTRV-NBR-GERAN/CRTE-

NBR-GERAN/DLT-NBR-GERAN
RELATION_IDX Database index of GERAN neighboring cell to the eNB.
VOIP_INCAPABLE Whether to support VoIP of GERAN neighboring cell.
• False: VoIP is supported.
• True: VoIP is not support.

Confidential
Counters and KPIs

S1AP_MSG S1apUeRadioCapabilityMatch The number of S1AP UE Radio Capability
Request Match Request received.
S1apUeRadioCapabilityMatch The number of S1AP UE Radio Capability
Response Match Response sent.
REFERENCE
[1] 3GPP TS 23.401 General Packet Radio Service (GPRS) enhancements for
Evolved Terrestrial Radio Access Network (E-UTRAN) access (Release 11)
[2] 3GPP TS 36.413 Evolved Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP) (Release 11)

Confidential
LTE-SW0531, Control Plane Optimization

Support
INTRODUCTION
Call Plane (CP) optimization utilizes RRC and S1 Application Protocol (S1AP)
signaling connections for small user data transfer without data bearer setup to
reduce signaling load produced by enormous number of NB-IoT or eMTC UEs.
BENEFIT
• Signaling load on an eNB and an MME can be reduced.
• The number of concurrent RRC connected UEs in the eNB can be reduced.
DEPENDENCY
• HW dependency
o Support Channel Cards: NB-IoT or eMTC supported channel cards
• Required Network Elements: An S-GW or an SCEF should support bearer
interface with the MME.
• Prerequisite Features: LTE-SW6301, NB-IoT Call Control Support or LTE-
SV1500, eMTC
• Others: The UE should support Control Plane Optimization feature
LIMITATION
None
SYSTEM IMPACT
capabilities.
LTE-SW6301 NB-IoT Call Control Support or LTE-SV1500 eMTC is required.
None
Coverage
None
Interfaces
New messages and IEs of the RRC and the S1 interface are added.

Confidential
FEATURE DESCRIPTION
The user plane data is transferred via Non Access Stratum (NAS) transport
capabilities of RRC connection and S1AP connection to MME. The MME then
relays the user plane data to Serving Gateway (S-GW) via newly defined S11
bearer, as depicted in figure below.
Figures below depict the overall CP optimization procedures of the Mobile

Originated (MO) and Mobile Terminated (MT) user data transport.

Confidential
1 The UE establishes RRC connections including uplink user data, Evolved

Packet System (EPS) bearer ID, and release assistance information in NAS
data PDU.
2 The eNB relays uplink user data and EPS bearer ID in NAS data PDU via the
initial UE message to a MME.
3 The MME checks the integrity of the NAS data PDU and decrypts user data
in the NAS data PDU.
4 If S11-U is not established between MME and S-GW, bearer modification
procedure is performed.

Confidential
5 The MME transfers uplink user data to S-GW via S11 bearer.
6 If no downlink data is expected in release assistance information, the MME
releases S1 connection immediately.
7 If no information exists in release assistance information, the MME sends
connection establishment indication message.
8 The MME receives downlink user data if available.
9 The MME does encryption and integrity protection for the downlink user
data.
10 The downlink user data encapsulated in a NAS data PDU is transferred via
S1 downlink NAS transport message.
11 If downlink data is expected in release assistance information, the MME
releases S1 connection immediately.
12 The eNB relays the downlink user data to the UE via RRC DL information
transfer.
13 If the eNB detects no more activity of UE, it triggers the S1 release
procedure.

Confidential
1 If the S-GW receives downlink user data and no downlink user plane to
MME exist, it buffers the downlink data.
2 The S-GW notifies the downlink user data to the MME.
3 The MME sends paging messages to wake up target UE.
4 The UE triggers RRC connection establishment with NAS service request.
5 The NAS service request is relayed to the MME via S1 initial UE message.
6 If S11-U between the MME and the S-GW is not established, the bearer
modification procedure is performed.

Confidential
7 Buffered downlink user data is transferred to the MME.

8 The MME does encryption and integrity protection for the downlink user
data.
9 The downlink user data encapsulated in NAS data PDU is transferred in the
S1 downlink NAS transport message.
10 The eNB relays the downlink user data to the machine device via RRC DL
information transfer.
11 If available, the UE transfers uplink user data via RRC UL information
transfer.
12 The eNB relays uplink user data and EPS bearer ID in NAS data PDU via the
Uplink NAS transport message to the MME.
13 The MME checks the integrity of the NAS data PDU and decrypts user data
in the NAS PDU.
14 The MME transfers uplink user data to the S-GW.
15 If the eNB detects no more activity of UE, it performs S1 release procedure.
SYSTEM OPERATION
For configuration, key parameters, and detailed information on counters associated
with this feature, see System Operation section of LTE-SW6301, NB-IoT Call
Control Support feature.
REFERENCE
[2] 3GPP TS 24.301 Non-Access-Stratum (NAS) protocol for Evolved Packet
System (EPS); Stage 3
[5] 3GPP TS 36.413 Evolved Universal Terrestrial Radio Access Network (E-

Confidential
LTE-SW0532, User Plane Optimization Support

INTRODUCTION
For the NB-IoT or eMTC devices, RRC connections and S1 associations can be
suspended while keeping necessary contexts in UE, eNB and MME. Later, the
suspended RRC connections and S1 associations can be resumed utilizing the
stored contexts through reduced signaling procedure.
BENEFIT
This feature reduces signaling overhead.
DEPENDENCY
• HW dependency: NB-IoT or eMTC supported channel card
• Prerequisite Features: LTE-SW6301, NB-IoT Call Control Support or LTE-
SV1500, eMTC
• Others: The UE should support UP optimization
LIMITATION
• The number of suspended UEs per eNB is limited by the maximum number of
RRC connected UEs per eNB.
• For NB-IoT, X2 retrieve UE context procedure (inter-eNB connection resume)
is not supported.
SYSTEM IMPACT
capabilities.
None
None
Coverage
None
Interfaces
• Air interface: New RRC messages and IEs are introduced for User Plane
Optimization.
• S1 Interface: New S1/X2 messages and IEs are introduced for User Plane
Confidential
Optimization.
FEATURE DESCRIPTION
The eNB can trigger connection suspend procedure if UE User Plane CIoT
Support Indicator IE in S1 Initial Context Setup Request is supported.
UE eNB MME
RRCConnectionRequest-NB
RRCConnectionSetup-NB
RRCConnectionSetupComplete-NB
(UP-CIoT-EPS-Optimisation)
Initial UE message
Initial Context Setup Request

(UE User Plane CIoT Support Indicator)
Initial Context Setup Response
The eNB triggers connection suspend procedure by sending UE context suspend

request to MME and sends rrcSuspend release cause with resume ID in the
RRCConnectionRelease message to the UE. After successful connection suspend
procedure, the eNB stores the UE context for further connection resumption.
If the UE requests for RRC Connection Resume with resume ID, the eNB resumes
the RRC connection using stored UE context and sends the UE context resume
request to MME.

Confidential
Figure below depicts the connection suspend and resume procedures.
UE eNB MME S-GW P-GW
store the UE AS context including the UE context suspend request

current RRC configuration, the current
security context, the PDCP state including
ROHC state, the C-RNTI used in the source Release access bearer request
PCell, the cellIdentity and the physical cell
Identity of the source PCEll; Release access bearer response
UE context suspend response
RRCConnectionRelease-NB the eNB shall suspend the UE context,

(resumeIdentity, releaseCause: rrcSuspend) the UE-associated logical S1-connection
and the related bearer contexts
Connection suspend procedure
Connection resume procedure

Random access
No S1 initial context setup request/response
No RRC connection reconfiguration
RRCConnectionResumeRequest-NB
no integrity
(resumeIdentity, shortMAC-I)
RRCConnectionResume-NB or fallback: RRCConnectionSetup-NB

no integrity or reject: RRCConnectionReject-NB
RRCConnectionResumeComplete-NB
UE context resume request
UE context resume response

or failure: UE context resume failure
RRC connection reconfiguration if E-RAB failed to resume item IE from MME
Uplink data
Modify bearer request
Modify bearer response
If suspended UE moves to another eNB and tries to resume, the new eNB tries to
retrieve UE context from the old eNB by X2 retrieve UE context procedure.

Confidential
Figure below depicts the retrieve UE context procedure.
UE New eNB Old eNB MME
RRCConnectionResumeRequest
X2-AP: RETRIEVE UE CONTEXT

REQUEST
X2-AP: RETRIEVE UE CONTEXT

RESPONSE
or failure: RETRIEVE UE CONTEXT FAILURE
RRCConnectionResume
S1-AP: PATH SWITCH REQUEST
S1-AP: PATH SWITCH REQUEST RESPONSE
X2-AP: UE CONTEXT RELEASE
SYSTEM OPERATION
How to Activate
Preconditions
• A valid license key is required to run the feature on the network.
• For eMTC available cell, run CHG-CELLPLMN-INFO and set
UP_OPT_FOR_EMTC_ENABLE to USE.
• For NB-IoT cell, run CHG-NBCELLPLMN-INFO and set
UP_OPT_FOR_NBIOT_ENABLE to USE.
• For eMTC available cell, run CHG-CELLPLMN-INFO and set
UP_OPT_FOR_EMTC_ENABLE to NOT_USE.
• For NB-IoT Cell, run CHG-NBCELLPLMN-INFO and set
UP_OPT_FOR_NBIOT_ENABLE to NOT_USE.
Key Parameters

Confidential
parameters.
UP_OPT_FOR_EMTC_ENAB This parameter indicates whether the selected PLMN is available for user
LE plane CIoT optimization or not.
Parameter Descriptions of CHG-NBCELLPLMN-INFO/RTRV-NBCELLPLMN-

INFO
UP_OPT_FOR_NBIOT_ENAB This parameter indicates whether the selected PLMN is available for user
LE plane CIoT optimization or not.
parameters.
S1_UE_CONTEXT_RESUME This parameter is the waiting time to receive the
UeContextResumeResponse message after the UeContextResumeRequest
message is transmitted from the eNB to the MME. A call is detached if the
UeContextResumeResponse message is not received before the timer
expiration. In general, this parameter should be set so that enough time is
guaranteed for the receipt of a response message after a message has been
transmitted to the MME (minimum 100ms or more).
[Related Specifications] 3GPP TS 36.413 [8.3.8]
S1_UE_CONTEXT_SUSPEND This parameter is the waiting time to receive the
UeContextSuspendResponse message after the UeContextSuspendRequest
UeContextSuspendResponse message is not received before the timer
transmitted to the MME (minimum 100 ms or more).
X2_RETRIEVE_UE_CONTEXT This parameter is the waiting time to receive the
X2RetrieveUeContextResponse message after the
X2RetrieveUeContextRequest message is transmitted from the new eNB
which received RRCConnectionResumeRequest.. The old eNB that has
received the X2RetrieveUeContextRequest makes preparations for UE
context. If the suspended UE context can be identified and verified, old eNB
transmits the X2RetrieveUeContextResponse message to the new eNB.
Otherwise, the X2RetrieveUeContextFailure message is transmitted to the
new eNB. Enough time must be guaranteed until a message is transmitted to
another eNB and a response message is received (minimum 100 ms or
more).
Parameter Descriptions of CHG-EMTCTIMER-INF/RTRV-EMTCTIMER-INF

Confidential
RRC_CONNECTION_RESUM This parameter is the waiting time to receive the
E RrcConnectionResumeComplete message after the RrcConnectionResume
message is transmitted from the eNB to the eMTC UE. The procedure above
is a procedure to resume the suspended Signaling Radio Bearer(s) (SRB(s))
and Data Radio Bearer(s) (DRB(s)) between the UE and the eNB. A call is
detached if the RrcConnectionResumeComplete message is not received
before the timer expiration. Enough time must be guaranteed until a message
is transmitted to a UE and a response message is received (minimum 100
ms or more).
Parameter Descriptions of CHG-NBTIMER-INF/RTRV-NBTIMER-INF

S1_UE_CONTEXT_RESUME This parameter is the waiting time to receive the
UeContextResumeResponse message after the UeContextResumeRequest
UeContextResumeResponse message is not received before the timer
S1_UE_CONTEX_SUSPEND This parameter is the waiting time to receive the
UeContextSuspendResponse message after the UeContextSuspendRequest
UeContextSuspendResponse message is not received before the timer
RRC_CONNECTION_RESUM This parameter is the waiting time to receive the
E RrcConnectionResumeComplete-NB message after the
RrcConnectionResume-NB message is transmitted from the eNB to the UE.
The procedure above is a procedure to resume the suspended Signaling
Radio Bearer(s) (SRB(s)) and Data Radio Bearer(s) (DRB(s)) between the
UE and the eNB. A call is detached if the RrcConnectionResumeComplete-
NB message is not received before the timer expiration. Enough time must
be guaranteed until a message is transmitted to a UE and a response
message is received (minimum 100 ms or more).
S1_PATH_SWITCH This parameter is the waiting time to receive the
PathSwitchRequestAcknowledge message or the PathSwitchRequestFailure
after the PathSwitchRequest message is transmitted from the eNB to the
MME. The Path Switch procedure is a procedure during RRC Connection
Resume to new eNB where the eNB requests from the MME to change the
downlink GTP tunnel to a new GTP tunnel after the UE has successfully
attached to the target eNB. In general, this parameter should be set so that
enough time is guaranteed for the receipt of a response message after a
message has been transmitted to the MME (minimum 100 ms or more).
Counters and KPIs

Table below outlines the main eMTC counters associated with this feature.
Family Display Type Name Type Description
Name
RRC eMTC_ConnResumeAtt The cumulated number of receiving
Connection RRCConnectionResumeRequest from the UE

Confidential

Name
Resume for eMTC_ConnResumeSucc The cumulated number of receiving
eMTC UE RRCConnectionResumeComplete in the RRC connection
resume procedure from the eMTC UE
eMTC_ConnResumeFallbackS The cumulated number of receiving
ucc RRCConnectionSetupComplete in the RRC connection
resume procedure from the eMTC UE due to fallback
eMTC_ConnResumeFail_CpCc The cumulated number when a call is released due to call
To control timeout in the RRC connection resume Procedure
because of not receiving response message from the
protocol blocks (MAC, RLC, PDCP, GTP)
eMTC_ConnResumeFail_CpCc The cumulated number when a call is released due to
Fail reset notification (eNB failure or block restart) in the RRC
connection resume Procedure
eMTC_ConnResumeFail_UpGt The cumulated number when a call is released due to the
pFail failure between GTPB and ECCB block in the RRC
eMTC_ConnResumeFail_UpMa The cumulated number when a call is released due to the
cFail failure between MAC and ECCB block in the RRC
eMTC_ConnResumeFail_UpPd The cumulated number when a call is released due to the
cpFail failure between PDCP and ECCB block in the RRC
eMTC_ConnResumeFail_UpRl The cumulated number when a call is released due to the
cFail failure between RLC and ECCB block in the RRC
eMTC_ConnResumeFail_RrcSi The cumulated number when a call is released due to
gTo timeout in the RRC connection resume procedure
because of not receiving
RRCConnectionResumeComplete Message.
eMTC_ConnResumeFail_S1ap The cumulated number when a call is released due to the
LinkFail S1AP link in the RRC connection resume Procedure,
because the S1AP link status is changed to Out of
service.
eMTC_ConnResumeFail_S1ap The cumulated number when a call is released due to
SigFail receiving S1AP reset from MME in the RRC connection
resume Procedure
eMTC_ConnResumeFallbackF The cumulated number when a call is released due to call
ail_CpCcTo control timeout in the RRC connection resume fallback
Procedure because of not receiving response message
from the protocol blocks (MAC, RLC, PDCP)
eMTC_ConnResumeFallbackF The cumulated number when a call is released due to
ail_CpCcFail reset notification (eNB failure or block restart) in the RRC
connection resume fallback Procedure
eMTC_ConnResumeFallbackF The cumulated number when a call is released due to the
ail_UpMacFail failure between MAC and ECCB block in the RRC
ail_UpPdcpFail failure between PDCP and ECCB block in the RRC
ail_UpRlcFail failure between RLC and ECCB block in the RRC

Confidential

Name
ail_RrcSigTo timeout in the RRC connection resume Procedure
because of not receiving RRCConnectionSetupComplete
Message.
ail_S1apLinkFail S1AP link in the RRC connection resume fallback
Procedure, because the S1AP link status is changed to
Out of service.
ail_S1apSigFail receiving S1AP reset from MME in the RRC connection
resume fallback Procedure
eMTC_ConnResumeReject_Cp The cumulated number when a call is released due to
CcFail receiving S1AP reset from MME in the RRC connection
eMTC_ConnResumeReject_Cp The cumulated number when eNB sends RRC
CapaCacFail Connection Reject to UE due to capacity based call
admission control failure for the suspended DRB context
QoSCacFail Connection Reject to UE due to QoS based call
admission control failure for the suspended GBR DRB
context
BhCacFail Connection Reject to UE due to Backhaul link capacity
based call admission control failure for the suspended
GBR DRB context
eMTC RRC eMTC_ConnSuspend_UpMacU The cumulated number when the RRC connection is
Connection EInact released from the eNB in order to suspend the eMTC UE
Release since a timeout occurs in eMTC UE subject to user plane
optimization after the RRC connection establishment
procedure is completed.
CSL [0x037D]EccTmout_RrcConnec A call is released when the RRC Connection Resume
tionResumeComplete Complete message is not received after the RRC
Connection Resume message is transmitted to the UE.
[0x037E]EccTmout_S1UeConte A call is released when the UE Context Resume
xtResumeResponse Response message is not received after transmitting the
UE Context Resume Request to the MME.
[0x037F]EccTmout_S1UeConte A call is released when the UE Context Suspend
xtSuspendResponse Response message is not received after transmitting the
UE Context Suspend Request to the MME.
[0x0380]EccUeSuspendUserIna A call subjected to user plane optimization is successfully
ctivity suspended due to user inactivity.
Table below outlines the main NB-IoT counters associated with this feature.
Name
RRC NBIoT_ConnResumeAtt The cumulated number of receiving
Connection RRCConnectionResumeRequest-NB from the UE
Resume for NB- NBIoT_ConnResumeSucc The cumulated number of receiving
IoT UE
RRCConnectionResumeComplete-NB in the RRC
connection resume procedure from the NB-IoT UE

Confidential

Name
NBIoT_ConnResumeFallbackS The cumulated number of receiving
ucc RRCConnectionSetupComplete-NB in the RRC
connection resume procedure from the NB-IoT UE due to
fallback
NBIoT_ConnResumeFail_CpCc The cumulated number when a call is released due to call
To control timeout in the RRC connection resume Procedure
because of not receiving response message from the
protocol blocks (MAC, RLC, PDCP, and GTP)
NBIoT_ConnResumeFail_CpCc The cumulated number when a call is released due to
Fail reset notification (eNB failure or block restart) in the RRC
NBIoT_ConnResumeFail_UpGt The cumulated number when a call is released due to the
pFail failure between GTPB and NCCB block in the RRC
NBIoT_ConnResumeFail_UpM The cumulated number when a call is released due to the
acFail failure between MAC and NCCB block in the RRC
NBIoT_ConnResumeFail_UpPd The cumulated number when a call is released due to the
cpFail failure between PDCP and NCCB block in the RRC
NBIoT_ConnResumeFail_UpRl The cumulated number when a call is released due to the
cFail failure between RLC and NCCB block in the RRC
NBIoT_ConnResumeFail_RrcSi The cumulated number when a call is released due to
gTo timeout in the RRC connection resume procedure
because of not receiving
RRCConnectionResumeComplete-NB Message.
NBIoT_ConnResumeFail_S1ap The cumulated number when a call is released due to the
LinkFail S1AP link in the RRC connection resume Procedure,
because the S1AP link status is changed to Out of
service.
NBIoT_ConnResumeFail_S1ap The cumulated number when a call is released due to
SigFail receiving S1AP reset from MME in the RRC connection
resume Procedure
NBIoT_ConnResumeFallbackF The cumulated number when a call is released due to call
ail_CpCcTo control timeout in the RRC connection resume fallback
Procedure because of not receiving response message
from the protocol blocks (MAC, RLC, PDCP)
NBIoT_ConnResumeFallbackF The cumulated number when a call is released due to
ail_CpCcFail reset notification (eNB failure or block restart) in the RRC
NBIoT_ConnResumeFallbackF The cumulated number when a call is released due to the
ail_UpMacFail failure between MAC and NCCB block in the RRC
ail_UpPdcpFail failure between PDCP and NCCB block in the RRC
ail_UpRlcFail failure between RLC and NCCB block in the RRC
ail_RrcSigTo timeout in the RRC connection resume procedure

Confidential

Name
because of not receiving RRCConnectionSetupComplete-
NB Message.
ail_S1apLinkFail S1AP link in the RRC connection resume fallback
Procedure, because the S1AP link status is changed to
Out of service.
ail_S1apSigFail receiving S1AP reset from MME in the RRC connection
NBIoT_ConnResumeReject_Cp The cumulated number when a call is released due to
CcFail receiving S1AP reset from MME in the RRC connection
NBIoT_ConnResumeReject_Cp The cumulated number when eNB sends RRC
CapaCacFail Connection Reject to UE due to capacity based call
admission control failure for the suspended DRB context
NB-IoT RRC NBIoT_ConnSuspend_UpMacU The cumulated number when the RRC connection is
Connection EInact released from the eNB in order to suspend the UE since
Release a timeout occurs in UE subject to user plane optimization
after the RRC connection establishment procedure is
completed.
NB-IoT Call Fail [0x037D]EccTmout_RrcConnec A call is released when the RRC Connection Resume
tionResumeComplete Complete message is not received after the RRC
Connection Resume message is transmitted to the UE.
[0x037E]EccTmout_S1UeConte A call is released when the UE Context Resume
xtResumeResponse Response message is not received after transmitting the
UE Context Resume Request to the MME.
[0x037F]EccTmout_S1UeConte A call is released when the UE Context Suspend
xtSuspendResponse Response message is not received after transmitting the
UE Context Suspend Request to the MME.
[0x0380]EccUeSuspendUserIna A call subjected to user plane optimization is successfully
ctivity suspended due to user inactivity.
REFERENCE
[2] 3GPP TS 24.301 Non-Access-Stratum (NAS) protocol for Evolved Packet
System (EPS); Stage 3
UTRAN); X2 Application Protocol (X2AP)

Confidential

Confidential
LTE-SW3001, AM, UM and TM Data Transfer at

RLC Layer
INTRODUCTION
The eNB uses Radio Link Control (RLC) protocol in radio link according to the
3GPP TS36.322 specification to transmit data to UE. The RLC connection is
disconnected when the UE carries out handover between cells or eNBs. It must be
set up again once the UE moves to a target cell. Samsung eNB supports three RLC
transmission modes, that is, Acknowledged Mode (AM), Unacknowledged Mode
(UM), and Transparent Mode (TM).
• The AM is a packet transmission method that checks the reception of a packet
that is sent to the UE by the eNB and supports re-transmission for a lost
packet. The same method is used when the UE sends data to the eNB. The AM
is used for internet connection service or file transmission service. In this
mode, there is no packet loss during transmission because the packet is
forwarded from a source cell to a target cell in case of handover.
• The UM is a simple transmission method that does not receive
acknowledgment from the UE. This is used to support delay sensitive service
such as voice packet rather than reliability sensitive. In this mode, there may
be packet loss because there is no forwarding to a target cell in case of
handover.
• The TM does not attach a RLC header to reduce radio overhead and this is
used to send the signaling message of RRC.
An operator can set up whether to use the AM mode or UM mode for each QCI.
BENEFIT
• RLC AM provides a reliable data transfer between eNB and UE.
• RLC UM allows a simple data transfer for delay sensitive packets.
• RLC TM removes RLC overhead to save radio resources.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT

Confidential
FEATURE DESCRIPTION
The RLC is a link layer protocol that is located between the PDCP layer and MAC
layer and it is applied to the radio link section between UE and eNB. The RLC is
working in Acknowledged Mode (AM), Unacknowledged Mode (UM), or
Transparent Mode (TM) depending on service property.
• The AM supports ARQ function that checks reception of a packet and also the
packet re-transmission function to guarantee reliability. It is used for a service
where delay-robustness and data reliability are important, such as FTP, or
Internet connection.
• The UM has no data re-transmission function and it is used to quickly send
delay sensitive packets in real-time. The most common application is VoLTE.
• The TM sends Service Data Unit (SDU) received from its upper layer without
a RLC header to reduce the radio overhead.
The RLC element sends a reliable data through data error correction and flow
control by cooperating with an upper PDCP element and a lower MAC/PHY. The
signaling messages such as broadcast/common/paging control channels, which use
Signaling Radio Bearer (SRB) 0, are transmitted in TM. The other signaling
messages using SRB 1 or SRB 2 are transmitted in AM. The user data sent to the
DRB through the PDCP is transmitted in AM or UM. The operator can configure
which mode is used for each QCI through the command (CHG-RLC-INF and the
parameter RLC_MODE). Usually, the default bearer is set to the AM mode and the
bearer that sends a VoLTE packet is set to the UM mode. RLC provides the
following functionalities:
The RLC provides the following functionalities:
• AM, UM, and TM data transfer
• Error correction through ARQ (AM)
• Concatenation, segmentation, and reassembly of RLC SDUs (UM and AM)
• In-sequence delivery of upper layer PDUs except uplink PDUs during
handover (UM and AM)
• Re-segmentation of RLC data PDUs if necessary (AM)
• Duplicate detection (UM and AM)
• RLC SDU discard (UM and AM)
• RLC re-establishment
• Protocol error detection (AM)
The RLC also provides the packet buffering function. In case of UE, if the speed at
which the eNB receives from SGW is higher than the speed at which the eNB
transmits through the radio link, packets is buffered in the RLC of the eNB.
The RLC configuration information including RLC mode per bearer is transmitted
through the signaling message between the UE and the eNB.
The most outstanding features of RLC AM mode for reliable data transmission are
the ARQ and re-transmission functions. An AM RLC entity can poll its peer AM
Confidential
RLC entity to trigger STATUS reporting at the peer AM RLC entity, which is
done by including the poll flag in RLC data PDU. The RLC transmitting entity
will include the poll flag when there is no data to transmit or when t-
PollRetransmit timer expires, or when no new RLC data PDU can be transmitted,
for example, due to window stalling. The STATUS reporting includes positive
and/or negative acknowledgements of RLC PDUs or portions of them.
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of RTRV-HO-OPT/RTRV-RLC-INF/CHG-RLC-
INF/RTRV-SRB-RLC/CHG-SRB-RLC
QCI This parameter is the QoS Class Identifier (QCI). The range is 0-255. The
standard QCI defined in the standard document is 1-9. 0 and 10-255 can be
used by the operator optionally.
RLC_MODE This parameter is the mode information (AM/UM) on RLC.
ENB_TIMER_POLL_RETRAN This parameter is the timer to retransmit the poll in a transmitting AM RLC
SMIT entity.
ENB_POLL_PDU This parameter is the threshold to trigger the poll for pollPDU PDUs in an AM
RLC entity.
ENB_POLL_BYTE This parameter is the threshold used to trigger the poll for pollByte bytes in
an AM_RLC entity.
ENB_MAX_RETX_THRESHO This parameter is the threshold used to limit the number of the AMD PDU
LD retransmission in a transmitting AM_RLC entity.
ENB_TIMER_REORDERING This parameter is the timer to detect the losses of RLC PDUs in a receiving
RLC entity.
ENB_TIMER_STATUS_PRO This parameter is the timer to prohibit the transmission of STATUS_PDU in a
HIBIT receiving AM_RLC entity.
UE_TIMER_POLL_RETRANS This parameter is the timer to retransmit the poll in a UE transmitting AM RLC
MIT entity.
UE_POLL_PDU This parameter is the threshold to trigger the poll for pollPDU PDUs in an UE
AM RLC entity.
UE_POLL_BYTE This parameter is the threshold used to trigger the poll for pollByte bytes in
an UE side AM_RLC entity.
UE_MAX_RETX_THRESHOL This parameter is the threshold used to limit the number of the AMD PDU

Confidential
D retransmission in a UE side transmitting AM_RLC entity.
UE_TIMER_REORDERING This parameter is the timer to detect the losses of RLC PDUs in a UE side
receiving RLC entity.
UE_TIMER_STATUS_PROHI This parameter is the timer to prohibit the transmission of STATUS_PDU in a
BIT UE side receiving AM_RLC entity.
SN_FIELD_LENGTH This parameter is the field size of UM sequence number.
SRB_ID The ID of SRB to retrieve.
• 1: Information on SRB1.
• 2: Information on SRB2.
TIMER_POLL_RETRANSMIT This parameter is the timer to retransmit the poll in a transmitting AM RLC
entity.
POLL_PDU This parameter is the threshold to trigger the poll for pollPDU PDUs in an AM
RLC entity.
POLL_BYTE This parameter is the threshold used to trigger the poll for pollByte bytes in
an AM_RLC entity.
MAX_RETRANSMISSION_TH This parameter is the threshold used to limit the number of the AMD PDU
RESHOLD retransmission in a transmitting AM_RLC entity.
TIMER_REORDERING This parameter is the timer to detect the losses of RLC PDUs in a receiving
RLC entity.
TIMER_STATUS_PROHIBIT This parameter is the timer to prohibit the transmission of STATUS_PDU in a
receiving AM_RLC entity.
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TS36.322: Evolved Universal Terrestrial Radio Access (E-UTRA):
Radio Link Control (RLC) protocol specification

Confidential
LTE-SW3010, PDCP Sublayer Support

INTRODUCTION
This feature provides the basic PDCP sublayer functionality of LTE layer 2.
BENEFIT
This feature enables basic LTE service by supporting delivery of control/user
plane data.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
In an LTE system, the layer 2 is split into three sublayers: Medium Access Control
(MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol
(PDCP).
Figure below depicts the control plane and the user plane protocol stack of the
LTE system.
Figure below depicts the functional architecture of the PDCP sublayer.

Confidential
The detailed functions are as follows:

• Header compression and decompression of user plane data
o The operator can configure whether to enable RoHC function per QCI
(ROHC_SUPPORT by using CHG-ROHC-INF).
o Related feature: LTE-SW3011 Header Compression ROHCv1 (RTP, UDP,
IP).
• PDCP Sequence number (SN) maintenance
o The operator can configure the length of the PDCP SN size for radio
bearers that are operating in RLC UM (UM_SN_SIZE by using CHG-
PDCP-INF).
• Timer based discard of user plane data.
o The operator can configure the discard timer value (DISCARD_TIMER by
using CHG-PDCP-INF).
• Discard of duplicates.
• In-sequence delivery of upper layer PDUs at PDCP re-establishment of lower
layers for RLC AM.
• Duplicate detection/elimination of lower layer SDUs at PDCP re-
establishment for RLC AM.
• Ciphering and deciphering of user plane data and control plane data.
• Integrity protection and verification of control plane data.
The PDCP sublayer processes Signaling Radio Bearers (SRB) that are mapped to

Confidential
Dedicated Control Channel (DCCH) and Data Radio Bearers (DRB) that are
mapped to dedicated traffic channel (DTCH).
Non-IP Data Delivery Support

3GPP introduced non-IP type bearers for Non-IP Data Delivery (NIDD) to support
non-IP Packet data Network (PDN) connection for EPS Cellular Internet of Things
(CIoT) optimization in release 13. It is specified for IoT devices that do not
support IP protocol stack.
A header compression function at PDCP layer cannot be applied to non-IP bearers,
because it operates only for IP flows. Therefore, for non-IP bearers, the eNB does
not perform header compression function even if header compression is enabled at
the eNB for the bearer's QCI and UE supports header compression.
The MME delivers Bearer Type IE with non IP value in the INITIAL CONTEXT
SETUP REQUEST, E-RAB SETUP REQUEST, and HANDOVER REQUEST
message for non-IP type bearers. In X2 handover case, the source eNB delivers
Bearer Type IE to the target eNB in the HANDOVER REQUEST message.
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-ROHC-INF/RTRV-ROHC-INF
ROHC_SUPPORT This parameter indicates whether to support the ROHC in the PDCP.
• False: Does not use the ROHC for the QCI.
• True: Uses the ROHC for the QCI.
Parameter description of CHG-PDCP-INF/RTRV-ROHC-INF

UM_SN_SIZE This parameter specifies the length of the PDCP Sequence Number (SN). For an
Radio Bearer (RB) operating in the Radio Link Control Unacknowledged Mode (RLC
UM), one of the two lengths below can be set. It is not applied to an RB operating in
the RLC Acknowledged Mode (AM) because only 12 bits is allowed to be used for it
according to the specifications below.

Confidential
• 7 bits: Sets 7 bits as the PDCP SN length.
• 12 bits: Sets 12 bits as the PDCP SN length.
[Related Specifications] 3GPP TS 36.323 [6.3] Parameters
DISCARD_TIMER This parameter specifies the discard timer value for a packet buffer managed per RB
in the PDCP. The PDCP keeps buffering for re-transmission until successful
transmission is confirmed either by a lower layer or the PDCP status report and
discards the packet after the set period has elapsed.
[Related Specifications] 3GPP TS 36.323 [7.2] Timers, TS 36.331 [6.3.2] Radio
Resource control Information elements.
Counters and KPIs

Packet Loss Rate PdcpSduLossRateUL The calculated average loss rate of uplink SRB Packet
that is received in the PDCP.
PdcpSduAirIntfAvg The calculated DL PDCP SDU loss rate.
PdcpSduTotalULNum The number of UL PDCP SDUs
PdcpSduLossULNum The number of lost UL PDCP SDUs
PdcpSduTotalDLNum The number of total DL PDCP SDUs.
PdcpSduLossDLNum The number of DL PDCP SDUs lost during the
collection period. When a RLC ACK message has not
been received even after maximum retransmission, the
SDU is regarded as a lost DL PDCP SDU. This counter
only applies for RLC AM. The value 0 should be
displayed for RLC UM bearers.
REFERENCE
Packet Data Convergence Protocol (PDCP) specification

Confidential
LTE-SW3011, Header Compression ROHCv1

(RTP, UDP, IP)
INTRODUCTION
The Header Compression ROHCv1 (RTP, UDP, and IP) feature supports 3GPP
and IETF specified Robust Header Compression (RoHC) algorithm on PDCP layer
between an eNB and a UE. RoHC compresses typical 40 bytes overhead of RTP,
UDP, and IP header up to only 3 bytes by placing a compressor before the L2 link,
and placing a decompressor after that link. The opposite side decompresses and
recovers the IP/UDP/RTP header before delivery to IP layer. The main application
for RoHC algorithm is VoLTE, which is a typical RTP/UDP/IP packet.
BENEFIT
• The eNB and UE can enhance user data throughput by applying RoHC to user
data transmitted over the radio link.
• When this feature is enabled for VoLTE, the eNB can accommodate more
VoLTE users at the same time.
DEPENDENCY
The UE needs to support RoHC for header compression over the radio link.
LIMITATION
Samsung eNB only supports 0x0000, 0x0001, 0x0002, and 0x0004 profiles.
SYSTEM IMPACT
FEATURE DESCRIPTION
Samsung eNB supports RoHC algorithm on PDCP sublayer. RoHC compression is
only applied to the user plane.
Table below outlines the header compression protocol and profiles. Each profile
can be applied to each IPv4 and IPv6, however, Samsung eNB supports only
0x0000, 0x0001, 0x0002, and 0x0004 profiles.
Profile Identifier Usage: Reference
0x0000 No compression RFC 4995
0x0001 RTP/UDP/IP RFC 3095, RFC 4815
0x0002 UDP/IP RFC 3095, RFC 4815
0x0003 ESP/IP RFC 3095, RFC 4815

Confidential
Profile Identifier Usage: Reference

0x0004 IP RFC 3843, RFC 4815
0x0006 TCP/IP RFC 4996
0x0101 RTP/UDP/IP RFC 5225
0x0102 UDP/IP RFC 5225
0x0103 ESP/IP RFC 5225
0x0104 IP RFC 5225
Upon connecting to the eNB, the UE can negotiate with the eNB for the RoHC
profile information over UE-EUTRA-CAPABILITY message. Each RoHC
profile is bearer-specific, and thus, the operator can set RoHC profile for each QCI
by CHG-ROHC-INF through LSM interface. The RoHC context is never
transferred during handover. The operator can enable or disable RoHC for each
QCI, profile list, and maximum RoHC context sessions (CHG-ROHC-INF).
RoHC Architecture and Configuration

Figure below depicts the RoHC compressor at transmission side and decompressor
at reception side.
The compression consists of the three states: Initialization and Refresh (IR) state,
First-Order (FO) state, and Second-Order (SO) state.
• IR state: The compressor has just been created or reset, and full packet headers
are sent.
• FO state: The compressor has detected and stored the static fields (such as IP
Confidential
addresses and port numbers) on both sides of the connection. The compressor
is also sending dynamic packet field differences in FO state. Thus, FO state is
essentially static and pseudo-dynamic compression.
• SO state: The compressor is suppressing all dynamic fields such as RTP
sequence numbers, and sending only a logical sequence number and partial
checksum to cause the other side to predictively generate and verify the
headers of the next expected packet.
In general, FO state compresses all static fields and most dynamic fields. SO state
is compressing all dynamic fields predictively using a sequence number and
checksum. When mismatch of the state happens, due to the change of the header
information, the compressor in the eNB side begins to transmit full header to
synchronize the context state.
According to RFC 3095 the ROHC method has three modes of operation: the
Unidirectional, the Bidirectional Optimistic, and the Bidirectional Reliable mode.
• In the Unidirectional mode of operation, packets are only sent in one direction:
from compressor to decompressor. This mode therefore makes ROHC usable
over links where a return path from decompressor to compressor is unavailable
or undesirable.
• The Bidirectional Optimistic mode (O-mode) is similar to the Unidirectional
mode, except that a feedback channel is used to send error recovery requests
and (optionally) acknowledgments of significant context updates from the
decompressor to compressor. The O-mode aims to maximize compression
efficiency and sparse usage of the feedback channel.
• The Bidirectional Reliable mode differs in many ways from the previous two.
The most important differences are a more intensive usage of the feedback
channel and a stricter logic at both the compressor and the decompressor that
prevents loss of context synchronization between compressor and
decompressor except for very high residual bit error rates.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-ROHC-INFO and set ROHC_SUPPORT of each QCI as True.

Confidential
• Run CHG-ROHC-INFO and set ROHC_SUPPORT of each QCI as False.
Key Parameters
parameters.
Parameter Descriptions of CHG-ROHC-INFO/RTRV-ROHC-INFO
ROHC_SUPPORT This parameter sets whether to support the RoHC in the PDCP.
• False: Does not use the RoHC for the QCI.
• True: Uses the RoHC for the QCI.
Configuration Parameter
parameters.
Parameter Descriptions of CHG-ROHC-INFO/RTRV-ROHC-INFO
MAX_CONTEXT_SES This parameter sets the maximum number of Active ROHC Contexts that the eNB
SION and the UE can support.
PROFILE0001 This parameter indicates whether to support the ROHC profile0001 (RTP/UDP/IP,
RFC3095/4815).
• False: The QCI does not support profile0001.
• True: The QCI supports profile0001.
PROFILE0002 This parameter indicates whether to support the ROHC profile0002 (UDP/IP,
RFC3095/4815).
PROFILE0003 This parameter indicates whether to support the ROHC profile0003 (ESP/IP,
RFC3095/4815).
PROFILE0004 This parameter indicates whether to support the ROHC profile0004 (IP,
RFC3095/4815).
PROFILE0006 This parameter indicates whether to support the ROHC profile0006 (TCP/IP,
RFC4996).
PROFILE0101 This parameter indicates whether to support the ROHC profile0101 (RTP/UDP/IP,
RFC5225).

Confidential
PROFILE0102 This parameter indicates whether to support the ROHC profile0102 (UDP/IP,
RFC5225).
PROFILE0103 This parameter indicates whether to support the ROHC profile0103 (ESP/IP,
RFC5225).
PROFILE0104 This parameter indicates whether to support the ROHC profile0104 (IP, RFC5225).
Counters and KPIs

CP_PACKET RoHCDecompFailRate The RoHC decompression failure rate of PDCP uplink
DRB packet. Therefore, the denominator is the total
number of received packets, RoHC decompression
success SDU, and RoHC decompression failure SDU.
RoHCDecompFailCnt The number of RoHC decompression failed UL PDCP
SDUs.
RoHCDecompSuccCnt The number of RoHC decompression succeeded UL
PDCP SDUs.
REFERENCE
[2] IETF RFC3095 Robust Header Compression (ROHC): Framework and four
profiles: RTP, UDP, ESP, and uncompressed
[3] IETF RFC3759 Robust Header Compression (ROHC): Terminology and
Channel Mapping Examples
[4] IETF RFC3843 Robust Header Compression (ROHC): A Compression Profile
for IP
[5] IETF RFC4815 Robust Header Compression (ROHC): Corrections and
Clarifications to RFC 3095
[6] IETF RFC4995 Robust Header Compression (ROHC) Framework
[7] IETF RFC4996 Robust Header Compression (ROHC): A Profile for TCP/IP
(ROHC-TCP)
[8] IETF RFC5225 Robust Header Compression Version 2 (ROHCv2): Profiles
for RTP, UDP, IP, ESP and UDP-Lite

Confidential
LTE-SW3013, ROHC IPv6 Support

INTRODUCTION
Samsung eNB supports 3GPP and IETF complaint Robust Header Compression
(RoHC) IPv6 feature. This feature provides an efficient and flexible header
compression mechanism at the PDCP layer, which improves the bandwidth
utilization for VoLTE services with small payload size. It compresses the
RTP/UDP/IP header of data packets that are transmitted between UE and eNB.
BENEFIT
• The eNB and UE can enhance user data throughput by applying RoHC to user
data transmitted over the radio link.
• When this feature is enabled for VoLTE, the eNB can accommodate more
VoLTE users at the same time.
DEPENDENCY
Others:
• The UE must support RoHC over the radio link.
• UE must support both IPv4 and IPv6 addresses.
LIMITATION
Samsung eNB only supports 0x0000, 0x0001, 0x0002, and 0x0004 profiles.
SYSTEM IMPACT
FEATURE DESCRIPTION
Samsung eNB supports RoHC algorithm on PDCP sublayer. RoHC compression is
only applied to the user plane. Table below outlines the header compression
protocol and profiles. Each profile can be applied to each IPv4 and IPv6. Samsung
eNB supports 0x0000, 0x0001, 0x0002, and 0x0004 profiles.
Profile Identifier Usage Reference
0x0000 No compression RFC 4995
0x0001 RTP/UDP/IP RFC 3095, RFC 4815
0x0002 UDP/IP RFC 3095, RFC 4815
0x0003 ESP/IP RFC 3095, RFC 4815
0x0004 IP RFC 3843, RFC 4815
0x0006 TCP/IP RFC 4996

Confidential
Profile Identifier Usage Reference

0x0101 RTP/UDP/IP RFC 5225
0x0102 UDP/IP RFC 5225
0x0103 ESP/IP RFC 5225
0x0104 IP RFC 5225
Upon connecting to the eNB, the UE shall be able to negotiate with the eNB,
RoHC profile information over UE-EUTRA-CAPABILITY message. Each RoHC
profile is bearer specific, thus, the operator may set RoHC profile for each QCI via
CHG-ROHC-INF command through LSM interface. The RoHC context is never
transferred during handover. An operator can set Enable/Disable RoHC for each
QCI, profile list, and maximum RoHC Context sessions (CHG-ROHC-INF).
RoHC Architecture and Configuration

The figure below depicts the RoHC compressor (transmission side) and
decompressor (reception side).
The compression consists of the three states: Initialization and Refresh (IR) state,
First-Order (FO) state, and Second-Order (SO) state.
• IR state: The compressor has just been created or reset, and full packet headers
are sent.
• FO state: The compressor has detected and stored the static fields (such as IP
addresses and port numbers) on both sides of the connection. The compressor
is also sending dynamic packet field differences in FO state. Thus, FO state is
essentially static and pseudo-dynamic compression.

Confidential
• SO state: The compressor is suppressing all dynamic fields such as RTP

sequence numbers, and sending only a logical sequence number and partial
checksum to cause the other side to predictively generate and verify the
headers of the next expected packet.
In general, FO state compresses all static fields and most dynamic fields. SO state
is compressing all dynamic fields predictively using a sequence number and
checksum. When mismatch of the state happens, due to the change of the header
information, the compressor in the eNB side begins to transmit full header to
synchronize the context state.
According to RFC 3095 the ROHC scheme has three modes of operation: the
Unidirectional, the Bidirectional Optimistic, and the Bidirectional Reliable mode.
• In the Unidirectional mode of operation, packets are only sent in one direction:
from compressor to decompressor. This mode therefore makes ROHC usable
over links where a return path from decompressor to compressor is unavailable
or undesirable.
• The Bidirectional Optimistic mode (O-mode) is similar to the Unidirectional
mode, except that a feedback channel is used to send error recovery requests
and (optionally) acknowledgments of significant context updates from the
decompressor to compressor. The O-mode aims to maximize compression
efficiency and sparse usage of the feedback channel.
• The Bidirectional Reliable mode differs in many ways from the previous two.
The most important differences are a more intensive usage of the feedback
channel and a stricter logic at both the compressor and the decompressor that
prevents loss of context synchronization between compressor and
decompressor except for very high residual bit error rates.
System Operation
How to Activate
The IPv6 is not controlled by any command. It is applied to the IP address version.
• Run CHG-ROHC-INF and set the parameters for activating ROHC support for
each QCI.
• Run CHG-ROHC-INF and set the parameters for deactivating ROHC support
for each QCI.

Confidential
Key Parameters
parameter.
Parameter Descriptions of CHG-ROHC-INF/RTRV-ROHC-INF
QCI Indicates QoS Class Identifier (QCI) index.
The range is from 0 to 255, where QCI defined in the standard is 1 to 9.
Operator can use QCI values 0 and 10 to 255.
ROHC_SUPPORT Determines whether to support ROHC feature or not.
MAX_CONTEXT_SESSION Indicates the maximum number of ROHC context sessions supported per
call. The supported sessions are:
• Max_2: Supports up to 2 sessions per call
• Max_16: Supports up to 16 sessions per call (default)
PROFILE0001 Determines whether to support the profile0001 (RTP/UDP/IP).
PROFILE0002 Determines whether to support the profile0002 (UDP/IP).
PROFILE0003 Determines whether to support the profile0003 (ESP/IP).
PROFILE0004 Determines whether to support the profile0004 (IP).
PROFILE0006 Determines whether to support the profile0006 (TCP/IP).
PROFILE0101 Decides whether to support the profile0101 (RTP/UDP/IP).
PROFILE0102 Decides whether to support the profile0102 (UDP/IP).
PROFILE0103 Decides whether to support the profile0103 (ESP/IP).
PROFILE0104 Decides whether to support the profile0104 (IP).
Counters and KPIs

with this feature.
REFERENCE
[1] The RoHC IPv6 feature complies with the RFC3095 standard.

Confidential
LTE-SW3051, Integrity Protection:

Null/SNOW3G/AES
INTRODUCTION
As per compliance of the data integrity discipline of communication, eNB shall
ensure that the data is not modified during the transmission. Samsung eNB
supports integrity protection to RRC-signaling as per 3GPP TS33.401.
BENEFIT
RRC-signaling messages between a UE and the eNB are integrity protected.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Samsung eNB supports integrity protection of RRC-signaling messages according
to 3GPP standard TS33.401.
The input parameters to the integrity algorithm are as follows:
• KEY: A 128-bit integrity key
• COUNT: 32-bit count
• BEARER: A 5-bit bearer identity
• DIRECTION: 1-bit direction of the transmission, 0 for uplink and 1 for
downlink
• MESSAGE: Message itself
• LENGTH: Bit length of the MESSAGE
Figure below depicts the use of integrity algorithm EIA to authenticate the
integrity of messages.

Confidential
Integrity protection applies to control plane messages whereas ciphering covers all
radio bearers including control plane and user plane. To ensure integrity for UE-
eNB communications, the integrity value (MAC-I) calculated and sent by one
party is compared with the recalculated value of the other party after receiving the
message. If any inconsistency found, the message is deemed altered during
transmission, and is discarded.
The detailed procedure is explained below:
• The RRC block of eNB acknowledges the Initial Context Setup Request and
selects an AS algorithm.
• The preferred integrity algorithm is specified by INTEGRITY_EA_PRIOR
(CHG-SECU-INF). (The command RTRV-SECU-INF is used to check
current preferred algorithm.)
The algorithm identical to the one sent using UE Security Capabilities IE of
the Initial Context Setup Request is selected. The RRC block derives from
KeNB, Krrc_int, Krrc_enc, and Kup_enc.
• The RRC block sends the selected algorithm, Krrc_int, Krrc_enc, and
Kup_enc to the PDCP block. The integrity protection should be applied to the
subsequent RRC message.
• After receiving acknowledgement from the PDCP, RRC block sends the
SecurityModeCommand message to UE, along with the selected algorithm.
• After receiving the Security Mode Complete message from UE, RRC block
controls the PDCP block to apply ciphering for SRB #1. The PDCP block then
applies integrity/ciphering protection to all subsequent radio bearers.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-SECU-INF and set INTEGRITY_EA_PRIOR to EIA1 or EIA2.
• Run CHG-SECU-INF and set INTEGRITY_EA_PRIOR to EIA0.
Key Parameters
parameter.
INTEGRITY_EA_PRIOR The integrity protection algorithm supported by the eNB.
• EIA0: NULL, EIA1: SNOW 3G, EIA2: AES
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 33.401: 3GPP System Architecture Evolution (SAE); Security
architecture
Radio Resource Control (RRC); Protocol Specification

Confidential
LTE-SW3052, Ciphering: Null/SNOW3G/AES

INTRODUCTION
As per compliance of the data confidentiality discipline of communication, eNB
shall ensure that the data is ciphered during the transmission. Samsung eNB
supports ciphering to RRC-signaling and User plane data as per 3GPP TS33.401.
BENEFIT
• An operator can prevent UE tracking based on cell level measurement reports.
• A user can support privacy protection for user information.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Samsung eNB supports confidentiality of RRC signaling and User plane messages
according to 3GPP standard TS33.401.
The input parameters to the ciphering algorithm are as follows:
• Key: A 128-bit cipher key
• COUNT: A 32-bit count
• BEARER: A 5-bit bearer identity
• DIRECTION: An 1-bit direction of the transmission, 0 for uplink and 1 for
downlink
• LENGTH: The length of the keystream
Figure below depicts the use of integrity algorithm EIA to authenticate the
integrity of messages.

Confidential
Ciphering applies to control plane and user plane messages whereas integrity
protection applies to control plane messages only.
The detailed procedure is as follows:
1 The RRC block of eNB acknowledges the Initial Context Setup Request and
selects an AS algorithm.
2 The preferred ciphering algorithm is specified by CIPHERING_EA_PRIOR
(CHG-SECU-INF). (The command RTRV-SECU-INF is used to check
current preferred algorithm.)
The algorithm identical to the one sent using UE Security Capabilities IE of
the Initial Context Setup Request is selected. The RRC block derives from
KeNB, Krrc_int, Krrc_enc, and Kup_enc.
3 The RRC block sends the selected algorithm, Krrc_int, Krrc_enc, and
Kup_enc to the PDCP block. The integrity protection should be applied to the
subsequent RRC message.
4 After receiving acknowledgement from the PDCP, the RRC block sends the
SecurityModeCommand message to UE, along with the selected algorithm.
5 After receiving the Security Mode Complete message from UE, the RRC
block controls the PDCP block to apply ciphering for SRB #1. The PDCP
block then applies integrity/ciphering protection to all subsequent radio
bearers.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-SECU-INF and set CIPHERING_EA_PRIOR to EIA1 or EIA2.
• Run CHG-SECU-INF and set CIPHERING_EA_PRIOR to EIA0.
Key Parameters
parameter.
CIPHERING_EA_PRIOR The ciphering algorithm supported by the eNB.
• EIA0: NULL, EIA1: SNOW 3G, EIA2: AES
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 33.401: 3GPP System Architecture Evolution (SAE); Security
architecture

Confidential
LTE-SW4101, Capacity Based Call Admission

Control
INTRODUCTION
The Call Admission Control (CAC) function is basically enabled to efficiently use
the limited radio resources, to guarantee the quality of user service even in case of
congestion, and to protect eNB system from being overloaded.
Three call admission control functionalities are, Capacity-based Call Admission
Control, QoS-based Call Admission Control and Pre-emption. The Capacity-based
CAC makes a decision based on the capacity that an operator configures in
advance. The QoS-based CAC makes a decision based on the required QoS level
and available radio resources of that time. It has an effect only when MME
requests GBR bearers. Pre-emption allows a priority call. These three
functionalities work at the same time.
The operator can configure the capacity per cell and per eNB. To sustain a certain
level of QoS for non-GBR services, operator can limit the maximum number of
users allowed per cell. In addition, the operator can configure the amount of
resources that are reserved for incoming handover calls. In this case, the call
admission algorithms make a decision based on the capacity that reflects the
reserved resources. In case of no resources, emergency calls are allowed by
preempting existing calls.
BENEFIT
• By limiting the maximum number UEs or bearers per cell and per eNB,
considering radio and backhaul bandwidth, operator can control the minimum
QoS level provided for UEs.
• The operator can protect the system from being shut down due to overload or
congestion
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT

Confidential
FEATURE DESCRIPTION
The Capacity-based CAC operates on the RRC connection establishment and E-
RAB bearer establishment while the QoS-based CAC and Pre-emption has impact
on E-RAB bearer establishment only.
Figure below depicts the overall call admission control procedure.
Capacity-based CAC
The Capacity-based CAC allows an incoming call or bearer as long as the total
number of calls/bearers does not exceed the pre-configured thresholds per cell and
eNB. The operator can configure four types of thresholds, threshold for normal,
threshold for emergency and handover user, hihgPriorityAccess (HPA) users, and
the maximum. These thresholds per eNB are depicted in figure below.
Normal users can be allowed up to NOR_ENB_CALL_COUNT per eNB.
Emergency and HO users can be allowed up to EM_HO_ENB_CALL_COUNT
per eNB. HPA users are allowed up to HPA_ENB_CALL_COUNT. These
thresholds can be configured for CAC by using
CALL_CAC_THRESH_FOR_NORMAL, CALL_CAC_THRESH_FOR_EMER_HO,
and CALL_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS as follows:
• NOR_ENB_CALL_COUNT = MAX_ENB_CALL_COUNT *
CALL_CAC_THRESH_FOR_NORMAL for the corresponding eNB,
• EM_HO_ENB_CALL_COUNT = MAX_ENB_CALL_COUNT *
CALL_CAC_THRESH_FOR_EMER_HO for the corresponding eNB.

Confidential
• HPA_ENB_CALL_COUNT = MAX_ENB_CALL_COUNT *
CALL_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS for the
corresponding eNB.
Similar thresholds per cell can also be configured, as depicted in figure below.
Normal users can be allowed up to NOR_CELL_CALL_COUNT per cell.
Emergency and HO users can be allowed up to EM_HO_CELL_CALL_COUNT
per cell. HPA users can be allowed up to HPA_CELL_CALL_COUNT. These
thresholds can be configured for CAC by using
CALL_CAC_THRESH_FOR_NORMAL, CALL_CAC_THRESH_FOR_EMER_HO,
and CALL_CAC_THRESHOLD_FOR_HIGH_PRIORITY_ACCESS as follows:
• NOR_CELL_CALL_COUNT = MAX_CELL_CALL_COUNT *
CALL_CAC_THRESH_FOR_NORMAL for the corresponding cell.
• EM_HO_CELL_CALL_COUNT = MAX_CELL_CALL_COUNT *
CALL_CAC_THRESH_FOR_EMER_HO for the corresponding cell.
• HPA_CELL_CALL_COUNT = MAX_CELL_CALL_COUNT *
CALL_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS for the
corresponding cell.
In addition, there is another threshold for generating a notification if the number of
admitted UEs in the cell exceeds the threshold.
For radio bearer, the capacity-based CAC applies similar concept per cell, as
depicted in figure below. Bearers for normal users can be allowed up to
NOR_DRB_CALL_COUNT per cell. Bearers for emergency and HO users can be
allowed up to EM_HO_DRB_COUNT per cell. Bearers for HPA users can be
allowed up to HPA_DRB_COUNT. Theses thresholds can be configured for CAC
by using DRB_CAC_THRESH_FOR_NORMAL,
DRB_CAC_THRESH_FOR_EMER_HO, and
DRB_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS as follows:
• NOR_DRB_COUNT = MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_NORMAL for the corresponding cell,
• EM_HO_DRB_COUNT= MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_EMER_HO for the corresponding cell.
Confidential
• HPA_DRB_COUNT = MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS for the
corresponding cell.
In addition, there is another threshold for generating a notification if the number of
admitted bearers in the cell exceeds the threshold.
eNB Capacity-based CAC Parameters

For the capacity, the operator should consider the hardware platform and radio
resources, for example, radio bandwidth, the number of channel card, QoS level.
The following table shows an example in case of 10 MHz bandwidth and the
maximum values in the following table can be different in different channel card.
The following table shows an example of system parameters configuration for
capacity-based CAC. The system parameter configuration can be different
according to channel card and system bandwidth.
System Parameters Criteria (10 Mhz BW) Decision
MaxUeCELL 600 Current # of UEs of the cell <
(=MAX_CELL_CALL_COUNT) MaxUeCELL
MaxUeENB 1800 Current # of UEs of the eNB <
(=MAX_ENB_CALL_COUNT) MaxUeENB
MaxRbUE 8 Current # of bearers of the UE <
MaxRbUE
MaxRbCELL 1200 Current # of bearers of the cell <
(=MAX_DRB_COUNT) MacRbCELL
In this context, the number of active UEs is equal to the number of active RRC
Connections. For the number of bearers, GBR bearers and Non-GBR bearers are
counted all together.
Maximum number of radio bearers per UE, which counts only data radio bearers
excluding signaling radio bearers, is limited by MAC layer protocol specification
(3GPP TS 36.321) and it is not configurable by operator.
The operator can configure the amount of resources that are reserved for incoming
handover calls. In this case, the call admission algorithms make a decision based
on the capacity that reflects the reserved resources.
Capacity-based CAC Operation

This section describes the capacity-based CAC operation in each call procedure.

Confidential
Capacity based CAC Operation at RRC Connection Establishment
1 During the RRC connection establishment, the eNB capacity-based CAC

operates per call. The procedure starts when the RRC connection request
message is received from the UE.
2 The eNB capacity-based CAC procedure is initiated. Firstly, the CAC
operates at eNB level. If eNB level CAC is passed, cell level CAC proceeds.
Detailed procedure can be described as follows:
a eNB level CAC:
i If the attempted RRC Connection is for normal user,
NOR_ENB_CALL_COUNT is applied for the threshold. If the current
number of UEs in the eNB is less than NOR_ENB_CALL_COUNT,
eNB level CAC for the RRC Connection is passed. Otherwise, the call
is rejected.
ii If the attempted RRC Connection is for an emergency user,
EM_HO_ENB_CALL_COUNT is applied for the threshold. If the
current number of UEs in the eNB is less than
EM_HO_ENB_CALL_COUNT, eNB level CAC for the RRC
Connection is passed. Otherwise, the call is rejected.
b Cell level CAC
i If the attempted RRC Connection is for normal user,
NOR_CELL_CALL_COUNT is applied for the threshold. If the
current number of UEs in the cell is less than
NOR_CELL_CALL_COUNT, eNB level CAC for the RRC
ii If the attempted RRC Connection is for an emergency user,
EM_HO_CELL_CALL_COUNT is applied for the threshold. If the
current number of UEs in the cell is less than
EM_HO_CELL_CALL_COUNT, eNB level CAC for the RRC
3 If the call is rejected and RRCConnectionReject is sent to UE,
depriotisationReq IE can be populated according to the configuration.

Confidential
RRCConnectionReject-v1130-IEs ::= SEQUENCE {

deprioritisationReq-r11 SEQUENCE {
deprioritisationType-r11 ENUMERATED {frequency, e-utra},
deprioritisationTimer-r11 ENUMERATED {min5, min10, min15, min30}
} OPTIONAL, -- Need ON
nonCriticalExtension SEQUENCE {} OPTIONAL}
4 If both eNB and cell level CAC is passed, RRC connection establishment is
initiated by transmitting the RRC connection setup message to the UE. If the
call is rejected and the call type is emergency call, the longest call among
active calls in the cell is released. For a normal call, the RRC connection
release message is transmitted to the UE and the call is released.
5 The UE transmits the RRC Connection Setup Complete message.
6 The eNB sends the MME Initial UE message.
Capacity based CAC Operation at E-RAB Setup
7 After the RRC establishment, the eNB capacity-based CAC operates by

receiving the initial context setup request or E-RAB setup/modify request
message from the MME for the default radio bearer and dedicated radio
bearer (DRB) setup.
8 The eNB capacity-based CAC runs per E-RAB.
o If the attempted bearer is for normal user, NOR_DRB_COUNT is applied
for the threshold. If the current number of bearers in the cell is less than
NOR_DRB_COUNT, the call is admitted. Otherwise, the call is rejected.
o If the attempted bearer is for emergency user, EM_HO_DRB_COUNT is
applied for the threshold. If the current number of bearers in the cell is less
than EM_HO_DRB_COUNT, the call is admitted. Otherwise, the call is
rejected.
3 to 4) If the E-RAB is successfully admitted, the RRC connection reconfiguration
message is transmitted to the UE to initiate an E-RAB (DRB) establishment. If the
call is rejected, whether to admit the E-RAB is determined in interoperation with
the preemption function per E-RAB (DRB) to control the call flow.
In the case that not all bearers can be admitted, bearers can be handled as follows

Confidential
according to the configuration:

a A partial success per E-RAB is ignored (whole bearers are rejected) if a
partial success flag is not set.
b Possible E-RABs are admitted if a partial success flag is set.
5) The eNB sends the MME E-RAB setup message.
Capacity based CAC Operation at intra-eNB Handover
1 The eNB receives a measurement report from a UE.

2 When cell change take places within the same eNB, the eNB capacity-based
CAC operates to control intra-eNB handover call admission.
3 The eNB capacity-based CAC is initiated based on a call. If the current
number of UEs in the cell is less than EM_HO_ENB_CALL_COUNT, the call
is admitted. Otherwise, the call is rejected. If the current number of bearers in
the cell is less than EM_HO_DRB_COUNT, the call is admitted. Otherwise, the
call is rejected.
4 If the call is admitted, the RRC connection reconfiguration message is
transmitted to the UE to initiate the intra-eNB handover. If the call is
rejected, whether to admit the E-RAB is determined in interoperation with the
preemption function per E-RAB (DRB) to control the call flow.
In the case that not all bearers can be admitted, bearers can be handled as
follows according to the configuration:
5 The UE transmits RRC connection reconfiguration complete message.

Confidential
Capacity based CAC Operation at inter-eNB Handover

2 The source eNB determines HO and sends the target eNBs a Handover
Request message.
3 To control inter-eNB handover call admission, the eNB capacity-based CAC
operates by using the E-RAB Level QoS parameter included in the Handover
Request message received. The eNB capacity-based CAC is initiated based
on a call. If the current number of UEs in the cell is less than
EM_HO_ENB_CALL_COUNT, the call is admitted. Otherwise, the call is
rejected. If the current number of bearers in the cell is less than
EM_HO_DRB_COUNT, the call is admitted. Otherwise, the call is rejected.
4 If the call is admitted, the Handover Request Acknowledge message is
transmitted to the source eNB to initiate the inter-eNB handover. If the call is
rejected, whether to admit the E-RAB is determined in interoperation with the
preemption function per E-RAB (DRB) to control the call flow.
In the case that not all bearers can be admitted, bearers can be handled as
follows according to the configuration:
5 and 6) The source eNB transmits the RRC connection reconfiguration message
to the UE and performs SN Status Transfer.
8 to 10) After path switch procedure, the target eNB sends Release Request the
source eNB.

Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-ENB-CAC and set CALL_COUNT_CAC_USAGE to use.
• Run CHG-CELL-CAC and set CELL_COUNT_CAC_USAGE to use.
• Run CHG-ENB-CAC and set CALL_COUNT_CAC_USAGE to no_use.
• Run CHG-CELL-CAC and set CELL_COUNT_CAC_USAGE to no_use.
Key Parameters
parameters.
Parameter Descriptions of CHG-ENB-CAC/RTRV-ENB-CAC, CHG-CELL-
CAC/RTRV-CELL-CAC
CALL_COUNT_CAC_USAGE Whether to execute the Capacity-based Call Admission Control (CAC)
function per cell.
• ci_no_use: The capacity-based CAC function per base station is not
performed.
• ci_use: The capacity-based CAC function per base station is performed.
CELL_COUNT_CAC_USAGE Whether to execute the call count-based CAC function, which is one of the
capacity based Call Admission Control (CAC) functions per cell.
• ci_no_use: The capacity-based CAC function per cell is not performed.
• ci_use: The capacity-based CAC function per cell is performed.
parameters.

Confidential
CALL_COUNT_CAC_USAGE Whether to execute the Capacity-based Call Admission Control (CAC)
function per cell.
• ci_no_use: The capacity-based CAC function per base station is not
performed.
• ci_use: The capacity-based CAC function per base station is performed.
MAX_ENB_CALL_COUNT The limit for capacity based CAC at the eNB level. The number of calls that
can be allowed by the eNB. This parameter cannot be changed.
CALL_CAC_THRESH_FOR_ The percentage of the allowable calls to the total normal calls. When a
NORMAL normal call is requested, if the number of connected calls exceeds
MAX_ENB_CALL_COUNT * CALL_CAC_THRESH_FOR_NORMAL, the
Capacity-based CAC Fail is generated.
CALL_CAC_THRESH_FOR_ Emergency call availability of total handover calls in percentage. When a
EMER_HO normal call is requested, if the number of connected calls exceeds
MAX_ENB_CALL_COUNT * CALL_CAC_THRESH_FOR_EMER_HO, the
Capacity-based CAC Fail is generated.
CALL_CAC_THRESH_FOR_ This parameter is the acceptable percentage of high priority access calls. If
HIGH_PRIORITY_ACCESS the number of attached calls exceeds the MAX_CALL_COUNT *
CALL_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS value when high
priority access call is requested, the Capacity based CAC Failure is
generated.
This threshold is valid only if HIGH_PRIORITY_ACCESS_TYPE is
configured as independentOperationType (Related CLI : RTRV-ENB-CAC).
CHECK_UE_ID_USAGE Whether to execute the SAE Temporary Mobile Station Identifier (S-TMSI)
Duplication Check function for a new call.
• ci_no_use: The S-TMSI Duplication Check function is not performed.
• ci_use: The S-TMSI Duplication Check function is performed. If a call is
found as a duplicate, the existing call is released and the new call is
accommodated.
HIGH_PRIORITY_ACCESS_T This parameter determines the type of a highpriorityaccess call. If the type is
YPE normalType, handles the highpriorityaccess as a normal call.
If the type is emergencyType, handles the highpriorityaccess as an
emergency call.
If the type is independentOperationType, handles the highpriorityaccess as
independent call type.
EMERGENCY_DURATION This parameter is the time taken to recognize a UE that includes the s-TMSI
in paging as an emergency call. If the s-TMSI included in the paging
message comes in with a call within the EMERGENCY_DURATION time, it is
handled as an emergency call.
CAC_NOTIFICATION_USAG Control on/off of the feature to send a notification to LSM when the calls or
E DRBs exceed the call or drb Notification Threshold set by RTRV/CHG- CELL-
CAC.
CAC_NOTIFICATION_MONIT Decide whether to generate a notification again after the period from the
ORING_PERIOD moment when a call or DRB CAC notification was generated as the calls or
DRBs were created more than the set Notification threshold.

CELL_NUM This parameter is the number of cells. This value must
not exceed the maximum number of cells supported by
the system. It is determined by FA/Sector. For example,
if the maximum capacity provided to the carrier per
system is 1 FA/3 Sector, up to 3 cells are supported.

Confidential
CELL_COUNT_CAC_USAGE This parameter indicates whether to perform call count
based CAC among the cell-based capacity based Call
Admission Control (CAC) functions.
• no_use: Does not perform the capacity based CAC
function per cell.
• use: Performs the capacity based CAC function per
cell.
MAX_CALL_COUNT This parameter indicates the maximum call count in a
Cell. This value is used during Capacity based CAC(Call
Admission Control) per cell.
The maximum call count is recommended based on
system performance and RRH bandwidth. Be sure not to
increase more than contracted system capacity per cell.
This parameter cannot be changed.

CALL_CAC_THRESH_FOR_NORMAL This parameter is capacity based CAC threshold for
normal calls (for example, Attach and Idle to Active) of
the cell. If the number of connected calls exceeds
MAX_CALL_COUNT * CALL_CAC_THRESH_
FOR_NORMAL when a normal call is requested, the
capacity based CAC failure is generated.
• If this parameter is too high, the system load after
CAC is probably too high, which results in system
congestion.
• If it is too low, the call requests are more likely to be
failed, and some resources may be idled and wasted.
CALL_CAC_THRESH_FOR_EMER This parameter is the capacity based CAC threshold for
emergency calls of the cell. If the number of connected
calls exceeds MAX_CALL_COUNT *
CALL_CAC_THRESH_FOR_EMER when an
emergency is requested, a capacity based CAC failure
is generated.
congestion.
• If it is too low, the call requests are more likely to fail,
and some resources may be idled and wasted.
CALL_CAC_THRESH_FOR_HO This parameter is the capacity based CAC threshold for
incoming handover call without emergency priority. If the
number of connected calls exceeds
MAX_CALL_COUNT * CALL_CAC_THRESH_FOR_HO
when an incoming handover call is requested, a capacity
based CAC failure is generated.
congestion.
CALL_CAC_THRESH_FOR_MO_SIG This parameter is the capacity based CAC threshold for
Mobile Originating Signaling calls of the cell. If the
MAX_CALL_COUNT *
CALL_CAC_THRESH_FOR_MO_SIG when a incoming
call with establishment cause = mo_Signaling call is
requested, a capacity based CAC failure is generated.

Confidential
congestion.
CALL_CAC_THRESH_FOR_MT_ACCESS This parameter is the capacity based CAC threshold for
Mobile Terminating Access calls of the cell. If the
MAX_CALL_COUNT *
CALL_CAC_THRESH_FOR_MT_ACCESS when a
incoming call with establishment cause = mt-Access call
is requested, a capacity based CAC failure is generated.
congestion.
CALL_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS This parameter is the capacity based CAC threshold for
high priority access calls (for example, Attach and Idle to
Active) of the cell. If the number of connected calls
exceeds MAX_CALL_COUNT * CALL_CAC_THRESH_
FOR_HIGH_PRIORITY_ACCESS when a high priority
access call (an incoming call with establishment cause
with highPriorityAccess with system configuration option
of the HIGH_PRIORITY_ACCESS_TYPE (related CLI :
RTRV-ENB-CAC) is independentOperationType) is
requested, a capacity based CAC failure is generated.
If this parameter is too high, the system load after CAC
is probably too high, which results in system congestion.
If it is too low, the call requests are more likely to fail,
DRB_COUNT_CAC_USAGE This parameter indicates whether to perform E-UTRAN
Radio Access Bearer (E-RAB) based CAC among the
capacity based CAC per cell.
• no_use: Does not perform the E-RAB number based
CAC per cell.
• use: Performs the E-RAB number based CAC per cell.
MAX_DRB_COUNT This parameter is the maximum number of EUTRAN
radio access bearer(E-RAB) used by capacity based call
admission control(CAC) per cell. The DRB count within
the cell cannot exceed this value. Actually applicable
number limit is determined through a calculation using
DRB_CAC_THRESH_FOR_NORMAL /
DRB_CAC_THRESH_FOR_EMER_HO.
This parameter cannot be changed.

DRB_CAC_THRESH_FOR_NORMAL This parameter is acceptable percentage of normal
calls. If the number of connected calls exceeds
MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_NORMAL when a normal
call is requested, the Capacity based CAC Failure is
generated.
congestion.

Confidential
DRB_CAC_THRESH_FOR_EMER_HO This parameter is acceptable percentage of emergency
calls and handover calls. If the number of connected
calls exceeds MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_EMER_HO when a normal
call is requested, the Capacity based CAC Failure is
generated.
congestion.
DRB_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS This parameter is acceptable percentage of high priority
access calls. If the number of connected DRBs exceeds
MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS
when a high priority access call is requested, a Capacity
based CAC Failure is generated.
This threshold is vaild only if
HIGH_PRIORITY_ACCESS_TYPE is configured as
independentOperationType (Related CLI : RTRV-ENB-
CAC).
If this parameter is too high, the system load after CAC
is probably too high, which results in system congestion.
If it is too low, the call requests are more likely to fail,
LOW_CALL_REL_OPTION When doing CAC about the new emergency Call,
Determine the operation method releasing the already
attached normal call. (If there is no Normal call among
the existing call at all, the new emergency call reception
is impossible.)
• LongestCall: Release UE with the Longest Call base.
• ArpBased: Release UE with ARP base.
• No_use: Release is not performed although the
Normal Call remains.
EMERGENCY_ARP_PRIORITY This parameter defines priority of emergency call or
priority call.
CALL_CAC_NOTIFICATION_THRESHOLD Call CAC notification is generated when the number of
UEs attached to the cell/ maxCallCount of the cell
exceeds the threshold while CAC Notification is on.
DRB_CAC_NOTIFICATION_THRESHOLD Drb CAC notification is generated when the number of
DRBs set in the cell / maxDrbCount of the cell exceeds
the threshold while CAC Notification is on.
PARTIAL_CAC_USAGE It is a parameter to set whether to support Partial CAC in
the eNB. If the parameter is set to ‘Use’, it operates in a
way that as many bearers as possible are accepted
even if the available resources are insufficient when
multiple bearers are requested for a new call.

Confidential
Counters and KPIs

Capacity based E- HpaCapaErabCacAtt The cumulated number of capacity based E-RAB CAC
RAB CAC for High attempt for high priority access UE.
Priority Access UE
HpaCapaErabCacSucc The cumulated number of capacity based E-RAB CAC
success for high priority access UE.
HpaCapaErabCacFail The cumulated number of capacity based E-RAB CAC
failure for high priority access UE.
REFERENCE

Confidential
LTE-SW4102, QoS Based Call Admission

Control
INTRODUCTION
The Call Admission Control (CAC) function is enabled to efficiently use the
limited radio resources, to guarantee the quality of user service even in case of
congestion, to protect eNB system from being overloaded. The QoS-based Call
Admission Control feature admits a new GBR bearer only when the eNB can
support the required bit rate.
BENEFIT
• An operator can provide QoS guaranteed service to UEs.
• The operator can configure how much resources (PRB, backhaul bandwidth,
number of GBR bearers) can be used for GBR services.
• The operator can configure the maximum number of GBR bearers per cell.
DEPENDENCY
• Required Network Elements: This feature has effect when MME requests
GBR bearers.
• Prerequisite Features: LTE-SW4101, Capacity based Call Admission Control
LIMITATION
None
SYSTEM IMPACT
capabilities.
Interdependencies between features: QoS-based CAC operates with Capacity
based CAC.
None
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
There are three CAC functionalities: Capacity-based Call Admission Control
(CAC), QoS-based Call Admission Control and Pre-emption.
For other two CAC features, refer to the LTE-SW4101 (Capacity based Call
Admission Control) and the LTE-SW4103 (Pre-emption).
Figure below depicts the overall call admission control procedure.
This feature admits a new GBR bearer only when it is expected to achieve its
guaranteed bit rate requirement under the radio condition of that time. Additional
admission of a new GBR bearer must not degrade the QoS level of existing GBR
bearers. For this, the eNB monitors the PRB usage and backhaul bandwidth
utilization that existing GBR bearers are consuming. The eNB makes an admission
decision based on these resources utilizations of that time and the QoS level
required by the new GBR bearer.
The GBR bearers are not likely to consume all the reserved resource as much as
the guaranteed bit rate required. Therefore, the estimation of expected throughput
of the new GBR bearer QCI is computed based on the actual average throughput
of the existing GBR bearers with the same QCI. This allows the eNB to
accommodate more GBR bearers. Note that GBR bearers with the same QCI are
assumed to use the same service and to consume the similar level of throughput.
This feature applies only to GBR bearers. Non-GBR bearers are always allowed as
long as the total number bearers per UE and per cell do not exceed the maximum
limit, which is not to hinder a UE’s access to the network because it must establish
at least one default non-GBR bearer to attach to the network.

Confidential
As the eNB allows more GBR bearers, less resource can be allocated to non-GBR
bearers. It will degrade quality of user experience of the UEs who have non-GBR
bearers. To sustain a certain level of service quality for non-GBR services,
operator can limit the amount of resources that can be allocated to GBR bearers or
the total number of UEs. For this, operator can configure following system
parameters. The eNB allows GBR bearers within the amount of resources
configured by operator.
• The amount of PRBs that can be allocated to GBR bearers
• The amount of backhaul bandwidth that can be allocated to GBR bearers
• The maximum number of GBR bearers
The basic CAC equation for PRBs that can be allocated to GBR bearers is given as
follows:
CurrentGbrPrbUsage + ExpectedPrbUsage < GBRPrbUsageThresh,
Where ExpectedPrbUsage is calculated based on the previous PRB usage where
bearers with same QCI have been used. If a bearer with the same QCI has never
been used, the expectedPrbUsage is calculated based on the PRB usage of other
QCIs. For GBRPrbUsageThresh, there are separate thresholds for Normal GBR
bearers and Emergency/Handover bearers. Separate thresholds for the maximum
PRB usage can be configured for GBR and for GBR per quality of service index
for both downlink and uplink respectively.
There are two policy options available for the determination of the current used
physical resource. These options are configured via LSM, using
QOS_POLICY_OPTION (CHG-CELL-CAC).
• QoSPolicy_option(0): For a GBR bearer newly requested, the current PRB
usage is calculated based on all QCIs of GBR bearers. Non-GBRs are always
allowed. Option0 would be typically used if no differentiation of the bearer
traffic is required. The impact to lower priority bearer traffic that has already
passed QoS based CAC would be less significant.
• QoSPolicy_option(1): For a GBR bearer newly requested, the current PRB
usage is calculated based on the GBR bearers which have equal or higher
priorities than the newly requested bearer. Non-GBRs are always allowed.
Option1 would be typically used if bearer traffic is required to be
differentiated according to its specific quality of service index. High priority
bearer traffic may impact lower priority QCI bearers by degrading their service
with respect to air interface scheduling.
The ExpectedPrbUsage Estimation option, “AUTO” or “MANUAL” can be
applied per QCI under both QoS policy option configurations. The parameter
‘unitUsageManual’ itself is concerned with the basic CAC equation for the
calculation of the PRB usage given below and is used explicitly to derive the
estimated ‘ExpectedPrbUsage’.
The definition of the ‘unitUsageManual’ is a percentage value configurable to
three decimal places, from 0.000% to 100%. The definition determines the
maximum amount of PRB’s required to process 1Kbps of throughput.
Each term in the above equation is summarized as shown in the following table.

Confidential
QOS_POLICY_OPTION CurrentGbrPrbUsage ExpectedPrbUsage GBRPrbUsageThresh

QoSPolicy_option0 PRB usage of all currently • ESTIMATION_OPT is • Configurable in cell
used GBR bearers (Normal “Auto” → Per QCI level by using CHG-
+ Emergency/handover) estimation QCAC-PARA command
• ESTIMATION_OPT is • Different thresholds for
“Manual” → Using normal or
manually configured emergency/handover
parameter per QCI bearer request
QoSPolicy_option1 PRB usage of the currently • ESTIMATION_OPT is • Configurable per QCI in
used GBR bearers which “Auto” → Per QCI cell level by using CHG-
have equal or higher priority estimation QCACQ-PARA
than the incoming bearer • ESTIMATION_OPT is command
(Normal + “Manual” → Using • Different thresholds for
Emergency/handover) manually configured normal or
parameter per QCI emergency/handover
bearer request
The basic equation for backhaul CAC is given as follows:

CurrentGbrBwUsage + ExpectedBw < OverbookingRatio * bhBwCacThreshold
The basic CAC threshold for backhaul bandwidth, “bhBwCacThresh” shown
above is calculated using the parameter representing the total backhaul capacity
based on the interface bandwidth. The parameter is configurable and given by
“bhLinkCapacity”.
Therefore the actual backhaul threshold can be represented by a percentage of the
total interface bandwidth as shown below.
• For downlink
bhBWCacThreshold = bhBWCacDLThreshold(0%-100%) * bhLinkCapacity
• For uplink
bhBWCacThreshold = bhBWCacULThreshold(0%-100%) * bhLinkCapacity
Where, OverbookingRatio ranges from 1 to 10. Backhaul CAC is applied only for
the GBR bearers, and different bhBwCacThreshold and OverbookingRatio values
can be configured for Normal GBR bearer and Emergency/Handover bearers. The
detailed parameters are found in Section 2.4.2. In the above equation, the
ExpectedBw is calculated based on E-RAB Guaranteed Bit Rate Downlink and E-
RAB Guaranteed Bit Rate Uplink fields in E-RAB Setup Request message. The
operator can choose QCI based backhaul CAC or Service group based backhaul
CAC or both. If QCI based backhaul CAC option is chosen, the backhaul
bandwidth value calculation and configuration of the bandwidth threshold and
overbooking ratio can be done for each QCI bearers. On the other hand, if Service
group based CAC option is chosen, the above equation is calculated for
aggregation of several QCI bearers, which are included in the same service group.
Service group is composed of one or multiple QCIs. Each QCI’s service group can
be defined by setting bhServiceGroup parameter.

Confidential
Operation Details
RRC Connection Setup
The QoS based CAC is not used in RRC connection setup procedures but capacity
based CAC is used.
Figure below depicts the E-RAB based setup subjected to capacity and QoS based
CAC.
5 After the RRC Establishment procedure, the Initial Context Setup Request
message or the E-RAB Setup/Modify Request message is received from the
MME to set up the default radio bearer and the dedicated radio bearer
(hereafter, DRB). Then, the eNB capacity-based CAC and the QoS-based
CAC are performed sequentially to determine whether to admit the call.
6 The eNB capacity-based CAC (SW4101) is initiated per E-RAB.
7 When the E-RAB has the GBR, the QoS-based CAC is initiated.
o If the PRB usage of the cell satisfies ‘CurrentGbrPrbUsage +
ExpectedPrbUsage < GbrPrbUsageThresh’, the call is admitted. If not, the
call is rejected. An estimated PRB usage for the GBR bearer is
accumulated to currentGbrPrbUsage usage if the GBR bearer is requested
and admitted before currentGbrPrbUsage usage is updated.
o If the Backhaul BW satisfies ‘CurrentGbrBwUsage + ExpectedBw <
OverbookingRatio * bhBwCacThreshold’, the call is admitted. If not, the
call is rejected.
o If admission control based on packet delays of existing GBR bearers is
activated and the estimated packet delays of existing GBR bearers are
greater than threshold, the call is reject. If not, the call is admitted.
o If the E-RAB is admitted, the RRC Connection Reconfiguration message
is transmitted to the UE to perform the E-RAB (DRB) Establishment
procedure. If a call is rejected, the CAC function determines whether to
admit E-RAB by interworking with the preemption function per E-RAB
(DRB) to control the flow of each call. (Partial success per E-RAB is not
considered.)
4 and 5) If the E-RAB is successfully admitted, the RRC connection

Confidential
reconfiguration message is transmitted to the UE to initiate an E-RAB (DRB)

establishment. If the call is rejected, whether to admit the E-RAB is determined in
interoperation with the preemption function per E-RAB (DRB) to control the call
flow (a partial success per E-RAB is ignored).
6) The eNB sends the MME E-RAB setup message.
Intra-eNB Handover
Figure below depicts the Intra-eNB Handover subject to Capacity and QoS based
CAC.
1) The eNB receives a measurement report from a UE.

2 and 3) The source eNB determines the handover and capacity based CAC is
performed.
4) When the E-RAB has the GBR, the QoS-based CAC is initiated.
o If the PRB usage of the target cell satisfies ‘CurrentGbrPrbUsage +
ExpectedPrbUsage < GbrPrbUsageThresh’, the call is admitted. If not, the
call is rejected. An estimated PRB usage for the GBR bearer is
accumulated to currentGbrPrbUsage usage if the GBR bearer is requested
and admitted before currentGbrPrbUsage usage is updated.
o If admission constrol based on packet delays of existing GBR bearers is
5) If the call is admitted, the RRC Connection Reconfiguration message is
transmitted to the UE to perform the Intra-eNB Handover procedure. If the call is
rejected, the CAC function controls the flow of each call by interworking with the
preemption function per E-RAB (DRB) determining whether to admit E-RAB.
(Partial success per E-RAB is not considered.)
6) The RRC Connection Reconfiguration Complete message is received from the
UE.
Inter-eNB Handover
Figure below depicts the Inter-eNB Handover subject to Capacity and QoS based
CAC.

Confidential

9 The source eNB determines HO and sends the target eNBs a Handover
Request message.
10 The eNB performs capacity-based CAC (LTE-SW4101).
11 If the capacity-based CAC is passed, when the E-RAB has the GBR, the
QoS-based CAC is initiated.
o If not, the call is rejected. If the PRB usage of the target cell satisfies
‘CurrentGbrPrbUsage + ExpectedPrbUsage < GbrPrbUsageThresh’, the
call is admitted. If not, the call is rejected. An estimated PRB usage for the
GBR bearer is accumulated to currentGbrPrbUsage usage if the GBR
bearer is requested and admitted before currentGbrPrbUsage usage is
updated.
o If the backhaul BW satisfies ‘CurrentGbrBwUsage + ExpectedBw
<OverbookingRatio * bhBwCacThreshold, the call is admitted.
o If admission constrol based on packet delays of existing GBR bearers is
12 If the call is admitted, the Handover Request Acknowledge message is
transmitted to the source eNB to initiate the inter-eNB handover.
13 The source eNB transmits the RRC connection reconfiguration message to
the UE and performs SN Status Transfer.
8 to 10) After path switch procedure, the target eNB sends Release Request the
source eNB
Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CELL-CAC and set QOS_CAC_OPTION to QoSCAC_option1
(use).
• Run CHG-CELL-CAC and set QOS_CAC_OPTION to QoSCAC_option0
(no_use).
Key Parameters
parameter.
QOS_CAC_OPTION The policy of the QoS (Quality of Service) based CAC (call admission control)
at the cell level.
• QoSCAC_option0: The QoS based CAC function at the cell level is not
used.
• QoSCAC_option1: The QoS-based CAC function per cell is used.
parameters.
PARAMETER DESCRIPTIONS OF CHG-ENB-CAC/RTRV-ENB-CAC/CHG-
CELL-CAC/RTRV-CELL-CAC
cells supported by the system. It is determined by Carrier/Sector. For
example, if the maximum capacity system is 1 Carrier/3 Sector, up to 3
cells are supported.

Confidential
QOS_CAC_OPTION The policy of the QoS (Quality of Service) based CAC (call admission
control) at the cell level.
• QoSCAC_option0: The QoS based CAC function at the cell level is not
used.
• QoSCAC_option1: The QoS-based CAC function per cell is used.
QOS_POLICY_OPTION The policy used when executing the Quality of Service (QoS)-based Call
Admission Control (CAC) function per cell.
• QoSPolicy_option0: For a GBR bearer newly requested, the PRB usage
is calculated based on the resource type (GBR or non-GBR) of the QCI.
Then CAC is executed based on the calculated PRB usage. Non-GBRs
are always allowed.
• QoSPolicy_option1: For a GBR bearer newly requested, the PRB usage
is calculated based on the priority of the QCI. Then CAC is executed
based on the calculated PRB usage. Non-GBRs are always allowed.
PRB_REPORT_PERIOD PRB (Physical Resource Block) report period for QoS CAC at the cell
level.
ESTIMATION_OPT The policy of the Expected PRB usage calculation. (0: auto, 1:manual)
• EstimationOption_auto(0): The PRB Usage is automatically calculated.
• EstimationOption_manual(1): The PRB Usage is manually calculated.
PREEMPTION_FLAG Whether to use preemption at the cell level.
• ci_no_use: The Preemption function per cell is disabled.
• ci_use: The Preemption function per cell is enabled.
BH_BW_CAC_USAGE Whether to use backhaul bandwidth based CAC at the cell level.
• ci_no_use: Backhaul Bandwidth-based CAC function per cell is not
used.
• ci_use: Backhaul Bandwidth-based CAC function per cell is used.
BH_BW_CAC_OPTION The policy used when executing the Backhaul-based Call Admission
Control (CAC) function per cell.
• bhBwCac_Qci_only: QoS-based CAC.
• bhBwCac_ServiceGroup_only: Service group-based CAC.
• bhBwCac_Both_Qci_ServiceGroup: QoS amp; Service group-based
CAC.
DELAY_QOS_CAC_USAGE Whether to use or not delay based CAC. It is running when the number of
GBR is the same or larger than delayQosCacBearerCountThresh.
DELAY_QOS_CAC_BEARER_C Delay based CAC is running when the number of GBR is the same or
OUNT_THRESH larger than delayQosCacBearerCountThresh.
QCI12_SUM_CAC_USAGE To support sum of QCI1 + QCI2 bearer based CAC. max 5 points can be
configured.
POINT0_USAGE Usage of point0 at sum of QCI1+QCI2 bearer based CAC
QCI1_POINT0 Number of max qci1 at point0

Confidential
UL_LCG1_THRESH Delay based CAC threshold for UL LCG1.
UL_LCG2_THRESH Delay based CAC threshold for UL LCG2.
Parameter Descriptions of CHG-QCAC-PARA/RTRV-QCAC-PARA

example, if the maximum capacity system is 1 Carrier/3 Sector, up to 3
cells are supported.
QCI This parameter is the QoS Class Identifier (QCI). The range is 0 - 255.The
standard QCI defined in the standard document is 1 - 9. 0 and 10 - 255
characteristics.
DL_QCI_USAGE_THRESH_NOR This parameter is the percentage (%) of PRB that can be allocated per
MAL QoS Class Identifier(QCI) as downlink for normal calls. If the downlink
GBR PRB usage amount exceeds the entered parameter value when a
new call is requested, the QoS CAC Fail is generated.
DL_QCI_USAGE_THRESH_HO This parameter is the percentage (%) of PRB that can be allocated per
QoS Class Identifier (QCI) as downlink for emergency calls or handover
calls. If the downlink GBR PRB usage amount exceeds the entered
parameter value when an emergency call or handover call is requested,
the QoS CAC Fail is generated.
DL_QCI_USAGE_THRESH_HIG This parameter is the percentage (%) of PRB that can be allocated per
H_PRIORITY_ACCESS QoS Class Identifier (QCI) as downlink for high priority access calls. If the
downlink GBR PRB usage amount exceeds the entered parameter value
when a new call is requested, the QoS CAC Fail is generated.
If this parameter is the too high, the system load after CAC is probably too
high, which results in system congestion.
This threshold is vaild only if HIGH_PRIORITY_ACCESS_TYPE is
configured as independentOperationType (Related CLI : RTRV-ENB-
CAC).
UL_QCI_USAGE_THRESH_NOR This parameter is the percentage (%) of PRB that can be allocated per
MAL QoS Class Identifier(QCI) as uplink for normal calls. If the uplink GBR
PRB usage amount exceeds the entered parameter value when a new call
is requested, the QoS CAC Fail is generated.
UL_QCI_USAGE_THRESH_HO This parameter is the percentage (%) of PRB that can be allocated per
QoS Class Identifier(QCI) as uplink for emergency calls or handover calls.
If the uplink GBR PRB usage amount exceeds the entered parameter
value when an emergency call or handover call is requested, the QoS
CAC Fail is generated.
UL_QCI_USAGE_THRESH_HIG This parameter is the percentage (%) of PRB that can be allocated per
H_PRIORITY_ACCESS QoS Class Identifier(QCI) as uplink for high priority access calls. If the
uplink GBR PRB usage amount exceeds the entered parameter value
when a new call is requested, the QoS CAC Fail is generated.

Confidential
CAC).
UNIT_USAGE_MANUAL This parameter is the PRB usage percentage for manual assignment. It is
used if the estimationOption in the RTRV-CELL-CAC is Manual(1) and
valid up to three digits below the decimal point.
Parameter Descriptions of CHG-BHBW-QCI/RTRV-BHBW-QCI

QCI This parameter is the QoS Class Identifier(QCI). The range is 0 - 255.The
standard QCI defined in the standard document is 1 - 9. 0 and 10 - 255
characteristics.
BH_BW_CAC_DL_THRESH_FO This parameter is the downlink threshold value per QCI. It is used when
R_NORMAL Backhaul CAC is executed during normal handover.
If the downlink usage exceeds the threshold during normal call request,
the call request will not be accepted.(Backhaul Bandwidth CAC Failure)
R_EMER_HO Backhaul CAC is executed during emergency and handover.
If the downlink usage exceeds the threshold during emergency and
handover request, the call request will not be accepted.(Backhaul
Bandwidth CAC Failure)
BH_BW_CAC_UL_THRESH_FO This parameter is the uplink threshold value per QCI. It is used when
R_NORMAL Backhaul CAC is executed during normal call (e.g. Attach and Idle to
Active).
If the uplink usage exceeds the threshold during normal call request, the
call request will not be accepted.(Backhaul Bandwidth CAC Failure)
If the uplink usage exceeds the threshold during emergency and handover
request, the call request will not be accepted.(Backhaul Bandwidth CAC
Failure)
OVER_BOOKING_RATIO This parameter is the overbooking ratio against the downlink and uplink
thresholds when the backhaul based CAC is performed per QoS Class
Identifier(QCI). It is set when the backhaul capacity needs to be allowed
arbitrarily and as much capacity as the result of the multiplication by this
ratio is additionally allowed when calculating the thresholds.
R_HIGH_PRIORITY_ACCESS Backhaul CAC is executed for high priority access call.
If the downlink usage exceeds the high priority access call threshold, the
call request will not be accepted. (Backhaul Bandwidth CAC Failure)
CAC).
R_HIGH_PRIORITY_ACCESS Backhaul CAC is executed for High priority access call.
If the uplink usage exceeds the high priority access call threshold, the call
request will not be accepted. (Backhaul Bandwidth CAC Failure)
CAC).
Parameter Descriptions of CHG-BHBW-SVCGR/RTRV-BHBW-SVCGR

Confidential
SERVICE_GROUP This parameter is the service group.
• VoIP: Service Group that uses the Voice over Internet Protocol (VoIP)
service.
• Video: Service Group that uses the video service.
BH_BW_CAC_DL_THRESH_FO This parameter is the downlink threshold value (ratio) per service group for
R_NORMAL normal call.
The downlink threshold value per service group is used when Backhaul
CAC is executed when normal call is requested.
If the downlink usage exceeds the threshold during normal call request,
the call request will not be accepted(Backhaul Bandwidth CAC Failure).
If the downlink usage exceeds the threshold during emergency and
handover request, the call request will not be accepted.(Backhaul
Bandwidth CAC Failure)
BH_BW_CAC_DL_THRESH_FO This parameter is the downlink threshold value(ratio) per service group
R_HIGH_PRIORITY_ACCESS for high priority access call.
The downlink threshold value per service group is used when Backhaul
CAC is executed when high priority access call is requested.
If the downlink usage exceeds the threshold during high priority access
call request, the call request will not be accepted(Backhaul Bandwidth
CAC Failure).
configured as independentOperationType (Related CLI: RTRV-ENB-CAC).
BH_BW_CAC_UL_THRESH_FO This parameter is the uplink threshold value (ratio) per service group for
R_NORMAL normal call.
The uplink threshold value per service group is used when Backhaul CAC
is executed when normal call is requested (for example, Attach and Idle to
Active).
If the uplink usage exceeds the threshold during normal call request, the
call request will not be accepted.(Backhaul Bandwidth CAC Failure)
BH_BW_CAC_UL_THRESH_FO This parameter is the uplink threshold value(ratio) per service group for
R_EMER_HO emergency or handover calls.
is executed when emergency or handover call is requested
If the uplink usage exceeds the threshold during emergency and handover
Failure)
BH_BW_CAC_UL_THRESH_FO This parameter is the uplink threshold value(ratio) per service group for
R_HIGH_PRIORITY_ACCESS high priority access call.
is executed when high priority access call is requested.
If the uplink usage exceeds the threshold during high priority access call
Failure)
CAC).
OVER_BOOKING_RATIO This parameter is the overbooking ratio against the downlink and uplink
thresholds when the backhaul based CAC is performed per QoS Class
Identifier(QCI). It is set when the backhaul capacity needs to be allowed
arbitrarily and as much capacity as the result of the multiplication by this
ratio is additionally allowed when calculating the thresholds.

Confidential
DL_PDCP_SDU_DELAY_THRES For delay based CAC, DL pdcp sdu delay threshold is configured using
H this parameter. It is noted that it is applied to QCI = 1 only.
Counters and KPIs

Transport E-RAB HpaTransportErabCacAtt The cumulated number of Transport E-RAB CAC
CAC for High Priority attempt for high priority access UE or UE belongs to the
Access UE highest ARP group.
HpaTransportErabCacSucc The cumulated number of Transport E-RAB CAC
success for high priority access UE or UE belongs to the
highest ARP group.
HpaTransportErabCacFail The cumulated number of Transport E-RAB CAC failure
for high priority access UE or UE belongs to the highest
ARP group.
REFERENCE
[2] 3GPP TS23.203, Technical Specification Group Services and System Aspects;
Policy and charging control architecture

Confidential
LTE-SW4103, Preemption
INTRODUCTION
When there are no resources available, an eNB can admit a new bearer by pre-
empting existing bearers. This feature can be used to give admission to priority
users even in congestion.
The decision is based on Allocation and Retention Priority (ARP) information of
new bearers and existing bearers. ARP consists of priority level, pre-emption
capability, and pre-emption vulnerability, which are delivered from MME to eNB
during E-RAB establishment. When there are multiple pre-emptive candidate
bearers, the eNB selects a candidate bearer randomly. The MME configures
appropriate ARP per each bearer.
BENEFIT
An operator can provide a differentiated service that allows a high-priority UE to
access the network even in congestion.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Table below outlines a functional architecture for call admission control. Capacity
based CAC has impact on the RRC connection establishment and E-RAB bearer
establishment while QoS based CAC and Pre-emption has impact on E-RAB
bearer establishment only. This section covers pre-emption. In case of other two
CAC features, refer to LTE-SW4101 and LTE-SW4102.

Confidential
The Preemption function is applied to GBR and non-GBR bearers in case of no

resources available. Related resources are the number of bearers defined per cell.
If operator provides QoS service and has limited resources that can be allocated to
GBR bearers, the lack of GBR bearers, PRBs and backhaul bandwidth can trigger
pre-emption function. In this case, an existing GBR bearer is pre-empted. The eNB
follows the pre-emption rules defined in 3GPP TS36.413. If there are multiple pre-
emption candidates that have the same ARP, the eNB will select a candidate bearer
at random.
Parameter Presence Range IE Type and Semantics Description
reference
Priority Level M - INTEGER (0 The priority of allocation and retention.
to 15) Value 15 means "no priority". Values between 1
and 14 are ordered in decreasing order of
priority, that is, 1 is the highest and 14 the
lowest. Value 0 is treated as a logical error if
received.
Pre-emption M - ENUMERAT This indicates pre-emption capability of the
Capability ED (does not request on other E-RABs.
trigger pre- The E-RAB does not pre-empt other E-RABs or,
emption, it may pre-empt other E-RABs. The Pre-emption
may trigger Capability indicator applies to the allocation of
pre-emption) resources for E-RAB and as such it provides the
trigger to the pre-emption procedures/processes
of the eNB.
Pre-emption M - ENUMERAT This IE indicates the vulnerability of the E-RAB
Vulnerability ED (not pre- to pre-emption of other E-RABs.
emptable,

Confidential
Parameter Presence Range IE Type and Semantics Description

reference
pre- The E-RAB does not preempt by other E-RABs
emptable) or it may be pre-empted by other RABs. Pre-
emption Vulnerability indicator applies for the
entire duration of the E-RAB, unless modified
and as such indicates whether the E-RAB is a
target of the pre-emption procedures/processes
of the eNB.
Handover of Preempted UE
The preempted UE can be handed over to a neighbor cell. The eNB sends MR
Solicitation to the pre-empted UE and it performs handover procedures based on
the measurement result from the UE. If multiple carriers are available, they are all
configured for the measurement. Operator can configure handover thresholds
appropriately for the pre-emption case. Operator can enable or disable the
handover of pre-empted UE. According to the eNB and the UE situation, call
procedure executed can be divided as follows:
• Inter-frequency handover: The UE to be pre-empted supports multiple E-
UTRA carriers, and inter-frequency handover is available according to the
CAC pre-emption handover function.
• Intra-frequency handover: The UE to be pre-empted does not support multiple
E-UTRA carriers, and intra-frequency handover is available according to the
• Inter-frequency redirection: The UE to be pre-empted supports multiple E-
UTRA carriers, and inter-frequency handover is not available according to the
• RRC connection release: The UE to be pre-empted does not support multiple
E-UTRA carriers; or it supports multiple E-UTRA carriers, but inter-frequency
handover and inter-frequency redirection are not available according to the
Figure below depicts an operational flow before the CAC pre-emption handover
function executes.

Confidential
1 Upon receiving a new call/bearer setup or handover request, the eNB

performs CAC function.
2 After CAC function is performed in step 1, if the new call/bearer setup or
handover request can be accepted without pre-emption, the request is
accepted and the next procedure is performed.
3 After CAC function is performed in step 1, if pre-emption is needed, pre-
emption function is performed to decide whether pre-emption of the existing
call is available.
4 If pre-emption of the existing call is available in step 3, the new call/bearer
setup or handover request is accepted, and the next procedure is performed.
5 CAC pre-emption handover function is performed for the pre-empted call
selected in step 3. CAC pre-emption handover is operated only when the
entire call is pre-empted.
When only some bearers of a call are pre-empted, CAC pre-emption handover
is not operated for the call.
6 If pre-emption of the existing call is unavailable in step 3, the new call/bearer

Confidential
setup or handover request is rejected, and the next procedure is performed.

The CAC pre-emption handover function can be described as follows:
1 The eNB operates CAC pre-emption handover function according to the

result of the CAC/pre-emption performance. (Continued from the [A] of the
operation flow before the CAC pre-emption handover function executes.)
2 The eNB judges whether there is enough resource available for the CAC pre-
emption handover process.
o If the CAC pre-emption handover process is available in step 1, step 2 is
performed.
o If the CAC pre-emption handover process is not available in step 1, step 7
is performed.
3 The eNB decides the target carrier, which is handed over the pre-empted call.
o If the UE does support multiple E-UTRA carriers, one of the carriers that
is not a serving carrier is selected.
o If the UE does not support multiple E-UTRA carriers, the serving carrier is
selected.

Confidential
4 The eNB solicits the UE for Measurement Report for the target carrier
selected in step 2. At this moment, it starts a wait timer to determine whether
the measurement solicitation fails.
5 When the Measurement Report message is received from the UE while the
wait timer of step 3 is in operation, the eNB checks if there exists neighbor
cells whose UE measurement results are above the configured threshold.
6 If neighbor cells exist whose UE measurement results are above the
configured threshold in step 4, the best cell is selected among cells and
handover preparation procedure starts.
7 If the handover preparation succeeds in step 5, the UE to be pre-empted is
directed to perform handover.
8 If one of the events below occurs during steps 4 through 6, CAC pre-emption
handover is unavailable. Thus, it is judged whether inter-frequency
redirection is available.
o The wait timer of step 3 expires while the Measurement Report message is
not received from the UE yet.
o In step 4, there is no neighbor cell whose UE measurement result is above
the configured threshold.
o In step 5, the handover preparation fails.
9 In step 7, if the UE does support multiple E-UTRA carriers, one of the
carriers that is not a serving carrier is selected and inter-frequency redirection
is performed.
10 In step 7, if the UE does not support multiple E-UTRA carriers, inter-
frequency redirection is unavailable. Thus, the RRC connection release
procedure is performed.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CELL-CAC or RTRV-CELL-CAC to enable the pre-emption
function by setting PREEMPTION_FLAG to USE.

Confidential
• Run CHG-CELL-CAC or RTRV-CELL-CAC to disable the pre-emption

function by setting PREEMPTION_FLAG to NOT_USE.
When this function is disabled, the eNB ignores the ARP information received
from MME and it does not admit a new bearer when the configured maximum
number of bearers is all used.
Key Parameters
feature.
parameters.
Parameter description of CHG-CELL-CAC/RTRV-CELL-CAC
Parameters Description
supported by the system. It is determined by carrier/sector. For example, if
the maximum capacity system is 1 Carrier/3 Sector, up to three cells are
supported.
PREEMPTION_FLAG This parameter decides whether the cell enables or disables the use pre-
emption functionality.
Counters and KPIs

with this feature.
REFERENCE
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application
Protocol (S1AP), Section 9.2.1.60

Confidential
LTE-SW4104, Cell Barring

INTRODUCTION
Cell barring is used to prohibit commercial UEs from accessing the network
during eNB commissioning or performance testing, but test UEs are allowed to
camp on the cell. Operator can configure related system parameters through LSM.
Then, the eNB broadcasts these parameters in System Information Block Type 1
message.
BENEFIT
An operator can prohibit UEs from camping on a specific cell, which enables
operator to test the cell for the commissioning of base stations without any
interference of commercial UEs.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Cell Reservations and Access Restrictions

There are two mechanisms, which allows operator to impose cell reservations or
access restrictions. The first mechanism uses indication of cell status and special
reservations for control of cell selection and reselection procedures. The second
mechanism, referred to as Access Control, allows preventing selected classes of
users from sending initial access messages for load control reasons. At
subscription, one or more Access Classes (ACs) are allocated to the subscriber and
stored in the USIM.
Cell status and cell reservations are indicated in the SIB1 message by means of
two fields:
• cellBarred (IE type: barred or not barred): In case of multiple PLMNs
indicated in SIB1, this field is common for all PLMNs
• cellReservedForOperatorUse (IE type: reserved or not reserved): In case of
multiple PLMNs indicated in SIB1, this field is specified per PLMN.

Confidential
cellAccessRelatedInfo SEQUENCE {
plmn-IdentityList PLMN-IdentityList,
cellBarred ENUMERATED {barred, notBarred},
},
PLMN-IdentityList ::= SEQUENCE (SIZE (1..maxPLMN-r11)) OF PLMN-

IdentityInfo
PLMN-IdentityInfo ::= SEQUENCE {
plmn-Identity PLMN-Identity,
cellReservedForOperatorUse ENUMERATED {reserved, notReserved}
When cell status is indicated as 'not barred' and 'not reserved' for operator use, all
UEs treat this cell as a candidate cell during the cell selection and reselection
procedures.
When cell status is indicated as 'not barred' and 'reserved' for operator use for any
PLMN:
• UEs assigned to AC 11 or 15 operating in their HPLMN/EHPLMN treat this
cell as a candidate cell during the cell selection and reselection procedures if
the field cellReservedForOperatorUse for that PLMN set to reserved.
• UEs assigned to an AC in the range of 0 to 9, 12 to 14 behave as if the cell
status is 'barred' in case the cell is reserved for operator use for the registered
PLMN or the selected PLMN.
ACs 11, 15 are only valid for use in the HPLMN/EHPLMN. ACs 12, 13, 14 are
only valid for use in the home country.
When cell status barred is indicated or to be treated as if the cell status is barred:
• The UE is not permitted to select/reselect this cell, not even for emergency
calls.
• The UE selects another cell.
Refer to 3GPP TS36.304 section 5.3 for more detail information on the cell
selection and reselection of UEs.
Indication of Cell Status

For cell barring, the operator can change the following system parameters in LSM:

Confidential
• CELL_BARRED (CHG-CELL-ACS) is used for configuring cellBarred (IE

type: ‘barred’ or ‘not barred’). When a cell serves multiple PLMNs, the cell
barring parameter has effect on all the PLMNs.
• CELL_RESERVED_FOR_OP_USE (CHG-CELL-ACS) is used for
configuring cellReservedForOperatorUse (IE type: ‘reserved’ or ‘not
reserved’). When the cell serves multiple PLMNs, this parameter has effect
only on the PLMN indicated by PLMN-Identity.
SYSTEM OPERATION
How to Activate
Preconditions
• The cell is established.
• Run CHG-CELL-ACS and set CELL_BARRED to 0.
• Run CHG-CELL-ACS and set CELL_BARRED to 1.
Key Parameters
feature.
parameter.
CELL_BARRED This parameter indicates whether the cell is barred or not.
• barred: A cell is barred.
• notBarred: A cell is not barred.
Both when the cell status becomes Shutdown and when the operator sets this
parameter to barred, the cellBarred value of SIB1 becomes barred and then is
broadcasted.

Confidential
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TS36.304: Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) procedures in idle mode, Section 5.3

Confidential
LTE-SW4105, Access Class Barring

INTRODUCTION
Access Class Barring (AC-barring) is used to reduce the amount of call request
from UEs. An operator can manually configure the access class barring
information via LSM.
Samsung eNB uses AC-barring function for eNB overload control. When the CPU
is overloaded, the eNB automatically adjusts the ac-barring parameters and
broadcasts in SIB type 2 message. For more detail information, see LTE-SW2102,
eNB Overload Control feature.
Cell barring is also related to access control of UEs. For more detail, see LTE-
SW4104, Cell Barring feature.
BENEFIT
The operator can reduce the amount of incoming calls per call type.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
If ACB is broadcasted, the UE can be limited to access network.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
As shown in the table below, the operator can set the access level for Emergency
Call, Signaling Call and Data Call of each CPU load level. The access level for

Confidential
Emergency Call is decided via ac-BarringForEmergency by selecting “Barred” or

“Not_Barred”. BarringFactor and ac-BarringTime are setup via ac-BarringForMO-
Signaling and ac-BarringForMO-Data respectively. The ac-BarringFactor decides
the statistical percentage of UEs to be accepted, and the ac-BarringTime
determines the seconds after which UE can attempt to call. For example, if the ac-
BarringFactor is set to 90 %, ninety out of 100 UEs in the coverage are allowed to
attempt to call immediately and the rest 10 % attempt to call after 16 s.
Table below gives an example of AC barring parameter setting for each overload
level.
AC Barring Parameters (SIB Type2) CPU Load Level
Critical Major Minor Normal
ac-BarringForEmergency Barred Not Barred Not Barred Not Barred
ac-BarringForMO- ac-BarringFactor 0% 90 % 95 % -
Signalling
ac-BarringTime 128s 32s 16s -
Data
ac-BarringTime 128s 32s 16s -
The UE generates a random number between 0 and 1 at the time point of a call
attempt. If the number is smaller than the ac-BarringFactor, it attempts the call
immediately; if the number is bigger than the ac-BarringFactor, it waits as long as
ac-BarringTime and then attempts the call.
The ac-BarringForMO-Signaling is applicable for Attach, Tracking Area Update
and Detach messages, and the acBarringForMO-Data is a parameter applied to
Service Request or Extended Service Request message.
Also, access class barring is supported per PLMN. The detailed parameters are
shown as follows.

ac-BarringInfo SEQUENCE {
ac-BarringForEmergency BOOLEAN,
ac-BarringForMO-Signalling AC-BarringConfig OPTIONAL, -- Need OP
ac-BarringForMO-Data AC-BarringConfig OPTIONAL -- Need OP
} OPTIONAL, -- Need OP
...,
[[ ssac-BarringForMMTEL-Voice-r9 AC-BarringConfig OPTIONAL, -- Need OP
ssac-BarringForMMTEL-Video-r9 AC-BarringConfig OPTIONAL -- Need OP
]],
[[ ac-BarringForCSFB-r10 AC-BarringConfig OPTIONAL -- Need OP
]],
[[
ac-BarringSkipForMMTELVoice-r12 ENUMERATED {true} OPTIONAL, -- Need OP
ac-BarringSkipForMMTELVideo-r12 ENUMERATED {true} OPTIONAL, -- Need OP
ac-BarringSkipForSMS-r12 ENUMERATED {true} OPTIONAL, -- Need OP
ac-BarringPerPLMN-List-r12 AC-BarringPerPLMN-List-r12 OPTIONAL -- Need OP
]]
}
AC-BarringPerPLMN-List-r12 ::= SEQUENCE (SIZE (1.. maxPLMN-r11)) OF AC-BarringPerPLMN-

r12
AC-BarringPerPLMN-r12 ::= SEQUENCE {

plmn-IdentityIndex-r12 INTEGER (1..maxPLMN-r11),
ac-BarringInfo-r12 SEQUENCE {
ac-BarringForEmergency-r12 BOOLEAN,

Confidential
ac-BarringForMO-Signalling-r12 AC-BarringConfig OPTIONAL, -- Need OP

ac-BarringForMO-Data-r12 AC-BarringConfig OPTIONAL -- Need OP
ac-BarringSkipForMMTELVoice-r12 ENUMERATED {true} OPTIONAL, -- Need OP
ac-BarringSkipForMMTELVideo-r12 ENUMERATED {true} OPTIONAL, -- Need OP
ac-BarringSkipForSMS-r12 ENUMERATED {true} OPTIONAL, -- Need OP
ac-BarringForCSFB-r12 AC-BarringConfig OPTIONAL, -- Need OP
ssac-BarringForMMTEL-Voice-r12 AC-BarringConfig OPTIONAL, -- Need OP

ssac-BarringForMMTEL-Video-r12 AC-BarringConfig OPTIONAL -- Need OP
}
AC-BarringConfig ::= SEQUENCE {

ac-BarringFactor ENUMERATED {
p00, p05, p10, p15, p20, p25, p30, p40,
p50, p60, p70, p75, p80, p85, p90, p95},
ac-BarringTime ENUMERATED {s4, s8, s16, s32, s64, s128, s256, s512},
ac-BarringForSpecialAC BIT STRING (SIZE(5))
SYSTEM OPERATION
How to Activate
Preconditions
• The cell is established.
• Run CHG-CELL-ACS and set BARRING_CTR_USAGE to manualCtrl or
cpuStatusCtrl.
To activate PLMN-specific access barring, do the following
• Run CHG-CELL-ACS and set BARRING_PLMN_CTR_USAGE to
manualCtrl or cpuStatusCtrl.
• Run CHG-CELL-ACS and set BARRING_CTR_USAGE to barringOff.
To deactivate PLMN-specific access barring, do the following:
barringOff.

Confidential
Key Parameters
parameters.
CELL_NUM This parameter is the cell number to identify each cell. This value must
not exceed the maximum number of cells supported by the system.
BARRING_CTR_USAGE This parameter represents the how to set the ac-barringInfo
parameters of SIB2.
• barringOff: Does not use the barring control parameters.
• manualCtrl: Uses the barring control function manually.
• cpuStatusCtrl: Uses the barring control function depending on CPU
overload.
BARRING_PLMN_CTR_USAGE This parameter represents how to set the AC-BarringPerPLMN-List-
r12 parameters of SIB2.
overload.
Parameter Descriptions of CHG-BARCOM-PARA/RTRV-BARCOM-PARA

CELL_NUM This parameter is the cell number to identify each cell. This value must
not exceed the maximum number of cells supported by the system.
BARRING_SIGNAL_USAGE This parameter indicates to enable/disable ac-BarringforMO-Signaling
of a cell in the eNB.
• no_use: ac-BarringforMO-Signaling is not used. A UE can access a
cell during attachment.
• use: ac-BarringforMO-Signaling is used. A UE controls access to a
cell depending on access barring data parameter during attachment.
BARRING_DATA_USAGE This parameter indicates to enable/disable ac-BarringforMO-Data of a
cell in the eNB.
• no_use: ac-BarringforMO-Data is not used. A UE can access a cell
upon service request.
• use: ac-BarringforMO-Data is used. A UE controls access to a cell
depending on access barring data parameter upon service request.
ACCESS_BARRING_EMERGENCY This parameter indicates whether emergency call barring of a cell is
_CALL enabled/disabled.
• False: Emergency Call Barring is not used.
• True: Emergency Call Barring is used.
BARRING_MMTEL_VOICE_USAGE This parameter indicates to enable/disable ssac-BarringForMMTEL-
Voice of a cell in the eNB.
• no_use: ssac-BarringForMMTEL-Voice is not used. A UE can
access a cell upon service request.
• use: ssac-BarringForMMTEL-Voice is used. A UE controls access to

Confidential
a cell depending on access barring data parameter upon service
request.
BARRING_MMTEL_VIDEO_USAGE This parameter indicates to enable/disable ac-ssac-BarringForMMTEL-
Video of a cell in the eNB.
• no_use: ssac-BarringForMMTEL-Video is not used. A UE can
• use: ssac-BarringForMMTEL-Video is used. A UE controls access to
request.
BARRING_CSFB_USAGE This parameter indicates to enable/disable ac-ssac-BarringForCSFB of
a cell in the eNB.
• no_use: ssac-BarringForCSFB of the cell is not used. The UE can
access the cell at service request.
• use: ssac-BarringForCSFB of the cell is used. The UE controls cell
access according to the access barring data parameter value at
service request.
AC_BARRING_SKIP_FOR_MMTEL This parameter indicates to enable/disable skipping of Access Class
_VOICE Barring (Mo-Sig, Mo-Data) procedure when MMTEL Voice is used.
• False (0): do not skip Access Class Barring (Mo-Sig, Mo-Data)
procedure.
• True (1): skip Access Class Barring (Mo-Sig, Mo-Data) procedure.
_VIDEO Barring (Mo-Sig, Mo-Data) procedure when MMTEL Video is used.
procedure.
_SMS Barring (Mo-Sig, Mo-Data) procedure when SMS is used.
procedure.
Parameter Descriptions of CHG-BARPLMN-PARA/RTRV-BARPLMN-PARA

barringStatusType This parameter is the barring status to be changed or retrieved.
• cpuCritical: The CPU of the main card is in Critical state.
plmnBarParamUsage This parameter indicates whether PLMN specific ACB parameters and
ACB skip indicators are used or not.
• CI_no_use: barring parameters for the corresponding PLMN index
and barringStatusType is not used.
• CI_Use: barring parameters for the corresponding PLMN index and
barringStatusType can be used.
barringSignalUsage This parameter indicates to enable/disable ac-BarringforMO-Signaling

Confidential
barringDataUsage This parameter indicates to enable/disable ac-BarringforMO-Data of a
cell in the eNB.
accessBarringEmergencyCall This parameter indicates whether emergency call barring of a cell is
enabled/disabled.
barringMMTELvoiceUsage This parameter indicates to enable/disable ssac-BarringForMMTEL-
request.
barringMMTELvideoUsage This parameter indicates to enable/disable ac-ssac-BarringForMMTEL-
request.
barringCSFBUsage This parameter indicates to enable/disable ac-ssac-BarringForCSFB of
a cell in the eNB.
service request.
acBarringSkipForMMTELvoice This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when MMTEL Voice is used.
• False: do not skip Access Class Barring (Mo-Sig, Mo-Data)
procedure.
• True: skip Access Class Barring (Mo-Sig, Mo-Data) procedure.
acBarringSkipForMMTELvideo This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when MMTEL Video is used.
procedure.
acBarringSkipForSMS This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when SMS is used.
procedure.
parameters.
Confidential

BARRING_STATUS_TYPE This parameter is the barring status to be changed or retrieved.
• barManual: Manual Mode
BARRING_SIGNAL_USAGE This parameter indicates to enable/disable ac-BarringforMO-Signaling
of a cell in a base station.
ACC_PROB_FAC_SIGNAL This parameter is the access probability factor for signaling of the cell
in the eNB.
The UE generates a random value (rand) between 0 and 1. If rand less
than 0, accessProbabilityFactor, the UE can access the cell; otherwise,
access is not possible.
ACC_CLASS_BAR_TIME_SIGNAL This parameter is the access barring time for signaling of the cell in the
eNB.
The UE generates a random value (rand) between 0 and 1. If rand
value less than accessProbabilityFactor, the UE determines that the
cell is barred, and does not establish RRC connection until T305 timer
terminates. The expression used to calculate T305 timer value is (0.7 +
0.6 * rand) * acBarringTime.
BAR_AC11_SIGNAL This parameter indicates to enable/disable Access barring for Signal
for AC 11 (Home PLMN only if the EHPLMN list is not present or any
EHPLMN) of a cell in a base station.
• False: Barring is not used.
• True: Barring is used.
BAR_AC12_SIGNAL This parameter indicates to enable/disable Access barring for Signal
for AC 12 (Home PLMN and visited PLMNs of home country only. For
this purpose the home country is defined as the country of the MCC
part of the IMSI) of a cell in a base station.
BAR_AC13_SIGNAL This parameter indicates to enable/disable access barring for signal for
AC 13 (Home PLMN and visited PLMNs of home country only. For this
purpose the home country is defined as the country of the MCC part of
the IMSI) of a cell in a base station.
AC15 of a cell in a base station.

Confidential
BARRING_DATA_USAGE This parameter indicates to enable/disable ac-BarringforMO-Data of a
cell in a base station.
ACC_PROB_FAC_DATA This parameter is the access probability factor for data of the cell in the
eNB.
ACC_CLASS_BAR_TIME_DATA This parameter is the access barring time for data of the cell in the
eNB.
BAR_AC11_DATA This parameter indicates to enable/disable access barring for data for
AC 11 of a cell in the eNB.
UE can be
AC 12 of a cell in a base station.
UE can be
UE can be
AC15 of a cell in a base station.
ACCESS_BARRING_EMERGENCY This parameter indicates whether emergency call barring of a cell is
_CALL enabled/disabled.
• False: Emergency call barring is not used.
• True: Emergency call barring is used.
BARRING_MMTEL_VOICE_USAGE This parameter indicates to enable/disable ssac-BarringForMMTEL-
Voice of a cell in a base station.

Confidential
request.
ACC_PROB_FAC_MMTEL_VOICE This parameter is the access probability factor for MMTEL-Voice of the
cell in the eNB.
ACC_CLASS_BAR_TIME_MMTEL_ This parameter is the access barring time for MMTEL-Voice of the cell
VOICE in the eNB.
cell is barred, and does not establish RRC connection until T303 or
T305 timer terminates. The expression used to calculate T303 or T305
timer value is (0.7 + 0.6 * rand) * acBarringTime.
BAR_AC11_MMTEL_VOICE This parameter indicates to enable/disable Access barring for MMTEL
Voice for AC 11 (Home PLMN only if the EHPLMN list is not present or
any EHPLMN) of a cell in a base station.
BAR_AC12_MMTEL_VOICE This parameter indicates to enable/disable access barring for MMTEL
Voice for AC 12 (Home PLMN and visited PLMNs of home country
only. For this purpose the home country is defined as the country of
the MCC part of the IMSI) of a cell in a base station.
Voice for AC15 of a cell in a base station.
BARRING_MMTEL_VIDEO_USAGE This parameter indicates to enable/disable ac-ssac-BarringForMMTEL-
Video of a cell in a base station.
request.
ACC_PROB_FAC_MMTEL_VIDEO This parameter is the access probability factor for MMTEL-Video of the
cell in the eNB.

Confidential
ACC_CLASS_BAR_TIME_MMTEL_ This parameter is the access barring time for MMTEL-Video of the cell
VIDEO in the eNB.
cell is barred, and does not establish RRC connection until T303 or
BAR_AC11_MMTEL_VIDEO This parameter indicates to enable/disable access barring for MMTEL
Video for AC 11 (Home PLMN only if the EHPLMN list is not present or
any EHPLMN) of a cell in a base station.
Video for AC 12 (Home PLMN and visited PLMNs of home country
BAR_AC14_MMTEL_VIDEO This parameter indicates to enable/disable access barring for
MMTELvideo.
UE can be
Video for AC15 of a cell in a base station.
BARRING_CSFB_USAGE This parameter indicates to enable/disable ac-ssac-BarringForCSFB of
a cell in a base station.
service request.
ACC_PROB_FAC_CSFB This parameter is the access probability factor for CSFB of the cell in
the eNB.
ACC_CLASS_BAR_TIME_CSFB This parameter is the access barring time for CSFB of the cell in the
eNB.

Confidential
BAR_AC11_CSFB This parameter indicates whether AC 11 (Home PLMN only if the
EHPLMN list is not present; otherwise, any EHPLMN) in the eNB is
barred at barring data.
• False: Not barred.
• True: Barred.
BAR_AC12_CSFB This parameter indicates to enable/disable access barring for data for
UE can be
BAR_AC13_CSFB This parameter indicates whether AC 13 (Home PLMN and visited
PLMNs of home country only. For this purpose, the home country is
defined as the country of the MCC part of the IMSI) in the eNB is
barred at barring data.
• False: Not barred.
• True: Barred.
UE can be
UE can be
_VOICE Barring (Mo-Sig, Mo-Data) procedure when MMTEL Voice is used.
procedure.
_VEDIO Barring (Mo-Sig, Mo-Data) procedure when MMTEL Video is used.
procedure.
_SMS Barring (Mo-Sig, Mo-Data) procedure when SMS is used.
procedure.

barringStatusType This parameter is the barring status to be changed or retrieved.

Confidential
plmnBarParamUsage This parameter indicates whether PLMN specific ACB parameters and
ACB skip indicators are used or not.
• CI_no_use: barring parameters for the corresponding PLMN index
and barringStatusType is not used.
• CI_Use: barring parameters for the corresponding PLMN index and
barringStatusType can be used.
barringSignalUsage This parameter indicates to enable/disable ac-BarringforMO-Signaling
accProbFacSignal This parameter is the access probability factor for signaling of the cell
in the eNB. UE generates a random value (rand) between 0 and 1. If
rand value is less than accessProbabilityFactor, UE can access the
cell; otherwise, access is not possible. The value p00 corresponds with
0.00, p05 corresponds with 0.05 and so on.
accClassBarTimeSignal This parameter is the access barring time for signaling of the cell in the
eNB. UE generates a random value (rand) between 0 and 1. If rand
value is higher than accessProbabilityFactor, UE determines that the
barAc11Signal This parameter indicates to enable/disable access barring for Signal
for AC11 (Home PLMN only if the EHPLMN list is not present or any
EHPLMN) of a cell in the eNB.
part of the IMSI) of a cell in the eNB.
for AC15 of a cell in the eNB.

Confidential
barringDataUsage This parameter indicates to enable/disable ac-BarringforMO-Data of a
cell in the eNB.
accProbFacData This parameter is the access probability factor for Data of the cell in
the eNB. UE generates a random value (rand) between 0 and 1. If
accClassBarTimeData This parameter is the access barring time value for Data of the cell in
rand value is higher than accessProbabilityFactor, UE determines that
the cell is barred, and does not establish RRC connection until T303
timer terminates. The expression used to calculate T303 timer value is
(0.7 + 0.6 * rand) * acBarringTime.
barAc11Data This parameter indicates to enable/disable access barring for data for
AC 11 of a cell in the eNB. ACs 11, 15 are only valid for use in the
HPLMN/EHPLMN; ACs 12, 13, 14 are only valid for use in the home
country. UE can be assigned to more than one SSAC (Service Specific
Access Class) among ACs11 (for PLMN Use), ACs12 (Security
Services), ACs13 (Public Utilities, for example, water/gas suppliers),
ACs14 (Emergency Services), ACs15 (PLMN Staff) and this
information is stored in USIM.
Access Class) among ACs11 (For PLMN Use), ACs12 (Security
country. UE can be assigned to more than one SSAC among ACs11
(For PLMN Use), ACs12 (Security Services), ACs13 (Public Utilities,
for example, water/gas suppliers), ACs14 (Emergency Services),
ACs15 (PLMN Staff) and this information is stored in USIM.
the IMSI) of a cell in the eNB.

Confidential
AC15 of a cell in the eNB.
accessBarringEmergencyCall This parameter indicates whether emergency call barring of a cell is
enabled/disabled.
barringMMTELvoiceUsage This parameter indicates to enable/disable ssac-BarringForMMTEL-
request.
accProbFacMMTELvoice This parameter is the access probability factor for MMTEL-Voice of the
cell in the eNB. UE generates a random value (rand) between 0 and 1.
If rand value is less than accessProbabilityFactor, UE can access the
accClassBarTimeMMTELvoice This parameter is the access barring time for MMTEL-Voice of the cell
the cell is barred, and does not establish RRC connection until T303 or
barAc11MMTELvoice This parameter indicates to enable/disable access barring for MMTEL
Voice for AC 11 (Home PLMN only if the EHPLMN list is not present or
any EHPLMN) of a cell in the eNB.
the MCC part of the IMSI) of a cell in the eNB.
Voice for AC15 of a cell in the eNB.

Confidential
barringMMTELvideoUsage This parameter indicates to enable/disable ac-ssac-BarringForMMTEL-
request.
accProbFacMMTELvideo This parameter is the access probability factor for MMTEL-Video of the
cell in the eNB. UE generates a random value (rand) between 0 and 1.
If rand value is less than accessProbabilityFactor, UE can access the
accClassBarTimeMMTELvideo This parameter is the access barring time for MMTEL-Video of the cell
the cell is barred, and does not establish RRC connection until T303 or
barAc11MMTELvideo This parameter indicates to enable/disable access barring for MMTEL
Video for AC 11 (Home PLMN only if the EHPLMN list is not present or
any EHPLMN) of a cell in the eNB.
Video for AC 14 of a cell in the eNB. ACs 11, 15 are only valid for use
in the HPLMN/EHPLMN; ACs 12, 13, 14 are only valid for use in the
home country. UE can be assigned to more than one SSAC among
ACs11 (For PLMN Use), ACs12 (Security Services), ACs13 (Public
Utilities, for example, water/gas suppliers), ACs14 (Emergency
Services), ACs15 (PLMN Staff) and this information is stored in USIM.
Video for AC15 of a cell in the eNB.
barringCSFBUsage This parameter indicates to enable/disable ac-ssac-BarringForCSFB of
a cell in the eNB.

Confidential
service request.
accProbFacCSFB This parameter is the access probability factor for CSFB of the cell in
accClassBarTimeCSFB This parameter is the access barring time value for CSFB of the cell in
the cell is barred, and does not establish RRC connection until T306
timer terminates. The expression used to calculate T306 timer value is
(0.7 + 0.6 * rand) * acBarringTime.
barAc11CSFB This parameter indicates to enable/disable access barring for CSFB for
purpose, the home country is defined as the country of the MCC part
of the IMSI) of a cell in the eNB.
AC 14 of a cell in the eNB.
ACs 11, 15 are only valid for use in the HPLMN/EHPLMN; ACs 12, 13,
14 are only valid for use in the home country. UE can be assigned to
more than one SSAC (Service Specific Access Class) among ACs11
(For PLMN Use), ACs12 (Security Services), ACs13 (Public Utilities,
for example, water/gas suppliers), ACs14 (Emergency Services),
ACs15 (PLMN Staff) and this information is stored in USIM.

Confidential
acBarringSkipForMMTELvoice This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when MMTEL Voice is used.
procedure.
acBarringSkipForMMTELvideo This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when MMTEL Video is used.
procedure.
acBarringSkipForSMS This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when SMS is used.
procedure.
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TS36.304: Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) procedures in idle mode, Section 5.3

Confidential
LTE-SW4106, Call Admission Control per QCI

INTRODUCTION
To utilize limited resources of an eNB efficiently and prevent the eNB from being
overloaded, management of the resources is needed, Call Admission Control
(CAC) can be used. Bearer admission control per QCI can be performed through
CAC per QCI.
BENEFIT
The operator can control bearer admission per QCI.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
In QCI based CAC, call types for CAC is more classified, that is, CAC is applied
per each QCI while Capacity based CAC is performed based on the number of
total bearer and QoS based CAC is only applied to GBR bearer.
When an RRC connection is setup, capacity based CAC is applied since QCI is not
known in this stage. QCI-based CAC can be applied when a bearer is
created/activated or call is handed in. At this moment, the applicable admission
control procedure can be described as follows:
• Capacity-based CAC: Checks whether the bearer can be admitted or not based
on the pre-configured number of bearer. For detailed procedure, see LTE-
SW4101.
• QoS-based CAC: Checks whether the GBR bearer can be admitted or not
based on the PRB usage and BH usage, if the bearer is GBR and this feature is
enabled. For detailed procedure, see LTE-SW4102.
• QCI-based CAC: Checks whether the bearer can be admitted or not based on
preconfigured number of bearers to the corresponding QCI.
To set the preconfigured number of bearers for the QCI via LSM,
MAX_DRB_COUNT (CHG-QCIDRB-CAC) is used.

Confidential
o If the current number of bearers with the same QCI as that of the bearer is
less than the threshold, the bearer is admitted.
o If the current number of bearers with the same QCI as that of the bearer is
equal to the threshold and the pre-emption is off, the bearer is not
admitted. If the current number of bearer with the same QCI as that of the
bearer is equal to the threshold and the pre-emption is on, pre-emption is
tried according to its ARP value.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CELL-CAC and set QCI_DRB_CAC_USAGE to ci_use.
• Run CHG-CELL-CAC and set QCI_DRB_CAC_USAGE to ci_no_use.
Key Parameters
parameters.
CELL_NUM Specifies the identity of EUTRAN cell.
QCI_DRB_CAC_USAGE This parameter indicates whether to perform the QCI based DRB CAC
function per cell.
• ci_no_use: Does not perform QCI based CAC function.
• ci_use: Performs the QCI based CAC function.
parameters.

Confidential

QCI_DRB_CAC_USAGE This parameter indicates whether to perform the QCI based DRB CAC function
per cell.
• ci_no_use: Does not perform QCI based CAC function.
• ci_use: Performs the QCI based CAC function.
PREEMPTION_FLAG This parameter indicates whether to perform the preemption function per cell.
• ci_no_use: If a new bearer cannot be taken over while performing the CAC
per QCI function, reject the bearer.
• ci_use: If a new bearer cannot be taken over while performing the CAC Per
QCI function, preempt the existing bearer to take over the new bearer.
Parameter Descriptions of CHG-QCIDRB-CAC/RTRV-QCIDRB-CAC

DB_INDEX Index of the QCI to perform the CAC Per QCI function.
STATUS This parameter specifies the validity of the DB_INDEX.
• N_EQUIP (=0): The DB_INDEX information is invalid.
• EQUIP (=1): The DB_INDEX information is valid.
QCI_VALUE QCI value to perform the CAC Per QCI function.
The standard QCI defined in the standard document is 1 - 9. 0 and 10 - 255
MAX_DRB_COUNT MAX DRB Count limit for the QCI to perform the CAC Per QCI function.
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TS23.203: Technical Specification Group Services and System Aspects;

Confidential
LTE-SW4107, ARP based Call Admission

Control
INTRODUCTION
The Call Admission Control (CAC) function is used to efficiently use the limited
radio resources, to guarantee the quality of user service even in case of congestion,
and to protect an eNB system from being overloaded. ARP-based Call Admission
Control determines whether to admit or reject a new radio bearer based on ARP of
the bearer.
BENEFIT
An operator can use admission control considering priority of bearers.
DEPENDENCY
Prerequisite Features: LTE-SW4101, Capacity based Call Admission Control
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature provides admission control for a new radio bearer based on ARP
information of the bearer.
Allocation and Retention Priority (ARP) information of a bearer is delivered from
MME to during the E-RAB establishment. ARP consists of priority level, pre-
emption capability, and pre-emption vulnerability. Priority level IE is defined in
3GPP 36.413 as follows.
Parameter Presence Range IE Type and reference Semantics description
Priority Level M - INTEGER (0.. 15) This IE should be understood as “priority of
allocation and retention”.
Value 15 means “no priority”. Values
between 1 and 14 are ordered in decreasing
order of priority, that is, 1 is the highest and
14 the lowest. Value 0 shall be treated as a
logical error if received.
For ARP-based CAC, the eNB makes a group. The number of groups can be up to

Confidential
4. Each ARP can be assigned to a specific group according to the configuration.

Table below shows an example of ARP groups.
ARP 1,2,3,4 5,6,7,8 9,10,11,12 13,14,15
Group Highest High Medium Low
ARP-based CAC has a configurable admission threshold for each priority group.
Bearers in each group can be allowed up to the corresponding threshold.
Figure below depicts the thresholds and the ARP-based CAC operations.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CELL-CAC and set ARP_GROUP_BASED_CAC_USAGE to USE.
• Run CHG-CELL-CAC and set ARP_GROUP_BASED_CAC_USAGE to
NOT_USE.
Key Parameters
Confidential
parameters.
ARP_GROUP_BASED_CAC_USAGE This parameter is the ARP group ID for specific ARP value.
(ARP_GROUP = 1 to 4).
(ARP_GROUP 1 is the highest priority ARP group).
parameters.
Parameter Descriptions of CHG-ARPGRP-CONF/RTRV-ARPGRP-CONF
ARP This parameter is the ARP index to configure ARP group.
(ARP = 1 to 15)
ARP_GROUP This parameter is the ARP group ID for specific ARP value.
(ARP_GROUP 1 is the highest priority ARP group).
PARAMETER DESCRIPTIONS OF CHG-ARPGRP-INFO/RTRV-ARPGRP-

INFO
ARP_GROUP_INDEX This is ARP group Index.
(ARP_GROUP 1 is the highest priority ARP Group).
DRB_THRESH This parameter is the DRB count threshold for the specific ARP group.
This parameter is valid only if ARP_GROUP_BASED_CAC_USAGE is use
(RTRV-CELL-CAC).
Counters and KPIs

Arp Group based E-RAB ArpGroupErabCacAtt The cumulated number of ARP group based E-
CAC RAB CAC attempt per each ARP group.
ArpGroupErabCacSucc The cumulated number of ARP group based E-
RAB CAC success per each ARP group.
ArpGroupErabCacFail The cumulated number of ARP group based E-
RAB CAC failure per each ARP group.
REFERENCE
Protocol (S1AP), Section 9.2.1.60

Confidential
LTE-SW4201, Standard QCI Support

INTRODUCTION
In the access network, it is the eNB's responsibility to ensure that the required QoS
for a bearer over the radio interface is met. Each bearer has an associated QoS
Class identifier (QCI). Each QCI is characterized by priority, packet delay budget,
and acceptable packet loss rate. The QCI is used for packet forwarding or
scheduling when eNB, UE, S-GW, and P-GW handle user data packets (for
example, scheduling weights, admission thresholds, queue management
thresholds, and link layer protocol configuration.)
BENEFIT
• Operator can plan a variety of premium services; end-to-end QoS
differentiated services in nine different levels as per defined in 3GPP standard.
• Operator can provide high-quality VoLTE service by using GBR bearer.
• Operator can define different service classes for each user.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Standardized QoS characteristics

The QoS characteristics of QCI 1 to 9 are standardized by 3GPP and understood as
guidelines to the pre-configuration of node specific parameters for each QCI. The
goal of standardizing a QCI with corresponding characteristics is to ensure that
applications/services mapped to that QCI receive the same minimum level of QoS
in multi-vendor network deployments and in roaming case.
The following table shows 9 standard QCIs defined in 3GPP LTE standard.
QCI Resource Priority Packet Delay Packet Error Loss Example Services
Type Budget Rate
1 GBR 2 100 ms 10-2 Conversational Voice

Confidential
QCI Resource Priority Packet Delay Packet Error Loss Example Services
Type Budget Rate
2 GBR 4 150 ms 10-3 Conversational Video (Live
Streaming)
3 GBR 3 50 ms 10-3 Real Time Gaming
4 GBR 5 300 ms 10-6 Non-Conversational Video (Buffered
Streaming)
5 Non-GBR 1 100 ms 10-6 IMS Signaling
6 Non-GBR 6 300 ms 10-6 Video (Buffered Streaming) TCP-
based (for example, www, e-mail,
chat, ftp, p2p file sharing, and
progressive video)
7 Non-GBR 7 100 ms 10-3 Voice, Video (Live Streaming)
Interactive Gaming
progressive video.)
progressive video.)
To enable a specific QCI, QCI’s status configuration parameter should be EQUIP

via CHG-QCI-VAL. If a QCI’s status value is N_EQUIP, the eNB rejects an E-
RAB setup request from MME (or source eNB for handover case), for that QCI.
QCI 1-specific Parameter Support

According to GSMA IR.92 document, the dedicated bearer for Conversational
Voice (VoLTE service) must utilize the standardized QCI value of 1. If the
VoLTE and data bearers share the common radio and/or transmission parameters,
the VoLTE service quality may be degraded because VoLTE bearers have
different QoS requirements from that of data bearers. QCI 1-specific parameter
support enables differentiated treatment for VoLTE calls.
Maximum Transmission Number of PUCCH Scheduling Request

The operator can configure the maximum transmission number of PUCCH
Scheduling Request for normal case (DSR_TRANS_MAX of CHG-DPHY-SR) and
VoLTE case (DSR_TRANS_MAXFOR_QCI1 of CHG-DPHY-SR), separately.
Normally, the eNB uses the value of DSR_TRANS_MAX by setting this value to
dsr-TransMax field in SchedulingRequestConfig IE of RRC Connection
Reconfiguration message. During VoLTE call setup, the eNB sets value of
DSR_TRANS_MAXFOR_QCI1 instead of the value of DSR_TRANS_MAX.
This operation also is applied to the handover case. The target eNB includes either
DSR_TRANS_MAX value or DSR_TRANS_MAXFOR_QCI1 value, when it sends
Handover Command message to source eNB.
When VoLTE call is released (QCI 1 bearer is released), it is re-configured to the

Confidential
value of DSR_TRANS_MAX parameter.
SYSTEM OPERATION
How to Activate
Preconditions
It is recommended for operators not to change the standard QCI-related
configurations.
The required QCIs can be activated by using CHG-QCI-VAL.
Key Parameters
parameters.
characteristics.
STATUS This parameter indicates the whether to use the QoS Class Identifier (QCI).
• EQUIP: eNB uses the relevant QCI.
• N_EQUIP: eNB does not use the relevant QCI.
RESOURCE_TYPE This parameter is the resource type of the QoS Class Identifier (QCI).
• NonGBR: Sets the resource type of the QCI to non-Guaranteed Bit Rate
(GBR).
• GBR: Sets the resource type of the QCI to Guaranteed Bit Rate (GBR).
PRIORITY This parameter is the priority of the QoS Class Identifier (QCI). The range is
0.5 to 16.0, and 0.5 means the highest priority.
SCHEDULING_TYPE Scheduling type of the QoS Class Identifier (QCI). Entered parameter value is
used for scheduling in the MAC layer.
• Dynamic_scheduling: The QCI uses the dynamic scheduling.
• SPS_scheduling: The QCI uses the SPS scheduling.
UPLINK_FORWARD This parameter determines whether to perform uplink data forwarding from the
target eNB on the bearer that has the QCI during handover.
• 0: Disables the uplink data forwarding function (not uplink data forwarding).
• 1: Enables the uplink data Forwarding function (uplink data forwarding).

Confidential
DOWNLINK_FORWARD This parameter determines whether to perform downlink data forwarding from
the target eNB on the bearer that has the QCI during handover.
• 0: Disables the downlink data forwarding function (not downlink data
forwarding).
• 1: Enables the downlink data forwarding function (downlink data forwarding).
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 23.203, Technical Specification Group Services and System Aspects;

Confidential
LTE-SW4202, Operator Specific QCIs Support

INTRODUCTION
In addition to standard QCIs, the Operator Specific QCIs Support feature allows an
eNB to support extended QCIs that range from 128 to 254.
BENEFIT
• An operator can define a customized QCI for a specific service, where QoS
characteristics of the extended QCIs may be different from those of standard
QCIs.
• UE can receive a customized network service that is suitable to a specific
application.
DEPENDENCY
Others: For the use of operator-specific QCIs, EPC and UE must recognize the
operator-specific QCIs and they shall behave to support the QoS level.
LIMITATION
• LSM may have limitation on the number of operator specific QCIs because
additional QCIs increase the amount of PM data.
• PM data is provided for the standard QCIs 1 to 9 and the operator-specific
QCIs 128 to 131.
SYSTEM IMPACT
FEATURE DESCRIPTION
Samsung eNB enables operator to define extended QCIs. Operator can determine
the resource type, priority (for GBR-type bearers), and non-GBR weight (for non-
GBR-type bearers) of the extended QCIs through LSM.
The eNB handles the extended QCIs based on those QoS characteristics
configured by operator. For the use of extended QCIs, UE and EPC shall also
recognize the extended QCIs and support the QoS characteristics.
The following table outlines the parameters for operator-specific QCI.
Parameter for Range Parameter (Command) Description
Operator Specific QCI
QCI Index 128 to 254 The numbers 10 to 127 are reserved and
cannot be used for operator-specific QCIs.
Refer to 3GPP TS24.301 Table 9.9.4.3.1.

Confidential
Parameter for Range Parameter (Command) Description

Operator Specific QCI
Resource Type GBR or RESOURCE_TYPE The operator can set GBR or Non-GBR for
Non-GBR (CHG-QCI-VAL) the operator-specific QCI.
Priority (for GBR-type 16 levels PRIORITY (CHG- The operator can select one among 16
bearers) QCI-VAL) different priority levels.
Non-GBR weight (for 16 levels NON_GBR_PF_WEIGHT The operator can choose one among 12
non-GBR-type (CHG-LOCH-INF) different non-GBR weight.
bearers)
The QoS characteristics such as resource type and priority have the same
semantics as the QoS factors of the standardized QCIs. Therefore, they have the
same impact on scheduling priority when the eNB sends UEs packets from bearers
with the operator-specific QCIs.
To support backhaul QoS in uplink direction, the operator has to configure the
QCI to DSCP mapping table via CHG-DSCP-TRF command to reflect a newly
defined operator-specific QCI, which enables eNB to assign a corresponding
DSCP value for the operator-specific QCI. In addition, operator has to configure
which network queue can be used to buffer the packets with the operator-specific
QCI via CRTE-QOS-CLASS. Depending on the queues, different network
scheduling algorithm is applied, such as Deficit Round Robin or Strict Priority
(SCHEDULER_TYPE of CRTE-QOS-POLICY).
The eNB supports both the standardized QCIs and operator-specific QCIs defined
and enabled by operator. The eNB will reject ERAB setup request if it includes an
unknown QCI (QCI’s STATUS value is N_EQUIP, which can be retrieved by
RTRV-QCI-VAL).
SYSTEM OPERATION
How to Activate
Preconditions
• It is recommended for operators to set for operator specific QCIs, STATUS,
RESOURCE_TYPE, PRIORITY must be configured before the QCI value is
activated.
• Run CHG-QCI-VA and set QCI information.
The operator can retrieve or modify QCI information by running RTRV-QCI-VAL
or CHG-QCI-VAL. The operator can input any QCI value from 10 to 255, but it is
Confidential
recommended to choose one value between 128 and 254 as per the 3GPP standard.
QCI, QCI, STATUS, RESOURCE_TYPE, and PRIORITY must be configured
before the QCI value is activated by running CHG-QCI-VAL.
• Run CHG-QCI-VAL and change the status of the operator-specific QCIs to
N_EQUIP.
Key Parameters
parameters.
characteristics.
parameters.
characteristics.
RESOURCE_TYPE This parameter is the resource type of the QoS Class Identifier (QCI).
• NonGBR: Sets the resource type of the QCI to non-Guaranteed Bit Rate
(GBR).
• GBR: Sets the resource type of the QCI to Guaranteed Bit Rate (GBR).
PRIORITY This parameter is the priority of the QoS Class Identifier (QCI). The range is
0.5 to 16.0, and the smaller value means the higher priority.
BH_SERVICE_GROUP This parameter is the Service Group of the QoS Class Identifier (QCI). The

Confidential
entered parameter value is used for the backhaul Call Admission Control
(CAC).
• voipService: The QCI uses the Voice over Internet Protocol (VoIP) service.
• videoService: The QCI uses the video service.
SCHEDULING_TYPE Scheduling type of the QoS Class Identifier (QCI). Entered parameter value
is used for scheduling in the MAC layer.
UPLINK_FORWARD This parameter determines whether to perform Uplink Data Forwarding from
• 0: Disables the uplink data forwarding function (not uplink data forwarding).
• 1: Enables the uplink data forwarding function (uplink data forwarding).
DOWNLINK_FORWARD This parameter determines whether to perform downlink data forwarding from
• 0: Disables the Downlink Data Forwarding function (not downlink data
forwarding).
• 1: Enables the Downlink Data Forwarding function (downlink data
forwarding).
CONFIGURED_BIT_RATE This is minimum configured bit rate of standard non-GBR QCI bearer in Cell
Load Calculation. If loadEvaluateMode is loadPrb, this parameter is used in
Cell Load Calculation. This parameter is applied to the bearer of QCI value 5
to 9. loadEvaluateMode is attribute of RTRV (CHG)-ACTIVE-LB.
WEIGHT_FOR_CELL_LOAD This is the weight value of PRB usage per non-GBR QCI in Cell Load
Calculation. It is used in case that loadEvaluateMode which can be checked
by CLI RTRV-ACTIVE-LB is loadPrb and the cell load is calculated
automatically.
Parameter Descriptions of CRTE-QOS-CLASS/RTRV-QOS-CLASS

CLASS_NAME This parameter is the class name used for mapping Differentiated Services
Code Point (DSCP) value and class. A class name can enter up to 32 bytes.
To map multiple DSCP values to one class, the operator can enter different
indexes and DSCP values for the same class. Use the CLASS_NAME
entered here when user add a new class to a policy by executing the CRTE-
QOS-POLICY command.
DSCP_NUMBER This parameter is the DSCP value mapped to an entered class. Multiple
DSCP values can map to the same CLASS_NAME.
Parameter Descriptions of CRTE-QOS-POLICY/RTRV-QOS-POLICY

POLICY_NAME This parameter is the name of the policy to add a new class. The policy name
can enter up to 32 bytes. When a policy is applied to a backhaul interface by
executing the CRTE-BHQOS-CONF command, use the POLICY_NAME
entered here.
CLASS_NAME This parameter is the name of a class to be added to the policy. Maximum 32
bytes can be entered. Enter the CLASS_NAME that is entered during class
configuration by executing the CRTE-QOS-CLASS command.
SCHEDULER_TYPE This parameter is the Scheduler type of the class (queue) There are two
types of schedulers, i.e. Strict Priority Queue (SPQ) and Deficit Round Robin

Confidential
(DRR).
SPQ: Transmits packets out of SPQ classes newly added to the policy
according to the priority entered for the QUEUE_PRIORITY.
DRR: If the traffic transmitted to the backhaul interface exceeds the
PORT_RATE set by CRTE-BHRATE-CONF, SPQ packets are transmitted
first according to the priorities. The remaining packets are transmitted from
the bandwidth guaranteed by the ratio set by the BW_PERCENTAGE
parameter.
QUEUE_PRIORITY If the SCHEDULER_TYPE is SPQ, priorities are set among SPQ classes
within the policy. It is valid only when the SCHEDULER_TYPE is SPQ.
BW_PERCENTAGE This parameter is the ratio of the minimum guaranteed bandwidth when the
traffic transmitted to the backhaul interface exceeds the bandwidth limit if the
SCHEDULER_TYPE is DRR. It is valid only when the SCHEDULER_TYPE is
DRR. [UNIT: %]
QUEUE_RATE This parameter is the rate of the bandwidth limitation function of the class
(queue). Shaping occurs if the traffic transmitted to the class (queue)
exceeds the set rate. The rate of the bandwidth limitation must be set in
multiple of 32.
Counters and KPI

with this feature.
REFERENCE
[1] 3GPP TS 23.203 Policy and charging control architecture (Release 12)

Confidential
LTE-SW4203, QCI to DSCP Mapping

INTRODUCTION
LTE system supports the designated level of QoS for each QCI. However, the QoS
cannot be guaranteed if the backhaul between eNB and EPC does not support
corresponding QoS. The backhaul IP network sections that cannot recognize LTE
traffic require the QoS support of IP network such as DiffServ. Therefore, LTE
QoS needs to be mapped to the IP network QoS in order to support LTE system’s
end-to-end QoS.
To provide end-to-end QoS, the eNB marks an appropriate DSCP for uplink
packets so that bearer QoS can be differentiated in the backhaul IP network section
as well. The operator can set different DSCPs for each QCI concerning all packets
transmitted by eNB. It is also available to separate DSCP for the signaling
message sent to MME or the OAM traffic delivered to LSM.
As for DL packets, SGW should support a function of DSCP marking per QCI.
For the backhaul IP network to support QoS, switches or routers that consist the
operator IP network between eNB and SGW should be set up to support QoS
based on DSCP. For example, the buffer size of each DSCP, scheduling priority,
and so on. should be set up appropriately.
BENEFIT
The operator can manage traffic from eNB to SGW for end-to-end QoS service.
DEPENDENCY
None
LIMITATION
The eNB can set DSCP values only for uplink packets. DSCP values for downlink
packets are marked by SGW.
SYSTEM IMPACT
FEATURE DESCRIPTION
The operator can set a different DSCP value for each traffic such as QCI 1 – 9
(CHG-DSCP-TRF), Signaling (S1/X2 Signaling, S1/X2-U management) (CHG-
DSCP-SIG), Management (SNMP), OAM (PM data, CSL, Trace), Network
Control (DHCP, NTP), and Default (CHG-DSCP-SYS) as shown in the table
below. This table is an example of QCI to DSCP mapping. Appropriate DSCP
values can be set according to the operator’s backhaul network operation policy

Confidential
and service.
QCI DSCP Value Traffic Type Remarks
- 24 (CS3) Signaling S1/X2 signaling (including SCTP heart-beat), GTP echo, GTP
error indication
- 24 (CS3) Management SNMP messages (Alarm, Status, Command Request/Response)
- 26 (AF31) OAM Traffic FTP, Logs (CSL, Trace), ICMP (between LSM and eNBs)
- 48 (CS6) Network control IP control (DHCP), NTP (LSM and eNBs)
1 46 (EF) QCI-1 User Data Conversational Voice (RTP) (CDMA Voice)
2 34 (AF41) QCI-2 User Data Conversational Video (Live Streaming)
3 36 (AF42) QCI-3 User Data Real Time Gaming
4 38 (AF43) QCI-4 User Data Non-Conversational Video (Buffered Streaming)
5 24 (CS3) QCI-5 User Data IMS Signaling
6 16 (CS2) QCI-6 User Data Video (Buffered Streaming), TCP-based (for example, www, e-
mail, chat, ftp, p2p)
7 18 (AF21) QCI-7 User Data Voice, Interactive Gaming, Video (Live Streaming)
8 20 (AF22) QCI-8 User Data Video (Buffered Streaming), TCP-based (for example, www, e-
9 22 (AF23) QCI-9 User Data Video (Buffered Streaming), TCP-based (for example, www, e-
- 0 (CS0) Remaining Traffic Best Effort
The backhaul network transmits and receives mixtures of various traffics such as
signaling traffic, OAM traffic, bearer traffic, and network control traffic, so the
traffics should be controlled according to the priority of each traffic. For instance,
in case of loss of signaling traffic or network control traffic, the entire service can
be affected, so it requires a higher priority than a general user's traffic. In addition,
latency of voice traffic is important, so it should have a higher priority than
Internet data traffic.
Likewise, the transport QoS function is required to control the priority of each
traffic type. In the Ethernet backhaul network, the IP layer and the Ethernet layer
uses DSCP and CoS respectively to provide the transport QoS function. The
operator can control the priorities by setting DSCP/CoS for each traffic type.

Confidential
The following figure depicts a conceptual diagram of transport QoS.
The same DSCP value can be mapped even if QCIs are different. In the eNB,
packets are classified as different network buffers (queues) depending on the
DSCP values. If the queues are different, each can have different scheduling
priorities. Strict Priority Queuing (SPQ) and Deficit Round Robin (DRR) are
applied for scheduling the packet transmission from these queues to the backhaul
network. The scheduling algorithm to be applied for each queue can be configured
by SCHEDULER_TYPE of CRTE-QOS-POLICY.
SYSTEM OPERATION
with this feature.
How to Activate
• Run CHG-DSCP-TRF and set the DSCP mapping information per QoS Class
Identifier (QCI).
The changeable information is the mapped DSCP value per QCI. When you
configure the QCI value and enter a DSCP value to change, the DSCP value of
QCI is changed.
• Run CHG-DSCP-SIG and set the DSCP setting value for signal
communication for S1/X2 Signaling, S1/X2-U management, and M2 signaling
(it is valid in MBMS-supported system.) in an eNB.
If the VirtualRouting interface is not used, the VRID value is always set to 0.
If the VirtualRouting interface is used, it can configure a DSCP value by using
VirtualRouting ID and signaling class ID as an index.

Confidential
• Run CHG-DSCP-SYS and set DSCP for system traffic, which is used
commonly for all technologies including OAM and network control traffic.
• Run CHG-DSCPCOS-MAP and set the DSCP-to-CoS mapping.
The CoS value of each packet is set to 0 by default.
Key Parameters
parameter.
Parameter Descriptions of CHG-DSCP-TRF/RTRV-DSCP-TRF
QCI It is a QoS class identifier (QCI) value to which the DSCP mapping
information will be set.
DSCP It is a DSCP value to be set for each traffic type (for each QCI).
Parameter Descriptions of CHG-DSCP-SIG/RTRV-DSCP-SIG

VR_ID This parameter is the virtual interface ID for signal of eNB.
If virtual interface is not supported, it is always set to 0.
CLASS_ID It represents a signal class ID in the eNB. Each class ID is defined as follows.
• 0: S1 Signaling
• 1: X2 Signaling
• 2: S1/X2-U management
• 3: M2 signaling (It is valid in MBMS Supported System)
DSCP It is a DSCP value to be set for each signaling traffic type generated by the
system.
Parameter Descriptions of CHG-DSCP-SYS/RTRV-DSCP-SYS

CLASS_ID This parameter is the index defined to configure the control, management
traffic, and the mapping information of Differentiated Services Code Point
(DSCP) created by the system. 7 traffic types are defined and the traffic types
corresponding to each index are as follows:
• 0: Simple Network Management Protocol (SNMP).
• 1: Secure Shell (SSH).
• 2: Secure FTP (SFTP)/File Transfer Protocol (FTP).
• 3: OAM traffic, CSL, Trace.
• 4: ICMP (Ping). This field is reserved. Currently, the DSCP marking of ICMP
is not supported.
• 5: Network control traffic.
• 6: IEEE 1588 traffic.
DSCP This parameter is the Differentiated Services Code Point (DSCP) value that is

Confidential
to be configured per control or management traffic type created by the system.
Parameter Descriptions of CHG-DSCPCOS-MAP/RTRV-DSCPCOS-MAP

DSCP This parameter is the Differentiated Services Code Point (DSCP) value that is
used to configure the Class of Service (CoS) mapping information.
COS This parameter is the Class of Service (CoS) value configured per
Differentiated Services Code Point (DSCP). More high CoS value has more
high priority.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 23.203, Technical Specification Group Services and System Aspects;

Confidential
LTE-SW4204, GBR and MBR Support

INTRODUCTION
The Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR) are the key QoS
parameters of LTE. These parameters can be set for each dedicated bearer
together. An eNB receives the two parameters from MME. A PCRF has
responsibility in the decision of GBR and MBR value. By means of GBR, an
operator can specify a minimum bit rate that the LTE system guarantees for a
specific dedicated bearer, and by means of MBR, the operator can constrain a
maximum bit rate that the dedicated bearer can achieve.
When a GBR bearer setup completes, it means that the eNB reserves radio
resources as much as it can support the guaranteed bit rate. Since the radio
resources are not enough, which operator may allow a limited amount of resources
for GBR uses, QoS based CAC has a role to decide whether eNB can support the
required GBR of a new bearer or not. For the decision, the special CAC function
takes into account of PRB usage, backhaul bandwidth usage, and the amount of
GBR resources that may be configured by operator.
In 3GPP Release 8 and Release 9 systems, MBR is recommended to be set to the
same level as GBR. However, 3GPP Release 10 allows MBR greater than GBR.
Samsung eNB supports MBR that can be greater than GBR.
BENEFIT
• The operator can provide high-quality QoS services by using GBR bearers.
• The UEs that connect a GBR bearer can achieve at least the guaranteed bit rate
that system allows even in case of congestion.
• By configuring MBR, operator can prevent GBR UEs from overusing data and
monopolizing radio resources.
• The efficient use of the radio resources.
DEPENDENCY
• The MME should support MBR so that operator can configure MBR greater
than GBR
• Related Features: LTE-ME3304 Scheduling with QoS Support
LIMITATION
None
SYSTEM IMPACT

Confidential
FEATURE DESCRIPTION
3GPP specification (TS 23.203) defines QoS classes as shown in the following
table. QCI is an index that represents each QoS class simply and defines a total of
nine QoS classes. GBR and MBR are QoS attributes that can be used by QCI 1-4
whose resource type is designated as GBR. GBR resource type is recommended to
be used mainly for voice, video and other services that need to be provided in real
time.
QCI Resource Priority Packet Delay Packet Error Example Services
Type Budget Loss Rate
1 GBR 2 100 ms 10-2 Conversational Voice
2 GBR 4 150 ms 10-3 Conversational Video (Live Streaming)
3 GBR 3 50 ms 10-3 Real Time Gaming
4 GBR 5 300 ms 10-6 Non-Conversational Video (Buffered
Streaming)
5 Non-GBR 1 100 ms 10-6 IMS Signaling
6 Non-GBR 6 300 ms 10-6 Video (Buffered Streaming)
TCP-based (for example, www, e-mail, chat,
ftp, p2p file sharing, and progressive video)
7 Non-GBR 7 100 ms 10-3 Voice, Video (Live Streaming), Interactive
Gaming
As shown in the following call flow, the UE can use a particular service through
the user plane or request for QoS through the control plane. When the UE uses a
particular service through the user plane, PCRF decides the dedicated bearer
setting, and an appropriate QoS parameter for the service such as GBR or MBR is
also decided. When the UE requests for QoS service through the control plane, the
request is delivered to PCRF through the MME. The PCRF ultimately decides
appropriate QoS parameters for the service such as GBR or MBR.
QoS Bearer Request of UE (Control Plane)

The UE can request MME for QoS bearer via Bearer Resource Allocation Request
message of NAS layer. If resource type of the QCI is GBR, the UE can indicate
GBR and MBR. However, the requested QoS information can be modified and
changed according to PCRF decision. The final QoS parameter decided by PCRF
is delivered to PGW, SGW, and eNB to support end-to-end QoS in LTE system
for the bearer.

Confidential
QoS Bearer Request of UE (User Plane)

Figure below depicts the case where UE requests for a particular service from user
plane. For example, if the UE requests for VoLTE service, the INVITE message is
delivered to server, and the server (for example, P-CSCF) requests PCRF for the
appropriate QoS support in regard to the particular IP flow. When PCRF finally
approves the request, the QoS information is delivered to QoS enforcement entities
of the user plane such as PGW, SGW, and eNB.

Confidential
The eNB receives GBR and MBR values from MME for each GBR bearer setup
request via the following messages:
• Initial Context Setup Request
• E-RAB Setup Request
• E-RAB Modify Request
The eNB allocates radio resources for GBR bearers first so as to support GBR.
The eNB rejects the call if it cannot meet the required QoS due to the lack of
resource. The eNB performs QoS based Call Admission Control (LTE-SW4102)
to decide whether it can provide the required QoS or not.

Confidential
SYSTEM OPERATION
How to Activate
Since this feature operates based on the values received via S1AP, the eNB does
not have commands and parameters related to the system operation.
Key Parameters
Counters and KPIs

RRC_REESTAB ConnReEstabReject_CP_ A call is rejected due to Air QoS based CAC during the
QOS_CAC_FAIL RRC connection reestablishment.
RRC_RELEASE ConnRelease_CP_QOS_C A call is released due to Air QoS based CAC.
AC_FAIL
ERAB_ESTAB ErabInitFailNbr_CP_QOS_ Initial E-RAB setup fails due to Air QoS based CAC.
CAC_FAIL
ERAB_ESTAB_ADD ErabAddFailNbr_CP_QOS E-RAB setup fails due to Air QoS based CAC.
_CAC_FAIL
E-RAB Modify ModQoSFailNbr_CP_QOS A call is released due to insufficient QoS-based eNB
_CAC_FAIL resources during E-RAB Modify.
REFERENCE
[2] 3GPP TS23.203: Technical Specification Group Services and System Aspects;

Confidential
LTE-SW4206, UE-AMBR Support

INTRODUCTION
The eNB restricts radio resources allocation for non-GBR bearers in a specific UE
up to the specified value by UE-AMBR. The UE-AMBR is used to control the
total sum of service rate of non-GBR bearers in the UE. Thus, it is not applied for
each bearer, individually. The UE-AMBR value is decided by MME and is
delivered to eNB when the MME requests bearer setup/modify/release to the eNB.
BENEFIT
• An operator can control the maximum achievable throughput per UE.
• The operator can differentiate subscribers by setting UE-AMBR differently per
user class.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The UE-AMBR (UE Aggregate Maximum Bit Rate) is one of QoS parameter for
non-GBR type of bearers, which is delivered from MME to eNB. When the MME
decides UE-AMBR value for a specific UE, it usually considers the following.
• The UE-AMBR value should not exceed the UE-AMBR value configured in
the Subscriber Profile.
• The UE-AMBR value should not exceed the total sum of APN-AMBR values
which UE can access.
However, UE-AMBR decision at the MME can be different depending on the
requirements of operator.
UE-AMBR is defined separately for DL and UL in the unit of bps (Refer to 3GPP
TS 36.413 Section 9.2.1.20.) and is valid until the release of RRC connection. UE-
AMBR value can be delivered to eNB via the following messages:
• INITIAL CONTEXT SETUP REQUEST (S1-MME I/F)
• E-RAB SETUP REQUEST (S1-MME I/F)
Confidential
• UE CONTEXT MODIFICATION REQUEST (S1-MME I/F)

• E-RAB MODIFY REQUEST (S1-MME I/F)
• E-RAB RELEASE COMMAND (S1-MME I/F)
• PATH SWITCH REQUEST ACKNOWLEDGE (S1-MME I/F)
• HANDOVER REQUEST (S1-MME I/F, X2 I/F)
The radio scheduler of the eNB performs packet scheduling so that the total
throughput of all non-GBR bearer of a specific UE would not exceed UE-AMBR.
This operation is performed separately for UL and DL.
SYSTEM OPERATION
How to Activate
This feature is enabled and operator cannot disable.
Key Parameters
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-SW4207, Max 8 Bearers per UE

INTRODUCTION
The eNB supports up to eight bearer connections for each UE. Eight are the
maximum number of bearers that an UE can have as per 3GPP standard. Each
bearer can be either a default bearer or a dedicated bearer, and can have different
level of QoS. The eNB provides QoS for each bearer according to parameters
delivered by messages from MME such as INITIAL CONTEXT SETUP
REQUEST, E-RAB SETUP REQUEST, HANDOVER REQUEST, and so on.
BENEFIT
An operator can provide a UE with 8 different quality of services at the same time.
DEPENDENCY
None
LIMITATION
At the eNB, the maximum number of bearers per cell and maximum number of
bearers per eNB are defined. A UE may be allocated less than eight bearers
according to call admission control function due to eNB’s bearer capacity
limitation.
SYSTEM IMPACT
FEATURE DESCRIPTION
The maximum number of data radio bearers that are permitted per UE is limited by
the 3GPP standard. As per 3GPP TS 36.321, which specifies Medium Access
Control (MAC) protocol, index values from 1 (00001 in binary) to 10 (01010 in
binary) can be used for the Logical Channel ID (LCID) in the MAC layer. Two of
them are used for signaling radio bearers, such as SRB1 and SRB2. The remaining
eight LCIDs can be used for the data radio bearers.
The table below shows values of LCID for DL-SCH (3GPP TS 36.321 Table
6.2.1-1).
Index LCID Value
00000 CCCH
00001-01010 Identity of the logical channel
01011-11011 Reserved
11100 UE Contention Resolution Identity

Confidential
Index LCID Value

11101 Timing Advance Command
11110 DRX Command
11111 Padding
The eNB provides the QoS-aware scheduling for each logical channel according to
the required QoS of the bearer. QoS parameters are delivered from MME through
messages such as INITIAL CONTEXT SETUP REQUEST, E-RAB SETUP
REQUEST, and HANDOVER REQUEST. Neighbor eNBs can also transmit
HANDOVER REQUEST messages through the X2 interface.
SYSTEM OPERATION
How to Activate
This feature is enabled and operator cannot disable.
Key Parameters
Counters and KPIs

with this feature.
REFERENCE
Medium Access Control (MAC) protocol specification, Section 6.2.1
[3] 3GPP TS36.203: Policy and charging control architecture
[4] 3GPP TS23.401: General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access, Section
4.7

Confidential
LTE-SW4208, QCI-based Non-GBR Throughput

Differentiation
INTRODUCTION
This is a proprietary feature. It provides throughput differentiation among non-
GBR bearers with different QCI (QoS Class Identifier) values. Different weight
factors can be configured for non-GBR QCIs. The weight factors are then applied
to the proportional fair scheduling to prioritize or de-prioritize radio resource
allocation to bearers with the corresponding QCIs. QCI-based differentiation
function operates regardless of cell congestion status. However, it takes effect only
in congested cells because, in uncongested situation, every bearer is able to
transmit all data regardless of configured weight value.
BENEFIT
This feature enables an operator to provide differentiated service and various
charging policies.
DEPENDENCY
The UE and the EPC also should support the same QCIs configured by this
feature.
LIMITATION
In SLR7.0.1, the configured NON_GBR_PF_WEIGHT value is not effective for UL
scheduling as per operator's s request.
SYSTEM IMPACT
FEATURE DESCRIPTION
Weight Factor Application

The weight factor represents the relative amount of the allocated radio resources.
The eNB scheduler allocates twice as many resources to the bearer with weight 2
compared to the resources for the bearer with weight 1.
The MAC scheduler firstly allocates the air resources for QCI 5 and GBR bearers,
and then it allocates the remaining air resources to the non-GBR bearers excluding
QCI 5. When it allocates the air resources to the non-GBR bearers, it considers the
weight factors. The weight factors are applied to both UL and DL.
If an UE has multiple non-GBR bearer connections, the MAC scheduler allocates

Confidential
the resources based on the weight factor of each bearer, individually. Operator can
change the weight factor for each non-GBR QCI by NON_GBR_PF_WEIGHT
configuration parameter by CHG-LOCH-INF.
When there are enough resources, the weight values do not affect to the amount of
data transmitted because all demanded traffic of each bearer will be serviced.
However, if there are not enough resources due to congestion, the resources are
distributed according to the weight factor. Thus, the bearers with a high weight can
achieve relatively higher throughput in such situation.
Weight Value Range and Configuration

The operator can set the weight values through the LSM for the non-GBR QCIs
(CHG-LOCH-INF). The operator-specific QCI (QCIs from 128 to 254) can also
have the weight value if its resource type is non-GBR. The weight value can be set
to one of 16 different weight levels.
Interaction with Proportional Fair (PF) Scheduler

For weight based scheduling of non-GBR bearers excluding QCI 5, the PF metric
is calculated as follows:
Where, Rk (t) is instantaneous data rate of non-GBR bearer k in time t, AvgRk (t)
is average throughput of non-GBR bearer k in time t, α is fairness weight factor, β
is channel quality weight factor, and W is configured non-GBR weight factor of
the bearer's QCI (that is, NON_GBR_PF_WEIGHT).
If LTE-SW4210 SPID-based Throughput Differentiation for Non-GBR UEs

feature is enabled with this feature at the same time, the effective W value is
calculated by multiplying two weight values (that is, NON_GBR_PF_WEIGHT and
PFWEIGHT_SPID.
As the value of the weight factor (W) increases, scheduling opportunity for
corresponding non-GBR bearer will increase.
UE-AMBR parameter is applied independently of this feature. If the sum of
Confidential
average throughput of non-GBR bearers (excluding QCI 5) that belongs to a

specific UE is larger than UE-AMBR, PF scheduler does not schedule
corresponding non-GBR bearers (excluding QCI 5).
Considerations when Optimizing the Feature

As the number of non-GBR bearers increases, the throughput that can be achieved
by each non-GBR bearer decreases. Especially in congestion, the throughput of the
bearers with lower weight may critically decrease due to the bearers with higher
weight. Therefore, it is necessary to limit the maximum number of UEs that are
allowed by the cell in order to guarantee a certain level of the quality of non-GBR
Bearers. Also, if the difference between lowest configured value and highest
configured value becomes larger, the impact on the bearers with low weights will
increase.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-LOCH-INF and set NON_GBR_PF_WEIGHT for specific non-GBR
QCI to nonzero value with different weight.
• Run CHG-LOCH-INF and set NON_GBR_PF_WEIGHT for all equipped QCI
to 0.
Key Parameters
parameters.
Parameter Descriptions of CHG-LOCH-INF/RTRV-LOCH-INF
NON_GBR_PF_WEIGHT The non-GBR bearer's proportional fairness weight per QCI. This parameter is

Confidential
not applied to a GBR bearer. The range is from 0 to 15 and represents 1 to 16
weight levels, respectively.
parameter.
Parameter Descriptions of CHG-LOCH-INF/RTRV-LOCH-INF
QCI QCI (QoS Class Identifier) index.
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TS 23.203: Technical Specification Group Services and System Aspects;

Confidential
LTE-SW4210, SPID-based Throughput

Differentiation for Non-GBR UEs
INTRODUCTION
This function allows differentiated non-GBR service according to UE's SPID value
received from MME. When MME is executing the connection setup procedure for
an UE, it notifies the UE's user class to eNB through the SPID value.
The eNB internally manages the mapping table between SPID and weight. The
operator can set and change the mapping table between SPID and weight via the
LSM.
BENEFIT
An operator can support a differentiated service plan according to UE class such as
Gold User, Silver User, and Bronze User. Thus, an operator can operate various
charging policy according to UE class.
DEPENDENCY
None
LIMITATION
The maximum of eight differentiation levels are supported. (Operator can
configure weights for up to eight SPID values.)
SYSTEM IMPACT
FEATURE DESCRIPTION
Managing Mapping Table of SPID and Weight through LSM

To enable this function, the operator sets the mapping table between the SPID and
the weight via the LSM. The SPID value must be a valid value included in the
SPID value range that is transmitted by MME to the eNB. The eNB applies the
default weight value of "1" if the MME does not designate a SPID value for the
UE or when the SPID that is not included in the configured table is transmitted.
The operator also change weight factor for each SPID by PFWEIGHT_SPID of
CHG-SPIDPFWEIGHT-CONF.

Confidential
The following table is an example of the mapping table of SPID and weight value.
Index SPID Weight
0 101 1
1 102 2
2 103 3
3 104 4
4 107 1
5 108 2
6 109 3
7 110 4
SPID Transmission
MME transmits a particular SPID value via S1 messages (Initial Context Setup or
UE Context Modification Request) for the premium users.
Range of SPID Values

SPID value usage is defined in 3GPP TS36.300 Annex I. SPID value range is
defined as 1 to 256 in the standard. SPID 129~256 defined in 3GPP is used for
specific purposes and SPID 1 to 128 is used for operator’s specific purposes. For
this feature, SPID value is used independently from its original purpose and this
feature does not affect its original operation (for example, SPID 254 to 256 are
used for deciding the priority of carriers between Inter-RATs).
Interaction with Proportional Fair (PF) Scheduler

For weight based scheduling of non-GBR bearers excluding QCI 5, the PF metric
is calculated as follows:
Where, Rk(t) is instantaneous data rate of non-GBR bearer k in time t, AvgRk(t) is

average throughput of non-GBR bearer k in time t, α is fairness weight factor, β is
channel quality weight factor, and EffectiveW is the calculated value by
multiplying NON_GBR_PF_WEIGHT and PFWEIGHT_SPID.
NON_GBR_PF_WEIGHT is non-GBR weight factor of the bearer's QCI. (Refer
LTE-SW4208 QCI-based non-GBR Throughput Differentiation feature
description.) As the value of the weight factor (EffectiveW) increases, scheduling
opportunity for corresponding non-GBR bearer will increase.
Simultaneous Application of Weight-Related Functions

Not only this feature but the LTE-SW4208 feature also provides non-GBR
throughput differentiation based on weight. When both features are enabled, the
effective weight is the product of the SPID weight and QCI weight. If the
multiplied value is over 16, the maximum value, 16, is applied.

Confidential
Where:
• W1 is the weight value applied to the corresponding UE based on the SPID.
• W2 is the weight value that is applied to the Non-GBR QCI based on the QCI.
The range of the relevant system parameter, NON_GBR_PF_WEIGHT via CHG-

LOCH-INF command, is 0 to 15 for 1 to 16 weight levels.
Considerations when Optimizing Function

Because the wireless resources to be shared are limited, it is natural that the
throughput, which can be achieved by each UE, decreases as the number of UEs
increases. In congestion, if the number of premium users with the higher weight
values increases, the users with the lower weight values experience low
throughput. Therefore, the QoS levels of overall UEs are determined in
consideration of the weight value levels and the number of users permitted by each
cell.
Also, when operator turns on this feature along with the LTE-SW4208 function,
the weight values shall be configured with consideration of both non-GBR
weights. The ranges of effective weight are not to be biased.
This function shall be disabled if operator wants to use SPID values for other
purpose.
SYSTEM OPERATION
How to Activate
Preconditions
• SPID to apply this feature should be configured in advance in the operator
network.
• Run CHG-SPIDPFWEIGHT-CONF and set appropriate non-GBR weight to
the user specified SPID (non-zero SPID).
• Set all SPIDs to 0 (not use).

Confidential
Key Parameters
parameters.
Parameter Descriptions of CHG-SPIDPFWEIGHT-CONF/RTRV-
SPIDPFWEIGHT-CONF
SPID[8] This parameter is the subscriber profile ID (SPID) to which scheduling weight
for non-GBR bearer is applied.
• 0: Not Use
• 1 to 256: Use SPID
parameters.
Parameter Descriptions of CHG-SPIDPFWEIGHT-CONF/RTRV-
SPIDPFWEIGHT-CONF
PF_WEIGHT_SPID[8] This parameter is the scheduling weight to applied to designated SPID. If the
value is set to zero, then the scheduling weight are not applied for the
corresponding SPID.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS36.413: Evolved Universal Terrestrial Radio Access (E-UTRAN) S1
Application Protocol (S1AP)
[2] 3GPP TS36.300: Evolved Universal Terrestrial Radio Access (E-UTRAN);
Overall description; Stage 2

Confidential
LTE-SW4211, Application Aware QoS

INTRODUCTION
The Application Aware QoS feature supports application-aware traffic control,
which controls packet rate of a specific application when the cell congestion
occurs. The eNB identifies specific applications within a non-GBR bearer. Then,
the eNB performs rate control for the application not to exceed the configured
service rate, if a cell is in congestion state.
BENEFIT
• Operator can prevent network service quality degradation due to the specific
applications such as P2P and FTP. Some applications such as video and web
can have high service quality in terms of throughput and/or latency by
dropping (a part of) packets belong to the specific applications such as P2P
and FTP under the congestion situation.
• Users can experience better quality for delay-sensitive applications even in
congestion situation.
DEPENDENCY
Others: The Core Network (CN) should support DSCP marking of the UE IP
packet and deliver to the eNB to enable this feature.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
According to current 3GPP standard, QoS differentiation is performed on E-RAB
basis. However, in most commercial LTE network, multiple different types of
application (for example, video, web, email, P2P, FTP, and so on) are delivered
through one specific non-GBR bearer (usually, a default bearer for Internet APN).
Therefore, they will have same QoS characteristics according to QCI of the bearer.
The eNB processes them without distinction even in congestion situation.
With this feature, the eNB can control packet service rate of a specific application,
which is distinguished by DSCP, when the cell congestion occurs.
Figure below depicts the example of the rate control for packets with DSCP = YY
and DSCP = ZZ.

Confidential
The rates of 100 Kbps and 200 Kbps are configured for YY application and ZZ
application, respectively. The incoming packets for each configured application
will be dropped according to their configured rate.
The rate control function is activated only when the cell congestion situation as
depicted figure below.
Detection for Application Awareness

Application differentiation is based on DSCP marked from the Core with inner IP
header of data packets. Thus, the core network is needed to support packet
inspection functionality.
Application-Aware Traffic Control

If air resource utilization of a cell is higher than the pre-configured threshold, rate
control is activated for the service with a configured DSCP. The rate control
function performs dropping (a part of) packets according to configured rate for the
DSCP value. If air resource utilization of a cell is lower than the pre-configured

Confidential
threshold, rate control is de-activated for the service with a configured DSCP. The
congestion is determined based on air resource utilization measured from physical
resource block (PRB) usage. The PRB usage includes total usage of signaling
bearers, GBR bearers, and non-GBR bearers.
Traffic Control Policy

The following figure shows how the eNB performs the rate control function
through well-known token bucket algorithm.
Token
MAX Bucket
Received Packet PASS

DROP
• A token is generated periodically regardless of packet reception.

• Tokens can be accumulated by maximum number of tokens or maximum
bucket size. An amount of tokens in a bucket means the number of packets that
can be passed.
• If the size of a received packet is larger than the amount of tokens in the
bucket, the packet is dropped.
• If the size of a received packet is smaller than the amount of tokens in the
bucket, the packet is passed. Then, the amount of tokens is reduced by the size
of the passed packet.
The operator can configure token generating rate via dlTcBandwidth (in
Kbps), and maximum bucket size (in bytes) via dlTcBurstLimit.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• The CN should support DSCP marking functionality about IP packet of UE.

• Run CHG-GTP-INF and set TC_FLAG to ON to activate this feature.
• Run CHG-GTP-INF and set TC_FLAG to OFF to deactivate this feature.
Key Parameters
parameter.
Parameter Descriptions of CHG-TWAMP-CONF
TC_FLAG This parameter is on/off configuration of Traffic Control.
parameters.
Parameter Descriptions of CHG-TC-POLICY
cellType This parameter is the eNB cell type. The Macro type has to input
SmartCellType_OFF, and the Smart type input the SmartCellType_ON.
cellNumId This parameter is the cell ID applied for the traffic control policy. The Macro
type has to input the cell ID, and the Smart type input the Subcell ID.
dscpId This parameter is the dscp index applied for the traffic control policy.
innerDscp This parameter is the dscp value. DSCP value means DSCP value mapping
QCI of a non-GBR in PLDDSCPMapTraffic. To input the DSCP value making in
core system. In case the user sets up a wrong parameter, the traffic loss can
happen.
dlTcBandwidth This parameter is the maximum Bandwidth of Rate Limiting for Traffic Control.
(0: disable, 1 to 1000000: enable)
dlTcBurstLimit This parameter is the maximum token size in which it can be processed packet
at a burst time.
Parameter Descriptions of CHG-TC-PI
cellType This parameter is the eNB cell type. The Macro type has to input
SmartCellType_OFF, and the Smart type input the SmartCellType_ON.
cellNumId This parameter is the cell ID of the traffic control PRB information. The macro
type has to input the cell ID, and the Smart type input the Subcell ID.

Confidential
prbThreshold This parameter is threshold of downlink total PRB usage. (0: disable, 1 to 100:
enable)
Counters and KPIs

Family Display Name Counter Type Description
DL_TRAFFIC_CONTROL CellTcDLByte This counter collects the byte count of DL
traffic by each DSCP and each cell.
CellTcDLPeriod This counter specifies the CellTcDLByte
collection time.
CellTcDLPacket This counter collects the packet count of DL
CellTcDLThruAvg This counter collects the average total
throughput of DL traffic by each DSCP and
each cell.
CellTcDLThruMin This counter collects the minimum total
each cell.
CellTcDLThruMax This counter collects the maximum total
each cell.
CellTcDLDropByte This counter collects the drop byte count of DL
CellTcDLDropPacket This counter collects the drop packet count of
DL traffic by each DSCP and each cell.
CellTcDLDropRatio This counter collects the drop packet ratio of
DL traffic by each DSCP and each cell.
REFERENCE
None

Confidential
LTE-SW5500, CA Call Control

INTRODUCTION
The Carrier Aggregation (CA) is one of the key LTE-Advanced features. It
aggregates more than one contiguous or non-contiguous Carrier Components (CC)
to increase bandwidth. With this feature, the Samsung eNB allows single UE to
use two or more carrier resources simultaneously in Downlink (DL).
BENEFITS
• An operator can enhance the utilization of network resources by distributing
the traffic dynamically over multiple carriers.
• A UE can aggregate adjacent, non-adjacent, or different frequency bands,
which in turns improves the throughput and reduces the download time.
DEPENDENCY
• HW dependency:
Support Channel Cards: Refer to carrier aggregation bandwidth combination
features
• Related Radio Technology: E-UTRAN (LTE) 3GPP LTE Rel.10 Carrier
Aggregation
LIMITATION
The UE connecting to a TDD cell does not have a FDD SCell in this release.
SYSTEM IMPACT
capabilities.
LTE-SW5500 CA Call Control and CA bandwidth combination features, which
are varied by operator and eNB configuration, should be supported for carrier
aggregation.
available spectrum resources effectively across the network.
Coverage

Confidential
Interfaces
None
FEATURE DESCRIPTION
The Samsung eNB uses the radio resources of Primary Cell (PCell) and Secondary
Cell (SCell) to provide maximum data rate based on the UE capabilities. The UE
can utilize the resources of both the cells in DL, which transmits data traffic on
different channels. The eNB configures the control channel at PCell to allocate
resources at SCell for user data transmission.
The eNB performs the following functions to configure SCells when the UE has a
Radio Resource Connection (RRC) on a PCell:
• Selection of SCell(s)
• Decision on addition of SCell(s)
• Delivery of the L1 and L2 configuration information for SCell(s)
To support these functions, the basic call processing procedures, such as a UE
context setup and handover are upgraded. For detailed information on each
procedure, see section Operational Procedure.
Types of Carrier Aggregation
The eNB aggregates two CCs depending upon the frequency band usage:
• Intra-band Contiguous: The eNB aggregates contiguous CCs within the same
operating frequency band.
• Intra-band non-contiguous: The eNB aggregates multiple CCs, which have
gaps in between them, from same operating frequency band for CA.
• Inter-band Non-contiguous CA: The eNB aggregates multiple CCs across
different frequency bands for CA. With this type of aggregation, mobility
robustness is improved potentially by utilizing different radio propagation
characteristics of different bands.
The figure below depicts the types of CA in different frequency bands.
The eNB supports two different CA deployment scenarios based on the spectrum
usage and area to be covered. To support the basic deployment scenarios, two
operating modes are introduced. Each mode has different characteristics. Operator
can configure a suitable mode that fits your coverage deployment by using
caOperationMode (CHG-CACELL-INFO).

Confidential
Figure below depicts the CA deployment scenarios, where CC1 and CC2 are of
two different bands.
Table below outlines the operating modes of the eNB in two deployment scenarios
indicated in the figure above.
CA Preferred Characteristics Example Measurement
Operation Deployment Configuration State (per
Mode Scenario carrier-frequency)
Configured Non-
frequency configured
frequency
1 1 The PCell and SCell are SCell Not
co-located, and therefore, Configuration applicable
the eNB adds the SCell
without checking the radio
quality of SCell when the
co-located SCell
designated to PCell is
connected and HO is led
in.
2 1 and 2 The eNB adds the SCell • SCell Event A4
unconditionally when the Configurati configurati
UE is attached. The co- on on for
located SCell can be • Event A2 SCell
released based on the Configurati addition
event A2 MR or added on for
depending on the radio SCell
quality measurement release
received through event A4.
The collocated cell can be configured to PCell by using colocatedCellNum

(CHG-CA-COLOC) per component carrier.

Confidential
Operational Procedure
A UE establishes and re-establishes Radio Resources Connection (RRC) with an
eNB on a PCell, and then uses this connection to add or remove more serving
cells. The eNB identifies the RRC connection of each UE by Cell Radio Network
Identifier (C-RNTI). On receipt of Initial Context Setup message, the eNB:
• Configures the Secondary Carrier Component (SCC) measurements for the UE
based on the UE Capability Information IE received in the message
• Sends the RRC Connection Reconfiguration message to the UE for adding or
removing the SCell depending on the deployed CA mode
The eNB considers the conditions outlined in the table below to configure the
number of SCells based on the UE capabilities and available CA mode.
Condition Selection Description
Criteria
C1 PCell CA Based on flag per PCell (caAvailableType (CHG-CACELL-INFO))
ON/OFF • If the value is 0, then off
• If the value is 1, the on
C2 CA Band Decides success or failure per SCC if the carrier frequency and allowed
Capability measurement bandwidth of SCC supported by the eNB exist in the scope of
band combination and CA bandwidth class of the received UE capacity
C3 Co- Decides whether co-scheduling of PCell and SCell is allowed.
Schedulability Operator can set the schedulable unit for a cell by using parameter
schedulabilityUnit (CHG-CASCHED-INF). If the cell requested as a SCell
is in the schedulable unit same as PCell, then success, else, failure.
C4 SCell • Decides the service availability of SCells in the serving area
Availability Releases the SCell for a UE if the state of the cell requested as a SCell is cell
release
• Decides on the SCell shut down state, if the state of the cell requested as a
SCell is shutdown
• Decides on the possibility to add a SCell considering all cells are barred and
reserved for operator use
C5 Cell • Decides the allowed number of SCell addition based on the number of
Capability connected UEs in PCell and SCell
• Rejects SCell addition, if the UE has exceeded the maximum number of SCell
connections
CA Procedure during Initial Context Setup

When the Mobile Management Entity (MME) sends the Initial Context Setup
request, the eNB checks the UE capability and configured co-located SCell, and
then adds the SCell or sets the measurements based on the deployed modes. The
eNB validates the following conditions in sequence during initial context setup to
determine the CA availability:
• C1: PCell CA ON/OFF
• C2: CA Band Capability
• C4: SCell Availability
• C5: Cell Capability
Figure below depicts the SCC measurement configuration procedure during Initial
Confidential
Context Setup.
1 The UE establishes the RRC connection with the eNB through a PCell.
2 The eNB checks whether the UE is capable of supporting SCell and the co-
located SCell is configured for the cell or not.
If… Then…
The UE is capable of supporting SCell The eNB selects the CA mode, based on the configuration, and
configuration and the co-located SCell goes to step 3.
is configured
The co-located SCell is not configured The eNB goes to step 3.
3 Selects the SCell if the C1 and C2 conditions are passed according to the CA
operation modes
In case of… The eNB configures…
Mode 1 C4 and C5 are met for the UE to add the co-located SCell at SCC after passing C2
co-located SCell If the co-located cell is not configured, the eNB does not perform CA
related operations on reconfiguration message.
Mode 2 C4 and C5 are met for the • UE to add the co-located SCell at SCC after passing C2
co-located SCell • Event A2 measurement for SCell release
• Configure measurement cycles for SCell
For details about how the eNB releases the co-located SCell after
receiving the A2 Measurement Report (MR), see section CA
Procedure at Reception of Event A2 MR in Modes 2.
C4 and C5 are not met for Event A4 measurement for SCell addition at SCC after passing C2.
the co-located SCell For more details about how eNB adds the SCell after receiving the
A4 MR, see section CA Procedure at Reception of Event A4 MR in
Modes 2.

Confidential
4 If neither of the conditions is passed, the eNB configures normal settings in

RRC Connection Reconfigure message and sends it to UE. If any of the
conditions is met before releasing the RRC connection or during handover,
the SCell and relevant measurement configuration is not changed.
CA Procedure at Reception of Event A2 MR in Modes 2
When the eNB receives event A2 MR from a UE, it initiates a separate RRC
Connection Reconfiguration message towards UE to set:
• SCell release in the SCC corresponding to MO of the triggered event A2
• Release of event A2 measurement for SCell at SCC for which released SCell
is MO
• Configuration of event A4 measurement for SCell addition at SCC for which
released SCell is MO
The Event A2 setting for SCell release can be configured by using CHG-EUTRA-
A2CNF command with purpose index as ci_A2PurposeCa.
CA Procedure at Reception of Event A4 MR in Modes 2
The UE and eNB are at the state of no added SCell when the UE sends event A4
MR to the eNB to add an SCell. The eNB validates the following conditions in
sequence after receiving the report for the neighbor cell:
• C3: Co-Schedulability
The Event A4 setting for SCell addition can be configured by using CHG-EUTRA-
A4CNF command with purpose index as ci_A4PurposeCa.
Figure below depicts the CA procedure to add a SCell on receipt of Event A4.
1 The eNB receives event A4 MR for the neighbor cells through PCell.

Confidential
2 If conditions C3, C4 and C5 are met, the eNB uses a separate RRC
Connection Reconfiguration message to set the information outlined in the
following table, otherwise it ignores the A4 measurement report.
In case of… The eNB…
Mode 2 C3, C4, and C5 are met • Configures the MR triggered cell as an SCell
• Releases the event A4 measurement on SCC of added SCell
• Configures the event A2 measurement to release SCell for
which SCC of added SCell is Measurement Object (MO)
CA Operation at Intra-eNB Handover

When a serving eNB supporting CA receives a measurement report for intra-eNB
handover, it determines the CA availability in the target cell by validating the
following conditions in sequence:
Figure below depicts the CA procedure during intra-eNB handover.
1 The PCell sends the SCell configuration in event A3 report and sets
reportAddNeighMeas to Setup through the RRC Connection Reconfiguration
message to UE when the UE is attached to the PCell or during hand-in.
2 The UE sends the measurement report to the PCell. The report includes the
measurement results: RCRP/RSRQ of SCells and PCID and RSRP/RSRQ of
neighbor cells with the greatest RSRP in the SCC, which is the existing
configured SCell in the MeasResultServFreq IE.
3 The eNB determines the SCells to be configured based on the CA operating
mode of the target PCell. The list of SCells configured in the source PCell is
configured in SCellToReleaseList-r10 IE.

Confidential

Mode 1 The C1 and C2 conditions UE to add the co-located SCell on SCC
are passed and C4 and C5
are met for the co-located
SCell
Mode 2 The C1 to C3 conditions • UE to add the co-located SCell on SCC
are passed and C4 and C5 • Event A2 measurement for SCell release at SCC on which
are met for the co-located added SCell is MO
SCell
CA Operation at Inter-eNB Handover

When a UE detects the neighboring inter-frequency cell's strength stronger than
the serving PCell, it notifies the serving eNB through A3 measurement report. The
eNB performs an inter-frequency handover in advance, before the UE reaches to
the edge of an area to maintain the throughput. It determines the CA availability in
the target cell by validating the following conditions in sequence:
Figure below depicts the CA procedure during inter-eNB handover.

Confidential
1 The PCell sends the SCell configuration in event A3 report and sets
reportAddNeighMeas to Setup through the RRC Connection Reconfiguration
message to UE
2 The UE responds on the measurement report to the PCell. The report includes
the measurement results: RCRP/RSRQ of SCells and PCID and RSRP/RSRQ
of neighbor cells with the greatest RSRP in the SCC, which is the existing
configured SCell in the MeasResultServFreq.
3 The source eNB sends the S1AP or X2AP Handover Request message to the
target eNB. The message includes:
o Serving SCell list (sCellToAddModList) set by the source eNB

Confidential
o CandidateCellInfoList on the serving frequencies

o UE-RadioAccessCapability
4 If all conditions C1 to C3 are met, the eNB determines the SCells to be
configured based on the CA operating mode of the target eNB's PCell.
Mode 1 C4 and C5 are met for the UE to add co-located SCell at SCC after passing C2
co-located SCell
Mode 2 C4 and C5 are met for the UE to add co-located SCell at SCC after passing C2
co-located SCell Event A2 measurement for SCell release at SCC on which the
SCells are added
CA Operation at Reception of RRC Connection Re-establishment

The UE sends an RRC Connection Reestablishment message to the eNB in case of
a radio link or handover failure. After receiving the message, the eNB:
• Deletes all existing SCell information for the UE
• Reconfigures new SCell information for PCell
• Sends a separate RRC Connection Reestablishment message to the UE
The eNB follows the same procedure for reconfiguration of SCell and
measurements as described in the Section CA Procedure during Initial Context
Setup.
CA Call Count and CAC
Cell Call Count = RRC Connected UE + UE activated as SCell

• Connected UE: UE that has RRC connection with the Cell as Serving Cell
(Non-CA) or PCell (CA).
• SCell UE Call Count: SCell UE Call Count is pegged by the first SCell
activation of the CA Call.
If the Call Count reaches to maxCallCount, 1 SCell UE is released for admission

of new-coming Non-CA UE or PCell UE.
PCell Frequency Changing
On meeting event-triggering conditions for SCell-configured UEs, SCell-
configured UEs perform inter frequency searching and inter frequency handover to
the SCC. The following figure shows state transition diagram of SCell
configuration and measurement configuration in PCell Frequency Switching.
• CA_InterF_: threshold or offset for SCell-configured UEs to trigger inter-
frequency carrier searching or handover
• InterF_: threshold or offset for non-CA UEs (including CA UEs which do not
have SCell added) to trigger inter-frequency carrier searching or handover
Operation Details (Mode 1)

This section describes how measurements are managed in Mode 1.

Confidential
As aforementioned, the SCell is added in Mode 1 at the time of RRC Connection

Reconfiguration (if not already added). With the SCell addition, the
CA_InterF_A2 event is configured for the PCell. This event is used to monitor the
PCell level and trigger further measurements. It should be defined higher than
regular A2 measurements.
When the CA_InterF_A2 trigger is reported, the eNB configures CA_InterF_A1
(on PCell), CA_InterF_A3/A5, and InterF_A2 (on PCell). If the UE reports
CA_InterF_A1, other measurement triggers are removed and CA_InterF_A2 is
again added.
If the UE reports InterF_A2, eNB configures InterF_A1 and InterF_A3/A5 on the
UE and removes other measurements.
If the UE reports CA_InterF_A3/A5 (for SCell FA), the eNB performs a PCell
switch in which the SCell FA becomes the new PCell and the previous PCell FA is
added as the new SCell.
If the UE reports InterF_A1, the eNB removes the existing measurements and adds
CA_InterF_A1 (on PCell), CA_InterF_A3/A5, and InterF_A2 (on PCell).
If the UE reports InterF_A3/A5, a regular handover is performed.
Operation Details (Mode 2)

The Mode 2 operates similarly to Mode 1 except that A2 measurements related to
SCell addition and release are also added.

Confidential
The Event A1 setting for PCell frequency changing can be configured by using
CHG-EUTRA-A1CNF with purpose index as ci_A1PurposeCaInterFreq.
Limitation
PCell Frequency Switching does not apply to UEs having GBR bearers.
SCC Selection
The eNB selects one of a number of Supported Band Combinations identified from
the UE Capability to configure the SCell(s). The operator can set SCC selection
criteria by using parameter sccSelectionPriority1, 2, and 3 (CHG-CA-OPTION) to
maximize the utility of the multi-carrier or to adapt to the service strategy and
policy of each LTE frequency.
Samsung eNB system offers a four selection criteria, as below
• UE/BW is supposed to be minimized to give the CA UE better opportunity of
resource allocation. To use this option, set sccSelectionPriority as
number_of_UE_with_BW.
• Total BW is to be maximized to maximize the UE peak throughput. To use
this option, set sccSelectionPriority as Size_of_BW.
• Available capacity is to be maximized to maximize the expected throughput of
Confidential
the UE, based on radio resource utility. To use this option, set
sccSelectionPriority as CAC.
• Operator specific band priority option is given to allow the operator to assign a
CA priority to a specific LTE frequency band(s). To use this option, set
sccSelectionPriority as operator_specific and
operatorPreferredDlBand.
• If PCell or SCell candidate supports 4x4 MIMO or DL 256QAM, BW and
available capacity is converted to effective value by weight factor of 4x4
MIMO and weight factor of DL 256QAM. These weight factors can be
configured with controlFactorFor4LayerMimo and
controlFactorFor256Qam (CHG-CACELL-INFO).
Dynamic SCC Selection

Depending on the location and mobility of the UE, the first priority CA band
combination may not be the best CA band combination selection if the coverage of
each frequency differs, as depicted in the following figure.
UE Throughput
1st priority band
combination
2nd priority band

combination
Distance
CA Call Control improves this problem with Dynamic SCC Selection function,
which can be enabled with parameter sbcListPriorityUsage (CHG-CA-
OPTION).
Dynamic SCC Selection supports the MR-based SCell addition operation by
setting the SCell Addition purpose measurement to the SCC of the next rank if the
CA state does not come back to first priority combination until the waiting timer
expires after the SCell release occurs. This function helps to improve CA
performance by changing to a different combination when coverage of the first CA
band combination selected by the SCC selection setting is not sufficient.

Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CACELL-INFO and set CA_AVAILABLE_TYPE to DL_Only to
enable carrier aggregation.
• Run CHG-CACELL-INFO and set CA_AVAILABLE_TYPE to CA_OFF to
disable carrier aggregation.
Key Parameters

Confidential

• CA_OFF
• DL_only
• DL_and_UL
parameters.
CELL_NUM The cell number. This value must not exceed the maximum
number of cells supported by the system. It is determined by
FA/Sector. For example, if the maximum capacity provided to
the carrier per system is 1 FA/3 Sector, up to 3 cells are
supported.
CA_AVAILABLE_TYPE This parameter indicates whether to support CA.
P_CELL_ONLY_FLAG This parameter indicates whether to support only P Cell.
MAX_DL_CA_CC_NUM The maximum number of carriers to support downlink CA.
MAX_UL_CA_CC_NUM The maximum number of carriers to support uplink CA.
CA_OPERATION_MODE CA Operation mode.
• Mode1: Pcell and Scell are co-located and the Scell is added
during initial attachment.
• Mode2: Pcell and Scell are co-located and initial attachment
will try Scell addition. If Scell is not found, Scell is released.
• Mode3: Pcell and Scell are co-located and Scell is added
based on MR.
• Mode4: SCell is changed by measurement about SCC
CONTROL_FACTOR_FOR_4LAYER_MIMO This parameter indicates the expected average throughput gain
to be obtained additionally when 4-layer MIMO is applied, and
is represented by a unit of %. This parameter controls only DL
CA. The larger the number of this parameter, the greater the
possibility of choosing Supported Band Combination including
carrier Component that supports 4-layer MIMO. If
sccSelectionPriority is operator specific, this parameter does
not effect to select SBC.
CONTROL_FACTOR_FOR_256QAM This parameter indicates the expected average throughput gain
to be obtained additionally when 256QAM is applied, and is
represented by a unit of %. This parameter controls only DL
CA. The larger the number of this parameter, the greater the
possibility of choosing Supported Band Combination including
carrier component that supports 256QAM. If
sccSelectionPriority is operator specific, this parameter does
not effect to select SBC.
Parameter Descriptions of CHG-CASCHED-INF/RTRV-CASCHED-INF

SCHEDULABILITY_UNIT This parameter is the CA Schedulability unit. It indicates the range of

Confidential
SCells for CA in the eNB.
• IntraEnb: Selects SCells in the same eNB.
• caGroup: Selects SCells in the CA Group.
Parameter Descriptions of CHG-CA-COLOC/RTRV-CA-COLOC

STATUS This parameter indicates whether the tuple information is valid.
COLOCATED_CELL_NUM This parameter is the number of the cells in the same eNB that are co-
located with CELL_NUM. This parameter is the input range is the maximum
number of the cells that the system supports. In case of Mode1, 2, the cells
specified as COLOCATED_CELL_NUM become the Scell targets.

S_CELL_DEACTIVATION_TIM This parameter is the waiting time until a Scell is deactivated by MAC. This
ER parameter is the value set to a UE if one or more Secondary Cells (Scell)
are operating during Carrier Aggregation (CA) operation. It is
recommended to use a default value. Be careful when setting the value
because the Scell Deactivation time becomes long if the timer value is
large.
Parameter Descriptions of CHG-CABAND-INFO/RTRV-CABAND-INFO

BAND0_USAGE This parameter indicates whether to use band combination of BandEutra0
and caBandwidthClassDl0
BAND_INDICATOR0 CA-supported BandIndicator
CA_BANDWIDTH_CLASS_DL0 CA Bandwidth Class
CA_BANDWIDTH_CLASS_DL1 CA bandwidth class
CA_BANDWIDTH_CLASS_DL2 CA bandwidth class
BAND0_FOR_UL_USAGE This Parameter indicates whether to use BandIndicator0 for UL CA.
CA_BANDWIDTH_CLASS_UL0 CA bandwidth class Of BandIndiCator0.
When SupportedBandCombination-r10 in UE-EUTRA-CAPABILITY
includes band parameter, which consists of bandIndicator0 and
caBandwidthClassUl0, This parameter can be selected PCELL Band or UL
CA Band
BAND1_FOR_UL_USAGE This parameter indicates whether to use BandIndicator1 for UL CA.
CA_BANDWIDTH_CLASS_UL1 CA bandwidth class Of BandIndiCator1.

Confidential
CA Band.
CA_BANDWIDTH_CLASS_UL2 CA Bandwidth Class Of BandIndiCator2.
CA Band.
Parameter Descriptions of CHG-CA-OPTION/RTRV-CA-OPTION

SCC_SELECTION_PRIORITY1 This parameter is used to give priority to SCC Selection. When a high
priority condition is chosen and there is more than one SCC that meets
the condition, the SCC selection is determined by the condition specified
in this parameter. An option that is chosen in high priority should not be
chosen again, except for the option Not_use.
• Size_of_BW: The size of BW becomes the condition for SCC selection.
The SCC with bigger BW is chosen.
• CAC: CAC stands for Composite Available Capacity. The SCC with
greater CAC is chosen.
• number_of_UE_with_BW: The number of UE with BW consideration
becomes the condition for SCC selection. The SCC with the least
amount of UE after BW normalization is chosen.
• operator_specific: This option exists to give the operator forced priority.
OPERATOR_PREFERRED_BAND is selected as SCC.
• not_use: Does not give additional priority to SCC selection.
OPERATOR_PREFERRED_DL_ This parameter is to define Band Value that gives the operator forced
BAND1 priority for SCC selection. The selected Band value is valid if the value of
sccSelectionPriority1 equals operator_specific.

Confidential
BAND3 priority for SCC selection. the selected Band value is valid if the value of
SCC_PLMN_SELECTION This parameter is used to control SCell configuration capability for Cells
that do not support the same PLMN as PCell PLMN.
• Not_use: Set the Cell that does not support the same PLMN as PCell
PLMN as an SCell.
• USE: Do not set the Cell that does not support the same PLMN as
PCell's PLMN as an SCell.
USE_MO_DATA_BARRING Whether to use ac-barringforMO-data as SCell configuration condition.
• Not_use: Set the Cell as an SCell regardless the SIB2 MO-data-barring
value.
• USE: Set the Cell as an SCell depending on SIB2 MO-data-barring
value. If SIB2 MO-data-barring value is 'use', Do not set the Cell as an
SCell. If it is no_use, set as an SCell.
SCELL_CHANGE_SUPPORT Shows whether Scell Change support function through SCell
Release/Add is operated for UEs that do not support FGI#111, when
operating in CA Mode4.
SBC_LIST_PRIORITY_USAGE SBC List can be used with Priority up to 3. This parameter designates
how many priorities can be used for CA.
• 1: Priority1_use: One SBC List can be used with Priority1.
• 2: Priority1_Priority2_use: Two SBC Lists can be used with Priority1
and Priority2.
• 3: Priority1_Priority2_Priority3_use: Three SBC Lists can be used with
Priority1, Priority2, Priority3.
OPERATOR_PREFERRED_UL_ This parameter is to define UL Band Value that gives the operator forced
OPERATOR_PREFERRED_UL_ This parameter is to define UL Band Value that gives the operator forced

MEAS_CYCLE_SCELL This parameter is the subframes for SCell.
Counters and KPIs


Confidential

Carrier Aggregation CaCapaPCellUE Number of CA capable UEs (PCell)
capable UEs(PCell)
CaUECapaEnquiryAdditionalSbc The number of sending
UECapabilityEnquiry message to get
additional SBC during Attach, Idle to
Active, Inter-eNB Handover, Re-
establishment procedures
CaUECapaInformationAdditionalSbc The number of receiving
UECapabilityInformation after sending
additional SBC during Attach, Idle to
Active, Inter-eNB Handover, Re-
Carrier Aggregation SCellAddAtt Scell Addition attempt count (SCell)
Message count for SCellAddSucc_RrcSig Number of successes in addition to co-
Addition/Release
located SCell or successes in SCell
addition by HO-in procedure (SCell)
SCellAddSucc_EventA4 Number of successes in SCell addition by
Event A4 (SCell)
SCellAddSucc_EventA6 Number of successes in SCell addition
(change) by Event A6 (SCell)
SCellAddSucc_RrcResetup Number of successes in addition to SCell
after RRC connection reestablishment
procedures (SCell)
SCellAddFail_RrcSigTO Number of fails in Scell addition by
released calls by RRC Connection
Reconfiguration T/O (SCell)
SCellAddFail_CaCapaCac Number of fails in SCell addition under
Carrier Aggregation Capability CAC
Procedure (SCell)
SCellAddFail_CpCcFail Number of fails in Scell Addition under
ECCB (Scell)
SCellAddFail_CpRrmFail Number of fails in Scell Addition due to
resource allocation failure (Scell)
SCellRel_RrcSig Number of times that SCell Release is
performed under the RRC connection
reestablishment procedures (SCell)
SCellRel_HoOut Number of times that SCell Release is
performed under the HO Out procedures
(SCell)
SCellRel_EventA2 Number of times that SCell Release is
performed by Event A2 (SCell)
SCellRel_EventA6 Number of times that SCell Release
(Change) is performed by Event A6 (SCell)
SCellRel_RrcResetup Number of times that SCell Release is
SCellRel_CaCac Number of times that SCell Release is
performed under the Carrier Aggregation
CAC (SCell)
SCellAddCnt_Avg The average number of SCell Added UEs.
SCellAddAtt_RrcSig The number of attempt to Add Scells

Confidential

during attach
SCellAddAtt_HoIn The number of attempt to add Scells
during Handover In
SCellAddAtt_EventA4 The number of attempt to add Scells
triggered by A4 Event MR
SCellAddAtt_EventA6 The number of attempt to add Scells
SCellAddAtt_RrcResetup The number of attempt to add Scells
triggered by
rrcConnectionReestablishment
SCellRel_SbcPriority The number of attempt to release existed
Scells because of adding new Scell of SBC
with high priority
SCellAddAtt_AddSbcRrcSig The number of attempt to Add Scells
during attach after getting additional SBC
SCellAddAtt_AddSbcHoIn The number of attempt to add Scells
during Handover In after getting additional
SBC
SCellAddAtt_AddSbcRrcResetup The number of attempt to add Scells
triggered by
rrcConnectionReestablishment after
getting additional SBC
SCellAddSucc_AddSbcRrcSig The number of success to add Scells
during attach after getting additional SBC
SCellAddSucc_AddSbcHoIn The number of success to add Scells
during Handover In after getting additional
SBC
SCellAddSucc_AddSbcRrcResetup The number of success to add Scells
triggered by
rrcConnectionReestablishment after
getting additional SBC
SCellRel_AddSbcRrcSig The number of attempt to release existent
Scells because of adding new Scells after
getting additional SBC during attach
procedure
SCellRel_AddSbcHoIn The number of attempt to release existent
getting additional SBC during Handover In
procedure
SCellRel_AddSbcRrcResetup The number of attempt to release existent
getting additional SBC during RRC
Reestablishment procedure
SCellAddAtt_AddSbcRrcSig The number of attempt to Add Scells
during attach
SCellRel_AddSbcHoIn The number of attempt to add Scells
during Handover In
SCellRel_AddSbcRrcResetup The number of attempt to add Scells
Carrier Aggregation SCellActivation Count of activations (SCell)
Message count for SCellDeactivation_TO Count of SCell deactivation occurrences by
Activation/Deactivation reason: When deactivation timer expires

Confidential

(SCell) (SCell)
SCellDeactivation_Mismatch Count of SCell deactivation occurrence by
reason: When CA status of eNB and that
of the UE are different (SCell)
CRNTIcollision The cumulated number of Scell Activation
fail due to C-RNTI collision (The C-RNTI of
UE, who requests Scell activation to SCell,
is already used in SCell)
SCellActUEAvg The average number of Scell activated UE
SCellActivationAtt The cumulated number of Scell Activation
Attempts.
SCellActFailCaCac The cumulated number of Scell Activation
Failures due to CA CAC Fail.
SCellActFailSCellSetupTimeOut The cumulated number of Scell Activation
Failures due to not receiving the response
to Scell Setup within predefined time from
eNB.
SCellActFailActMacCeResBler The cumulated number of Scell Activation
Failures due to that Residual BLER occurs
about Activation MAC CE Transmission.
Air MAC Packet (PCell) AirMacULByte The sum of the size of the MAC PDU
successfully received via PUSCH during
the statistics period
AirMacULByteCnt AirMacULByte collection count
AirMacULTti The sum of sections that have the MAC
PDU successfully received via PUSCH
during the statistics period
AirMacULThruAvg Average size per second of the MAC PDU
successfully received via PUSCH
AirMacULEfctivThruAvg Average size of the MAC PDU of the
section successfully received via PUSCH
AirMacDLByte The sum of the size of the DCCT/DTCH
MAC PDU that received HARQ ACK
among the MAC PDU transmitted via
PDSCH during the statistics period
AirMacDLByteCnt AirMacDLByte collection count
AirMacDLTti The sum of sections that have the MAC
PDU successfully transmitted via PDSCH
AirMacDLThruAvg Average size per second of the
DCCT/DTCH MAC PDU that received
HARQ ACK among the MAC PDU
transmitted via PDSCH during the statistics
period
AirMacDLEfctivThruAvg Average size of the MAC PDU of the
section successfully transmitted via
AirMacULByteCurr The most recently collected AirMacByteUl
value
AirMacDLByteCurr The most recently collected AirMacDLByte
value

Confidential

AirMacULThruMin Minimum of the average size per second of
the MAC PDU successfully received via
PUSCH
AirMacULThruMax Maximum of the average size per second
of the MAC PDU successfully received via
PUSCH
AirMacDLThruMin Minimum value of average size per second
of the DCCT/DTCH MAC PDU that
received HARQ ACK among the MAC
PDU transmitted via PDSCH during the
statistics period
AirMacDLThruMax Maximum value of average size per
second of the DCCT/DTCH MAC PDU that
statistics period
Air MAC Packet (SCell) AirMacULByte The sum of the size of the MAC PDU
successfully received via PUSCH during
AirMacULTti The sum of sections that have the MAC
PDU successfully received via PUSCH
during the statistics period.
successfully received via PUSCH.
AirMacULEfctivThruAvg Average size of the MAC PDU of the
section successfully received via PUSCH
AirMacDLByte The sum of the size of the DCCT/DTCH
MAC PDU that received HARQ ACK
among the MAC PDU transmitted via
AirMacDLTti The sum of sections that have the MAC
PDU successfully transmitted via PDSCH
AirMacDLThruAvg Average size per second of the
DCCT/DTCH MAC PDU that received
HARQ ACK among the MAC PDU
transmitted via PDSCH during the statistics
period
AirMacDLEfctivThruAvg Average size of the MAC PDU of the
section successfully transmitted via
value
value
PUSCH
AirMacULThruMax Maximum of the average size per second

Confidential

of the MAC PDU successfully received via
PUSCH
AirMacDLThruMin Minimum value of average size per second
of the DCCT/DTCH MAC PDU that
statistics period
AirMacDLThruMax Maximum value of average size per
second of the DCCT/DTCH MAC PDU that
statistics period
DL Wideband CQI (PCell) DLReceivedCQI0 Number of receiving CQI 0 for a wideband
CQI per layer/codeword transmitted from
CA UE whose the cell is PCell
DLReceivedCQI1 Number of receiving CQI 1 for a wideband
DLReceivedCQI10 Number of receiving CQI 10 for a
wideband CQI per layer/codeword
transmitted from CA UE whose the cell is
PCell
PCell

Confidential

PCell
PCell
PCell
PCell
DLReceivedCQIMin The minimum value of DlReceivedCQI
received from CA UE whose cell is PCell
DLReceivedCQIMax The maximum value of DlReceivedCQI
DLReceivedCQIAvg The average value of DlReceivedCQI
CQIErase Number of times that CQI erase per
layer/codeword is received from CA UE
whose cell is PCell
DL Wideband CQI (SCell) DLReceivedCQI0 Number of receiving CQI 0 for a wideband
CA UE whose the cell is SCell

Confidential

SCell
SCell
SCell
SCell
SCell
SCell
SCell
SCell
SCell
whose cell is SCell
CA UE per number of CC DL_1FD_SCC The average number of UEs that has one
of FDD DL carrier to SCell.
DL_1TD_SCC The average number of UEs that has one
of TDD DL carrier to SCell.
DL_2FD_SCC The average number of UEs that has two
of FDD DL carriers to SCell.
DL_2TD_SCC The average number of UEs that has two
of TDD DL carriers to SCell.
DL_1FD_1TD_SCC The average number of UEs that has one
of FDD DL carrier and one of TDD DL
carrier to SCell.
SCell Added Information No_DlCaCapabilityUe There is no CA capability corresponding to
(PCell) the supportedBandCombination
2CC_DlCaCapabilityUe CA capability corresponding to the
supportedBandCombination support 2
Component Carrier

Confidential

Component Carrier
2CC_ScellAdditionTime Total SCell Addition Time of 2 Component
Carrier
Carrier
Carrier Aggregation with Ca2CcDl4LayerPCell This counter is increased when all the
MIMO following conditions are met : 2CC CA, DL
4 layer MIMO service in only PCell.
Ca2CcDl4LayerSCell This counter is increased when all the
following conditions are met : 2CC CA, DL
4 layer MIMO service in only SCell.
Ca2CcDl4LayerPCellSCell This counter is increased when all the
4 layer MIMO service in both PCell and
SCell.
Ca3CcDl4LayerPCell This counter is increased when all the
4 layer MIMO service in only PCell.
Ca3CcDl4Layer1SCell This counter is increased when all the
4 layer MIMO service in only 1SCell.
Ca3CcDl4Layer2SCell This counter is increased when all the
4 layer MIMO service in only 2SCell.
Ca3CcDl4LayerPCell1SCell This counter is increased when all the
4 layer MIMO service in both PCell and
SCell.
Ca3CcDl4LayerPCell2SCell This counter is increased when all the
4 layer MIMO service in PCell and 2SCells.
Ca4CcDl4Layer_1Cell This counter is increased when all the
4 layer MIMO service in 1 SCell.
4 layer MIMO service in 2 SCells.
4 layer MIMO service in 1 SCell.

Confidential

Carrier Aggregation with Ca2CcDl4LayerPCell256QPCell This counter is increased when all the
MIMO and 256QAM following conditions are met : 2CC CA, DL
4 layer MIMO service in only PCell and
256 QAM services in only PCell.
Ca2CcDl4LayerSCell256QPCell This counter is increased when all the
4 layer MIMO service in only SCell and
256 QAM services in only PCell.
Ca2CcDl4LayerPCellSCell256QPCel This counter is increased when all the
l following conditions are met : 2CC CA, DL
4 layer MIMO service in both PCell
and SCell and 256 QAM services in only
PCell.
Ca2CcDl4LayerPCell256QSCell This counter is increased when all the
4 layer MIMO service in only PCell and
256 QAM services in only SCell.
Ca2CcDl4LayerSCell256QSCell This counter is increased when all the
256 QAM services in only SCell.
Ca2CcDl4LayerPCellSCell256QSCel This counter is increased when all the
and SCell and 256 QAM services in only
SCell.
Ca2CcDl4LayerPCell256QPCellSCel This counter is increased when all the
4 layer MIMO service in PCell and 256
QAM services in PCell and SCell
Ca2CcDl4LayerSCell256QPCellSCel This counter is increased when all the
256 QAM services in PCell and SCell.
Ca2CcDl4LayerPCellSCell256QPCel This counter is increased when all the
lSCell following conditions are met : 2CC CA, DL
and SCell and 256 QAM services
in PCell and SCell
Ca3CcDl4LayerPCell256QPCell This counter is increased when all the
QAM services in PCell
Ca3CcDl4Layer1SCell256QPCell This counter is increased when all the
4 layer MIMO service in one SCell and

Confidential

256 QAM services in PCell
Ca3CcDl4Layer2SCell256QPCell This counter is increased when all the
4 layer MIMO service in two SCells and
256 QAM services in PCell
Ca3CcDl4LayerPCell1SCell256QPC This counter is increased when all the
ell following conditions are met : 3CC CA, DL
4 layer MIMO service in PCell and one
SCell and 256 QAM services in PCell
4 layer MIMO service in PCell and two
SCells and 256 QAM services in PCell
Ca3CcDl4LayerPCell256Q1SCell This counter is increased when all the
QAM services in one SCell
Ca3CcDl4Layer1SCell256Q1SCell This counter is increased when all the
256 QAM services in one SCell
256 QAM services in one SCell
Ca3CcDl4LayerPCell1SCell256Q1S This counter is increased when all the
Cell following conditions are met : 3CC CA, DL
SCell and 256 QAM services in one
SCell
SCells and 256 QAM services in one
SCell
Ca3CcDl4LayerPCell256Q2SCell This counter is increased when all the
QAM services in two SCells
256 QAM services in two SCells
256 QAM services in two SCells
SCell and 256 QAM services in two
SCells

Confidential

SCells and 256 QAM services in two
SCells
Ca3CcDl4LayerPCell256QPCell1SC This counter is increased when all the
QAM services in PCell and one SCell
Ca3CcDl4Layer1SCell256QPCell1S This counter is increased when all the
256 QAM services in PCell and one SCell
256 QAM services in PCell and one SCell
ell1SCell following conditions are met : 3CC CA, DL
and one SCell
and one SCell
Ca3CcDl4LayerPCell256QPCell2SC This counter is increased when all the
QAM services in PCell and two SCells
256 QAM services in PCell and two
SCells
256 QAM services in PCell and two
SCells
and two SCells
and two SCells
Ca4CcDl4Layer256Q This counter is increased when all the
4 layer MIMO service in more than one
Cell and 256 QAM services in more than
one cell
Ca5CcDl4Layer256Q This counter is increased when all the

Confidential

4 layer MIMO service in more than one
Cell and 256 QAM services in more than
one cell
REFERENCE
Equipment (UE) radio transmissiox1n and reception

Confidential
LTE-SW5503, UL CA Call Control

INTRODUCTION
UL Carrier Aggregation (UL CA) is a LTE-Advanced feature that enhances the
UL peak throughput and sentiment quality of UE by allowing the UE to use two or
more UL carrier resources simultaneously. For this feature, eNB performs the
following functions:
• Selection of UL SCell
• Decision on the allowance of UL SCell configuration
• Delivery of the configuration of Multiple TA(Timing Advance) Group ID and
Timer for SCell
The basic call processing procedures such as UE Context Setup and Handover are
upgraded to support the aforementioned functions.
BENEFIT
• An operator can enhance the utilization of UL frequency resource and obtain
load balance effects for scheduling.
• The UE can improve UL throughput and reduce file upload delay.
DEPENDENCY
• HW dependency
o Support Channel Cards: See UL carrier aggregation bandwidth
combination features
• Related Radio Technology: E-UTRAN (LTE) LTE Rel.10 Carrier Aggregation
and LTE Rel.11 Carrier Aggregation Enhancement.
• Others: UE category 7, 10, and above
LIMITATION
None
SYSTEM IMPACT
capabilities.
LTE-SW5500 CA Call Control, LTE-SW5503 UL CA Call Control, and UL CA
bandwidth combination features, which are varied by operator and eNB
configuration, must be supported for carrier aggregation.

Confidential

UL Carrier Aggregation increases the system capacity for end-users by utilizing
the available spectrum resources effectively across the network.
Coverage
UL Carrier Aggregation allows end users to access the network through multiple
component carriers.
Interfaces
None
FEATURE DESCRIPTION
This section describes the UL SCell configuration and deconfiguration procedures.
UL SCell Configuration
For DL CA configured UE with UL CA capability, UL SCell can be selected from
DL SCells.
Figure below depicts the flow of UL SCell decision.
CA Capable UE
DL CA SCell
Decsion
UL CA DL CA
Capable UE? Configuration
NO Supported UL NO
# of DL Band
SCell > 1? Combination?
YES YES
UL SCell Selection
from DL SCells
DL & UL CA
Configuration
For CA UE with DL and UL CA Supported Band Combination capability, the

eNB performs DL CA SCell combination decision by LTE-SW5500 CA Call
Control
Among the selected DL SCells, eNB performs UL SCell selection with the criteria
below

Confidential
• Co-located configuration with PCell

• Supported UL Band Combination of eNB
SCell UL De-configuration
Since UL CA function is supported only for the SCell that has Co-located
configuration with PCell, SCell UL de-configuration will be caused by SCell
Change operation in CA Operation Mode 3 & 4. Measurement report based SCell
UL de-configuration can be triggered if the RSRP measurement of UE is lower
than configured threshold.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CACELL-INFO and set CA_AVAILABLE_TYPE to DL_and_UL.
• Run CHG-CACELL-INFO and set CA_AVAILABLE_TYPE to CA_OFF or
DL_only.
Key Parameters
maximum capacity provided to the carrier per system is 1 FA/3 Sector, up

Confidential
to 3 cells are supported.
MAX_UL_CA_CC_NUM The maximum number of carriers to support Uplink Carrier Aggregation
ulScellCarrierChangeUsage This parameter indicates whether to support UL SCell Carrier Change.
• 0: no_use
• 1: use
ulScellCarrierChangeUsage This parameter indicates A1 offset for UL SCell Carrier Change. This offset
is applied to non-UL SCell carrier.

STATUS This parameter indicates whether to use Band Combination List.
BAND0_USAGE This parameter indicates whether to use Band Combination of BandEutra0
BAND0_FOR_UL_USAGE This Parameter indicates whether to use BandIndicator2 for UL CA.
When SupportedBandCombination-r10 in UE-EUTRA-Capability includes
band parameter, which consists of bandIndicator0 and
CA Band
CA Band.
caBandwidthClassUl2. This parameter can be selected PCELL Band or UL
CA Band.

Confidential

SCC_SELECTION_PRIORITY1 This parameter is used to provide priority to SCC Selection. When a high
priority condition is chosen and there is more than one SCC that meets the
condition, the SCC selection is determined by the condition specified in this
parameter. An option that is chosen in high priority must not be chosen
again, except for the option Not_use.
becomes the condition for SCC selection. The SCC with the least amount
of UE after BW normalization is chosen.
• operator_specific: This option exists to provide the operator forced
priority. OPERATOR_PREFERRED_BAND is selected as SCC.
• not_use: Does not provide additional priority to SCC selection.
SCC_SELECTION_PRIORITY2 This parameter is used to provide priority to SCC Selection. When a high
priority condition is chosen and there is more than one SCC that meets the
condition, the SCC selection is determined by the condition specified in this
parameter. An option that is chosen in high priority must not be chosen
again, except for the option Not_use.
becomes the condition for SCC selection. The SCC with the least amount
of UE after BW normalization is chosen.
• operator_specific: This option exists to provide the operator forced
priority. OPERATOR_PREFERRED_BAND is selected as SCC.
• not_use: Does not provide additional priority to SCC selection.
OPERATOR_PREFERRED_UL This parameter is to define UL Band Value that provides the operator
_BAND1 forced priority for SCC selection. The selected Band value is valid if the
value of sccSelectionPriority1 equals operator_specific.
OPERATOR_PREFERRED_UL This parameter is to define UL Band Value that provides the operator
_BAND2 forced priority for SCC selection. The selected Band value is valid if the
value of sccSelectionPriority2 equals operator_specific.
Parameter Descriptions of CHG-ULCA-SCHED/RTRV-ULCA-SCHED

CELL_NUM The cell number for which the command was executed.
MULTIPLE_TA_SUPPORT This parameter determines multiple TA support
Counters and KPIs

Counters and KPIs are the same as DL CA (see LTE-SW5500 CA Call Control).
Table below outlines the UL CA-specific counters associated with this feature.
UL CA Information ULCaCapaPCellUEAvg Average UL CA Capable UE count (PCell)

Confidential

Uplink Carrier Aggregation ULSCellConfigByAdd Number of UL SCell Configuration by SCell
Count for Configuration- Addition
Deconfiguration
ULSCellConfigBySccCha Number of UL SCell Configuration by SCell
nge Event A1
ULSCellDeconfigBySccC Number of UL SCell deconfiguration by SCell
hange Event A1
ULSCellConfigByEventA Number of UL SCell Configuration by SCell
6 Event A6
ULSCellDeconfigByEvent Number of UL SCell deconfiguration by SCell
A6 Event A6
REFERENCE

Confidential
LTE-SW5505, Inter-eNB Carrier Aggregation

INTRODUCTION
Carrier Aggregation (CA), introduced in 3GPP LTE Rel-10 as a fundamental
technology of LTE Advanced, is a technique that extends bandwidth by
aggregating more than two Component Carriers (CCs) to achieve high data rate
transmission. CCs may belong to different eNBs, which are located at the same
sites.
Samsung eNB provides an Inter-eNB CA feature to expand CA benefits between
collocated eNBs connected with ideal backhaul.
BENEFIT
This feature expands CA benefits between different eNBs.
DEPENDENCY
• Related Radio Technology: E-UTRAN(LTE)
• Others: CA capable UE supporting band combinations
LIMITATION
• The eNBs should be collocated and inter-connected by optic cable directly or
via Inter-Baseband Switch.
• The same SW version is required at all eNBs in a CA cluster.
• Dedicated configuration for inter-connection between eNBs is applied.
• For Inter-eNB CA, the eNB has its own iNodeID to distinguish each other
(e.g. 0, 1, 2, 3, ...). The iNodeIDs in a CA group should be four consecutive
numbers.
SYSTEM IMPACT
capabilities.
For carrier aggregation, the operation mode and the system configuration are
performed by using LTE-SW5500, CA Call Control feature and LTE-ME5010,
Best Cell Aggregation. For the configuration associated with this feature, see LTE-
SW5500 and LTE-ME5010 features.

Confidential
and detailed information on counters associated with this feature, see LTE-SW5500
and LTE-ME5010 features.
Coverage
Interfaces
None
FEATURE DESCRIPTION
CA enables operators to maximally utilize their available spectrum, increases data
rates, and improves user experience.
Samsung eNB supports various CA configurations, such as intra or inter-channel
card. As the number of frequencies increases, the CA component carriers may be
served by different eNBs. All CA features (for example, LTE-SW5500, CA Call
Control and LTE-ME5010, Best Cell Aggregation) require interworking operation
between primary cell (PCell) and secondary cells (SCell) to exchange scheduling
information and user’s feedback. To maximize CA performance, PCells and
SCells should be configured within an eNB or between collocated eNBs with real-
time inter-connection.
This feature enables CA between collocated eNBs connected with ideal backhaul.
Direct links or Inter-Baseband Switch (IBS) can be used for inter-connection
between eNBs. For C-RAN, IBS enables BBU clustering that in turn enables the
expansion of CA cluster area.
Figure below depicts the inter-eNB CA configuration for C-RAN site.
Figure below depicts the inter-eNB CA configuration for D-RAN site.

Confidential
SYSTEM OPERATION
How to Activate
Precondition
• Run CHG-CACELL-INFO and set CA_AVAILABLE_TYPE to DL_Only to
enable Carrier Aggregation.
• Run CHG-CAGROUP-INFO and set the ENB_CA_USAGE to Active to
enable Inter Carrier Aggregation.
• Run CHG-CACELL-INFO and set CA_AVAILABLE_TYPE to CA_OFF to
disable Carrier Aggregation.
• Run CHG-CAGROUP-INFO and set the ENB_CA_USAGE to Inactive to
disable Inter Carrier Aggregation.
Key Parameters
parameters.
Parameter Descriptions of CHG- CACELL-INFO/RTRV-CACELL-INFO
CA_AVAILABLE_TYPE This parameter indicates whether to support CA.
• CA_OFF

Confidential
• DL_only
• DL_and_UL
Parameter Descriptions of CHG-CAGROUPSH-INFO/RTRV-CAGROUPSH-INFO

ENB_CA_USAGE Whether to use eNB which is matched to iNode ID in CA Group.
parameters.
Parameter Descriptions of CHG-CAGROUPCO-INFO/RTRV-CAGROUPCO-INFO
CA_GROUP_SETUP_REQT_COUNT The retry count for the CA Group Setup procedure when
Communication Failure status occurs after sending the Ca Group
Setup Request.
PERIOD_CA_GROUP_SETUP The time to wait for a response after sending the CA Group
Setup Request message to other eNB in CA Group.
SCELL_CONFIG_RESP_WAIT_TIME The time to wait for a Scell Configuration Response message
after sending the Scell Configuration Request message.
SCELL_CONFIG_COMMON_WAIT_TIME The time to wait for a Scell Configuration Commit message after
sending the Scell Configuration Response message.
parameters.
cells supported by the system. It is determined by FA/Sector. For
example, if the maximum capacity provided to the carrier per system is
1 FA/3 Sector, up to 3 cells are supported.
P_CELL_ONLY_FLAG This parameter indicates whether to support only P Cell.
MAX_DL_CA_CC_NUM The maximum number of carriers to support Downlink Carrier
Aggregation.
MAX_UL_CA_CC_NUM The maximum number of carriers to support Uplink Carrier Aggregation.
CA_OPERATION_MODE CA Operation mode.
• Mode1: Pcell and Scell are collocated and the Scell is added during
initial attachment.
• Mode2: Pcell and Scell are collocated and initial attachment will try
Scell addition. If Scell is not found, Scell will be released.
• Mode3: Pcell and Scell are collocated and Scell is added based on
MR (measurement report).
• Mode4: SCell is changed by measurement about SCC

Confidential
Parameter Descriptions of CHG-CASCHED-INF/RTRV-CASCHED-INF

SCHEDULABILITY_UNIT This parameter is the CA schedulability unit. It indicates the range of
SCells for CA in the eNB.
• IntraEnb: Selects SCells in the same eNB.
• caGroup: Selects SCells in the CA Group.
Parameter Descriptions of CHG-CA-COLOC/RTRV-CA-COLOC

STATUS This parameter indicates whether the tuple information is valid.
COLOCATED_CELL_NUM This parameter is the number of the cells in the same eNB that are co-
located with CELL_NUM. This parameter is the input range is the
maximum number of the cells that the system supports. In case of
Mode1, 2, the cells specified as COLOCATED_CELL_NUM become the
Scell targets.
S_CELL_DEACTIVATION_TIMER This parameter is the waiting time until a Scell is deactivated by MAC.
This parameter is the value set to a UE if one or more Scell are operating
during CA operation. It is recommended to use a default value. Be careful
when setting the value because the Scell Deactivation time becomes long
if the timer value is large.

BAND0_USAGE This parameter indicates whether to use Band Combination of
BandEutra0 and caBandwidthClassDl0
BAND0_FOR_UL_USAGE This Parameter indicates whether to use BandIndicator0 for UL
CA.
When SupportedBandCombination-r10 in UE-EUTRA-Capability
includes band parameter which consists of bandIndicator0 and
caBandwidthClassUl0, This parameter can be selected PCELL
Band or UL CA Band
BAND1_FOR_UL_USAGE This parameter indicates whether to use BandIndicator1 for UL
CA.

Confidential
Band or UL CA Band.
BAND2_FOR_UL_USAGE This parameter indicates whether to use BandIndicator2 for UL
CA.
Band or UL CA Band.

SCC_SELECTION_PRIORITY1 This parameter is used to give priority to SCC Selection. When
a high priority condition is chosen and there is more than one
SCC that meets the condition, the SCC selection is determined
by the condition specified in this parameter. An option that is
chosen in high priority should not be chosen again, except for
the option 'Not_use'.
• Size_of_BW: The size of BW becomes the condition for SCC
selection. The SCC with bigger BW is chosen.
• CAC: CAC stands for Composite Available Capacity. The
SCC with greater CAC is chosen.
• number_of_UE_with_BW: The number of UE with BW
consideration becomes the condition for SCC selection. The
SCC with the least amount of UE after BW normalization is
chosen.
• operator_specific: This option exists to give the operator
forced priority. OPERATOR_PREFERRED_BAND will be
chose as SCC.
OPERATOR_PREFERRED_DL_BAND1 This parameter is to define Band Value that gives the operator
forced priority for SCC selection. The selected Band value is
valid if the value of sccSelectionPriority1 equals
operator_specific.
the option Not_use.
chosen.

Confidential
chose as SCC.
operator_specific.
the option Not_use.
chosen.
chose as SCC.
'operator_specific'.
SCC_PLMN_SELECTION This parameter is used to control SCell configuration capability
for Cells that do not support the same PLMN as PCell's PLMN.
• Not_use: Set the Cell that does not support the same PLMN
as PCell's PLMN as an SCell.
• USE: Do not set the Cell that does not support the same
PLMN as PCell's PLMN as an SCell.
USE_MO_DATA_BARRING Whether to use ac-barringforMO-data as SCell configuration
condition.
• Not_use: Set the Cell as the SCell regardless the SIB2 MO-
data-barring value.
• USE: Set the Cell as the SCell depending on SIB2 MO-data-
barring value. If SIB2 MO-data-barring value is use, Do not
set the Cell as an SCell . If it is no_use, set as the SCell.
SCELL_CHANGE_SUPPORT Shows whether or not Scell Change support function through
SCell Release/Add is operated for UEs that do not support
FGI#111, when operating in CA Mode4.
SBC_LIST_PRIORITY_USAGE SBC List can be used with Priority up to 3. This parameter
designates how many priorities can be used for CA.
• 1: Priority1_use: One SBC List can be used with Priority1.
• 2: Priority1_Priority2_use: Two SBC Lists can be used with
Priority1 and Priority2.
• 3: Priority1_Priority2_Priority3_use: Three SBC Lists can be
used with Priority1, Priority2, Priority3.
OPERATOR_PREFERRED_UL_BAND1 This parameter is to define UL Band Value that gives the
operator forced priority for SCC selection. The selected Band

Confidential
value is valid if the value of sccSelectionPriority1 equals
OPERATOR_PREFERRED_UL_BAND2 This parameter is to define UL Band Value that gives the
operator forced priority for SCC selection. The selected Band
value is valid if the value of sccSelectionPriority2 equals

MEAS_CYCLE_SCELL This parameter is the subframes for SCell.
Counters and KPIs

Table below outlines the main counters associated with this feature
Carrier Aggregation CaCapaPCellUE Number of CA capable UEs (PCell)
capable UEs(PCell)
CaUECapaEnquiryAdditionalSbc The number of sending UECapabilityEnquiry
message to get additional SBC during Attach,
Idle to Active, Inter-eNB Handover, Re-
CaUECapaInformationAdditionalSbc The number of receiving
UECapabilityInformation after sending
additional SBC during Attach, Idle to Active,
Inter-eNB Handover, Re-establishment
procedures
Carrier Aggregation SCellAddAtt Scell Addition attempt count (SCell)
Messagecount for SCellAddSucc_RrcSig Number of successes in addition to co-located
Addition/Release
SCell or successes in SCell addition by HO-in
procedure (SCell)
SCellAddSucc_EventA4 Number of successes in SCell addition by
Event A4 (SCell)
SCellAddSucc_EventA6 Number of successes in SCell addition
(change) by Event A6 (SCell)
SCellAddSucc_RrcResetup Number of successes in addition to SCell after
RRC connection reestablishment procedures
(SCell)
SCellAddFail_RrcSigTO Number of fails in Scell addition by released
calls by RRC Connection Reconfiguration T/O
(SCell)
SCellAddFail_CaCapaCac Number of fails in SCell addition under Carrier
Aggregation Capability CAC Procedure
(SCell)
SCellAddFail_CpCcFail Number of fails in Scell Addition under ECCB
(Scell)
SCellAddFail_CpRrmFail Number of fails in Scell Addition due to
resource allocation failure (Scell)
SCellRel_RrcSig Number of times that SCell Release is

Confidential

SCellRel_HoOut Number of times that SCell Release is
performed under the HO Out procedures
(SCell)
SCellRel_EventA2 Number of times that SCell Release is
performed by Event A2 (SCell)
SCellRel_EventA6 Number of times that SCell Release (Change)
is performed by Event A6 (SCell)
SCellRel_RrcResetup Number of times that SCell Release is
SCellRel_CaCac Number of times that SCell Release is
performed under the Carrier Aggregation CAC
(SCell)
SCellAddCnt_Avg The average number of SCell Added UEs.
SCellAddAtt_RrcSig The number of attempt to Add Scells during
attach
SCellAddAtt_HoIn The number of attempt to add Scells during
Handover In
SCellAddAtt_EventA4 The number of attempt to add Scells triggered
by A4 Event MR
SCellAddAtt_EventA6 The number of attempt to add Scells triggered
by A6 Event MR
SCellAddAtt_RrcResetup The number of attempt to add Scells triggered
by rrcConnectionReestablishment
SCellRel_SbcPriority The number of attempt to release existed
Scells because of adding new Scell of SBC
with high priority
SCellAddAtt_AddSbcRrcSig The number of attempt to Add Scells during
attach after getting additional SBC
SCellAddAtt_AddSbcHoIn The number of attempt to add Scells during
Handover In after getting additional SBC
SCellAddAtt_AddSbcRrcResetup The number of attempt to add Scells triggered
by rrcConnectionReestablishment after getting
additional SBC
SCellAddSucc_AddSbcRrcSig The number of success to add Scells during
attach after getting additional SBC
SCellAddSucc_AddSbcHoIn The number of success to add Scells during
Handover In after getting additional SBC
SCellAddSucc_AddSbcRrcResetup The number of success to add Scells
triggered by rrcConnectionReestablishment
after getting additional SBC
SCellRel_AddSbcRrcSig The number of attempt to release existent
getting additional SBC during attach
procedure
SCellRel_AddSbcHoIn The number of attempt to release existent
getting additional SBC during Handover In
procedure
SCellRel_AddSbcRrcResetup The number of attempt to release existent

Confidential

getting additional SBC during RRC
Reestablishment procedure
SCellAddAtt_AddSbcRrcSig The number of attempt to Add Scells during
attach
SCellRel_AddSbcHoIn The number of attempt to add Scells during
Handover In
SCellRel_AddSbcRrcResetup The number of attempt to add Scells triggered
by A4 Event MR
Carrier Aggregation SCellActivation Count of activations (SCell)
Message count for SCellDeactivation_TO Count of SCell deactivation occurrences by
Activation/Deactivation reason: When deactivation timer expires
(SCell)
(SCell)
SCellDeactivation_Mismatch Count of SCell deactivation occurrence by
reason: When CA status of eNB and that of
the UE are different (SCell)
CRNTIcollision The cumulated number of Scell Activation fail
due to C-RNTI collision (The C-RNTI of UE,
who requests Scell activation to SCell, is
already used in SCell)
SCellActUEAvg The average number of Scell activated UE
SCellActivationAtt The cumulated number of Scell Activation
Attempts.
SCellActFailCaCac The cumulated number of Scell Activation
Failures due to CA CAC Fail.
SCellActFailSCellSetupTimeOut The cumulated number of Scell Activation
Failures due to not receiving the response to
Scell Setup within predefined time from eNB.
SCellActFailActMacCeResBler The cumulated number of Scell Activation
Failures due to that Residual BLER occurs
about Activation MAC CE Transmission.
Air MAC Packet AirMacULByte The sum of the size of the MAC PDU
(PCell) successfully received via PUSCH during the
statistics period
AirMacULTti The sum of sections that have the MAC PDU
successfully received via PUSCH during the
statistics period
successfully received via PUSCH
AirMacULEfctivThruAvg Average size of the MAC PDU of the section
statistics period
AirMacDLByte The sum of the size of the DCCT/DTCH MAC
PDU that received HARQ ACK among the
MAC PDU transmitted via PDSCH during the
statistics period
AirMacDLTti The sum of sections that have the MAC PDU
successfully transmitted via PDSCH during

Confidential

AirMacDLThruAvg Average size per second of the DCCT/DTCH
MAC PDU that received HARQ ACK among
the MAC PDU transmitted via PDSCH during
AirMacDLEfctivThruAvg Average size of the MAC PDU of the section
value
value
PUSCH
AirMacULThruMax Maximum of the average size per second of
PUSCH
AirMacDLThruMin Minimum value of average size per second of
the DCCT/DTCH MAC PDU that received
HARQ ACK among the MAC PDU transmitted
via PDSCH during the statistics period
AirMacDLThruMax Maximum value of average size per second of
Air MAC Packet AirMacULByte The sum of the size of the MAC PDU
(SCell) successfully received via PUSCH during the
statistics period
AirMacULTti The sum of sections that have the MAC PDU
statistics period.
successfully received via PUSCH.
AirMacULEfctivThruAvg Average size of the MAC PDU of the section
statistics period
AirMacDLByte The sum of the size of the DCCT/DTCH MAC
PDU that received HARQ ACK among the
MAC PDU transmitted via PDSCH during the
statistics period
AirMacDLTti The sum of sections that have the MAC PDU
AirMacDLThruAvg Average size per second of the DCCT/DTCH
MAC PDU that received HARQ ACK among
the MAC PDU transmitted via PDSCH during
AirMacDLEfctivThruAvg Average size of the MAC PDU of the section

Confidential

value
value
PUSCH
AirMacULThruMax Maximum of the average size per second of
PUSCH
AirMacDLThruMin Minimum value of average size per second of
AirMacDLThruMax Maximum value of average size per second of
DL Wideband CQI DLReceivedCQI0 Number of receiving CQI 0 for a wideband
(PCell) CQI per layer/codeword transmitted from CA
UE whose the cell is PCell
CQI per layer/codeword transmitted from CA

Confidential

whose cell is PCell
DL Wideband CQI DLReceivedCQI0 Number of receiving CQI 0 for a wideband
(SCell) CQI per layer/codeword transmitted from CA
UE whose the cell is SCell

Confidential

SCell
SCell
SCell
whose cell is SCell
CA UE per number of DL_1FD_SCC The average number of UEs that has one of
CC FDD DL carrier to SCell.
DL_1TD_SCC The average number of UEs that has one of
TDD DL carrier to SCell.
DL_2FD_SCC The average number of UEs that has two of
FDD DL carriers to SCell.
DL_2TD_SCC The average number of UEs that has two of
TDD DL carriers to SCell.
DL_1FD_1TD_SCC The average number of UEs that has one of
FDD DL carrier and one of TDD DL carrier to
SCell.
SCell Added No_DlCaCapabilityUe There is no CA capability corresponding to the
Information (PCell) supportedBandCombination
Component Carrier
Component Carrier
Carrier

Confidential

Carrier
REFERENCE
[1] 3GPP TS 36.101 ‘E-UTRA; User Equipment (UE) radio transmission and
reception’
[2] 3GPP TS 36.211 ‘E-UTRA; Physical Channels and Modulation’
[3] 3GPP TS 36.212 ‘E-UTRA; Multiplexing and channel coding’
[4] 3GPP TS 36.213 ‘E-UTRA; Physical layer procedures’
[5] 3GPP TS 36.300 ‘E-UTRA and Evolved Universal Terrestrial Radio Access
Network (E-UTRAN); Overall description; Stage 2’
[6] 3GPP TS 36.331 ‘E-UTRA; Radio Resource Control (RRC); Protocol
specification’
[7] 3GPP TR 36.814 ‘E-UTRA; Further advancements for E-UTRA physical layer
aspects’
(LTE-Advanced)’

Confidential
LTE-SW6301, NB-IoT Call Control Support

INTRODUCTION
Samsung eNB supports Narrow Band - IoT (NB-IoT) defined in 3GPP Rel13. This
feature supports basic call control procedures including signaling procedures and
user data transmission based on Control Plane optimization or User Plane
optimization.
BENEFIT
An operator can launch an IoT service through NB-IoT technology providing:
• 20 dB coverage gains compared to GPRS
• Long UE battery life
• Massive UE connections
DEPENDENCY
• HW dependency
o Support Channel Cards: NB-IoT capacity varies depending on the DU and
RU types. Some old DU and RU cannot support this feature.
• Required Network Elements: MME C-SGN
• Related Radio Technology: E-UTRAN (LTE) NB-IoT
• Others: NB-IoT UE (Cat-NB1) is required
LIMITATION
Single NB-IoT carrier is supported.
SYSTEM IMPACT
capabilities.
None
None
Coverage
According to the deployment area of NB-IoT cells and the NB-IoT PRB position,
NB-IoT UL signal can be potential interference sources to LTE within LTE
channel bandwidth.

Confidential
Interfaces
None
FEATURE DESCRIPTION
3GPP Rel.13 NB-IoT supports new low cost/low power NB-IoT UEs. NB-IoT
provides 20dB coverage gain compared to GPRS, long UE battery life and massive
UE connections. Various IoT services, such as smart meters, remote system
monitoring, and asset tracking can be supported by NB-IoT solution.
This feature supports basic NB-IoT call control functions.
MIB-NB and SIB-NBs Support

For NB-IoT, new system information messages are defined, as outlined in table
below.
Message Description Supported Release
• Most essential information of the cell required to Current
receive further system information.
MasterInformationBlock-NB
• Uses a fixed schedule with a periodicity of 640
ms and repetitions made within 640 ms
• Cell access/selection, other SIB scheduling Current
- Uses a fixed schedule with a periodicity of
SystemInformationBlockType1- 2560 ms
NB
• Configures the SI-window length and the
transmission periodicity for all SI messages
SystemInformationBlockType2- Current
Radio resource configuration information
NB
SystemInformationBlockType3- Cell re-selection information for intra-frequency, Current
NB inter-frequency
SystemInformationBlockType4- Neighboring cell related information relevant for Current
NB intra-frequency cell re-selection
SystemInformationBlockType5- Neighboring cell related information relevant for Current
NB inter-frequency cell re-selection
• Access barring Current
SystemInformationBlockType14-
NB • Change of Access Barring (AB) parameters can
occur at any point in time
SystemInformationBlockType16- GPS time and Coordinated Universal Time (UTC) Current
NB information
Category NB1 (Cat.NB1 and NB-IoT UE) Support

Cat.NB1 is a low cost device such as IoT (=Internet of Things) sensor and Half
Duplex FDD Type B single-Rx.
There are two types of power class of Cat.NB1 UE such as:
• Rel.13 LTE Cat.NB1 power class 3 (23dBm)
• Rel.13 LTE Cat.NB1 power class 5 (20dBm)

Confidential
NB-IoT RRC and S1 Procedure Support

In NB-IoT, during the RRC connection establishment procedure, SRB1bis is
established implicitly with SRB1. SRB1bis uses the logical channel identity with
the same configuration as SRB1 but no PDCP entity.
An NB-IoT UE that only supports the Control Plane CIoT EPS optimization (see
TS 24.301) only establishes SRB1bis. SRB1bis is used until security is activated.
A NB-IoT UE that only supports the Control Plane CIoT EPS optimization does
not need to support any DRBs and associated procedures. The NB-IoT UE only
supports 0, 1 or 2 DRBs, depending on its capability.
The following procedures are supported for NB-IoT.
Paging
Figure below depicts the procedure used for transmitting paging information to the
UE in RRC_IDLE.
RRC Connection Establishment

Figure below depicts the procedure used for establishing an RRC connection. The
RRC connection establishment involves SRB1 and SRB1bis establishment.
This procedure is also used to transfer the initial NAS dedicated

information/message from the UE to the E-UTRAN.
Figure below depicts the procedure used for releasing the RRC connection,

Confidential
including release of the established radio bearers as well as all radio resources.
Radio Link Failure-related Actions

The NB-IoT UE detects a radio link failure by T310 expiry, the UE perform the
actions upon leaving the RRC_CONNECTED state.
DL Information Transfer
Figure below depicts the procedure used for transferring NAS or tunneled non-
3GPP dedicated information from E-UTRAN to the UE in the
UL Information Transfer
Figure below depicts the procedure used for transferring NAS or tunneled non-
3GPP dedicated information from UE to the E-UTRAN in the
UE Capability Transfer
Figure below depicts the procedure used for transferring UE radio access
capability information from UE to the E-UTRAN.

Confidential

The purpose of this procedure is to set up/modify/release the radio configuration
for controlling the connected UE. The RRC connection reconfiguration procedure
is used in various situations to set up the call, to add the DRB, to change the radio
resource configuration, to change the security context, and so on. This procedure is
related to UP Optimization case only.

The purpose of this procedure is to re-setup the RRC connection. This procedure is
triggered upon detecting Radio Link Failure (RLF), integrity check failure from
lower layers and upon RRC Connection Reconfiguration failure.
The RRC connection reestablishment procedure helps to re-establish the SRB1
operation and re-activate the Security Algorithms (Security Algorithms are not
changed). This procedure is successful when eNB has a valid UE Context. If eNB
does not have a UE context, then UE moves to RRC IDLE state.
This procedure is related to UP optimization case only in Rel.13.

Confidential
Control Plane Operation Support

CP optimization utilizes RRC and S1 Application Protocol (S1AP) signaling
connections for small user data transfer without data bearer setup to reduce the
number of control messages.
The user plane data is transferred via Non Access Stratum (NAS) transport
capabilities of RRC connection and S1AP connection to MME. And then, the
MME relays the user plane data to Serving Gateway (S-GW) via newly defined
S11 bearer, as depicted in figure below.
For more details, see LTE-SW0531, Control Plane Optimization Support feature.
User Plane Operation support

RRC connections and S1 associations can be suspended while keeping necessary
contexts in UE, eNB, and MME. Later, the suspended RRC connections and S1
associations can be resumed utilizing the stored contexts through reduced
signaling procedure.

Confidential
NB-IoT Access Barring and Cell Barring

This section describes the NB-IoT Access Barring and Cell Barring functions.
NB-IoT Access Barring
For NB-IoT, if the UE is establishing mobile originating data, mobile originating
signaling, or mobile originating ExceptionData, the UE performs access barring
check upon initiation of the procedure.
If access to the cell is barred, the UE informs upper layers about the failure to
establish the RRC connection while access barring is applicable.
The access-barring parameters for NB-IoT are contained in the SIB14-NB and
MIB-NB (CHG-NBEAB-PARAM).
The NB-IoT UE checks an ab-Enabled indication in the MasterInformationBlock-
NB to know whether access barring is enabled. If access barring is enabled, the UE
does not initiate the RRC connection establishment until the UE has a valid
version of SIB14-NB.
The conditions for SIB14-NB transmission consist of the automatic mode and the
manual mode (setting made by the operator). The automatic mode is triggered with
SIB14-NB transmission based on CPU Overload.
NB-IoT Cell Barring
The cell-barring parameters for NB-IoT are contained in the SIB1-NB (CHG-
NBCELL-ACS).
• cellBarred (IE type: barred or not barred): In case of multiple PLMNs
indicated in SIB1-NB, this field is common for all PLMNs
• cellReservedForOperatorUse (IE type: reserved or not reserved): In case of
multiple PLMNs indicated in SIB1-NB, this field is specified per PLMN.
NB-IoT Call Admission Control Support

The Call Admission Control (CAC) function is enabled to efficiently use the

Confidential
limited radio resources and to protect eNB system from being overloaded.
The capacity-based CAC makes a decision based on the capacity that operator
configures in advance. It allows an incoming call as long as the total number of
calls does not exceed the pre-configured thresholds.
The operator can configure the separated thresholds per the establishment cause of
RRC connection request, per PLMN, per cell, or per eNB (CHG-NBCELLPLMN-
CAC, CHG-NBCELL-CAC, and CHG-NBENB-CAC).
NB-IoT Cell Selection/Reselection Support

This section describes the NB-IoT cell selection and reselection functions.
Cell Selection
The cell selection is performed on the detected cell with RX signal and decoded
MIB-NB and SIB-NBs.
Cell selection criteria:
Srxlev > 0 AND Squal > 0
Where:
• Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation - Qoffsettemp
• Squal = Qqualmeas - Qqualmin - Qoffsettemp
Table below outlines the parameters of the cell selection criteria.
Parameter Name Description
Srxlev Cell selection RX level value (dB)
Squal Cell selection quality value (dB)
Qoffsettemp Offset temporarily applied to a cell (dB)
Qrxlevmeas Measured cell RX level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qrxelvmin Minimum required RX level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
Pcompensation max (PEMAX-PPowerClass, 0) (dB)
PEMAX Maximum TX power level the UE can use when transmitting on the uplink
in the cell (dBm) defined as P_MAX in [TS 36.101]
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power
class
Cell Reselection
When a cell reselection condition is met, the UE in idle mode attempts to detect,
synchronize, and read system information of candidate frequencies. The UE
performs only the cell reselection evaluation for NB-IoT frequencies that are
provided in system information.
When evaluating Srxlev and Squal of non-serving cells for reselection, the UE uses
parameters provided by the serving cell.
The following rules are used by the UE to limit required measurements:

Confidential
• If the serving cell fulfils Srxlev > SIntraSearchP, the UE can choose not to perform
intra-frequency measurements. Otherwise, the UE performs intra-frequency
measurements.
• The UE applies the following rules for the NB-IoT inter-frequencies that are
indicated in system information:
o If the serving cell fulfils Srxlev > SnonIntraSearchP, the UE can choose not to
perform inter-frequency measurements. Otherwise, the UE performs inter-
frequency measurements.
The following criteria are for the intra-frequency and equal priority inter-
frequency cell reselection. The cell-ranking criterion Rs for serving cell and Rn for
neighboring cells is defined by:
• Rs = Qmeas,s + QHyst
• Rn = Qmeas,n - Qoffset
Where:
o Rs: Used for the serving cell.
o Rn: Used for the neighbor cell.
o Qmeas: RSRP measurement quantity used in cell reselections.
o Qoffset: For intra-frequency, equals to Qoffsets,n, if Qoffsets,n is valid,
otherwise this equals to zero. For inter-frequency, equals to Qoffsets,n plus
Qoffsetfrequency, if Qoffsets,n is valid, otherwise, and for NB-IoT, this equals
to Qoffsetfrequency.
o QHyst: This parameter (in dB) is used to reduce ping-pong effects between
the serving and the neighbor cells.
The UE performs ranking of all cells that fulfil the cell selection criterion S,
however, can exclude all CSG cells that are known by the UE not to be CSG
member cells.
The cells are ranked according to the R criteria specified above, deriving Qmeas,n
and Qmeas,s and calculating the R values using averaged RSRP results.
If the cell is ranked as the best cell, the UE performs cell reselection to that cell. In
all cases, the UE reselects the new cell only if the following conditions are met:
• The new cell is better ranked than the serving cell during a time interval
Treselection
• More than 1 s has elapsed since the UE camped on the current serving cell
NB-IoT EARFCN and NB-IoT carrierFreqOffset Configuration

The carrier frequency of Cat.NB1 in the downlink is designated by the E-UTRA
Absolute Radio Frequency Channel Number (EARFCN) and the carrierFreqOffset
in the range {-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, -0.5, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9}. If
the downlink carrier is the anchor, then available carrierFreqOffsets are {-2, -1, 0,
1}.
The following is the carrier center frequency of the Cat.NB1 in the downlink (=

Confidential
FDL, NB-IoT):
FDL, NB-IoT = FDL_low + 0.1 (NDL, NB-IoT - NOffs-DL) + 0.0025 * (2MDL + 1)
Where:
• FDL_low: The lowest frequency of the downlink operating band
• NDL, NB-IoT: NB-IoT downlink EARFCN
• NDL, LTE: LTE downlink EARFCN
• NOffs-DL: Offset used for calculating the downlink EARFCN
• MDL: NB-IoT downlink carrierFreqOffsets
The carrier frequency of the Cat.NB1 in the uplink is designated by the EARFCN
and the carrierFreqOffset in the range {-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 0, 1, 2,
3, 4, 5, 6, 7, 8, 9}.
The following is the carrier center frequency of the Cat.NB1 in the uplink (= FUL,
NB-IoT):
FUL,NB-IoT = FUL_low + 0.1 (NUL, NB-IoT-NOffs-UL) + 0.002 5 * (2MUL)

Where:
• FUL_low: The lowest frequency of the uplink operating band
• NUL, NB-IoT: NB-IoT uplink EARFCN
• NUL, LTE: LTE uplink EARFCN
• NOffs-UL: Offset used for calculating uplink EARFCN
• MUL: NB-IoT uplink carrierFreqOffsets
NB-IoT Center Frequency for Guard-band Mode

According to the NB-IoT center frequency rule, Samsung supports the following
candidate downlink distances between LTE center frequency and NB-IoT center
frequency (DDL) in Guard-band mode:
LTE 10 MHz Case
• Candidate DDL = + 4.5975 MHz <=> NDL, NB-IoT = NDL, LTE + 46, NOffs-DL = -1 (=
vN1)
• Candidate DDL = - 4.5975 MHz <=> NDL, NB-IoT = NDL, LTE - 46, NOffs-DL = 0 (=
v0)
• Candidate DDL = + 4.7025 MHz <=> NDL, NB-IoT = NDL, LTE + 47, NOffs-DL = 0 (=
v0)
• Candidate DDL = - 4.7025 MHz <=> NDL, NB-IoT = NDL, LTE - 47, NOffs-DL = -1 (=
vN1)
According to the NB-IoT center frequency rule, Samsung supports the following
candidate uplink distances between LTE center frequency and NB-IoT center
frequency (DUL) in Guard-band mode:

Confidential
LTE 10 MHz Case

• Candidate DUL = + 4.590 MHz <=> NUL, NB-IoT = NUL, LTE + 46, NOffs-UL = -2 (=
vN2)
• Candidate DUL = - 4.590 MHz <=> NUL, NB-IoT = NUL, LTE - 46, NOffs-UL = 2 (=
vP2)
• Candidate DUL = + 4.620 MHz <=> NUL, NB-IoT = NUL, LTE + 46, NOffs-UL = 4 (=
vP4)
• Candidate DUL = - 4.620 MHz <=> NUL, NB-IoT = NUL, LTE - 46, NOffs-UL = -4 (=
vN4)
• Candidate DUL = + 4.635 MHz <=> NUL, NB-IoT = NUL, LTE + 46, NOffs-UL = 7 (=
vP7)
• Candidate DUL = - 4.635 MHz <=> NUL, NB-IoT = NUL, LTE - 46, NOffs-UL = -7 (=
vN7)
• Candidate DUL = + 4.665 MHz <=> NUL, NB-IoT = NUL, LTE + 47, NOffs-UL = -7 (=
vN7)
• Candidate DUL = - 4.665 MHz <=> NUL, NB-IoT = NUL, LTE - 47, NOffs-UL = 7 (=
vP7)
SYSTEM OPERATION
This feature controls calls for supporting NB-IoT and does not have activation or
deactivation.
REFERENCE
[1] TS36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Universal Terrestrial Radio Access Network (E-UTRAN); Overall description;
Stage 2
[2] TS36.304 Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) procedures in idle mode
[4] TS36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
[5] TS36.401 Evolved Universal Terrestrial Radio Access Network (E-UTRAN);
Architecture description
S1 general aspects and principles

Confidential
LTE-SW6311, Paging Optimization for Low

Complexity and Coverage Enhanced UE
INTRODUCTION
To support paging for NB-IoT or eMTC devices, paging mechanism needs to be
enhanced to distinguish between paging to legacy UE and paging to NB-IoT or
eMTC UE. To support coverage enhanced NB-IoT or eMTC UEs and reduce
signaling load by paging, the number of NPDCCH or MPDCCH repetition for the
paging needs to be determined optimally. Furthermore, paging area can be
optimized for the paging signaling load reduction.
BENEFIT
Signaling load by paging can be reduced.
DEPENDENCY
• HW dependency: NB-IoT or eMTC supported channel cards.
• Prerequisite Features: LTE-SW6301, NB-IoT Call Control Support or
LTE-SV1500, eMTC
• Others: NB-IoT or eMTC UEs
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
By the configuration parameters of the feature, an operator can adjust tradeoff
between paging success ratio and paging signaling load.
Coverage
Coverage enhanced UEs such as eMTC or NB-IoT can receive paging message via
this feature.
Interfaces
S1 Interface: IEs for paging optimization are added to the S1 messages.

Confidential
FEATURE DESCRIPTION
This feature supports the following three optimizations:
• Paging channel selection for low complexity UE (PDCCH for LTE UE,
MPDCCH for eMTC UE, and NPDCCH for NB-IoT UE)
• The number of NPDCCH or MPDCCH repetition decisions for coverage
enhanced UE
• Paging area selection for low mobility UE
For the paging optimization, the eNB provides information for paging to MME
when UE goes to idle. Using this information from the eNB, the MME provides
assistance information to eNB in paging message, as depicted in figure below.
The following are the information sent from eNB to MME in the UE context
release complete message:
• Recommended cells and eNBs for paging area decision.
• Cell ID and coverage level of previously connected cell for the decision of the
number of NPDCCH or MPDCCH repetition for paging.
The following are the assistance information sent from MME to eNB in paging
message:
• UE radio capability for the selection of physical channel for paging, that is,
PDCCH for the legacy UE, NPDCCH for the NB-IoT UE, MPDCCH for the
eMTC UE. The MME obtains this information from eNB at UE radio
capability enquire procedure.
• Recommended cells and eNBs for paging area decision.
• Cell ID and coverage level of previously connected cell for the decision of the
number of NPDCCH or MPDCCH repetition for the paging.
• Information on paging attempt for the optimal decision of the number of
NPDCCH or MPDCCH repetitions for the paging.
Using this received assistance information from MME in the paging message, the
eNB decides physical channel, the number of NPDCCH or MPDCCH repetition,
and paging area optimally as follows.

Confidential
Paging Channel Selection for Low Complexity UEs

The eNB selects the paging channel based on the UE Radio Capability for Paging
IE in the paging message from MME. If the IE indicates m1, the eNB uses
MPDCCH for paging (eMTC UE). If it indicates nb1, the eNB uses NPDCCH for
paging (NB-IoT UE). When the UE Radio Capability for Paging IE is missing or
there is no m1 or nb1 indication, the eNB uses PDCCH for paging (LTE UE).
NPDCCH or MPDCCH Repetition Decision for Coverage Enhanced UEs]

The eNB can decide the number of NPDCCH/MPDCCH repetition based on
received Assistance Data for Paging IE from MME and operator's configuration as
follows:
• Start repetition
o If paging to the last connected cell, the eNB uses last used number of
repetition in Assistance Data for CE capable UEs IE in paging message.
o If paging to other cells, the eNB uses operator-configured start number of
repetition (PAGING_REPETITION_OPTION by using CHG-BRDLREP-
CONF).
• Transition to maximum repetitions
o If paging attempt count in Assistance Data for CE capable UEs IE in
paging is the same or bigger than operator-configured
PAGING_ATT_CNT_TO_SELECT_MAX_MPDCCH/PAGING_ATT_CNT
_TO_SELECT_MAX_NPDCCH (CHG-EMTCPAGINGOPENB-
INFO/CHG-NBPAGINGOPENB-INFO), the eNB uses configured
maximum number of repetitions for subsequent paging
(PAGING_REPETITION_OPTION by using CHG-BRDLREP-CONF).
o If the configured PAGING_ATT_CNT_TO_SELECT_MAX_MPDCCH is
greater than received Intended Number of Paging Attempts IE in the
paging message, the eNB uses configured maximum number of repetitions
at the last paging attempt.

Confidential
Figure below depicts an example of NPDCCN/MPDCCH repetition decision.
# of M/NPDCCH repetition
MME Configurable max.
repetition
example example
Previously configuration configuration
connected cell 1 2
1st paging: Previously
used # of repetitions
Configurable start
subsequent pagings: repetition
Paging
increased # of repetitions attempts
1st 2nd 3rd Final attempt
attempt attempt attempt
Paging Area Selection for Low Mobility UEs]

The eNB selects the paging area based on received Assistance Data for Paging IE
from MME and operator's configuration as follows:
• Start paging area: Start paging area can be configured by
START_PAGING_AREA_CONF using CHG-EMTCPAGINGOPENB-
INFO/CHG-NBPAGINGOPENB-INFO.
o Paging to receive last connected cell
o Paging to receive recommended cells: Recommended cells can be
configured by RECOMMENDED_CELL_NUM_1/2/3 using CHG-
EMTCPAGINGOPCELL-INF/CHG-NBPAGINGOPCELL-INF.
o Paging based on received TAIs
• Transition to paging to TAIs
o If paging attempt count in received Assistance Data for CE capable UEs IE
in paging is the same or bigger than the operator-configured
PAGING_ATT_CNT_TO_SELECT_TAIS (CHG-EMTCPAGINGOPENB-
INFO/CHG-NBPAGINGOPENB-INFO), the eNB pages based on received
TAIs.
o If the configured PAGING_ATT_CNT_TO_SELECT_TAIS is greater
than received Intended Number of Paging Attempts IE in paging message,
the eNB pages based on received TAIs at the last paging attempt.

Confidential
Figure below depicts an example of paging area selection.
MME
Example configuration
paging to recommended eNBs first:
up to MME’s policy Paging Example Example
attempt configuration 1 configuration 2
1st paging recommended cells
1st attempt Last connected cell + last connected cell
Other cell: TA1 Recommended
cell: TA1 recommended cells
2nd attempt Cells in target TA + last connected cell
last connected Subsequent
attempts Cells in target TA Cells in target TA
cell: TA1
1st paging
SYSTEM OPERATION
How to Activate
Key Parameters
There are no specific parameters associated with this feature
parameters.
Parameter Descriptions of CHG-EMTCPAGINGOPCELL-INF/RTRV-
EMTCPAGINGOPCELL-INF
CELL_NUM This parameter is the cell number to identify each cell. This value must not
RECOMMENDED_CELL_NUM_1 This parameter is cell number to select recommended cell in same eNB
related Paging Optimization feature.
This value must not exceed the maximum number of cells supported by
the system. If this parameter is -1, then this is not valid.

Confidential
Parameter Descriptions of CHG-EMTCPAGINGOPENB-INFO/RTRV-

EMTCPAGINGOPENB-INFO
DB_INDEX DB index
PAGING_ATT_CNT_TO_SELEC This parameter is Paging Attempt Count received from MME. This
T_MAX_MPDCCH parameter decides to transmit maximum MPDCCH Repetition Number.
This parameter decides to transmit MAX MPDCCH when Paging Attempt
Count received from MME is greater than this parameter.
T_TAIS parameter is to decide when to send Paging to UE based on TAI.
For example, If this parameter is 2, then eNB send Paging to UE based on
TAI when Paging Attempt Count in received from MME is greater than 2
regardless PagingCellSelectionMode.
START_PAGING_AREA_CONF This parameter is to configure Mode to decide selecting Target Cell
according to Paging Attempt Count when receiving Paging from MME
(refer to 3GPP 36.413).
• Paging_Area_Mode1: The eNB send Paging message to UE based on
previous connected cell. If the Message from MME does not include
previous connected cell, the eNB sends the Paging message to UE
based on TAIs.
• Paging_Area_Mode2: The eNB send Paging message to UE based on
recommended cells in S1 Paging Message from MME. If the Message
from MME does not include recommended cells, the eNB sends the
Paging message to UE based on TAIs.
• Paging_Area_Mode3: The eNB send the Paging message to UE based
on TAIs in S1 Paging message.
Parameter Descriptions of CHG-NBPAGINGOPCELL-INF/RTRV-

NBPAGINGOPCELL-INF

Confidential
Parameter Descriptions of CHG-NBPAGINGOPENB-INF/RTRV-

NBPAGINGOPENB-INF
DB_INDEX DB index
T_MAX_NPDCCH parameter decide to transmit maximum NPDCCH Repetition Number
This parameter decides to transmit MAX NPDCCH when Paging Attempt
Count received from MME is greater than this parameter.
T_TAIS parameter is to decide when to send Paging to UE based on TAI.
For example, If this parameter is 2, then the eNB sends the Paging to UE
based on TAI when Paging Attempt Count in received from MME is
greater than ‘2’ regardless PagingCellSelectionMode
START_PAGING_AREA_CONF This parameter is to configure Mode to decide selecting Target Cell
according to Paging Attempt Count when receiving Paging from MME
(refer to 3GPP 36.413)
• Paging_Area_Mode1: The eNB sends the Paging message to UE based
on previous connected cell. If the Message from MME does not include
previous connected cell, the eNB sends the Paging message to UE
based on TAIs.
• Paging_Area_Mode2 : The eNB send Paging message to UE based on
recommended cells in S1 Paging Message from MME. If the Message
from MME does not include Recommended cells, the eNB sends the
Paging message to UE based on TAIs.
• Paging_Area_Mode3: The eNB sends the Paging message to UE based
on TAIs in S1 Paging Message.
Parameter Descriptions of CHG-BRDLREP-CONF/RTRV-BRDLREP-CONF

PAGING_REPETITION_OPTION This parameter configures the number of repetition for paging MPDCCH.
• ci_Option0: start repetition = 1, max repetition = 1
Counters and KPIs

with this feature.

Confidential
REFERENCE

Confidential
Chapter 3 Load Control
LTE-SW2001, Intra-LTE Mobility Load Balancing

INTRODUCTION
Samsung intra-LTE MLB (Mobility Load Balancing) enables an eNB to release
the overload of a cell or to maintain the cell load difference between the co-located
inter-frequency cells within the range set by an operator.
For intra-LTE MLB, the eNB periodically monitors the cell load status of its own
cells and neighbor cells. If the served cell’s load reaches the threshold value, the
eNB relocates some selected UEs from a higher-loaded cell to lower-loaded
neighbor cells.
BENEFIT
• By distributing traffic over multiple carriers, good QoS can be provided for
each carrier.
• The Quality of Experience (QoE) can be improved.
DEPENDENCY
• Interface and Protocols:
o X2 Interface: The eNBs should support X2 Resource Status Reporting so
that the cell-load information can be exchanged between neighbor cells via
the X2 interface.
• Others:
o UE capability: Only UEs that support multiple carriers in the operator
network are selected as candidates for load balancing between carriers.
o Co-existence with Smart SON Tx Power Control (LTE-SO2021): It is
recommended that A3 measurement for intra-frequency MLB is turned off
since Smart SON TPC periodically modifies the DL Tx power for load
balancing between intra-frequency cells.
LIMITATION
Conditions for Load Equalization: Load equalization is available only when the
inter-frequency co-located neighbor cell supports a carrier of the same carrier
group and its attribute isColocated in NRT is set to true.

Confidential
SYSTEM IMPACT
capabilities.
None
Performance
Intra-LTE MLB feature performs gradual reduction of overload traffic by moving
configured rate of UEs to neighbors every period (configurable: a few second).
The amount offloaded traffic at each period can be adjusted by configuring related
parameters (RATE_LB_CANDIDATE and RATE_LB_TARGET).
Coverage
Intra-LTE MLB feature uses the dedicated A3/A4 event parameter setting for
MLB. The thresholds such as a3Offset and a4ThresholdRSRP (/RSRQ) can affect
the area where MLB-triggered HOs occur.
Interfaces
None
FEATURE DESCRIPTION
This section describes various methods supported by Samsung eNB for load
balancing.
Intra-LTE MLB Functions and Carrier Grouping

Samsung Intra-LTE MLB feature works based on carrier groups. Carriers must be
configured into one or more carrier groups based on the operator radio spectrum
management policy. For example, the operator can group a few lower frequency
carriers as the VoLTE-preferred carriers or the operator can group a few carriers
for RAN sharing with other operator. In these cases, the carriers for a specific
purpose need to be configured into a same carrier group.
This feature consists of the following three types of load balancing functions,
which can be enabled or disabled at the cell level:
• Load equalization within intra-group carriers
(LOAD_EQUALIZATION_ENABLE (CHG-TM-CNTR))
The purpose of this function is to maintain the cell load difference between a
source cell and a co-located inter-frequency neighbor cell within the
configured threshold level. Only the co-located neighbor cells of the same
carrier group are candidate cells for this function.
• Offloading to intra-group carriers (INTRA_GROUP_OFFLOAD_ENABLE
(CHG-TM-CNTR))
The purpose of this function is to reduce a source cell load by using lower-
loaded intra-frequency and inter-frequency neighbor cells that belong to the
same carrier group.

Confidential
• Offloading to inter-group carriers (INTER_GROUP_OFFLOADING_ENABLE

(CHG-TM-CNTR))
The purpose of this function is to reduce a source cell load by using lower-
loaded inter-frequency neighbor cells that belong to a different carrier group.
Figure below depicts the three types of intra-LTE MLB functions that can be
activated according to the load level of the source cell. Load equalization within
intra-group carriers is inactivated when offloading to intra-group carriers is
activated. However, offloading to intra-group carriers still work when offloading
to inter-group carriers is activated.
Figure below depicts an example of how intra-LTE MLB functions offload UEs to
neighbor cells based on carrier grouping.

Confidential
Procedure of Intra-LTE MLB Functions

Figure below depicts the brief procedure of intra-LTE MLB.
• When any of the intra-LTE MLB functions is turned on, the eNB monitors the
load levels of its cells and neighbor cells periodically.
• If a source cell exceeds a configured threshold for one of the intra-LTE MLB
functions, the corresponding intra-LTE MLB function is activated. However,
load equalization within intra-group carriers is activated only if the cell load
difference between the source cell and its co-located inter-frequency cell also
exceeds a configured level.
• The eNB selects a configured rate of candidate UEs randomly and configures
measurements for the purpose of load balancing.
• After the eNB collects measurement reports from candidate UEs, it selects the
configured rate of target UEs to be moved to target cells. Pairs of (target UE,
target cell) are selected based on the target cell load and reported signal
strength.
• The eNB performs handovers of the target UEs to the target cells.
Figure below shows the call flow of intra-LTE MLB. The details for each step are
described in the following sub-sections.

Confidential
Cell Load Monitoring

When any of the intra-LTE MLB functions for a source cell is turned on, the eNB
monitors the load levels of the source cell and its neighbor cells periodically. The
eNB monitors the source cell load with the period of T_LOAD_DECISION_LB
(CHG-ACTIVE-LB) and neighbor cells’ load with the period of
T_RESOURCE_STATUS_REPORTING (CHG-ACTIVE-LB).
If only load equalization within intra-group carriers is turned on, the source cell
selects the intra-group inter-frequency neighbors, which have the attribute
IS_COLOCATED (CHG-NBR-EUTRAN) set to TRUE. When offloading to intra-
group carriers or offloading to inter-group carriers is turned on and the source cell
has no existing cell load report from neighbor cells, the eNB selects the:
• Configured number (NUM_OF_NR_FOR_ACTIVE_LB (CHG-ACTIVE-LB))
of high-ranked neighbor cells in each carrier
• Co-located inter-frequency neighbors in the intra-group.

Confidential
If there is any existing cell load report from at least one neighbor cell, then the
process of selecting neighbors are performed at the next ANR ranking period. The
neighbors are ranked based on the number of HO successes in the period of
RANK_PERIOD (CHG-SON-ANR).
To monitor the load of the selected inter-eNB neighbor cells, the eNB uses X2
Resource Status Reporting procedure. A source eNB sends X2 Resource Status
Request message to a neighbor eNB to which a selected neighbor cell belongs. The
X2 Resource Status Request message includes the following information:
• Report Characteristic IE: Samsung eNB requests the Composite Available
Capacity Group IE so that it can estimate a neighbor cell load from the DL/UL
Capacity Value IEs (as described in Cell Load Metric).
• Reporting Periodicity IE: The Reporting Periodicity IE is determined by the
T_RESOURCE_STATUS_REPORTING (CHG-ACTIVE-LB).
When the neighbor eNB receives the X2 Resource Status Request message and
can report the Composite Available Capacity Group IE, it does the following:
• Sends the X2 Resource Status Response message.
• Reports the cell load information periodically by using the X2 Resource Status
Update message.
Decision on MLB Activation
Three types of intra-LTE MLB functions are activated by different threshold
levels:
• Load equalization within intra-group carriers
The load equalization is activated if the source cell load exceeds
EQUAL_THRESHOLD(k) (k = 0, 1, 2, 3) (CHG-LBCELL-CONF) and the cell
load difference between the source cell and its co-located intra-group inter-
frequency neighbor cell exceeds EQUAL_DELTA(k) (k = 0, 1, 2, 3) (CHG-
LBCELL-CONF).
The co-located inter-group inter-frequency neighbor is not considered for load

equalization.
The number of levels for load equalization can be controlled from 1 to 4 by
setting NUM_EQUAL_STEP. The following relations must be maintained
irrespective of NUM_EQUAL_STEP (CHG-LBCELL-CONF) when changing
the thresholds below:
o EQUAL_THRESHOLD0 ≤ EQUAL_THRESHOLD1 ≤
EQUAL_THRESHOLD2 ≤ EQUAL_THRESHOLD3 ≤
INTRA_GROUP_OFFLOAD_THRESHOLD [Inequation 1]
o EQUAL_DELTA3 ≤ EQUAL_ DELTA2 ≤ EQUAL_ DELTA1 ≤
EQUAL_DELTA0 [Inequation 2]
Figure below depicts an example of how the values are set in load
equalization. Since both the source cell load and the load difference at the
point A exceed the configured thresholds, the load equalization is activated. In
this example, point A is moved to the point B by the action of load

Confidential
equalization. At point B, the source cell load exceeds the

EQUAL_THRESHOLD0 (CHG-LBCELL-CONF), however, the load difference
does not exceed the EQUAL_DELTA0 (CHG-LBCELL-CONF). Therefore, the
load equalization is not activated.
• Offloading to intra-group carriers

Offloading to intra-group carriers is activated if the source cell load exceeds
INTRA_GROUP_OFFLOAD_THRESHOLD (CHG-LBCELL-CONF).
• Offloading to inter-group carriers
To enable offloading to the n-th carrier group, both

Confidential
INTER_GROUP_OFFLOADING_ ENABLE (CHG-TM-CNTR) for the source

cell and OFFLOADING_TO_THIS_INTER_GROUP_ENABLE (CHG-
LBGRPCELL-CONF) at the n-th carrier group in the source eNB need to be set
to ON.
When multiple carrier groups are configured, the threshold for offloading to a
specific carrier group from any other can be set separately. Offloading to the
n-th carrier group is activated if the source cell load exceeds
INTER_GROUP_OFFLOADING_THRESHOLD (CHG-LBGRPCELL-CONF)
at the n-th carrier group.
Configuring Measurements for Candidate UEs
The eNB selects the candidate cell based on the activated MLB function. These are
the selection procedures:
• Load equalization within intra-group carriers: A co-located intra-group inter-
frequency cell, which meets the cell load difference condition, is determined as
a candidate cell.
• Offloading to intra-group carriers: An intra-group intra-/inter-frequency
neighbor cell, whose cell load is less than [source cell load-
DELTA_OFFLOAD_THRESHOLD], is determined as a candidate cell
(DELTA_OFFLOAD_THRESHOLD can be configured by CHG-LBCELL-
CONF). A co-located intra-group inter-frequency neighbor cell is also included
for offloading to intra-group carriers.
• Offloading to inter-group carriers: An inter-group inter-frequency neighbor
cell, whose cell load is less than [source cell load-
DELTA_OFFLOAD_THRESHOLD] and serves a frequency of the n-th carrier
group, is determined as a candidate cell.
If USE_TRAFFIC_PER_UE (CHG-CELL-CAC) is set to USE, the source cell
selects UEs with higher downlink PRB usage grade as candidate UEs up to the
configured rate (RATE_LB_CANDIDATE (CHG-LBCELL-CONF)). In this case,
UEs are periodically graded according to their downlink per-UE PRB usage.
Otherwise, the source cell randomly selects candidate UEs up to the configured
rate. The source cell provides them the measurement configuration on the
frequencies of the candidate cells, through the RRC Connection Reconfiguration
message. It starts the timer (T_MEASUREMENT_COLLECTION_LB (CHG-
ACTIVE-LB)) for collecting measurement reports. If the source cell receives
measurement reports from all the candidate UEs or the timer expires, then it starts
selecting (target UE, target cell) pairs.
UEs with CA capability can be selected as the candidate UE if they are not SCell-
activated. If CA_UE_CANDIDATE_FLAG (CHG-ACTIVE-LB) is Ci_ON, a
SCell-activated UE can be selected as the candidate UE.
For the intra-frequency measurement, the event A3 with the purpose index
CI_A3PURPOSE_INTRA_FREQUENCY_LB (CHG-EUTRA-A3CNF) is
configured. To get the region for intra-frequency MLB, A3OFFSET (CHG-
EUTRA-A3CNF) for the MLB HO purpose should be set to less than the normal
intra-frequency HO purpose. For the inter-frequency measurement, the event A4

Confidential
with the purpose index CI_A4PURPOSE_INTER_FREQUENCY_LB (CHG-

EUTRA-A4CNF) is configured.
When the Measurement Report is received from the UE and the reported strongest
neighbor in a frequency is one of the candidate cells, the pair of the UE and the
strongest neighbor cell can be the candidate pair for load-balancing handover.
Selecting {target UE, target cell} Pairs
The eNB selects the strongest pairs, target UE, and cell, among the candidate pairs.
To do this, the eNB uses the following methods:
• Selects the candidate cell with the lowest cell load among the reported
strongest neighbors for each candidate UE.
• Selects {target UE, target cell} pairs until the ratio of the selected target UEs
to the RRC connected UEs approaches the configured rate
(RATE_LB_TARGET (CHG-LBCELL-CONF)) with the criterion of the lowest
cell load.
After selecting {target UE, target cell} pairs, the source eNB performs X2
handover procedure, where the Cause IE in the X2 Handover Request message is
set to Reduce Load in Serving Cell.
Figure below depicts how the {target UE, target cell} pairs are selected.
Blind Mode in Offloading to Inter-group Carriers

In offloading to inter-group carriers, if
OFFLADING_TO_THIS_INTER_GROUP_ENABLE (CHG-LBGRPCELL-
CONF) at the n-th carrier group is set to LB_BLIND, the source eNB does not send
the X2 Resource Status Request messages to the inter-eNB neighbors at the
carriers of the n-th carrier group. The source eNB uses source cell load-
DELTA_OFFLOAD_THRESHOLD -1 as the fixed cell load for these neighbors.
The other procedure is same as that described above.
When the candidate UE reports multiple carriers of the n-th carrier group and it is
selected as the target UE, its target cell is selected in a stochastic manner. The

Confidential
probability of the target carrier is proportional to the corresponding

CELL_CAPACITY_CLASS_VALUE_DL_PER_FA (CHG-EUTRA-FA).
Call Admission Control on Load-based HO

When the target eNB receives the X2 Handover Request message with the Cause
IE set to Reduce Load in Serving Cell, it sends the X2 Handover Request
Acknowledge message. This message is sent only if the requested target cell load
is smaller than TARGET_CELL_LOAD_THRESHOLD (CHG-LBCELL-CONF).
Otherwise, the target eNB sends the X2 Handover Preparation Failure message.
Cell Load Metric

Samsung intra-LTE MLB feature provides two modes for cell load evaluation:
• LOAD_PRB mode: Only DL and UL PRB usages are factored in cell load
evaluation.
• LOAD_TOTAL mode: The DL and UL PRB usages, CPU usage, backhaul
usage, and the number of RRC connected UEs are factored in cell load
evaluation.
The cell load for the time window index i is given by:
The DL and UL bar{Load_{total}}(i) for the time window index i are updated
respectively every PRB_REPORT_PERIOD (CHG-CELL-CAC) by an exponential
moving average as follows.
Here, alpha is the filtering coefficient and Load^{*}_{mode}(i) is calculated

according to the selected cell load evaluation mode.
The eNB checks whether the source cell load exceeds a configured threshold for
one of enabled intra-LTE MLB functions with the period of T_LOAD_
DECISION_LB (CHG-ACTIVE-LB) while it updates the source cell load every
PRB_REPORT_PERIOD (CHG-CELL-CAC).
LOAD_PRB Mode
When LOAD_EVALUATE_MODE (CHG-ACTIVE-LB) is set to LOAD_PRB,
Load^{*}_{mode}(i) is evaluated as follows. In this mode, DL and UL
Load^{*}_{mode}(i) are equal to DL and UL PRB load Load_{PRB}(i)
respectively.
DL and UL PRB load are evaluated as:
The loads due to control channels and GBR bearers are calculated as the control
PRB usage and the GBR PRB usage as follows:

Confidential
The load due to non-GBR bearers is calculated as:
Here, the non-GBR bearers load QCI=q, Load_{NGBR, q} is calculated as:

For q = 5, 6,.., 9,
Where:
• min {a, b} indicates the minimum between a and b.
• CBR_{q} is the configured bit rate for a non-GBR QCI=q bearer (configurable
parameter: CONFIGURED_BIT_RATE (CHG-QCI-VAL)). Here, the
configured bit rate can be set to the expected average bit rate for a non-GBR
QCI=q bearer.
• W indicates the time window length (= 1 sec).
• N_{q}(i) is the number of active bearers during the time window index i.
• w_{q} is the weight factor for the non-GBR QCI=q (configurable parameter:
WEIGHT_FOR_CELL_LOAD (CHG-QCI-VAL)).
For the other non-GBR QCIs (q=10, 11, …),
To reduce the computational load of DSP, the load formula for the other non-GBR
QCIs is simplified.
The padding PRB usage indicates the percentage of the PRBs which include only
the padding bits. It is calculated as follows.
The load due to padding PRB usage is calculated as:
Where:
• estimated_PRB_{padding, GBR} indicates the estimated padding PRB usage
caused by GBR bearers, and is calculated as follows.
• estimated_PRB_{padding, NGBR} indicates the estimated padding PRB usage

Confidential
caused by non-GBR bearers, and is calculated as follows:
LOAD_TOTAL Mode
When LOAD_EVALUATE_MODE (CHG-ACTIVE-LB) is set to LOAD_TOTAL,
DL and UL Load^{*}_{mode}(i) are evaluated as:
Where:
• max {a, b} indicates the maximum between a and b.
• intraGroupOffloadThreshold indicates
INTRA_GROUP_OFFLOAD_THRESHOLD (CHG-LBCELL-CONF), which is
the threshold for offloading to intra-group carriers.
• Condition A is met if one of these conditions is true:
o (C1): The number of RRC_Connected_UEs in a serving cell exceeds the
configured threshold (CAPACITY_LB_ALPHA_FACTOR ×
MAX_CALL_COUNT; CAPACITY_LB_ALPHA_FACTOR can be
configured by CHG-ACTIVE-LB and MAX_CALL_COUNT indicates the
maximum number of allowed calls per cell.)
o (C2): The CPU load exceeds the configured threshold (CPU_THRESHOLD

(CHG-ACTIVE-LB))
o (C3): The backhaul load exceeds the configured threshold. In other words,
the assignable backhaul capacity is less than the configured threshold
(MIN_BACK_HUAL_CAPACITY (CHG-ACTIVE-LB)).
o (C4): The PDCCH usage exceeds the configured threshold

(PDCCH_THRESHOLD (CHG-LBCELL-CONF)).
Capacity Value
DL and UL capacity values indicate the DL and UL Capacity Value IEs of
Composite Available Capacity IE in X2 Resource Status Update message.
The DL or UL capacity value is evaluated as:

Confidential
Cell Load Difference

Cell load difference in load equalization is calculated as:
Here, the cell load of a neighbor cell is given by:
SYSTEM OPERATION
How to Activate
Preconditions
You can operate MLB choosing single or multiple functions among
LOAD_EQUALIZATION_ENABLE, INTRA_GROUPOFF_LOAD_ENABLE, and
INTER_GROUPOFF_LOADING_ENABLE.
• Run CHG-LBGRP-CONF/RTRV-LBGRP-CONF to configure carrier groups.
• Run CHG-ACTIVE-LB/RTRV-ACTIVE-LB to set the related parameters.
• Run CHG-LBGRP-CONF/RTRV-LBGRP-CONF to configure
OFFLADING_TO_THIS_INTER_GROUP_ENABLE and
INTER_GROUP_OFFLOADING_THRESHOLD for offloading to inter-group
carriers.
• Run CHG-NBR-EUTRAN/RTRV-NBR-EUTRAN to configure
IS_COLOCATED of the co-located inter-frequency neighbor for load
equalization within intra-carrier group.
• Run CHG-TM-CNTR/RTRV-TM-CNTR to enable the selected intra-LTE MLB
functions: LOAD_EQUALIZATION_ENABLE,
INTRA_GROUPOFF_LOAD_ENABLE, and
INTER_GROUPOFF_LOADING_ENABLE to ON. For offloading to the n-th
inter-group carriers, OFFLADING_TO_THIS_INTER_GROUP_ENABLE at
the n-th carrier group is also set to lb_ON.
To deactivate this feature, run CHG-TM-CNTR and set
LOAD_EQUALIZATION_ENABLE, INTRA_GROUPOFF_LOAD_ENABLE, and

Confidential
INTER_GROUPOFF_LOADING_ENABLE to OFF
Key Parameters
parameters.
Parameter Descriptions of CHG-TM-CNTR/RTRV-TM-CNTR
LOAD_EQUALIZATION_ENA This parameter configures whether to execute the LOAD_EQUALIZATION
BLE function.
INTRA_GROUP_OFFLOAD_ This parameter configures whether to execute the
ENABLE INTRA_GROUP_OFFLOADING function.
INTER_GROUP_OFFLOAD_ This parameter configures whether to execute the
ENABLE INTER_GROUP_OFFLOADING function.
parameters.
Parameter Descriptions of CHG-LBGRP-CONF/RTRV-LBGRP-CONF
GRP_FA0 This parameter configures the EARCFN_DL value of a carrier in this carrier
group ID. If it is not configured, enter 0.
Parameter Descriptions of CHG-LBGRPCELL-CONF/RTRV-LBGRPCELL-CONF

OFFLADING_TO_THIS_INTE This parameter decides whether enabling or disabling
R_GROUP_ENABLE INTER_GROUP_OFFLOADING to the FA group that belongs to a specific
group ID.
INTER_GROUP_OFFLOADIN This parameter configures threshold of serving cell load to perform
G_THRESHOLD INTER_GROUP_OFFLOADING to a FA group belong to the group ID.

Confidential
Parameter Descriptions of CHG-NBR-EUTRAN/RTRV-NBR-EUTRAN

IS_COLOCATED This parameter indicates whether the neighbor cell covers most of the
physically identical region.
Counters and KPIs

LOAD LoadIndicatorAvg Average load of a cell when overload occurs due to
the MLB operation.
LoadIndicatorMin Minimum load of a cell when overload occurs due
to the MLB operation.
LoadIndicatorMax Maximum load of a cell when overload occurs due
to the MLB operation.
LoadIndicatorTot Accumulated load of a cell when overload occurs
due to the MLB operation
LoadIndicatorCnt The number of LoadIndicatorAvg called.
OverloadCount The number of overload occurrences due to the
MLB operation.
MlbDurationAvg Average of the overload period due to the MLB
operation.
MlbDurationMin Minimum value of the overload period due to the
MLB operation.
MlbDurationMax Maximum value of the overload period due to the
MLB operation.
MlbDurationTot Accumulated value of the overload period due to
the MLB operation.
MlbDurationCnt The number of MlbDurationAvg called.
NumUeOverloadCnt The number of events that the number of RRC
connected UEs exceeds the configured threshold
when loadEvaluateMode = loadTotal
CpuOverloadCnt The number of events that the CPU usage exceeds
the configured threshold when loadEvaluateMode
= loadTotal
BackhaulOverloadCnt The number of events that the available backhaul
resource falls down below the configured threshold
when loadEvaluateMode = loadTotal
PdcchOverloadCnt The number of events that the PDCCH usage
exceeds the configured threshold when
loadEvaluateMode = loadTotal
LBHO MlbNotTriggered_Load The number of times when there is no candidate
Condition neighbor cell that meets the load condition
although MLB is triggered.
MlbNotTriggered_Radi The number of times when there is no candidate
oCondition UE because radio condition is not met although
MLB is triggered.
MlbHOPrepAtt The number of HO preparation attempts by Intra-
LTE MLB
MlbHOPrepFailureNoR The number of HO preparation failure by Intra-LTE

Confidential

esource MLB. It is collected when eNB receives HO
preparation failure with No radio resources
available in target cell or Intra eNB HO failure
indication caused by same reason.
MlbHOAtt The number HO attempts after HO preparation
success for intra-LTE MLB.
MlbHOSucc The number of successful handovers when MLB is
triggered.
LbhoCnt Load Balancing handover collection count.
LbhoCid tcID of which collection is requested.
LOAD_HISTOGRAM LoadBinAvg Cumulative LoadBinAvg.
LoadBinCnt LoadBinAvg collection count.
DLLoadBinTot Sum of PRB-based DL Cell Load samples
corresponding to the histogram bin
DLLoadBinCnt The number of PRB-based DL Cell Load samples
ULLoadBinTot Sum of PRB-based UL Cell Load samples
ULLoadBinCnt The number of PRB-based UL Cell Load samples
REFERENCE
[1] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2
[2] 3GPP 36.331: E-UTRAN; Radio Resource Control (RRC); Protocol
specification
[3] 3GPP 36.423: E-UTRAN; X2 application protocol (X2AP)
[4] 3GPP 36.902: E-UTRAN; Self-configuring and self-optimizing network (SON)
use cases and solutions

Confidential
LTE-SW2003, Idle UE Distribution

INTRODUCTION
Idle UE distribution provides a method of controlling the UE populations over
multi-carriers. Idle UE distribution algorithm makes active-to-idle transition UEs
distributed over carriers by giving dedicated cell reselection priority information to
each UE via Idle Mode Mobility Control Info IE in the RRC Connection Release
message.
The cell reselection priorities for carriers delivered by the SIB information are
commonly applied to all the UEs in a serving cell. In this case, it is highly likely
that most of idle UEs will camp on the carrier with the highest priority.
When many idle UEs in a specific carrier turn into RRC connected UEs in a short
time, traffic load may be concentrated to the carrier. In the multi-carrier LTE
network, idle UEs need to be distributed over multiple carriers not to densely camp
on a carrier.
Idle UE distribution feature enables eNB to distribute RRC-connection-released
UEs according to the UE distribution rate to each carrier.
The following figure shows the concept of idle UE distribution. When idle UE
distribution is not used, most of UEs may camp on the carrier A while only the UE
not supporting carrier A or UE out of the cell reselection coverage of the carrier A
camps on the carrier B. On the other hand, idle UE distribution can distribute UEs
almost equally between the carrier A and the carrier B.
BENEFIT
This feature makes UEs distributed over carriers.
DEPENDENCY
Others: Most of UEs need support multiple carriers of the operator's LTE network.

Confidential
LIMITATION
None
SYSTEM IMPACT
capabilities.
LTE-SW2007 Load based Redirection to Different Carrier feature is available
when this feature (LTE-SW2003) is set to AutoApply mode.
Idle UE Distribution affects the number of RRC-idle UEs camping on a cell in the
multi-carrier network, which influences the number of call attempts to the cell.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
There are two operating modes for idle UE distribution and Operator can select the
operating mode by using IDLE_MODE_LB_ENABLE (CHG-TM-CNTR). In the
manual operating mode (LbManualApply), the eNB distributes active-to-idle
transition UEs over carriers by using the configured UE distribution rate to each
carrier (PLMN(k)_SEARCH_RATE_FOR_IDLE_LB (CHG-EUTRA-FA)). In the
automatic operating mode (LbAutoApply), the UE distribution rate to each
carrier is automatically generated based on the average cell capacity of a carrier.
Automatically generated UE distribution rate does not change the parameter value
of PLMN(k)_SEARCH_RATE_FOR_IDLE_LB.
Manual Operating Mode

Based on the configured UE distribution rates, eNB calculates the percentage of
UEs to have the dedicated highest cell reselection priority on a specific carrier. For
example, the UE distribution rates to carrier A and carrier B are ‘2’ and ‘3’
respectively in the two-carrier LTE network. Then, 40%(=2/(2+3)) RRC released
UEs will have the highest dedicated cell reselection priority on carrier A and
60%(=2/(2+3)) UEs will have the highest dedicated priority on carrier B.
When a UE is in the process of RRC connection release, the eNB determines the
carrier with the highest priority for the UE so that the percentage of actually RRC-
connection-released UEs for each carrier approaches the calculated percentage for
idle UE distribution. The priorities of the other unchosen carriers are set to less
than 7 while the selected carrier has the priority ‘7.’ (Note that the range of the cell

Confidential
reselection priority is from 0 to 7 and ‘7’ is the highest value according to 3GPP
spec. TS36.331.) The dedicated cell reselection priority information is included in
the IdleModeMobilityControlInfo IE of the RRC Connection Release message.
The following figure depicts an example above in 2-carrier LTE network.
As shown in the following figure, the dedicated cell reselection priority

information in the IdleModeMobilityControlInfo IE is valid only for the duration
T320 (CHG-TIME-INF). After the timer expires, an idle mode UE shall use the
cell reselection priority information in the received SIB3 & SIB5. (The cell
reselection priority of a serving carrier is contained in the SIB3 and those of inter-
carriers are contained in SIB5.)
Automatic Operating Mode

In the automatic operating mode, the UE distribution rate to each carrier is
automatically updated every period (PERIOD_FOR_IDLE_LB (CHG-IDLE-
LB)). The dedicated cell reselection priority information
(IdleModeMobilityControlInfo IE) is included in the RRC Connection Release
message only if the serving cell’s load exceeds the threshold
IDLE_LB_ENTER_THRESHOLD. Otherwise, dedicated cell reselection priority
information is not included. The remaining procedure is same as that in the manual
operating mode.

Confidential
Evaluation on the Average Cell Capacity of a Carrier

The UE distribution rate to each carrier is calculated as proportional to the average
cell capacity value of the carrier, which is the average of cell capacity values of the
configured number (NUM_OF_NR_FOR_IDLE_LB (CHG-IDLE-LB)) of
selected cells in the carrier during a period (PERIOD_FOR_IDLE_LB). The cell
capacity of a cell is the minimum between DL capacity value and UL capacity
value. (Refer to the part on ‘Cell load metric’ in LTE-SW2001 for the definition of
capacity value.) To get the information on the DL/UL capacity values of inter-eNB
neighbor cells, X2 Resource Status Reporting procedure is used. The UE
distribution rates to each carrier is calculated as:
Where, CCCV (carrier#k) indicates the cell capacity class value for carrier #k and
can be configured by using CELL_CAPACITY_CLASS_VALUE_DL_PER_FA
(CHG-EUTRA-FA). (For the concept of cell capacity class value, refer to the
TS36.423.).
When selecting a configured number of cells in each inter-carrier for calculating
the UE distribution rate, the eNB first includes the co-located inter-frequency cells
and then selects neighbors with larger HO successes. In the case of the serving
carrier, a serving cell is selected and then NUM_OF_NR_FOR_IDLE_LB - 1
neighbors are selected.
The following figure shows an example of selecting cells for calculating the
average cell capacity value of each carrier when
NUM_OF_NR_FOR_IDLE_LB = 7.
Separate UE Rate for CA Capable UEs

If the operator wants that most of CA capable UEs shall camp only on CA
supportable carriers, the separate CA-UE distribution rates can be used. When
IDLE_CA_USE (CHG-TM-CNTR) is set as CI_ON, then
PLMN(k)_SEARCH_RATE_FOR_IDLE_LB_CA (CHG-EUTRA-FA) will be
applied to CA capable UEs. The procedure is same as Manual operating mode.

Confidential
Fixed CA-UE rates configured by operator are applied to CA capable UEs even in
the automatic operating mode as well as in the manual operating mode.
The eNB tries to distribute CA capable UEs and non-CA UEs so that the
percentage of actual total RRC released UEs for each carrier approaches the
percentage calculated from the UE distribution rates as shown in the figure below.
The example shows the case in the manual operating mode.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-TM-CNTR and set IDLE_MODE_LB_ENABLE to
MANUAL_APPLY or AUTO_APPLY for selecting the operation mode of idle
UE distribution.
• Run CHG-TM-CNTR and set IDLE_CA_USE to ON when operator wants to
use separate CA-UE distribution rates.
To deactivate the feature, do the following:
• Run CHG-TM-CNTR and set IDLE_MODE_LB_ENABLE to OFF for disabling
the operation mode of idle UE distribution.
• Run CHG-TM-CNTR and set IDLE_CA_UE to OFF when operator does not
want to use separate CA-UE distribution rates.

Confidential
Key Parameters
parameters.
IDLE_MODE_LB_ENAB This parameter configures how to execute the idle UE distribution. This parameter
LE can be set to Off, Manual, and Auto.
• Off: Does not execute the idle UE distribution.
• Manual: Execute the idle UE distribution by using a fixed UE distribution rates
configured by Operator.
• Auto: Execute the idle UE distribution by using UE distribution rates
automatically adjusted based on the available capacities of carriers.
IDLE_CA_USE This parameter controls whether to apply separate CA-UE distribution rates to CA
capable UEs.
• Off: Total UE distribution rates (PLMN* _Search_Rate_For_Idle_Lb) are applied
to CA capable UEs.
• On: Separate CA-UE distribution rates (PLMN* _Search_Rate_For_Idle_Lb_CA)
are applied to CA capable UEs.
PLMN_OPTION_FOR_I This parameter decides whether to use a dedicated set of UE distribution rates
DLE_LB according to UE’s PLMN.
• Use: PLMN (n)_Search_Rate_For_Idle_Lb or PLMN
(n)_SEARCH_RATE_FOR_IDLE_LB_CA for each carrier is applied to PLMN (n)
UEs.
• No Use: PLMN0_Search_Rate_For_Idle_Lb or
PLMN0_SEARCH_RATE_FOR_IDLE_LB_CA for each carrier is applied to UEs
irrespective of their PLMNs.
parameters.
FA_INDEX Carrier index
PLMN0_Search_Rate_F Total UE distribution rate (in other words, carrier selection ratio) to this FA_INDEX
or_Idle_Lb carrier for PLMN0 UEs in idle UE distribution when
PLMN_OPTION_FOR_IDLE_LB = Use
This is applied to all UEs irrespective of their PLMNs when
PLMN_OPTION_FOR_IDLE_LB = No_Use.

Confidential
plmn0_Search_Rate_For CA-UE distribution rate (in other words, carrier selection ratio) to this carrier for
_Idle_Lb_Ca PLMN0 CA UEs in idle UE distribution when IDLE_CA_USE = On and
This is applied to all CA UEs irrespective of their PLMNs when
PLMN_OPTION_FOR_IDLE_LB = No_Use.
Parameter Descriptions of CHG-IDLE-LB/RTRV-IDLE-LB

NUM_OF_NR_FOR_IDL To execute auto mode idle UE distribution, it is necessary to acquire the neighbor
E_LB cell load information from the neighbor cell registered to a serving cell. This
parameter configures maximum number of neighbor cells per carrier for acquiring
load information.
IDLE_LB_ENTER_THRE This parameter configures the minimum cell load of a serving cell that is required
SHOLD to execute auto mode idle UE distribution.
PERIOD_FOR_IDLE_LB This parameter configures the interval for calculating the UE distribution rates to
execute auto-mode idle UE distribution.
Counters and KPIs

IDLE_LB UECount The number of UEs which is allocated in the largest
carrier selected as the highest
cellReselectionPriorityby Idle UE distribution when
RRC Connection Release is occurred
IdleLbCnt Counter of trying Idle Load Balancing
IdleLbTargetEarfcnDL TargetEarfcnDl collected by idle UE distribution

Confidential
REFERENCE
specification

Confidential
LTE-SW2008, Blind Offloading to eHRPD

INTRODUCTION
Depending on a service provider’s network environment, the intra-LTE load
balancing functions such as load equalization, offloading to intra-group carriers,
and offloading to inter-group carriers are initiated first of all and the blind
offloading to inter-RAT (eHRPD) function is initiated if the overload state cannot
be resolved within the LTE network.
Figure below depicts the step-by-step activation of load balancing functions as the
serving cell load increases.
BENEFIT
• This feature reduces the overload state of an LTE cell by using eHRPD
network.
• This feature will relieve the bad QoE due to overload.
DEPENDENCY
Others: To enable the blind offloading to eHRPD function, the operator must set
the information on eHRPD band classes by using RTRV-HRPD-BCLS/CHG-
HRPD-BCLS.
LIMITATION
Threshold condition: The BlindOffloadtoIRAT_Threshold
(IRAT_OFFLOAD_THRESHOLD (RTRV-IRAT-MLB/CHG-IRAT-MLB)) in the
figure of introduction should be set higher than intraGroupOffloadThreshold

Confidential
(INTRA_GROUP_OFFLOAD_THRESHOLD (RTRV-LBCELL-CONF/CHG-
LBCELL-CONF)) and interGroupOffloadingThreshold(k)
(INTRA_GROUP_OFFLOAD_THRESHOLD (RTRV-LBGRPCELL-CONF/CHG-
LBGRPCELL-CONF)).
SYSTEM IMPACT
capabilities.
LTE-SW2001 Intra-LTE MLB feature is not activated when this feature is turned
on and the source cell load exceeds IRAT_OFFLOAD_THRESHOLD.
This feature reduces the load of the LTE network by offloading UEs to the eHRPD
network. Therefore, this feature affects the load of the eHRPD network.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
The procedure of blind offloading to eHRPD is depicted in figure below.

Confidential
1 To enable this feature, OFFLOAD_TO_HRPD_ENABLE (RTRV-TM-

CNTR/CHG-TM-CNTR) must be set to ON. The operator must configure the
information of eHRPD band classes in advance by using RTRV-HRPD-
BCLS/CHG-HRPD-BCLS.
2 The eNB monitors the load levels of its own cells periodically.
3 If the cell load of its own cell exceeds IRAT_OFFLOAD_THRESHOLD
(RTRV-IRAT-MLB/CHG-IRAT-MLB), then blind offloading to eHRPD is
activated.
4 The eNB selects candidate UEs supporting the configured eHRPD band
classes up to RATE_LB_CANDIDATE/100 x MAX_CALL_COUNT. The eNB
then configures eHRPD measurements on candidate UEs.
The RATE_LB_CANDIDATE can be configured by using RTRV-LBCELL-
CONF/CHG-LBCELL-CONF.
MAX_CALL_COUNT indicates the maximum number of allowable RRC
connected users per cell.
The operator can configure the measurement report type (REPORTING_TYPE
(RTRV-IRAT-MLB/CHG-IRAT-MLB)) as periodical or event B1.
5 If the event B1 type is used and a UE reports a corresponding B1
Measurement Report (MR), the eNB redirects the UE to the reported eHRPD
band class. If the periodical MR type is used and the UE reports a periodical
MR, the eNB checks whether the reported eHRPD-RSSI exceeds
HRPD_RSSI_THRESHOLD (RTRV-IRAT-MLB/CHG-IRAT-MLB). If so,

Confidential
the eNB redirects the UE. The eNB keeps redirecting UEs until the number of
offloaded UEs reaches RATE_LB_TARGET/100 x (number of current RRC
Connected UEs).
RATE_LB_ TARGET can be configured by using RTRV-LBCELL-
CONF/CHG-LBCELL-CONF.
When the eNB redirects the UE to an eHRPD band class, the eNB releases the
UE by sending RRC Connection Release message including both
redirectCarrierInfo IE and idleModeMobilityControlInfo IE. The dedicated
cell reselection information (idleModeMobilityControlInfo IE) is used to
prevent UE’s short return from eHRPD to LTE.
The IdleModeMobilityControlInfo IE is generated based on the
OFFLOAD_DEDICATED_PRIORITY (RTRV-EUTRA-FA/CHG-EUTRA-
FA) of LTE carriers, OFFLOAD_DEDICATED_PRIORITY (RTRV-HRPD-
BCLS/CHG- HRPD-BCLS) of eHRPD band classes, and
T320_FOR_OFFLOAD (RTRV-TIME-INF/CHG-TIME-INF).
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-TM-CNTR and set OFFLOAD_TO_HRPD_ENABE to ON.
• Run CHG-TM-CNTR and set OFFLOAD_TO_HRPD_ENABE to OFF.
Key Parameters
parameter.

Confidential
Parameter Description of CHG-TM-CNTR/RTRV-TM-CNTR

OFFLOAD_TO_HRPD_ENABL
This parameter is used to turn on/off blind offloading to eHRPD.
E
parameter.
Parameter Descriptions of CHG-IRAT-MLB/RTRV-IRAT-MLB
IRAT_HRPD_OFFLOAD_PRIO This parameter indicates the priority of HRPD among inter-RATs (3G, 2G,
RITY and HRPD) for the purpose of inter-RAT offloading.
This parameter indicates the type of measurement reporting used for Inter
REPORTING_TYPE
RAT MLB: periodical MR or event B1 MR.
This parameter is serving cell load condition for entering blind offloading to
IRAT_OFFLOAD_THRESHOLD
neighbor.
Parameter Descriptions of CHG-HRPD-BCLS/RTRV-HRPD-BCLS

This parameter indicates dedicated priority for each HRPD band class.
OFFLOAD_DEDICATED_PRIO
This is used for configuring dedicated cell reselection priority when a UE is
RITY
redirected by inter-RAT offloading.

This parameter indicates dedicated priority for each LTE carrier.
OFFLOAD_DEDICATED_PRIO
This is used for configuring dedicated cell reselection priority when a UE is
RITY
redirected by inter-RAT offloading.
Parameter Descriptions of CHG-TIME-INF/RTRV-TIME-INF

T320_FOR_OFFLOAD This parameter is t320 timer used only for inter-RAT offloading.
Counters and KPIs

LB_REDIRECTION LBRedirectiontoHRPD The count for redirected UE to HRPD by load
balancing
REFERENCE

Confidential

specification
[5] Feature Detail Description (LTE-SW2001, SW2002) Intra-LTE Load
Balancing, Samsung Electronics

Confidential
LTE-SW2009, Multi-carrier Load Balancing with

CA
INTRODUCTION
Multi-carrier load balancing with CA feature is the enhanced version of the feature
LTE-SW2001, Intra-LTE Mobility Load Balancing (MLB). Two features have the
same purpose to reduce the load level of an overloaded cell. While some UEs may
experience degraded user throughputs after offloaded by Intra-LTE MLB, this
feature minimizes degradation of offloaded throughput of UEs and tries to
improve offloaded the throughput by first estimating throughput for each UE after
offloaded, and then selecting UEs to be offloaded.
BENEFIT
This feature improves throughput of each offloaded UE.
DEPENDENCY
• Prerequisite Features: LTE-SW2001, Intra-LTE Mobility Load Balancing and
LTE-SW5500, CA Call Control
• Others: Most of UEs need to support multiple carriers of the operator LTE
network.
LIMITATION
None
SYSTEM IMPACT
capabilities.
Inter-dependencies between Features
None
LTE-SW2009 Multi-carrier Load Balancing with CA feature performs gradual
reduction of overload traffic by moving configured rate of UEs to neighbors every
period (configurable: a few second). The amount offloaded traffic at each period
can be adjusted by configuring related parameters (RATE_LB_CANDIDATE and
RATE_LB_TARGET).
Coverage
None

Confidential
Interfaces
None
FEATURE DESCRIPTION
This feature works based on the operation of the feature LTE-SW2001, Intra-LTE
MLB since it is designed as an add-on to LTE-SW2001. Therefore, the procedure
of this feature is similar to that of LTE-SW2001. However, this feature has
differences from LTE-SW2001 in the stage of selecting {target UE, target cell}
pairs.
Figure below depicts the operational procedure of this feature.
1 To enable this feature when any functions of the intra-LTE MLB is turned
On, CA_OPTION_FOR_LB (RTRV-TM-CNTR/CHG-TM-CNTR) must be set
to ON.
This feature also stops when all the MLB functions are turned off. It is
recommended that the function offloading to intra-group carriers
(INTRA_GROUP_OFFLOAD_ENABLE (CHG-TM-CNTR)) be used for this
feature.)

Confidential
2 The eNB monitors the load levels and DL PRB usages of its own cells and
neighbor cells periodically.
3 If a source cell exceeds a configured threshold for one of turned-on intra-LTE
MLB functions, then the corresponding intra-LTE MLB function is activated.
4 The eNB selects candidate UEs with higher DL PRB usage in the source cell.
USE_TRAFFIC_PER_UE (RTRV-CELL-CAC/CHG-CELL-CAC) must be set to

CI_USE. )
SCell UEs as well as PCell UEs can be selected as candidate UEs since this
feature uses UE’s SCell change as well as inter-frequency HO by considering
all the Supported Band Combinations (SBCs) of each CA UE.
5 The eNB configures measurements to candidate UEs and collects
Measurement Reports (MRs).
6 The eNB evaluates each candidate UE’s achievable throughput enhancement,
which indicates the increased ratio of the future estimated throughput to the
current throughput for the UE. The estimated UE throughput is calculated
based on the SBC, reported RSRP, and available DL PRB usage.
7 The eNB selects target PCell UEs and SCell UEs with higher achievable
throughput enhancement.
8 The source cell performs HOs of target PCell UEs while the corresponding
PCell of each target SCell UE performs HO or changes the SCell to release
the source cell.
SYSTEM OPERATION
How to Activate
Preconditions
• There should be a configured EUTRAN neighbor network.
• This feature work on “Intra-LTE Mobility Load Balancing” feature. So
configuration for “Intra-LTE Mobility Load Balancing” feature is prerequisite.
• Run CHG-TM-CNTR to enable this feature.
• Run CHG-ACTIVE-LB to configure required information for this feature.
• Run CHG-EUTRA-FA to configure required information for this feature.

Confidential
• Run CHG-TM-CNTR to disable this feature.
Key Parameters
parameters.
CA_OPTION_FOR_LB This parameter is used to enable/disable this “Multi-Carrier Load Balancing
with CA” feature.
parameters.
Parameter Descriptions of CHG-ACTIVE-LB/RTRV-ACTIVE-LB
PRB_IIR_COEF This parameter is used to control filter coefficient which is used for the
calculation of PRB occupancy rate per UE. This is used for “Multi-Carrier
Load Balancing with CA” feature.

LB_DELTA_NI This parameter is used for compensation during SINR estimation of one
frequency using the other frequencies. It is required for different physical
characteristics of frequencies. This is used for Multi-Carrier Load Balancing
with CA feature.
LB_MIMO_LAYER This parameter is used to provide a representative value for the number of
MIMO layers related with a frequency of network. This is used for Multi-
Carrier Load Balancing with CA feature.
LB_DL256_QAM This parameter is used to provide a representative value for the modulation
scheme related with a frequency of network. This is used for Multi-Carrier
Load Balancing with CA feature. FALSE (non-256 QAM), TRUE (256
QAN).
Counters and KPIs

Multi-Carrier Load Balancing by MclbCaCcChangeReq This is a cumulated number of SBC Change by
CA MCLB with CA.

Confidential

MclbCaRequestWithGive This is a cumulated number of Candidate Cell
nCell Information received from Source Cell.
MclbCaDoneByGivenCell This is a cumulated number of CA Decision by
MCLB with CA based on Candidate Cell
Information.
REFERENCE
specification
[5] Samsung LTE SW Feature Description; LTE-SW2001 Intra-LTE Mobility
Load Balancing

Confidential
LTE-SW2020, Load Distribution over Backhaul

Links
INTRODUCTION
When an eNB is connected to a backhaul network with multiple Ethernet links,
there are different ways to distribute load over the links depending on the IP
configuration. When single IP address is used for two Ethernet links in the same
subnet, the link aggregation can be used for load balancing between two links. To
send a packet, one link is selected by a hashing algorithm based on five tuples of
the packet. When one link fails, the other link carries all the packets. In this case,
however, the SCTP multi-homing for S1/X2 interface cannot be used because
there is only one IP address available.
The Equal Cost Multi Path (ECMP) is another way to achieve load balancing
between two links that has two different IP addresses belonging to different
subnet. However, it is not likely to distribute load over the links evenly because
most packets have the same source and destination IP and port number.
This feature allows application layer to select a link during call setup or handover
procedure based on the number of UEs per each link. Data traffic from a UE is
carried over the same link.
BENEFIT
Load balancing can be achieved among multiple links.
DEPENDENCY
• Interface & Protocols: S1 bearer interface
• Others: This feature performs load distribution of S1 bearer traffic link for IP
addresses of LTE_bearer_S1 set to True by COM-IP0501 (Flexible IP
Operation for OAM, Signaling and Bearer Traffic).
LIMITATION
This feature does not support automatic configuration of load distribution ratio
considering the capacity of each backhaul port, for example, in case of the mixed
usage of 10 G port and 1 G port. Operators determine the load-balancing ratio
manually considering not only the capacity of eNB backhaul port but also the
capacity of backbone network.
SYSTEM IMPACT

Confidential
FEATURE DESCRIPTION
When an eNB receives the Initial Context Setup Response message during call
setup or S1AP Handover Request Acknowledge message during handover process
from MME, it selects a S1 bearer traffic link (S1-U) which has the lowest load in
terms of the number of the connected UEs. When the load is distributed based on
the number of UEs, the actual amount of traffic may not be strictly equalized
among multiple links. The eNB then includes the selected S1-U IP to the Initial
Context Setup Response message or S1AP Handover Request Acknowledge
message and sends the messages to MME, as depicted in figure below.
Load Distribution Algorithm (S1-U Selection Algorithm)

This feature runs automatically by pre-configuration using command CHG-
S1BHLB-INFO. The eNB distributes load based on the configured load-balancing
rate for each backhaul link in terms of the number of UEs. Operator can configure
load balancing ratio parameter (S1_BACKHAUL_RATE), which has its range from
1 to 10 for each link. Then, the eNB calculates UE Usage for each link and selects
the S1-U, which has the lowest UE Usage. UE Usage for a specific link is defined
as follows:
Where:
• The number of UEs connected to the link is the number of the connected UEs
that use S1-U IP address of this link.
• maxEnbCallCount is the maximum number of the connected UEs for the eNB.
• S1_BACKHAUL_RATE is the rate assigned to the S1-U for backhaul link
distribution and is configurable by operator.
SYSTEM OPERATION

Confidential
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-S1BHLB-INFO/RTRV-S1BHLB-INFO
DB_INDEX This parameter is index about the S1-U Backhaul LB Rate.
STATUS The EQUIP status information on the S1 backhaul Port.
• N_EQUIP: Configured S1-U IP address is not used for S1 Backhaul Link
distribution.
• EQUIP: Configured S1-U IP address is used for S1 Backhaul Link
distribution.
IP_VER The IP address version of the S1-U eNB IP address. Either IPv4 or IPv6 is
assigned.
S1_BACKHAUL_IPV4 Information on the S1-U IPV4 address of the eNB. This parameter value is
valid only if the IP_VER parameter is set to IPv4. It is not used if the IP_VER
S1_BACKHAUL_IPV6 Information on the S1-U IPV6 address of the eNB. This parameter value is
valid only if the IP_VER parameter is set to IPv6. It is not used if the IP_VER
S1_BACKHAUL_RATE This parameter sets the rate to be assigned the S1-U for Backhaul link
distribution.
For example, backhaul port with rate 10 will have 10 times higher opportunity
to be selected for S1-U interface than the backhaul ports with rate 1, when 2
backhaul ports are configured.
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
LTE-SW2007, Load based Redirection to

Different Carrier
INTRODUCTION
The preemption feature (LTE-SW4103) enables a new UE to be admitted by CAC
to the utmost. When the number of existing UEs in a cell is equal to the maximum
for normal calls and preempting an existing UE is not available, a new UE will be
rejected by CAC. The eNB can inform the rejected UE of an available carrier with
the lowest load by using the load information for each carrier when LTE-SW2003
idle UE distribution feature is set to AutoApply mode.
BENEFIT
• The operator can use the multicarrier network efficiently by moving the
rejected UEs to carriers with lower load.
• The UE can be connected to a lower loaded carrier and get more reliable
services.
DEPENDENCY
Prerequisite Features: This feature is available only when the LTE-SW2003, Idle
UE Distribution feature is set to AutoApply mode.
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
This feature is applied only to the UEs rejected by the call admission control or the
pre-empted UEs if the feature idle UE distribution (LTE-SW2003) with the
automatic mode is operating. Therefore, there is no significant impact on UE's
service.
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
The load-based redirection to another carrier feature operates as shown in the
following figure which depicts a scenario for CAC rejection at RRC connection
establishment.
New UE eNB
RRC Connection Request
CAC at RRC connection

establishment
Reject
RRC Connection Setup Complete
Select target carrier based on

carrier load for incoming UE (If
selected target carrier ==
serving carrier, not include in
RRC Release)

(Selected Target carrier)
The following figure depicts a scenario for CAC rejection at E-RAB

establishment.

Confidential
eNB
UE MME
ECCB
RRC Connection Request
CAC at RRC connection

establishment
Accept
RRC Connection Setup Complete

Initial UE
CAC at E-RAB
establishment
Reject Initial Context Setup Failure

(RedirectedCarrierInfo (LTE or IRAT 1 FA),
IMMCI (available all LTE & Inter-RAT FA), t320Offload)
If a UE is rejected by CAC, then eNB informs the rejected UE of an available

carrier with the lowest load by sending the RedirectedCarrierInfo IE in the
RRCConnectionRelease message.
For per-carrier load monitoring, refer to the Calculation of the Average Cell
Capacity of a Carrier in LTE-SW2003, Idle UE Distribution.
When a UE is rejected at the stage of RRC connection establishment, the eNB
cannot know the UE’s radio capability. Since the UE may not support the
redirected carrier, eNB informs the UE of the IdleModeMobilityControlInfo IE,
which includes all the LTE carriers. In the IdleModeMobilityControlInfo IE, the
redirected carrier has the highest priority (7) while other LTE carriers have the
priorities lower than 7. When a UE is rejected at the stage of E-RAB
establishment, eNB can know the UE’s radio capability if S1 Initial Context Setup
Request message contains the UE Radio Capability IE. If eNB gets the UE’s radio
capability, then eNB generates the RedirectedCarrierInfo IE and the
IdleModeMobilityControlInfo IE based on the UE’s supportable carriers.
SYSTEM OPERATION
provides associated key parameters to customize the configuration settings.

Confidential
How to Activate
Preconditions
• A valid license key is required to activate this feature.
• Idle UE distribution feature needs to be turned on in advance to run the feature
based on the load information received from neighbor eNBs.
• Run CHG-CELL-CAC and set LB_REDIRECTION_USAGE to USE.
• Run CHG-CELL-CAC and set LB_REDIRECTION_USAGE to NO_USE.
Key Parameters
LB_REDIRECTION_USAGE Determines whether or not the load-based redirection is allowed at CAC per
cell.
The possible values are:
• CI_no_use: The load-based redirection is not allowed at CAC function.
• CI_use: The load-based redirection is allowed at CAC function.
parameters.
CELL This parameter is the number of cells. This value must not exceed the
LB_REDIRECTION_USAGE This parameter indicates whether to perform the load based redirection at
CAC per cell.
• NO_USE: Does not perform the load-based redirection at CAC function.
• USE: Perform the load-based redirection at CAC function.

Confidential

CELL This parameter is the number of cells. This value must not exceed the
T320_FOR_OFFLOAD This parameter is t320 timer used in the offloading only.
Counters and KPIs

The following table outlines the main counter associated with this feature.
REDIR_LBCAC RedirLbCac The number of redirections performed after
rejecting the UEs by CAC function.
REFERENCE
specification
[5] Feature Detail Description (LTE-SW4103) Pre-emption, Samsung Electronics
[6] Feature Detail Description (LTE-SW2006) Load-based Idle UE Distribution,
Samsung Electronics

Confidential
LTE-SW2033, Redistribution of Idle-mode UEs

INTRODUCTION
When a cell is overloaded due to too many RRC-connected UEs, mobility load
balancing (LTE-SW2001 Intra-LTE MLB) offloads a part of RRC-connected UEs
to lower-loaded inter-frequency cells in the LTE multiple carrier network. If the
RRC-establishment attempt rate keeps high in the overloaded cell, the overloaded
state cannot be resolved for the time being. By redistributing RRC-connection
idle-mode UEs camping on the overloaded cell, the RRC establishment attempt
rate will be reduced and eNB can reduce the load-based HOs.
Only Rel. 13 redistribution-capable UE supports cell reselection based on

redistribution.
BENEFIT
This feature enables redistribution-capable UEs in RRC-connection idle-mode to
be distributed over multiple frequencies or helps the overload reduction by
inducing redistribution-capable UEs to reselect another frequency.
DEPENDENCY
Others:
• Only Rel. 13 redistribution-capable UE supports this feature.
• UEs with the dedicated priority information do not perform cell reselection
based on the redistribution.
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
If the percentage of redistribution-capable UEs is too low, then it is difficult for
this feature to reduce the RRC establishment attempt rate.
When LTE-SW2003 Idle UE Distribution is turned on, the redistribution can be
restricted since a lot of UEs have valid dedicated priority information.

Confidential
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Samsung eNB provides two types of redistribution methods: Continuous
Randomization Scheme (CRS) and One Shot Scheme (OSS) with paging. While
redistribution actions in CRS continuously occur, redistribution actions in OSS
occur only when redistributionIndication-r13 paging is sent. The eNB broadcasts
the redistribution information via SIB3 and SIB5, which includes the redistribution
factor of each frequency and t360 timer.
Redistribution-capable UEs in the RRC-connection idle-mode perform cell
reselection according to the redistribution information included in SIB3 and SIB5.
The UE selects a redistribution target based on its International Mobile Subscriber
Identity (IMSI) and the redistribution factors of the frequencies, which meet the
cell selection criterion. For the detail of the UE redistribution procedure, see the
section 5.2.4.10 E-UTRAN Inter-frequency Redistribution Procedure in TS36.304.
If the UE reselects the redistribution target, then it starts the T360 timer. While the
timer is running, the redistribution target is considered as highest priority in the
cell reselection evaluation process. The UE stops this timer and ceases to consider
a frequency to be redistribution target when it enters to the RRC-connected state,
receives the redistributionIndication-r13 paging, or reselects another frequency.
UEs with the dedicated priority information do not perform cell reselection based
on the redistribution.
Continuous Randomization Scheme (CRS)

The eNB broadcasts the redistribution information via SIB3 and SIB5 without
redistrOnPagingOnly IE in SIB3. In this case, redistribution actions are performed
continuously based on the constant redistribution factors configured by operator.
One Shot Scheme (OSS)

The eNB broadcasts the redistribution information via SIB3 and SIB5 with
redistrOnPagingOnly IE in SIB3. In this case, redistribution actions are performed
only when the eNB determines that the RRC establishment attempt rate needs to
be reduced in its served cell and redistributionIndication-r13 paging is sent.
Samsung eNB uses two-level redistribution by monitoring the RRC-establishment
attempt rate and the RRC-connected UEs periodically. If the eNB detects that its
cell enters into level 1 or level 2, it makes the cell send the
redistributionIndication-r13 paging. If the cell enters into level 1, the eNB uses the
redistribution factors configured by operator. If the cell enters into level 2, the eNB
reduces the redistribution factor of the serving frequency so that more
redistribution-capable UEs reselect other frequencies.

Confidential
Table below outlines the conditions for redistribution levels.

Condition Level 1 Level 2
Number of RRC-connected UEs X > connectTh
(X)
RRC-establishment attempt rate attemptTh0 < Y <= attemptTh1 Y > attemptTh1
(Y)
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-TM-CNTR and set REDISTRIBUTION_MODE to CRS_MODE or
OSS_MODE.
• Run CHG-TM-CNTR and set REDISTRIBUTION_MODE to REDIST_OFF.
Key Parameters
parameter.
Parameter Description of CHG-TM-CNTR/RTRV-TM-CNTR
REDISTRIBUTION_MODE This parameter is used to select operation mode of Redistribution of Idle
Mode UEs.
parameter.

Confidential

REDIST_FACTOR This parameter is RedistributionFactor-r13for each FA index

T360 This parameter is RedistributionFactor-r13 for each FA index
Parameter Descriptions of CHG-REDISTCELL-CONF/RTRV-REDISTCELL-

CONF
REDIST_PERIOD_FOR_OSS This parameter is a period to decide Redistribution in OSS mode.
CONNECT_TH_RATIO This parameter is a ratio that is used to calculate the threshold for the
number of connected UEs.
ATTEMPT_TH0 This parameter is threshold 0 that is used to decide
REDISTRIBUTION_FACTOR_SERVING in OSS mode.
This value is always smaller than ATTEMPT_TH1.
ATTEMPT_TH1 This parameter is threshold 1 that is used to decide
REDISTRIBUTION_FACTOR_SERVING in OSS mode.
This value is always bigger than ATTEMPT_TH0.
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
LTE-SW2102, eNB Overload Control (Adaptive

Access Barring)
INTRODUCTION
Samsung eNB uses the access barring function defined in the standard to reduce
the amount of signaling messages flowing from the UE. The 3GPP standard
(TS36.331) defines to set access probability and access limit time information for
MO-signaling and MO-data to a SIB2 message broadcast by cell. The UE
stochastically decides whether it should attempt the current call or a call after a
certain period based on AC-Barring Information of SIB2. If the number of
signaling messages is increased, the CPU load of the main card of eNB is on rise
and therefore the service quality can be deteriorated by increasing the call setup
time, etc. In the worst case, the system may be shut down. The eNB overload
control function prevents the system from being shut down by reducing the
number of signaling messages occurring from the UE if the CPU load is increased.
An operator can set the access probability and the access limit time corresponding
to each CPU load state including Minor, Major, and Critical. When the load level
becomes minor, major or critical by monitoring the CPU load periodically, the
eNB broadcasts AC-Barring Information to all cells managed thereby. When the
load of the CPU returns to be normal, the AC-Barring information is restored to
the default value and broadcast. Also, eNB considers the number of RRC
connected users and the rate of RRC connection requests. If either of these reaches
a corresponding threshold and does not fall below the threshold for a certain time,
eNB uses the access barring function.
BENEFIT
• Can reduce the number of call attempts to an overloaded eNB, which can
prevent the eNB from shutting down due to overload.
• LTE users can avoid access to an eNB under congestion.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
capabilities.

Confidential

None
If ACB is broadcasted due to CPU overload, the UE can be limited to access
network.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Adaptive access class barring is to reduce the amount of call attempts from the UE
by broadcasting AC-Barring information. This adaptive access class barring
consists of CPU load based and RRC connection based access barring, as depicted
in figure below.
RRC Connection-based Access Class Barring

Broadcasting access class barring is triggered by the number, rate, or rejection
ratio of RRC connections.

Confidential
Whenever the eNB admits a RRC Connection, it checks whether the number of
RRC connections exceeds a predefined threshold, THRESHOLD_ACTIVATION
(CHG-ENBACB-RRC/CHG-CELLACB-RRC). If the number of RRC connections
rises above the threshold and does not fall below the threshold for a configured
time GUARD_TIME_ACTIVATION (CHG-ENBACB-RRC/CHG-CELLACB-
RRC), broadcasting access class barring parameters is triggered. At each interval,
DYNAMIC_ACB_UPDATE_PERIOD (CHG-CELL-ACS), the eNB monitors
change in the number and adjust access class barring parameters if necessary.
During a configurable time, GUARD_TIME_DEACTIVATION (CHG-ENBACB-
RRC/CHG-CELLACB-RRC), the number of RRC connections keeps below a
predefined threshold, THRESHOLD_DEACTICATION (CHG-ENBACB-
RRC/CHG-CELLACB-RRC), access class barring based on the number of RRC
connections is deactivated.
Broadcasting Access Class Barring Information can be triggered based on rate of
RRC Connections. To measure the rate of RRC connection request, the eNB
counts the number of RRC connection request for 1 s. If the rate rises above a
threshold, THRESHOLD_ACTIVATION (CHG-ENBACB-RATE/CHG-CELLACB-
RATE), and does not fall below the threshold for a configured time,
GUARD_TIME_ACTIVATION (CHG-ENBACB-RATE/CHG-CELLACB-RATE),
broadcasting access class barring information is triggered. Once access class
barring is triggered, barring parameters can be updated in each monitoring interval,
DYNAMIC_ACB_UPDATE_PERIOD (CHG-CELL-ACS). For instance, if the rate
of RRC connection requests keeps increasing even though access class barring
parameter is broadcasted, barring factors can be adjusted. During a configurable
time, GUARD_TIME_DEACTIVATION (CHG-ENBACB-RATE/CHG-CELLACB-
RATE), the rate of RRC connection requests keeps below a predefined threshold,
THRESHOLD_DEACTICATION (CHG-ENBACB-RATE/CHG-CELLACB-RATE),
access class barring based on the rate of RRC connection request is deactivated.
Broadcasting Access Class Barring Information can be triggered based on
rejection ratio of RRC Connections. To measure the rejection ratio of RRC
Confidential
connection, the eNB counts the number of RRC connection requests and the
number of rejected RRC connections for 1 s. If the rejection ratio rises above a
threshold, THRESHOLD_ACTIVATION (CHG-ENBACB-REJ/CHG-CELLACB-
REJ), the number of RRC connection requests during every 1 s window,
THRESHOLD_RRC_REQUEST_RATE, and does not fall below the threshold for a
configured time, GUARD_TIME_ACTIVATION (CHG-ENBACB-REJ/CHG-
CELLACB-REJ), broadcasting access class barring information is triggered. Once
access class barring is triggered, barring parameters can be updated in each
monitoring interval, DYNAMIC_ACB_UPDATE_PERIOD (CHG-CELL-ACS). For
instance, if the rejection ratio requests keep increasing even though access class
barring parameter is broadcasted, barring factors can be adjusted. During a
configurable time, GUARD_TIME_DEACTIVATION (CHG-ENBACB-REJ/CHG-
CELLACB-REJ), the rejection ratio keeps below a predefined threshold,
THRESHOLD_DEACTICATION (CHG-ENBACB-REJ/CHG-CELLACB-REJ),
access class barring based on the rejection ratio of RRC connections is deactivated.
CPU load based Access Class Barring

The eNB overload control function is to reduce the amount of call attempts from
the UE by broadcasting AC-Barring information if it reaches the load level set by
the operator due to the increase of the CPU load of the main card. For this, the
eNB monitors the CPU load periodically and confirms that the load level as the
result of monitoring reaches that including minor, major or critical set by the
operator. If the CPU load level is changed, the AC-Barring information
corresponding to the load level is reflected to the SIB2 message to broadcast the
information to each cell managed by the eNB.
Standard for Deciding and Changing Loads

The eNB measures the CPU load in every 3 s and checks whether the mean value
recently measured five times exceeds the load level threshold set by the operator.
The operator can set each threshold to three load levels including minor, major,
and critical.
For configuring CPU thresholds by its load level, refer to OAM-FM0201, Alarm
Parameter Configuration.
If the mean value recently measured five times is kept to less than the threshold for
Confidential
one minute, it releases the alarm of the current level and goes off the alarm of the
lower level.
Load Level and AC-Barring Information Setting

As shown in the following table, the operator may set each access level for
emergency call, signaling call and data call by CPU load level. To set the access
level for the emergency call, ac-BarringForEmergency may select either value:
Barred or Not_Barred.
Ac-BarringForMO-Signaling and ac-BarringForMO-Data may set ac-
BarringFactor and ac-BarringTime, respectively. Ac-BarringFactor decides which
percentage of the phones will be statistically allowed, and ac-BarringTime decides
after which seconds the phone can attempt a call. For example, this is a concept
that if ac-BarringFactor is set to be 90 %, and ac-BarringTime to be 16 s, 90 out of
100 UEs in the coverage are allowed to immediately attempt calls and the other 10 %
attempt calls after 16 s.
The example of setting AC Barring parameter by overload level is as follows:
AC Barring Parameters (SIB Type2) CPU Load Level
Critical Major Minor Normal
ac-BarringForEmergency Barred Not Barred Not Barred Not Barred
Signalling
ac-BarringTime 128 s 32 s 16 s -
Data
ac-BarringTime 128 s 32 s 16 s -
If the phone generates a random number between 0 and 1 at the time that the
phone attempts a call and the number is smaller than ac-BarringFactor, the phone
attempts the call immediately and if the random number is larger than ac-
BarringFactor, the phone waits for as long as ac-BarringTime and then attempts a
call. ac-BarringForMO-Signalling corresponds to Attach, Tracking Area Update,
or Detach messages and acBarringForMO-Data is a parameter applied to the
Service Request message or the Extended Service Request message.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-CELL-ACS and set barringCtrUsage to cpuStatusCtrl.

To activate PLMN specific adaptive access barring control, do the following:
• Run CHG-CELL-ACS and set barringPlmnCtrUsage to
cpuStatusCtrl.
• Run CHG-BARPLMN-PARA and set plmnBarParamUsage to CI_use for
corresponding PLMN and barringStatusType.
• Run CHG-CELL-ACS and set barringCtrUsage to barringOff or
manualCtrl.
To deactivate PLMN specific adaptive access barring control, do the following:
• Run CHG-CELL-ACS and set barringPlmnCtrUsage to barringOff
or manualCtrl.
Key Parameters
feature.
parameters.
BARRING_CTR_USAGE This parameter specifies how to set the ac-barringInfo parameters of SIB2.
overload.
BARRING_PLMN_CTR_USA This parameter represents how to set the AC-BarringPerPLMN-List-r12
GE parameters of SIB2.
overload.
PLMN_BAR_PARAM_USAGE This parameter indicates to enable/disable ac-BarringforMO-Signaling of a
cell in the eNB.
• no_use: ac-BarringforMO-Signaling is not used. A UE can access a cell
during attachment.
• use: ac-BarringforMO-Signaling is used. A UE controls access to a cell
depending on access barring data parameter during attachment.

Confidential
parameter.
UDT_RESTRICTION This parameter configures Unattended Data Traffic (UDT) restricting in
SIB2 according to TS36.331 Release 13.
• TRUE: udt-Restricting-r13 is included as TRUE in SIB2.
• FALSE: udt-Restricting-r13 is not included in SIB2.
UDT_RESTRICTING_TIME This parameter configures UDT restricting time in SIB2 according to
TS36.331 Release 13. If udt-RestrictingTime is present in SIB2, and when
the udt-Restricting changes from TRUE, the UE runs a timer for a period
equal to (random number) * udt-RestrictingTime [sec]. The timer stops if
udt-Restricting changes to TRUE. Upon timer expiry, the UE indicates to
the higher layers that the restriction is alleviated.
• s4: 4
• s8: 8
• s16: 16
• s32: 32
• s64: 64
• s128: 128
• s256: 256
• s512: 512
• NOT_USED: udt-RestrictingTime is not included in SIB2.

UDT_RESTRICTION This parameter configures UDT restricting in SIB2 according to
TS36.331 Release 13.
• TRUE: udt-Restricting-r13 is included as TRUE in SIB2.
• FALSE: udt-Restricting-r13 is not included in SIB2.
UDT_RESTRICTING_TIME This parameter configures UDT restricting time in SIB2
according to TS36.331 Release 13. If udt-RestrictingTime is
present in SIB2, and when the udt-Restricting changes from
TRUE, the UE runs a timer for a period equal to (random
number) * udt-RestrictingTime [sec]. The timer stops if udt-
Restricting changes to TRUE. Upon timer expiry, the UE
indicates to the higher layers that the restriction is alleviated.
• s4: 4
• s8: 8
• s16: 16
• s32: 32
• s64: 64
• s128: 128
• s256: 256
• s512: 512
• NOT_USED: udt-RestrictingTime is not included in SIB2.

Confidential

DYNAMIC_ACB_UPDATE_PERIOD This parameter configures the time interval over which the
barring parameters are dynamically adjusted when Dynamic
ACB is activated.
DYNAMIC_ACB_USAGE This parameter indicates whether to use the cell-based
Dynamic ACB function in the cell.
Parameter Description of CHG-ENBACB-RRC/RTRV-ENBACB-RRC

DB_INDEX This parameter is the Index for the eNB information.
This parameter is the ON/OFF of Dynamic ACB (Access Class
DYNAMIC_BARRING_USAGE
Barring) based on the number of RRC Connection in the eNB.
This parameter configures on or off for including ACB Barring
ACB_SKIP_DISABLE_ENABLED Skip IEs in SIB2 in the cell if the dynamic ACB is not capable of
lowering the load.
This parameter configures on or off to apply barring to
EMERGENCY_CALL_BARRING_ENABLED emergency calls if the dynamic ACB is not capable of lowering
the load.
This parameter is the percentage of MAX_ENB_CALL_COUNT
THRESHOLD_ACTIVATION retrieved by RTRV-ENB-CAC to be met to activate Dynamic
ACB based on the number of RRC Connection in the eNB.
retrieved by RTRV-ENB-CAC to be met prior to stopping the
THRESHOLD_DEACTIVATION
barring parameter broadcast in SIB2 based on the number of
RRC Connection in the eNB.
retrieved by RTRV-ENB-CAC to be met prior to disabling the
THRESHOLD_ACB_SKIP_DISABLE
ACB Skip in SIB2 based on the number of RRC Connection in
the eNB.
This parameter configures the guard time that the eNB ACB
activation criteria must be met prior to broadcasting barring
GUARD_TIME_ACTIVATION
parameters in SIB2 based on the number of RRC Connection
in the eNB.
deactivation criteria must be met prior to stopping the barring
GUARD_TIME_DEACTIVATION
parameter broadcast in SIB2 based on the number of RRC
Connection in the eNB.
GUARD_TIME_ACB_SKIP_DISABLE criteria must be met prior to disabling the ACB skip in SIB2
based on the number of RRC Connection in the eNB.
GUARD_TIME_EMERGENCY_BARRING criteria must be met prior to apply barring to emergency calls
based on the number of RRC Connection in the eNB.
This parameter configures the maximum barring factor that is
the most restrictive for the corresponding Dynamic ACB load
MAX_BARRING_FACTOR type. As the definition in TS36.311 for barring factor in SIB2,
MAX_BARRING_FACTOR should be equal or less than
MIN_BARRING_FACTOR.

Confidential
This parameter configures the minimum barring factor that is

the least restrictive for the corresponding Dynamic ACB load
MIN_BARRING_FACTOR type. As the definition in TS36.311 for barring factor in SIB2,
MIN_BARRING_FACTOR.
This parameter configures the maximum barring time for the
MAX_BARRING_TIME corresponding Dynamic ACB load type. Refer to the definition
in TS36.311 for barring time in SIB2.
This parameter configures the minimum barring time for the
MIN_BARRING_TIME corresponding Dynamic ACB load type. Refer to the definition
This parameter configures the amount by which the barring
STEP_BARRING_FACTOR_INCREASE factor is dynamically adjusted to be more restrictive when
Dynamic ACB is activated for the corresponding load type.
STEP_BARRING_FACTOR_DECREASE factor is dynamically adjusted to be less restrictive when
STEP_BARRING_TIME_INCREASE time is dynamically adjusted for increasing when Dynamic ACB
is activated for the corresponding load type.
STEP_BARRING_TIME_DECREASE time is dynamically adjusted for decreasing when Dynamic
ACB is activated for the corresponding load type.
This parameter configures the guard time that the ACB criteria
SPECIAL_AC_BARRING_ENABLED must be met prior to apply barring to Special ACs for the
corresponding Dynamic ACB load type.
GUARD_TIME_SPECIAL_AC_BARRING must be met prior to apply barring to Special ACs for the
Parameter Description of CHG-ENBACB-RATE/RTRV-ENBACB-RATE

DYNAMIC_BARRING_USAGE Barring) based on the RRC Connection Request Rate in the
eNB.
lowering the load.
the load.
This parameter configures the threshold to be met to activate
THRESHOLD_ACTIVATION Dynamic ACB based on the RRC Connection Request Rate
per second in the eNB.
This parameter configures the threshold to be met prior to
THRESHOLD_DEACTIVATION stopping the barring parameter broadcast in SIB2 based on the
RRC Connection Request Rate per second in the eNB.
THRESHOLD_ACB_SKIP_DISABLE disabling the ACB Skip in SIB2 based on the RRC Connection
Request Rate per second in the eNB.

Confidential
parameters in SIB2 based on the RRC Connection Request
Rate in the eNB.
This parameter configures the guard time that the ACB
parameter broadcast in SIB2 based on the RRC Connection
Request Rate in the eNB.
GUARD_TIME_ACB_SKIP_DISABLE must be met prior to disabling the ACB Skip in SIB2 based on
the RRC Connection Request Rate in the eNB.
GUARD_TIME_EMERGENCY_BARRING must be met prior to apply barring to emergency calls based on
the RRC Connection Request Rate in the eNB.
MIN_BARRING_FACTOR.
MIN_BARRING_FACTOR.

Confidential
Parameter Description of CHG-CELLACB-RRC/RTRV-CELLACB-RRC

This parameter is the cell number to identify each cell. This
CELL_NUM value must not exceed the maximum number of cells supported
by the system.
This parameter is the ON/OFF of Dynamic ACB based on the
DYNAMIC_BARRING_USAGE
number of RRC Connection in the Cell.
lowering the load.
the load.
This parameter is the percentage of MAX_CALL_COUNT
THRESHOLD_ACTIVATION retrieved by RTRV-CELL-CAC to be met to activate Dynamic
ACB based on the number of RRC Connection in the Cell.
retrieved by RTRV-CELL-CAC to be met prior to stopping the
THRESHOLD_DEACTIVATION
barring parameter broadcast in SIB2 based on the number of
RRC Connection in the cell.
retrieved by RTRV-CELL-CAC to be met prior to disabling the
THRESHOLD_ACB_SKIP_DISABLE
ACB Skip in SIB2 based on the number of RRC Connection in
the cell.
This parameter configures the guard time that the cell ACB
parameters in SIB2 based on the number of RRC Connection
in the Cell.
parameter broadcast in SIB2 based on the number of RRC
Connection in the Cell.
GUARD_TIME_ACB_SKIP_DISABLE criteria must be met prior to disabling the ACB skip in SIB2
based on the number of RRC Connection in the Cell.
GUARD_TIME_EMERGENCY_BARRING criteria must be met prior to apply barring to emergency calls
based on the number of RRC connection in the cell.
MIN_BARRING_FACTOR.
MIN_BARRING_FACTOR.

Confidential

Parameter Description of CHG-CELLACB-RATE/RTRV-CELLACB-RATE

by the system.
DYNAMIC_BARRING_USAGE Barring) based on the RRC Connection Request Rate in the
Cell.
lowering the load.
the load.
THRESHOLD_ACTIVATION Dynamic ACB based on the RRC Connection Request Rate
per second in the cell.
RRC Connection Request Rate per second in the cell.
Request Rate per second in the cell.
This parameter configures the guard time that the Cell ACB
parameters in SIB2 based on the RRC Connection Request
Rate in the cell.
parameter broadcast in SIB2 based on the RRC Connection
Request Rate in the cell.

Confidential
GUARD_TIME_ACB_SKIP_DISABLE must be met prior to disabling the ACB Skip in SIB2 based on
the RRC Connection Request Rate in the cell.
GUARD_TIME_EMERGENCY_BARRING must be met prior to apply barring to emergency calls based on
the RRC Connection Request Rate in the cell.
MIN_BARRING_FACTOR.
MIN_BARRING_FACTOR.
Parameter Description of CHG-ENBACB-REJ/RTRV-ENBACB-REJ

DYNAMIC_BARRING_USAGE Barring) based on the RRC Connection Request Reject Ratio
in the eNB.
lowering the load.

Confidential

the load.
THRESHOLD_ACTIVATION Dynamic ACB based on the RRC Connection Request Reject
Ratio per second in the eNB.
RRC Connection Request Reject Ratio per second in the eNB.
Request Reject Ratio per second in the eNB.
GUARD_TIME_ACTIVATION activation criteria must be met prior to broadcasting barring
parameters in SIB2 for the corresponding load type.
GUARD_TIME_DEACTIVATION deactivation criteria must be met prior to stopping the barring
parameter broadcast in SIB2 for the corresponding load type.
GUARD_TIME_ACB_SKIP_DISABLE must be met prior to disabling the ACB Skip in SIB2 for the
corresponding load type.
GUARD_TIME_EMERGENCY_BARRING must be met prior to apply barring to emergency calls for the
MIN_BARRING_FACTOR.
MIN_BARRING_FACTOR.
This parameter configures on or off to apply barring to Special
SPECIAL_AC_BARRING_ENABLED
AC if the dynamic ACB is not capable of lowering the load.

Confidential
This parameter configures the threshold to be met for RRC
THRESHOLD_RRC_REQUEST_RATE Connection Request Rate in the eNB to validate the load
information for RRC Connection Reject Ratio.
Parameter Description of CHG-CELLACB-REJ/RTRV-CELLACB-REJ

by the system.
DYNAMIC_BARRING_USAGE Barring) based on the RRC Connection Request Reject Ratio
in the cell.
lowering the load.
the load.
THRESHOLD_ACTIVATION Dynamic ACB based on the RRC Connection Request Reject
Ratio per second in the cell.
RRC Connection Request Reject Ratio per second in the cell.
Request Reject Ratio per second in the cell.
GUARD_TIME_ACTIVATION activation criteria must be met prior to broadcasting barring
parameters in SIB2 for the corresponding load type.
GUARD_TIME_DEACTIVATION deactivation criteria must be met prior to stopping the barring
parameter broadcast in SIB2 for the corresponding load type.
GUARD_TIME_ACB_SKIP_DISABLE must be met prior to disabling the ACB Skip in SIB2 for the
GUARD_TIME_EMERGENCY_BARRING must be met prior to apply barring to emergency calls for the
MIN_BARRING_FACTOR.
MIN_BARRING_FACTOR.

Confidential

This parameter configures on or off to apply barring to Special
SPECIAL_AC_BARRING_ENABLED
AC if the dynamic ACB is not capable of lowering the load.
This parameter configures the threshold to be met for RRC
THRESHOLD_RRC_REQUEST_RATE Connection Request Rate in the cell to validate the load
information for RRC Connection Reject Ratio.
Parameter Description of CHG-ACB-SPECIALAC/RTRV-ACB-SPECIALAC

CELL_NUM value must not exceed the maximum number of cells
supported by the system.
This parameter indicates SIB2 access class barring of
Signalling AC 11-15 for Dynamic ACB. The index 0 is for AC
11, the index 1 is for AC 12, and so on.
BARRING_FOR_SPECIAL_AC_SIGNALLING[5] • TRUE: Signalling access class x barred for Dynamic ACB
(x: 11 - 15).
• FALSE: Signalling access class x not barred for Dynamic
ACB (x: 11 - 15).
This parameter indicates SIB2 access class barring of Data
AC 11-15 for Dynamic ACB. The index 0 is for AC 11, the
index 1 is for AC 12, and so on.
BARRING_FOR_SPECIAL_AC_DATA[5] • TRUE: Data access class x barred for Dynamic ACB (x:
11 - 15).
• FALSE: Data access class x not barred for Dynamic ACB
(x: 11 - 15).

Confidential
Counters and KPIs

The following table outlines the main counters associated with this feature.
ACCESS_CLASS_BARRING AcbSkipDisabled The cumulated number of times that ACB
(Access Class Barring) SKIP is disabled in
the cell by the dynamic ACB.
EmergencyCallBarred The cumulated number of times that
Emergency Calls are barred in the cell by
the dynamic ACB.
BarringEmergencyCallPerInterval The cumulated number of times that
accessBarringEmergencyCall is included
in SIB2 in the cell. This number is
increased by 1 every barring update
interval by the dynamic ACB if
accessBarringEmergencyCall is included.
BarringMoSignalPerInterval The cumulated number of times that ac-
BarringForMO-Signalling is included in
SIB2 in the cell. This number is increased
by 1 every barring update interval by the
dynamic ACB if ac-BarringForMO-
Signalling is included.
BarringMoDataPerInterval The cumulated number of times that ac-
BarringForMO-Data is included in SIB2 in
the cell. This number is increased by 1
every barring update interval by the
dynamic ACB if ac-BarringForMO-Data is
included.
SpecialAc11Barred The cumulated number of times that
Special AC 11 is barred in the cell by the
Dynamic ACB.
Dynamic ACB.
Dynamic ACB.
Dynamic ACB.
Dynamic ACB.
REFERENCE
Resource Control (RRC) protocol specification Section 6.3.1

Confidential
LTE-SW2103, UL Congestion Prevention

INTRODUCTION
In a network with a limited backhaul bandwidth, the packets can be discarded at
eNB or at an intermediate node due to small buffer size or rate mismatch. The
network may be congested when an operator constrains the UL backhaul
bandwidth of eNB that is connected to a narrow bandwidth backhaul network. In
this case, the eNB reduces the overall amount of UL packets generated at UEs by
throttling down UL resource allocation. In such scenario, the eNB controls UL
UE-Aggregate Maximum Bit Rate (AMBR) internally depending on the queue
length of the outgoing network scheduler. If the number of packets in buffer
increases over a threshold, the eNB will decreases UL UE-AMBR of UEs.
Consequently, the radio scheduler will reduce the amount of allocated radio
resources in proportion.
BENEFIT
• Operators can prevent UL packets from being discarded at eNB due to UL
backhaul congestion.
• Delayed UL packet transmission can be one way to initiate a flow control at
application layer.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The eNB controls congestion toward the UL by recalculating UE-AMBR
parameter using adjustment factor (R) value if packets are discarded due to
congestion in UL backhaul section. The detailed procedure is as follows.
The following figure depicts the overall functional architecture for UL congestion
prevention. The eNB internally classifies UL packets into different queues.
Packets from bearers with a specific QCI are sent to a separate queue. Queues that
serve GBR bearers have a higher priority and their packets are transmitted before
the packets in the queues that serve Non-GBR bearers. If the number of packets in
one of the queues for non-GBR bearers increases over a threshold, the eNB re-

Confidential
calculates Rate Adjustment Factor (R) and sends it to UL scheduler.
Packet Drop
When the amount of packet data exceeds the eNB’s buffer capacity, a packet drop
occurs. To prevent packet drops, an eNB executes the UL flow control function or
the UL congestion prevention function.
The eNB periodically monitors the number of packets piled up in the UL buffer of
the eNB and, when the UL traffic exceeds the threshold (Low_Threshold), it
reduces the number of packets that an UE transmits by decreasing the UE-AMBR
value applied to the UE. The table below shows configuration parameters for this
feature (Configured via CHG-BHCGT-PARA command).
Parameter Description State
LOW_THRESHOLD This parameter indicates the minimum volume of the %
buffer that can affect the Rate Adjust Factor.
HIGH_THRESHOLD This parameter indicates the maximum volume of the %
buffer that minimizes the Rate Adjust Factor.
MONITORING_PERIOD The interval at which the Rate Adjust Factor is ms
calculated by measuring the number of packets in the
buffer of the eNB.
MIN_UE_AMBR The minimum UE-AMBR that can be allocated to the Bit
UE when congestion occurs.
MONITORING_STATE The function that enables or disables the UL Enabled or Disabled
congestion prevention function.
RESPONSE_MODE This parameter determines whether the Linear or Non-linear
Response_Mode is linear or non-linear.
If MONITORING_STATE configuration parameter is set to Enabled, the UL flow

Confidential
control periodically monitors the size of packet accumulated in the UL buffer of

eNB. When the UL traffic exceeds the threshold value (LOW_THRESHOLD), the
UL flow control reduces the amount of packet transmitted from UE to eNB by
reducing the value of UE-AMBR, which is applied to the UE.
UL Traffic Control
To control the UL traffic load, the eNB provides the following flow control
functions:
• The eNB periodically measures the size of packet in the buffer of transport
layer. If multiple queues are being used for non-GBR QCIs, the eNB measures
queue length of all buffers. In that case, the largest value is used for
calculation of Rate Adjustment Factor (R).
• If the queue length exceeds the LOW_THRESHOLD value, the eNB
determines the value (R) of UE-AMBR adjustment factor according to the
queue length. The R value is determined between 0 and 1 in decreasing linear
or non-linear values as the queue length increases. If the queue length is less
than the low_threshold value, the R value is set to 1. If the queue length
exceeds the HIGH_THRESHOLD value, the R value is set to 0. The operator
may use system parameters to configure the values of HIGH_THRESHOLD
and LOW_THRESHOLD. The operator can use system parameters to
configure the change rate of R value (Linear or Non-linear.)
• The eNB multiplies the R value by each of UE-AMBRs to determine the
effective UE-AMBR towards uplink, and allocates the UL radio resources to
each of UEs based on this value. In this case, the UE-AMBR towards the DL
direction is not affected. The UL effective UE-AMBR should always be
maintained above MIN_UE_AMBR to ensure the basic service availability for
UE.
Buffer Monitoring
The eNB monitors the queue length (Q_Length) periodically.
• The intervals can be configured with the minimum value of 20 ms.
• The eNB measures the Q_Length and applies re-calculated the rate adjustment
factor (R) value. Thus, based on the Q_Length, UL scheduler schedules
packets considering the modified UE-AMBR.
Linear Function
Linear function determines the rate adjustment factor R based on the Q_Length as
shown below:
• R = 1 if Q_Length < LOW_THRESHOLD
• R = 0 if Q_Length > HIGH_THRESHOLD
Otherwise, the R value is selected in proportion to Q_Length.

Confidential
Non- Linear Function

The Non-linear function determines the rate adjustment factor R based on the
Q_Length as shown below:
• R = 1 if Q_Length < LOW_THRESHOLD
• R = 0 if Q_Length > HIGH_THRESHOLD
Otherwise, the R value is calculated as follows.
SYSTEM OPERATION
How to Activate

Confidential
Preconditions
• The eNB provides the scheduling functions to limit the volume of data
transmitted from the UE when there is a limitation on bandwidth of the uplink
backhaul line.
• If the monitoring state is enabled, perform queue monitoring to determine the
occurrence of backhaul congestion.
• UL Congestion Prevention parameters can be activated using CHG-BHCGT-
PARA command.
• UL Congestion Prevention parameters can be deactivated using CHG-BHCGT-
PARA command.
Key Parameters
feature.
parameters
Parameter Descriptions of CHG-BHCGT-PARA/RTRV-BHCGT-PARA
MONITORING-STATE This parameter indicates to enable the queue monitoring used to determine
whether the backhaul is congested.
• 0: disabled
• 1: enabled
HIGH_THRESHOLD The high threshold of the queue length used to control the uplink traffic. It must be
larger than the low threshold.
LOW_THRESHOLD The low threshold of the queue length used to control the uplink traffic. It must be
less than the high threshold.
MONITORING_PERIOD The interval at which backhaul congestion is monitored in ms. The default is 100
(ms). The target queues are monitored every interval set in this parameter.
MIN_UE_AMBR UL Effective UE-AMBR must a larger than minimum UE-AMBR to guarantee a
basic service availability of UEs.
RESPONSE_MODE This parameter indicates a method to calculate UE-AMBR rate adjustment factor:
• 0: Linear
• 1: Non-linear
Counters and KPIs

with this feature.

Confidential
REFERENCE
None

Confidential
LTE-SW2104, eNB Overload Protection

INTRODUCTION
The eNB Overload Protection feature enables an eNB to limit the maximum
number of call connection requests per unit time to protect CPU from being
overloaded.
BENEFIT
An operator can configure the threshold for RRC connection requests per unit time
in the eNB to protect CPU from being overloaded.
DEPENDENCY
None
LIMITATION
The UE may experience a long setup time during congestion.
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature enables operator to configure the monitoring duration with
MONITORING_PERIOD (CHG-OVLD-PTC). The maximum number of requests
for each RRC establishment cause and PS paging can be configured during
monitoring duration.
• The maximum number of highPriorityAccess calls:
THRESHOLD_FOR_HIGH_PRIORITY_ACCESS_RATE (CHG-OVLD-
PTC).
• The maximum number of mo-Signalling calls:
THRESHOLD_FORMO_SIGNALING_RATE (CHG-OVLD-PTC).
• The maximum number of mo-Data calls: THRESHOLD_FORMO_DATA_RATE
(CHG-OVLD-PTC).
• The maximum number of delayTolerantAccess :
THRESHOLD_FOR_DELAY_TOLERANT_ACCESS_RATE (CHG-OVLD-
PTC).
• The maximum number of PS paging (if paging priority IE is included in the
paging message, the eNB does not discard this message):
THRESHOLD_FOR_PS_PAGING and PS_PAGING_DISCARD_STATUS

Confidential
(CHG-OVLD-PTC).
The emergency and mt-Access calls of RRC establishment causes in

RRCConnectionRequest message are not limited.
EstablishmentCause::= ENUMERATED {
emergency, highPriorityAccess, mt-Access,
mo-Signaling, mo-Data, delayTolerantAccess-v1020, spare2, spare1}
When this feature is active, the eNB:

• Observes the number of call requests per RRC establishment cause and the
number of PS paging for the monitoring duration
• Discard the RRC connection request with a specific RRC establishment cause
if the corresponding count exceeds the maximum number of call requests for
the establishment cause or PS paging message.
• Initializes all counters for RRC establishment causes and PS paging messages,
when the monitoring timer expires. The eNB then begins to count up during
the next monitoring time period. When the counter reaches the configured
maximum limit, the eNB discards the additional requests.
Operation Details
This section provides detailed overview of the operation procedure.
Establishment Cause-based Protection Procedure
• The maximum number of call connection requests per unit time can be set as a
system parameter for each RRC establishment cause except an emergency and
mt-Access.
• The eNB monitors the number of call connection requests for each RRC
establishment cause during the monitoring period set by the system parameter.
• When an RRC Connection Request message is received from the UE, if the
number of call connection requests has not exceeded the threshold
corresponding to the RRC establishment cause included in the RRC
Connection Request message, the call connection request is accepted;
however, if the count exceeds the threshold, the call connection request is not
accepted.
• If the monitoring period set by the system parameter has expired, the eNB
initializes the count of call connection requests for each RRC establishment
cause.
• The RRC establishment cause can be used by the network to prioritize the
connection establishment request from the UE at the high load situation in the
network.
Paging Based Protection Procedure
• The maximum number of paging processes per unit time can be set in the
system parameter.

Confidential
• The number of paging requests is monitored during the monitoring period set
by the system parameter.
• If the number of paging requests received from the MME has not yet exceeded
the threshold, the paging message is processed. When the requests exceeds the
threshold, further paging requests are ignored.
• If paging priority IE is included in the paging message received from the
MME, the eNB does not discard this message.
• If the monitoring period set by the system parameter has expired, the paging
request count is initialized.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-OVLD-PTC and set OVERLOAD_PROTECT_CTRL to control 1 or
2 to protect UE establishment
• Run CHG-NBOVLD-PTC and set OVERLOAD_PROTECT_CTRL to control 1
or 2 to protect UE establishment:
o ProtectPerNormalCall: number of Normal Call based Overload Protection
(control 1)
o ProtectPerEstablishCause: Establish Cause based Overload Protection
(control 2)
• Run CHG-OVLD-PTC and set PS_PAGING_PROTECT_USAGE to USE to
restrict paging.
• Run CHG-NBOVLD-PTC and set PS_PAGING_PROTECT_USAGE to USE to
restrict paging.
• Run CHG-OVLD-PTC and set OVERLOAD_PROTECT_CTRL to nouse to
allow UE establishment.
• Run CHG-NBOVLD-PTC and set OVERLOAD_PROTECT_CTRL to nouse to
allow UE establishment.
• Run CHG-OVLD-PTC and set PS_PAGING_PROTECT_USAGE to NO_USE
to allow paging.
• Run CHG-NBOVLD-PTC and set PS_PAGING_PROTECT_USAGE to

Confidential
NO_USE to allow paging.
Key Parameters
feature.
parameters.
Parameter Descriptions of CHG-OVLD-PTC/RTRV-OVLD-PTC
MONITORING_PERIOD Monitoring period
OVERLOAD_PROTECT_CTRL Setting Value for Overload Protect.
• 0: noUse
• 1: ProtectPerNormalCall
• 2: ProtectPerEstablishCause
THRESHOLD_FOR_NORMAL_CALL It is threshold for Normal call.
THRESHOLD_FOR_HIGH_PRIORITY HighPriorityAccess limit on the ratio of ProtectPerEstablishCause.
_ACCESS_RATE Threshold of call connection is calculated by multiply of the
thresholdForNormalCall and thresholdForHighPriorityAccessRate.
THRESHOLD_FORMO_SIGNALING_ mo-Signal limit on the ratio of ProtectPerEstablishCause. Threshold
RATE of call connection is calculated by multiply of the
thresholdForNormalCall and thresholdFormoSignalingRate.
THRESHOLD_FORMO_DATA_RATE mo-Data limit on the ratio of ProtectPerEstablishCause. Threshold of
call connection is calculated by multiply of the
thresholdForNormalCall and thresholdFormoDataRate.
THRESHOLD_FOR_DELAY_TOLERA DelayTolerantAccess limit on the ratio of ProtectPerEstablishCause.
NT_ACCESS_RATE Threshold of call connection is calculated by multiply of the
thresholdForNormalCall and thresholdForDelayTolerantAccessRate.
PS_PAGING_PROTECT_USAGE Whether to execute psPaging Protect function
THRESHOLD_FOR_PS_PAGING It is threshold for psPaging
PS_PAGING_DISCARD_USAGE Whether to discard PS Paging msg by CPU Status
PS_PAGING_DISCARD_STATUS CPU status for PS Paging Discard
Parameter Descriptions of CHG-NBOVLD-PTC/RTRV-NBOVLD-PTC

MONITORING_PERIOD Monitoring period
OVERLOAD_PROTECT_CTRL Setting Value for Overload Protect.
• 0: noUse
• 1: ProtectPerNormalCall
• 2: ProtectPerEstablishCause
THRESHOLD_FOR_NORMAL_CALL It is threshold for Normal call.
THRESHOLD_FORMO_SIGNALING_ mo-Signal limit on the ratio of ProtectPerEstablishCause. Threshold
RATE of call connection is calculated by multiply of the
thresholdForNormalCall and thresholdFormoSignalingRate.
THRESHOLD_FORMO_DATA_RATE mo-Data limit on the ratio of ProtectPerEstablishCause. Threshold of

Confidential
call connection is calculated by multiply of the
thresholdForNormalCall and thresholdFormoDataRate.
ACT_SELECTIVE_PAGING_DISCAR This parameter decides whether S1AP Paging message including
D Paging Priority IE should not be discarded when PS Paging Discard
State.
PS_PAGING_PROTECT_USAGE Whether to execute psPaging Protect function
THRESHOLD_FOR_PS_PAGING It is threshold for psPaging
PS_PAGING_DISCARD_USAGE Whether to discard PS Paging msg by CPU Status
PS_PAGING_DISCARD_STATUS CPU status for PS Paging Discard
Counters and KPIs

DENIED_CALL Denied_HighPriorit Number of high priority access-type calls
yAccess denied by the overload protection function
Denied_moSignali Number of MO signaling-type calls denied by
ng the overload protection function
Denied_moData Number of MO data-type calls denied by the
overload protection function
Denied_DelayToler Number of delay tolerant access calls denied
antAccess by the overload protection function
Denied_Paging Number of paging messages denied by the
overload protection function
NB_IOT_DENIED_CALL NBIoT_Denied_mo The number of MO Signaling calls that are
Signaling denied due to the overload prevention function
for NB-IoT
NBIoT_Denied_mo The number of MO Data calls that are denied
Data due to the overload prevention function for NB-
IoT
Denied_Paging The number of paging message that are
dumped by the overload prevention function
for NB-IoT
REFERENCE
Resource Control (RRC) protocol specification.

Confidential
LTE-SW2106, Delay Tolerant Access Processing

for eNB Overload Control
INTRODUCTION
Low priority UEs sets the Delay Tolerance Access bit in the RRC Connection
Request message from 3GPP Rel-10. When the network becomes congested, an
eNB rejects or releases the RRC connection with the ExtendedWaitTime period.
The UE can retry connecting to the network after the expiration of the
ExtendedWaitTime.
BENEFIT
• The eNB reduces the amount of signaling.
• The eNB uses the available radio resources for high priority UEs effectively.
DEPENDENCY
• Interface & Protocols: The MME should support 3GPP Release 10 S1
interface.
• Others: Low priority UEs (Release 10) need to implement
DelayTolerantAccess as part of the EstablishmentCause parameter, which is
sent in RRCConnection Setup message.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
When the network gets congested, traffic needs to be reduced and the eNB should
make effective use of available radio resources. To use resources effectively
during peak traffic, the network needs to identify priority UEs for which resources
are to be allocated. It is up to the scope of the operator to configure low-priority
UEs like Machine Type Communication (MTC) and other devices.
Figures below depict the overload control mechanism for LTE and Cat.NB.
LTE

Confidential
UE E-UTRAN MME
1) In case CPU load level is Normal or Minor

RRC Connection Request extendWaitTime IE is included in RRC connection Reject by
{EstablishmentCause=DelayTolerance} - eNB Overload Protection feature
RRC Connection Reject 2.1) Incase PLD OverloadProtectInfo::

w/extendedWaitTime IE extendedWaitTimeEnable=On, extenedWaitTime IE is included
in RRC Connection Reject by
- UE capacity based CAC
- MME Overload Start w/Overload Action {Reject delay tolerant
RRC ConnectionSetup access}
RRC ConnectionSetup Complete
RRC Connection Release 2.2) In case CPU load level is Major or Critical,
w/extendedWaitTime IE extenedWaitTime IE is included in RRC Connection Release by
call release event.
Initial UE message

w/extendedWaitTime IE 2.3) In case CPU load level is Major or Critical,
extenedWaitTime IE is included in RRC Connection Release by
call release event.
Cat.NB
UE E-UTRAN MME
RRC Connection Request-NB 1) In case CPU load level is Normal or Minor

extendWaitTime IE is included in RRC connection Reject by
{EstablishmentCause=DelayTolerance} - eNB Overload Protection feature
RRC Connection Reject-NB 2.1) extenedWaitTime IE is included in RRC Connection Reject by
w/extendedWaitTime IE - UE capacity based CAC
- MME Overload Start w/Overload Action {Reject delay tolerant
access}
RRC ConnectionSetup-NB
RRC ConnectionSetup Complete-NB
RRC Connection Release-NB 2.2) In case CPU load level is Major or Critical,
w/extendedWaitTime IE extenedWaitTime IE is included in RRC Connection Release by
call release event.
Initial UE message
RRC Connection Release-NB

w/extendedWaitTime IE 2.3) In case CPU load level is Major or Critical,
extenedWaitTime IE is included in RRC Connection Release by
call release event.
0) A low priority UE configured by the operator informs the eNB during RRC
Confidential
Connection Establishement procedure that it is delayTolerantAccess UE by setting

the parameter EstablishmentCause= DelayTolerantAccess as per 3GPP TS36.331.
1) When the eNB does not accept this UE due to UE capacity based CAC or MME
Overload Start with overload action=Reject delay tolerant access upon reception of
RRC Connection Request, it responds with RRC Connection Reject.
When sending the normal RRCConnection Reject to low priority UE, the eNB sets
the ExtendedWaitTime IE indicating to low priority UE that it can retry to connect
after the expiry of the ExtendedWaitTime. The ExtendedWaitTime is set by using
EXTENDED_WAIT_TIME (CHG-TIMER-INF) if
EXTENDED_WAIT_TIME_ENABLE (CHG-OVLD-PTC) parameter is set as 1
(ON).
2) When the eNB does not accept this UE due to Capacity based CAC upon
reception of RRC Connection Setup Complete, it responds with RRC Connection
Release.
At this time, if the load level of CPU is Major or Critical, then the eNB sets IE
ExtendedWaitTime in RRCConnection Release by using
EXTENDED_WAIT_TIME (CHG-TIMER-INF). ExtendedWaitTime indicates to
low priority UE to retry to connect to the network after the expiry of the
ExtendedWaitTime.
RRC Connection Request sent by UE

RRCConnectionRequest-r8-IEs ::= SEQUENCE {
ue-Identity InitialUE-Identity,
establishmentCause EstablishmentCause,
spare BIT STRING (SIZE (1))
}
EstablishmentCause ::= ENUMERATED {
emergency, highPriorityAccess, mt-Access, mo-Signalling,
mo-Data, delayTolerantAccess-v1020, spare2, spare1}
RRC Connection Reject sent by eNB

i) RRCConnectionReject-v1020-IEs ::= SEQUENCE {
extendedWaitTime-r10 INTEGER (1..1800) OPTIONAL, -- Need ON
nonCriticalExtension SEQUENCE {} OPTIONAL -- Need OP
}
RRCConnectionRelease-v1020-IEs ::= SEQUENCE {
extendedWaitTime-r10 INTEGER (1..1800) OPTIONAL, -- Need ON
nonCriticalExtension SEQUENCE {} OPTIONAL -- Need OP
}
extendedWaitTime
Value in seconds for the wait time for Delay Tolerant access requests.
ii) For Overload Detection in Capacity, Air Link Control and Backhaul Link Interfaces and System Parameters
to control this feature, Please Refer to LTE-SW4101 Capacity based Call Admission Control and LTE-SW2103
UL Congestion Prevention for details.

Confidential
Overload Start sent by Core Network (MME)

Table below describes the Overload Response IE content.
description
CHOICE - - - -
Overload
Response
> Overload Action - - - -
>> Overload M 9.2.3.20 -
Action
Overload Action M - ENUMERATED (Reject RRC connection -
establishments for non-emergency MO DT,
Reject RRC connection establishments for
Signaling, Permit Emergency Sessions and
mobile terminated services only, …, Permit
High Priority Sessions and mobile terminated
services only, Reject delay tolerant access)
For system parameters to control this feature, see LTE-SW4101, Capacity based
Call Admission Control and LTE-SW0503, MME Overload Control for details.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-OVLD-PTC and set EXTENDED_WAIT_TIME_ENABLE to ON to
provide extended wait time to the delayTolerantAccess call.
• Run CHG-OVLD-PTC and set EXTENDED_WAIT_TIME_ENABLE to OFF.
Key Parameters
feature.
parameters.
Parameter Description of CHG-OVLD-PTC/RTRV-OVLD-PTC

Confidential
EXTENDED_WAIT_TIME_EN This parameter is used to select whether to insert extendedWaitTime field or
ABLE not when Delay Tolerant Access establishment is rejected by overload
protection or MME overload control.
Parameter Description of CHG-TIMER-INF/RTRV-TIMER-INF

EXTENDED_WAIT_TIME This parameter is extended waitTime value for delayTolerantaccess call. It is
the information to set waitTime of the call when the call established, whose
EstablishmentCause value is delayTolerantaccess in RrcConnectionRequest
message is rejected in eNB. The UE transmits RrcConnectionRequest again
after extended waitTime. A sufficiently large value must be guaranteed for the
extended waitTime-value of a delayTolerantaccess call to give a connection
priority to another UE. This parameter is the second unit timer value, not like
other timers (a default value is recommended).
[Related Specifications] 3GPP TS 36.331 [6.2.2 RrcConnectioinReject]
Counters and KPIs

with this feature.
REFERENCE
description; Stage 2. Release 10 & 11.
Resource Control (RRC) protocol specification. Release 10 & 11.
Application Protocol (S1AP). Release 10 & 11.

Confidential
LTE-SW2107, MME Overload Protection

INTRODUCTION
The MME Overload Protection feature protects an MME from an overload
situation, by reducing the thresholds used for allowing a new call attempt, which
are configured for LTE-SW2104, eNB Overload Protection feature. Possible
scenarios are: when an eNB reboots or when all S1 interfaces are out of service
and then if any one of the S1 interface comes up.
BENEFIT
This feature prevents massive connection requests on MME abruptly when the
MME or the eNB recovers from failure, shutdown, or reboot.
DEPENDENCY
• Prerequisite Features: The LTE-SW2104, eNB Overload Protection feature
must be activated to use this feature.
• Others: This feature can limit the number of call attempts after eNB reboots,
and therefore, some UEs can experience longer network access time at that
moment.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The protective mechanism is implemented by reducing the RRC attempt threshold
in unit time to a fraction of normal threshold level. At the time when S1
connection is set up, the fraction is set to the configured initial value based on
mmeOverloadStartupControlThreshold (CHG-OVLD-PTC). The
fraction increases by a configured ramping step
{mmeOverloadStartupIncreasePortion (CHG-OVLD-PTC) } at every
configured period {mmeOverloadstartupStepTime (CHG-OVLD-PTC) }
until it reaches 100 %. This procedure is repeated until the RRC attempt threshold
reaches the normal threshold limit.
For instance, considering the following scenario when the normal threshold of
RRC attempt per sec is 160:
• Startup threshold ratio: 50 %

Confidential
• Period for increase: 60 s

• Increase ratio: 10 %
Figure below depicts an example with the parameters above.
SYSTEM OPERATION
provides associated key parameters to customize the configuration settings.
How to Activate
Preconditions
• Run CHG-OVLD-PTC and set mmeOverloadProtection to use.
• Run CHG-OVLD-PTC and set mmeOverloadProtection to no_use.
Key Parameters

Confidential
parameters.
mmeOverloadProtection This parameter indicates whether to perform MME overload protection for s1
signaling.

mmeOverloadProtection This parameter indicates whether to perform MME overload protection for s1
signaling in NB-IoT eNB.
parameters.
mmeOverloadProtection This parameter indicates whether to perform MME overload protection for S1
signaling.
mmeOverloadStartupCo This parameter is the threshold approved after first time of which at least S1
ntrolThreshold connection is set up with the MME.
mmeOverloadstartupSte This parameter is the increasing unit time ratio gradually in MME overload
pTime protection function.
mmeOverloadStartupInc This parameter is the increasing threshold ratio gradually in MME overload
reasePortion protection function.

mmeOverloadProtection This parameter indicates whether to perform MME overload protection for S1
signaling in NB-IoT eNB.
mmeOverloadStartupCo This parameter is the threshold approved after the first time of which at least one
ntrolThreshold S1 connection is set up with the NB-IoT supportable MME for NB-IoT eNB.
mmeOverloadstartupSte This parameter is the increasing unit time ratio gradually in MME overload
pTime protection function for NB-IoT eNB.
mmeOverloadStartupInc This parameter is the increasing threshold ratio gradually in MME overload
reasePortion protection function for NB-IoT eNB.
Counters and KPIs

Denied Call by Overload Denied_HighPriorityAccess The number of priority access calls that are denied
Protection due to the overload prevention function.

Confidential

Denied_moSignaling The number of MO signaling calls that are denied
due to the overload prevention function.
Denied_moData The number of MO data calls that are denied due to
the overload prevention function.
Denied_DelayTolerantAcce The statistics that counts the number of
ss DelayTolerantAccess calls that are denied due to
the overload prevention function.
Denied Call by Overload NBIoT_Denied_moSignalin The number of mo Signaling calls that are denied
Protection for NB-IoT g due to the overload prevention function for NB-IoT.
The number of mo Data calls that are denied due to
NBIoT_Denied_moData
the overload prevention function for NB-IoT.
The number of paging message that are dumped by
NBIoT_Denied_Paging
overload protection function for NB-IoT.
REFERENCE

Confidential
LTE-SW2108, Smart Congestion Mitigation

INTRODUCTION
Up to 3GPP Release 11, MMTel voice access is controlled by both Access Class
Barring (ACB) and Service Specific Access Control at the same time. As a result,
an operator cannot control MMTel voice access separated from data access. From
the 3GPP Release 12, using Smart Congestion Mitigation, the eNB can provide
three bits in SIB2 to indicate whether MMTel voice, MMTel video and SMS UEs
skip the ACB check. The operator can control MMTel voice access separated from
data access and prioritize MMTel voice access over data access. These three-bit
ACB skip indicators can be delivered to UEs per PLMN.
BENEFIT
Operators can prioritize MMTel voice, MMTel video and SMS access attempts
over other data packet services.
DEPENDENCY
Others: The UE should support Smart Congestion Mitigation.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
To allow UE to skip ACB for specific application such as mobile originating
MMTELVoice, MMTELVideo, or SMS, the eNB can broadcast three ACB skip
indicators in SIB2 in accordance with system configuration. Operator can
configure each indicator by setting AC_BARRING_SKIP_FOR_MMTEL_VOICE,
AC_BARRING_SKIP_FOR_MMTEL_VIDEO, and
AC_BARRING_SKIP_FOR_MMTEL_SMS configuration parameters to TRUE by
using CHG-BARCOM-PARA/CHG-BARPLMN-PARA. When the UE tries to
establish RRC connection for specific application, UE checks relevant ACB skip
indicator and considers access to the cell as not barred if ACB skip indicator for
relevant application is set.
Figure below depicts an example of ACB skip operation for a mobile originating
MMTELVoice.

Confidential
Using Smart Congestion Mitigation, the operator can allow access of specific
applications while blocking packet data service at the congestion situation as
depicted in the following figure.
SYSTEM OPERATION
How to Activate
Preconditions
Access barring feature should be enabled by setting BARRING_CTR_USAGE to
• Run CHG-BARCOM-PARA and set
AC_BARRING_SKIP_FOR_MMTEL_VOICE to 1.
AC_BARRING_SKIP_FOR_MMTEL_VIDEO to 1.
• Run CHG-BARCOM-PARA and set AC_BARRING_SKIP_FOR_MMTEL_SMS
to 1.
To activate PLMN specific smart congestion control, do the following:

Confidential

• Run CHG-BARPLMN-PARA and set
AC_BARRING_SKIP_FOR_MMTEL_SMS to 1.
• Run CHG-BARCOM-PARA and set AC_BARRING_SKIP_FOR_MMTEL_SMS
to 0.
To deactivate PLMN specific smart congestion control, do the following:
barringOff.
Key Parameters
feature.
parameters.
Parameter Descriptions of CHG-BAR-PARA/RTRV-BAR-PARA
AC_BARRING_SKIP_FOR_M This parameter indicates to enable/disable skipping of Access Class Barring
MTEL_VOICE (Mo-Sig, Mo-Data) procedure when MMTEL Voice is used.
• False (0): do not skip Access Class Barring (Mo-Sig, Mo-Data) procedure.
MTEL_VIDEO (Mo-Sig, Mo-Data) procedure when MMTEL Video is used.
MTEL_SMS (Mo-Sig, Mo-Data) procedure when SMS is used.

Confidential

MTEL_VOICE (Mo-Sig, Mo-Data) procedure when MMTEL Voice is used.
• False: do not skip Access Class Barring (Mo-Sig, Mo-Data) procedure.
MTEL_VIDEO (Mo-Sig, Mo-Data) procedure when MMTEL Video is used.
MTEL_SMS (Mo-Sig, Mo-Data) procedure when SMS is used.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TR 36.848 Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); Study on smart congestion mitigation
Radio Resource Control (RRC); Protocol specification (Release 12)

Confidential
LTE-SW2109, Application Specific Congestion

Control for Data Communication
INTRODUCTION
Access control prevents UEs in a cell from attempting a connection initiation when
a cell is overloaded or congested. 3GPP has defined multiple access control
mechanisms such as Access Class Barring (ACB), Service Specific Access Control
(SSAC), and Extended Access Barring (EAB). However, they do not differentiate
services or applications. In release 13, a new access control mechanism,
Application specific Congestion control for Data Communication (ACDC), is
defined to allow or prohibit connection initiation of operator-defined applications
in the UE.
BENEFIT
The operator can differentiate operator-defined services or applications in the UE
when the feature controls access attempt.
DEPENDENCY
Others: The UE should support ACDC capability (Release 13).
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The ACDC feature can apply separate access control parameters for each
application group categorized by ACDC category, while existing access control
mechanism, ACB, applies same access control parameters to all normal UEs
regardless of the importance of application initiates connection request. The
feature controls attempt from the UE to initiate connection to eNB. Therefore, it is
applicable to UEs in idle mode only. If both ACDC and ACB controls are
indicated, ACDC overrides ACB.
The categorization of application groups is out of the scope of 3GPP standard and
should be defined by the operator. 3GPP TS 36.331 defines 16 categories from 1
(highest) to 16 (lowest). The highest ACDC category is for least restricted
applications and the lowest ACDC category (or not categorized) is for most
restricted applications.
ACDC categories decision in the UE is vendor-specific and can follow:
Confidential
• Option 1: Upper layers send an App-ID to the EMM layer. The EMM layer
determines the ACDC category applicable to the request based on the
configuration in ACDC MO (managed object) or EFACDC in USIM.
• Option 2: Upper layers can determine and send the ACDC category to EMM
layer.
The ACDC configuration is broadcasted via SIB2. Two configurations of acdc-
BarringForCommon and acdc-BarringPerPLMN-List (maxPLMN = 6) are defined.
When both configurations are provided, per-PLMN parameter has higher priority
than common parameters.
Barring Parameters are as follows.
• plmn-IdentityIndex (only for ACDC-BarringPerPLMN)
• acdc-HPLMNonly (True or False)
• barringPerACDC-CategoryList (maxACDC-Cat = 16)
o Ordered list (highest ACDC category (least restricted) à lowest ACDC
category (most restricted)) of barring information
Barring Information per ACDC category is as follows.
• acdc-CatValue (1 (highest)-16 (lowest))
• acdc-BarringConfig: ac-BarringFactor (0-95 %)
• ac-BarringTime (4-512 sec (8 min 32 sec))
Actual barring time is calculated by ((0.7 + 0.6 * rand) * ac-BarringTime) as

described in 3GPP TS 36.331. (c.f., the rand is a random number uniformly
distributed in the range: 0 ≤ rand < 1.)
The operator can configure barring parameters including barring information for
each ACDC category by using CHG-ACDC-PROFILES.
Samsung eNB supports adaptive (CPU-based) ACDC Barring Control method in
addition to manual method (by setting ACDC_CTR_USAGE to cpuStatusCtrl
by using CHG-CELL-ACS). When adaptive control is used, broadcasted ACDC
barring parameters are adaptively changed according to CPU overload status
(Normal, Minor, Major, and Critical). For this operation, the operator can
configure five sets of ACDC barring parameters for manual control and for each
CPU overload status (Normal, Minor, Major, and Critical). The operator can
configure each ACDC profile by using CHG-ACDC-PROFILES and can set a
specific ACDC profile to one of barring types (that is, barManual, cpuNormal,
cpuMinor, cpuMajor, or cpuCritical) by using CHG-ACDCCOM-PARA.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
• To activate this feature, do the following:
o Run CHG-CELL-ACS and set ACDC_CTR_USAGE to manualCtrl or
cpuStatusCrl.
o Run CHG-ACDC-PROFILES and configure the ACDC parameters at one
of the PROFILE_ID, and set PROFILE_USAGE to USED for the
PROFILE_ID.
o Run CHG-ACDCCOM-PARA and set ACDC_PROFILE_ID, which is
configured as USED, for the cell and cpuNormal, cpuMinor,
cpuMajor, cpuCritical, and cpuManual.
• To activate PLMN specific ACDC, do the following additionally:
o Run CHG-ACDCPLMN-PARA, and set ACDC_PROFILE_ID, which is
configured as USED for the cell, and the PLMN and cpuNormal,
cpuMinor, cpuMajor, cpuCritical, and cpuManual.
To deactivation this feature, do either of the following:
• Run CHG-CELL-ACS and set ACDC_CTR_USAGE to barringOff.
• Run CHG-ACDC-PROFILES, and set PROFILE_USAGE to no_use for all
the PROFILE_ID.
Key Parameters
parameter.
Parameter Description of CHG-CELL-ACS/RTRV-CELL-ACS
ACDC_CTR_USAGE This parameter indicates the ACDC feature control.
• acdcBarringOff: ACDC feature is OFF ACDC barring parameters is not
broadcasted in SIB2
• acdcManualCtrl: Uses the ACDC barring control function manually.
• acdcCpuStatusCtrl: Uses the ACDC barring control function depending on
CPU overload.

Confidential
Parameter Description of CHG-ACDC-PROFILES/RTRV-ACDC-PROFILES

PROFILE_ID This parameter indicates the profileID.
PROFILE_USAGE This parameter indicates whether this profile configured to be used or not.
• CI_no_use: profile not used.
• CI_use: profile can be used
ACDC_HPLMN_ONLY Indicates whether ACDC is applicable for UEs not in their HPLMN for the
corresponding PLMN. TRUE indicates that ACDC is applicable only for UEs in
their HPLMN for the corresponding PLMN. FALSE indicates that ACDC is
applicable for both UEs in their HPLMN and UEs not in their HPLMN for the
corresponding PLMN.
ACDC_CAT_USAGE This parameter indicates whether ACDC is configured and can be used.
• CI_no_use: The corresponding category is not used.
• CI_use: The corresponding category can be used.
ACDC_CAT_PROB_FAC This parameter indicates barring factor for corresponding ACDC Category.
ACDC_CAT_BAR_TIME This parameter indicates barring time for corresponding ACDC Category.
Parameter Description of CHG-ACDCCOM-PARA/RTRV-ACDCCOM-PARA

CELL_NUM This parameter indicates the cell number.
ACDC_BARRING_STATUS_T This parameter is the acdc barring type
YPE • cpuNormal: The CPU of the main card is in Normal state.
ACDC_PROFILE_ID This parameter indicates the profileID.
-1 indicates that the profile is not configured.
Parameter Description of CHG-ACDCPLMN-PARA/RTRV-ACDCPLMN-PARA

CELL_NUM This parameter indicates the cell number.
PLMN_IDX This parameter indicates the PLMN index.
Index 0 is for PLMN Index 1 and so on.
ACDC_BARRING_STATUS_T This parameter is the acdc barring type
YPE • cpuNormal: The CPU of the main card is in Normal state.
ACDC_PROFILE_ID This parameter indicates the profileID.
-1 indicates that the profile is not configured.

Confidential
Counters and KPIs

with this feature.
REFERENCE
Radio Resource Control (RRC); Protocol specification (Release 13)
Equipment (UE) procedures in idle mode (Release 13)
Equipment (UE) radio access capabilities (Release 13)
[4] 3GPP TS 24.105 Application specific Congestion control for Data
Communication (ACDC) Management Object (MO) (Release 13)
[5] 3GPP TS 22.011 Service accessibility (Release 13)
[6] 3GPP TR 22.806 Study on Application-Specific Congestion Control for Data
Communication (Release 13)

Confidential
LTE-SW2301, Resource Pooling between Cells

INTRODUCTION
This feature groups cells of the same DSP and enables UE&DRB capacity to be
shared among cells of the pooling group.
BENEFIT
• Increases the maximum number of UE capacity of a cell, for example, 600
RRC connected UEs/cell to 900 RRC connected UEs/cell.
• Increases the maximum number of DRB capacity of a cell, for example, 1800
bearers/cell to 2700 bearers/cell.
DEPENDENCY
• HW dependency: LCC
LIMITATION
• The cells of the pooling group must belong to the same DSP.
• The eMTC UE capacity is excluded from this feature.
• 5 MHz UE capacity is excluded from this feature.
SYSTEM IMPACT
capabilities.
None
• Number of RRC_CONNECTED UEs: The maximum number of
RRC_CONNECTED UEs in a cell increases.
• Number of DRBs: The maximum number of DRBs in a cell increases.
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
The feature has the following three main functions:
• Cell Grouping
• RRC connected UE Pooling
• DRB Pooling
Cell Grouping
The purpose of this function is to pool the UE capacity and the DRB capacity in a
pooling group (POOLING_GROUP_ID). The cells of a pooling group are selected
by the operator, but cells of the same group should belong to the same DSP. The
capacity of the pooling group is depends on the number of cells of the pooling
group.
RRC connected UE Pooling

The purpose of this function is to increase the maximum UE capacity of a cell. The
maximum number of UEs per cell increases up to 900.
DRB Pooling
The purpose of this function is to increase the maximum DRB capacity of cells in
the group. The maximum number of DRBs per cell increases up to 2,700.
Functional Operation of UE Pooling

UE
• The number of UEs in a cell and the number of UEs in a group are controlled
by the Call Admission Control (CAC).
• When the number of UEs in the cell exceeds the normal capacity (for example,
600 UEs), the cell is converted to the greedy cell.
o The greedy cell is defined as the cell that is allowed to reach to the pre-
defined capacity (for example, 900 UEs)
• When the number of UEs in the cell is smaller than the normal capacity (for
example, 600 UEs), the greedy cell is switched to the normal cell.
DRB
• The number of DRBs in a cell and the number of DRBs in a group are
controlled by the Call Admission Control (CAC).
• When the number of DRBs in the cell exceeds normal capacity (for example,
1800 DRBs), the cell is converted to the greedy cell.
o The greedy cell is defined as the cell that is allowed to reach to the pre-
defined capacity (for example, 2700 DRBs)
• When the number of DRBs in the cell is smaller than normal capacity (for
example, 1800 DRBs), the greedy cell is switched to the normal cell.
Confidential
Figure below depicts an example of UE pooling when the feature is enabled and
disabled.
SYSTEM OPERATION
How to Activate
Preconditions
• Two or more cells should be configured with the same
POOLING_GROUP_ID.
• Run CHG-CELL-CAC and set POOLING_CAPABILITY to
PoolingCapable for one of the cells in the Pooling Group defined with
same POOLING_GROUP_ID.
• Run CHG-CELL-CAC and set POOLING_CAPABILITY to
PoolingIncapable for all of the cells in the Pooling Group defined with
same POOLING_GROUP_ID.

Confidential
Key Parameters
parameter.
Parameter Descriptions of CHG-CELL-CAC/RTRV- CELL-CAC
POOLING_CAPABILITY This parameter indicates whether to be a greedy cell when UE Pooling
function is used.
• PoolingIncapable: A cell cannot be a greedy cell.
• PoolingCapable: A cell can be a greedy cell.
parameter.
Parameter Descriptions of CHG-CELL-CAC/RTRV- CELL-CAC
POOLING_GROUP_ID This parameter indicates UE Pooling Group ID. Group ID can be
configured with the same ID in a DSP but cannot be configure
• 0: UE Pooling function is not executed.
• 1 to 18: UE Pooling Group ID (UE pooling function is executed).
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
Chapter 4 Mobility Control
LTE-SW1001, Paging
INTRODUCTION
When eNB receives a paging message from MME, the eNB transmits the paging
message to the UE in RRC_IDLE state based on the idle mode DRX configuration
cycle.
BENEFIT
• An operator can provide mobile terminating service to its subscribers.
• LTE users can receive a notification for mobile terminating call in RRC_IDLE
state. Save on battery power and signaling
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
If the MME needs to signal with an idle UE, it starts paging procedure by sending
paging request to the eNBs in the paging area. When a paging request (S1 Paging
message) is received from the MME, the eNB will page to the UE at the timing of
the UE paging occasion.
Paging procedure is as follows. (Network triggered Service Request case)

Confidential
1) When the S-GW receives a downlink data packet for a UE, it buffers the
downlink data packet and identifies which MME is serving that UE.
2) The MME responds to the S-GW with a Downlink Data Notification Ack
message.
3) The MME sends a Paging message to eNBs belonging to the tracking areas in
which the UE is registered.
4) The eNB calculates the paging occasion for the paged UE, and the paging is
transmitted at the time of the UE paging occasion.
The Paging occasion will depend on whether DRX is utilized. If UE-specific DRX
is not configured by the upper layer, the eNB will then utilize
DEFAULT_PAGING_CYCLE (CHG-PCCH-CONF) configuration parameter
value as the default DRX cycle. After transmission of the Paging message, the
eNB will peg the AttPaging counter to keep track of number of paging attempts.
5) When the UE receives a paging indication, the UE initiates the UE triggered
Service Request procedure.
SYSTEM OPERATION
How to Activate
This feature is enabled by default, and operator cannot disable.
Key Parameters
There are no specific parameters for activation or deactivation of this feature.
parameters.
Parameter Descriptions of CHG-PCCH-CONF/RTRV-PCCH-CONF

Confidential
DEFAULT_PAGING_CYCL When DRX is used, UE monitors a single paging occasion per DRX cycle. If
E UE-specific DRX is not set by the upper layer, defaultPagingCycle is applied as
the default DRX cycle.
N_B The parameter required to calculate the paging frame and paging occasion
using the TS 36.304 method, which is a multiple of defaultPagingCycle.
• ci_fourT
• ci_twoT
• ci_oneT
• ci_halfT
• ci_quarterT
• ci_oneEightT
• ci_onSixteenthT
• ci_oneThirtySecondT
Counters and KPIs

parameters.
PAGING AttPaging Paging transmission attempt count
REFERENCE
[3] 3GPP TS36. 413 Evolved Universal Terrestrial Radio Access (E-UTRA); S1
Application Protocol (S1AP)
[4] 3GPP TS23.401 Technical Specification Group Services and System Aspects;
GPRS enhancements for E-UTRAN access

Confidential
LTE-SW1002, Idle Mobility Support

INTRODUCTION
To support intra-LTE cell reselection, eNB broadcasts the System Information
Block type 3 (SIB3), System Information Block type 4 (SIB4) and System
Information Block type 5 (SIB5). The UE monitors the E-UTRAN BCCH during
idle mode to retrieve these SIBs for the preparation of intra-LTE cell reselection.
Then UE makes measurements on neighboring cells based on the criteria and
performs cell reselection to intra-frequency/inter-frequency neighboring cells
when needed.
The parameters for intra-LTE cell reselection broadcasted in SIB3, SIB4 and SIB5
are as follows.
• SIB3 conveys the common information for intra-frequency, inter-frequency
and/or inter-RAT cell reselection.
• SIB3 also conveys the specific information for intra-frequency cell reselection.
• SIB4 conveys the intra-frequency neighboring cell related information, that is,
intra-frequency neighbor cell list and blacklisted cells.
• SIB5 conveys the specific information for inter-frequency cell reselection.
BENEFIT
• Operator can provide idle mobility to its subscribers within E-UTRAN.
• LTE users in idle state can be moving within E-UTRAN.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
PLMN Selection
When a LTE UE is switched on, it will start a process to find Public Land Mobile
Network (PLMN). The PLMN may be selected either automatically or manually,
depending on the device configuration.
Confidential
On request from the NAS layer of the UE, if a required PLMN is already
associated with LTE, the UE scans LTE carriers based on the UE stored
information. The UE searches for the strongest PLMN cell and tune to the Physical
Downlink Shared Channel (PDSCH) to read SIB1s, where PLMN information is
delivered. The PLMN, which is reported to NAS, has its measured RSRP value.
Once PLMN has been selected, the UE access stratum is instructed to measure
reference signal and read the PDSCH for SIB1 again to initiate cell selection using
the S-Criteria (based on Q_RX_LEV_MIN). At this stage if the S-criteria is not
met, the UE will go in limited service (for emergency calls) or will find an
equivalent PLMN.
Figure below depicts the idle mode state procedure:
• Selected PLMN available/unavailable: The UE scans all RF channels in the E-

UTRAN band according to its capabilities to find available PLMNs.
• Not camped: No suitable cell found.
• Camped normally: UE obtains normal service and performs the following
tasks:
o Select and monitor the PCH of the cell.
o Performs system information monitoring.
o Perform necessary measurements for the cell reselection evaluation
procedure.
o Execute the cell reselection evaluation procedure.
• Camped on any cell: UE obtains limited service and periodically searches for a
suitable cell in the selected PLMN. If the UE supports
• Cell selection: The UE selects a suitable cell and the radio access mode based
on idle mode measurements and cell selection criteria.
• Cell reselection: If after cell reselection evaluation process a better cell is
found, the cell reselection is performed. If no suitable cell is found, the UE
enters to next state Any cell selection.
• Any cell selection: UE searches an acceptable cell of any PLMN to camp on
Table below outlines the parameters for PLMN selection:

Confidential

Q_RX_LEV_MIN Minimum required RX level in the cell (dBm) (SIB1)
(RTRV-EUTRA-FA/CHG-
EUTRA-FA)
PLMN MCC and MNC (SIB1)
(RTRV-ENBPLMN-
INFO/CHG-ENBPLMN-
INFO)
Cell Selection
Initial Cell Selection
Figure below depicts initial cell selection procedures.
The UE scans all RF channels in the E-UTRAN bands to its capability to find
acceptable cells which are not barred and measure RSRP value greater than or
equal to -110 dBm. To read PLMN identity and to decide the availability of the
cell, the UE detects Primary/Secondary synchronization signals (PSS/SSS) and
decodes cell specific reference signal (CRS), and reads at least MIB and SIB1.
PCID should not be overlapped between adjacent cells for successful detecting and
decoding of the signals. The PLMN reading is reported to the NAS layer, and the
search for PLMNs may be stopped on request of the NAS.
Once the UE has selected the PLMN, the cell selection procedure is performed to
select a suitable cell of that PLMN to camp on to access available services, as
described in TS36.304. If a UE has stored information of carrier frequencies and
also (optionally) information on cell parameters from previously received
measurement, the UE can use this information to speed up the selection procedure.
The suitable cell should satisfy that:
• The cell is not barred
• The cell is part of the selected PLMN or the registered PLMN or a PLMN of
the Equivalent PLMN list
• The cell is part of at least one TA that is not part of the forbidden tracking area
lists for roaming

Confidential
• The cell selection criterion S satisfies that Srxlev > 0 AND Squal > 0
Priorities between different frequencies or RATs provided to the UE by system
information or dedicated signaling are not used in the cell selection procedure.
Cell Barring
LTE E-UTRAN cells broadcast cell selection information through SIB1 and SIB2
(AC-Barring). SIB1 has two fields for cell status indication, cellBarred and
cellReservedForOperatorUse. cellBarred is common for all PLMNs and
cellReservedForOperatorUse is specific per PLMN.
When cell status is indicated as not barred and not reserved for operator use, all
UEs treat this cell as a candidate during the cell selection and cell reselection
procedures.
When cell status is indicated as not barred and reserved for operator use for any
PLMN, the following happens:
• UEs assigned to Access Class 11 or 15 operating in their HPLMN/EHPLMN
treat this cell as a candidate during the cell selection and reselection
procedures if the field cellReservedForOperatorUse for that PLMN is set to
reserved.
• UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 behave as if
the cell status is barred in case the cell is reserved for operator use for the
registered PLMN or the selected PLMN.
When cell status barred is indicated or to be treated as if the cell status is barred,
the UE is not permitted to select/reselect this cell, not even for emergency calls.
Cell Selection Criteria
The cell selection is performed on the detected a cell with RX signal and decoded
MIB and SIBs.
Cell selection criteria:
Srxlev > 0 AND Squal > 0
Where, Srxlev = Qrxlevmeas - (Q_RX_LEV_MIN + Q_RXLEV_MIN_OFFSET) -
Pcompensation, Squal = Qqualmeas - (Q_QUAL_MIN + Q_QUAL_MIN_OFFSET)
Table below outlines the cell selection criteria.
Srxlev Cell selection RX level value (dB)
Squal Cell selection quality value (dB)
Qrxlevmeas Measured cell RX level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Q_RX_LEV_MIN Minimum required RX level in the cell (dBm) (SIB1)
(RTRV-CELL-SEL/CHG-
CELL-SEL)
Q_QUAL_MIN Minimum required quality level in the cell (dB) (SIB1)
(RTRV-CELL-SEL/CHG-
CELL-SEL)
Q_RXLEV_MIN_OFFSET Offset to the signaled Q_RX_LEV_MIN taken into account in the Srxlev evaluation

Confidential

(RTRV-CELL-SEL/CHG- as a result of a periodic search for a higher priority PLMN while camped normally
CELL-SEL) in a VPLMN (SIB1)
Q_QUAL_MIN_OFFSET Offset to the signaled Q_QUAL_MIN taken into account in the Squal evaluation as
(RTRV-CELL-SEL/CHG- a result of a periodic search for a higher priority PLMN while camped normally in
CELL-SEL) a VPLMN (SIB1)
Pcompensation max (PEMAX - PPowerClass, 0) (dB)

P_MAX Maximum TX power level an UE may use when transmitting on the uplink in the
(RTRV-CELL-SEL/CHG- cell (dBm) defined as P_MAX in [TS 36.101] (SIB1)
CELL-SEL)
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class as
defined in [TS 36.101]
Since Q_QUAL_MIN and Q_QUAL_MIN_OFFSET are not provided in network,

devices will test Srxlev only.
If q-QualMinWB (in SIB1/SIB3/SIB5) is present, the UE, when performing RSRQ
measurement, uses a wider bandwidth.
Cell Reselection
Figure below depicts initial cell reselection procedures.
When a cell reselection condition is met, the UE in idle mode attempts to detect,
synchronize, and read system information of candidate frequencies. The UE
performs only cell reselection evaluation for E-UTRAN frequencies and inter-
RAT frequencies that are given in system information and for which the UE has a
priority provided.
The cell reselection procedures are triggered when one of the following conditions
is met:
1 The serving cell does not fulfil Srxlev > S_INTRA_SEARCH_P and Squal >
S_INTRA_SEARCH_Q. In this case, the UE performs intra-frequency cell
reselection procedures.
2 The UE has E-UTRA frequencies or other RAT frequencies with a

Confidential
reselection priority higher than the reselection priority of the current E-UTRA
frequency. In this case, the UE performs inter-RAT cell reselection
procedures. The UE searches every layer of higher priority at least every
Thigher_priority_search = (60 * Nlayers) seconds, where Nlayers is the total
number of configured higher priority E-UTRA, other RAT carrier
frequencies. (3GPP TS36.133 Section 4.2.2)
3 The service cell does not fulfil Srxlev > S_NON_INTRA_SEARCH_P and
Squal > S_NON_INTRA_SEARCH_Q. In this case, the UE performs inter-
RAT cell reselection procedures for an E-UTRA inter-frequency or another
RAT frequency with an equal or lower reselection priority than the
reselection priority of the current E-UTRA frequency.
Since RSRQ related parameters are not provided in network, devices will test Srxlev
only. The device will use S_INTRA_SEARCH and S_NON_INTRA_SEARCH
instead of S_INTRA_SEARCH_P and S_NON_INTRA_SEARCH_P
respectively.
Table below outlines the parameters that trigger cell reselection procedures.
Srxlev Cell selection RX level value (in dB) measured by UE
Squal Cell selection quality value (in dB) measured by UE
S_INTRA_SEARCH This specifies the Srxlev threshold (in dB) for intra-frequency measurements.
(RTRV-EUTRA-FA/CHG- This parameter is used by Rel-8 device. (SIB3)
EUTRA-FA)
S_INTRA_SEARCH_P This specifies the Srxlev threshold (in dB) for intra-frequency measurements.
EUTRA-FA)
S_INTRA_SEARCH_Q This specifies the Squal threshold (in dB) for intra-frequency measurements.
EUTRA-FA)
S_NON_INTRA_SEARCH This specifies the Srxlev threshold (in dB) for E-UTRAN inter-frequency and
(RTRV-EUTRA-FA/CHG- inter-RAT measurements. This parameter is used by Rel-8 device. (SIB3)
EUTRA-FA)
S_NON_INTRA_SEARCH_P This specifies the Srxlev threshold (in dB) for E-UTRAN inter-frequency and
EUTRA-FA)
S_NON_INTRA_SEARCH_Q This specifies the Squal threshold (in dB) for E-UTRAN inter-frequency and
EUTRA-FA)
Q_RX_LEV_MIN This specifies the minimum required Rx level in the cell in dBm
(RTRV-EUTRA-FA/CHG- This parameter (SIB3)
EUTRA-FA)
Q_QUAL_MIN_REL9 This specifies the minimum required quality level in the cell in dB. This
(RTRV-EUTRA-FA/CHG- parameter is used by Rel-9 device. (SIB3)
EUTRA-FA)
Thresholds and Priority Design

For network, cell reselection triggering thresholds and priority are configured so
that the UEs can select LTE network as a primary network in the presence of an

Confidential
acceptable LTE signal. In network, RSRP is used as a measurement triggering

criteria because RSRQ can vary even in the center of the serving cell from -3 dB to
-10 dB depending on traffic load from the serving cell. S_INTRA_SEARCH
should be greater than S_NON_INTRA_SEARCH so that LTE capable UEs can
select LTE frequency as long as it moves under LTE coverage.
Figure below depicts the thresholds for cell reselection:
UE triggers the measurement of intra-frequency when the RSRP signal strength

from LTE serving cell decreases below the threshold calculated as follows:
• RSRP Strength from Serving Cell =< S_INTRA_SEARCH +
Q_RX_LEV_MIN + Q_RXLEV_MIN_OFFSET + Pcompensation
Where, Pcompensation is maximum (PEMAX-PPowerClass, 0) (dB). PEMAX is defined as PMAX
in 3GPP TS36.101, and PPowerClass is 23 dBm as per 3GPP TS36.101. (118 dBm).
Therefore, Pcompensation is usually assumed to be 0.
UE triggers the measurement of other frequency when the RSRP signal strength
from LTE serving cell decreases below the threshold calculated as follows:
• RSRP Strength from Serving Cell = < S_NON_INTRA_SEARCH +
Q_RX_LEV_MIN + Q_RXLEV_MIN_OFFSET + Pcompensation
UE will start the measurements of LTE frequency when the measured RSRP is less
than -64 dBm [Q_RX_LEV_MIN = -63 (-126 dBm), Q_RXLEV_MIN_OFFSET
= 0, S_INTRA_SEARCH = 31 (62 dB), Pcompensation = 0], and start the
measurements of other frequency when the measured RSRP is less than -112 dBm
[Q_RX_LEV_MIN = -63 (-126 dBm), Q_RXLEV_MIN_OFFSET = 0,
S_NON_INTRA_SEARCH = 7 (14 dB), Pcompensation = 0).
For UEs to select primarily LTE frequency when UEs end a CSFB call or when
UEs come back into LTE coverage, LTE frequency priority must be greater than
other frequency.
The priority of each frequency is broadcasted in SIB3 (E-UTRA frequency).

Confidential
Intra-Frequency Cell Reselection

Intra-frequency cell reselection is performed when the signal strength from LTE
serving cell is less than the threshold as described above. The cell reselection is
performed on the basis of the ranking of the current and the neighboring cells.
Cell reselection criteria:
• Rs = Qmeas, s + Q_HYST
• Rn = Qmeas, n - Q_OFFSET_FREQ
Table below outlines the above mentioned parameters:
Rs Rs is for the serving cell.
Rn Rn is for the neighbor cell.
Qmeas RSRP measurement quantity used in cell reselections.
Q_HYST This parameter (in dB) is to reduce ping-pong effects between serving and
(RTRV-CELL-RSEL/CHG- neighbor cells. (SIB3)
CELL-RSEL)
Q_OFFSET_FREQ For intra-frequency: Equals to Qoffsets, n, if Qoffsets, n is valid, otherwise this
(RTRV-EUTRA-FA/CHG- equals to zero.
EUTRA-FA)
T_RESELECTION This specifies the reselection timer value for E-UTRAN. (SIB3)
(RTRV-EUTRA-FA/CHG-
EUTRA-FA)
The UE performs ranking of all cells that fulfil the cell selection criterion S. The
cells are ranked according to the R criteria specified above, deriving Qmeas, n and
Qmeas, s and calculating the R values using averaged RSRP results. If a cell is
ranked as the best cell, the UE performs cell reselection to that cell. The UE
reselects the new cell, only if the following conditions are met:
• The new cell is better ranked than the serving cell during a time interval
T_RESELECTION.
• More than 1 second has elapsed since the UE camped on the current serving
cell.
Initial Attach
When UE camps on a suitable cell, if the new cell does not belong to any tracking
areas to which the UE is registered previously, the UE will register to the network
by sending a Tracking Area Update message. Figure below depicts the initial
attach procedures.

Confidential
1~4) Step 2~4 completes a RRC connection establishing a SRB. The attach
procedure starts with the RRC connection establishment procedure. The Attach
Request message included in RRCConnectionSetupComplete is transparently
delivered to the MME in INITIAL UE MESSAGE message.
5~9) The eNB sends INITIAL UE MESSAGE to MME, then MME responds with
INITIAL CONTEXT SETUP REQUEST after selecting a S-GW.
10~12) eNB acquires UECapabilityInformation and reports it to the MME.
13~14) eNB sends the integrity-protected AS Security Mode Command message
to the UE. Then, the UE starts control plane signaling integrity.
15~16) eNB sends RRCConnectionReconfiguration message in order to a data
radio bearer. After eNB receives CONTEXT SETUP REQUEST message from

Confidential
MME, it creates a default radio bearer by sending RRCConnectionReconfiguration

message to UE. When the UE receives RRCConnectionReconfiguration message,
it can transmit packets in uplink and eNB can deliver the packets toward S-GW.
17) eNB sends Initial Context Setup Response message to MME and completes
the establishment of S1 bearer.
18~19) UE sends ULInformationTransfer message to eNB, which includes Attach
Complete message. This message is transparently delivered to MME in UPLINK
NAS TRANSPORT message.
20~21) MME sends Modify Bearer Request message to S-GW, in order to provide
downlink tunnel information of eNB. After S-GW receives the Modify Bearer
Request message, it can transmit packets in downlink.
If both DRB and SRB carry no packets in downlink and uplink for a certain
period, eNB releases the RRC connection and S1 bearer. Operator can configure
INTERNAL_SIGNALING_INACTIVITY for a signaling bearer and
INTERNAL_USER_INACTIVITY for a data bearer at eNB level.
When both inactivity timers expire, the eNB sends UE Context Release message to
the MME and releases the S1 connection for the UE.
Figure below depicts the connection release procedure by the inactivity timer
triggered.
Combined EPS and IMSI Attach

When supporting Combined EPS/IMSI Attach Request, MME selects the IWF
(MSC/VLR) based on the TA/LA mapping and sends the location update request
with new LAI, IMSI and the MME name to IWF. On receiving request, the
respective VLR creates an association for SGs interworking with the MME. In
response, the VLR provides VLR TMSI to MME.
Figure below depicts the combined EPS/IMSI attach call flow.

Confidential
The combined EPS/IMSI Attach procedures are:

1)~5) The UE sends an Attach Request to MME with Attach Type as Combined
EPS/IMSI, UE capability as CSFB and data APN name. The APN name is
depending on the subscriber type. UE may include any of the Internet APN.
6) The MME sends authentication information request message to HSS. After
receiving the Authentication Information Answer from HSS, MME and UE are
authenticated each other with set of authentication messages between UE and
MME. After the successful authentication, MME updates the subscriber location in
the HSS and gets the subscriber profile from HSS.
7)~8) The MME sends Create Session Request message to S-GW for establishing
the default bearer for the UE. S-GW forwards the session request message to P-
GW. P-GW replies with the Create Session Response to MME.

Confidential
9)~10) Since UE has requested for combined EPS/IMSI attach, after the default
bearer establishment MME updates the UE location in 3G network by sending the
location update message with new LAI, IMSI and the MME name to IWF
(MSC/VLR). After accepting the attach request by the network, default bearer is
established. IWF updates the UE CS location in HLR.
11)~14) The eNB acquires UECapabilityInformation and reports it to MME.
15)~16) The eNB sends the integrity-protected AS Security Mode Command
message to the UE. Then, the UE starts control plane signaling integrity.
17)~18) The eNB sends RRCConnectionReconfiguration message to a data radio
bearer. After eNB receives CONTEXT SETUP REQUEST message from MME, it
creates a default radio bearer by sending RRCConnectionReconfiguration message
to UE. When the UE receives RRCConnectionReconfiguration message, it can
transmit packets in uplink and eNB can deliver the packets toward S-GW.
19) The eNB sends Initial Context Setup Response message to MME and
completes the establishment of S1 bearer.
20)~21) The UE sends ULInformationTransfer message to eNB, which includes
Attach Complete message. This message is transparently delivered to MME in
UPLINK NAS TRANSPORT message.
22)~23) The MME sends Modify Bearer Request message to S-GW, to provide
downlink tunnel information of eNB. After S-GW receives the Modify Bearer
Request message, it can transmit packets in downlink.
Combined EPS and IMSI Detach

To detach the combined EPS/IMSI attached UE, the UE is required to be detached
from both EPS domain as well as from CS domain. Figure below depicts the
combined EPS/IMSI detach call flow.

Confidential
The combined EPS/IMSI Detach procedures are:

1)~2) The UE sends Detach Request to MME.
3) The MME sends Delete Session Request message to S-GW for deactivating the
default bearer for the UE. S-GW forwards the Delete Session Request message to
P-GW.
4) The IMSI Detach Indication message from MME to IWF (MSC/VLR) to
remove the SGs association with regarding to UE IMSI.
5) The P-GW replies with the Delete Session Response to MME.
6)~8) The MME sends Detach Accept to UE and releases the S1-MME signaling
connection.
Related SIB Messages

SIB2 contains radio resource configuration information that is common for all
UEs. Table below outlines the SIB2 message.
ac-BarringInfo • ac-BarringForEmergency
• ac-BarringForMO-Signaling (TAU, Attach/Detach message)
• ac-BarringforMO-Data (Service Request, Extended Service Request
messages)
freqInfo • ul-CarrierFreq
• ul-Bandwidth
• additionalSpectrumEmission
radioResourceConfigCommon • rach-config, bcch-config, pcch-config, prach-config, pdsch-config, pusch-
SIB config, and pucch-config
• UL-CyclicPrefixLength
• uplinkPowerControlCommon

Confidential
ac-BarringInfo • ac-BarringForEmergency
• ac-BarringForMO-Signaling (TAU, Attach/Detach message)
• ac-BarringforMO-Data (Service Request, Extended Service Request
messages)
freqInfo • ul-CarrierFreq
• ul-Bandwidth
• additionalSpectrumEmission
radioResourceConfigCommon • rach-config, bcch-config, pcch-config, prach-config, pdsch-config, pusch-
SIB config, and pucch-config
• UL-CyclicPrefixLength
• uplinkPowerControlCommon
ue-TimersAndConstants
timeAlignmentTimerCommon (to control how long the UE is considered uplink time aligned)
mbsfn-SubframeConfigLit
SIB3 contains cell re-selection information common for intra-frequency, inter-

frequency and/or inter-RAT cell re-selection. Table below outlines the SIB3
message.
cellReselectionInfoCommon • q-Hyst
• speedStateReselectionPars (Q-hysteresis scaling factor depending on UE
speed)
cellReselectionServingFreqInfo • s-NonIntraSearch
• threshServingLow
• cellReselectionPriority
intraFreqCellReselectionInfo • q-RxLevMin
• P-max (maximum uplink tx power of UE for the intra-frequency neighboring
E-UTRA cells)
• s-IntraSearch
• allowedMeasBandwidth
• neighCellConfig (MBSFN and TDD related information)
• t-ReselectionEUTRA (cell reselection timer, it can be set per E-UTRAN
frequency)
• t-ReselectionEUTRA-SF (speed dependent scale factor)
SIB4 contains neighboring cell related information relevant only for intra-
frequency cell re-selection. SIB4 includes cells with specific re-selection
parameters as well as blacklisted cells. Table below outlines the SIB4 message.
intraFreqNeighbCellList (List • physCellId
of intra-frequency neighboring • q-OffsetCell (Qoffsets, n, the offset between the two cells)
cells with specific cell re-
selection parameters, up to
16)
intraFreqBlackCellList (List of blacklisted intra-frequency neighboring cells, up to 16)
Table below outlines the SIB5 message. SIB5 is for information for inter-
frequency cell re-selection.

Confidential
InterFreqCarrierFreqInfo (list • dl-CarrierFreq

of frequency information up to • q-RxLevMin
8) • p-Max
• t-ReselectionEUTRA
• t-ReselectionEUTRA-SF
• threshX-High (cell reselection to a cell on a higher priority E-UTRAN
frequency or inter-RAT frequency than the serving frequency if a cell of a
higher priority RAT/frequency fulfils Srxlev > ThreshX, HighP during a time
interval TreselectionRAT)
• threshX-Low (cell reselection to a cell on a lower priority E-UTRAN
frequency or inter-RAT frequency than the serving frequency if the serving
cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority
RAT/frequency fulfils Srxlev > ThreshX, LowP during a time interval
TreselectionRAT)
• allowedMeasBandwidth
• presenceAntennaPort1 (to indicate whether all the neighboring cells use
Antenna Port 1)
• cellReselectionPriority
• neighCellConfig (MBSFN and TDD related information)
• q-OffsetFreq (Qoffsetfrequency, Frequency specific offset for equal priority
E-UTRAN frequencies)
• interFreqNeighCellList (up to 16)
• physCellId
• q-OffsetCell (Qoffsets, n, the offset between the two cells)
• interFreqBlackCellList (up to 16)
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of RTRV-EUTRA-FA/CHG-EUTRA-FA
PRIORITY This is a parameter specifying the priority of EUTRA-FA during idle
reselection or mobility control information. "7" is the highest priority. Be

Confidential
careful not to set the same priority when configuring multiple EUTRA-FAs.
Q_RX_LEV_MIN This parameter is minimum RX level required in a cell that is operating as
EUTRA-FA and its unit is dBm.
T_RESELECTION This parameter is the interval (timer) of reselection execution.
T_RESELECTION_SF_MEDI This parameter is the medium timer value of the reselection scaling factor.
UM
T_RESELECTION_SF_HIGH This parameter is the high timer value of the reselection scaling factor.
S_INTRA_SEARCH This parameter is the threshold value for intra-frequency measurement.
S_NON_INTRA_SEARCH This parameter is the threshold value for the inter-RAT and inter-frequency
measurement.
THRESH_SERVING_LOW This parameter is the low threshold for serving frequency upon reselection
evaluation.
THRESH_X_HIGH This parameter is the threshold value used by the UE when reselecting the
frequency with priority higher than the currently camped frequency.
THRESH_X_LOW This parameter is the threshold value used when reselecting the low-priority
frequency from the high-priority frequency.
Q-OFFSER-FREQ This parameter is the frequency offset applied to the q-OffsetFreq of a SIB5
message.
S_INTRA_SEARCH_P This parameter is the threshold-P value for the intra-frequency measurement
of Rel-9.
S_INTRA_SEARCH_Q This parameter is the threshold-Q value for the intra-frequency measurement
of Rel-9.
S_NON_INTRA_SEARCH_P This parameter is the threshold-P value for the inter-frequency measurement
and Inter-RAT.
S_NON_INTRA_SEARCH_Q This parameter is the threshold-Q value for the inter-frequency measurement
and Inter-RAT.
Q_QUAL_MIN_REL9 This parameter is the qQualMin value for Rel-9.
THRESH_SERVING_LOW_Q This parameter is the threshServingLowQ value for Rel-9.
_REL9
THRESH_XHIGH_Q_REL9 This parameter is the threshold value used by the UE when reselecting the
frequency with priority higher than the currently camped frequency in the Rel-
9.
THRESH_XLOW_QREL9 This parameter is the threshold value used when reselecting the low-priority
frequency from the high-priority frequency in the Rel-9.
Q_QUAL_MIN_WB If the allowedMeasBandwidth is bigger than 50RB, this parameter should be
set to measure wideband RSRQ
If this parameter is used, when RSRQ measurement is performed UE use a
wider bandwidth (according to TS 36.133) and apply this value for Qqualmin
according to TS 36.304
This parameter is transferred via SIB3, SIB5, SIB1.
Parameter Descriptions of RTRV-CELL-RSEL/CHG-CELL-RSEL

Q_HYST The cell number. This value must not exceed the maximum number of cells
Q_HYST_SFMEDIUM This parameter is the value added when the UE speed is medium among
Qhyst values that are added to the current serving
cell in the cell reselection criteria. To apply the change of this parameter, the

Confidential
SPEED_STATE_RESEL_PARAMS_USAG E should be changed to use in
the CHGMOBIL-STA beforehand.
Q_HYST_SFHIGH This parameter is the value added when the UE speed is high among Qhyst
values that are added to the current serving cell in the cell reselection criteria.
To apply the change of this parameter, the
SPEED_STATE_RESEL_PARAMS_USAG E should be changed to use in
the CHGMOBIL-STA beforehand.
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-SW1003, Intra-eNB Handover

INTRODUCTION
Intra-eNB handover is mobility control functionality between cells that belong to
the same eNB. UEs can move between the cells without any message exchange
with MME.
BENEFIT
• An operator can provide connected mobility to its subscribers between cells in
same eNB.
• Users in connected state can be moving within E-UTRAN, with change of
serving cell.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The intra-eNB handover does not use S1 or X2 interfaces to execute the handover
procedure between source cell and target cell. When the UE moves between cells
belonging to the same eNB, the intra-eNB handover function is carried out. The
Intra-eNB handover is performed as follows:
• When eNB receives a Measurement Report including Event A3/A4/A5 from
UE, eNB triggers intra-LTE handover to the best cell indicated in the
measurement report.
• The PDCB (eNB software control block module) becomes an anchor through
PDCP re-establishment, the channel card is switched, and the RLC context
does not persist, but is reset through RLC re-establishment. Therefore, for
lossless data transmission, the functions of PDCP SDU retransmission at the
PDCP terminal, PDCP status reporting, in-order delivery, and duplication
elimination are carried out.
Figure below depicts the intra-eNB handover procedure in E-UTRAN.

Confidential
1) UE sends Measurement Report including E-UTRAN measurements to the

serving eNB. The source eNB determines whether to hand over the UE based on
the MeasurementReport message and the radio resource management information.
At this time, if the determined target cell is located in the same eNB where the
current source cell is located, the intra-eNB handover procedure is performed
2) The source eNB commands the UE to perform handover to the target cell by
transmitting the RRCConnectionReconfiguration message containing the
mobileControlInfo IE.
3) After receiving the RRCConnectionReconfiguration message that includes the
mobilityControlInfo IE, the UE performs synchronization with the target cell and
connects to the target cell through the Random Access Channel (RACH). The
target cell replies with UL allocation and timing advance.
4) After having connected to the target cell successfully, the UE notifies the target
cell that the handover procedure has been completed, using the
RCConnectionReconfigurationComplete message.
UE measurement and Measurement reporting configuration

eNB sends to UE the measurement configuration information (refer to MeasConfig
IE in TS36.331) in the RRC Connection Reconfiguration message for intra-LTE
handover when call setup, hand-in, reestablishment or change of QCI mobility
group by E-RAB setup/modify/release. By configuring the measConfig IE, eNB
can control on what conditions UE will report for intra-LTE measurement.
eNB extracts a UE’s available E-UTRA carriers considering UE’s supported
bands, UE’s capability on measurement/handover and the serving cell’s
configuration for intra-LTE mobility. The extracted E-UTRA carriers are
configured to UE as measurement objects.
The following configuration is considered for intra-LTE mobility:
• E-UTRA carrier frequencies (parameter: EARFCN_DL of CHG-EUTRA-FA)
• The specific parameters per E-UTRA carrier frequency based on standard

Confidential
(parameter: MEASUREMENTBAND_WIDTH, PRESENCE_ANT_PORT1,

NEIGH_CELL_CONFIG and OFFSET_FREQ of CHG-EUTRA-FA)
• Carrier preference per each E-UTRA carrier frequency (parameter:
PREFERENCE0~5 of CHG-EUTRA-FA)
Then eNB configures reporting configuration per the extracted E-UTRA carriers
for UE. The following parameters are used for UE measurement reporting:
• Event type for intra-LTE handover (parameter: HANDOVER_TYPE of CHG-
EUTRA-FA)
• The HO parameters per Event type, such as trigger quantity, report quantity,
A3 offset, A4/A5 threshold, hysteresis, time to trigger. (the parameters of
CHG-EUTRA-A3CNF/CHG-EUTRA-A3CNFQ/CHG-EUTRA-
A4CNF/CHG-EUTRA-A4CNFQ/CHG-EUTRA-A5CNF/CHG-EUTRA-
A5CNFQ.)
Counters for intra-eNB HO

The results by performing intra-eNB handover are collected as following counters:
• Counter family: HO_INTRA/HO_INTRA_IN
o Number of intra-eNB HO preparation attempts (outgoing/incoming),
o Number of intra-eNB HO preparation successes (outgoing/incoming),
o Number of intra-eNB HO execution successes (outgoing/incoming),
o Number of intra-eNB HO preparation failures per cause
(outgoing/incoming),
o Number of intra-eNB HO execution failures per cause
(outgoing/incoming)
• Counter family: HO_TIME
o Intra-eNB handover time (average/maximum): Time taken between
sending intra-eNB handover command to UE and receiving handover
complete indication from UE.
• Counter family: MOBILITY
o Intra-eNB handover success rate
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-EUTRA-A3CNF and set ACTIVE_STATE corresponding to
PURPOSE (A3PurposeIntraLteHandover) to active or
Run CHG-EUTRA-A5CNF and set ACTIVE_STATE corresponding to
PURPOSE (A5PurposeIntraLteHandover) to active.
PURPOSE (A3PurposeIntraLteHandover) to Inactive or
PURPOSE (A5PurposeIntraLteHandover) to Inactive.
Key Parameters
parameters.
PURPOSE This parameter is the purpose of using Event A3.
• IntraLteHandover: Performs handover.
• ReportStrongestCells: Performs the ANR operation.
• IntraFrequencyLb: Performs Intra Frequency Load Balancing.
• CaInterFreq: Performs InterFrequency Carrier Aggregation.
• IntraFrequencyCre: Performs IntraFrequency CRE.
• PeriodicMr: Performs Periodic Measurement Report for eICIC.
ACTIVE_STATE Whether to use Event A3.
• Inactive: Event A3 is not used.
• Active: Event A3 is used.
parameters.
PURPOSE The purpose for using Event A3. It is currently used for intra-LTE handover and
the SON ANR function.
• IntraLteHandover
• ReportStrongestCells
• IntraFrequencyLb

Confidential
• CaInterFreq
A3_OFFSET RSRP threshold used for triggering the EUTRA measurement report for Event A3.
TIME_TO_TRIGGER timeToTrigger value for Event A3. The time-ToTrigger value is the period that must
be met for the UE to trigger a measurement report.
TRIGGER_QUANTITY Quantity (RSRP/RSRQ) used to calculate a triggering condition for Event A3.
Either RSRP or RSRQ is assigned.

PURPOSE The purpose for using Event A5. Not in current use. The definition is made for later
use.
• ci_A5PurposeIntraLteHandover: Intra-LTE handover.
• ci_A5PurposeSpare_1: Reserved.
ACTIVE_STATE Whether to use the Event A5.
A5_THRESHOLD2_RSR RSRP threshold1 used for triggering the EUTRA measurement report for Event
P A5.
Q A5.
Parameter Descriptions of RTRV-NBR-EUTRAN/CHG-NBR-EUTRAN/CRTE-

NBR-EUTRAN/DLT-NBR-EUTRAN
RELATION_IDX Database index of E-UTRAN neighboring cell.
STATUS The validity of the E-UTRAN neighboring cell information.
• N_EQUIP: The E-UTRAN neighboring cell information is invalid.
• EQUIP: The E-UTRAN neighboring cell information is valid.
ENB_ID The eNB ID of the eNB to which E-UTRAN neighboring cell to the eNB belongs. If
the enbType value is macro eNB, 20 bit of the value is eNB ID. If the enbType
value is home eNB, 28 bit of the value is eNB ID. It is used when creating a cell
identifier.
TARGET_CELL_NUM The local cell ID of E-UTRAN neighboring cell to the eNB. It is used when creating
a cell identifier.

Confidential
ENB_TYPE The type of the eNB to which E-UTRAN neighboring cell to the eNB belongs.
• ci_Macro_eNB: Indicates the macro eNB.
• ci_Home_eNB: Indicates the home eNB.
ENB_MCC The PLMN information (MCC) of the eNB to which E-UTRAN neighboring cell to
the eNB belongs. It is a three-digit number with each digit ranging from 0 to 9.
ENB_MNC The PLMN information (MNC) of the eNB to which E-UTRAN neighboring cell to
the eNB belongs. It is a three-digit or two-digit number with each digit ranging from
0 to 9.
PHY_CELL_ID The physical cell ID of E-UTRAN neighboring cell to the eNB.
TAC The tracking area code of E-UTRAN neighboring cell to the eNB.
MCC0 The broadcast PLMN list information (MCC) of E-UTRAN neighboring cell to the
eNB. It is a three-digit number with each digit ranging from 0 to 9.
MNC0 The broadcast PLMN list information
(MNC) of E-UTRAN neighboring cell to the eNB. It is a three-digit or two-digit
number with each digit ranging from 0 to 9.
MCC1 The broadcast PLMN list information
(MCC) of E-UTRAN neighboring cell to the eNB. It is a three-digit number with
each digit ranging from 0 to 9.
MNC1 The broadcast PLMN list information (MNC) of E-UTRAN neighboring cell to the
eNB. It is a three-digit or two-digit number with each digit ranging from 0 to 9.
EARFCN_UL The uplink EARFCN (E-UTRAN Absolute Radio Frequency Channel Number) of
EUTRAN neighboring cell to the eNB.
EARFCN_DL The uplink EARFCN (E-UTRAN Absolute Radio Frequency Channel Number) of
BANDWIDTH_UL The uplink bandwidth of E-UTRAN neighboring cell to the eNB.
BANDWIDTH_DL The downlink bandwidth of E-UTRAN neighboring cell to the eNB.
IND_OFFSET The cell individual offset to be applied to EUTRAN neighboring cell to the eNB. It is
used for UE measurement in RRC Connected mode.
QOFFSET_CELL The cell quality offset to be applied to EUTRAN neighboring cell to the eNB. It is
used for UE cell re-selection in RRC Idle mode.
IS_REMOVE_ALLOWED Whether to delete a certain neighboring cell to the eNB using the ANR (Automatic
Neighbor Relation) function.
• True: The neighboring cell can be deleted.

Confidential
• False: The neighboring cell cannot be deleted.
IS_HOALLOWED Whether to perform handover to E-UTRAN neighboring cell.
• True: Handover is allowed.
• False: Handover is not allowed.
IS_COLOCATED This parameter defines whether this neighbor cell is co-located with the serving
cell or not.
• True: The neighboring cell is co-located.
• False: The neighboring cell is not co-located.
Counters and KPIs

Intra-eNB Handover IntraEnbAtt Intra-handover attempt count.
IntraEnbPrepSucc Intra-handover preparation success count.
IntraEnbSucc Intra-handover execution success count.
IntraEnbPrepFail_CpCcTo Preparation fails due to call control timeout in the
during the intra handover preparation.
IntraEnbPrepFail_CpCcFail Preparation fails due to reset notification (the eNB
failure or block restart) from ECMB or by the
ECCB block during the intra handover preparation.
IntraEnbPrepFail_UpMacFail Preparation fails due to internal failure in the MAC
block during the intra handover preparation.
IntraEnbPrepFail_UpRlcFail Preparation fails due to internal failure in the RLC
block during the intra handover preparation.
IntraEnbPrepFail_RrcSigFail A call is released due to receiving RRC signaling
during the intra handover preparation.
IntraEnbPrepFail_CpBhCac Preparation fails due to insufficient backhaul-
Fail based eNB resources during the intra handover
preparation.
IntraEnbPrepFail_CpCapaC Preparation fails due to insufficient capacity-based
acFail eNB resources during the intra handover
preparation.
IntraEnbPrepFail_CpQosCa Preparation fails due to insufficient QoS-based
cFail eNB resources during the intra handover
preparation.
IntraEnbPrepFail_S1apCuFa Preparation fails due to S1AP specification cause
il during the intra handover preparation.
IntraEnbPrepFail_S1apLinkF Preparation fails due to S1 SCTP link failure
ail during the intra handover preparation.
IntraEnbPrepFail_S1apSigF Preparation fails due to receiving S1AP signaling
ail during the intra handover preparation.
IntraEnbFail_CpCcTo A call is released due to call control timeout in the
during the intra handover execution.
IntraEnbFail_CpCcFail A call is released due to reset notification (the eNB
failure or block restart) from ECMB or by the
ECCB block during the intra handover execution.

Confidential

IntraEnbFail_UpGtpFail A call is released due to the internal failure in the
GTP block during the intra handover execution.
IntraEnbFail_UpMacFail A call is released due to the internal failure in the
MAC block during the intra handover execution.
IntraEnbFail_UpRlcFail A call is released due to the internal failure in the
RLC block during the intra handover execution.
IntraEnbFail_RrcHcTo A call is released due to HO command timeout
(not received) during the intra handover execution.
IntraEnbFail_RrcSigFail A call is released due to receiving RRC signaling
IntraEnbFail_S1apCuFail A call is released due to the S1AP specification
cause during the intra handover execution.
IntraEnbFail_S1apLinkFail A call is released due to S1 SCTP link failure
IntraEnbFail_S1apSigFail A call is released due to S1AP signaling timeout
(not received) during the intra handover execution.
Handover Time IntraHOTime Time taken from transmitting the
RRCConnectionReconfiguration message to the
UE until after receiving the RRCConnection
ReconfigurationComplete message from the UE.
IntraHOTimeMax Average maximum intra HO interrupt time
IntraHOTimeTot Sum of Intra HO Interrupt time
IntraHOTimeCnt Count of IntraHoTimeAvg collected
S1HOTime Average S1 HO interrupt time
S1HOTimeMax Average maximum S1 HO interrupt time
S1HOTimeTot Sum of S1 HO interrupt time
S1HOTimeCnt Count of S1HoTimeAvg collected
X2HOTime Average X2 HO interrupt time
X2HOTimeMax Average maximum X2 HO interrupt time
X2HOTimeTot Sum of X2 HO Interrupt time
X2HOTimeCnt Count of X2HoTimeAvg collected
MOBILITY (KPI) EutranMobilityHOIntra HOIntra success rate of E-UTRAN mobility
sumHOIntra_Att Total intra handover attempt count
sumHOIntra_Succ Total intra handover execution success count
sumHOIntra_PrepSucc Total intra handover preparation success count
REFERENCE

Confidential
LTE-SW1004, S1 Handover
INTRODUCTION
S1 handover is mobility control functionality between two adjacent eNBs using the
S1 interface with the MME (inter-eNB handover through S1 interface). S1
handover is used when there is no available direct interface with the target eNB, or
the target eNB belongs to another MME group.
BENEFIT
different eNBs.
• Users in a connected state can move within E-UTRAN seamlessly, with
change of serving cell.
DEPENDENCY
With full configuration, Hyper Frame Number (HFN) is reset for all bearers and
lossless HO is not supported.
LIMITATION
None
SYSTEM IMPACT
capabilities.
This feature can be activated only when the LTE-SW0501, S1 Interface
Management feature is enabled.
None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
S1 handover is a handover between two adjacent eNBs using the S1 interface with
MME (inter eNB handover through S1 interface). It is used when there is no
available direct interface with the target eNB, or the target eNB belongs to other
Confidential
MME group.
The eNB performs S1 handover with indirect forwarding instead of X2 handover,
in case there is no direct forwarding path with the target eNB.
Figure below depicts the S1 handover procedure in E-UTRAN (S1 handover with
MME and S-GW relocation case).

Confidential

Confidential
1) The UE sends a Measurement Report (MR) including E-UTRAN

measurements to the source eNB.
2) The source eNB determines handover target cell based on the MR and whether
to trigger handover considering the serving cell configuration for handover.
• Handover target cell is selected the best one in the measured cells to which
handover can be possible.
• In case of PCI duplication: The eNB checks whether the PCI of the determined
target cell exists in neighbor cell list (Neighbor Relation Table, NRT) or not. If
there are several neighbors with the same PCI (this case is called PCI
duplication), then the eNB requests ECGI reporting to the UE to identify the
target cell. After obtaining a MR including the target cell’s ECGI, the eNB
triggers a handover.
3) The source eNB sends HANDOVER REQUIRED to the serving MME. The
source eNB provides the information about which bearers requires data forwarding
and whether direct forwarding with target eNB is available.
• The Direct Forwarding Path Availability IE is included in the HANDOVER
REQUIRED message, if the following criteria are met:
o Any X2 Path for data forwarding (X2-U) is available
o X2 connectivity with the target eNB (X2-C) is available
o X2 handover to the target eNB cannot be possible
4) - 6) The MME transmits the HANDOVER REQUEST message to the target
eNB. This message includes the UE context which is bearer related information
and security context.
7) The target eNB performs admission control for the incoming handover request.
If it is acceptable, the target eNB prepares the handover (for example, radio
resource allocation, and creation for data forwarding resources) and makes the
RRCConnectionReconfiguration message including the mobilityControlInfo IE
that tells the source eNB to perform the handover. The target eNB includes the
RRCConnectionReconfiguration message in the S1 HANDOVER REQUEST
ACKNOWLEDGE message and transmits it to the MME. This message includes
the accepted bearer list and a list of tunnel information for receiving forwarded
data if data forwarding can be possible.
8) - 10) If indirect forwarding is used, the MME transmits the Create Indirect Data
Forwarding Tunnel Request message to the S-GW. The S-GW replies to the MME
with the Create Indirect Data Forwarding Tunnel Response message.
11) The source eNB receives the HANDOVER COMMAND from the source
MME.
12) The source eNB constructs the RRCConnectionReconfiguration for handover
(for example, handover command) and it is sent to the UE.
The source eNB sends the S1 eNB STATUS TRANSFER message to the MME to
transfer the uplink and downlink PDCP SN status of the E-RABs. The MME then
sends the S1 MME STATUS TRANSFER message to the target eNB.
After receiving the handover command from the source cell, the UE performs

Confidential
synchronization with the target cell and connects to the target cell through the
Random Access Channel (RACH). The target cell replies with UL allocation and
timing advance.
13) After the random access to the target cell has been completed successfully, the
UE sends an RRCConnectionReconfigurationComplete message (that is, handover
complete) to the target cell. The downlink packet forwarded from the source eNB
can be transmitted to the UE. The uplink packet can be transmitted to the S-GW
from the UE through the target eNB
14) - 16) The target eNB sends a HANDOVER NOTIFY message to MME to
inform that the UE has changed the serving eNB/cell.
17) - 18) The MME sends the Modify Bearer Request message to the S-GW. The
downlink packet from the S-GW is immediately transmitted to the target eNB. The
downlink packet from the S-GW is immediately transmitted to the target eNB.
19) The S-GW transmits the Modify Bearer Response message to the MME. To
support packet re-arrangement in the target eNB, the S-GW transmits at least one
end marker packets to the previous path as soon as the path is changed.
20) If any of the conditions listed in Section 5.3.3.0 of TS 23.401 (6) is met, the
UE starts the Tracking Area Update procedure.
21) - 24) The source MME releases the resources of UE that are used in the source
eNB and the resources for data forwarding.
UE Measurement and Measurement Reporting Configuration

The eNB sends UE the measurement configuration information (refer to
MeasConfig IE in TS36.331) in the RRC Connection Reconfiguration message for
intra-LTE handover when call setup, hand-in, reestablishment or change of QCI
mobility group by E-RAB setup/modify/release.
The eNB extracts available E-UTRA carriers considering UE supported bands, UE
capability on measurement/handover and the serving cell’s configuration for intra-
LTE mobility. The extracted E-UTRA carriers are configured to UE as
measurement objects.
The following configurations are considered for extracting measurement objects:
• E-UTRA carrier frequencies (EARFCN_DL of CHG-EUTRA-FA)
(MEASUREMENTBAND_WIDTH, PRESENCE_ANT_PORT1,
NEIGH_CELL_CONFIG, and OFFSET_FREQ of CHG-EUTRA-FA).
• Carrier preference per each E-UTRA carrier frequency (PREFERENCE0 - 5
of CHG-EUTRA-FA)
Then eNB configures measurement event per the extracted E-UTRA carriers as
reporting configuration.
The following parameters are used for reporting configuration:
• Event type for intra-LTE handover (HANDOVER_TYPE of CHG-EUTRA-FA)
Confidential

A5CNFQ.)
Full Configuration
Full configuration is used to support intra-LTE handover to the eNB of an earlier
release. The target uses a full configuration and the previous configuration is
discarded by the UE. Since the source eNB may not be aware that target eNB is
using full configuration, there is no difference in the source eNB behaviour. The
target eNB does not retransmit data that was attempted delivery in the source eNB
to the UE to prevent data duplication.
The source eNB includes ue-ConfigRelease IE in HandoverPreparationInformation
message, ue-ConfigRelease IE indicates the RRC protocol release used for the
dedicated configuration of the UE. If the target eNB does not support the release of
RRC protocol which the source eNB configured to the UE, the target eNB may be
unable to comprehend the UE configuration provided by the source eNB. In this
case, the target eNB should use the full configuration option. The full
configuration option includes an initialization of the radio configuration, which
makes the configurations used in the source cell are not continued in the target cell
with the exception that the security algorithms are continued for the RRC re-
establishment. For reconfigurations involving the full configuration option, the
PDCP entities are newly established (SN and HFN do not continue) for all DRBs
irrespective of the RLC mode.
In case full configuration is indicated in RRCConnectionReconfiguration message,
the UE deletes current configuration and applies new configuration based on the
configuration provided by the target eNB. Security configuration is retained and
security algorithm is retained for re-establishment. SRBs are reconfigured. DRBs
are released and re-setup using new configuration.
Restricting Subsequent Handover Triggering to HO Preparation Failed Cells

Since SLR7.0, the eNB supports an option of restricting subsequent handover
triggering to the corresponding cells after a previous handover request is rejected.
The operator can enable/disable this option by using hoToPrepFailedCell
(CHG-HO-OPT).
To support this option, the eNB manages a list of HO preparation failed cells (a
maximum of eight) per UE. When handover target cell selection for subsequent
handover triggers, the eNB excludes the UE’s HO preparation failed cells from
handover target cell. If all the measured cells in the MR are included in the list of
the UE's HO preparation failed cell, then the eNB clears the list and triggers
handover to the target cell, which is the best cell among the measured cell.
Reducing Size of Handover Command Message

From this release, the eNB operations related to making Handover Command
message is changed that the message contains only necessary IEs that must be

Confidential
changed by comparing to the previous configuration used on source cell (delta

processing). Through this enhancement, the size of Handover Command message
can be reduced, thereby improving handover performance.
For the same purpose, the eNB supports the option for Scell configuration within
handover procedure. If this option is enabled, the Handover Command message
does not contain the IEs for Scell configuration. The Scell configuration is then
performed by additional RRC reconfiguration procedure after handover
completion.
The operator can enable/disable this option by using hoCmdIncludeScellAdd
(CHG-HO-OPT).
Counters for S1 HO
The counters for inter-eNB S1 handover are collected as follows:
• Counter family: HO_S1_OUT/HO_S1_IN
o Number of S1 HO preparation attempts (outgoing/incoming),
o Number of S1 HO preparation successes (outgoing/incoming),
o Number of S1 HO execution successes (outgoing/incoming),
o Number of S1 HO preparation failures per cause (outgoing/incoming),
o Number of S1 HO execution failures per cause (outgoing/incoming)
o S1 handover time (average/maximum): Time taken between sending S1
HO REQUEST ACKNOWLEDGE message to MME and receiving
handover complete indication from UE.
o S1 handover success rate
SYSTEM OPERATION
How to Activate
Preconditions

Confidential

• A3 event is preferred
• Run CHG-NBR-ENB and set NO_HO to false. It is controlled by NBR eNB
base.
Key Parameters
parameters.
parameters.
• CaInterFreq

Confidential
A3_OFFSET RSRP threshold used for triggering the EUTRA measurement report for Event A3.

PURPOSE The purpose for using Event A5. Not in current use. The definition is made for later
use.
P A5.
Q A5.

ENB_ID The eNB ID of the eNB to which E-UTRAN neighboring cell to the eNB belongs. If
the enbType value is macro eNB, 20 bit of the value is eNB ID. If the enbType
identifier.
TARGET_CELL_NUM The local cell ID of E-UTRAN neighboring cell to the eNB. It is used when creating
a cell identifier.

Confidential
the eNB belongs. It is a three-digit or two-digit number with each digit ranging from
0 to 9.
IND_OFFSET The cell individual offset to be applied to EUTRAN neighboring cell to the eNB. It is
used for UE measurement in RRC Connected mode.
IS_REMOVE_ALLOWED Whether to delete a certain neighboring cell to the eNB using the ANR (Automatic
Neighbor Relation) function.

Confidential
cell or not.
Parameter Descriptions of CHG-HO-OPT/RTRV-HO-OPT

hoToPrepFailedCell This parameter indicates if handover to preparation failed cell to be allowed or not.
• Off: Handover to preparation failed cells allowed.
• On: Handover to preparation failed cells is not allowed.
Counters and KPIs

S1 Out Handover InterS1OutAtt The number of attempts for S1 handover in SeNB
InterS1OutPrepSucc The number of successes for S1 handover preparation in
SeNB
InterS1OutSucc The number of successes for S1 handover execution in
SeNB
InterS1OutPrepFail_C Preparation fails due to reset notification (eNB failure or
pCcFail block restart) from ECMB or by ECCB block during inter
S1 handover preparation.
InterS1OutPrepFail_S Preparation fails due to S1AP specification cause during
1apCuFail inter S1 handover preparation.
InterS1OutPrepFail_S Preparation fails due to S1 SCTP link failure during inter
1apLinkFail S1 handover preparation.
InterS1OutPrepFail_S Preparation fails due to S1AP relocprep timeout (not
1apRpTo received) during the inter S1 handover preparation.
InterS1OutPrepFail_S Preparation fails due to receiving S1AP signaling during
1apSigFail inter S1 handover preparation.
InterS1OutFail_CpCc A call is released due to call control timeout in the
To protocol blocks (MAC, RLC, PDCP, GTP) during the inter
S1 handover execution.
InterS1OutFail_CpCc A call is released due to reset notification (eNB failure or
Fail block restart) from ECMB or by ECCB block during the
inter S1 handover execution.
InterS1OutFail_UpGtp A call is released due to the failure in the GTP block
Fail during the inter S1 handover execution.
InterS1OutFail_UpMa A call is released due to the failure in the MAC block
cFail during the inter S1 handover execution.
InterS1OutFail_UpPd A call is released due to the failure in the PDCP block
cpFail during the inter S1 handover execution.
InterS1OutFail_UpRlc A call is released due to the failure in the RLC block
InterS1OutFail_RrcSi A call is released due to receiving RRC signaling during

Confidential

gFail the inter S1 handover execution.
InterS1OutFail_S1ap A call is released due to the S1AP specification cause
CuFail during the inter S1 handover execution.
InterS1OutFail_S1apL A call is released due to the S1 SCTP link failure during
inkFail the inter S1 handover execution.
InterS1OutFail_S1ap A call is released due to S1AP relocoverall timeout (not
RoTO received) during the inter S1 handover execution.
InterS1OutFail_S1ap A call is released due to receiving S1AP signaling during
SigFail the inter S1 handover execution.
S1 In Handover InterS1InAtt S1 handover attempt count in TeNB
InterS1InPrepSucc S1 handover preparation success count in TeNB
InterS1InSucc S1 handover execution success count in TeNB
InterS1InPrep_FailCp Preparation fails due to call control timeout in the
CcTo protocol blocks (MAC, RLC, PDCP, GTP) during the inter
InterS1InPrep_FailCp Preparation fails due to reset notification (eNB failure or
CcFail block restart) from ECMB or by ECCB block during inter
InterS1InPrep_FailUp Preparation fails due to internal failure in the GTP block
GtpFail during the inter S1 handover preparation.
InterS1InPrep_FailUp Preparation fails due to internal failure in the MAC block
MacFail during the inter S1 handover preparation.
InterS1InPrep_FailUp Preparation fails due to internal failure in the PDCP block
PdcpFail during the inter S1 handover preparation.
InterS1InPrep_FailUp Preparation fails due to internal failure in the RLC block
RlcFail during the inter S1 handover preparation.
InterS1InPrep_FailCp Preparation fails due to insufficient backhaul-based eNB
BhCacFail resources during inter S1 handover preparation.
InterS1InPrep_FailCp Preparation fails due to insufficient capacity-based eNB
CapaCacFail resources during inter S1 handover preparation.
InterS1InPrep_FailCp Preparation fails due to insufficient QoS-based eNB
QosCacFail resources during inter S1 handover preparation.
InterS1InPrep_FailS1 Preparation fails due to S1AP specification cause during
apCuFail inter S1 handover preparation.
InterS1InPrep_FailS1 Preparation fails due to S1 SCTP link failure during inter
apLinkFail S1 handover preparation.
InterS1InPrep_FailS1 Preparation fails due to receiving S1AP signaling during
apSigFail inter S1 handover preparation.
InterS1InFail_CpCcTo A call is released due to call control timeout in the
protocol blocks (MAC, RLC, PDCP, GTP) during the inter
S1 handover execution.
InterS1InFail_CpCcFa A call is released due to reset notification (eNB failure or
il block restart) from ECMB or by ECCB block during the
inter S1 handover execution.
InterS1InFail_UpGtpF A call is released due to the failure in the GTP block
ail during the inter S1 handover execution.
InterS1InFail_UpMac A call is released due to the failure in the MAC block
InterS1InFail_UpPdcp A call is released due to the failure in the PDCP block

Confidential

InterS1InFail_UpRlcF A call is released due to the failure in the RLC block
ail during the inter S1 handover execution.
InterS1InFail_RrcHcT A call is released due to HO command timeout (not
o received) during the inter S1 handover execution.
InterS1InFail_RrcSigF A call is released due to receiving RRC signaling during
ail the inter S1 handover execution.
InterS1InFail_S1apCu A call is released due to the S1AP specification cause
InterS1InFail_S1apLin A call is released due to the S1 SCTP link failure during
kFail the inter S1 handover execution.
InterS1InFail_S1apSi A call is released due to receiving S1AP signaling during
gFail the inter S1 handover execution.
InterS1InFail_S1apSi A call is released due to S1AP signaling timeout (not
gTo received) during the inter S1 handover execution.
Handover Time IntraHOTime Time taken from transmitting the
RRCConnectionReconfiguration message to the UE until
after receiving the RRCConnection
ReconfigurationComplete message from the UE.
IntraHOTimeTot Sum of Intra HO Interrupt time
IntraHOTimeCnt Count of IntraHoTimeAvg collected
S1HOTime Average S1 HO interrupt time
S1HOTimeMax Average maximum S1 HO interrupt time
S1HOTimeTot Sum of S1 HO interrupt time
S1HOTimeCnt Count of S1HoTimeAvg collected
X2HOTime Average X2 HO interrupt time
X2HOTimeMax Average maximum X2 HO interrupt time
X2HOTimeTot Sum of X2 HO Interrupt time
X2HOTimeCnt Count of X2HoTimeAvg collected
MOBILITY (KPI) EutranMobilityHOS1O HOIS1Out success rate of E-UTRAN mobility
ut
sumHOS1Out_Att Total S1 handover attempt count in SeNB
sumHOS1Out_Succ Total S1 handover execution success count in SeNB
sumHOS1Out_PrepS Total S1 handover preparation success count in SeNB
ucc
EutranMobilityHOS1In HOS1In success rate of E-UTRAN mobility
sumHOS1In_Att Total S1 handover attempt count in TeNB
sumHOS1In_Succ Total S1 handover execution success count in SeNB
sumHOS1In_PrepSuc Total S1 handover preparation success count in TeNB
c
REFERENCE

Confidential

Confidential
LTE-SW1005, X2 Handover
INTRODUCTION
X2 handover is a handover between two adjacent eNBs using the X2 interface
(inter eNB handover through X2 interface). X2 based handover is used when there
is an available direct interface with the target eNB and the target eNB belongs to
the same MME group.
BENEFIT
different eNBs.
• Users in a connected state can be moving within E-UTRAN, with change of
serving cell.
DEPENDENCY
• Prerequisite Features
LTE-SW0521 (X2 Interface Management)
• Others
With Full Configuration, HFN is reset for all bearers and lossless HO is not
supported.
LIMITATION
None
SYSTEM IMPACT
capabilities.
This feature can be activated only when the LTE-SW0521 (X2 Interface
Management) feature is enabled.
FEATURE DESCRIPTION
X2 handover is a handover between two adjacent eNBs using the X2 interface
(inter eNB handover via X2 interface).
When eNB receives a measurement report including Event A3/A4/A5 for
handover from UE, eNB triggers intra-LTE handover to the best cell indicated in
the measurement report.
X2 handover is used when there is available direct interface with the target eNB,
Confidential
or the target eNB belongs to the same MME group.

eNB performs S1 handover with direct forwarding instead of X2 handover in case
X2 handover preparation was failed with specific failure cause (cause: Invalid
MME Group ID).
Figure below depicts the X2 handover procedure in E-UTRAN.
1) UE sends a Measurement Report including E-UTRAN measurements to the

source eNB.
2) The source eNB determines handover target cell based on the Measurement
Report (MR) and whether to trigger handover considering the serving cell
configuration for handover.
• Handover target cell is selected the best one in the measured cells to which
handover can be possible.

Confidential
• In case of PCI duplication: eNB checks whether the PCI of the determined
target cell exists in neighbor cell list (Neighbor Relation Table, NRT) or not. If
there are several neighbors with the same PCI (this case is called PCI
duplication), then eNB requests ECGI reporting to the UE to identity the target
cell. After obtaining a MR including the target cell's ECGI, eNB triggers a
handover.
3) The source eNB transmits the X2 HANDOVER REQUEST message including
the information necessary for handover to the target eNB.
4) The target eNB performs admission control for the incoming handover request.
If it is acceptable, the target eNB prepares the handover (for example, radio
resource allocation, creation for data forwarding resources, and so on.) and makes
the RRCConnectionReconfiguration message including the mobilityControlInfo IE
that tells the source eNB to perform the handover. The target eNB includes the
RRCConnectionReconfiguration message in the X2 HANDOVER REQUEST
ACKNOWLEDGE message and transmits it to the source eNB. This message
includes the accepted bearer list and a list of tunnel information for receiving
forwarded data if data forwarding can be possible.
5) The source eNB constructs the RRCConnectionReconfiguration message for
handover (that is, handover command) and it is sent to the UE.
The source eNB sends the X2 SN STATUS TRANSFER message to the target
eNB to transfer the uplink and the downlink PDCP SN status of the E-RABs.
After receiving the handover command from the source cell, the UE performs
synchronization with the target cell and connects to the target cell through the
Random Access Channel (RACH). The target cell replies with UL allocation and
timing advance.
6) After the random access to the target cell has been completed successfully, the
UE sends a RRCConnectionReconfigurationComplete message (that is, handover
complete) to the target cell.
7) The target eNB sends a S1 PATH SWITCH REQUEST message to serving
MME to inform that the UE has changed the serving eNB/cell.
8)~10) The MME sends the Modify Bearer Request message to the S-GW. The S-
GW changes the downlink data path into the target eNB. The S-GW transmits at
least one end marker to the source eNB through the previous path and releases the
user plane resource for the source eNB.
11) The S-GW transmits the Modify Bearer Response message to the MME.
12) The MME returns the S1 PATH SWITCH ACKNOWLEDGE message to the
target eNB.
13) The target eNB sends the X2 UE CONTEXT RELEASE message to the source
eNB to notify the handover has succeeded and to make the source eNB release its
resources.
If the source eNB receives the X2 UE CONTEXT RELEASE message, it releases
the radio resources and the control plane resources related to the UE context.
14) If Serving GW is relocated, the MME releases the UE’s resources that was
used in the source Serving GW.

Confidential

eNB sends UE the measurement configuration information (refer to MeasConfig
IE in TS36.331) in the RRC Connection Reconfiguration message for intra-LTE
handover when call setup, hand-in, reestablishment or change of QCI mobility
group by E-RAB setup/modify/release.
eNB extracts available E-UTRA carriers considering UE supported bands, UE
capability on measurement/handover and the serving cell’s configuration for intra-
LTE mobility. The extracted E-UTRA carriers are configured to UE as
measurement objects.
The following configurations are considered for extracting measurement objects:
• E-UTRA carrier frequencies (parameter: EARFCN_DL of CHG-EUTRA-FA)
(parameter: MEASUREMENTBAND_WIDTH, PRESENCE_ANT_PORT1,
NEIGH_CELL_CONFIG and OFFSET_FREQ of CHG-EUTRA-FA)
• Carrier preference per each E-UTRA carrier frequency (parameter:
PREFERENCE0~5 of CHG-EUTRA-FA)
Then eNB configures measurement event(s) per the extracted E-UTRA carriers as
The following parameters are used for reporting configuration:
• Event type for intra-LTE handover (parameter: HANDOVER_TYPE of CHG-
EUTRA-FA)
A5CNFQ.)
Full configuration
Full configuration is used to support intra-LTE handover to an eNB of an earlier
release. The target uses a full configuration and the previous configuration is
discarded by the UE. Since the source eNB may not be aware that target eNB is
using full configuration, there is no difference in the source eNB behaviour. The
target eNB does not resend data that was attempted delivery to the UE to prevent
data duplication.
The source eNB includes ue-ConfigRelease IE in HandoverPreparationInformation
message, ue-ConfigRelease IE indicates the RRC protocol release used for the
dedicated configuration of the UE. If the target eNB does not support the release of
RRC protocol which the source eNB configured to the UE, the target eNB may be
unable to comprehend the UE configuration provided by the source eNB. In this
case, the target eNB should use the full configuration option. Full configuration
option includes an initialization of the radio configuration, which makes the
configurations used in the source cell are not continued in the target cell with the
exception that the security algorithms are continued for the RRC re-establishment.

Confidential
For reconfigurations involving the full configuration option, the PDCP entities are
newly established (SN and HFN do not continue) for all DRBs irrespective of the
RLC mode.
In case full configuration is indicated in RRCConnectionReconfiguration message,
UE deletes current configuration and applies new configuration based on the
configuration provided by the target eNB. Security configuration is retained and
security algorithm is retained for re-establishment. SRBs are reconfigured. DRBs
are released and re-setup using new configuration.
Figure below depicts general message flow.
1) Source eNB sends X2 Handover Request message including ue-ConfigRelease

IE.
2) Target eNB sets FullConfig IE to true if ue-ConfigRelease IE is higher than
RRC Protocol releases of target eNB.
3) Target eNB sends X2 Handover Request Acknowledge message including
FullConfig IE.
4) Source eNB forwards RRC Connection Reconfiguration message to UE.
5) Source eNB transmits RRC Connection Reconfiguration Complete message to
Target eNB.
6) UE deletes current configuration of source eNB and applies new configuration
provided by target eNB except security configuration.
Counters for X2 HO
The counters for inter-eNB X2 handover are collected as follows:
• Counter family: HO_X2_OUT/HO_X2_IN
o Number of X2 HO preparation attempts (outgoing/incoming),

Confidential
o Number of X2 HO preparation successes (outgoing/incoming),

o Number of X2 HO execution successes (outgoing/incoming),
o Number of X2 HO preparation failures per cause (outgoing/incoming),
o Number of X2 HO execution failures per cause (outgoing/incoming)
o X2 handover time (average/maximum): Time taken between sending X2
HO REQUEST ACKNOWLEDGE message to source eNB and receiving
handover complete indication from UE.
o X2 handover success rate
SYSTEM OPERATION
How to Activate
Preconditions
• A3 event is preferred.
• Run CHG-NBR-ENB and set NO_X2 to false. It is controlled by NBR eNB
base.
Key Parameters

Confidential
parameters.
parameters.
• CaInterFreq
A3_OFFSET RSRP threshold used for triggering the EUTRA measurement report for Event
A3.
TIME_TO_TRIGGER timeToTrigger value for Event A3. The time-ToTrigger value is the period that
must be met for the UE to trigger a measurement report.

PURPOSE The purpose for using Event A5. Not in current use. The definition is made for
later use.

Confidential
A5_THRESHOLD2_RSRP RSRP threshold1 used for triggering the EUTRA measurement report for Event
A5.
A5_THRESHOLD2_RSRQ RSRP threshold2 used for triggering the EUTRA measurement report for Event
A5.
TIME_TO_TRIGGER timeToTrigger value for Event A5. The time-ToTrigger value is the period that
must be met for the UE to trigger a measurement report.

ENB_ID The eNB ID of the eNB to which E-UTRAN neighboring cell to the eNB belongs.
If the enbType value is macro eNB, 20 bit of the value is eNB ID. If the enbType
identifier.
TARGET_CELL_NUM The local cell ID of E-UTRAN neighboring cell to the eNB. It is used when
creating a cell identifier.
the eNB belongs. It is a three-digit or two-digit number with each digit ranging
from 0 to 9.
(MNC) of E-UTRAN neighboring cell to the eNB. It is a three-digit or two-digit
number with each digit ranging from 0 to 9.
(MCC) of E-UTRAN neighboring cell to the eNB. It is a three-digit number with
each digit ranging from 0 to 9.

Confidential
IND_OFFSET The cell individual offset to be applied to EUTRAN neighboring cell to the eNB. It
is used for UE measurement in RRC Connected mode.
IS_REMOVE_ALLOWED Whether to delete a certain neighboring cell to the eNB using the ANR
(Automatic Neighbor Relation) function.
cell or not.
Counters and KPIs

Display Name Type Name Type Description
X2 Handover Out InterX2OutAtt Attempt count for X2 handover from SeNB.
InterX2OutPrepSucc Success count for X2 handover preparation from
SeNB.
InterX2OutSucc Success count for X2 handover execution from
SeNB.
InterX2OutPrepFail_CP_ Preparation fails due to reset notification (eNB

Confidential

CC_FAIL failure or block restart) from ECMB or by ECCB
block during the inter X2 handover preparation.
InterX2OutPrepFail_S1A Preparation fails due to S1 SCTP link failure during
P_LINK_FAIL the inter X2 handover preparation.
InterX2OutPrepFail_S1A Preparation fails due to receiving S1AP signaling
P_SIG_FAIL during the inter X2 handover preparation.
InterX2OutPrepFail_X2A Preparation fails due to X2AP specification cause
P_CU_FAIL during the inter X2 handover preparation.
InterX2OutPrepFail_X2A Preparation fails due to X2 SCTP link failure during
P_LINK_FAIL the inter X2 handover preparation.
InterX2OutPrepFail_X2A Preparation fails due to X2AP relocprep timeout (not
P_RP_TO received) during the inter X2 handover preparation.
InterX2OutPrepFail_X2A Preparation fails due to receiving X2AP signaling
P_SIG_FAIL during the inter X2 handover preparation.
InterX2OutFail_CP_CC_ A call is released due to call control timeout in the
TO protocol blocks (MAC, RLC, PDCP, and GTP) during
the inter X2 handover execution.
InterX2OutFail_CP_CC_ A call is released due to reset notification (the eNB
FAIL failure or block restart) from ECMB or by the ECCB
block during the inter X2 handover execution.
InterX2OutFail_UP_GTP A call is released due to the failure in the GTP block
_FAIL during the inter X2 handover execution.
InterX2OutFail_UP_MAC A call is released due to the internal failure in the
_FAIL MAC block during the inter X2 handover execution.
InterX2OutFail_UP_PDC A call is released due to the internal failure in the
P_FAIL PDCP block during the inter X2 handover execution.
InterX2OutFail_UP_RLC A call is released due to the internal failure in the
_FAIL RLC block during the inter X2 handover execution.
InterX2OutFail_RRC_SI A call is released due to receiving RRC signaling
G_FAIL during the inter X2 handover execution.
InterX2OutFail_S1AP_C A call is released due to the S1AP specification
U_FAIL cause during the inter X2 handover execution.
InterX2OutFail_S1AP_LI A call is released due to the S1 SCTP link failure
NK_FAIL during the inter X2 handover execution.
InterX2OutFail_S1AP_SI A call is released due to receiving S1AP signaling
G_FAIL during the inter X2 handover execution.
InterX2OutFail_X2AP_C A call is released due to the X2AP specification
U_FAIL cause during the inter X2 handover execution.
InterX2OutFail_X2AP_LI A call is released due to the X2 SCTP link failure
NK_FAIL during the inter X2 handover execution.
InterX2OutFail_X2AP_R A call is released due to X2AP RelocOverall timeout
O_TO (not received) during the inter X2 handover
execution.
InterX2OutFail_X2AP_SI A call is released due to receiving the X2AP
G_FAIL signaling during the inter X2 handover execution.
X2 Handover In InterX2InAtt The number of attempts for X2 handover in TeNB
InterX2InPrepSucc The number of successes for X2 handover
preparation in TeNB
InterX2InSucc The number of successes for X2 handover
execution in TeNB

Confidential

InterX2InPrepFail_CP_C Preparation fails due to call control timeout in the
C_TO protocol blocks (MAC, RLC, PDCP, GTP) during the
inter X2 handover preparation.
InterX2InPrepFail_CP_C Preparation fails due to reset notification (eNB
C_FAIL failure or block restart) from ECMB or by ECCB
block during the inter X2 handover preparation.
InterX2InPrepFail_UP_G Preparation fails due to internal failure in the GTP
TP_FAIL block during the inter X2 handover preparation.
InterX2InPrepFail_UP_M Preparation fails due to internal failure in the MAC
AC_FAIL block during the inter X2 handover preparation.
InterX2InPrepFail_UP_P Preparation fails due to internal failure in the PDCP
DCP_FAIL block during the inter X2 handover preparation.
InterX2InPrepFail_UP_R Preparation fails due to internal failure in the RLC
LC_FAIL block during the inter X2 handover preparation.
InterX2InPrepFail_CP_B Preparation fails due to insufficient backhaul-based
H_CAC_FAIL eNB resources during the inter X2 handover
preparation.
InterX2InPrepFail_CP_C Preparation fails due to insufficient capacity-based
APA_CAC_FAIL eNB resources during the inter X2 handover
preparation.
InterX2InPrepFail_CP_Q Preparation fails due to insufficient QoS-based eNB
OS_CAC_FAIL resources during the inter X2 handover preparation.
InterX2InPrepFail_S1AP Preparation fails due to S1 SCTP link failure during
_LINK_FAIL the inter X2 handover preparation.
InterX2InPrepFail_S1AP Preparation fails due to receiving S1AP signaling
_SIG_FAIL during the inter X2 handover preparation.
InterX2InPrepFail_X2AP Preparation fails due to X2AP specification cause
_CU_FAIL during the inter X2 handover preparation.
InterX2InPrepFail_X2AP Preparation fails due to X2 SCTP link failure during
_LINK_FAIL the inter X2 handover preparation.
InterX2InPrepFail_X2AP Preparation fails due to receiving X2AP signaling
_SIG_FAIL during the inter X2 handover preparation.
InterX2InFail_CP_CC_T A call is released due to call control timeout in the
O protocol blocks (MAC, RLC, PDCP, GTP) during the
inter X2 handover execution.
InterX2InFail_CP_CC_F A call is released due to reset notification (eNB
AIL failure or block restart) from ECMB or by the ECCB
block during the inter X2 handover execution.
InterX2InFail_UP_GTP_ A call is released due to the failure in the GTP block
FAIL during the inter X2 handover execution.
InterX2InFail_UP_MAC_ A call is released due to the internal failure in the
FAIL MAC block during the inter X2 handover execution.
InterX2InFail_UP_PDCP A call is released due to the internal failure in the
_FAIL PDCP block during the inter X2 handover execution.
InterX2InFail_UP_RLC_ A call is released due to the internal failure in the
FAIL RLC block during the inter X2 handover execution.
InterX2InFail_RRC_HC_ A call is released due to HO command timeout (not
TO received) during the inter X2 handover execution.
InterX2InFail_RRC_SIG A call is released due to receiving RRC signaling

Confidential

InterX2InFail_S1AP_CU A call is released due to the S1AP specification
_FAIL cause during the inter X2 handover execution.
InterX2InFail_S1AP_LIN A call is released due to the S1 SCTP link failure
K_FAIL during the inter X2 handover execution.
InterX2InFail_S1AP_PA A call is released due to S1AP path switch timeout
TH_TO (not received) during the inter X2 handover
execution.
InterX2InFail_S1AP_SIG A call is released due to receiving S1AP signaling
InterX2InFail_X2AP_CU A call is released due to the X2AP specification
_FAIL cause during the inter X2 handover execution.
InterX2InFail_X2AP_LIN A call is released due to the X2 SCTP link failure
K_FAIL during the inter X2 handover execution.
InterX2InFail_X2AP_SIG A call is released due to receiving the X2AP
_FAIL signaling during the inter X2 handover execution.
InterX2InFail_X2AP_SIG A call is released due to X2AP signaling timeout (not
_TO received) during the inter X2 handover execution.
MOBILITY (KPI) EutranMobilityHOX2Out HOX2Out success rate of E-UTRAN mobility
sumHOX2Out_Att Total X2 handover attempt count in SeNB
sumHOX2Out_Succ Total X2 handover execution success count in SeNB
sumHOX2Out_PrepSucc Total X2 handover preparation success count in
SeNB
EutranMobilityHOX2In HOX2In success rate of E-UTRAN mobility
sumHOX2In_Att Total X2 handover attempt count in TeNB
sumHOX2In_Succ Total X2 handover execution success count in TeNB
sumHOX2In_PrepSucc Total X2 handover preparation success count in
TeNB
REFERENCE

Confidential
LTE-SW1006, Data Forwarding

INTRODUCTION
During handover, source eNB forwards PDCP SDUs in sequence to target eNB.
Direct data forwarding is used when a direct path between source eNB and target
eNB is available. Otherwise indirect data forwarding is used, where PDCP packets
are delivered to target eNB through S-GW.
BENEFIT
Users can obtain session continuity during handover within E-UTRAN, with
almost no interruption.
DEPENDENCY
Prerequisite Features: LTE-SW1004 (S1 handover), LTE-SW1005 (X2 handover)
LIMITATION
None
SYSTEM IMPACT
capabilities.
This feature can be activated only when the LTE-SW1004 (S1 Handover) or LTE-
SW1005 (X2 Handover) feature is enabled.
None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
The source eNB decides which of the EPS bearers are subject for forwarding of
packets from the source eNB to the target eNB. Samsung source eNB requests
downlink forwarding to the target eNB and the bearers that have accepted by the
target eNB are forwarded. Samsung target eNB always accepts downlink
forwarding if handover admission is success. If uplink forwarding, Samsung target
eNB requests to the source eNB according to system configuration by operator and

Confidential
the bearers that have accepted by the source eNB are forwarded. Samsung source
eNB always accepts the uplink forwarding request from the target eNB.
Following packets can be forwarded to the target eNB based on 3GPP standards:
• Downlink packets that have not been acknowledged by the UE (RLC-AM)
• Downlink packets for which transmission have not been completed (RLC-
UM)
• Fresh data arriving over S1 (RLC-AM/UM)
• Uplink data received out of sequence (RLC-AM)
Direct data forwarding is operated in the following two cases when there exists an
X2 connection between eNBs:
• Inter-eNB S1 handover
• Inter-eNB X2 handover
Figure below depicts X2/S1 handover data forwarding.
Direct data forwarding at Inter-eNB X2 handover

A handover occurs through X2 interface when the UE moves between eNBs in the
same MME group. If the X2 interface exists between different eNB cells, direct
data forwarding is operated (only applicable to radio bearers acting as RLC AM).
When performing handover through the X2 interface, the target eNB determines
whether to perform uplink data forwarding. The source eNB performs uplink data
forwarding only when the target eNB admits it. (Using operator set to true for
UPLINK_FORWARD using CHG-QCI-VAL)
During the handover, the RLC layer block of the source eNB assembles SDUs
through re-establishing the RLC to deliver the AM-mode uplink PDUs that
previously failed to be delivered to the PDCP layer block. In case of uplink data
forwarding, the PDCP layer block configures the PDCP SN status including
completion of SDU forwarding from the RLC layer block. If uplink data
forwarding is not operated, the PDCP layer block configures the PDCP SN status

Confidential
based on uplink data received so far.

Figure below depicts data forwarding at inter-eNB X2 handover.
1) The UE sends the MeasurementReport message according to rules, such as the

system information or specifications, and the source eNB decides whether to
accept the UE based on the MeasurementReport message and radio resources
management information.
2) The source eNB sends the HANDOVER REQUEST message and other
handover-related information (If disable for Data forwarding in source
eNB(SOURCE_DL_FORWARD in CHG-QCI-VAL), source eNB not include DL
Forwarding IE (optional) in HANDOVER REQUEST message) to the Target
eNB. It, then, operates management control according to the E-RAB QoS
information received.
3) The target eNB prepares the handover and creates the
RRCConnectionReconfiguration message including the mobilityControlInfo IE

Confidential
that allows the handover to be performed. The target eNB sends to the source eNB
the HANDOVER REQUEST ACKNOWLEDGE message containing
RRCConnectionReconfiguration. (If disable for Data forwarding in target eNB
(UPLINK_FORWARD/DOWNLINK_FORWARD in CHG-QCI-VAL), target
eNB not include Data forwarding information in HANDOVER REQUEST
ACKNOWLEDGE message)
4) The source eNB sends the UE the RRCConnectionReconfiguration message,
containing the needed parameter values to command the handover.
5) To send the uplink PDCP SN receiver status and the downlink PDCP SN
transmitter status of the E-RABs of which the PDCP status must be preserved, the
source eNB sends the SN STATUS TRANSFER message to the target eNB. (Data
forwarding can be possible even if it receives UE context release message during it
receives End marker or timer (FWD_END_TIMER) limits.)
6) Upon receiving the RRCConnectionReconfiguration message containing
mobilityControlInfo IE, the UE synchronizes with the target eNB and connects to
the target cell via the Random Access Channel (RACH). The target eNB responds
with UL allocation and timing advance.
7) After having connected to the target cell successfully, the UE notifies the target
cell that the handover procedure has been completed, using the RRCConnection
ReconfigurationComplete message.
8) The target eNB, using the PATH SWITCH REQUEST message, notifies the
MME that the UE has changed the cell.
9) The MME sends the Modify Bearer Request message to the S-GW, which
changes the downlink data path toward the target and sends one or more "end
markers" to the source eNB through the previous path, releasing user plane
resources for the source eNB. The source eNB sends one or more “end markers” to
the target eNB after all data from the source eNB gets forwarded to the target eNB.
10) The S-GW sends the Modify Bearer Response message to the MME.
11) The MME acknowledges the PATH SWITCH REQUEST message by issuing
the PATH SWITCH REQUEST ACKNOWLEDGE message.
12) The target eNB sends the UE CONTEXT RELEASE message to the source
eNB to notify the handover has succeeded and to make the source eNB release its
resources. If the source eNB receives the UE CONTEXT RELEASE message, it
releases the radio resources and the control plane resources related to the UE
context. (Data forwarding can be possible until source eNB send End Marker)
Data forwarding at Inter-eNB S1 handover

A handover is performed through the S1 interface when the UE moves between
cells of different eNBs. Generally, a handover is carried out through the X2
interface for two eNBs in the same MME, and through the S1 interface for the
eNBs in different MMEs. However, if the two eNBs in the same MME do not have
the X2 interface, the handover is performed through the S1 interface. If the
handover is done through the S1 interface and the X2 interface exists between the
two eNBs, direct data forwarding is operated through X2-U. If there is no X2
interface, indirect data forwarding is performed through S1-U.

Confidential
Figure below depicts data forwarding at inter-eNB S1 handover.

Confidential

Confidential
1) The source eNB makes a decision on an S1-based handover to the target eNB.
The decision can take place when there is no X2 connection to the target eNB, or
an inter-eNB handover of the target eNB is set to occur through S1.
2) The source eNB sends the HANDOVER REQUIRED message (If disable for
Data forwarding in source eNB (SOURCE_DL_FORWARD in CHG-QCI-VAL),
source eNB not include DL Forwarding IE (optional) in HANDOVER
REQUIRED message) to the MME, giving information on which bearer is used for
data forwarding and whether direct forwarding from the source eNB to the target
eNB is possible.
3) The MME sends to the target eNB the HANDOVER REQUEST message,
which creates, in the target eNB, bearer information and the UE context including
security context.
4) The target eNB sends the HANDOVER REQUEST ACKNOWLEDGE
message to the MME. (If disable for Data forwarding in target eNB
(UPLINK_FORWARD/DOWNLINK_FORWARD in CHG-QCI-VAL), target
eNB not include Data forwarding information in HANDOVER REQUEST
ACKNOWLEDGE message)
5) If indirect forwarding applies, the MME sends the Create Indirect Data
Forwarding Tunnel Request message to the S-GW.
6) The S-GW replies to the MME with the Create Indirect Data Forwarding
Tunnel Response message.
7) The MME sends the HANDOVER COMMAND message to the source eNB.
8) The source eNB creates the RRCConnectionReconfiguration message using the
Target to Source Transparent Container IE contained in the HANDOVER
COMMAND message and then sends it to the UE.
9) To send the PDCP and the HFN status of the E-RABs of which the PDCP
status must be preserved, the source eNB sends the eNB/MME STATUS
TRANSFER message to the target eNB via the MME. (Data forwarding can be
possible even if it receives UE context release message during it receives End
marker or timer (FWD_END_TIMER) limits.)
10) The source eNB must start forwarding the downlink data to the target eNB
through the bearer which was determined to be used for data forwarding. This can
be either direct or indirect forwarding.
11) The UE performs synchronization with the target eNB and connects to the
target cell via a RACH. The target eNB responds with UL allocation and timing
advance.
12) After having synchronized with the target cell, the UE notifies the target eNB
that the handover has been completed using the
RRCConnectionReconfigurationComplete message. The downlink packet
forwarded from the source eNB can be sent to the UE. The uplink packet can also
be sent from the UE to the S-GW via the target eNB.
13) The target eNB sends the HANDOVER NOTIFY message to the MME, which
starts the timer to inform when to release the source eNB resources and the
temporary resources used by the S-GW for indirect forwarding.

Confidential
14) For each PDN connection, the MME sends the Modify Bearer Request
message to the S-GW. The downlink packet is sent from the S-GW immediately to
the target eNB.
15) The S-GW sends the Modify Bearer Response message to the MME, and
sends one or more "end markers" packets to the previous path as soon as the path
changes to assist in reordering packets in the target eNB. The source eNB sends
one or more “end markers” to the target eNB after all data from the source eNB
gets forwarded to the target eNB.
16) If any of the conditions listed in Section 5.3.3.0 of TS 23.401 is met, the UE
starts the Tracking Area Update procedure.
17) When the timer started at step 13 expires, the MME sends the UE CONTEXT
RELEASE COMMAND message to the source eNB.
18) The source eNB releases the resources related to the UE and replies with the
UE CONTEXT RELEASE COMPLETE message. (Data forwarding can be
possible until source eNB send End Marker)
19) If indirect forwarding applies, the expiry of the timer started in the MME at
Step 13 causes the MME to send to the S-GW the Delete Indirect Data Forwarding
Tunnel Request message. This message allows release of temporary resources
allocated at Step 5 for indirect forwarding.
20) The S-GW replies to the MME with the Delete Indirect Data Forwarding
Tunnel Response message.
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
SOURCE_DL_FORWARD Source eNB is able to decide to support Data Forwarding depending on this
parameter value. This parameter is used for only Handover procedure.

Confidential
parameters.
Parameter Descriptions of CHG-PDCP-INF/RTRV-PDCP-INF
FWD_END_TIMER A period when PDCP of target eNB waits for end marker upon receiving a
Handover Complete message and source eNB waits for end marker upon
receiving a UE Context Release message in milliseconds.
Counters and KPIs

Table below outlines the main counters and main Key Performance Indicators
(KPIs) associated with this feature.
GTP Forward CntGtpDLEnbS1Nor The cumulated number of S1 downlink GTP packets
Traffic during the basis call.
CntGtpULEnbS1Nor The cumulated number of S1 uplink GTP packets
during the basis call.
CntGtpDLEnbS1Fw The cumulated number of forwarded packets
received in the S1 downlink during the S1 handover.
CntGtpULEnbS1Fw The cumulated number of packets forwarded to the
S1 uplink during the S1 handover.
CntGtpDLEnbX2Fw The cumulated number of forwarded packets
received in the X2 downlink during the X2 handover.
CntGtpULEnbX2Fw The cumulated number of packets forwarded to the
X2 uplink during the X2 handover.
ByteGtpDLEnbS1Nor The cumulated bytes of S1 downlink GTP packets
ByteGtpULEnbS1Nor The cumulated bytes of S1 uplink GTP packets
ByteGtpDLEnbS1Fw The cumulated bytes of forwarded packets received
in the S1 downlink during the S1 handover.
ByteGtpULEnbS1Fw The cumulated bytes of packets forwarded to the S1
uplink during the S1 handover.
ByteGtpDLEnbX2Fw The cumulated bytes of forwarded packets received
in the X2 downlink during the X2 handover.
ByteGtpULEnbX2Fw The cumulated bytes of packets forwarded to the X2
uplink during the X2 handover.
ThruGtpDLEnbS1Nor The average throughput of S1 downlink GTP packet
in the basis call
ThruGtpULEnbS1Nor The average throughput of S1 uplink GTP packet in
the basis call
ThruGtpDLEnbS1Fw The average throughput of forwarded packets
received in the S1 downlink during the S1 handover.
ThruGtpULEnbS1Fw The average throughput of packets forwarded to the
S1 uplink during the S1 handover.
ThruGtpDLEnbX2Fw The average throughput of forwarded packets
received in the X2 downlink during the X2 handover.
ThruGtpULEnbX2Fw The average throughput of packets forwarded to the
X2 uplink during the X2 handover.

Confidential
REFERENCE
[3] 3GPP 36.413: E-UTRA and E-UTRAN; S1 Application Protocol (S1AP)
[4] 3GPP 36.423: E-UTRA and E-UTRAN; X2 Application Protocol (X2AP)

Confidential
LTE-SW1007, Inter-Frequency Handover

INTRODUCTION
The Inter-Frequency Handover is mobility control feature between cells that use
different frequency band. An eNB provides UEs with measurement gap
information in order for the UEs to perform inter frequency search. Measurement
gap avoids scheduling of data for the UE during inter frequency scan periods.
When a user moves to a neighboring carrier area, the eNB processes the inter-
frequency handover procedure to ensure the service continuity in the LTE. The
eNB refers the inter-frequency measurement report by the UE for handover to the
neighboring carrier areas. After receiving the inter-frequency measurement result
by the UE, the eNB selects the handover target cell and processes the handover
preparation with a target cell/eNB. When the handover preparation with a target
cell/eNB is successful, the eNB instructs the UE to perform the inter-frequency
handover. The UE performs handover to the target cell specified by the eNB to
continue the service.
BENEFIT
• An operator can provide connected mobility to its subscribers between cells,
which have a different center frequency.
• Users in connected state can be moving within E-UTRAN, with change of
serving cell.
DEPENDENCY
Prerequisite Features:
• LTE-SW1003, Intra-eNB Handover
• LTE-SW1004, S1 Handover
• LTE-SW1005, X2 Handover
LIMITATION
None
SYSTEM IMPACT
capabilities.
This feature can be activated only when the LTE-SW1003 (Intra-eNB handover)
or LTE-SW1004 (S1 Handover), or LTE-SW1005 (X2 Handover) feature is
enabled.

Confidential

None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
During connection establishment with a UE, the eNB sends the measurement
configuration information to UE (refer to MeasConfig IE in TS36.331) in the RRC
Connection Reconfiguration message for intra-frequency handover. If inter-
frequency handover is enabled, the Event A2 for activation of inter-frequency
measurement is configured at this time.
The operator can enable/disable inter-frequency handover by using

INTER_FREQ_REDIR_SUPPORT (CHG-INTWO-OPT).
When the eNB receives Event A2 report message, it checks the purpose of the
Event A2. If the purpose is activating inter-frequency measurement, the eNB
configures neighboring E-UTRA frequencies as measurement objects and
configures measurement events for inter-frequency handover as reporting
configuration. At this time, the eNB configures Event A1 for activation of inter-
frequency measurement and also configures measurement gap if it is required for
inter-frequency measurement by UE capability. During measurement gap is
configured, the eNB does not transmit any signal or data to the UE in measurement
gap period.
When the eNB receives a report message with measurement event for inter-
frequency handover and inter-frequency handover can be possible, the eNB
performs inter-frequency handover procedure. The handover procedure is decided
according to whether the UE is moving between cells in the same eNB (Intra-eNB
HO) or moving between eNBs (Inter-eNB HO). In case of Inter-eNB HO, eNB
primarily chooses X2 handover when X2 connection between the serving eNB and
the target eNB is available and X2 handover to the target eNB can be possible.
Otherwise, the S1 handover is selected. Each handover procedures are explained in
detail in the following feature descriptions:
• Intra-eNB handover (see LTE-SW1003)
• S1 handover (see LTE-SW1004)
• X2 handover (see LTE-SW1005)

The eNB sends the measurement configuration information when the UE is in the
RRC_CONNECTED status. Then UE performs measurement of neighboring cells
and reports the measured information to the eNB in accordance with the
measurement configuration provided by the eNB.

Confidential
The following parameters are included in the measurement configuration provided

to the UE.
Measurement objects The object on which the UE must perform measurements.
The measurement object is a single E-UTRA carrier frequency for inter-frequency.
(Measurement object lists ordered by priority.)
Reporting configuration The reporting configuration list, each item of which consists of the reporting
criterion and the report format. The reporting criterion is the reference information
that the UE triggers to send a measurement report. It is either a periodical event or
a single event. The report format includes the quantity information and the related
information included by the UE in a measurement report (for example, number of
cells to report).
Measurement identities The measurement identity list, each item of which is associated with one
measurement object and one reporting configuration.
Quantity configuration Quantity configuration includes the measurement quantities and related filtering
information for all event evaluation, each of which is set by the RAT type.
Measurement gaps The period during which the UE performs measurements. UL/DL data
transmission is restricted during this period.
The eNB extracts a UE available E-UTRA carrier considering supported bands of

UE, capability on measurement/handover of UE, and the configuration of serving
cell for intra-LTE mobility. The extracted E-UTRA carriers are configured to UE
as measurement objects.
The following configuration is considered for extracting measurement objects:
• E-UTRA carrier frequencies (EARFCN_DL of CHG-EUTRA-FA)
(MEASUREMENTBAND_WIDTH, PRESENCE_ANT_PORT1,
NEIGH_CELL_CONFIG, and OFFSET_FREQ of CHG-EUTRA-FA)
• Carrier preference per each E-UTRA carrier frequency (PREFERENCE0~5 of
CHG-EUTRA-FA)
The eNB then configures measurement event per the extracted E-UTRA carriers as
Following parameters are used for reporting configuration:
• Event type for intra-LTE handover (HANDOVER_TYPE of CHG-EUTRA-FA)
A3 offset, A4/A5 threshold, hysteresis, time to trigger (CHG-EUTRA-
A4CNFQ/CHG-EUTRA-A5CNF/CHG-EUTRA-A5CNFQ.)
When measurement gap is configured, the eNB considers distribution of
measurement gap per UE as much as possible. The gap pattern of measurement
gap configuration (GAP_PATTERN_FOR_INTER_FA of CHG-MSGAP-INF) is
expressed in {0, 1} and the gap length and repetition period are shown as below.
IF the Gap Pattern Id is 0, the gapOffset is (0...39). If the Gap Pattern Id is 1, the
gapOffset is (0...79).

Confidential
Gap Pattern Id Transmission Gap Transmission Gap Minimum available time for inter-frequency
Length (TGL, ms) Repetition Period and inter-RAT measurements during 480
(TGRP, ms) ms period (Tinter1, ms)
0 6 40 60
1 6 80 30
RSRP+RSRQ Trigger Quantity Configuration

One trigger quantity is assigned for a measurement event per purpose either RSRP
or RSRQ that is, both RSRP and RSRQ cannot be mapped to the same purpose.
Otherwise, if RSRP + RSRQ trigger quantity configuration option is enabled
(TRIGGER_QUANTITY of CHG-EUTRA-AXCNF or CHG-EUTRA-AXCNFQ is
set to ‘BOTH’, Ax can be A2, A3, A4 or A5), the eNB configures two
measurement events for the same purpose with different trigger quantity that one is
RSRP and the other is RSRQ. This option can be applied to coverage-based
handover (configured by CHG-EUTRA-AXCNF) or service-based handover
(configured by CHG-EUTRA-AXCNFQ). Detail configuration parameters are
described in the following table.
Trigger Quantity Configuration Following A2 report

In case of Events for inter-frequency (A3/A4/A5) or inter-RAT mobility (B2),
trigger quantity can be set according to the previous A2 report which triggered the
new measurement event configuration. This option can be applied to coverage-
based handover (configured by CHG-EUTRA-AXCNF or CHG-{IRAT}-B2CNF)
or service-based handover (configured by CHG-EUTRA-AXCNFQ or CHG-
{IRAT}-B2CNFQ).
Once the A2 report is received and its purpose is activating inter-frequency or
inter-RAT measurement for coverage/service based handover, the eNB configures
subsequent measurement events (A1, A3, A4, A5 or B2) of the corresponding
purpose. If the trigger quantity of the subsequent measurement event is set to
‘ci_followA2Event’, the eNB configures the same trigger quantity of the received
A2 report as trigger quantity of the new measurement event. Detail configuration
parameters are described in the table below.
The figure below depicts the eNB behavior based on the above two option for
trigger quantity configuration.

Confidential
Trigger Quantity Options

Table below shows the supported options per purpose of measurement events.
• Measurement events for intra-LTE mobility
Measurement event CHG-EUTRA-AxCNF/CHG-EUTRA-AxCNFQ
PURPOSE TRIGGER_QUANTITY
Event A1 MeasGapDeact ci_rsrp, ci_rsrq, ci_followA2Event
others ci_rsrp, ci_rsrq
Event A2 LteHo, LteBlind, IRatHo, IRatBlind, Srvcc ci_rsrp, ci_rsrq, ci_both
Event A3/A4/A5 IntraLteHandover ci_rsrp, ci_rsrq, ci_followA2Event, ci_both

Confidential
Measurement event CHG-EUTRA-AxCNF/CHG-EUTRA-AxCNFQ

• Measurement events for IRAT mobility

Measurement event CHG-{IRAT}-B2CNF/CHG-{IRAT}-B2CNFQ, {IRAT} can be UTRA, GERAN, HRPD or
C1XRTT
Event B2 InterRatHandover, Srvcc ci_rsrp, ci_rsrq, ci_followA2Event
Handover Triggering-based on both RSRQ and RSRP Criteria

Since SLR7.0, the eNB supports a handover triggering option based on both
RSRQ and RSRP criteria. This option is applicable to coverage based or service
based handover by using RSRQ triggered event. During this option is enabled
(DOUBLE_CHECK_RSRQ_AND_RSRP of CHG-EUTRA-AXCNF or CHG-
EUTRA-AXCNFQ is set to TRUE, Ax can be A3, A4 or A5), if the eNB receives a
MR with RSRQ triggered event, then the eNB checks RSRP criteria
(A3_THRESHOLD_RSRP, A4_THRESHOLD_RSRP, and
A5_THRESHOLD2_RSRP of CHG-EUTRA-AXCNF or CHG-EUTRA-AXCNFQ)
for the received MR before handover triggering. Accordingly, if the RSRP criteria
is met, the eNB triggers a handover based on the received MR with RSRQ
triggered event. If not, eNB will not trigger any handover and discard the received
MR. This option can reduce numbers of call drop due to unstable (bad) RSRP level
in target cell after handover by using RSRQ triggered event.
Timer-based Deactivation of Measurement Gap

From SLR7.0 seg#3, the eNB supports Timer based deactiation of measurement
gap for inter-frequqncy or inter-RAT measurement to reduce bad impact to
throughput by measurement gap. This option is applicable to coverage-based (or
service-based) handover. During this option is enabled
(TIMER_BASED_GAP_DEACT_SUPPORT of CHG-INTWO-OPT or CHG-
INTWO-OPTQCI), the eNB start the pre-defined timer (GAP_DEACT_TIME of
CHG-TIMER-INF) when it configures inter-frequency or inter-RAT
measurement for coverage based (or service based) handover to a UE. If there are
no MRs till the timer is expired, the eNB releases measurement gap for inter-
frequency or inter-RAT measurement for coverage based or service based
handover, if possible. Timer-based deactivation of measurement gap can be
possible in case reporConfig for coverage-based (or service-based) mobility is
only configured to the corresponding UE.
Rel-12 Increased UE Carrier Monitoring

From SLR7.0 seg#3, the eNB supports Rel-12 Increased UE carrier monitoring. In
case of UE supporting this enhancement, UE measurement capability is extended.

Confidential
The UE, which indicate support for Increased UE carrier monitoring, is capable of
monitoring at least 8 FDD E-UTRA inter-frequency carriers and 8 TDD E-UTRA
inter-frequency carriers, depending on UE capability. (In pre-Rel-12, The UE is
capable of monitoring at least 3 FDD E-UTRA inter-frequency carriers, and 3
TDD E-UTRA inter-frequency carriers, depending on UE capability.)
The eNB supports the following related to this enhancement:
• Function on/off (INC_MON_EUTRA_SUPPORT of CHG-MEAS-FUNC)
• Configuration of the measurement scale factor (MEAS_SCALE_FACTOR of
CHG-MEAS-FUNC) and the performance group (normal/reduced) per E-
UTRA carriers (REDUCED_MEAS_PERFORMANCE of CHG-EUTRA-FA).
• If there is any E-UTRA carrier which is the reduced performance group
according to eNB configuration, eNB includes the reduced performance group
indicator for corresponding E-UTRA carrier, in SIB5 and UE measurement
configuration.
• The eNB includes the measurement scale factor in UE measurement
configuration, if it is configured.
Counters for Intra/Inter-Frequency HO

The counters for intra/inter-frequency HO are collected as follows:
• Counter family: HO_INTRA_FREQ_OUT
o Number of outgoing intra-freq. HO preparation attempts
o Number of outgoing intra-freq. HO preparation successes
o Number of outgoing intra-freq. HO execution successes
o Number of outgoing intra-freq. HO preparation failures per cause
o Number of outgoing intra-freq. HO execution failures per cause
• Counter family: HO_INTER_FREQ_OUT_WITH_GAP,
HO_INTER_FREQ_OUT_WITHOUT_GAP
o Number of outgoing inter-freq. HO preparation attempts (with
measurement gap/without measurement gap)
o Number of outgoing inter-freq. HO preparation successes (with
o Number of outgoing inter-freq. HO execution successes (with
o Number of outgoing inter-freq. HO preparation failures per cause (with
o Number of outgoing inter-freq. HO execution failures per cause (with
Since SLR 7.0.1, the following counters are added.
• Counter family: Outgoing Intra-Frequency Handover With Handover Cause,
Outgoing Inter-Frequency Handover With Handover Cause

Confidential
o Number of outgoing intra-freq./inter-freq. HO preparation attempts per

handover cause
o Number of outgoing intra-freq./inter-freq. HO preparation successes per
handover cause
o Number of outgoing intra-freq./inter-freq. HO execution successes per
handover cause
SYSTEM OPERATION
How to Activate
Preconditions
• LTE-SW1003 (Intra-eNB handover), LTE-SW1004 (S1 Handover) and LTE-
SW1005 (X2 Handover) features need to be enabled before this LTE-SW1007
feature work.
• There should be a configured EUTRAN neighboring cell having different
frequency than the current serving cell.
• No license key is required to activate this feature.
• Run CHG-EUTRA-FA and CHG-EUTRA-FAQCI, and set STATUS to EQUIP
and configure EUTRAN frequency information for inter frequencies.
• Run CHG-NBR-EUTRAN and configure EUTRAN neighboring cell
information manually, if ANR function is not activated.
• Run CHG-EUTRA-A1CNF and CHG-EUTRA-A1CNFQ, and set
ACTIVE_STATE of ci_A1PurposeMeasGapDeact purpose to Active.
ACTIVE_STATE of ci_A2PurposeLteHo purpose to Active.
ACTIVE_STATE of ci_A3PurposeIntraLteHandover purpose to Active.

Confidential
• Run CHG-EUTRA-FA and set STATUS for inter frequencies to N_EQUIP.
Key Parameters
parameters.
STATUS This parameter indicates whether to use the corresponding EUTRA
Frequency and it can be used only when it is set to EQUIP.
• N_EQUIP: The corresponding EUTRA Frequency is not used.
• EQUIP: The corresponding EUTRA Frequency is used.
Parameter Descriptions of CHG-EUTRA-FAQCI/RTRV-EUTRA-FAQCI

STATUS Whether the EUTRA FA is valid.
• N_EQUIP: Invalid.
• EQUIP: Valid.

ACTIVE_STATE This parameter indicates whether event A1 is enabled/disabled per target
frequency. This change will be applied to the UE from next RRC signaling
procedure (for example, Attach or Idle to Active). To avoid overload, a new
setting will not be updated to the current active UEs.
• Active: Event A1 is used. If HO of the target frequency is not needed in
the site, this is inactive.
Parameter Descriptions of CHG-EUTRA-A1CNFQ/RTRV-EUTRA-A1CNFQ


Confidential


frequency. If this is set to Inactive, the Event A3 is not configured. This
change will be applied to the UE from next RRC signaling procedure (for
example, Attach or Idle to Active). To avoid overload, a new setting will not
be updated to the current active UEs.



Confidential



parameters.
EARFCN_UL This parameter is the Absolute Radio Frequency Channel Number
(ARFCN) that is an Uplink EUTRA Carrier Frequency. Unlike the setting for
the downlink EARFCN, repeated entry check is not performed.

Confidential
[Related Specifications] 3GPP TS.36.101
EARFCN_DL This parameter is the Absolute Radio Frequency Channel Number
(ARFCN) that is a downlink EUTRA carrier frequency. This parameter is for
setting the downlink EARFCN for EUTRA Frequency. Run the Data Rule
Check (DRC) based on the EQUIP state to prevent duplicated entries.
[Related Specifications] 3GPP TS.36.101
MEAS_BANDWIDTH_USAGE This parameter indicates whether to use the
MEASUREMENT_BANDWIDTH value that is configured in EUTRA-FA.
The MEASUREMENT_BANDWIDTH is used only when it is set to Use. In
case of this parameter value is no_use, the allowedMeasBandwidth is not
included in the SystemInformationBlockType3. But the value corresponding
to the downlink bandwidth indicated by the DL Bandwidth included in
MasterInformationBlock applies to the UE.
MEASUREMENT_BANDWIDTH This parameter is the maximum allowable measurement bandwidth for a
EUTRA carrier frequency.
OFFSET_FREQ This parameter is used in the RRC Connection Reconfiguration message.
The offsetFreq is used to indicate a frequency specific offset to be applied
when evaluating candidates for cell re-selection or when evaluating
triggering conditions for measurement reporting. The value in dB. Value
dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on.
HANDOVER_TYPE This parameter is the handover type per carrier. The eNB sends the Report
Configuration Information in MeasConfig depend on this value.
• A3: Handover using Event A3.
MO_PRIORITY This parameter assigns measurement object priority to EUTRA FA and
used when composing measObject. Measurement object configuring the
FA that has higher priority is assigned smaller value of measObjectId.
Measurement object configuring the FA that has lower priority is assigned
higher value of measObjectId. Priority values range from 0 to 7, with 7
being the highest priority.
REDUCED_MEAS_PERFORM This parameter represents whether the assigned carrier is belonging to
ANCE Normal Measurement Performance Group or Reduced Measurement
Performance Group. Serving cell carrier cannot be set as Reduced
Measurement Performance Group.
• 0 : False : Normal Measurement Performance Group
• 1 : True : Reduced Measurement Performance Group

OFFSET_FREQ Frequency offset value applied to offsetFreq in RRC Connection
Reconfiguration.
HANDOVER_TYPE Handover Type per Carrier.
MO_PRIORITY This parameter assigns measurement object priority to EUTRA FA and
used when composing measObject. Measurement object configuring the
FA that has higher priority is assigned smaller value of measObjectId.
Measurement object configuring the FA that has lower priority is assigned
higher value of measObjectId. Priority values range from 0 to 7, with 7

Confidential
being the highest priority.

A1_THRESHOLD_RSRP This parameter is the RSRP threshold for Event A1 which is used to
perform measurement gap deactivation. Event A1 occurs when serving
becomes better than threshold. The UE could measure either Reference
Signal Received Power(RSRP) or Reference Signal Received
Quality(RSRQ) and TRIGGER_QUANTITY indicates it will operate based
on RSRP or RSRQ. This change will be applied to the UE from next RRC
signaling procedure (for example, attach or idle to active). To avoid
overload, a new setting will not be updated to the current active UEs. The
lower the parameter is, in the lower signal strength measurement gap is
deactivated. This parameter is set to a value between 0 - 97 using the unit
defined in the 3GPP TS36.331. Value used when the TRIGGER
QUANTITIY is set to RSRP. The actual RSRP measurement value must be
set to A1_THRESHOLD_RSRP - 140 (dBm).
[Related Specifications] 3GPP TS36.331
A1_THRESHOLD_RSRQ This parameter is the RSRQ threshold for Event A1 which is used to
Signal Received Power (RSRP) or Reference Signal Received Quality
(RSRQ) and TRIGGER_QUANTITY indicates it will operate based on
RSRP or RSRQ. This change will be applied to the UE from next RRC
signaling procedure (for example, Attach or Idle to Active). To avoid
QUANTITIY is set to RSRQ. The actual RSRQ measurement value must
be set to (A1_THRESHOLD_RSRQ - 40)/2 (dB).
HYSTERESIS This parameter is the hysteresis value of Event A1 during
ReportConfigEutra configuration. This information is used to determine the
entering condition [(Measurement Result - Hysteresis) Threshold] and
leaving condition [(Measurement Result + Hysteresis) Thresh]. The
hysteresis uses the unit defined in the TS36.331 and its range is 0 - 30.
The actual value is converted into hysteresis * 0.5 dB. This change will be
applied to the UE from next RRC signaling procedure (for example, Attach
or Idle to Active). To avoid overload, a new setting will not be updated to
the current active UEs.
TIME_TO_TRIGGER This parameter is the timeToTrigger value for the Event A1. The
timeToTrigger is the time which should be satisfied for the UE to trigger the
measurement report. The event A1 occurs only when a specific threshold
meet a threshold during the period of TIME_TO_TRIGGER and the
TIME_TO_TRIGGER can be set to a value 0 - 5120 ms as defined in the
TS.36.331. This change will be applied to the UE from next RRC signaling
rsrp/rsrq/followA2event. An UE transmits Event A1 when RSRP or RSRQ
meets a specific threshold according to TRIGGER_QUANTITY. If the

Confidential
TRIGGER_QUANTITY is RSRP, the A1_THRESHOLD_RSRP is used. If it
is RSRQ, the A1_THRESHOLD_RSRQ is used. If it is followA2event, A2
event TRIGGER_QUANTITY is used for A1 event. This change will be
• rsrp: The trigger quantity of this event is set RSRP.
• rsrq: The trigger quantity of this event is set RSRQ.
• followA2event: The trigger quantity of this event is set A2 event
TRIGGER_QUANTITY.
REPORT_QUANTITY This parameter is the information on quantity included in the measurement
report for the Event A1. It can be specified to be the same as the trigger
quantity, or to contain both RSRP and RSRQ value. This information is for
setting whether to report only values equal to the triggerQuantity (RSRP or
RSRQ), or all values (RSRP and RSRQ), when a device is reporting
measurement results. This change will be applied to the UE from next RRC
overload, a new setting will not be updated to the current active UEs.
• sameAsTriggerQuantity: If it is set to sameAsTriggerQuantity, the UE
transmits only the result corresponding to the TRIGGER_QUANTITY.
• both: A UE transmits both RSRP/RSRQ if the REPORT_QUANTITY is
set to both for the measurement result when transmitting Event A1.
MAX_REPORT_CELL This parameter is used to set up the maxReportCells of Event A1 during
ReportConfigEutra configuration. This information is maximum number of
neighbor cells that can be included in the measurement report for Event
A1. When transmitting the measurement report for Event A1, a UE can add
the measurement report of EUTRA neighbor cell as many as
MAX_REPORT_CELL if there is the measurement result of EUTRA
neighbor cell. This change will be applied to the UE from next RRC
REPORT_INTERVAL This parameter is the interval of measurement reports for the Event A1.
This information is used for setting the Measurement Report transmission
interval when a device is reporting measurement results. The
REPORT_INTERVAL must transmit a measurement report at the interval of
REPORT_INTERVAL as many times as specified in the
REPORT_AMOUNT if it meets the event A1 condition. This applies only
when the REPORT_AMOUNT is larger than 1. The REPORT_INTERVAL
can be set to 120 ms - 60 min.
REPORT_AMOUNT This parameter is used to set up the reportAmount of Event A1 during
ReportConfigEutra configuration. It is for setting the number of
measurement reports (Event A1) for a device reporting measurement
results. The REPORT_AMOUNT is the number of measurement report
transmission when the Event A1 condition is met. If the
REPORT_AMOUNT is larger than 1, the measurement report is transmitted
as many times as REPORT_AMOUNT according to the interval specified in
REPORT_INTERVAL. The REPORT_AMOUNT is set to 1 - infinity
according to the TS36.331. If it is set to infinity, a measurement report is
transmitted at the interval of REPORT_INTERVAL until the A1 leaving
condition is met. This change will be applied to the UE from next RRC

Confidential

Signal Received Power (RSRP) or Reference Signal Received
Quality(RSRQ) and TRIGGER_QUANTITY indicates it will operate based
on RSRP or RSRQ. This change will be applied to the UE from next RRC
QUANTITIY is set to RSRP. The actual RSRP measurement value must be
set to A1_THRESHOLD_RSRP - 140 (dBm).
Signal Received Power (RSRP) or Reference Signal Received Quality
(RSRQ) and TRIGGER_QUANTITY indicates it will operate based on
RSRP or RSRQ. This change will be applied to the UE from next RRC
QUANTITIY is set to RSRQ. The actual RSRQ measurement value must
be set to (A1_THRESHOLD_RSRQ - 40)/2 (dB).
rsrp/rsrq/followA2event. An UE transmits Event A1 when RSRP or RSRQ
meets a specific threshold according to TRIGGER_QUANTITY. If the
is RSRQ, the A1_THRESHOLD_RSRQ is used. If it is followA2event, A2
event TRIGGER_QUANTITY is used for A1 event. This change will be

Confidential
• followA2event: The trigger quantity of this event is set A2 event
TRIGGER_QUANTITY.

Confidential

perform measurement gap activation or redirection. In the serving cell, the
measurement is triggered by an event A2 that means the quality of
EUTRAN DL reference signal becomes worse than the absolute threshold.
The UE could measure either Reference Signal Received Power(RSRP) or
Reference Signal Received Quality(RSRQ) and TRIGGER_QUANTITY
indicates it will operate based on RSRP or RSRQ. This change will be
the current active UEs. TRIGGER_QUANTITY indicates it will operate
based on RSRP or RSRQ. The higher the parameter is, the stronger signal
strength measurement gap is activated and too frequent measurement gap
activation can impact service experience. The lower the parameter is, the
weaker signal strength measurement gap is activated and the later
measurement gap activation can impact HO success rate.
The UE could measure either Reference Signal Received Power (RSRP) or
Reference Signal Received Quality (RSRQ) and TRIGGER_QUANTITY
the current active UEs. The higher the parameter is, the stronger signal
rsrp/rsrq. An UE transmits Event A2 when RSRP or RSRQ meets a specific
threshold according to TRIGGER_QUANTITY. If the
is RSRQ, the A2_THRESHOLD_RSRQ is used. This change will be

Confidential
• both: The trigger quantity of this event is set RSRQ and RSRP.
GAP_REACT_OFFSET This parameter is used to set up A2 Threshold Offset for measurement gap
reactivation after timer based measurement gap deactivation during inter
frequency or inter RAT measurement.

Confidential
the current active UEs. TRIGGER_QUANTITY indicates it will operate
based on RSRP or RSRQ. The higher the parameter is, the stronger signal
applied to the UE from next RRC signaling procedure (e.g. Attach or Idle to
Active). To avoid overload, a new setting will not be updated to the current
active UEs. The higher the parameter is, the stronger signal strength
measurement gap is activated and too frequent measurement gap

Confidential
• both: The trigger quantity of this event is set RSRQ and RSRP.
GAP_REACT_OFFSET This parameter is used to set up A2 Threshold Offset for measurement gap
reactivation after timer based measurement gap deactivation during inter
frequency or inter RAT measurement.

Confidential

A3_OFFSET This parameter is the RSRP threshold for Event A3 that is triggered the
offset between neighbor reference signal and serving is more than the
absolute threshold. The serving cell performs intra eNB HO and inter-
frequency HO to the better cell if the frequency is configured to use the
event A3 triggering. The UE could measure either Reference Signal
Received Power (RSRP) or Reference Signal Received Quality (RSRQ)
and TRIGGER_QUANTITY indicates it will operate based on RSRP or
RSRQ. This change will be applied to the UE from next RRC signaling
setting will not be updated to the current active UEs. The higher the
parameter is, the less HO is performed and it can impact HO success rate,
The lower the parameter is, the more frequent HO is performed and it can
cause ping pong. This value needs to be optimized up to site environment.
A3_REPORT_ON_LEAVE This parameter indicates whether to report when an UE satisfies Event A3
leaving condition. This change will be applied to the UE from next RRC
signaling procedure (e.g. Attach or Idle to Active). To avoid overload, a new
• False: Set the A3ReportOnLeave parameter to False. Even when an UE
satisfies leaving condition, it is not reported (default).
• True: Set the A3ReportOnLeave parameter to True. When an UE
satisfies leaving condition, it is reported. This report can increase
signaling overhead, so the default value is False.
• followA2event: It indicates that the value of TriggerQuantity corresponds
with the value of A2 Event triggerQuantity.

Confidential
• both: It indicates that RSRP and RSRQ are used for triggerQuantity.
A3_OFFSET_FOR_RSRQ RSRQ threshold for Event A3 that is triggered the offset between neighbor
reference signal and serving is more than the absolute threshold. The
serving cell performs intra eNB HO and inter-frequency HO to the better
cell if the frequency is configured to use the event A3 triggering. The UE
could measure either Reference Signal Received Power(RSRP) or
the current active UEs. The higher the parameter is, the less HO is
performed and it can impact HO success rate. The lower the parameter is,

Confidential
the more frequent HO is performed and it can cause ping pong. This value
needs to be optimized up to site environment.
DOUBLE_CHECK_RSRQ_AND This parameter indicates support of the function that handover start in case
_RSRP that RSRP condition is satisfied when RSRQ based handover is executed.
A3_THRESHOLD_RSRP RSRP threshold that handover start in case that RSRP condition is
satisfied when RSRQ based handover is executed.

Received Power(RSRP) or Reference Signal Received Quality(RSRQ) and
TRIGGER_QUANTITY indicates it will operate based on RSRP or RSRQ.
This change will be applied to the UE from next RRC signaling procedure
(for example, Attach or Idle to Active). To avoid overload, a new setting will
not be updated to the current active UEs. The higher the parameter is, the
less HO is performed and it can impact HO success rate, The lower the
parameter is, the more frequent HO is performed and it can cause ping
pong. This value needs to be optimized up to site environment.

Confidential
• followA2event : It indicates that the value of TriggerQuantity corresponds
• both : It indicates that RSRP and RSRQ are used for triggerQuantity.

Confidential
could measure either Reference Signal Received Power (RSRP) or
the current active UEs. The higher the parameter is, the less HO is
performed and it can impact HO success rate. The lower the parameter is,
the more frequent HO is performed and it can cause ping pong. This value
needs to be optimized up to site environment.
A3_THRESHOLD_RSRP RSRP threshold that handover start in case that RSRP condition is
satisfied when RSRQ based handover is executed.

A4_THRESHOLD_RSRP This parameter is the RSRP threshold used for the Event A4 that occurs
when a neighbor becomes better than the threshold. The serving cell
performs intra- eNB HO and inter-frequency HO if the frequency is
configured to use the Event A4 triggering. The UE could measure either the
Reference Signal Received Power(RSRP) or the Reference Signal
Received Quality(RSRQ) and TRIGGER_QUANTITY indicates it will
operate based on RSRP or RSRQ. This change will be applied to the UE
from the next RRC signaling procedure (for example, Attach or Idle to
active UEs. The higher the parameter is, the later the HO is performed and
it can impact HO success rate, The lower the parameter is, the earlier the
HO is performed and it can cause ping pong. This value needs to be
optimized up to site environment.
A4_THRESHOLD_RSRQ This parameter is the RSRQ threshold used for the Event A4 that occurs
performs intra-eNB HO and inter-frequency HO if the frequency is
operate based on the RSRP or RSRQ. This change will be applied to the
UE from the next RRC signaling procedure (for example, Attach or Idle to

Confidential
• rsrp : It indicates that RSRP is used for triggerQuantity.
• rsrq : It indicates that RSRQ is used for triggerQuantity.
This information is for setting the Measurement Report transmission
transmit when the Event A4 condition is met. If the REPORT_AMOUNT is
larger than 1, the measurement report is transmitted as many times as

Confidential
REPORT_AMOUNT according to the interval specified in


Confidential

Confidential

A5_THRESHOLD1_RSRP This parameter is the A5_Threshold1 value of Event A5 during
ReportConfigEutra configuration. It range is 0 - 97. This value used when
the TRIGGER_QUANTITY is set to RSRP.
ReportConfigEutra configuration, it is set to 0 - 97. This value used when
A5_THRESHOLD1_RSRQ This parameter is the A5_Threshold1 value of Event A5 during
ReportConfigEutra configuration, it is set to 0 - 34. This value is used when
the TRIGGER_QUANTITY is set to RSRQ.
• rsrp: It indicates that RSRP is used for triggerQuantity.
• rsrq: It indicates that RSRQ is used for triggerQuantity.

Confidential


Confidential

Confidential
Parameter Descriptions of CHG-NBR-EUTRAN/RTRV-NBR-EUTRAN/CRTE-

ENB_ID The eNB ID of the eNB to which E-UTRAN neighboring cell to the eNB
belongs. If the enbType value is macro eNB, 20 bit of the value is eNB ID.
If the enbType value is home eNB, 28 bit of the value is eNB ID. It is used
when creating a cell identifier.
TARGET_CELL_NUM The local cell ID of E-UTRAN neighboring cell to the eNB. It is used when
ENB_TYPE The type of the eNB to which E-UTRAN neighboring cell to the eNB
belongs.
ENB_MCC The PLMN information (MCC) of the eNB to which E-UTRAN neighboring
cell to the eNB belongs. It is a three-digit number with each digit being from
0 to 9.
ENB_MNC The PLMN information (MNC) of the eNB to which E-UTRAN neighboring
cell to the eNB belongs. It is a three-digit or two-digit number with each digit
being from 0 to 9.
MCC0 The broadcast PLMN list information (MCC) of E-UTRAN neighboring cell
to the eNB. It is a three-digit number with each digit being from 0 to 9.
(MNC) of E-UTRAN neighboring cell to the eNB. It is a three-digit or two-
digit number with each digit being from 0 to 9.

Confidential
(MCC) of E-UTRAN neighboring cell to the eNB. It is a three-digit number
with each digit being from 0 to 9.
MNC1 The broadcast PLMN list information (MNC) of E-UTRAN neighboring cell
to the eNB. It is a three-digit or two-digit number with each digit being from
0 to 9.
0 to 9.
0 to 9.
0 to 9.
0 to 9.
EARFCN_UL The uplink EARFCN (E-UTRAN Absolute Radio Frequency Channel
Number) of EUTRAN neighboring cell to the eNB.
EARFCN_DL The uplink EARFCN (E-UTRAN Absolute Radio Frequency Channel
Number) of EUTRAN neighboring cell to the eNB.
IND_OFFSET The cell individual offset to be applied to EUTRAN neighboring cell to the
eNB. It is used for UE measurement in RRC Connected mode.
QOFFSET_CELL The cell quality offset to be applied to EUTRAN neighboring cell to the
eNB. It is used for UE cell re-selection in RRC Idle mode.
IS_REMOVE_ALLOWED Whether to delete a certain neighboring cell to the eNB using the ANR
(Automatic Neighbor Relation) function.
IS_COLOCATED This parameter defines whether this neighbor cell is co-located with the
serving cell or not.
• False: The neighboring cell is NOT colocated
Parameter Descriptions of CHG-INTWO-OPT/RTRV-INTWO-OPT

Confidential
MO_PRIORITY_SUPPORT This parameter controls the feature activation of measurement object
priority based measurement configuration.
• False(0) : moPriority not used.
• True(1) : moPriority used.
TIMER_BASED_GAP_DEACT_ This parameter indicates whether to provide the function of timer based
SUPPORT measurement gap deactivation during inter frequency or inter RAT
measurement.
• False(0): measurement gap deactivation not support.
• True(1): measurement gap deactivation support.
TIMER_BASED_GAP_REACT_ This parameter indicates whether to provide the function of measurement
SUPPORT gap reactivation after timer based measurement gap deactivation during
inter frequency or inter RAT measurement.
• False(0): measurement gap reactivation not support.
• True(1): measurement gap reactivation support.
Parameter Descriptions of CHG-INTWO-OPTQCI/RTRV-INTWO-OPTQCI

MO_PRIORITY_SUPPORT This parameter controls the feature activation of measurement object
priority based measurement configuration.
• False(0) : moPriority not used.
• True(1) : moPriority used.
TIMER_BASED_GAP_DEACT_ This parameter indicates whether to provide the function of timer based
SUPPORT measurement gap deactivation during inter frequency or inter RAT
measurement.
• False(0): measurement gap deactivation not support.
• True(1): measurement gap deactivation support.
TIMER_BASED_GAP_REACT_ This parameter indicates whether to provide the function of measurement
SUPPORT gap reactivation after timer based measurement gap deactivation during
inter frequency or inter RAT measurement.
• False(0): measurement gap reactivation not support.
• True(1): measurement gap reactivation support.

GAP_DEACT_TIME This parameter is the timer to decide triggering time for measurement gap
deactivation during inter frequency or inter RAT measurement.
Parameter Descriptions of CHG-MEAS-FUNC/RTRV-MEAS-FUNC

INC_MON_EUTRA_SUPPORT This parameter represents whether Rel-12 increased UE carrier monitoring
for E-UTRA carriers function is enabled or not.
• 0 : False : Rel-12 Increased UE carrier monitoring for E-UTRA carriers is
disabled
• 1 : True : Rel-12 Increased UE carrier monitoring for E-UTRA carriers is
enabled
MEAS_SCALE_FACTOR This parameter represents measurement scaling factor defining the

Confidential
relaxation to be applied to the requirements for carriers measured with
reduced measurement performance.
• 0 : cf1 : sf-EUTRA-cf1 is applied as measurement scaling factor
• 1 : cf2 : sf-EUTRA-cf2 is applied as measurement scaling factor
Counters and KPIs

Table below outlines the main Key Performance Indicators (KPIs) associated with
this feature.
Outgoing Intra-Frequency IntraFreqOutAtt The cumulated number of Outgoing intra-
Handover frequency handover attempt count
IntraFreqOutPrepSucc The cumulated number of Outgoing intra-
frequency handover preparation success count
IntraFreqOutSucc The cumulated number of Outgoing intra-
frequency handover execution success count
IntraFreqOutPrepFail_Cp The cumulated number when preparation fails
CcFail due to a reset notification (eNB failure or block
restart) from ECMB or ECCB resource
allocation failure during the intra eNB, inter X2
or inter S1 HO preparation procedure when the
frequency information is the same between the
source eNB (cell) and target eNB (cell).
IntraFreqOutPrepFail_S1 The cumulated number when execution fails
apCuFail since a S1AP specification cause occurs
during the intra eNB, inter X2 or inter S1 HO
preparation procedure when the frequency
information is the same between the source
eNB (cell) and target eNB (cell).
IntraFreqOutPrepFail_S1 This counter is not collected in the system
apLinkFail
IntraFreqOutPrepFail_S1 The cumulated number when preparation fails
apRpTo due to a timeout that has occurred when a S1
handover command message is not received
from MME after the SeNB transmits a S1
handover required message to MME during
the inter S1 HO preparation procedure when
the frequency information is the same between
the source eNB (cell) and target eNB (cell).
IntraFreqOutPrepFail_S1 The cumulated number when preparation fails
apSigFail due to receiving S1AP UE CONTEXT
RELEASE COMMAND or S1AP RESET from
MME during the intra eNB, inter X2 or inter S1
HO preparation procedure when the frequency
IntraFreqOutPrepFail_X2 The cumulated number when preparation fails
apCuFail since the serving eNB receives a handover
preparation failure message from the target
eNB after transmitting a handover request
message to the target eNB during the inter X2

Confidential

IntraFreqOutPrepFail_X2 This counter is not collected in the system
apLinkFail
IntraFreqOutPrepFail_X2 The cumulated number when preparation fails
apRpTo due to a timeout that has occurred since the
serving eNB transmits a handover request
message to the target eNB and does not
receive a handover request acknowledge
message from the target eNB during the inter
X2 HO preparation procedure when the
IntraFreqOutPrepFail_X2 This counter is not collected in the system
apSigFail
IntraFreqOutFail_CpCcT The cumulated number of releases due to a
o timeout that has occurred since a response
message is not received after a call control
message is transmitted to the inner block
execution procedure when the frequency
IntraFreqOutFail_CpCcF The cumulated number when execution fails
ail due to a reset notification (eNB failure or block
IntraFreqOutFail_UpGtpF The cumulated number when execution fails
ail due to not receiving a response message from
the GTP block during the intra eNB, inter X2 or
inter S1 HO execution procedure when the
IntraFreqOutFail_UpMac The cumulated number when execution fails
Fail since Fail is received as a response message
from the MAC block or an audit mismatch
occurs with the MAC block during the intra
eNB, inter X2 or inter S1 HO preparation
procedure when the frequency information is
the same between the source eNB (cell) and
target eNB (cell).
IntraFreqOutFail_UpPdcp The cumulated number when execution fails
Fail since Fail is received as a response message
from the PDCP block during the intra eNB,
inter X2 or inter S1 HO execution procedure
when the frequency information is the same
between the source eNB (cell) and target eNB
(cell).
IntraFreqOutFail_UpRlcF The cumulated number when execution fails
ail since Fail is received as a response message
from the RLC block or an audit mismatch
occurs with the RLC block during the intra
eNB, inter X2 or inter S1 HO execution

Confidential

the same between the source eNB (cell) and
target eNB (cell).
IntraFreqOutFail_RrcSig This counter is not collected in the system
Fail
IntraFreqOutFail_S1apC The cumulated number of releases due to a
uFail S1AP specification cause that occurs during
intra eNB, inter X2 or inter S1 HO execution
when the frequency information is the same
(cell).
IntraFreqOutFail_S1apLi The cumulated number when execution fails
nkFail since the S1AP link status is changed to 'Out
of Service' during the intra eNB, inter X2 or
IntraFreqOutFail_S1apR The cumulated number of timeouts that occur
OTo during the inter S1 HO execution procedure
when the source eNB transmits a RCC
connection reconfiguration message to the UE
and the target eNB receives a RRC connection
reconfiguration complete message from the
UE, then an UE context release command
message is transmitted to the source eNB but
the source eNB does not receive the message.
IntraFreqOutFail_S1apSi The cumulated number when execution fails
gFail due to receiving S1AP UE CONTEXT
RELEASE COMMAND or S1AP RESET from
MME during the intra eNB, inter X2 or inter S1
HO execution procedure when the frequency
IntraFreqOutFail_X2apC This counter is not collected in the system
uFail
IntraFreqOutFail_X2apLi This counter is not collected in the system
nkFail
IntraFreqOutFail_X2apR The cumulated number of timeouts that occur
oTo during the inter X2 HO execution procedure
when the source eNB transmits a RCC
connection reconfiguration message to the UE
and the target eNB receives a RRC connection
IntraFreqOutFail_X2apSi The cumulated number of releases due to
gFail receiving X2AP signaling during the inter X2

Outgoing Inter-frequency InterFreqMeasGapOutAtt The cumulated number of outgoing inter-
Handover with Measurement frequency handover (measurement gap

Confidential

Gap assisted) attempt count
InterFreqMeasGapOutPr The cumulated number of outgoing inter-
epSucc frequency handover (measurement gap
assisted) preparation success count
InterFreqMeasGapOutSu The cumulated number of outgoing inter-
cc frequency handover (measurement gap
assisted) execution success count
InterFreqMeasGapOutPr The cumulated number when execution fails
epFail_CP_CC_FAIL due to a reset notification (eNB failure or block
frequency information is different between the
source eNB (cell) and target eNB (cell) and the
measurement gap is used.
InterFreqMeasGapOutPr The cumulated number when execution fails
epFail_S1AP_CU_FAIL since a S1AP specification cause occurs
information is different between the source
eNB (cell) and target eNB (cell) and the
InterFreqMeasGapOutPr This counter is not collected in the system
epFail_S1AP_LINK_FAIL
InterFreqMeasGapOutPr The cumulated number when preparation fails
epFail_S1AP_RP_TO due to a timeout that has occurred when a S1
the frequency information is different between
the source eNB (cell) and target eNB (cell) and
the measurement gap is used.
epFail_S1AP_SIG_FAIL since S1AP UE CONTEXT RELEASE
COMMAND or S1AP RESET message is
received from MME during the intra eNB, inter
X2 or inter S1 HO preparation procedure when
epFail_X2AP_CU_FAIL since the serving eNB receives a handover
epFail_X2AP_LINK_FAIL
epFail_X2AP_RP_TO due to a timeout that has occurred since the

Confidential

epFail_X2AP_SIG_FAIL
InterFreqMeasGapOutFai The cumulated number of releases due to a
l_CP_CC_TO timeout that has occurred since a response
InterFreqMeasGapOutFai The cumulated number when execution fails
l_CP_CC_FAIL due to a reset notification (eNB failure or block
or inter S1 HO execution procedure when the
l_UP_GTP_FAIL since Fail is received as a response message
from the GTP block during the intra eNB, inter
X2 or inter S1 HO execution procedure when
l_UP_MAC_FAIL since Fail is received as a response message
different between the source eNB (cell) and
target eNB (cell) and the measurement gap is
used.
l_UP_PDCP_FAIL since Fail is received as a response message
when the frequency information is different
(cell) and the measurement gap is used.
l_UP_RLC_FAIL since Fail is received as a response message
used.

Confidential

InterFreqMeasGapOutFai This counter is not collected in the system
l_RRC_SIG_FAIL
InterFreqMeasGapOutFai The cumulated number of releases due to a
l_S1AP_CU_FAIL S1AP specification cause that occurs during
(cell) and the measurement gap is used.
l_S1AP_LINK_FAIL since the S1AP link status is changed to 'Out
InterFreqMeasGapOutFai The cumulated number of timeouts that occur
l_S1AP_RO_TO during the inter S1 HO execution procedure
(cell) and the measurement gap is used, the
source eNB transmits a RCC connection
reconfiguration message to the UE and the
target eNB receives a RRC connection
InterFreqMeasGapOutFai The cumulated number when preparation fails
l_S1AP_SIG_FAIL since S1AP UE CONTEXT RELEASE
l_X2AP_CU_FAIL
l_X2AP_LINK_FAIL
InterFreqMeasGapOutFai The cumulated number of timeouts that occur
l_X2AP_RO_TO during the inter X2 HO execution procedure
(cell) and the measurement gap is used, the
source eNB transmits a RCC connection
InterFreqMeasGapOutFai The cumulated number of releases due to
l_X2AP_SIG_FAIL receiving X2AP signaling during the inter X2

Confidential


Outgoing Inter-Frequency InterFreqNoMeasGapOut The cumulated number of outgoing inter-
Handover without Measurement Att frequency handover (no measurement gap
Gap assisted) attempt count
InterFreqNoMeasGapOut The cumulated number of outgoing inter-
PrepSucc frequency handover (no measurement gap
assisted) preparation success count
InterFreqNoMeasGapOut The cumulated number of outgoing inter-
Succ frequency handover (no measurement gap
assisted) execution success count
InterFreqNoMeasGapOut The cumulated number when execution fails
PrepFail_CpCcFail due to a reset notification (eNB failure or block
measurement gap is not used.
PrepFail_S1apCuFail since a S1AP specification cause occurs
InterFreqNoMeasGapOut This counter is not collected in the system
PrepFail_S1apLinkFail
InterFreqNoMeasGapOut The cumulated number when preparation fails
PrepFail_S1apRpTo due to a timeout that has occurred when a S1
the measurement gap is not used.
PrepFail_S1apSigFail since S1AP UE CONTEXT RELEASE
X2 or inter S1 HO preparation procedure when
PrepFail_X2apCuFail since the serving eNB receives a handover

Confidential

PrepFail_X2apLinkFail
PrepFail_X2apRpTo due to a timeout that has occurred since the
PrepFail_X2apSigFail
InterFreqNoMeasGapOut The cumulated number of releases due to a
Fail_CpCcTo timeout that has occurred since a response
Fail_CpCcFail due to a reset notification (eNB failure or block
or inter S1 HO execution procedure when the
Fail_UpGtpFail since Fail is received as a response message
from the GTP block during the intra eNB, inter
Fail_UpMacFail since Fail is received as a response message
not used.
Fail_UpPdcpFail since Fail is received as a response message
(cell) and the measurement gap is not used.
Fail_UpRlcFail since Fail is received as a response message

Confidential

not used.
Fail_RrcSigFail
InterFreqNoMeasGapOut The cumulated number of releases due to a
Fail_S1apCuFail S1AP specification cause that occurs during
(cell) and the measurement gap is not used.
Fail_S1apLinkFail since the S1AP link status is changed to 'Out
InterFreqNoMeasGapOut The cumulated number of timeouts that occur
Fail_S1apRoTo during the inter S1 HO execution procedure
(cell) and the measurement gap is not used,
the source eNB transmits a RCC connection
Fail_S1apSigFail since S1AP UE CONTEXT RELEASE
Fail_X2apCuFail
Fail_X2apLinkFail
InterFreqNoMeasGapOut The cumulated number of timeouts that occur
Fail_X2apRoTo during the inter X2 HO execution procedure
(cell) and the measurement gap is not used,
the source eNB transmits a RCC connection

Confidential

InterFreqNoMeasGapOut The cumulated number of releases due to
Fail_X2apSigFail receiving X2AP signaling during the inter X2

MRs triggered by serving cell A1event_MeasGapDeact This Counter is the cumulated number when a
A1 event measurement report message for
Measurement Gap Deactivation is received
from the UE.
A1event_CaPeriodicMr This Counter is the cumulated number when a
Smart Carrier Aggregation Periodic MR is
received from the UE.
A1event_CaInterFreq This Counter is the cumulated number when a
A1 event measurement report message for CA
inter-frequency is received from the UE.
A2event_LteHo This Counter is the cumulated number when a
Inter-Freq Handover is received from the UE.
A2event_LteBlind This Counter is the cumulated number when a
Inter-Frequency Redirection is received from
the UE.
A2event_IratHo This Counter is the cumulated number when a
Inter-Rat Handover is received from the UE.
A2event_IratBlind This Counter is the cumulated number when a
Inter-Rat Redirection is received from the UE.
A2event_CA This Counter is the cumulated number when a
Scell Release is received from the UE.
A2event_CaPeriodicMr This Counter is the cumulated number when a
Smart Carrier Aggregation Periodic Mr is
A2event_Srvcc This Counter is the cumulated number when a
Single Radio Voice Call Continuity is received
from the UE.
A2event_Mdt This Counter is the cumulated number when a
Minimization of Drive Tests is received from
the UE.
A2event_CaInterFreq This Counter is the cumulated number when a
Inter Frequency Carrier Aggregation is

Confidential

Discard MRs by Handover DiscardA3byRsrpThresh The cumulated number of A3 Event MR
Threshold old discarded because received MR RSRP value
do not satisfy RSRP threshold in reference
with the source eNB for each cell.
DiscardA4byRsrpThresh The cumulated number of A4 Event MR
old discarded because received MR RSRP value
DiscardA5byRsrpThresh The cumulated number of A5 Event MR
old discarded because received MR RSRP value

Outgoing Intra-Frequency IntraFreqOutWithHoCaus The cumulated number of Outgoing intra-
Handover With Handover Cause eAtt frequency handover attempt count
IntraFreqOutWithHoCaus The cumulated number of Outgoing intra-
ePrepSucc frequency handover preparation success count
IntraFreqOutWithHoCaus The cumulated number of Outgoing intra-
eSucc frequency handover execution success count

Outgoing Inter-Frequency InterFreqOutWithHoCaus The cumulated number of outgoing inter-
Handover With Handover Cause eAtt frequency handover attempt count
InterFreqOutWithHoCaus The cumulated number of outgoing inter-
ePrepSucc frequency handover preparation success count
InterFreqOutWithHoCaus The cumulated number of outgoing inter-
eSucc frequency handover execution success count
REFERENCE

Confidential
LTE-SW1008, Inbound Mobility to HeNB

(CSG/Hybrid Cells)
INTRODUCTION
In 3GPP specification Release 8, there is no description about the mechanisms for
inbound handover to HeNB. The main challenge with supporting inbound
handover to a HeNB is for the source macro eNB to identify the target HeNB. In
normal macro cell operation, the operator is expected to plan the allocation of PCIs
to neighboring macro cells in such a way that the PCI of a macro cell is locally
unique.
However, the HeNB is expected to be deployed in an unplanned manner; hence,
under a given macro cell coverage, there might be a large number of HeNBs
configured with the same PCI (considering that there are a limited number of
available PCIs and the HeNBs is forced to reuse PCI values). When UE detects a
HeNB PCI and sends a measurement report to the network, the network cannot
ensure that target cell PCI the UE reported is based solely on the reported PCI.
This so-called PCI confusion issue has to be resolved to allow successful inbound
handover to a HeNB.
BENEFIT
• You can provide connected mobility to its subscribers toward CSG/Hybrid
cells.
• LTE users in connected state can be moving toward its own CSG cells or
Hybrid cells.
DEPENDENCY
• Others
If target CSG/hybrid cell is shared among several PLMNs, then 3GPP R12 UE
support inbound mobility to a shared CSG cell should be supported.
LIMITATION
• Device and EPC, HeNB related feature (indoor small cell)
• To support this feature, UE device requires intra/interFreqProximityIndication
and intra/interFreqSI-AcqisitionForHO.
• To support this feature, UE device needs to support AdditionalSI-Info-r9 with
CSG-memberstatus-r9 and CSG-idnetity-r9.
• If Release 12 or later UE does not support inbound mobility to a shared CSG
cell enhancement, unexpected handover can happen or MR can be ignored

Confidential
during handover to shared CSG/Hybrid cell.
SYSTEM IMPACT
FEATURE DESCRIPTION
In this feature, mobility to CSG/Hybrid handover is covered: Macro to HeNB
(CSG/Hybrid) handover.
While the UE is in RRC_CONNECTED state, the UE performs normal
measurement and mobility procedures based on configuration provided by the
network. Basically, handover to a HeNB follows the framework of UE assisted
network controlled handover, but there are some differences in three aspects,
comparing the normal handover procedure:
• Proximity Estimation: To report the global identity of the target cell, the UE
needs to first read the SI of the target cell. To do this the UE detects using the
autonomous search function if it is likely to be in the coverage of a CSG or
hybrid cell whose CSG ID is in the UE CSG Whitelist. Depending on UE
capabilities, the UE may then provide the source cell with an indication of
proximity to trigger handover preparation if needed. Based on this proximity
indication, the source cell may configure.
• PSC/PCI Confusion: Due to the typical cell size of HeNBs being much smaller
than macro cells, there can be multiple HeNBs within the coverage of the
source eNB that have the same PCI. This leads to a condition referred to as
PCI confusion, wherein the source eNB is unable to uniquely determine the
target cell for handover from measurement reports received from the UE. PCI
confusion is solved by the UE reporting the global identity of the target cell.
Upon receiving a command from the network, the UE reads the system
information of the target cell and reports it back to the network. To read the
information, the UE creates autonomous gaps temporarily aborting
communication with the serving cell.
• Access Control: The membership status of the UE in the CSG of the target
HeNB is important for HO. For the case when the target cell is a CSG cell, HO
should be performed only if the UE is a member. For the case when the target
cell is a hybrid cell, the prioritization of allocated resources may be performed
based on the UE membership status. Access control is done by two step
process, where first the UE reports the membership status based on the
observed CSG ID and CSG Whitelist, and then the network verifies the
reported status. The UE reports the following information for the target cell:
o For target cell in EUTRAN: Cell Global ID, TAC, CSG ID, and CSG
Member Status
o If the target cell is a CSG cell, HO should be initiated only if the CSG
Member status reported by the UE is positive.
• PLMN Selection: In case the cell is shared by multi PLMN, UE reports the
subset of the broadcasted PLMN identities passing PLMN ID check (whether

Confidential
a PLMN ID is the RPLMN identity or an EPLMN identity of the UE) and the
CSG whitelist of the UE includes an entry comprising of the concerned PLMN
identity and the CSG ID broadcast by the target cell. The source eNB performs
PLMN ID check for the PLMNs reported by the UE and selects one if multiple
pass the PLMN ID check based on Handover Restriction List (HRL)
information. Finally the MME verifies the CSG membership according to the
received CSG ID, the selected PLMN ID and stored subscription CSG
information of the UE.
Basically, mobility from Macro eNB to a HeNB CSG/hybrid cell may take place
with the S1 handover procedure, because there is no X2 interface between Macro
eNB and HeNB. The procedure applies to any scenario where the CSG ID is
provided by the UE or provided by the source eNB.
Macro to HeNB Handover (Inbound mobility to CSG/Hybrid Cell)

The figure below describes Inbound Mobility to CSG/Hybrid Cell.

Confidential
1) The source eNB configures the UE with proximity indication control by setting
Report Proximity Configuration in RRC Connection Reconfiguration message.
2) The UE sends an entering proximity indication when it determines it may be
near a cell (based on autonomous search procedures) whose CSG ID is in the UE
CSG whitelist. The proximity indication includes the RAT and frequency of the
cell.
3) If a measurement configuration is not present for the concerned
frequency/RAT, the source eNB configures the UE with relevant measurement
configuration including measurement gaps as needed, so that the UE can perform
measurements on the reported RAT and frequency. The network may also use the
proximity indication to minimize the requesting of handover preparation
information of CSG/hybrid cells by avoiding requesting such information when
the UE is not in the geographical area where cells whose CSG IDs are in the UEs
CSG White-list are located.
4) The UE sends a measurement report including the PCI (for example, due to
triggered event A3).
5) The source eNB configures the UE to perform SI acquisition and reporting of a
particular PCI.
6) The UE performs SI acquisition using autonomous gaps, that is, the UE may
suspend reception and transmission with the source eNB within the limits defined
in [TS 36.133] to acquire the relevant system information from the target HeNB.
7) The UE sends a measurement report including E-CGI, TAI, CSG ID and
“member/non-member” indication. If the target cell is a shared CSG/hybrid cell,
the measurement report also includes the subset of the broadcast PLMN identities
that pass PLMN ID check and for which the CSG whitelist of the UE includes an
entry comprising the cell CSG ID and the respective PLMN identity.
8) The source eNB determine the target PLMN based on UE reported PLMN
information and the handover restriction list. Then the source eNB includes the
target E-CGI and the CSG ID in the Handover Required message sent to the
MME. If the target is a hybrid cell the Cell Access Mode of the target is included.
9) The MME performs UE access control to the CSG cell based on the CSG ID
received in the Handover Required message and the stored CSG subscription data
for the UE. If the access control procedure fails, the MME ends the handover
procedure by replying with the Handover Preparation Failure message. If the Cell
Access Mode is present, the MME determines the CSG Membership Status of the
UE handing over to the hybrid cell and includes it in the Handover Request
message.
10) to 11) The MME sends the Handover Request message to the target HeNB
including the target CSG ID received in the Handover Required message. If the
target is a hybrid cell, the CSG Membership Status is included in the Handover
Request message.
12) The target HeNB verifies that the CSG ID received in the Handover Request
message matches the CSG ID broadcast in the target cell and if such validation is
successful it allocates appropriate resources. UE prioritization may also be applied
if the CSG Membership Status indicates that the UE is a member.

Confidential
13) to 14) The target HeNB sends the Handover Request Acknowledge message to
the MME through the HeNB GW, if present.
15) The MME sends the Handover Command message to the source eNB.
16) The source eNB transmits the Handover Command (RRC Connection
Reconfiguration message including mobility control information) to the UE.
SYSTEM OPERATION
How to Activate
Set PCI range of the CSG or Hybrid cells per cell/FA by using following CLIs:
CHG-CSGPCI-IDLE (for CSG PCI) or CHG-HYBRIDPCI-INF (for Hybrid
PCI).
Key Parameters
parameters.
Parameter Descriptions of RTRV-CSGPCI-IDLE/CHG-CSGPCI-IDLE
FA_INDEX This parameter is the Frequency index. Maximum 8 FAs can be entered for
each cell.
CSG_PCI_RANGE_USED This parameter indicates whether to use the PCI range of a CSG cell.
• no_use: Does not use the PCI range.
• use: Uses the PCI range.
PCI_TYPE This parameter represents the PCI type of a CSG cell. This parameter
indicates whether to use a range of CSG PCIs or a single PCI.
• singlePci: Uses a single CSG PCI.
• rangedPci: Uses a range of CSG PCIs.
CSG_PCI_START This parameter is the PCI starting value of a CSG cell.
CSG_PCI_RANGE This parameter is the PCI range of a CSG cell. The range includes the starting
value.
FORCED_MODE This parameter indicates whether to change the configuration regardless of the
cell status.
• False: Set the value considering the cell status.
• True: Set the value without considering the cell status.
Parameter Descriptions of RTRV-HYBRIDPCI-INF/CHG-HYBRIDPCI-INF

Confidential
FA_INDEX This parameter is the Frequency index. Maximum 8 FAs can be entered for
each cell.
HYBRID_PCI_RANGE_USA This parameter indicates whether to use the PCI range of a hybrid cell.
GE • no_use: Does not use the PCI range of a hybrid cell.
• use: Uses the PCI range of a hybrid cell.
PCI_TYPE This parameter indicates the PCI type of a hybrid cell.
• singlePci: Uses a single PCI.
• rangedPci: Uses the PCI range.
HYBRID_PCI_START This parameter is the PCI starting value of a hybrid cell.
HYBRID_PCI_RANGE This parameter is the PCI range of a hybrid cell. The range includes the
starting value.
Sequentially becomes the range of n number of PCIs, which includes the
starting value, using the HYBRID_PCISTART value as the starting value.
If HYBRID_PCISTART = 1 and HYBRID_PCIRANGE = n4, the PCI range is 1
to 4.
If HYBRID_PCISTART = 1 and HYBRID_PCIRANGE = n12, the PCI range is 1
to 12.
If HYBRID_PCISTART = 20 and HYBRID_PCIRANGE = n16, the PCI range is
20 to 36.
Counters and KPIs

HO_S1_OUT_FEMTO InboundInterS1OutAtt The count of inbound inter S1 handover attempt from
Macro to Femto of SeNB
InboundInterS1OutPre The count of successful inter inbound S1 handover
pSucc preparation from Macro to Femto of SeNB
InboundInterS1OutSuc The count of successful inter inbound S1 handover
c execution from Macro to Femto of SeNB.
InboundInterS1OutPre The situation when either ECMB notifies reset (base
pFail_CpCcFail station failure or block restart) or preparation failure
occurs, due to ECCB block, during inbound inter S1
handover preparation from Macro to Femto.
InboundInterS1OutPre The situation when preparation fails due to S1AP
pFail_S1apCuFail specification cause occurrence during inbound inter
S1 handover preparation from Macro to Femto.
InboundInterS1OutPre The situation when preparation fails due to S1 SCTP
pFail_S1apLinkFail link failure during inbound inter S1 handover
preparation from Macro to Femto.
InboundInterS1OutPre The situation when preparation fails due to T/O (no
pFail_S1apRpTo reception) of S1AP relocprep during inbound inter S1
handover preparation from Macro to Femto.
InboundInterS1OutPre The situation when preparation fails due to S1AP
pFail_S1apSigFail signal reception during inbound inter S1 handover

Confidential

preparation from Macro to Femto.
InboundInterS1OutFail Statistics that occur due to Call Control T/O of
_CpCcTo protocol block (MAC, RLC, PDCP, and GTP) during
inbound inter S1 handover execution from Macro to
Femto.
InboundInterS1OutFail Statistics that occur when reset notification (base
_CpCcFail station failure or block restart) from ECMB or
release, due to ECCB block, during inbound inter S1
handover execution from Macro to Femto.
InboundInterS1OutFail Release statistics according to GTP block interior
_UpGtpFail failure during inbound inter S1 handover execution
from Macro to Femto.
InboundInterS1OutFail Release statistics according to MAC block interior
_UpMacFail failure during inbound inter S1 handover execution
InboundInterS1OutFail Release statistics according to PDCP block interior
_UpPdcpFail failure during inbound inter S1 handover execution
InboundInterS1OutFail Release statistics according to RLC block interior
_UpRlcFail failure during inbound inter S1 handover execution
from Macro to Femto
InboundInterS1OutFail Release statistics according to RRC signal reception
_RrcSigFail during inbound inter S1 handover execution from
Macro to Femto.
InboundInterS1OutFail Release statistics according to S1AP specification
_S1apCuFail cause occurrence during inbound inter S1 handover
execution from Macro to Femto.
InboundInterS1OutFail Release statistics according to S1 SCTP link failure
_S1apLinkFail during inbound inter S1 handover execution from
Macro to Femto.
InboundInterS1OutFail Release statistics according to S1AP relocoverall
_S1apRoTO T/O (no reception) during inbound inter S1 handover
InboundInterS1OutFail Release statistics according to S1AP signal
_S1apSigFail reception during inbound inter S1 handover
REFERENCE
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Radio
Resource Control (RRC) protocol specification"
Protocol (S1AP)

Confidential
LTE-SW1010, Intra-LTE Redirection

INTRODUCTION
Intra-LTE redirection is intra-LTE mobility functionality that moves UE to a
different LTE carrier from the serving carrier if handover is not possible. eNB
determines a target carrier based on the measurement report of UE. If inter-
frequency handover is not possible, the eNB performs inter-frequency redirection.
For intra-LTE redirection, the eNB releases RRC connection with the UE, and
designates a target carrier frequency in the LTE. The UE switches to the target
carrier frequency designated by the eNB, continuing to receive the data service.
BENEFIT
• An operator can provide connected mobility to its subscribers between LTE
carriers when inter-frequency handover is not supported.
• Improved UE experience in terms of mobility
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Redirection Procedures
Inter-frequency handover may not be possible because eNB receives no Handover
Event from UE until the signaling strength from the serving cell falls under a
certain threshold or the UE does not support inter-frequency handover. In these
cases, Redirection scheme is used to move the UE to a neighbor cell.
The eNB performs redirection when INTER_FREQ_REDIRECTION is set to
TRUE.
• When the eNB receives A2 measurement report (PurposeLteBlind) from the
UE, the eNB performs redirection.
• When the eNB receives Inter-frequency measurement (A3, A4 or A5) from the
UE, but the UE does not support inter-frequency handover (FGI #13), the eNB
performs redirection.
Confidential
The following figure shows the intra-LTE redirection procedure. During RRC
Connection Setup procedures, the eNB setups measurement configuration for the
UE such as A2, A3 and so on. When the UE supports inter-frequency
measurement (FGI #25), the eNB configures measurement gaps for neighbor
frequencies. For blind redirection, the eNB should configure A2
(PurposeLteBlind).
1) The eNB receives A2 measurement report (PurposeLteBlind) from the UE, or

the eNB receives Handover related measurement reports (A3, A4 or A5) from the
UE.
2) The eNB determines inter-frequency redirection when it receives A2
(PurposeLteBlind) Event, or when it receives Handover Events (A3, A4 or A5) but
the UE does not support inter-frequency handover (FGI #13). In case of A2
(PurposeLteBlind), for a redirected carrier the eNB selects one at random from the
neighbor carrier frequency list. In case of Handover Events (A3, A4 or A5), for a
redirected carrier the eNB selects the best carrier frequency based on the
measurement report from the UE.
3) The eNB transmits RRC Connection Release to the UE. The RRC Connection
Release message includes a redirected carrier frequency in IE
redirectedCarrierInfo to which the UE is switched.
4) The eNB transmits UE Context Release Request message to the MME for the
UE.
5) The MME sends UE Context Release Command message to the eNB for the
UE.
6) The eNB transmits UE Context Release Complete to the MME.
7) The UE is switched to the target carrier that is specified in RRC Connection
Release message by the eNB.
If the available redirected carrier frequency is different from the serving frequency

Confidential
in terms of duplex mode (FDD or TDD) and the UE does not support FDD-TDD
handover (FGI #30), the eNB will perform redirection procedures.
When the eNB receives A2 (PurposeLteBlind) Event but there is no redirected
carrier frequency available, then the eNB releases the RRC connection without
redirectedCarrierInfo.
The following table shows the FGI bit information (3GPP TS36.331).
Index of indicator Definition (description of the supported functionality, if indicator set to Notes
(bit number) one)
13 Inter-frequency handover (within FDD or TDD) Can only be set
to 1 if the UE
has set bit
number 25 to 1
25 Inter-frequency measurements and reporting in E-UTRA connected -
mode
The UE setting this bit to 1 and indicating support for FDD and
TDD frequency bands in the UE capability signaling implements
and is tested for FDD measurements while the UE is in TDD, and
for TDD measurements while the UE is in FDD.
30 Handover between FDD and TDD Can only be set
to 1 if the UE
has set bit
number 13 to 1
SYSTEM OPERATION
How to Activate
Preconditions
• There should be a configured EUTRAN neighbor network.
• Run CHG-EUTRA-FA to configure EUTRAN frequency information.
• Run CHG-NBR-EUTRAN to configure EUTRAN neighbor information.
• Run CHG-EUTRA-A2CNF to configure measurement Object information.
• Run CHG-INTWO-OPT to configure redirection options.
• Run CHG-EUTRA-A2CNF to deconfigure measurement Object information.

Confidential
• Run CHG-NBR-EUTRAN to deconfigure EUTRAN neighbor information.

• Run CHG-EUTRA-FA to deconfigure EUTRAN frequency information.
Key Parameters
parameters.
Parameter Descriptions of RTRV-INTWO-OPT/CHG-INTWO-OPT
cells supported by the system. It is determined by Carrier/Sector.
For example, if the maximum capacity system is 1 Carrier/3 Sector, up to
three cells are supported.
INTER_FREQ_REDIRECTION Whether to force redirection during the inter-frequency handover.
• False: Redirection is not executed during handover (normal).
• True: Redirection is executed regardless of condition (force-used).

example, if the maximum capacity system is 1 Carrier/3 Sector, up to
three cells are supported.
PURPOSE The purpose for using Event A2. It is currently used to activate
measurement gap and redirection.
A2_THRESHOLD_RSRP RSRP threshold used in the EUTRA measurement report triggering
condition for Event A2.
A2_THRESHOLD_RSRQ RSRQ threshold used in the EUTRA measurement report triggering
condition for Event A2.
HYSTERESIS Hysteresis applied to entry and leave condition of Event A2.
TIME_TO_TRIGGER timeToTrigger value for Event A2. The time-ToTrigger value is the period
that must be met for the UE to trigger a measurement report.
TRIGGER_QUANTITY Quantity (RSRP/RSRQ) used to calculate a triggering condition for Event
A2. Either RSRP or RSRQ is assigned.
REPORT_QUANTITY The quantity information included in a measurement report for Event A2.
It can be the same value as the trigger quantity or be set to include both
of the RSRP and RSRQ values.

Confidential
MAX_REPORT_CELL The maximum number of cells included in a measurement report for
Event A2.
REPORT_INTERVAL The reporting interval of a measurement report for Event A2.
REPORT_AMOUNT The number of measurement reports for Event A2.
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-SW1014, RLF Triggered Handover

INTRODUCTION
This feature minimizes rejection of the RRC Reestablishment (RRE) request when
the UE requests for RRE due to the Radio Link Failure (RLF). When the eNB that
has no context receives a request for RRE, the eNB can accept RRE of the UE by
securing the UE context through signaling with the serving eNB.
BENEFIT
If the eNB that has no UE context is requested for RRE due to the RLF, the eNB
can hand over the RRE request through signaling with the serving eNB.
DEPENDENCY
LTE-SW1005 (X2 Handover)
LIMITATION
This feature can be activated using X2 handover only.
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-SW1005(X2 Handover)
This feature can be activated only when the LTE-SW1005(X2 Handover) feature
is enabled.
If source eNB has s/w version as older than SLR600 with
PLDHandoverOptionInfoFunc::handoverByRLF set to On and target eNB has
SLR650 with Off, Hand-in success rate can be dropped because target eNB cannot
discriminate a RLF HO from a normal Hand-in.
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
The UE, which enters into an area where the wireless environment is not good,
requests for RRE. At this point, if not the existing serving eNB and target eNB
received RRE request from the UE, the RRE request is rejected since the target
eNB has no UE context information.
However, this feature is implemented and operator set ‘ON’ for

HANDOVER_BY_RLF(CHG-HO-OPT/RTRV-HO-OPT) to avoid the RRE
rejection as much as possible through handover signaling as follows.
This feature can operate only between Samsung eNBs in case of inter-vendor
option(CHG-HO-OPT/RTRV-HO-OPT) is disabled. If not, that is, inter-vendor
option is enabled, RLF triggered handover with Non-Samsung eNBs can be
possible. The Samsung eNB can identity whether each neighboring eNB is a
Samsung eNB from the exchange information during X2 setup procedure.
1) If the target eNB2 that receives the RRE request of UE cannot find a context of
the UE, the target eNB2 notifies the source eNB1 which the RLF has occurred.
The target eNB2 waits for a HO request from the source eNB1 during
X2_HO_REQ_WAIT_TIME(CHG-TIMER-INFO/RTRV-TIMER-INFO) timer

Confidential
and a response of UE’s RRE request is delayed during RLF triggered handover
preparation.
2) Source eNB1 receives the RLF indication message from target eNB2. The
eNB1 performs HO preparation by transmitting a handover request to the eNB2.
Even if the target cell is unknown neighbor cell, this HO preparation can be
possible if there has X2 connectivity with the target eNB2, and the UE’s handover
to the target cell is allowable based on the information about the UE specific
access restrictions and target cell’s broadcast PLMNs.
In this step, if performing the following procedure with the RLF UE, the source
eNB1 does not perform RLF triggered HO, that is, eNB1 does not send X2 HO
Request:
o During UE Context Release; or
o During Security Key modification triggered by MME request; or
o During CSFB procedure after receiving CSFB indicator from MME.
3) The eNB2 transmits a response to RRE of the UE by securing the context of the
UE and ensures that it is normally completed. (An eNB2 transmits RRE message
to UE when transmitting the Handover Acknowledge message to eNB1 in RLF
triggered Handover procedure.)
Vendor Identification
Samsung cognitive method makes use of X2AP IE extensions defined in 3GPP
specification for X2AP to achieve vendor identification. Global eNB-ID IE in X2
Setup Request and Response message is extended to include Samsung specific
information. Whenever a Samsung eNB receives X2 Setup Request or Response
from another Samsung eNB, the receiver can identify that the sender is a Samsung
eNB.
Vendor Identification
GlobalENB-ID::= SEQUENCE {
pLMN-Identity PLMN-Identity,
eNB-ID ENB-ID,
iE-Extensions ProtocolExtensionContainer { {GlobalENB-ID-ExtIEs} } OPTIONAL,
...
}
GlobalENB-ID-ExtIEs X2AP-PROTOCOL-EXTENSION::= {
...
}

Confidential
eNB1 eNB2 eNB3

(Samsung) (Samsung) (Other Vendor)
X2 Setup Request
IE_Extension = Samsung Specific Information
X2 Setup Response
eNB 2 is Samsung eNB eNB1 is Samsung eNB
X2 Setup Request
X2 Setup Response
eNB 2 is NOT Samsung eNB
Scenarios in the scope of RLF HO

Following detailed call flows of various re-establishment scenarios in the scope of
RLF HO.
RLF HO-Control Path
Figure below shows the control path for RLF HO message flow.

Confidential
eNB1 UE eNB2
RRC Connection
Radio Link Failure

RRC Connection Reestablishment Request
RLF Detection and Timer start
Checksupport for RLF HO at
eNB1
TInternal_Reetab_Time_To_Wait Start RLF HO Wait Timer
RLF Indication
Stop re-estab wait timer

Checksupport for RLF HO at eNB2 TRLF_HO_Wait
Start RLF HO for the UE
T301
HO Request
HO Req for RLF UE
Updates Security Keys and

TX2_HO_Preparation RRC Context to facilitate Re-
establishment
Handover Request Ack

RLF HO Preparation Success RRC Connection Reestablishment Complete
Update RLF HO Prep Stats
RRC Re-Config Not sent to UE
TX2_Reloc_Overall RRC Connection Reconfig Complete
RLF HO Data Path-Fig. 5
UE Context Release
RLF HO Complete
MRO counters are updated
(this is not in scope of RLF HO)
RLF HO-Data Path

Figure below shows the data forwarding in case of RLF HO from eNB1 (source
eNB) to eNB2 (target eNB). The data path handling is similar to a normal HO
procedure.

Confidential
eNB1 UE eNB2 MME SGW
RLF HO does not require eNB1

to Send Reconfig message with
HO Command to UE
eNB1 prepares for Data

forwarding
SN Status Transfer
Data forwarding
Packet Data
Packet Data
Path switch Request
User pane update Req
End Marker
End Marker
Packet Data
User pane update Rsp
Path switch Request Ack
UE Context Release
RLF HO Complete
HO to Wrong Cell Use case

Figure below shows another use case for RLF HO. In case of HO to wrong cell,
eNB2 shall facilitate UE to re-establish connection to eNB3 by providing RRC
AS-Context information to eNB3.

Confidential
eNB1 UE eNB2 eNB3
HO Decision
Target = eNB2
HO Preparation
RRC Connection Reconfiguration (HO Command)
RRC Connection Reconfig Complete
Radio Link Failure
RRC Connection Reestablishment Req
RLF Indication
RLF Trigger Start HO for the TRLF_HO_Wait

UE
HO Request
HO Report
HO Req for RLF UE
HO to Wrong Cell MRO
counter is updated (this is not TX2_HO_Preparation Updates Security Keys and
in scope of RLF HO) RRC Context to facilitate Re-
establishment
Handover Ack
RLF HO Preparation
Complete
RRC Connection Reestablishment Complete
Interworking with third party Source eNB

If inter-vendor option(CHG-HO-OPT/RTRV-HO-OPT) is disabled, eNB2 before
starting RLF HO preparation phase, checks if eNb1 supports RLF HO or not. If
eNb1 does not have RLF HO support, then eNB1 rejects UEs attempt for re-
establishment.

Confidential
eNB1 UE eNB2
RRC Connection
Radio Link Failure

RLF Indication
eNB1 was identified as non-

Samsung during X2 setup
procedure via vendor
identification (No support for
T301 RLF HO at eNB1)
Do not start RLF HO/RLF HO

WAIT timer Send Re-estab
Reject
RRC Connection Reestablishment Reject
UE actions upon leaving

RRC_CONNECTED
Interworking with third party Target eNB

If inter-vendor option(CHG-HO-OPT/RTRV-HO-OPT) is disabled, eNB1 on
reception of RLF Indication message, before starting RLF HO preparation phase,
checks if eNb2 supports RLF HO feature or not. If eNb2 does not support RLF
HO, then eNB1 does not initiate RLF HO feature.
eNB1 UE eNB2
RRC Connection
Radio Link Failure

RLF Indication
T301
eNB2 was identified as non-
Samsung during X2 setup
procedure via vendor
identification (No support for
RLF HO at eNB2)
Do not trigger RLF HO UE actions upon leaving

RRC_CONNECTED
RLF HO WAIT Timeout Scenario

If eNB1 receives RLF Indication procedure after the expiry of internal RLF wait
timer, then eNb1 will not have valid UE context for this UE. eNB1 shall not
trigger RLF HO. eNb2 guard timer for receiving X2AP HO request will expire
(RLF_HO_WAIT timer) and on expiry, eNB2 shall send RRC Connection
Reestablishment Reject message to UE.

Confidential
eNB1 UE eNB2
RRC Connection
Radio Link Failure
RLF Detection and Timer start RRC Connection Reestablishment Request
TInternal_Reestab_Time_to_wait
RLFtimer Expiry
TRLF_HO_Wait
Delete UE Context
X2AP RLF Indication
UE Context Not Found

RLF HO Wait Timer Expiry
RLF HO Not triggered
Reject Re-establishment
Call drop due to Re-
Attempt
establishment statistics is
updated
RLF HO Failure
Update Statistics
Action leaving
RRC_CONNECTED
Move to RRC_IDLE
RLF HO Preparation Failure

In case of RLF HO preparation failure (for example, security algorithm mismatch,
Re-establishment UE Identity verification failure, admission failure and so on.) at
target, X2AP Handover Preparation Failure message shall be used to indicate
failure.

Confidential
eNB1 UE eNB2
RRC Connection
Radio Link Failure
RLF Detection and Timer start RRC Connection Reestablishment Request

eNB1
TInternal_Reestab_Time_to_wait Start RLF HO Wait Timer
X2AP RLF Indication
Stop re-estab wait timer TRLF_HO_Wait

eNB2
HO Request
Security Algorithm Mismatch

Or
Admission Failure for at least
one n-GBR Bearer
Handover Preparation Failure
RLF HO Preparation Failure
RLF HO Execution Failure

In case of RLF HO execution failure (eg: RRC Connection Re-establishment
Complete message not received after sending Re-establishment message to UE,
Reconfiguration Complete message timer expiry and so on.) at target, RLF HO
execution failure statistics shall be updated. At source, X2 Reloc Overall timer will
expire and shall peg Call drop due to Radio Link failure along with RLF HO
failure.

Confidential
eNB1 UE eNB2
RRC Connection
Radio Link Failure

RLF Detection and Timer start
Checksupport for
RLF HO at eNB1
TInternal_Reetab_Time_To_Wait Start RLF HO Wait Timer
RLF Indication
Stop re-estab wait timer

Checksupport for RLF HO at TRLF_HO_Wait
eNB2
T301
HO Request
HO Req for RLF UE
Updates Security Keys and

TX2_HO_Preparation RRC Context to facilitate Re-
establishment
TX2_Reloc_Overall
TInternal_Reetab_Time_To_Wait
Timer Expiry
Timer Expiry Reestablishment Complete not
UE Context Release Not received-RLF HO Failure
received
Update RLF HO Failure
Update Call drop due to Radio
Link Failure

Confidential
RLF HO-After HO Timeout at Target
eNB1 UE eNB2
RRC Connection
UE Measurement Reports
triggers HO to eNB2
HO Request
Admission of UE and Bearers

TX2_HO_Preparation

TRRC_Reconfig_Wait
Radio Link Failure
TX2_Reloc_Overall
Timer Expiry
Delete UE Context
UpdateHO Fail Statistics
RRC Reestablishment Request
X2AP RLF Indication
X2AP RLF Indication Received

instead of UE Context Release,
Stop Timer
Update HO Failure statistics
TRLF_HO_WAIT
X2AP RLF Ind for UE prepared
for HO
Indicates Re-estab attempt
after Reconfig Complete Time
out, Continue with RLF HO
HO Request
RLF HO
Stop Timer
TX2_HO_Preparation Admit UE and Bearers
HO Ack
TX2_Reloc_Overall RRC Connection Reconfig Req
X2AP UE Context Release

Confidential
RLF HO-After HO Timeout at Source
eNB1 UE eNB2
RRC Connection
UE Measurement Reports
triggers HO to eNB2
HO Request
TX2_HO_Preparation Admission of UE and Bearers


TRRC_Reconfig_Wait
Radio Link Failure
TX2_Reloc_Overall
Timer Expiry Delete UE Context

UpdateHO Fail Statistics
RRC Reestablishment Request
Timer Expiry Delete UE Context

UpdateHO Failure Stats
X2AP RLF Indication

TRLF_HO_WAIT
UE Context Not Found
RLF HO Not Started
Timer Expires-RLF HO Failure
Scenarios Not in the Scope of RLF HO

Below are some scenarios which do not come under the scope of RLF HO.

Confidential
Radio link failure at eNB1 and re-establishment attempt back to eNB1 before
RLF timeout
eNB1 UE eNB2
RRC Connection
Radio Link Failure
RLF Detectio, Start

Internal_Reestab_Time_To_ T310 + Time
Wait for cell re-
selection
Stop Timer
Proceed with re-establishment

Procedure
If eNB1 receives RRC Connection Re-establishment request from a UE and if has

valid UE context (RLF WAIT timer has not expired), then proceeds with re-
establishment procedure. RLF HO feature is not involved in this scenario.

Confidential
Radio link failure at eNB1 and re-establishment attempt back to eNB1 after
RLF timeout.
eNB1 UE eNB2
RRC Connection
Radio Link Failure
RLF Detection
RLF Timer Start
Re-establishment
Timer Expiry
Delete UE Context and update

RLF counters
UE Context Not found

Send Re-estab Reject
Perform Actions leaving

RRC_CONNECTED Move to
RRC_IDLE
eNB1 on expiry of RLF WAIT timer, deletes the UE context. If RRC

Reestablishment request is received after deleting the UE context, the attempt shall
be rejected as no valid UE context is present. RLF HO is not involved in this
scenario.
Radio link failure after eNB1 prepares eNB2 for HO and re-establishment
attempt to eNB2
ON reception of RRC Connection Reestablishment Request from UE, eNB2 shall
proceed with Re-establishment procedure if HO preparation is completed for this
UE.

Confidential
eNB1 UE eNB2
RRC Connection
UE Meeasurement Reports
triggers HO to eNB2
HO Request
RRC Connection Reconfiguration Stop Reconfig Complete Wait

Timer
Radio Link Failure
RRC Connection Reconfig Req
X2AP UE Context Release

Confidential
Radio link failure after eNB1 prepares eNB2 for HO and re-establishment
attempt back to eNB1
eNB1 UE eNB2
RRC Connection
UE Meeasurement Reports
triggers HO to eNB2
HO Request
Radio Link Failure
RLF detection
RLF Timer start
TInternal_Reestab_Time_to_wait
Stop RLF WAIT timer

Continue with re-establishment
And Cancel HO
X2AP HO Cancel

Delete the UE context
RRC Connection Reconfig Req
In case UE attempts re-establishment towards eNb1 after eNB1 prepared eNB2 for
HO, eNB1 shall proceed with re-establishment procedure. eNB1 shall cancel
prepared HO by sending X2AP HO Cancel request message.
Configurations Not Allowed in Deployments

To ensure below scenarios are not occurring in field, configurations shall be done
considering the limitations mentioned.

Confidential
Source eNB disabled RLF HO support
eNB1 UE eNB2
RRC Connection
Radio Link Failure

RLF Indication
Expiry of
eNB1 does not support TRLF_HO_Wait
RLF triggered HO
Update Call drop due to RLF T301

Statistics
Timer expires for RLF triggered HO

Send RRC Conenction Reestablishment
Reject

RRC_CONNECTED
This figure shows a negative scenario where operator has disabled RLF HO in
eNB1. eNB2 on reception of re-establishment request message from UE, sends
X2AP RLF indication and starts RLF HO preparation phase (since eNB1 supports
RLF HO). Since eNB1 has disabled RLF HO, eNB2 has to wait for the internal
RLF HO timer to expire to send RRC Connection Re-establishment Reject
message. This delays the rejection of re-establishment attempt and may delay the
subsequent access attempt of the UE. This scenario is not expected in deployment
and support for RLF HO shall be enabled in all Samsung eNBs.

Confidential
Target eNB disabled RLF HO support
eNB1 UE eNB2
RRC Connection
Radio Link Failure

RLF Indication
T301
Start RLF Trigger
HO for the UE RRC Connection Reestablishment Reject
HO Request
eNB2 prepares for HO without knowledge

that Source is preparing for RLF HO
HO Ack
eNB1 considers RLF HO is in

progress
TX2_RELOC_ RRC_CONNECTED T RRC_
Reconfig_Wait
OVERALL
UE Contextgets deleted
UE Context gets deleted on Timer expiry
on Timer expiry-RLF HO
Failure
This figure shows scenario which is not expected in deployment, where operator
has disabled RLF HO in eNB2. On reception of X2AP RLF Indication message,
eNB1 moves to RLF HO preparation phase and sends X2AP HO Request with the
necessary information for facilitating re-establishment at eNB2, if eNB2 supports
RLF HO feature. eNB2 would have already rejected the re-establishment attempt
as eNB2 has disabled support for RLF HO. eNB2 will treat HO Request as a
normal HO and would wait for UE to send RRC Connection Reconfiguration
Complete message. UE would move to RRC IDLE state and perform actions
leaving RRC_CONNECTED and would not send Reconfiguration Complete
message. eNB1 and eNB2 HO timer expiry cleans up the UE context created at
both eNBs. UE might again camp on to eNB2 after cell search. This scenario is not
expected in deployment and hence RLFHO shall be enabled in all Samsung eNBs
eNB operations in case of race conditions between RLF triggered handover and other
call procedures
When the source eNB1 receives X2 RLF Indication from neighboring eNB2 if
eNB1 is performing other call procedure, for example, waiting for RRC
Connection Reconfiguration Complete from the RLF UE, the eNB1 decides
whether to trigger RLF triggered handover according to the following conditions
and will perform the described operations per each case.

Confidential
Ongoing call procedure RLF triggered Source eNB1 operations

HO triggering
A) during UE Context Release No A-1) eNB1 ignores the RLF Indication and continues
the ongoing procedure.
B) during Security Key modification No • B-1) eNB1 ends the ongoing procedure.
triggered by MME request • B-2) eNB1 should respond the failure of the ongoing
procedure to MME with an appropriate cause.
• B-3) eNB1 responds the failure of RLF triggered HO
to the eNB2, if possible.
• B-4) eNB1 starts RLF wait timer. If it is expired, the
UE context is released.
C) during CSFB processing after No • C-1) eNB1 ends the ongoing procedure.
receiving CSFB indicator from MME • C-2) eNB1 responds the failure of RLF triggered HO
to the eNB2, if possible
• C-3) eNB1 starts RLF wait timer. If it is expired, the
UE context is released.
D) during RRC Connection Yes • D-1) eNB1 ends the ongoing procedure.
Reconfiguration for the purpose • D-2) eNB1 triggers RLF triggered HO to the eNB2, if
described as below: possible.
• UL resource reallocation • D-3) If RLF triggered HO cannot be possible, eNB1
• UE measurement configuration starts wait timer. If it is expired, the UE context is
• Scell reconfiguration released.
• TTI bundling
E) during E-RAB Yes • E-1) eNB1 ends the ongoing procedure.
Setup/Modify/Release • E-2) eNB1 should respond the failure of the ongoing
procedure to MME with an appropriate cause.
• E-3) eNB1 triggers RLF triggered HO to the eNB2, if
possible.
• E-4) If RLF triggered HO cannot be possible, eNB1
starts wait timer. If it is expired, the UE context is
released.
For case D) and E), RLF triggered Ho can be possible only in case the eNB2 is a
Samsung eNB. This is also applicable to in case inter-vendor option is enabled.
Counters for RLF triggered handover

RLF triggered handover (RLF HO) related counters are collected with 'Time
critical handover' of HO cause. So it can be distinguished from the HO counters
for UE measurement based handover.
The following counters are provided as HO counters for RLF triggered handover:
• Number of RLF HO preparation attempts
• Number of successful RLF HO preparation attempts
• Number of failed RLF HO preparation attempts with failure cause
• Number of successful RLF HOs
• Number of failed RLF HOs with failure cause

Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-HO-OPT and set HANDOVER_BY_RLF to ON to use this
function.
• Run CHG-HO-OPT and set HANDOVER_BY_RLF to OFF to use this
function.
Key Parameters
parameters.
Parameter Descriptions of CHG-HO-OPT/RTRV-HO-OPT
HANDOVER_BY_RLF Whether to use Inter-eNB RRE function
• Off: not use Inter-eNB RRE
• On: use Inter-eNB RRE
parameters.
Parameter Descriptions of CHG-TIMER-INFO/RTRV-TIMER-INFO
X2_HO_REQ_WAIT_TIM This parameter is the waiting time for target-eNB to receive X2 Handover Request
E from Source eNB during RLF Triggered Handover.
• Timer X2_HO_REQ_WAIT_TIME:
SLR 6.0 P0 Value: 40 ms (Controllable)

Confidential
Start Stop
in Target eNB: X2 RLF in Target eNB: Handover request from SeNB
Indication sent
Counters and KPIs

RLF triggered handover is pegged as the following X2 Handover counters with
index HoCause = Time Critical Handover.
X2 Handover Out InterX2OutAtt Attempt count for X2 handover from SeNB.
InterX2OutPrepSucc Success count for X2 handover preparation from SeNB.
InterX2OutSucc Success count for X2 handover execution from SeNB.
InterX2OutPrepFail_C Preparation fails due to reset notification (eNB failure or
P_CC_FAIL block restart) from ECMB or by ECCB block during the
InterX2OutPrepFail_S Preparation fails due to S1 SCTP link failure during the
1AP_LINK_FAIL inter X2 handover preparation.
InterX2OutPrepFail_S Preparation fails due to receiving S1AP signaling during
1AP_SIG_FAIL the inter X2 handover preparation.
InterX2OutPrepFail_X Preparation fails due to X2AP specification cause during
2AP_CU_FAIL the inter X2 handover preparation.
InterX2OutPrepFail_X Preparation fails due to X2 SCTP link failure during the
2AP_LINK_FAIL inter X2 handover preparation.
InterX2OutPrepFail_X Preparation fails due to X2AP relocprep timeout (not
2AP_RP_TO received) during the inter X2 handover preparation.
InterX2OutPrepFail_X Preparation fails due to receiving X2AP signaling during
2AP_SIG_FAIL the inter X2 handover preparation.
InterX2OutFail_CP_C A call is released due to call control timeout in the
C_TO protocol blocks (MAC, RLC, PDCP, GTP) during the
InterX2OutFail_CP_C A call is released due to reset notification (eNB failure or
C_FAIL block restart) from ECMB or by the ECCB block during
InterX2OutFail_UP_G A call is released due to the failure in the GTP block
TP_FAIL during the inter X2 handover execution.
InterX2OutFail_UP_M A call is released due to the internal failure in the MAC
AC_FAIL block during the inter X2 handover execution.
InterX2OutFail_UP_P A call is released due to the internal failure in the PDCP
DCP_FAIL block during the inter X2 handover execution.
InterX2OutFail_UP_R A call is released due to the internal failure in the RLC
LC_FAIL block during the inter X2 handover execution.
InterX2OutFail_RRC_ A call is released due to receiving RRC signaling during
SIG_FAIL the inter X2 handover execution.
InterX2OutFail_S1AP_ A call is released due to the S1AP specification cause
CU_FAIL during the inter X2 handover execution.
InterX2OutFail_S1AP_ A call is released due to the S1 SCTP link failure during
LINK_FAIL the inter X2 handover execution.
InterX2OutFail_S1AP_ A call is released due to receiving S1AP signaling

Confidential

SIG_FAIL during the inter X2 handover execution.
InterX2OutFail_X2AP_ A call is released due to the X2AP specification cause
CU_FAIL during the inter X2 handover execution.
InterX2OutFail_X2AP_ A call is released due to the X2 SCTP link failure during
LINK_FAIL the inter X2 handover execution.
InterX2OutFail_X2AP_ A call is released due to X2AP RelocOverall timeout
RO_TO (not received) during the inter X2 handover execution.
InterX2OutFail_X2AP_ A call is released due to receiving the X2AP signaling
SIG_FAIL during the inter X2 handover execution.
InterX2OutCnt X2 Handover Out collection count
InterX2OutCid tcID of which collection is requested
X2 Handover In InterX2InAtt The number of attempts for X2 handover in TeNB
InterX2InPrepSucc The number of successes for X2 handover preparation
in TeNB
InterX2InSucc The number of successes for X2 handover execution in
TeNB
InterX2InPrepFail_CP Preparation fails due to call control timeout in the
_CC_TO protocol blocks (MAC, RLC, PDCP, GTP) during the
InterX2InPrepFail_CP Preparation fails due to reset notification (eNB failure or
_CC_FAIL block restart) from ECMB or by ECCB block during the
InterX2InPrepFail_UP Preparation fails due to internal failure in the GTP block
_GTP_FAIL during the inter X2 handover preparation.
InterX2InPrepFail_UP Preparation fails due to internal failure in the MAC block
_MAC_FAIL during the inter X2 handover preparation.
InterX2InPrepFail_UP Preparation fails due to internal failure in the PDCP
_PDCP_FAIL block during the inter X2 handover preparation.
InterX2InPrepFail_UP Preparation fails due to internal failure in the RLC block
_RLC_FAIL during the inter X2 handover preparation.
InterX2InPrepFail_CP Preparation fails due to insufficient backhaul-based eNB
_BH_CAC_FAIL resources during the inter X2 handover preparation.
InterX2InPrepFail_CP Preparation fails due to insufficient capacity-based eNB
_CAPA_CAC_FAIL resources during the inter X2 handover preparation.
InterX2InPrepFail_CP Preparation fails due to insufficient QoS-based eNB
_QOS_CAC_FAIL resources during the inter X2 handover preparation.
InterX2InPrepFail_S1 Preparation fails due to S1 SCTP link failure during the
AP_LINK_FAIL inter X2 handover preparation.
InterX2InPrepFail_S1 Preparation fails due to receiving S1AP signaling during
AP_SIG_FAIL the inter X2 handover preparation.
InterX2InPrepFail_X2 Preparation fails due to X2AP specification cause during
AP_CU_FAIL the inter X2 handover preparation.
InterX2InPrepFail_X2 Preparation fails due to X2 SCTP link failure during the
AP_LINK_FAIL inter X2 handover preparation.
InterX2InPrepFail_X2 Preparation fails due to receiving X2AP signaling during
AP_SIG_FAIL the inter X2 handover preparation.
InterX2InFail_CP_CC A call is released due to call control timeout in the
_TO protocol blocks (MAC, RLC, PDCP, GTP) during the

Confidential

InterX2InFail_CP_CC A call is released due to reset notification (eNB failure or
_FAIL block restart) from ECMB or by the ECCB block during
InterX2InFail_UP_GT A call is released due to the failure in the GTP block
P_FAIL during the inter X2 handover execution.
InterX2InFail_UP_MA A call is released due to the internal failure in the MAC
C_FAIL block during the inter X2 handover execution.
InterX2InFail_UP_PD A call is released due to the internal failure in the PDCP
CP_FAIL block during the inter X2 handover execution.
InterX2InFail_UP_RL A call is released due to the internal failure in the RLC
C_FAIL block during the inter X2 handover execution.
InterX2InFail_RRC_H A call is released due to HO command timeout (not
C_TO received) during the inter X2 handover execution.
InterX2InFail_RRC_SI A call is released due to receiving RRC signaling during
G_FAIL the inter X2 handover execution.
InterX2InFail_S1AP_C A call is released due to the S1AP specification cause
U_FAIL during the inter X2 handover execution.
InterX2InFail_S1AP_L A call is released due to the S1 SCTP link failure during
INK_FAIL the inter X2 handover execution.
InterX2InFail_S1AP_P A call is released due to S1AP path switch timeout (not
ATH_TO received) during the inter X2 handover execution.
InterX2InFail_S1AP_S A call is released due to receiving S1AP signaling
IG_FAIL during the inter X2 handover execution.
InterX2InFail_X2AP_C A call is released due to the X2AP specification cause
U_FAIL during the inter X2 handover execution.
InterX2InFail_X2AP_L A call is released due to the X2 SCTP link failure during
INK_FAIL the inter X2 handover execution.
InterX2InFail_X2AP_S A call is released due to receiving the X2AP signaling
IG_FAIL during the inter X2 handover execution.
InterX2InFail_X2AP_S A call is released due to X2AP signaling timeout (not
IG_TO received) during the inter X2 handover execution.
REFERENCE
[3] 3GPP TS36.423 E-UTRA and E-UTRAN; X2 Application Protocol (X2AP)

Confidential
LTE-SW1015, Frequency-Priority-based HO
INTRODUCTION
General coverage-based inter-frequency handover would not be triggered if the
serving cell quality is good, so that the user stays in the serving cell. However, in
multi-carrier environment, different handover scheme regardless of serving cell
quality should be needed according to operator usage purpose per carrier
frequency.
For example, an operator deploys small cells on the different frequency from
macro cells in hot spot area for offloading macro traffic. This offloading is
possible by forcing handover of users close to the small cells.
For these requirements, Samsung supports Frequency priority based handover (FP-
based HO, FPHO). FPHO is a forced handover based on pre-assigned per-
frequency priority. eNB determines higher priority frequencies based on the per-
frequency priority. Higher priority frequency means a frequency which priority is
higher than serving frequency priority. FPHO makes that users can detect there are
neighboring cells of higher priority frequencies at any place within serving cell,
and eNB performs FPHO when it decides that handover to a higher priority
frequency is possible from user report.
The operator can configure per-frequency priority, and also can configure FPHO
specific handover parameters per frequency for differentiating handover triggering
criteria from coverage-based inter-frequency handover.
BENEFIT
• The operator can differentiate handover criteria according to frequency
priority.
• The operator can steer or distribute their subscribers based on the usage
purpose per frequency band, and then they can maximize frequency resource
usages in multi-carrier environment.
DEPENDENCY
• Required Network Elements
MME
• Related Radio Technology
E-UTRAN (LTE)
• Interface & Protocols
RRC, S1, X2
o LTE-SW1003 (Intra-eNB Handover)
o LTE-SW1004 (S1 Handover)
Confidential
o LTE-SW1005 (X2 Handover)

o LTE-SW1007 (Inter-Frequency Handover)
o LTE-SW1010 (Intra-LTE Redirection)
o LTE-SW1016 (Forced Handover Control)
o LTE-SW1401 (Handover between LTE-FDD and TD-LTE)
LIMITATION
Frequency priority based handover is not possible if a user is selected for the
following features:
• SPID UEs based on LTE-SW2014 SPID (Subscriber Profile ID for
RAT/Frequency Priority) based handover
• MBMS interest UEs based FR40 of LTE-SV0513 MBMS service continuity
• SCell activated UEs, and Intra-eNB hand-in UEs based on LTE-SW1017
Inter-frequency handover for CA
SYSTEM IMPACT
capabilities.
Interdependent Feature: Inter-Frequency Handover
Frequency-priority based Handover feature enables inter-frequency handover
toward higher priority frequency layers regardless of serving cell quality.
In the cell edge, inter-frequency handover toward any priority frequency layers is
possible as well as the conventional inter-frequency handover.
FEATURE DESCRIPTION
For FPHO, when call setup or hand-in of the UE which supports the higher priority
frequencies, the eNB orders inter-frequency measurement for the higher priority
frequencies. Then the UE can perform inter-frequency measurement for the higher
priority frequencies regardless of serving cell quality and it will report to the eNB
if handover event is occurred. When receiving UE measurement report for
handover to the higher priority frequencies, the eNB will directly trigger FPHO for
the UE to move to the higher priority frequency.
Initial measurement configuration

In case FPHO is enabled, initial measurement configuration is performed as
following procedure for a UE when call setup, hand-in or change of QCI mobility
group by E-RAB setup/modify/release.
(*) Operator can enable/disable FPHO by using parameter FPHO_SUPPORT
(CHG-FPHO-CTRL)

Confidential
1) The eNB extracts the UE candidate carriers considering UE supported bands,

serving cell configuration for intra-LTE and inter-RAT mobility based on operator
policy.
2) The eNB adds UE measurement configuration for intra-frequency mobility:
serving frequency with HO event (A3/A4/A5) for intra-frequency mobility.
3) The eNB checks FPHO option (parameter: FPHO_SUPPORT of CHG-FPHO-
CTRL) and performs next step based on FPHO option.

Confidential
• If FPHO option ≠ noUse (FPHO_SUPPORT=True), go to step 4).

• Else, go to step 7).
4) The eNB checks the possibility for FPHO based on UE capabilities.
• If there are higher priority frequencies in UE supported bands and UE supports
inter-frequency measurement, that is, FGI #25 = 1, go to step 5).
5) The eNB adds UE measurement configuration for FPHO, higher priority
frequencies with HO event (A4/A5) per higher priority frequencies for FPHO and
measurement gap if needed. In case of Hand-in UE, this step is performed at
handover completion.
(*) Operator can set frequency priority and HO event type per E-UTRA frequency
by using parameter FP_HO_PRIORITY and HO_EVENT_TYPE, respectively
(CHG-EUTRA-FPHOPRIOR).
The related HO parameters (for example, A4/A5 threshold, hysteresis, time to
trigger, and so on.) can be set by using parameters of CHG-EUTRA-
A4CNF/CHG-EUTRA-A4CNFQ/CHG-EUTRA-A5CNF/CHG-EUTRA-A5CNFQ.
If FPHO UE selection ratio (parameter: FPHO_UE_SELECT_RATIO of CHG-
FPHO-CTRL) is configured, the eNB should determine whether to select this UE
as FPHO UE based on the FPHO UE selection ratio. UE measurement for FPHO is
configured only for the selected FPHO UE.
5-0) If FPHO UE selection ratio is configured, to determine whether to select this
UE as FPHO UE or not, the eNB generates a random value (0-1). Then the eNB
compares the value to the FPHO UE selection ratio.
If the value is smaller than the FPHO selection ratio, this UE is selected as FPHO
UE. Otherwise, the eNB handles this UE as well as FPHO incapable UE, and go to
step 7).
5-1) The eNB selects the configurable higher priority frequencies to be
configured.
5-2) The eNB configures reportConfig for HO event (A4/A5) per higher priority
frequencies for FPHO.
5-3) The eNB configures measGap if needed.
5-4) The eNB configures s-Measure based on s-Measure usage option (parameter:
S_MEASURE_OPTION of CHG-FPHO-CTRL). If this option is not applied
(S_MEASURE_OPTION=FALSE), eNB configures that the value of s-Measure is
set to '0' to UE.
6) For FPHO capable UE, the eNB adds UE measurement configuration for inter-
frequency mobility to All frequencies: Event A2 for inter-frequency mobility.
7) For FPHO incapable UE, the eNB adds UE measurement configuration for
inter-frequency mobility: Event A2 for inter-frequency mobility.
8) The eNB adds UE measurement configuration for inter-RAT mobility: Event
A2 for inter-RAT mobility.

Confidential
9) The eNB sends RRC Connection Reconfiguration message to the UE, including
UE measurement configuration of step 2), 5), 6) or 7). In case of Hand-in UE, UE
measurement configuration of step 5 is not included.
10) In case of Hand-in UE and when receiving RRC Connection Reconfiguration
Complete message from UE (at Handover completion), the eNB starts Forced HO
Restriction timer (parameter: FORCED_HO_RESTRICTION_TIME of CHG-
TIMER-INF). Then when the Forced HO Restriction timer is expired, the eNB
checks whether to get UE measurement configuration for FPHO.
• If needed, go to step 11).
• Else, this procedure ends.
11) The eNB sends RRC Connection Reconfiguration message to the UE,
including UE measurement configuration for FPHO: higher priority frequencies
with HO event (A4/A5)per higher priority frequencies for FPHO and measurement
gap if needed (For details refer to step 5)).
FPHO triggering and FPHO procedure

If FPHO specific MR is received from UE, the eNB decides whether FPHO
triggering and performs the following procedure.

Confidential
1) The eNB decides FPHO target cell according to the following conditions:
• The best cell in measuredCells of the FPHO specific MR.
• HO to the best cell is allowed.
• The best cell is not Forbidden TA based on the UE Handover Restriction List.
• FPHO to the best cell can be allowed if Excessive FPHO restriction option is
activated (the parameter FPHO_RESTRICTION_TIME of CHG-FPHO-CTRL
is not set to ‘0’). The eNB checks the number of FPHO requests to the best
cell during FPHO restriction time (parameter: FPHO_RESTRICTION_TIME
of CHG-FPHO-CTRL). If the number is larger than the maximum allowable
number of FPHO request (Excessive FPHO threshold (parameter:
EXCESSIVE_FPHO_REQ of CHG-FPHO-CTRL)), FPHO to the best cell is
restricted. Go to step 7).
2) The eNB checks Available capacity threshold for FPHO for the target
frequency.
(*) Operator can set the value of Available capacity threshold for FPHO per E-
UTRA frequency by using parameter CAPA_THRESHOLD (EUTRA-
FPHOPRIOR).
Confidential
• If Available capacity threshold for FPHO ≠ 0, go to step 3).

3) The eNB checks the available capacity of FPHO target cell.
• If there is no available capacity of FPHO target cell, go to step 4).
• Else if there is available capacity of FPHO target cell >= Available capacity
threshold for FPHO, go to step 4).
4) The eNB checks UE HO capability.
• If HO capable to the target frequency, go to step 5).
5) The eNB triggers FPHO to target cell.
If Excessive FPHO restriction option is activated (the parameter
FPHO_RESTRICTION_TIME of CHG-FPHO-CTRL is not set to ‘0’), eNB
increments the number of FPHO requests to the FPHO target cell during FPHO
restriction time by 1.
6) The eNB performs MR based redirection to the frequency of FPHO specific
MR.
7) The eNB discards the FPHO specific MR.
Release of FPHO measurement configuration

If FPHO measConfig release option=Use (the parameter
MEAS_DURATION_OPTION of CHG-FPHO-CTRL is set to ‘False’), eNB start
Timer for release of FPHO measConfig (parameter:
MEAS_REL_TIMER_FOR_FORCED_HO of CHG-TIMER-INF) at FPHO
specific measurement configuration. When the timer expires, eNB releases FPHO
specific measurement configuration.
Handling for FPHO specific MR collision

When receiving FPHO specific MR during processing for previous MR for
mobility, the eNB checks the frequency priority of previous MR and FPHO
specific MR. If the last FPHO specific MR frequency priority is higher than that of
the previous MR, the eNB performs FPHO based the last FPHO specific MR.
• Discard the previous MR.
• Cancel the HO if already HO triggered due to the previous MR.
• This action is not applied for the following features MR: MLB, eICIC, CA and
PCC selection.
Reducing load situation due to FPHO

In certain environments where FPHO events can occur intensively in a short

Confidential
period, FPHO can make increasing handover signaling load temporarily.

To avoid this improper situation due to FPHO in the corresponding area, following
two schemes can be used:
• Limit the number of UEs which is directed FPHO specific measurement
configuration, based on FPHO UE selection ratio, and/or
(*) Operator can set the 'FPHO UE selection ratio' by using parameter
FPHO_UE_SELECT_RATIO (CHG-FPHO-CTRL).
• Restrict Excessive FPHO request to neighbors during FPHO restriction time.
(*) Operator can set the maximum allowable number of FPHO request
(Excessive FPHO threshold) and FPHO restriction time by using parameter
EXCESSIVE_FPHO_REQ and FPHO_RESTRICTION_TIME, respectively
(CHG-FPHO-CTRL). If the FPHO_RESTRICTION_TIME is set to ‘0’, then
this option is disabled.
Counters for FPHO

eNB collects the results of FPHO as normal HO counter families (for example,
HO_INTRA, HO_X2_OUT, HO_S1_OUT,
HO_INTER_FREQ_OUT_WITH_GAP,
HO_INTER_FREQ_OUT_WITHOUT_GAP, and so on.).
SYSTEM OPERATION
How to Activate
Preconditions
• Basic EUTRA FA Configuration should be configured correctly by CHG-
EUTRA-FA.
• Run CHG-FPHO-CTRL and set FPHO_SUPPORT to True.
• Run CHG-EUTRA-A4CNF [and CHG-EUTRA-A4CNFQ] and set
ACTIVE_STATE of ci_A4PurposeInterFrequencyFPHO purpose to Active.
• Run CHG-EUTRA-A5CNF [and CHG-EUTRA-A5CNFQ] and set
ACTIVE_STATE of ci_A5PurposeInterFrequencyFPHO purpose to Active.
• Run CHG-EUTRA-FPHOPRIOR and assign a priority at FP_HO_PRIORITY
for each Frequency. If operator does not assign a priority, all Frequencies have
the same priority and Frequency Priority Based Handover does not happen.
Confidential
Run CHG-FPHO-CTRL and set FPHO_SUPPORT to False.
Key Parameters
This section describes the key parameters for activation/deactivation of the feature.
parameters.
Parameter Descriptions of CHG-FPHO-CTRL/RTRV-FPHO-CTRL
FPHO_SUPPORT It shows whether Frequency Priority Based Handover is supported.
• False (0): Frequency Priority Based Handover is not supported.
• True (1): Frequency Priority Based Handover is supported.

frequency. If this is set to Inactive, the Event A4 is not configured. This change
is applied to the UE from next RRC signaling procedure (for example, Attach or
Idle to Active). To avoid overload, a new setting is not updated to the current
active UEs.
• Active: Event A4 is used. If HO of the target frequency is not needed in the
site, this is inactive.

active UEs.

active UEs.

Confidential

active UEs.
parameters.
Parameter Descriptions of CHG-FPHO-CTRL/RTRV-FPHO-CTRL
S_MEASURE_OPTION It shows whether s-Measure is applied in case of the UE Measurement for
Frequency Priority Based Handover (s-Measure is not applied in case of UE
Measurement when s-Measure is set to 0.).
• False (0): s-Measure is not applied.
• True (1): s-Measure is applied.
MEAS_DURATION_OPTIO It shows whether Measurement Configuration for Frequency Priority Based
N Handover is maintained.
• False (0): In case FPHO is not triggered within the set time, Measurement
Configuration for Frequency Priority Based Handover is released.
• True (1): Measurement Configuration for Frequency Priority Based Handover
is maintained continuously.
FPHO_UE_SELECT_RATI It shows the UE selection ratio to adjust UE measurement configuration for
O Frequency Priority Based Handover. (Unit: %)
FPHO_RESTRICTION_TIM It shows the period to restrict the number of the Frequency Priority Based
E Handover request to a target cell. If it is set as "0", eNB does not perform the
restriction of the Frequency Priority Based Handover request to a target cell.
(Unit: Seconds)
EXCESSIVE_FPHO_REQ It shows the maximum number of Frequency Priority Based Handover to a
target cell in the period (PLDFpHoControlInfo::fphoRestrictionTime). If
fphoRestrictionTime is set as "0", it does not work.
Parameter Descriptions of CHG-EUTRA-FPHOPRIOR/RTRV-EUTRA-

FPHOPRIOR
FP_HO_PRIORITY Priority of each frequency to select the target frequency for Frequency Priority
Based Handover. The frequency with a priority higher than the Serving
Frequency is selected as the target frequency. In the range of the priority, 0 is

Confidential
the lowest and 7 is the highest priority.
CAPA_THRESHOLD The threshold of Available Capability for each Target frequency to restrict
Frequency Priority Based Handover. In case Available Capability of the
Frequency Priority Based Handover Target Cell is lower than the threshold,
Frequency Priority Based Handover to the cell is not performed. If it is set to 0,
Frequency Priority Based Handover is performed regardless of Available
Capability of the Target Cell.
HO_EVENT_TYPE Select the Handover Event Type to trigger Frequency Priority Based Handover.
• ci_FpHoEventA4 (0): Trigger inter-frequency handover by Event Type A4.
• ci_FpHoEventA5 (1): Trigger inter-frequency handover by Event Type A5.

A4_THRESHOLD_RSRP This parameter is the RSRP threshold used for the Event A4 that occurs when
a neighbor becomes better than the threshold. The serving cell performs intra-
eNB HO and inter-frequency HO if the frequency is configured to use the Event
A4 triggering. The UE could measure either the Reference Signal Received
Power (RSRP) or the Reference Signal Received Quality (RSRQ) and
TRIGGER_QUANTITY indicates it will operate based on RSRP or RSRQ. This
change is applied to the UE from the next RRC signaling procedure (for
example, Attach or Idle to Active). To avoid overload, a new setting is not
updated to the current active UEs. The higher the parameter is, the later the HO
is performed and it can impact HO success rate, The lower the parameter is,
the earlier the HO is performed and it can cause ping pong. This value needs to
be optimized up to site environment.
A4_THRESHOLD_RSRQ This parameter is the RSRQ threshold used for the Event A4 that occurs when
TRIGGER_QUANTITY indicates it will operate based on the RSRP or RSRQ.
This change is applied to the UE from the next RRC signaling procedure (for
HYSTERESIS This parameter is the hysteresis value of Event A4 during ReportConfigEutra
configuration. This information is used to determine the entering condition
[(Measurement Result-Hysteresis) Threshold] and leaving condition
[(Measurement Result + Hysteresis) Thresh]. The hysteresis uses the unit
into hysteresis * 0.5 dB. This change is applied to the UE from next RRC
signaling procedure (for example, Attach or Idle to Active). To avoid overload, a
new setting is not updated to the current active UEs.
TIME_TO_TRIGGER This parameter is the timeToTrigger value for the Event A4. The timeToTrigger
is the time which should be satisfied for the UE to trigger the measurement
report. The event A4 occurs only when a specific threshold meet a threshold
during the period of TIME_TO_TRIGGER and the TIME_TO_TRIGGER can be
set to a value 0-5120 ms as defined in the TS.36.331. This change is applied to
the UE from next RRC signaling procedure (for example, Attach or Idle to
Active). To avoid overload, a new setting is not updated to the current active
UEs.

Confidential
threshold according to TRIGGER_QUANTITY. If the TRIGGER_QUANTITY is
RSRP, the A4_THRESHOLD_RSRP is used. If it is RSRQ, the
A4_THRESHOLD_RSRQ is used. This change is applied to the UE from next
RRC signaling procedure (for example, Attach or Idle to Active). To avoid
overload, a new setting is not updated to the current active UEs.
• followA2event: It indicates that the value of TriggerQuantity corresponds with
the value of A2 Event triggerQuantity.
measurement results. This change is applied to the UE from next RRC
• both: A UE transmits both RSRP/RSRQ if the REPORT_QUANTITY is set to
both for the measurement result when transmitting Event A4.
neighbor cells that can be included in the measurement report for Event A4.
When transmitting the measurement report for Event A4, a UE can add the
measurement report of EUTRA neighbor cell as many as
MAX_REPORT_CELL if there is the measurement result of EUTRA neighbor
cell. This change is applied to the UE from next RRC signaling procedure (for
updated to the current active UEs.
REPORT_INTERVAL This parameter is the interval of measurement reports for the Event A4. This
information is for setting the Measurement Report transmission interval when a
device is reporting measurement results. The REPORT_INTERVAL must
transmit a measurement report at the interval of REPORT_INTERVAL as many
times as specified in the REPORT_AMOUNT if it meets the event A4 condition.
This applies only when the REPORT_AMOUNT is larger than 1. The
ReportConfigEutra configuration. It is for setting the number of measurement
reports (Event A4) for a device reporting measurement results. The
REPORT_AMOUNT is the number of measurement report transmit when the
Event A4 condition is met. If the REPORT_AMOUNT is larger than 1, the
measurement report is transmitted as many times as REPORT_AMOUNT
according to the interval specified in REPORT_INTERVAL. The
REPORT_AMOUNT is set to 1-infinity according to the TS36.331. If it is set to
infinity, a measurement report is transmitted at the interval of
REPORT_INTERVAL until the A4 leaving condition is met. This change is
applied to the UE from next RRC signaling procedure (for example, Attach or
active UEs.

Confidential
A4_THRESHOLD_RSRP This parameter is the RSRP threshold used for the Event A4 that occurs when
TRIGGER_QUANTITY indicates it will operate based on RSRP or RSRQ. This
change is applied to the UE from the next RRC signaling procedure (for
A4_THRESHOLD_RSRQ This parameter is the RSRQ threshold used for the Event A4 that occurs when
TRIGGER_QUANTITY indicates it will operate based on the RSRP or RSRQ.
This change is applied to the UE from the next RRC signaling procedure (for
UEs.

Confidential
active UEs.

ReportConfigEutra configuration. It range is 0-97. This value used when the
TRIGGER_QUANTITY is set to RSRP.
ReportConfigEutra configuration, it is set to 0-97. This value used when the
ReportConfigEutra configuration, it is set to 0-34. This value is used when the
TRIGGER_QUANTITY is set to RSRQ.

Confidential
UEs.

Confidential
active UEs.

ReportConfigEutra configuration. It range is 0-97. This value used when the
ReportConfigEutra configuration, it is set to 0-97. This value used when the
UEs.

Confidential
active UEs.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.300: 'Evolved Universal Terrestrial Radio Access (E-UTRA) and
description; Stage 2'. (10.1.2.1.2, 10.1.2.3.1)

Confidential

Radio Resource Control (RRC); Protocol specification (5.3.1, 5.3.5.8)

Confidential
LTE-SW1017, Inter-Frequency Handover for CA

INTRODUCTION
A certain type of CA-capable UE cannot support CA at the current serving cell
since the UE does not have any corresponding band combination for CA, which
has the serving frequency as a PCell in the operator’s LTE network. (For example,
rel. 12 TDD-FDD CA UEs does not support a TDD PCell.) On the other hand, in
the case that the current cells CA function can be turned off according to the
operator’s policy, all CA-capable UEs connected to the cell cannot use CA-
capability. In these cases, if some UEs support another CA band combination
available in another frequency of the operator’s network, directing these CA-
capable UEs to the corresponding frequencies helps them get higher data rates.
BENEFIT
Benefits for end user
• A CA-capable UE can have more chances of getting higher data rate.
DEPENDENCY
Prerequisite Features: LTE-SW5500, CA Call Control
LIMITATION
An operator must configure the target frequencies, each of which supports CA
PCell, by using the parameter TARGET_FREQUENCY_HO_FOR_CA (CHG-
EUTRA-FA/CHG-EUTRA-FA).
SYSTEM IMPACT
capabilities.
None
None
Coverage
This feature uses the dedicated A4 event parameter setting. The threshold (that is,
a4ThresholdRSRP/RSRQ) can affect the area where HOs triggered by this feature
occur.
Interfaces
None

Confidential
FEATURE DESCRIPTION
Figure below depicts an example to which this feature can be applied. If the UE
supports TDD-FDD CA with a FDD PCell and its data traffic is heavy, moving the
UE to the FDD frequency f1 helps the UE get higher data rate. However, it is
unnecessary to move a TDD-FDD CA UE with a light traffic to the FDD
frequency.
The procedure for inter-frequency HO for CA is as follows:

1 When a UE is newly connected to a cell, the eNB checks the UE’s CA
capability such as its supported band combinations and the corresponding
maximum aggregated bandwidths.
2 If the eNB cannot configure a SCell to the CA-capable UE, it monitors the
amount of the downlink data traffic for the UE.
3 If the amount of the data buffer for the UE exceeds a configured threshold
(DATA_TRAFFIC_THRESHOLD (RTRV-CACELL-INFO/CHG-CACELL-

Confidential
INFO)), then eNB makes a candidate frequency set for measurements based
on both the UE’s CA capability and the target frequency list configured by
operator. (The list of target frequencies indicates the group of frequencies
whose TARGET_FREQUENCY_HO_FOR_CA (RTRV-EUTRA-FA/CHG-
EUTRA-FA) is configured as TRUE).
4 eNB configures A4 event (with PURPOSE =
INTER_FRQUENCY_FOR_CA) measurement to the UE. Then, eNB starts
the timer for the allowed measurement duration
(MEAS_REL_TIMER_FOR_FORCED_HO (RTRV-TIMER-INF/CHG-
TIMER-INF)).
5 If the eNB receives an A4 measurement report before the timer expires, it
makes a decision on inter-frequency HO for CA. The eNB does not perform
HO if the reported target cell corresponds to the latest frequency in the UE
History Information in the case of a hand-in UE or the target cell in the same
eNB does not support any supported band combination of the UE. Otherwise,
the eNB performs inter-frequency HO.
6 If the eNB cannot receive any A4 measurement report until the timer expires,
it removes the corresponding measurement configuration from the UE.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CACELL-INFO and set INTER_FREQ_HO_FOR_CA_ENABLE
to 1.
• Run CHG-CACELL-INFO and set INTER_FREQ_HO_FOR_CA_ENABLE
to 0.
Key Parameters
parameters.

Confidential

INTER_FREQ_HO_FOR_CA_E This parameter indicates whether to support Inter-Frequency Handover for
NABLE CA.
• 0: This feature is Inactive.
• 1: This feature is Active.
parameters.
DATA_TRAFFIC_THRESHOLD This parameter is data traffic threshold for Inter Frequency HO for CA. It
means number of packet in Tx Buffer.

TARGET_FREQUENCY_HO_F This parameter indicates whether this carrier is a target frequency for the
OR_CA feature 'Inter-frequency HO for CA'.

PURPOSE This parameter is data traffic threshold for Inter Frequency HO for CA. It
means number of packet in Tx Buffer.
This parameter is the purpose of using Event A4.
• IntraLteHandover: handover is executed
• ANR_Specific:the ANR operation is executed
• CA: SCELL is configured
• Sendback : the Sendback operation is executed
• InterFrequencyLb : the Active Load Balancing operation is executed
• ArpHandover : Enable inter frequency handover function for UEs that
have a specific ARP
• OnDemandHandover : Enable the forced handover triggering by operator
• InterFrequencySPID : inter-frequency handover is executed for specific
SPID with handover mobility option.
• InterFrequencyFPHO : For Frequency Priority Based Handover.
• InterFrequencyForCa : inter-frequency handover for non-CA UE to CA
available Cell.

Confidential
Counters and KPIs

with this feature.
REFERENCE
specification

Confidential

[4] 3GPP 36.413: E-UTRAN; S1 application protocol (S1AP)
[6] Feature Detail Description (LTE-SW5500) CA Call Control, Samsung
Electronics

Confidential
LTE-SW1019, Uplink Quality Based Inter-

frequency HO
INTRODUCTION
General coverage-based handover considers downlink signal quality of serving cell
and target cell from UE perspective, so the eNB uses UE measurement reports for
starting inter-frequency measurement by UE and triggering handover.
If a UE is located in the area that downlink quality is not bad, however, uplink
quality is bad, the conventional handover scheme is not enough and additional
handover scheme by considering uplink signal quality level for UEs is required.
UL quality based inter-frequency handover considers a UE’s uplink signal quality.
For this, the eNB monitors a UE’s UL quality (SINR) level during connection by
eNB internal measurement and if a UE’s UL quality becomes worse, then the eNB
commands inter-frequency measurement to the UE. When the UE reports the
measured results, the eNB decides a handover target cell based on the received
measurement report and triggers handover if possible.
BENEFIT
Better network quality can be achieved by reducing the number of call drop due to
bad uplink quality.
DEPENDENCY
• HW dependency: Smallcell products do not support this feature.
LIMITATION
The following operations for UL quality based HO by target eNB can be possible
only in case of intra-eNB handover within Samsung eNB or X2 handover between
Samsung eNBs.
• UL SINR estimation in target cell
• HO admission based on the estimated UL SINR
SYSTEM IMPACT
capabilities.
Related Feature: LTE-SW1007 Inter-frequency Handover
The LTE-SW1007 feature is designed for general coverage-based inter-frequency

Confidential
handover and its triggering event is based on UE measurement, that is, downlink
signal quality. According to eNB command and control, a UE monitors serving
cell’s downlink signal quality and if it becomes worse, then UE can start inter-
frequency measurement.
Otherwise UL quality based inter-frequency handover feature considers the uplink
signal quality of UE and the internal measurement of eNB is used as triggering
event of inter-frequency measurement.
These two features operate independently and there is no priority between these
features.
In the area if there is a mismatch of uplink coverage area and downlink coverage
area, UL quality based inter-frequency handover feature can help decrease call
drop ratio and increase uplink cell throughput by performing handover to other
frequency area for users suffering bad uplink quality.
Coverage
None
Interfaces
X2 interface:
New IE (Samsung proprietary) is added in the X2 Handover Request message to
transfer the required information for target eNB to estimate the hand-in UE’s UL
quality level.
FEATURE DESCRIPTION
UL quality based inter-frequency handover (UL based HO, ULHO) considers the
uplink signal quality of UE, that is, UL SINR. For this, the eNB monitors the UL
SINR of UE during connection by eNB internal measurement and performs the
control functions of inter-frequency handover/measurement according to the
monitoring results.
If the eNB supports ULHO function and it is enabled, it monitors each connected
UL quality (SINR) level of UE since when connection setup (for example, call
setup, hand-in, or connection reestablishment) is completed. If the UL quality of
UE becomes worse, the eNB commands inter-frequency measurement to the UE
and when the UE reports the measured results, the eNB decides a handover target
cell based on the received measurement report and triggers handover if possible.
For ULHO, the following parameters should be configured properly.
• Feature on/off
• Criteria on UL quality monitoring/indication
o UL SINR threshold to detect Bad_UL
o UL SINR threshold to detect Good_UL
o Minimum required time for UL quality (Bad/Good) indication
o UL quality check count: Maximum number of consecutive Bad_UL or
Good_UL for UL quality indication
Confidential
o Per-QCI priority using in case per-QCI UL SINR threshold is set

• HO event type for ULHO (A3/A4/A5) and parameters of the selected event
• Admission criteria for ULHO in target cell
o HO offset for ULHO (ULHO_offset)
o HO margin for ULHO (ULHO_margin)
All the above parameters are operator configurable (details are described in the
System Operations section.)
UL Quality Monitoring of a UE and Measurement Configuration for ULHO

In case ULHO is enabled, the eNB starts/restarts UL quality (SINR) monitoring
for a UE when call setup, RRC connection re-establishment, or change of QCI
mobility group by E-RAB setup/modify/release.
For hand-in cases, the eNB starts UL quality (SINR) monitoring after expiry of
Forced HO Restriction Timer to minimize too frequent handover such as UL
quality based handover right after DL quality based handover.
The eNB checks UL SINR for a UE whenever receiving UL signal/traffic from the
UE, and compare the results to thresholds to detect Bad_UL or Good_UL.
If Bad_UL is detected consecutively the times of UL quality check count and the
Bad_UL condition continues over the time duration of 'minimum required time for
UL quality indication', that is, UL_A2 condition is satisfied, then eNB commands
starting inter-frequency measurement for ULHO to the UE.
If during UE measurement for ULHO, Good_UL is detected consecutively the
times of UL quality check count and the Bad_UL condition continues over the
time duration of 'minimum required time for UL quality indication', that is, UL_A1
condition is satisfied, then eNB commands stopping inter-frequency measurement
for ULHO to the UE.
The eNB supports Timer based deactivation of UL HO specific inter-frequency
measurement to reduce bad impact to throughput by measurement gap. It starts the
pre-defined timer when it configures UL HO specific inter-frequency measurement
to a UE if the timer value is set. If there are no MRs till the timer is expired, the
eNB releases UL HO specific inter-frequency measurement configuration. After
then, UL HO specific inter-frequency measurement configuration for the UE can
be possible only when UL_A2 condition is satisfied again.

Confidential
ULHO Triggering and ULHO Procedure

If ULHO specific MR is received from UE, the eNB decides whether ULHO triggering and performs
the following procedure.
1 The source eNB decides ULHO target cell according to the following
condition. If the source eNB cannot decide ULHO target cell in this step,
goes to step 5.
o HO is allowed
o Not included in Forbidden TAs in UE’s Handover Restriction List
o Not a HO preparation failed cell
o The best cell in measuredCells of the ULHO specific MR, which are
satisfied all the above criteria
2 The source eNB makes the UE’s uplink quality information to be transferred
to target cell/eNB. Uplink quality information includes UE measured RSRP
result for target cell and the normalized UL SINR for source cell.
o The normalized UL SINR for source cell =Ssource – NIsource
o Ssource = min( Pmax,source, Max_UE_Tx_Power )– Path_Losssource
o Path_Losssource = RS_Tx_Powersource – Measured RSRPsource
3 The source eNB checks UE’s HO capability. If this handover capable to the
target frequency, goes to step 4. Otherwise, goes to step 5.

Confidential
4 The source eNB triggers ULHO to target cell and performs HO

preparation/execution procedure according to target cell/eNB’s response. If
failed, goes to step 5.
o If target cell/eNB receives HO request including uplink quality
information, it decides whether ULHO is appropriate based on admission
criteria for ULHO.
o If the ULHO is not appropriate based on the criteria, the HO preparation
will be failed.
5 The source eNB discards the ULHO specific MR.
Admission criteria for ULHO

Target cell/eNB calculates the normalized UL SINR for target cell if ULHO
function is supported/enabled and a HO request for ULHO is received (the
equation is the same as that for source cell, refer to description of step 2 in the
above flow).
Then target cell/eNB should decide that it will admit or reject the ULHO request
based on Admission criteria for ULHO.
The admission criteria for ULHO are as follows. The following both criteria are
satisfied, then the ULHO request will be admitted by target cell/eNB.
• [criteria 1] UL SINR for target cell (normalized) ³ UL SINR for source cell
(received) + ULHO_offset for target cell
• [criteria 2] UL SINR for target cell (normalized) ³ UL SINR threshold to
detect 'Bad_UL' for target cell + ULHO_margin for target cell
Counters for ULHO

The eNB can collect the ULHO related counters and it is separated from the HO
counters for UE measurement based handover.
The following counters are provided as HO counters for ULHO:
• The number of ULHO preparation attempts (outgoing/incoming)
• The number of successful ULHO preparation attempts (outgoing/incoming)
• The number of successful ULHOs(outgoing/incoming)
• The number of failed ULHO preparation attempts due to UL quality based
admission criteria
SYSTEM OPERATION
How to Activate

Confidential
Preconditions
EUTRA-FA.
• Run CHG-ULQUALITYHO-CTRL and set
UL_QUALITY_BASED_HOSUPPORT to True.
• Run CHG-EUTRA-FA and CHG-EUTRA-FAQCI, and set
UL_BASED_HO_EVENT_TYPE properly.
ACTIVE_STATE to ci_A3PurposeUlQualityBasedHO.
• Run CHG-ULQUALITYHO-CTRL and set
UL_QUALITY_BASED_HOSUPPORT to False.
Key Parameters
parameters.
Parameter Descriptions of CHG-ULQUALITYHO-CTRL/RTRV-ULQUALITYHO-
CTRL
UL_QUALITY_BASED_HO_SU This parameter represents whether Uplink Quality based Inter-Frequency
PPORT Handover function is enabled or not.
• False(0): Uplink Quality based Inter-Frequency Handover function is
disabled
• True(1): Uplink Quality based Inter-Frequency Handover function is
enabled

change will be applied to the UE from next RRC signaling procedure (e.g.

Confidential
Attach or Idle to Active). To avoid overload, a new setting will not be





Confidential

parameters.
Parameter Descriptions of CHG-MACULQUALITY-INFO/RTRV-
MACULQUALITY-INFO
UL_QUALITY_CHECK_SINR_T Configuration for UL SINR threshold to check Bad UL quality
H_BAD
UL_QUALITY_CHECK_SINR_T Configuration for UL SINR threshold to check Good UL quality
H_GOOD
UL_QUALITY_CHECK_COUNT Configuration for counter threshold to check UL quality
_TH
UL_QUALITY_MIN_HOLD_TIM Minimum required time for UL quality check
E
PRIORITY The priority of QCI. The lower index the higher priority.
Parameter Descriptions of CHG-ULQUALITYHO-CTRL/RTRV-

ULQUALITYHO-CTRL
UL_SINR_HO_OFFSET This parameter is used to determine whether to accept the handover
request in the target cell. If the below condition is not satisfied, the
handover request will be rejected.
- SINRtarget >= SINRsource + UL_SINR_HO_OFFSET
UL_SINR_HO_MARGIN This parameter is used to determine whether to accept the handover
request in the target cell. It is defined to prevent the ping-pong handover
due to Uplink Quality based Inter-Frequency Handover function. If the
below condition is not satisfied, the handover request will be rejected.)
- SINRtarget >= UL_QUALITY_CHECK_SINR_TH_BADtarget +
UL_SINR_HO_MARGIN

Confidential
UL_BASED_HO_EVENT_TYPE This parameter represents the Handover Event Type to trigger Uplink
Quality Based Inter-frequency Handover.
• ci_HoEventA3(0): Uplink Quality Based Inter-frequency Handover is
triggered by Event Type A3.

UL_BASED_HO_EVENT_TYPE This parameter represents the Handover Event Type to trigger Uplink
Quality Based Inter-frequency Handover.
• ci_HoEventA3(0) : Uplink Quality Based Inter-frequency Handover is

(e.g. Attach or Idle to Active). To avoid overload, a new setting will not be
updated to the current active UEs. The higher the parameter is, the less
HO is performed and it can impact HO success rate, The lower the

Confidential
active UEs.
procedure (e.g. Attach or Idle to Active). To avoid overload, a new setting
will not be updated to the current active UEs.
active UEs.

Confidential
signaling procedure (e.g. attach or idle to active). To avoid overload, a new
active UEs. The higher the parameter is, the less HO is performed and it
can impact HO success rate. The lower the parameter is, the more frequent

(e.g. Attach or Idle to Active). To avoid overload, a new setting will not be
updated to the current active UEs. The higher the parameter is, the less
HO is performed and it can impact HO success rate, The lower the

Confidential
active UEs.
active UEs.

Confidential
active UEs. The higher the parameter is, the less HO is performed and it
can impact HO success rate. The lower the parameter is, the more frequent

from the next RRC signaling procedure (e.g. Attach or Idle to Active). To
avoid overload, a new setting will not be updated to the current active UEs.
The higher the parameter is, the later the HO is performed and it can
impact HO success rate, The lower the parameter is, the earlier the HO is
performed and it can cause ping pong. This value needs to be optimized up
to site environment.

Confidential
UE from the next RRC signaling procedure (e.g. Attach or Idle to Active).
To avoid overload, a new setting will not be updated to the current active
UEs. The higher the parameter is, the later the HO is performed and it can
active UEs.
active UEs.

Confidential

from the next RRC signaling procedure (e.g. Attach or Idle to Active). To
avoid overload, a new setting will not be updated to the current active UEs.
The higher the parameter is, the later the HO is performed and it can
Reference Signal Received Power (RSRP) or the Reference Signal
UE from the next RRC signaling procedure (e.g. Attach or Idle to Active).
To avoid overload, a new setting will not be updated to the current active
UEs. The higher the parameter is, the later the HO is performed and it can

Confidential
active UEs.
active UEs.

Confidential
results. The REPORT_AMOUNT is the number of measurement reports

active UEs.
active UEs.

Confidential


Confidential
active UEs.
active UEs.

Confidential
Counters and KPIs

Outgoing UL Quality based UlHoOutAtt The number of Outgoing Uplink Quality based
Handover Inter-frequency Handover Attempt
UlHoOutPrepSucc The number of Outgoing Uplink Quality based
Inter-frequency Handover Preparation Success
UlHoOutSucc The number of Outgoing Uplink Quality based
Inter-frequency Handover Execution Success

Incoming UL Quality based UlHoInAtt The number of Incoming Uplink Quality based
Handover Inter-frequency Handover Attempt
UlHoInPrepSucc The number of Incoming Uplink Quality based
Inter-frequency Handover Preparation Success
UlHoInSucc The number of Incoming Uplink Quality based
Inter-frequency Handover Execution Success
UlHoInPrepFail_UlQuality The number of Incoming Uplink Quality based
Cac Inter-frequency Handover Preparation Failure
due to the unsatisfied uplink quality of the
target cell.

Confidential
REFERENCE

Confidential
LTE-SW1101, Idle Mobility to CDMA Network

(HRPD/1xRTT)
INTRODUCTION
When LTE and CDMA (HRPD or 1xRTT) networks interwork, an idle state UE
can move to CDMA (HRPD or 1xRTT) network. To support this idle mobility,
eNB broadcasts information needed to move CDMA (HRPD or 1xRTT) network
in SIB 8 message. SIB 8 includes the neighboring carrier frequencies, the related
thresholds for cell resection towards CDMA cells and CDMA neighboring cell
related information, that is, HRPD and 1xRTT neighbor cell list. SIB 8 also
includes the HRPD system information and 1xRTT system information, and
contains CDMA timing information, as well as information controlling the pre-
registration for PS handover to HRPD or CS Fallback to CDMA2000 1x.
BENEFIT
• Operator can provide idle mobility to its subscribers to CDMA network.
• Users in idle state can move to CDMA network.
DEPENDENCY
E-UTRAN (LTE), CDMA (2G)
• Others
CDMA capable device
LIMITATION
None
SYSTEM IMPACT
capabilities.
Cell reselection is supported by following features:
• Idle Mobility Support, Idle Mobility to CDMA Network (HRPD/1xRTT), Idle
Mobility to UTRAN, and Idle Mobility to GERAN.
• Idle Mobility Support is used for cell reselection between LTE cells. This
feature can be configured optionally for interworking with CDMA Network
(1X/eHRPD).

Confidential
FEATURE DESCRIPTION
The eNB uses SIB8 to transmit the idle state UE go to the CDMA network.
Required parameter is as below:
• CDMA system time
The absolute time in the current cell is informed and the UE uses this absolute
time knowledge to derive the CDMA2000 Physical cell identity, expressed as
PNOffset, of neighbor CDMA2000 cells.
SystemTimeInfoCDMA2000::= SEQUENCE {
cdma-EUTRA-Synchronisation BOOLEAN,
cdma-SystemTime CHOICE {
synchronousSystemTime BIT STRING (SIZE (39)),
asynchronousSystemTime BIT STRING (SIZE (49))
}
}
• Search window size

This is the CDMA2000 parameter to be used to assist in searching for the
neighbor pilots.
• HRPD cell reselection parameters
o HRPD band class list
o Cell reselection priority per HRPD band class
o Cell reselection threshold per HRPD band class
o HRPD neighboring cell list
o Cell reselection timer for HRPD cell reselection
o Cell reselection timer for speed dependent HRPD cell reselection
• 1xRTT cell reselection parameters
o 1xRTT band class list
o Cell reselection priority per 1xRTT band class
o Cell reselection threshold per 1xRTT band class
o 1xRTT neighboring cell list
o Cell reselection timer for 1xRTT cell reselection
o Cell reselection timer for speed dependant 1xRTT cell reselection
SIB8 In addition to CDMA cell reselection parameters sent with the following
parameters related to the operation of the pre-registration to HRPD and CSFB to
1xRTT.
SIB8 has CDMA cell reselection parameter, and the operating parameter of pre-
registration to HRPD and CSFB to 1xRTT.
• HRPD pre-registration parameter
o Indication whether pre-registration is allowed
o Pre-registration information

Confidential
The following figure shows the idle mode mobility to eHRPD procedure.
1) The UE is attached to E-UTRAN network and stay in ECM_IDLE state. The

UE has a dormant HRPD session in the target HRPD network, either through the
pre-registration procedure or previous HRPD attachment.
2) The UE is in idle mode. Based on some trigger, the idle UE decides to perform
cell re-selection to the HRPD system.
3) The UE follows 3GPP2 procedures in 3GPP2 C.S0087-0: "E-UTRAN-HRPD
and CDMA2000 1x Connectivity and Interworking: Air Interface Aspects" to
inform the HRPD access network the UE has performed an inter-technology idle
mode mobility event and is now tuned to HRPD.
4) The HRPD access indicates to the HSGW that the UE has moved to HRPD.
4a) The HSGW fetches the PDN GW identity for all the active PDN connections
from the 3GPP AAA Server.
5) and 6) The HSGW exchanges a PMIP BU/BA with the PDN GW. The UE
address information in PMIP BA returns the IP Address assigned to the UE. In this
message, the Charging ID is also carried for charging correlation purposes. At this
point the user plane is switched in the PDN GW towards the HRPD access
network through the HSGW. Multiple PDN connections to the same APN can be
supported using PDN connection identities in the same way as it is specified for
S2a procedures.
6a) The PDN GW executes a PCEF-Initiated IP CAN Session Modification
Procedure with the PCRF as specified in TS 23.203 [19] to obtain any new QoS
policy and charging rules for all the active sessions as a result of the handover
Confidential
procedure. Since steps 6 and 6a are both triggered by the Proxy Binding Update in
step 5), steps 6) and 6a) may occur in parallel.
For multiple PDN connections, steps 5)-6) and 6a)-6b) are performed for each
PDN connection.
7) The HS-GW acknowledges the HRPD access network.
8) At any time after step 6), the P-GW initiates the PDN GW Initiated PDN
Disconnection procedure, so that any resources are released in the EPS serving
nodes that were serving the UE in E-UTRAN access before the idle-mode mobility
to HRPD took place.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-SIB-INF to set sib8Period to the correct value.
• Run CHG-SIB-INF to set sib8Period to NOT_USE.
Key Parameters
parameters.
Parameter Descriptions of RTRV-SIB-INF/CHG-SIB-INF
sib8Period This parameter is the broadcast interval for SIB 8.
• not_used: Does not broadcast SIB8.
parameters.

Confidential
Parameter Descriptions of RTRV-CDMA-CNF/CHG-CDMA-CNF

cdmaEutraSynchronisation Synchronization status between the EUTRA and CDMA2000 systems.
searchWindowSize The size of the search window in the eNB.
csfbSupportDualRxUe Dual Rx CSFB support status by the eNB.
• False: the eNB does not support Dual RX UE.
• True: the eNB supports Dual RX UE.
csfbSupportDualRxTxUe Dual RxTx CSFB support status by the eNB.
• False: the eNB does not support Dual RX UE.
• True: the eNB supports Dual RX UE.
Parameter Descriptions of RTRV-C1XRTT-BCLS/CHG-C1XRTT-BCLS

bcIndex Index of information on the CDMA 1XRTT band class.
status Validity status of the CDMA2000 1XRTT band class.
• EQUIP: Valid.
bandClass bandclass of CDMA2000 1XRTT band class DB.
cellReselectionPriority cellReselectionPriority of CDMA2000 1XRTT band class DB.
threshXHigh threshXHigh of CDMA2000 1XRTT band class DB.
threshXLow ThreshXLow of CDMA20001XRTT band class DB.
Parameter Descriptions of RTRV-C1XRTT-FREQ/CHG-C1XRTT-FREQ

cellNum The cell number to be changed.
carrierIndex CDMA2000 1xRTT carrier index. Up to 8 carriers can be assigned per
cell.
status Whether the CDMA2000 1xRTT carrier is valid.
• EQUIP: Valid.
bandClass Band class of the cell.
arfcn ARFCN of the cell.
offsetFreq Offset frequency of the cell.
Parameter Descriptions of RTRV-C1XRTT-OVL/CHG-C1XRTT-OVL

cellNum The cell number to be changed or retrieved.
tReselection1XRTT 1XRTT reselection timer of the cell in the eNB.
tReselectionSfUsage1XRTT Whether the scaling factor is used for 1XRTT reselection of the cell in the
eNB.
• CI_no_use: Scaling factor is not used.
• CI_use: Scaling factor is used.

Confidential
tReselectionSfMedium1XRTT The medium timer value of the scaling factor used for 1XRTT reselection
of the cell in the eNB.
• ci_oDot25: 0.25 is used for the medium timer.
• ci_1Dot0: 1.0 is used for the medium timer.
tReselectionSfHigh1XRTT The high timer value of the scaling factor used for 1XRTT reselection of
the cell in the eNB.
• ci_oDot25: 0.25 is used for the high timer.
• ci_1Dot0: 1.0 is used for the high timer.
usageLongCodeState1XRTT Whether the LongCodeState1XRTT is used for CDMA2000 handover.
• CI_no_use: LongCodeState1XRTT is not used.
• CI_use: LongCodeState1XRTT is used.
Parameter Descriptions of RTRV-C1XRTT-PREG/CHG-C1XRTT-PREG

csfbPreRegUsage Whether to use the CSFB preRegistration information that is sent down to
the SIB8.
• CI_no_use: CSFB preRegistration information is not used.
• CI_use: CSFB preRegistration information is used.
sid The SID value used along with oneXRTT-NetworkID when the UE is re-
registered on the CDMA 1xRTT network.
nid The NID value used along with oneXRTT-SystemID when the UE is re-
registered on the CDMA 1xRTT network.
multipleSID Whether to use multipleSID (CDMA2000 1xRTT Multiple SID storage
indicator).
• False: multipleSID is not used.
• True: multipleSID is used.
multipleNID Whether to use multipleNID (1xRTT Multiple NID storage indicator).
• False: multipleNID is not used.
• True: multipleNID is used.
homeReg Whether to use homeReg (1xRTT Home registration indicator).
• False: homeReg is not used.
• True: homeReg is used.
foreignSIDReg Whether to use foreignSIDReg (1xRTT SID roamer registration indicator).
• False: foreignSIDReg is not used.
• True: foreignSIDReg is used.
foreignNIDReg Whether to use foreignNIDReg (1xRTT NID roamer registration indicator).
• False: foreignNIDReg is not used.
• True: foreignNIDReg is used.
parameterReg Whether to use the parameterReg (1xRTT Parameter-change registration
indicator).
• False: parameterReg is not used.

Confidential
• True: parameterReg is used.
powerUpReg Whether to use the powerUpReg (1xRTT Power-up registration indicator).
• False: powerUpReg is not used
• True: powerUpReg is used.
registrationPeriod The RegistrationPeriod value used by csfb-PreRegistration. It can be
changed by the operator.
registrationZone The RegistrationZone value used by csfb-PreRegistration. It can be
changed by the operator.
totalZone The totalZone value used during csfb-PreRegistration. It can be changed
by the operator.
zoneTimer The zoneTimer value used during csfb-PreRegistration. It can be changed
by the operator.
powerDownRegInd Whether to use the powerDownRegInd (1xRTT Power-Down registration
indicator).
• False: powerDownRegInd is not used.
• True: powerDownRegInd is used.
Parameter Descriptions of RTRV-HRPD-BCLS/CHG-HRPD-BCLS

bcIndex Index of information on the CDMA2000 HRPD band class in the eNB.
status The validity of each tuple information.
• EQUIP: Valid.
bandClass Band class of the cell in the eNB.
cellReselectionPriority Reselection priority of the cell in the eNB. The range is 0-7, where 0
indicates low, and 7 high in priority.
threshXHigh ThreshXHigh of CDMA2000 HRPD band class DB.
threshXLow ThreshXLow of CDMA2000 HRPD band class DB.
Parameter Descriptions of RTRV-HRPD-FREQ/CHG-HRPD-FREQ

carrierIndex CDMA2000 HRPD carrier index. Up to 8 carriers can be assigned per
cell.
status Whether the CDMA2000 HRPD carrier is valid.
• EQUIP: Valid.
bandClass Band class of the cell.
arfcn ARFCN of the cell.
offsetFreq Offset frequency of the cell.

Confidential
Parameter Descriptions of RTRV-HRPD-OVL/CHG-HRPD-OVL

colorCode ColorCode information of the cell overlaid with the CDMA2000 HRPD
system in the eNB.
It can be changed by the operator.
bsmId BSM (Base Station Manager) ID of the CDMA2000 HRPD system
overlaid in the cell in the eNB.
bscId BSC (Base Station Controller) ID of the CDMA2000 HRPD system
dpssId DPSS ID of the CDMA2000 HRPD system overlaid in the cell in the eNB.
btsId BTS (Base Transmission Station) ID of the CDMA2000 HRPD system
sectorId Sector ID of the CDMA2000 HRPD system overlaid in the cell in the eNB.
tReselectionHRPD TReselctionHRPD included in the HRPD Reselection information sent to
SIB8.
The default is 0, and can be changed by the operator.
tReselectionSfUsageHRPD Whether to use tReselectionSfUsageHRPD of HRPD reselection
information that is sent down to SIB8.
tReselectionSfUsageHRPD determines whether to apply a scaling factor
for HRPD cell reselection.
• CI_no_use: tReselectionSfUsageHRPD is not used.
• CI_use: tReselectionSfUsageHRPD is used.
tReselectionSfMediumHRPD TReselectionSfMediumHRPD included in the HRPD Reselection
information sent to SIB8.
• ci_1Dot0: 1.0 is used for the medium timer.
tReselectionSfHighHRPD TReselectionSfHighHRPD included in the HRPD Reselection information
sent to SIB8.
• ci_1Dot0: 1.0 is used for the high timer.
Parameter Descriptions of RTRV-HRPD-PREG/CHG-HRPD-PREG

preRegAllowed Whether to use CDMA2000 HRPD pre-registration of the cell in the eNB.
preRegZoneId The preRegistration zone ID of the cell in the eNB.
NumOf2ndPreRegZoneIdList The secondary pre-registration zone ID list count of the cell in the eNB.

Confidential
secondaryPreRegZoneId1 The first secondary pre-registration zone ID of the cell in the eNB.
secondaryPreRegZoneId2 The second secondary pre-registration zone ID of the cell in the eNB.
Counters and KPIs

with this feature.
REFERENCE
Radio Resource Control (RRC); Protocol specification (Release 9).
[2] 3GPP TS 23.402: Architecture enhancements for non-3GPP accesses (Release
9).

Confidential
LTE-SW1102, Non-Optimized Handover to

HRPD
INTRODUCTION
If a user gets out of the LTE service coverage and moves into a HRPD network
coverage while receiving LTE data, the eNB transfers the data to the HRPD
network in accordance with the non-optimized handover (redirection) procedure,
providing continuity of the data service. The eNB determines non-optimized
handover to HRPD based on the measurement report of the UE. After determining
HRPD non-optimized handover of the UE, the eNB releases the RRC connection
of the UE, and designates the carrier frequency of the HRPD network to which the
UE is to move. The UE switches into the target carrier frequency of HRPD
designated by the eNB and starts receiving the data service on the HRPD network.
BENEFIT
• An operator can provide connected mobility to its subscribers from E-UTRAN
to CDMA2000 HRPD.
• Users in connected state can move from E-UTRAN to CDMA2000 HRPD.
DEPENDENCY
MME
CDMA (2G)
• Others
CDMA Device
LIMITATION
None
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-SW1010 Intra-LTE Redirection
This feature and LTE-SW1010 Intra-LTE Redirection use RRC Connection
Release with redirectedCarrierInfo.

Confidential
According to UE capability, configuration, CDMA network, radio condition of

UE, either this feature or Intra-LTE Redirection operates.
FEATURE DESCRIPTION
Interworking between LTE and eHRPD operates based on the following
architecture. When UE exists on LTE networks, traffics flow from eNB to PDN
Gateway. If the UE switches into eHRPD, the traffic flows through HSGW.
Non-optimized eHRPD refers the movement of the UE from E-UTRAN to eHRPD

without tunneled signaling (that is, S101 signaling) and data forwarding between
the LTE and eHRPD (S103). After leaving E-UTRAN, the UE performs radio-
level attachment to the target access network such creating an eHRPD session.
Below call flow illustrates the non-optimized handover procedure.

Confidential
1) The eNB decides non-optimized handover to HRPD.

2) The eNB transmits a UE context release request to the MME.
3) The MME transmits a UE context release command to the eNB.
4) The eNB transmits a RRC connection release with the target HRPD carrier
frequency to the UE.
5) The eNB transmits a UE context release complete to the MME.
6) The UE switches to the HRPD designated by the eNB on the RRC connection
release, and access the HRPD network. The UE performs the connection setup
procedure to receive the service on the HRPD network. UE stays on the HRPD
network to continue receiving the service.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-EUTRA-A2CNF and set activeState to Active for
A2PurposeIRatBlind purpose.
• To deactivate this feature, do the following:
• Run CHG-EUTRA-A2CNF and set activeState to Inactive for
A2PurposeIRatBlind purpose.
Key Parameters
parameters.
Parameter Descriptions of RTRV-EUTRA-A2CNF/CHG-EUTRA-A2CNF
PURPOSE This parameter is the purpose of using the Event A2 per cell. It is used to
activate the measurement gap as default.
• LteHo: Used for Gap Activate
• LteBlind: Used for Blind HO
• IRatHo: Used for IRAT HO
• IRatBlind: Used for IRAT Blind HO
• Ca: Used for Carrier Aggregation
• CaPeriodicMr
• Srvcc
• Mdt
• CaInterFreq
frequency.
This change is applied to the UE from next RRC signaling procedure (for
updated to the current Active UEs.
parameters.

Confidential
CARRIER_INDEX CDMA2000 HRPD carrier index. Up to 8 carriers can be assigned per
cell.
STATUS Whether the CDMA2000 HRPD carrier is valid.
• N_EQUIP: Invalid
• EQUIP: Valid
BAND_CLASS Band class of the cell.
ARFCN ARFCN of the cell.
OFFSET_FREQ Offset frequency of the cell.
Counters and KPIs

HO_INTER_RAT_NONOPT_HRP NonOptHrpdAtt Inter RAT Non-Optimized HRPD handover
D attempt count
NonOptHrpdPrepSucc Inter RAT Non-Optimized HRPD handover
preparation success count
NonOptHrpdSucc Inter RAT Non-Optimized HRPD handover
execution success count
REFERENCE
[3] 3GPP TS36.413 Evolved Universal Terrestrial Access Network (E-UTRAN);
[4] 3GPP TS23.402 Architecture enhancements for non-3GPP access
[5] 3GPP2 X.S0057 E-UTRAN-eHRPD Connectivity and Interworking: Core
Network Aspects

Confidential
LTE-SW1103, Optimized Handover to HRPD

INTRODUCTION
If a user gets out of the LTE service coverage and moves into a HRPD network
coverage while receiving LTE data, eNB makes UE switch to the HRPD network.
Before switching, UE can pre-register the HRPD network if the both networks and
UE support the pre-registration. The LTE supports pre-registration between UE
and the HRPD network through tunneling. eNB decides optimized handover to
HRPD based on the HRPD measurement report of UE. After receiving the result
of HRPD measurement of the UE, the eNB selects the handover target cell, and
performs handover preparation. If handover preparation with the HRPD network is
performed successfully, the eNB commands the UE to perform handover to the
HRPD. The UE performs handover to the target cell of HRPD designated by the
eNB, receiving the data service on the HRPD network.
BENEFIT
• Operator can provide connected mobility to its subscribers from E-UTRAN to
CDMA2000 HRPD.
• Users in connected state can move from E-UTRAN to CDMA2000 HRPD,
remaining the connected state.
DEPENDENCY
MME
CDMA (2G)
• Others
CDMA Device
LIMITATION
None
SYSTEM IMPACT
capabilities.
Interdependent Feature: Intra-LTE Handovers
This feature is a type of inter-RAT handover.

Confidential
According to UE capability, configuration, CDMA network, radio condition of

UE, either this feature or Intra-LTE Handovers operates.
FEATURE DESCRIPTION
Interworking between LTE and eHRPD operates based on the architecture shown
below. When UE exists on LTE networks, traffics flow from eNB to PDN
Gateway. If the UE switches into eHRPD, the traffic flows through HSGW. There
are two kinds of PS Handover to eHRPD: Non-optimized handover and optimized
handover.
The optimized handover includes pre-registration and data forwarding. For pre-
registration, S101 interface between MME and eAN needs to be supported.
Through this interface, UE register eHRPD when UE stays on LTE. During
handover, serving gateway can forward data to HSGW through S103 interface.
Figure below depicts the pre-registration procedure.

Confidential
1) The UE starts preregistration to HRPD. Idle UE establishes RRC connection

with eNB to switch into the connected status.
2) to 7) Radio session, authentication and IP session establishment between UE
and HRPD network are made with S101 tunnelling interface.
Figure below depicts the handover procedure to eHRPD.

Confidential
1) The UE transmits a measurement report with the HRPD measurement.

2) The source eNB decides optimized handover to HRPD.

Confidential
3) The source eNB transmits the handover from EUTRA preparation request to
UE, requesting handover preparation to HRPD.
4) The source eNB receives the UL HO preparation transfer from UE.
5) The source eNB transmits UL CDMA2000 tunnelling to Source MME,
requesting optimized handover to HRPD. The HRPD message received from UE
in step 4) is included in the message.
6) to 10) Handover preparation procedures are performed between Source E-
UTRAN and target HRPD network. In these processes, resources are assigned so
that UE can continue receiving the data service on the target HRPD after
optimized handover. If data forwarding is possible, tunnel setup is made for data
forwarding.
11) The source eNB receives DL CDMA2000 tunnelling from the source MME.
12) The source eNB transmits the mobility from EUTRA command including the
HO command from the target HRPD AN to the UE.
13) and 14) The UE switches to the HRPD target cell designated by eNB, and
transmits the traffic channel completion to HRPD AN. UE continues receiving the
data service from HRPD.
15) and 16) The target HRPD network performs handover completion.
17) and 18) The target HRPD AN notifies the source MME of completion of
optimized handover.
19) to 24) The source MME releases the resources used in E-UTRAN after
optimized handover with the HRPD network. If the tunnel for data forwarding is
set up, the source MME releases the data forwarding tunnel.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-EUTRA-A2CNF and set activeState to Active for
ci_A2PurposeIRatHo purpose.
• Run CHG-EUTRA-A2CNF and set activeState to Inactive for
ci_A2PurposeIRatHo purpose.

Confidential
Key Parameters
parameters.
• CaPeriodicMr
• Srvcc
• Mdt
• CaInterFreq
frequency.
This change is applied to the UE from next RRC signaling procedure (for
updated to the current Active UEs.
parameters.
cell.
• EQUIP: Valid.
BAND_CLASS Band class of the cell.
ARFCN ARFCN of the cell.
Parameter Descriptions of RTRV-NBR-HRPD/CHG-NBR-HRPD/CRTE-NBR-

HRPD/DLT-NBR-HRPD

Confidential
RELATION_IDX Database index of CDMA2000 HRPD neighboring cell.
STATUS The validity of the CDMA2000 HRPD neighboring cell information.
• N_EQUIP: Information on the CDMA2000 HRPD neighboring cell is
invalid.
• EQUIP: Information on the CDMA2000 HRPD neighboring cell is valid.
COLOR_CODE The color code of CDMA2000 HRPD neighboring cell.
BSM_ID BSM ID of CDMA2000 HRPD neighboring cell.
BSC_ID BSC ID of CDMA2000 HRPD neighboring cell.
DPSS_ID DPSS ID of CDMA2000 HRPD neighboring cell.
BTS_ID BTS ID of CDMA2000 HRPD neighboring cell.
SECTOR_ID The sector ID of CDMA2000 HRPD neighboring cell.
BAND_CLASS The band class of CDMA2000 HRPD neighboring cell.
ARFCN ARFCN of CDMA2000 HRPD neighboring cell.
PN_OFFSET The PN offset of the CDMA2000 HRPD neighboring cell.
Parameter Descriptions of RTRV-HRPD-B1CNF/CHG-HRPD-B1CNF

PURPOSE The purpose for using the CDMA2000 HRPD Event B1 information. It is
used for inter-RAT Handover and SON ANR function.
• ci_B1PurposeInterRatHandover: For inter-RAT Handover.
• ci_B1PurposeANR_Specific: For ANR.
• ci_B1PurposeSpare_1: Reserved.
cell.
ACTIVE_STATE Whether to use the CDMA2000 HRPD Event B1.
• Inactive: CDMA2000 HRPD Event B1 is not used.
• Active: CDMA2000 HRPD Event B1 is used.
B1_THRESHOLD_CDMA2000 The threshold used for triggering the inter-RAT measurement report for
CDMA2000 HRPD Event B1.
HYSTERESIS Hysteresis applied to entry and leave condition of CDMA2000 HRPD
Event B1.
TIME_TO_TRIGGER timeToTrigger value for the CDMA2000 HRPD Event B1. The
timeToTrigger value is the period that must be met for the UE to trigger a
measurement report.
REPORT_INTERVAL The reporting interval of a measurement report for CDMA2000 HRPD
Event B1.
REPORT_AMOUNT The number of measurement reports for CDMA2000 HRPD Event B1.
Parameter Descriptions of RTRV-HRPD-B2CNF/CHG-HRPD-B2CNF

Confidential
PURPOSE The purpose for using the CDMA2000 HRPD Event B2 information. It is
currently used for the Inter-RAT handover function.
• ci_B2PurposeInterRatHandover: For inter-RAT handover.
• ci_B2PurposeSrvcc: For SRVCC.
cell.
ACTIVE_STATE Whether to use CDMA2000 HRPD Event B2.
• Inactive: CDMA2000 HRPD Event B2 is not used.
• Active: CDMA2000 HRPD Event B2 is used.
B2_THRESHOLD1_RSRP RSRP threshold1 used for triggering the EUTRA measurement report for
B2_THRESHOLD1_RSRQ RSRQ threshold1 used for triggering the EUTRA measurement report for
B2_THRESHOLD2_CDMA2000 CDMA2000 threshold 2 used for triggering the inter-RAT CDMA2000
measurement report for CDMA2000 HRPD Event B2.
HYSTERESIS Hysteresis applied to entry and leave condition of CDMA2000 HRPD
Event B2.
TIME_TO_TRIGGER timeToTrigger value for the CDMA2000 HRPD Event B2. The
timeToTrigger value is the period that must be met for the UE to trigger a
measurement report.
REPORT_INTERVAL The reporting interval of a measurement report for CDMA2000 HRPD
Event B2.
REPORT_AMOUNT The number of measurement reports for CDMA2000 HRPD Event B2.
TRIGGER_QUANTITY_EUTRA The EUTRA quantity used to calculate a triggering condition for
• ci_rsrp: RSRP.
• ci_rsrq: RSRQ.
Parameter Descriptions of RTRV-HRPD-PRESEC/CHG-HRPD-PRESEC

CELL_NUM The cell number to be changed or retrieved.
RELATION_IDX Database index of HRPD Pre-Registration Sector.
STATUS The validity of the HRPD Pre-Registration Sector information.
BAND_CLASS The band class of HRPD Pre-Registration Sector.
ARFCN ARFCN of HRPD Pre-Registration Sector.
PN_OFFSET The PN offset of the HRPD Pre-Registration Sector.
SECTOR_ID_123[33] This parameter indicates SectorID of HRPD Pre-Registration Sector.
Counters and KPIs


Confidential
with this feature.
REFERENCE
[4] 3GPP TS23.402 Architecture enhancements for non-3GPP access
[5] 3GPP2 X.S0057 E-UTRAN-eHRPD Connectivity and Interworking: Core
Network Aspects

Confidential
LTE-SW2011, Service based Intra-LTE Handover

INTRODUCTION
The UE can use a variety of services such as Voice over LTE, Web or FTP in the
LTE network. Because each service has different characteristics, it is necessary to
use a different handover policy for each service. For example, in case of VoLTE in
a multi-carrier environment, it is necessary to enable the UE to handover to the
carrier with good coverage. Services with a different QoS use a different QCI. For
handover control for each service, the eNB applies the handover policy set for
each QCI.
The service based intra-LTE handover function can be used in the multi-carrier
environment. The eNB uses this function only to the UE that supports multi-
carrier.
BENEFIT
• Using a handover policy set for each QCI, a different handover policy can be
applied for a different service.
• The mobility quality of VoLTE can be improved.
DEPENDENCY
LTE-SW1007 (Inter-frequency handover)
• Others
This function can be enabled in the multi-carrier environment.
LIMITATION
• Up to 5 mobility profiles are allowed.
• QCI 5 is determined according to the default mobility profile (Mobility Profile
0).
SYSTEM IMPACT
capabilities.
This feature can be activated only when the LTE-SW1007 (Inter-frequency
handover) feature is enabled.

Confidential
FEATURE DESCRIPTION
The operator sets the parameters required for service based intra-LTE handover.
Provisioning/Parameter Settings for service based Intra-LTE
Appropriate mobility profile is allocated to each QCI. The table below shows an
example of mobility profile allocation according to QCI. Mobility Profile 0 is the
default configuration, which is allocated to the QCI that does not belong to
Mobility Profiles 1-4. For QCI 5, Mobility Profile 0 is allocated instead of
Mobility Profiles 1-4.
The table below is example of mobility profile allocation for each QCI.
Mobility Profile # Mobility Profile Mobility Profile Mobility Profile Mobility Profile Mobility Profile
0 1 2 3 4
QCIs allocated to Default QCI 1 QCI 2, 3, 4 QCI 7, 8, 9 No allocated
each mobility configuration QCI
group (Default value
per QCI)
Mobility control related items are set for each mobility profile as shown below.
• Preferred target carrier frequencies for E-UTRAN (FDD or TDD)
• Handover triggering event
• Measurement configuration
• Blind redirection option
UE may have multiple QCIs belonging to different mobility profiles. In such
cases, Mobility Profile of a UE is determined by the mobility profile associated
with highest priority QCI (without QCIs in Mobility Profile #0) of that UE. If
highest priority QCI (without QCIs in Mobility Profile #0) is nothing, then service-
based handover scheme is disabled for that UE and existing handover scheme is
applied.
The table below is example of Priority Allocation per QCI.
QCI # 0 1 2 3 4 5 6 7 8 9
Priority 9 2 4 3 5 1 6 7 8 9
The mobility profile for a UE is determined based on the QCI of a bearer that is
used by the UE. Therefore, a different handover policy can be used per QCI. The
operational scenario is described below.
The figure below is example of service based intra-LTE handover.

Confidential
For example, UE A and UE B have QCI 1 and QCI 9 respectively and mobility
profile per QCI is set as shown in the table below. That is, Mobility Profile 1 is
allocated to UE A and Mobility Profile 2 is allocated to UE B. In this case, if a
preferred carrier is set to Carrier A for Mobility Profile 1 and Carrier B for
Mobility Profile 2, UE A handovers to Carrier A and UE B handovers to Carrier B
as shown in the figure below.
The table below is example of Mobility Profile Allocation per QCI that is Set in
the UE.
UE A B
QCI 1 9
Mobility Profile Mobility Profile 1 Mobility Profile 2
SYSTEM OPERATION
How to Activate
Preconditions
If multiple bearers with different QCIs are configured for the same UE, then the
QCI Mobility Group ID with highest priority QCI is selected. QCI Mobility Group
specific handover parameters can be configured by RTRV/CHG-EUTRA-FAQCI,
RTRV/CHG-EUTRA-A1CNFQ, RTRV/CHG-EUTRA-A2CNFQ, RTRV/CHG-
EUTRA-A3CNFQ, RTRV/CHG-EUTRA-A4CNFQ, RTRV/CHG-EUTRA-
A5CNFQ. If specific QCI Mobility Group is going to use event A3 to handover to
the specific FA, then use:
• CHG-EUTRA-FAQCI to set handover type to be A3
• CHG-EUTRA-A3CNFQ to set the active status of the corresponding cell,
handover purpose, QCI group index, and FA index.
• Run CHG-QCI-VAL and set QCI_MOBILITY_GROUP_ID of the specific

Confidential
QCI (except QCI = 5) to 1-4.

• Run CHG-QCI-VAL and set QCI_MOBILITY_GROUP_ID of the specific
QCI to 0.
Key Parameters
parameters.
characteristics.
QCI_MOBILITY_GRO This attribute defines the QCI Mobility Group ID of the QCI.
UP_ID
parameters.
characteristics.
QCI_MOBILITY_GRO This attribute defines the QCI Mobility Group ID of the QCI.
UP_ID
Parameter Descriptions of RTRV-EUTRA-FAQCI/CHG-EUTRA-FAQCI

FA_INDEX EUTRA frequency index. Up to 8 FAs can be assigned per cell.
QCI_GROUP_INDEX QCI Group index.
STATUS Whether the EUTRA FA is valid.
• EQUIP: Valid.

Confidential
OFFSET_FREQ Frequency offset value applied to offsetFreq in RRC Connection Reconfiguration.
HANDOVER_TYPE Handover Type per Carrier
• ci_HoEventA3
• ci_HoEventA4
• ci_HoEventA5
Parameter Descriptions of RTRV-EUTRA-A1CNFQ/CHG-EUTRA-A1CNFQ

ACTIVE_STATE This parameter indicates whether event A1 is enabled/disabled per target frequency.

PURPOSE This parameter is the purpose of using the Event A2 per cell. It is used to activate
the measurement gap as default.
• CaPeriodicMr
• Srvcc
• Mdt
• Spare_2: Reserved.
ACTIVE_STATE This parameter indicates whether event A2 is enabled/disabled per target frequency.
• Active: Event A2 is used. If HO of the target frequency is not needed in the site,
this is inactive.
This change is applied to the UE from next RRC signaling procedure (for example,
Attach or Idle to Active). To avoid overload, a new setting is not updated to the
current Active UEs.


Confidential
PURPOSE This parameter is the purpose of using Event A3 event.
• Spare_2: Reserved. Not used at this moment.
FA_INDEX The FA_INDEX is a parameter corresponding to the FA_INDEX of EUTRA-FA. The
configuration conditions of A3 event (A3_OFFSET and TRIGGER_QUANTIY) can be
set differently per FA. To configure A3 event for a specific FA, the status of EUTRA-
FA (FA_INDEX #n) must be EQUIP and the ACTIVE_STATE of EUTRA-A3CNF
(FA_INDEX #n) must be Active.
ACTIVE_STATE This parameter is the purpose of using Event A3 event. If this is set to Inactive, the
A3 event is not configured.

• A4PurposeUntraLteHandover: handover is executed
• A4PurposeANR_Specific: the ANR operation is executed
• A4PurposeCA: SCELL is configured
• A4PurposeUnloading: the unloading operation is executed
• A4PurposeSpare_2: it is not used at this moment because it is reserved for future
use.
configuration conditions of A4 event (A4_THRESHOLD_RSRP and
TRIGGER_QUANTIY) can be set differently per FA. To configure A4 event for a
specific FA, the status of EUTRA-FA (FA_INDEX #n) must be EQUIP and the
ACTIVE_STATE of EUTRA-A4CNF (FA_INDEX #n) must be Active. The
ANR_Specific/CA/Unloading is only used to configure FA_INDEX #0 and other
values are ignored.


Confidential
• IntraLteHandover: Intra-LTE handover.
configuration conditions of A5 event (A5_THRESHOLD_RSRP1 and
TRIGGER_QUANTIY) can be set differently per FA. To configure A5 event for a
specific FA, the status of EUTRA-FA (FA_INDEX #n) must be EQUIP and the
ACTIVE_STATE of EUTRA-A5CNF (FA_INDEX #n) must be Active.
Counters and KPIs

- IntraEnbAtt Intra eNB handover attempt count
IntraEnbPrepSucc Intra eNB handover preparation success count
IntraEnbSucc Intra eNB handover execution success count
IntraEnbPrepFail_CP_ Intra eNB handover preparation fails due to due to call
CC_TO control timeout in the protocol blocks (MAC, RLC, PDCP,
GTP)
IntraEnbPrepFail_CP_ Intra eNB handover preparation fails due to reset
CC_FAIL notification (eNB failure or block restart) from ECMB or by
the ECCB block
IntraEnbPrepFail_UP_ Intra eNB handover preparation fails due to the failure in
MAC_FAIL the MAC block
IntraEnbPrepFail_UP_ Intra eNB handover preparation fails due to the failure in
RLC_FAIL the RLC block
IntraEnbPrepFail_RRC Intra eNB handover preparation fails due to receiving RRC
_SIG_FAIL signaling
IntraEnbPrepFail_CP_ Intra eNB handover preparation fails due to Backhaul QoS
BH_CAC_FAIL based CAC
IntraEnbPrepFail_CP_ Intra eNB handover preparation fails due to Capacity
CAPA_CAC_FAIL based CAC
IntraEnbPrepFail_CP_ Intra eNB handover preparation fails due to Air QoS
QOS_CAC_FAIL based CAC
IntraEnbPrepFail_S1A Intra eNB handover preparation fails due to the S1AP
P_CU_FAIL specification cause
IntraEnbPrepFail_S1A Intra eNB handover preparation fails due to the S1 SCTP
P_LINK_FAIL link failure
IntraEnbPrepFail_S1A Intra eNB handover preparation fails due to receiving
P_SIG_FAIL S1AP signaling
IntraEnbFail_CP_CC_ Intra eNB handover fails due to call control timeout in the
TO protocol blocks (MAC, RLC, PDCP, GTP)
IntraEnbFail_CP_CC_ Intra eNB handover fails due to reset notification (eNB
FAIL failure or block restart) from ECMB or by the ECCB block
IntraEnbFail_UP_GTP Intra eNB handover fails due to the failure in the GTP
_FAIL block

Confidential

IntraEnbFail_UP_MAC Intra eNB handover fails due to the failure in the MAC
_FAIL block
IntraEnbFail_UP_RLC Intra eNB handover fails due to the failure in the RLC
_FAIL block
IntraEnbFail_RRC_HC Intra eNB handover fails due to HO preparation timeout
_TO (not received HO command)
IntraEnbFail_RRC_SI Intra eNB handover fails due to receiving RRC signaling
G_FAIL
IntraEnbFail_S1AP_C Intra eNB handover fails due to the S1AP specification
U_FAIL cause
IntraEnbFail_S1AP_LI Intra eNB handover fails due to the S1 SCTP link failure
NK_FAIL
IntraEnbFail_S1AP_SI Intra eNB handover fails due to receiving S1AP signaling
G_FAIL
IntraHOTime Time taken from transmitting the
RRCConnectionReconfiguration message to the UE until
after receiving the RRCConnectionReconfiguration
Complete message from the UE.
IntraHOTimeTot Sum of intra HO interrupt time
IntraHOTimeCnt Count of IntraHOTime collected
REFERENCE
None

Confidential
LTE-SW2014, SPID based Dedicated Priority

INTRODUCTION
The eNB supports dedicated signaling with Inter-Frequency/RAT cell reselection
or handover priorities based on Subscriber Profile ID (SPID).
• Standard-based SPID support
• Operator-specific SPID support
BENEFIT
• An operator can control idle mode camping RAT and carriers of a UE based
on absolute priorities determined by subscription information.
• The operator can control service frequency of a UE based on absolute
priorities determined by subscription information.
DEPENDENCY
E-UTRAN (LTE), UTRAN (3G), GERAN (2G)
• Others
SPID values required.
LIMITATION
• The reference values, SPID = 1-128, 254, 255 and 256 can be supported.
• SPID dedicated priority is supported for only LTE, UTRAN, or GERAN
frequencies.
SYSTEM IMPACT
capabilities.
This feature can be activated only when the LTE-SW1007 (Inter-Frequency
Handover) or Inter-RAT Handover (for example, LTE-SW1202 PS Handover
between LTE and UTRAN) feature is enabled.
FEATURE DESCRIPTION
SPID information is received from MME (Initial Context Setup Request/UE
Context Modification/Downlink NAS Transport) or Other eNB (Handover Setup
Request).
Confidential
eNB support to Inter-frequency handover or reselection priority based on

dedicated priority each SPID.
SPID based inter-frequency handover

When the eNB receives UE SPID, it checks whether the SPID is set by the
operator. If this SPID is set, the eNB performs Inter-frequency handover for the
highest prioritized frequency in the dedicated priority list.
Related Operation
• When the eNB receives UE SPID and operator set to 'use' for USED_FLAG
(CHG-EUTRA-PRIOR) each frequencies (with set
SPID_MOBILITY_OPTION of the specific Cell/PLMN/FA/SPID with the
highest dedicatedPriority value to 'handoverOnly' or 'both' using CHG-
EUTRA-PRIOR).
• The eNB performs measurement (A4, A5) using
RRCConnectionReconfiguration procedure for the highest prioritized
frequencies among the selected frequencies.
• The eNB sets Measurement Gap, which leads to search for Inter-frequency
cell.
• When the eNB receives MR by A4 (neighbor cell signal strength only) or A5,
it performs inter-frequency handover toward the searched frequency.
SPID based inter-RAT handover

When the eNB receives UE SPID, it checks whether the SPID is set by the
operator. If the SPID is set and the highest prioritized frequency is Inter-RAT
frequency, the eNB performs Inter-RAT handover to the chosen frequency.
Related Operation
• When the eNB receives UE SPID and operator set to 'use' for USED_FLAG
(CHG-UTRA-PRIOR or CHG-GERAN-PRIOR) each frequencies (with set
SPID_MOBILITY_OPTION of the specific Cell/PLMN/FA/SPID with the
highest dedicatedPriority value to 'handoverOnly' or 'both' using CHG-UTRA-
PRIOR or CHG-GERAN-PRIOR).
• If the highest prioritized frequency is Inter-RAT frequency, the eNB performs
measurement (B1, B2) using RRCConnectionReconfiguration procedure on
the highest prioritized inter-RAT frequency.
• The eNB sets Measurement Gap, which leads to search for Inter-frequency
cell.
• When the eNB receives MR by B1 or B2, it performs inter-frequency
handover toward the searched frequency.
• If the frequencies of multiple RATs have the same highest priority, one target
RAT is chosen according to the fixed order of LTE > UTRAN > GERAN.

Confidential
SPID based reselection priority

During RRC Connection Release occurrence, the SPID setup of corresponding UE
is verified by eNB. If the setup is complete, the corresponding dedicated priority
list is transferred to UE by eNB.
Related Operation
• When eNB send RRC Connection Release message to UE, using reselection
priority based on SPID. (Set SPID_MOBILITY_OPTION of the specific
Cell/PLMN/FA/SPID with the highest dedicatedPriority value to
'reselectionOnly' or 'both' using CHG-EUTRA-PRIOR.)
• If USED_FLAG is 'use', eNB configuration to UE for
IdleModeMobilityControlInfo based on SPID.
• If USED_FLAG is 'no_use' for the UE, eNB configured
IdleModeMobilityControlInfo according to Idle mode Load Balancing feature.
Specification
SPID range
• Values 1-128: Operator specific SPID values.
• Values 129-256: Reference values
Reference SPID values
Table below outlines eNB local configuration in idle and connected mode for
SPID = 256.
Configuration parameter Value Meaning
E-UTRAN carriers priority high The selection priorities for idle and connected mode of all E-
UTRAN carriers are higher than the priorities for all UTRAN and
GERAN carriers.
UTRAN carriers priority medium The selection priorities for idle and connected mode of all UTRAN
carriers are lower than the priorities for all E-UTRAN carriers and
higher than the priorities for all GERAN carriers.
GERAN carriers priority low The selection priorities for idle and connected mode of all GERAN
carriers are lower than the priorities for all E-UTRAN and UTRAN
carriers.
SPID = 255.
UTRAN carriers priority high The selection priorities for idle and connected mode of all UTRAN
carriers are higher than the priorities for all GERAN and E-
UTRAN carriers.
GERAN carriers priority medium The selection priorities for idle and connected mode of all GERAN
carriers are lower than the priorities for all UTRAN carriers and
higher than the priorities for all E-UTRAN carriers.
E-UTRAN carriers priority low The selection priorities for idle and connected mode of all E-
UTRAN carriers are lower than the priorities for all UTRAN and
GERAN carriers.

Confidential
SPID = 254.
GERAN carriers priority high The selection priorities for idle and connected mode of all
GERAN carriers are higher than the priorities for all UTRAN and
E-UTRAN carriers.
UTRAN carriers priority medium The selection priorities for idle and connected mode of all UTRAN
carriers are lower than the priorities for all GERAN carriers and
higher than the priorities for all E-UTRAN carriers.
E-UTRAN carriers priority low The selection priorities for idle and connected mode of all E-
UTRAN carriers are lower than the priorities for all GERAN and
UTRAN carriers.
SYSTEM OPERATION
How to Activate
Preconditions
• Set dedicated priority of the FA to the specific SPID by using RTRV/CHG-
EUTRA-PRIOR for EUTRAN FA, RTRV/CHG-UTRA-PRIOR for UTRAN
FA, and RTRV/CHG-GERAN-PRIOR for GERAN FA.
• If an operator wants to make a UE with specific SPID to intra-LTE handover
to FA with the highest dedicate priority using A4 or A5 measurement event,
a Set SPID_MOBILITY_OPTION of the specific Cell/PLMN/FA/SPID
with the highest dedicatedPriority value to handoverOnly or both
using CHG-EUTRA-PRIOR.
b Set SPID_MEASURE_OPTION of the corresponding
Cell/PLMN/FA/SPID to hoEventA4 or hoEventA5 using CHG-
EUTRA-PRIOR.
c Set ACTIVE_STATE of the A4 or A5 event for the corresponding Cell/FA
to be active using CHG-EUTRA-A4CNF or CHG-EUTRA-A5CNF with
index A4purposeInterFrequencySPID or A5purposeInterFrequencySPID
(if service based handover feature is applied, EUTRA-A4CNFQ or
EUTRA-A5CNFQ with the relevant QCI Mobility Group ID has to be
considered also.).
• If an operator wants to make a UE with specific SPID to inter-RAT handover

Confidential
to FA with the highest dedicate priority using B1 or B2 measurement event,

a Set SPID_MOBILITY_OPTION of the specific Cell/PLMN/FA/SPID
with the highest dedicatedPriority value to handoverOnly or both
using CHG-UTRA-PRIOR or CHG-GERAN-PRIOR.
b Set SPID_MEASURE_OPTION_INTER_RAT of the corresponding
Cell/PLMN/FA/SPID to hoEventB1 or hoEventB2 using CHG-
UTRA-PRIOR or CHG-GERAN-PRIOR.
c Set activeState of the B1 or B2 event for the corresponding Cell/FA to be
active using CHG-UTRA-B1CNF/CHG-UTRA-B2CNF or CHG-
GERAN-B1CNF/CHG-GERAN-B2CNF (if the service specific handover
feature is applied, UTRA-B1CNFQ/UTRA-B2CNFQ or GERAN-
B1CNFQ/GERAN-B2CNFQ with the relevant QCI Mobility Group ID has
to be considered also.).
• Set USED_FLAG of the SPID to be NO_USE by using RTRV/CHG-EUTRA-
PRIOR for EUTRAN FA, RTRV/CHG-UTRA-PRIOR for UTRAN FA, and
RTRV/CHG-GERAN-PRIOR for GERAN FA.
Key Parameters
parameters.
Parameter Descriptions of RTRV-EUTRA-PRIOR/CHG-EUTRA-PRIOR
USED_FLAG This parameter shows whether the dedicated priority is used.
• no_use: Dedicated priority is not used.
• use: Dedicated priority is used.
Parameter Descriptions of RTRV-UTRA-PRIOR/CHG-UTRA-PRIOR

USED_FLAG Whether to use dedicatedPriority.
• CI_no_use: dedicatedPriority is not used.
• CI_use: dedicatedPriority is used.
Parameter Descriptions of RTRV-GERAN-PRIOR/CHG-GERAN-PRIOR


Confidential
parameters.
Parameter Descriptions of RTRV-EUTRA-PRIOR/CHG-EUTRA-PRIOR
PLMN_ID PLMN index. It is mapping to MCC/MNC configured in plmnIdx of
PLDEnbPlmnInfo.
FA_ID This parameter is the Evolved Universal Terrestrial Radio Access (EUTRA)
frequency index. This parameter enters the FA value that each cell supports
and it is mapped to the FA_INDEX parameter value in the RTRV-EUTRA-FA
command.
SPID_INDEX This parameter is the Subscriber Profile ID (SPID). This parameter is the index
used to refer to the registration information of a subscriber.
SPID This parameter is the Subscriber Profile ID (SPID) for Radio Access Terminal
(RAT)/frequency priority value. The range of an entered value is 1-128 and a
value between 129 and 253 cannot be entered.
USED_FLAG This parameter shows whether the dedicated priority is used.
• no_use: Dedicated priority is not used.
• use: Dedicated priority is used.
DEDICATED_PRIORITY This parameter is the dedicated priority value. Enter a dedicated priority value
according to the FA_INDEX and SPID.
SPID_MOBILITY_OPTION Define additional operations based on the mobility setting of the parameter for
SPID of the UE.
• reselectionOnly (0): When UE is released, send the dedicated priority per FA
for SPID that the UE currently possesses among the FAs supported in UE
Radio Capability through IdleModeMobilityControlInfo. However, A4 or A5
based inter-frequency handover based on SPID is not performed.
• handoverOnly (1): When the UE first receives SPID, if the FA configured to
be the highest DEDICATED_PRIORITY for the SPID is different from the
serving frequency of the UE but can be supported in UE Radio Capability,
attach A4 or A5 event to induce inter-frequency handover.
In this case, idleModeMobilityControlInfo to be transmitted when the UE is

released is based on Idle Mode Load Balancing.
• both (2): When the UE first receives SPID, if the FA configured to be the
highest DEDICATED_PRIORITY for the SPID is different from the serving
frequency of the UE but can be supported in UE Radio Capability, attach A4
or A5 event to induce inter-frequency handover. In addition, when the UE is
released, the dedicated priority per FA configured in SPID that the UE
currently possesses among the FAs that can be supported in UE Radio
Capability is transmitted through IdleModeMobilityControlInfo.
SPID_MEASURE_OPTION If spidMobilityOption is handoverOnly or both, designate measurement event
type to trigger inter-frequency handover.
• spidHoEventA4 (0): measurement event type for inter-frequency handover

Confidential
triggering is EventA4.
• spidHoEventA5 (1): measurement event type for inter-frequency handover
triggering is EventA5.
Parameter Descriptions of RTRV-UTRA-PRIOR/CHG-UTRA-PRIOR

CELL_NUM This parameter specifies the cell number to retrieve the periodic report config
information used for interoperating with the UTRAN.
PLMN_INDEX PLMN index. It is mapping to MCC/MNC configured in plmnIdx of
PLDEnbPlmnInfo.
FA_ID This parameter is the Universal Terrestrial Radio Access (UTRA) frequency
index. The operator can enter a FA value each cell supports and maximum 6
FAs can be entered. This parameter is mapped to the FA_INDEX parameter
value included in the RTRV-UTRA-FA command.
SPID_INDEX This parameter is the Subscriber Profile ID (SPID) index. This parameter is the
index used to refer to the registration information of a subscriber.
SPID Subscriber Profile ID for RAT/Frequency priority. spid could not be setting 129-
253.
DEDICATED_PRIORITY Dedicated Priority Value for Frequency according SPID.
According to 3GPP TS36.300, if spid is 255, dedicated priority is set to 7.
SPID of the UE.
Radio Capability through IdleModeMobilityControlInfo. However, B1 or B2
based inter-RAT handover to UTRAN based on SPID is not performed.
attach B1 or B2 event to induce inter-RAT handover to UTRAN.

frequency of the UE but can be supported in UE Radio Capability, attach B1
or B2 event to induce inter-RAT handover to UTRAN. In addition, when the
UE is released, the dedicated priority per FA configured in SPID that the UE
SPID_MEASURE_OPTION_ If spidMobilityOption is handoverOnly or both, designate measurement event
INTER_RAT type to trigger inter-RAT handover to UTRAN.
• spidHoEventB1 (0): measurement event type for inter-RAT handover to
UTRAN triggering is EventB1.
UTRAN triggering is EventB2.

Confidential
Parameter Descriptions of RTRV-GERAN-PRIOR/CHG-GERAN-PRIOR

PLMN_INDEX PLMN index. It is mapping to MCC/MNC configured in plmnIdx of
PLDEnbPlmnInfo.
FA_INDEX GERAN frequency index. Up to 6 FAs can be assigned per cell. It is mapping
to PLDGeranFaPriorInfo.
SPID_INDEX SPID index.
SPID Subscriber Profile ID for RAT/Frequency priority. SPID cannot be in the range
129-253.
DEDICATED_PRIORITY Dedicated Priority Value for Frequency according SPID.
According to 3GPP TS36.300, if SPID is 254, dedicated priority is set to 7.
SPID of the UE.
Radio Capability through IdleModeMobilityControlInfo. However, B1 or B2
based inter-RAT handover to GERAN based on SPID is not performed.
attach B1 or B2 event to induce inter-RAT handover to GERAN.

frequency of the UE but can be supported in UE Radio Capability, attach B1
or B2 event to induce inter-RAT handover to GERAN. In addition, when the
UE is released, the dedicated priority per FA configured in SPID that the UE
SPID_MEASURE_OPTION_ If spidMobilityOption is handoverOnly or both, designate measurement event
INTER_RAT type to trigger inter-RAT handover to GERAN.
GERAN triggering is EventB1.
GERAN triggering is EventB2.
Parameter Descriptions of RTRV-EUTRA-A4CNF/CHG-EUTRA-A4CNF or

RTRV-EUTRA-A4CNFQ/CHG-EUTRA-A4CNFQ
• IntraLteHandover: handover is executed
• ANR_Specific: the ANR operation is executed
• CA: SCELL is configured
• Sendback: the Sendback operation is executed

Confidential
• InterFrequencyLb: the Active Load Balancing operation is executed
• ArpHandover: Enable inter frequency handover function for UEs that have a
specific ARP
• OnDemandHandover: Enable the forced handover triggering by operator
• InterFrequencySPID: inter-frequency handover is executed for specific SPID
with handover mobility option.
ACTIVE_STATE This parameter is the purpose of using Event A4. If this is set to Inactive, the
Event A4 is not configured.
Parameter Descriptions of RTRV-EUTRA-A5CNF/CHG-EUTRA-A5CNF or

RTRV-EUTRA-A5CNFQ/CHG-EUTRA-A5CNFQ
• IntraLteHandover: Used for Intra LTE Handover.
• CaInterFreq: Performs Inter frequency handover for Carrier Aggregation (CA)
UE
• InterFrequencyMbms: Inter frequency handover to get MBMS service
• ArpHandover: Enable Inter frequency handover function for UEs that have a
specific ARP
• OnDemandHandover: Enable the forced handover triggering by operator
• InterFrequencySPID: Inter frequency handover for the specific SPID with
handover mobility option
ACTIVE_STATE This parameter is the purpose of using Event A5. If this is set to Inactive, the
Event A5 is not configured.
Parameter Descriptions of RTRV-UTRA-B1CNF/CHG-UTRA-B1CNF or

RTRV-UTRA-B1CNFQ/CHG-UTRA-B1CNFQ
PURPOSE This parameter specifies the use of the UTRAN Event B1 used for
interoperating with the UTRAN.
• InterRatHandover: Used for handover to the UTRAN. (0)
• ANR_Specific: Used for the ANR operation with the UTRAN. (1)
• Srvcc: Used for the Srvcc with the UTRAN. (2)
• Mlb: Used for MLB. (3)
• InterRatSPID: inter-RAT handover is executed for specific SPID with
handover mobility option. (4)
ACTIVE_STATE This parameter is the purpose of using Event B1. If this is set to Inactive, the
Event B1 is not configured.
Parameter Descriptions of RTRV-UTRA-B2CNF/CHG-EUTRA-B2CNF or

RTRV-EUTRA-B2CNFQ/CHG-EUTRA-B2CNFQ
PURPOSE This parameter is the purpose to retrieve the B2 report configuration
information used for interoperating with the UTRAN.
• InterRatHandover: Used for handover to the UTRAN. (0)
• Srvcc: Used for SRVCC. (1)

Confidential
Parameter Descriptions of RTRV-GERAN-B1CNF/CHG-GERAN-B1CNF or

RTRV-GERAN-B1CNFQ/CHG-GERAN-B1CNFQ
PURPOSE This parameter is the usage of information on the GERAN Event B1 report. It is
used for inter-RAT Handover and SON ANR function.
• InterRatHandover: Used for InterRAT Handover (0)
• ANR_Specific: Used for SON ANR (1)
• Srvcc: Used for SRVCC (2)
• Mlb: For MLB. (3)
Parameter Descriptions of RTRV-GERAN-B2CNF/CHG-GERAN-B2CNF or

RTRV-GERAN-B2CNFQ/CHG-GERAN-B2CNFQ
PURPOSE This parameter is the usage of the GERAN Event B2 report. It is used for inter-
RAT Handover. (0)
• InterRatHandover: For Inter-RAT handover. (0)
• Srvcc: For SRVCC. (1)
Counters and KPIs

with this feature.
REFERENCE
Evolved Universal Terrestrial Radio Access Network (E-UTRAN);Overall

Confidential
LTE-SW3014, ROHC Context Continuation

INTRODUCTION
Up to Release 10, after handover to the target cell, the UE resets ROHC context
and restarts from initialization and refresh state. This leads to inefficiency because
of full uncompressed packet transmission after handover. However, in case of
intra-eNB handover, it is possible to continue ROHC compression/decompression
without reset because ROHC context is in the same eNB. From Release 11, to let
the UE continue ROHC, the eNB can indicate ROHC continue in the
MobilityControllInfo IE.
BENEFIT
For intra-eNB handover, the UE can continue ROHC compression/decompression
after handover. Consequently, air resource efficiency degradation caused by
ROHC context reset after intra-eNB handover can be avoided. Users also can
experience better service quality from the reduced delay jitter.
DEPENDENCY
The UE should support ROHC context continuation.
LIMITATION
ROHC context continuation is applicable only to intra-eNB handover case.
SYSTEM IMPACT
capabilities.
This feature requires LTE-SW3011 Header Compression ROHCv1 as a
prerequisite.
When intra-eNB handover occurs, RoHC context is not reset (that is, no transition
to Initialization and Refresh (IR) state). Therefore, air resource efficiency can be
improved.
FEATURE DESCRIPTION
In intra-eNB HO case, the eNB transmits Handover Command message with
ROHC continue indication in MobilityControlInfo IE. If UE receives ROHC
continue indication, the UE continues full ROHC compression/decompression
even after intra-eNB handover to the target cell. Operator can enable this feature
by setting ROHC_CONTEXT_CONTINUE configuration parameter to On via

Confidential
CHG-ENBPDCP-INF.
Figure below depicts the benefit of ROHC context continuation. With ROHC
context continuation, the UE can continue transmitting/receiving compressed
packets even after Intra-eNB HO.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-ENBPDCP-INF and set ROHC_CONTEXT_CONTINUE as On.
• Run CHG-ENBPDCP-INF and set ROHC_CONTEXT_CONTINUE as Off.
Key Parameters
parameters.
Parameter Descriptions of CHG-ENBPDCP-INF/RTRV-ENBPDCP-INF
ROHC_CONTEXT_CONTIN This parameter indicates whether to continue or reset RoHC context for the
UE RLC UM bearers in a case of a handover within the same eNB.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.331 (Chapter 6.3.4)

Confidential
LTE-SW5005, Inter-PLMN Handover

INTRODUCTION
Inter-PLMN handover is mobility control functionality between cells that served
PLMN is different from each other.
BENEFIT
Operator can provide connected mobility to its subscribers within a shared
network.
User can obtain LTE service in other network operators area which is not the
subscribed network operator.
DEPENDENCY
E-UTRAN (LTE)
LTE-SW1004 (S1 Handover) and LTE-SW1005 (X2 Handover)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Inter-PLMN handover means that UE serving PLMN is changed before and after
handover.
The eNB uses the selected PLMN ID of UE (provided by the UE at RRC
establishment, or, provided by the MME/source eNB at S1/X2 handover) to select
target cells for future handovers appropriately.
When handover event occurs, the source eNB determines a PLMN to be used in
the target cell based on current PLMN in use, or other information present in the
eNB.
The selected target PLMN should be the same as the one in use. This is
accomplished by not changing the serving PLMN if the PLMN in use is supported
in the target cell.
If the PLMN in use is not supported in the target cell the eNB selects the target
PLMN based on the Equivalent PLMNs list provided by the MME.
Confidential
If current serving PLMN is available in the target cell, the target PLMN is the
same as the current serving PLMN. But if not, the source eNB checks whether
inter-PLMN handover is possible based on the UE equivalent PLMNs.
The source eNB at handover indicates that selected target PLMN ID to the MME
as part of the selected TAI sent in the Handover Required message.
In case of inter-PLMN X2 handover, the source eNB replaces the serving PLMN
with the identity of the selected target PLMN and moves the current serving
PLMN to the equivalent PLMN list, before propagating the UE area restriction
information.
Figure below depicts the inter-PLMN X2 handover procedures.

Confidential
Figure below depicts the inter-PLMN S1 handover procedure.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-NBR-EUTRAN, and set (MCC0, MNC0) to (MCC5, MNC5) for
configuring Broadcast PLMN list of the neighbor cell.

Confidential
• Run CHG-NBR-EUTRAN, and set (MCC0, MNC0) to (MCC5, MNC5) to FFF
to de-configure the Broadcast PLMN list of the neighbor cell.
Key Parameters
parameters.
RELATION_IDX Specifies the relation index of EUTRAN Neighbor cell.
MCC0 This parameter is the MCC of PLMN-0 in Broadcast PLMN list information of the
neighbor cell. Enter a 3-digit number whose each digit ranges from 0 to 9.
MNC0 This parameter is the MNC of PLMN-0 in the Broadcast PLMN list information of the
neighbor cell. Enter a 2-digit or 3-digit number where each digit ranges from 0 to 9.
parameters.
Parameter Descriptions of RTRV-ENBPLMN-INFO/CHG-ENBPLMN-INFO

Confidential
PLMN_IDX The PLMN index to be changed or retrieved.
MCC[4] Mobile Country Code (MCC) that comprises Public Land Mobile Network (PLMN).
MNC[4] Mobile Network Code (MNC) that comprises Public Land Mobile Network (PLMN).
Parameter Descriptions of RTRV-CELLPLMN-INFO/CHG-CELLPLMN-INFO

PLMN_IDX The PLMN index to be changed or retrieved.
PLMN_USAGE When cell is operational, this parameter determines whether to use the value of PLMN
corresponding PLMN_IDX.
• USE: The value of PLMN corresponding PLMN_IDX can be serviced.
• NO_USE: The value of PLMN corresponding PLMN_IDX cannot be serviced.

RELATION_IDX Specifies the relation index of EUTRAN Neighbor cell.
ENB_ID This parameter is the eNB ID of the eNB where the neighbor cell belongs.
TARGET_CELL_ID This parameter indicates the Cell Number of the Neighbor EUTRAN Cell. This
information is exchanged between eNBs through X2 messages, and is used for
Handovers.
PHY_CELL_ID This parameter is the Physical Cell ID of the neighbor cell.

Confidential
Counters and KPIs

with this feature.
REFERENCE
[3] 3GPP TS23.251 Network Sharing; Architecture and functional description

Confidential
LTE-SW6001, HetNet Mobility Enhancement

INTRODUCTION
Handover performance in HetNet deployments is not as good as in pure macro
deployments. Especially, HeNB to eNB handover performance shows the worst
performance. In 3GPP Rel.12, multiple enhancements for HetNet mobility are
adopted.
BENEFIT
The following is the list of enhancements for HetNet mobility:
• The T312 timer procedure for improvement to RLF recovery with shorter RLF
recovery time
The use of this timer reduces the total service interruption time in dense
HetNet environment (4-10 picocells per macrocell).
• Cell-specific time to trigger handling
This feature supports is to achieve an optimal balance between the handover
failure rate and short time of stay for Macro-to-Pico or Pico-to-Macro
situations.
DEPENDENCY
• Others
UE: This feature is applicable only to Release 12 (or later) UEs (T312 timer
and altTTT supported).
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
T312 Timer Procedure for Improvement to RLF Recovery with Shorter RLF
Recovery Time
In a dense HetNet deployment, a UE in a pico cell may receive interference from
not only a macro cell but also the other pico cells in the same cluster. Due to such
an increased number of interfering nodes, the interference is significantly
increased even though the UE has not detected a HO target cell yet. This increases

Confidential
the probability of overlap of handover process with the possible RLF (governed by
T310). Typically, the RLF process starts when the UE detects an out of sync
condition (as determined by L1). If the UE receives consecutive N310 out of sync
indications it starts the timer T310. If during the time T310 is running the UE
receives N311 consecutive in sync indications T310 is stopped and the RLF
process is terminated without declaring a Radio Link Failure. If however T310
expires, a radio link failure is declared allowing the UE to attempt a recovery
through re-establishment.
In a dense HetNet deployment, out of sync may occur when UE is moving out of
Pico towards Macro (or other Picos) due to high interference even before the
handoff is triggered. While the T310 timer is running, however, the UE can start
seeing a better RSRP from the target and trigger a Measurement Report. In this
case, given that the Pico’s DL is in out of sync state, the HO signaling with the
target will not be successful. UE has to simply wait for T310 timer to expire and
then initiate re-establishment. This causes unnecessary delay.
To address the above issue, the Timer T312 is introduced as a means of early T310
termination, so that the total service interruption time can be reduced while not
significantly increasing the frequency of RLF/HOF. As shown in figure above,
when Measurement Report (MR) is triggered while the T310 timer is running, the
UE starts T312 timer. When T312 timer expires, it allows for early re-
establishment, instead of waiting for T310 timer.
The T310 timer can also expire prior to T312 resulting in the usual re-
establishment procedure).
The Timer T312 is an optional feature whose use and configuration is controlled
by the operator via the parameters UseT312 (which is an on/off flag) and T312
(which controls the actual time duration of T312 timer). When the TTT (time to
expiry) for that event expires and if T310 is running at that time, T312 is started
(T312 will generally be shorter than T310). If the conditions that lead to the exit
(that is, stopping) of T310 occur while T312 is running, T312 is stopped. If T312
expires the UE declares RLF (without waiting for the expiry of T310). This further
allows UE to perform re-establishment quicker than when T312 timer is not used.

Confidential
Cell Specific Time to Trigger Handling

There is a trade-off between handover failure rates and short time of stay for
different time to trigger values. Thus, TTT values are generally optimized to
achieve a balance. However, prior to Rel-11, TTT values are applied to all target
cells involved in a handover (that is, there is no target cell specific TTT).
Specifically, optimal TTT values for Macro-Pico handover are different from
Macro-Macro handovers. The same holds for Pico-Pico vs Pico-Macro handovers.
This feature allows the operator to set target cell specific TTT values for those
events which control handovers (that is, A3/A4/A5). These TTT values are
referred to as alternativeTimeToTrigger. The target cells for which
alternativeTimeToTrigger is used are sent to the UE using the IE altTTT-
CellsToAddModList-r12 in the IE MeasObjectEUTRA.
SYSTEM OPERATION
How to Activate
Preconditions
• Configure the T312 to non-zero value for the FA index of the cell. The
recommended value is 500 msec.
• Run CHG-EUTRA-A3CNF, CHG-EUTRA-A3CNFQ, CHG-EUTRA-A4CNF,
CHG-EUTRA-A4CNFQ, CHG-EUTRA-A5CNF and CHG-EUTRA-A5CNFQ,
and set ALTERNATIVE_TIME_TO_TRIGGER to non-zero value for the
purpose of IntraLteHandver. The recommended value is 480msec.
• Run CHG-EUTRA-A3CNF, CHG-EUTRA-A3CNFQ, CHG-EUTRA-A4CNF,
CHG-EUTRA-A4CNFQ, CHG-EUTRA-A5CNF and CHG-EUTRA-A5CNFQ,
and set configure ALTERNATIVE_TIME_TO_TRIGGER for the purpose of
IntraLteHandver.
• Configure the T312 to "disabled" for the FA index of the cell. The
recommended value is 500 msec.
Key Parameters

Confidential
parameters.
CELL_NUM The PLD index parameter of the cell number. This value must not exceed
FA_INDEX The PLD index parameter of the FA index. This parameter is the EUTRA
frequency index. This value must not exceed the maximum number of FA
T312 This parameter is the timer value of T312 which the UE starts after sending
Measurement Report, when T310 was running. On the expiry of this timer,
UE sends RRC Connection Reestablishment Request.
Each configurable value indicates the value of T312 timer as defined in
TS36.331 when T312 timer support is enabled.
• disabled: indicates that T312 timer is disabled.

PUPRPOSE The index parameter of the purpose of using Event A3.
ALTERNATIVE_TIME_TO_TRI This parameter is the value of Alternative Time to Trigger. The parameter
GGER shall be valid only for IntraLteHandover purpose.
Each configurable value indicates the value of Alternative Time to Trigger
when Alternative Time to Trigger support is enabled as defined in
TS36.331.
• disabled: Indicates Alternative Time to Trigger support is disabled.

TS36.331.

Confidential

Each configurable value indicates the value of Alternative Time to
Trigger when Alternative Time to Trigger support is enabled as defined in
TS36.331.
• disabled : indicates Alternative Time to Trigger support is disabled.

TS36.331.

TS36.331.

Confidential
TS36.331.
parameters.
Parameter Descriptions of RTRV-ALTTTT-LIST/CHG-ALTTTT-LIST/CRTE-
ALTTTT-LIST/DLT-ALTTTT-LIST
ALT_TTT_CELL_LIST This parameter is the index of neighboring cell to which AltTTT value is
applicable.
STATUS QCI Group index.
PCI_TYPE This parameter indicates the PCI type of the AltTTT neighbor cell.
• singlePci : Uses the single PCI.
• rangedPci : Uses the PCI range.
START_PCI This parameter is the PCI starting value of the AltTTT neighbor cell.
PCI_RANGE Range from the starting physical cell ID of the AltTTT neighbor cell. Not
used if it is a single physical cell ID type. The range includes the start
value.
EARFCN_UL This parameter is the Absolute Radio Frequency Channel Number
(ARFCN) that is an uplink EUTRA carrier frequency.
EARCN_DL This parameter is the ARFCN that is a downlink EUTRA carrier frequency.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.331 EUTRAN Radio Resource Control (RRC) Specification
[2] 3GPP TR 36.839 Mobility enhancements in heterogeneous networks

Confidential
Chapter 5 Operation and

Maintenance
LTE-OM8001, Convention for eNB/Cell Identifier

and Name
INTRODUCTION
This feature describes the format of eNB ID in Global eNB ID, Cell ID in ECGI
and TAC ID. This feature also describes the format of eNB Name and Cell Name.
BENEFIT
Operator can identify the eNB or Cell with its own convention rule and recognize
a specific eNB or Cell with the ID/Name value easily.
DEPENDENCY
None
LIMITATION
The possible special characters are also limited in ‘_’, ‘-’, ‘(’, and ‘)’ when
configured eNB/cell name in LSM.
FEATURE DESCRIPTION
eNodeB ID
The eNB ID is fully configurable (0 ~ 1048575) when eNB is created in LSM.
This eNB ID is used for both eNB ID (20bit) defined in 3GPP TS
36.300/TS24.301 and NE ID.
eNodeB Name
The eNB ID is fully configurable (64 characters) when eNB is created in LSM.
Operator can set the eNB Name with desired string such as 'eNB ID_Sitename'.
The possible special characters are limited in ‘_’, ‘-’, ‘(’, and ‘)’ when configured
eNB name in LSM.
Cell ID
Within a PLMN or network, a cell is uniquely identified by a 28-bit cell ID. The
cell ID is composed of the 20-bit eNB ID supporting the cell, together with the 8-
bit cell ID within the eNB. The relationship between cell ID, eNB ID, and 8-bit
cell ID is given here:

Confidential
Chapter 5 Operation and Maintenance
• cell ID = eNB ID * 256 + 8-bit cell ID

The 8-bit cell ID range has a numeric range from 0 to 255. The table below
summarizes the VZW numbering scheme for the 8-bit cell ID. The value assigned
is a function of both the sector number and the carrier number.
When the cell is created, the Cell ID will be generated by combining eNB ID and
8-bit cell ID (sector ID & carrier ID) inputted by operator. And the same number
with 8-bit cell ID is used for the main identifier for a cell in a network’s OA&M
system such as LSM GUI, CLI, statistics and etc.
Carrier
F1 F2 F3 F4 F5 F6 F7 F8 F9
Sector 1 1 12 13 14 15 16 17 18 19
2 2 22 23 24 25 26 27 28 29
3 3 32 33 34 35 36 37 38 39
4 4 42 43 44 45 46 47 48 49
5 5 52 53 54 55 56 57 58 59
6 6 62 63 64 65 66 67 68 69
7 7 72 73 74 75 76 77 78 79
8 8 82 83 84 85 86 87 88 89
9 9 92 93 94 95 96 97 98 99
10 101 102 103 104 105 106 107 108 109
11 111 112 113 114 115 116 117 118 119
12 121 122 123 124 125 126 127 128 129
13 131 132 133 134 135 136 137 138 139
14 141 142 143 144 145 146 147 148 149
15 151 152 153 154 155 156 157 158 159
16 161 162 163 164 165 166 167 168 169
17 171 172 173 174 175 176 177 178 179
18 181 182 183 184 185 186 187 188 189
19 191 192 193 194 195 196 197 198 199
20 201 202 203 204 205 206 207 208 209
21 211 212 213 214 215 216 217 218 219
22 221 222 223 224 225 226 227 228 229
23 231 232 233 234 235 236 237 238 239
24 241 242 243 244 245 246 247 248 249
Tracking Area Code (TAC)

Within a PLMN or network, a tracking area is uniquely specified by its Tracking
Area Code (TAC). The TAC is a two byte number. And TAC is fully configurable
(0 ~ 65535) when the cell is created in LSM.

Confidential
Chapter 5 Operation and Maintenance
Cell Name
When the cell is created in LSM, the cell name is generated by combining eNB ID,
sector ID, and carrier ID inputted by operator with the following format:
• eNB ID_sector ID_carrier ID (In case of 1st carrier, '_carrier ID' is not
attached.)
After the cell is created, operator can changed the cell name by CLI command.
SYSTEM OPERATION
How to Activate
Preconditions
There are no specific preconditions associated with this feature.
The feature does not need to be activated. It runs automatically.
The feature does not need to be deactivated.
Key Parameters
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
Chapter 6 RAN Sharing
LTE-SW5001, Multi-PLMN Support

INTRODUCTION
Multiple-PLMN support allows provide LTE service to subscribers of multiple
operators in a cell concurrently.
For Multiple-PLMN support, eNB broadcasts multiple PLMN IDs, which are
sharing a cell in system information and supports UE associated signaling with a
UE and an appropriated core network based on the PLMN, which the UE has
selected.
In RAN sharing, each operator may have its own dedicated carrier. The only
available PLMN that is serviced in the dedicated carrier cell is either primary
PLMN or secondary PLMN, which depends on operator ownership of the
dedicated carrier. The primary PLMN ID will always be included in the
broadcasted PLMN list to support successful ANR operation and is marked as
reserved for operator use to avoid access from primary PLMN subscribers when
the carrier is only available for secondary PLMN.
The Multiple Operator Core Network (MOCN) has the RAN structure where
multiple partner operators share one spectrum and the Multiple Operator Radio
Access Network (MORAN) has the RAN structure where each partner operator
uses each dedicated frequency but shares eNB.
BENEFIT
• Operator can reduce CAPEX and OPEX by sharing carrier frequency, site,
eNB, and backhaul network with partners.
• Host operator can figure out how much data is consumed by each partner
operator. The usage data can be utilized for the purpose of settlement among
partner operators.
DEPENDENCY
E-UTRAN (LTE)
• Others
o Partner operators can have their dedicated carrier for MORAN.
o For usage report function, in addition to eNB, LSM should support this
feature.

Confidential
LIMITATION
Supports maximum six PLMNs per eNB.
SYSTEM IMPACT
FEATURE DESCRIPTION
eNB functions for Multiple-PLMN support are as follows:
• Broadcast multiple PLMN IDs (up to six) in system information.
• Routing of signaling for call control based on the selected PLMN ID by UE.
• Inter-PLMN handover support in shared network. (Refer to LTE-SW5005)
• Radio resource sharing in shared cell. (Refer to LTE-SW5002)
In a shared cell, eNB broadcasts the supported PLMN ID list up to 6 through SIB1,
which can be configured by PLMN_IDX, MCC/MNC and PLMN_USAGE
respectively by CHG-ENBPLMN-INFO and CHG-CELLPLMN-INFO. The first
PLMN ID broadcasted to SIB 1 must be set to the same as the PLMN ID of the
global eNB ID. The first listed PLMN is the same as the primary PLMN of eNB.
The supporting PLMN ID list per cell is configured by system parameter. The UE
can read up to six PLMN IDs, to select one of the PLMN IDs based on its
selection process.
When the UE is expected to make RRC connection with the eNB, the selected
PLMN ID by the UE is included in RRC Connection Setup Complete message.
The eNB uses this PLMN ID to select the core network and, in turn the MME, and
to indicate towards appropriate core network operator when transferring Initial UE
Message.
The signaling procedures are as follows.

Confidential
Multiple Operator Support with Dedicated Carriers

In MORAN architecture, operators do not have to share spectrum. One possible
scenario is that operators have their own dedicated carrier and do not share with
others. This feature enables operators to share eNB with their own dedicated
carrier.
The following figure shows an eNB sharing with dedicated carrier between
operators A and B, while the operator A is the owner or manager of the shared
eNB and the operator B shares eNB with a dedicated carrier. In the dedicated
carrier cells of each operator, only one PLMN ID is available, which provides
services to the subscribers of the carrier owner.

Confidential
Definitions used to describe the relation between PLMN ID and the dedicated
carrier owner are given below:
• Owner PLMN: The operator PLMN ID that is the eNB owner or manager of
the eNB.
• Sharing PLMN: The operator PLMN ID that shares eNB with a dedicated
carrier with eNB owner operator.
The rules for PLMN broadcasting in the dedicated carrier cells are as follows:
• In the dedicated carrier cells of eNB owner or manager:
o Only PLMN ID of owner PLMN is broadcasted in SIB1 as the primary
PLMN.
• In the dedicated carrier cells that shares eNB with owner operator:
o Two PLMN IDIDs shall be broadcasted in SIB1 (owner PLMN + sharing
PLMN). Owner PLMN ID shall be the primary PLMN and sharing PLMN
ID shall be the secondary PLMN.
o Owner PLMN, that is, primary PLMN in SIB1, shall set to “reserved for
operator” to prevent provide services to owner PLMN’s subscribers in
sharing PLMN operator’s dedicated carrier.
The reason for including PLMN ID of owner PLMN in sharing PLMN carrier is to
enable SON related operation, for example, ANR, and packets forwarding issue in
the shared eNB.
This feature supports up to six operators dedicated carriers MOCN sharing
operation.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
To add additional PLMN ID broadcasted to the specific cell,
• Run CHG-ENBPLMN-INFO, and configure additional PLMN ID (= MCC +
MNC) to the unused PLMN_IDX.
• Run CHG-CELLPLMN-INFO, and set PLMN_USAGE of the newly specified
PLMN ID with the specific cell and the corresponding PLMN_IDX.
To deactivate specific PLMN ID:
• Run CHG-CELLPLMN-INFO and set PLMN_USAGE to 'no_use'.
Key Parameters
parameters.
PLMN_IDX The plmn index to be changed or retrieved. PLMN ID corresponding to the
selected plmnIdx is mapped to the PLMN ID which is retrieved/changed by
command RTRV/CHG-ENBPLMN-INFO with the same plmnIdx number.
MCC/MNC of the PLMN_IDX = 0 is representative PLMN ID of the system

operator, and cannot be changed using CHG-ENBPLMN-INFO.

Sector, up to 3 cells are supported.
PLMN_USAGE When cell is operated, determine whether to use the value of PLMN corresponding

Confidential
plmnIdx.
• use: the value of PLMN corresponding plmnIdx can be serviced.
• no_use: the value of PLMN corresponding plmnIdx not be serviced.
parameters.
MCC/MNC of the PLMN_IDX = 0 is representative PLMN ID of the system

operator, and cannot be changed using CHG-ENBPLMN-INFO.

Sector, up to 3 cells are supported.
plmnIdx.
Counters and KPIs

with this feature.
REFERENCE
[3] 3GPP TS23.251 Network Sharing; Architecture and functional description

Confidential
LTE-SW5002, Flexible Radio Resource

Configuration for RAN Sharing
INTRODUCTION
In RAN sharing deployment scenario, one radio spectrum can be shared by several
providers. How to share and use wireless resources among providers are important.
Samsung eNB provides the very flexible method for the provider sharing or
dividing and using wireless resources. This allows a variety of business models
including the integrated operation of the radio spectrum among providers, pricing
based on wholesale or usage of the wireless resources, and so on.
To share or divide wireless resources, Samsung eNB supports four resources
sharing models: Full Common Sharing, Strict Separation, Partial Common
Sharing, and Adaptive Sharing. The operator may configure resource partitioning
percentages among providers and accordingly the eNB controls the amount of
resources allocated by provider.
• The Full Common Sharing is a method for sharing radio resource in a first-
come-first serve form regardless of providers.
• Strict Separation is a method for allowing providers to partition wireless
resource and allocating certain portion of the resource only for a designated
provider.
• Partial Common Sharing is a method in a hybrid form of full common sharing
and strict separation as for part of the whole radio resource being used
regardless of providers and the other part being allocated as dedicated resource
to each provider.
• In Adaptive Sharing method, even the resources allocated as dedicated
resources may be allocated to other providers even though they are not used by
the corresponding provider.
The use of resource partition can be set based on a certain period and the peak
throughput of the UE is not restricted. The peak throughput of the UE is available
as much as permitted by air bandwidth. The radio resources may be shared up to
six providers.
BENEFIT
• This feature enables the business model where the operator can wholesale a
portion of radio resources to partner operator in common spectrum sharing.
• The operator can highly utilize radio resources between different PLMNs by
configuring radio resource sharing ratio among them.
• In addition to radio spectrum, the operator can share site, eNB equipment, and
backhaul network to reduce CAPEX and OPEX.

Confidential
DEPENDENCY
• Prerequisite Features : LTE-SW5001 Multiple PLMN support
• Others: A common carrier that is shared by multiple PLMNs. If Per-PLMN
CAC feature in LTE-SW5012 is enabled, this feature should be also enabled.
LIMITATION
• A common carrier is shared among up to six operators
• Radio sharing ratio can be set by the unit of 1 %
• From SLR 4.5, license dependent added.
• If eMTC is enabled, the PRBs used for eMTC is considered as common
portion in LTE.
• If in-band mode NB-IoT is enabled, the PRB for NB-IoT is excluded for per
PLMN PRB resource sharing in LTE. Per PLMN PRB sharing is not
supported due to less RB numbers for NB-IoT.
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-SW5012, Operator Specific Feature Activation
If Per-PLMN CAC feature in LTE-SW5012 is enabled, this feature should be also
enabled.
None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Radio Resource Sharing Models

Samsung eNB supports four kinds of radio resource sharing models as follow:
Full Common Sharing of Resource: Multiple operators share all radio resources.
The eNB allocates resources in the First-Come-First-Serve format according to the
request of the UE regardless of the classification of the operator. The operator

Confidential
enters the resource sharing ratio by PLMN as 0. In conclusion, 100 % of all the
resources are operated as common resources in the system.
Strict Separation of Resource: Partition and allocate all radio resources by
operator. Each operator may use it as much as designated portion, and even though
the resources are left because another operator has not used them, the resources
cannot be used. The sum of the resources allocated to the operator must be 100 %.
Partial Common Sharing of Resource: Share among operators by designating part
of resources as common resources. The operator automatically allocates the left
part of dedicated resources by PLMN after being allocated in the system. Each
operator additionally uses common resources other than the dedicated resource
allocated to him or her. The common resource is allocated to the UE based on the
first-come-first serve format regardless of classification of operators.
Adaptive Sharing of Resource: Just like the Partial Common Sharing of Resource
model, allocate dedicated resource to each operator. If all dedicated resources are
not used and are completely left, the resource holding operator allows other
operators to use them. The left dedicated resources after being allocated to each
operator is designated internally as common resources in the system and the
resources are allocated to the UE based on the first-come-first serve format
regardless of classification of operators.
Each operator (PLMN) can designate Minimum Dedicated Resource Reservation

(MinDRR) and Maximum Dedicated Resource Reservation (MaxDRR) values by
PLMN0_PORTION - PLMN5_PORTION, PLMN0_PORTION_MIN -
Confidential
PLMN5_PORTION_MIN and COMMON_SHARING_PORTION by (CHG-

NET-SHR) for LTE and EMTC_PLMN0_PORTION -
EMTC_PLMN5_PORTION, EMTC_PLMN0_PORTION_MIN -
EMTC_PLMN5_PORTION_MIN by (CHG-EMTCNET-SHR) for eMTC. The
resource portion for LTE and eMTC can be set independently. In the
aforementioned example (Adaptive Sharing of Resource), the MinDRR value of
Operator A is 5 % and the MaxDRR value is 35 %. In addition, in case of the
Partial Common Sharing of Resource, the MinDRR of Operator A is 40 % and the
MaxDRR is 40 %. For example, if the MinDRR and MaxDRR values of Operator
C are same, Operator C guarantees dedicated resources as much as the MaxDRR
value all the time and does not use any of the left dedicated resource for other
operators. Conversely, if the MinDRR and MaxDRR values of Operator C are
different, the resources not used by Operator C as much as MaxDRR-MinDRR
value can be allocated for other operators. At the time, the resources allocated to
other operators, if necessary, can be immediately withdrawn and used by Operator
C.
If there are the resources allocated and left as dedicated resources to each operator
(100% - (Sum of MaxDRRs)), the resources are allocated as common resources
internally in the system in the first-come-first-server format regardless of the
classification of operators.
Among the four resource-sharing models as explained above, three models
including Full Common Sharing, Partial Common Sharing, and Adaptive Sharing
can be independently applied by operator. For example, Operator A may apply the
Partial Common Sharing and at the same time Operator B may apply Adaptive
Sharing. However, the Strict Separation must be applied to all operators at the
same time, and at the time, the sum of MaxDDR must be 100 %. In such
configuration, a specific operator does not allocate any left dedicated resources to
any other operator and does not use the resources of any other operators even
though the resource is insufficient due to congestion.
The resource-sharing ratio configured by the operator is applied when each
scheduler allocates DL and UL resources or performs call admission control for
the UE and the bearer. For example, in the network operating the 20 MHz
bandwidth, Operator A can get the allocated resource as much as 100 PRB x T x
40 %, accept the UEs as many as 600UEs x 40 % per cell at the same time and
also the bearers as many as 1200 Bearers x 40 %.
PRB Resource Allocation and Method among PLMNs

The method for allocating and sharing resources among PLMNs in the eNB is as
follows. When eMTC is enabled, the PRBs used for eMTC is considered as
common PRB resource in legacy LTE scheduler. The PRB resource sharing per
PLMN applies to LTE only (not includes eMTC).

Confidential
1) TTresh is automatically changed depending on the result of resource allocation

of the previous time duration T between the MinDRR value and the MaxDRR
value according to the setting value by PLMN. If the reserved resources as many
as TTresh as the result of the resource allocation to the operator in the T zone was
insufficient, increase the TTresh value in the 2T zone and if the resources were
left, reduce TTresh as much. The TTresh value is not increased higher than the
MaxDRR value and is not reduced less than the MinDRR value. During T, for the
operator, the dedicated resource as much as TTresh is allocated, and the resource is
not allocated to any other operators even though it is not used. In the example, the
resource as much as 100%-TTresh (A)-TTresh (B) is used as common resources.
2) According to the result of the resource allocation of Operators A and B during
the T zone, each TTresh was changed in the 2T zone. But due to many resources
requested by each operator, the resource in the common resource area beyond
TTresh is used. The common resource is allocated in the first-come-first-serve
format regardless of classification of PLMNs.
3) Due to many resources requested by each of Operator A and B, TTresh
increased to MaxDRR and congestion occurred because all the resources in the
common resource area were used.
4) Because Operator A requests many resources, some of common resource is
used and Operator B did not use all dedicated resources because the requested
resources were reduced.
5) In the 5T zone, the TTresh value of Operator B was adjusted by reflecting the
result of resource allocation in the 4T zone. Operator B cannot use all the reserved
resources as TTresh, but Operator A additionally uses the resource as much as the
MaxDRR-TTresh of Operator B. Even though Operator A is in the congestion, the
resource reserved to Operator B that is not used cannot be allocated to Operator A.
6) Due to the increased request of Operator B for resources, the resource reserved
as TTresh becomes insufficient.
7) According to the result of the resource allocation in the 6T zone, the TTresh of
Operator B is increased to MaxDRR to secure dedicated resources that can be used
by Operator B. At the time, Operator A still requests many resources, but the
available resources are reduced.
As such, resource allocation and shared algorithm are equally applied for DL and
UL resources.

Confidential
UE Connection and Bearer Resource Allocation and Sharing Method among PLMNs
When the cell is at the normal state, the RRC Connection and Bearer resources are
allocated to the UE regardless of classification of operators in the first-come-first-
serve format. If the resources are insufficient due to the increased load, the
operator who uses fewer resources than the given quota gets additional resources
but the one who uses more than the given quota cannot get additional resources.
To provide resources additionally for an operator at the congestion, the resources
must be withdrawn from the operator who uses more resources than the given
quota.
In case of the quota per operator means, the operator uses the Maximum Dedicated
Resource Reservation (MaxDRR) and Minimum Dedicated Resource Reservation
(MinDRR) values set by PLMN and the meaning is as same as defined in the
Radio Resource Sharing model.
The fewer resources-using operator is defined as the operator who uses fewer
resources than the given quota and the resource-overusing operator as the operator
who uses more resources than the given quota. If a subscriber of the fewer
resources-using operator requests a call at the congestion, the eNB pre-empts the
subscriber of the resource-overusing operator and accepts the call in a method for
providing the secured resources for the subscriber of the fewer resources-using
operator. If the subscriber of the resource-overusing operator requests a call at the
congestion, the eNB accepts the call in a method for pre-empting the UE which
belongs to the same operator.
When pre-emption is applied among PLMNs, the two following options are
provided and the operator may select either option:
• Overusing PLMN First (option 1): Select candidate UEs first from resource-
overusing operators, that is, UE from PLMN that has the most overused
resources. And then choose the UE with the bearer with lowest ARP of that
selected PLMN. If there are still multi candidates exist, then randomly select
the pre-emption candidate.
• Lowest ARP First (option 2): Select candidate UEs who has the bearer with
lowest ARP first, and then select the UEs from PLMN that has the most
overused resources. If there are still multiple candidates, then randomly select
the pre-emption candidate.

Confidential
Considerations in QoS
If the congestion occurs, the contention for the resource occurs in the resource
allocated to a specific operator. QoS-based CAC determines the supportability of
QoS based on the MaxDRR resource allocated by PLMN. For this, the operator
may set maximum number of GBR bearers, and maximum PRB usage of GBR
bearers by PLMN. At the time, the number of GBR bearers and maximum PRB
usage available by GBR bearer must be set not to exceed the MaxDDR of the
provider. Otherwise, at the congestion, the QoS of GBR bearer may be poorer.
SYSTEM OPERATION
How to Activate
Preconditions
• License key is required to activate this feature.
• LTE-SW5001 Multiple PLMN feature must be supported as a precondition.
• Run CHG-ENBPLMN-INFO and CHG-CELLPLMN-INFO to configure

Confidential
PLMN IDs to be used in a specific eNB.

• Multiple PLMNs can be configured for the carrier to be shared in a MOCN
cell.
• Run CHG-CELL-CAC to enable “ADAPTIVE_SHARING_USAGE” and to
select “RS_PREMPTION_OPTION”.
• Run CHG-NET-SHR to configure Minimum and Maximum Resource Portion.
• Run CHG-NET-SHR to remove Minimum and Maximum Resource Portion.
• Run CHG-CELL-CAC to disable “ADAPTIVE_SHARING_USAGE”.
• Run CHG-RSHR-PLMN4G and CHG-CELLPLMN-INFO to remove PLMNs
except a primary PLMN.
Key Parameters
parameters.
PLMN_IDX This parameter is the Public Land Mobile Network (PLMN) index. The PLMN ID
corresponding to the selected PLMN_IDX is mapped to the PLMN ID which is
retrieved/changed by command RTRV/CHG-ENBPLMN-INFO with the same
PLMN_IDX number. A PLMN is identified by the Mobile Country Code (MCC)
and the Mobile Network Code (MNC).
PLMN_USAGE When cell is operated, determine whether to use the value of PLMN
corresponding PLMN index.
• use: the value of PLMN corresponding PLMN index can be serviced.
• no_use: the value of PLMN corresponding PLMN index not be serviced.

ADAPTIVE_SHARING_USA Whether to use Adaptive RAN sharing
GE • no_use: Adaptive RAN sharing is not used.
• use: Adaptive RAN sharing is used.
RS_PREMPTION_OPTION The policy of RAN sharing pre-emption.
• overUsingPLMNfirst: For a RAN sharing, PLMN is selected based on

Confidential
overusing PLMN. Then PLMN is selected based on the lowest ARP.
• lowestARPfirst: For a RAN sharing, PLMN is selected based on the lowest
ARP. Then PLMN is selected based on overusing PLMN.
parameters.
Parameter Descriptions of CHG-ENBPLMN-INFO/RTRV-ENBPLMN-INFO
• For PLMN_ID = 0, MCC and MNC should be fixed to primary PLMN.
PLMN_IDX number. A PLMN is identified by the Mobile Country Code (MCC)
and the Mobile Network Code (MNC).
MCC Mobile Country Code (MCC) that comprises Public Land Mobile Network
(PLMN). MCC of PLMN_IDX = 0 cannot be changed and used for the
representative PLMN, which is included in the Global eNB ID.
MNC Mobile Network Code (MNC) that comprises Public Land Mobile Network
(PLMN). MNC of PLMN_IDX = 0 cannot be changed and used for the
representative PLMN, which is included in the Global eNB ID.
OP_ID This parameter is an operator index which share resources in this system.
Parameter Descriptions of CHG-NET-SHR/RTRV-NET-SHR

PLMN0_PORTION to This parameter is the maximum portion of PLMN0 to PLMN5.
PLMN5_PORTIN
PLMN0_PORTION_MIN to This parameter is the minimum portion of PLMN0 to PLMN5.
PLMN5_PORTION_MIN
COMMON_SHARING_POR This parameter is the maximum portion of common
TION
• PLMN0_PORTION + PLMN1_PORTION + PLMN2_PORTION +

PLMN3_PORTION + PLMN4_PORTION + PLMN5_PORTION +
COMMON_SHARING_PORTION = 100
• PLMN0_PORTION_MIN <= PLMN0_PORTION,
PLMN1_PORTION_MIN <= PLMN1_PORTION,
PLMN5_PORTION_MIN <= PLMN5_PORTION.
Parameter Descriptions of CHG-NBNET-SHR/RTRV-NBNET-SHR

Confidential
CELL_NUM This parameter is the NB-IoT cell number to identify each cell. This value
must not exceed the maximum number of cells supported by the system.
PLMN0_PORTION~PLMN5_PO This parameter is maximum portion of PLMN0 ~ PLMN5 in NB-IoT Cell.
RTIN
PLMN0_PORTION_MIN~PLMN This parameter is minimum portion of PLMN0 ~ PLMN5 in NB-IoT Cell.
5_PORTION_MIN
COMMON_SHARING_PORTIO This parameter is maximum portion of common resource in NB-IoT Cell.
N
Similar DRC holds for NB-IoT network sharing portion.

Parameter Descriptions of CHG-EMTCNET-SHR/RTRV-EMTCNET-SHR
EMTC_PLMN0_PORTION~EMT This parameter is maximum portion of PLMN0 ~ PLMN5 in eMTC cell.
C_PLMN5_PORTIN
EMTC_PLMN0_PORTION_MIN This parameter is minimum portion of PLMN0 ~ PLMN5 in eMTC cell.
~EMTC_PLMN5_PORTION_MI
N
EMTC_COMMON_SHARING_P This parameter is maximum portion of common resource in eMTC cell.
ORTION
Similar DRC holds for eMTC network sharing portion.
Counters and KPIs

PRB Usage PrbDLAvg The average use rate for PRBs used for each QCI to transmit
DTCH traffic for the downlink during the collection interval.
PrbULAvg The average use rate for PRBs used for each QCI to transmit
DTCH traffic for the uplink during the collection interval.
REFERENCE
[1] 3GPP TS23.251, Network Sharing; Architecture and functional description
[2] 3GPP TS22.951, Service aspects and requirements for network sharing

Confidential
LTE-SW5004, Frequency Relocation Handover

INTRODUCTION
In shared network, operators would want to steer their own subscribers to specific
frequency bands. So, the operators need a method to relocate their own subscribers
to preferred carrier frequencies when a mobility event occurs.
For this requirement, Samsung supports that operators can pre-configure their
specific carrier preference per E-UTRA and inter-RAT (UTRA, GERAN or
CDMA2000 HRPD/1xRTT) carrier frequencies, that is, PLMN specific carrier
preference.
eNB considers the pre-configured carrier preference per UE serving PLMN in
following ways:
• When configuring a UE measurement objects for intra-LTE or inter-RAT
handover.
• When selecting target carrier frequency for redirection, cell change order or
CSFB.
• When extracting carrier frequencies for SPID based dedicated priority
signaling.
• When selecting candidate carrier frequencies for intra-LTE or intra-RAT load
balancing.
• When extracting carrier frequencies for idle UE distribution.
BENEFIT
Operators can steer their own subscribers to specific target carrier frequencies.
DEPENDENCY
E-UTRAN (LTE)
• Others
The related inter-frequency, inter-RAT mobility, and load sharing feature
should be enabled.
LIMITATION
None
SYSTEM IMPACT

Confidential
FEATURE DESCRIPTION
For frequency relocation considering PLMN specific carrier preference, each
operator which shares an eNB should pre-configure their own preference per
carrier frequencies for all available RATs, for example, E-UTRA, UTRA, GERAN
or CDMA2000 HRPD/1xRTT.
PLMN specific carrier preference defines as follows for E-UTRA or inter-RAT
(UTRA, GERAN or CDMA2000 HRPD/1xRTT) carrier frequencies.
The carrier frequency preference of PLMN0~PLMN5 can be configured by
PREFERENCE0~PREFERENCE5 by CHG-EUTRA-FA, CHG-UTRA-FA, CHG-
GERAN-FA, CHG-C1XRTT-FREQ and CHG-HRPD-FREQ respectively.
Carrier Preference for E-UTRA frequencies per PLMN

• Preferred (preferred_prefer): Higher priority frequency and used for all inter-
frequency mobility cases of the PLMN subscribers.
o This means that the operator allows and prefers its subscribers having this
preference to move to E-UTRA frequencies than others.
o Preferred E-UTRA frequencies are always configured as measurement
object for inter-frequency mobility and mapped to event reporting (A3, A4
or A5) per each frequency.
o Also, preferred E-UTRA frequencies are included in additional
measurement configuration for intra-LTE load balancing.
• Allowed (allowed_prefer): Lower priority frequency and used only for the
PLMN subscribers load based inter-frequency handover/redirection due to
load balancing
o This means that the operator does not want its subscribers to move to E-
UTRA frequencies having this preference, if not necessary.
o Allowed E-UTRA frequencies are only included when additional
measurement configuration for intra-LTE load balancing.
• Not allowed (not_allowed_prefer): Forbidden frequency and never used for the
PLMN subscribers.
o This means that the operator does not allow its subscribers to move to E-
UTRA carriers having this preference in any case.
o Not allowed E-UTRA frequencies are never used for measurement
configuration and any mobility case of the PLMN subscribers.
Carrier Preference for Inter-RAT (UTRA, GERAN or CDMA2000 HRPD/1xRTT)

Frequencies per PLMN
• Preferred (preferred_prefer): Higher priority frequency and used for all inter-
RAT mobility cases of the PLMN subscribers.
o This means that the operator allows and prefers its subscribers having this
preference to move to inter-RAT frequencies than others.

Confidential
o Preferred inter-RAT frequencies are always configured as measurement

object for inter-RAT mobility and mapped to event reporting (B1 or B2)
per each frequency.
o Also, preferred inter-RAT frequencies are included in additional
measurement configuration for inter-RAT load balancing.
• Allowed (allowed_prefer): not defined for inter-RAT frequencies (if this type
is set, eNB regards this same as to preferred)
• Not allowed (not_allowed_prefer): Forbidden frequency and never used for the
PLMN subscribers.
o This means that the operator does not allow its subscribers to move to
inter-RAT carriers having this preference, in any case.
o Not allowed inter-RAT frequencies are never used for the measurement
configuration and any mobility case of the PLMN subscribers.
PLMN specific carrier preference is used by eNB in the following ways:
1 When configuring an UE measurement objects for intra-LTE or inter-RAT
handover, the preferred frequencies of the UE serving PLMN are only
configured.
o Serving frequency is always configured regardless of PLMN specific
carrier preference for intra-frequency handover.
o If a preferred frequency corresponds to a carrier frequency of Forbidden
RAT which was indicated UE Handover Restriction List, the frequency is
not configured as measurement objects.
2 When non-handover mobility event occurs, such as inter-frequency or inter-
RAT redirection, cell change order to GERAN or CSFB, eNB selects target
carrier frequency among the preferred frequencies of the UE serving PLMN.
o In CSFB with registered LAI case, eNB selects frequencies corresponding
to the registered LA if available.
not selected.
3 When releasing a call which has SPID and if SPID based dedicated priorities
per carrier frequency is configured, eNB extracts SPID based dedicated
priorities per the preferred frequencies of the UE serving PLMN and includes
that in RRC Connection Release message for SPID based dedicated priority
signaling.
ruled out from the list.
4 When serving cell load status is changed to heavily loaded situation and a UE
is selected to a candidate user for intra-LTE or inter-RAT load balancing,
eNB selects candidate carrier frequencies among the preferred or allowed
frequencies of the UE serving PLMN.
o If a preferred or allowed frequency corresponds to a carrier frequency of

Confidential
Forbidden RAT which was indicated UE Handover Restriction List, the

frequency is not selected.
5 When releasing a call and if idle UE distribution feature is enabled, eNB
extracts load based dedicated priorities per the preferred or allowed
frequencies of the UE serving PLMN and includes that in RRC Connection
Release message for idle UE distribution.
o If a preferred or allowed frequency corresponds to a carrier frequency of
Forbidden RAT which was indicated UE Handover Restriction List, the
frequency is ruled out from the list.
The following block diagram shows the operation in eNB on how to select the
candidate frequency for mobility and load balancing.
SYSTEM OPERATION
How to Activate
Preconditions
• Run RTRV-CELLPLMN-INFO to check CELL_NUM value that must not
• Run CHG-CELLPLMN-INFO and set PLMN_USAGE to use.

Confidential
• Run CHG-CELLPLMN-INFO and set PLMN_USAGE to no_use.
Key Parameters
parameters.
Parameter Descriptions of CHG-ENBPLMN-INFO/RTRV-ENBPLMN-INFO
PLMN_IDX The PLMN index to be changed or retrieved. PLMN ID corresponding to
the selected plmnIdx is mapped to the PLMN ID which is
retrieved/changed by command RTRV/CHG-ENBPLMN-INFO with the
same plmnIdx number.
MCC Mobile Country Code (MCC) that comprises Public Land Mobile Network
(PLMN).
MNC Mobile Network Code (MNC) that comprises Public Land Mobile Network
(PLMN).

FA/Sector. For example, if the maximum capacity provided to the carrier
per system is 1 FA/3 Sector, up to three cells are supported.
PLMN_IDX The PLMN index to be changed or retrieved. PLMN ID corresponding to
the selected plmnIdx is mapped to the PLMN ID which is
retrieved/changed by command RTRV/CHG-ENBPLMN-INFO with the
same plmnIdx number.
PLMN_USAGE When cell is operated, determine whether to use the value of PLMN
corresponding plmnIdx.
parameters.
Parameter Descriptions of CHG-C1XRTT-FREQ/RTRV-C1XRTT-FREQ
CARRIER_INDEX CDMA2000 1xRTT carrier index. Up to eight carriers can be assigned per
cell.
STATUS Whether the CDMA2000 1xRTT carrier is valid.

Confidential
• EQUIP: Valid.
PREFERENCE0 Preference of PLMN #0 for FA.
Parameter Descriptions of CHG-HRPD-FREQ/RTRV-HRPD-FREQ

CARRIER_INDEX CDMA2000 HRPD carrier index. Up to eight carriers can be assigned per
cell.
• EQUIP: Valid.

FA_INDEX This parameter is the EUTRA frequency index. This value must not
exceed the maximum number of FA supported by the system.
STATUS This parameter indicates whether to use EUTRA FA and it can be used
only when it is set to EQUIP.
Parameter Descriptions of CHG-UTRA-FA/RTRV-UTRA-FA


Confidential
FA_INDEX This parameter specifies the frequency index to change the UTRAN
carrier information.
Maximum 6 FAs can be set for each cell.
STATUS This parameter indicates whether to use the UTRAN carrier information.
• N_EQUIP: Does not use the UTRAN carrier information.
• EQUIP: Uses the UTRAN carrier information.
Parameter Descriptions of CHG-GERAN-FA/RTRV-GERAN-FA

FA_INDEX GERAN frequency index. Up to 6 FAs can be assigned per cell.
STATUS Whether the GERAN FA object is valid.
• EQUIP: Valid.
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
LTE-SW5012, Operator Specific Feature

Activation
INTRODUCTION
Samsung provides a set of features which can be activated and configured per
PLMN and thus, with this feature, each operator can activate and configure its
desired features independently from other operators.
BENEFIT
The operator can flexibly configure and activate the feature they are interested.
DEPENDENCY
• Prerequisite Features: LTE-SW5001 Multiple PLMN support and LTE-
SW5002 Flexible Configuration for Radio Resources Sharing. To implement
per PLMN call admission control (CAC), LTE-SW5002 should be enabled.
LIMITATION
SLR4.5 (Per Carrier based Neighbor Relation Addition) is out of license control.
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-SW5002, Flexible Configuration for Radio
Resources Sharing
If per PLMN Call Admission Control (CAC) is required that included in this
feature, then LTE-SW5002 Flexible Radio Resource Configuration for RAN
Sharing should also be enabled to include the per PLMN resource sharing ratio.
None
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
In RAN sharing operation, different operator may have different requirements on
enable/disable some feature and configure some parameters that independently
with other shared operators. This feature meets operator’s requirements and
provides more flexibility in RAN sharing operation. The following features are
provided:
UE Inactivity Timer Configuration per PLMN

UE inactivity timer is used to control release of RRC connection after a certain
period. Different operator may have different requirement on control of their UE’s
idle mode settings. UE inactivity timer has impact on UE battery consuming.
Through per PLMN configuration of this parameter, operators can flexible control
their subscriber’s UE battery consumption.
In this feature, Samsung eNB supports configuration of user inactivity timer
regarding signaling and data respectively per PLMN basis as follows:
• Signaling inactivity timer per PLMN by
INTERNAL_SIGNALING_INACTIVITY_TIMER (CHG-
PLMNSIGTIMER-INFO).
The period during which there is no signaling message exchange between the
eNB and the UE.
• Data inactivity timer per QCI per PLMN by
INTERNAL_USER_INACTIVITY (CHG-INACT-TIMER).
The period during which there is no data traffic.
Per QCI bearer basis user inactivity timer is supported.
• Up to six configurations of PLMN UE inactivity timer are supported.
UE DRX configuration per PLMN

Similar to UE inactivity timer, DRX also has impact to UE’s battery life. The
operator may also request to be capable of configuring DRX of UE independently
to other partner operators. For DRX feature description, refer to LTE-ME3402
Active DRX. In current Samsung’s solution, the eNB support to configure DRX
value per QCI basis. DRX related parameters can be configured by CHG-DRX-
INF
By this feature, standard QCIs (1 - 9) and operator specific QCIs (128 - 254) can
be enabled/disabled per PLMN basis. Independently DRX configuration per QCI
per PLMN is implemented also in SLR3.1, the associated QCIs including standard
QCIs (1 - 9) and operator specific QCIs (128 - 254). The partner operator can
flexible configure their subscriber’s DRX to control the battery life of UE.
Table below gives an example of DRX configuration per QCI per PLMN of
standard QCIs (1 - 9). The DRXxy can be configured independently of QCI and
PLMN. The specified configurable DRXxy values refer to LTE-ME3402, Active
DRX description. Up to six operators are supported in this PKG release.

Confidential
PLMN QCI (1) QCI (2) … QCI (9)

PLMN A DRXA1 DRXA2 … DRXA9
PLMN B DRXB1 DRXB1 … DRXB9
… … … … …
PLMN F DRXF1 DRXF2 … DRXF9
Admission Control Parameters Configuration per PLMN

Call admission control is used to efficiently control the limited resource utilization,
to guarantee the QoS of service and to prevent congestion and overloading of eNB.
Samsung system provide capacity based CAC and QoS based CAC respectively to
satisfy the above requirements, refer to LTE-SW4101, Capacity based Call
Admission Control and LTE-SW4102, QoS based Call Admission Control.
In RAN sharing scenario, partner operators have requirements on independently
control the CAC parameters per PLMN basis to satisfy operator specific
requirement on CAC, per PLMN CAC can be enabled/disabled by
ADAPTIVE_SHARING_USAGE (CHG-CELL-CAC). For an instance, operator A
may consider user experience has higher priority than the user numbers while
operator B may consider user number is prior to user experience. To satisfy the
various requirement of different partner operator, the CAC parameters can be
configured per operator basis in this PKG release (SLR3.1).
Table below lists the parameters that can be configured by per operator.
The configured parameter should not exceed the resource ratio that assigned to
each partner operator.
CAC Scheme CAC parameters per PLMN configurable

Capacity Based Max UE umber per cell per PLMN based on each PLMN’s resource sharing portion.
Refer to LTE-SW5002 for resource sharing portion configurations.
Max Radio Bearer number per cell per PLMN based on each PLMN’s resource sharing
portion. Refer to LTE-SW5002 for resource sharing portion configurations.
Max Bearer numbers per QCI per cell per PLMN based on each PLMN’s resource
sharing portion. Refer to LTE-SW5002 for resource sharing portion configurations.
Air QoS Based Amount of PRBs that can be allocated to GBR bearers per PLMN based on each
PLMN’s resource sharing portion. Refer to LTE-SW5002 for resource sharing portion
configurations. Per PLMN QoS based CAC does not apply to NB-IoT and eMTC.
Others Enable/disable CAC and pre-emption functionality per PLMN by
CELL_COUNT_CAC_USAGE, DRB_COUNT_CAC_USAGE, QOS_CAC_OPTION,
PREEMPTION_FLAG (CHG-CELLPLMN-CAC), and PLMN_CELL_COUNT_CAC_USAGE
(CHG-NBCELL-CAC).
Per-PLMN thresholds for CAC by CALL_CAC_THRESH_FOR_NORMAL,
CALL_CAC_THRESH_FOR_EMER_HO, DRB_CAC_THRESH_FOR_NORMAL,
DRB_CAC_THRESH_FOR_EMER_HO (CHG-CELLPLMN-CAC), and
CALL_CAC_THRESH_FOR_NORMAL/CALL_CAC_THRESH_FOR_MO_EX_DATA (CHG-
NBCELLPLMN-CAC).
Max UE-AMBR configuration per PLMN

UE Aggregate Max Bit Rate (UE-AMBR) is used to control the non-GBR service
Confidential
throughput provided to the UE. This data transmitted to eNB initially by core
network (MME). In RAN sharing scenario, due to some business need, the UE-
AMBR value may have to be overridden by operator to control the UE throughput
provided to partner operator’s subscriber.
This feature provides a scheme to allow configuring maximum UE AMBR value
(UL and DL) of each partner operator by UL_UE_AMBR and DL_UE_AMBR
(CHG-UEAMBR-CTRL). An associated flag that override the MME assigned UE-
AMBR function is also provided and controlled by UE_AMBR_OVERRIDE_FLAG
(CHG-UEAMBR-CTRL). The counter S1APUEAmbrOverride and
X2APUEAmbrOverride is pegged if UE-AMBR override happens. The following
logic is performed to enable the feature:
if (flag=FALSE)
accept the requested UE AMBR
if (flag=TRUE)
if (requested AMBR <= configured AMBR)
accept the UE AMBR requested
if (requested AMBR > configured AMBR)
override CN assigned AMBR with configured value
The above rule is checked in the following cases:

• Initial bearer setup phase, for example, ,
o INITIAL CONTEXT SETUP REQUEST
o E-RAB SETUP REQEUST.
• Bearer modification procedure, for example, ,
o UE CONTEXT MODIFICATION REQUEST
o RAB MODIFY REQUEST
o E-RAB RELEASE COMMAND
• Handover procedure,
o HANDOVER REQUEST
o PATH SWITCH REQUEST ACKNOWLEDGE
Statistics related:
When the requested UE-AMBR is larger than the configured value per partner
operator, a related counter is generated.
X2 Setup Configuration per Primary PLMN of Neighbor eNBs

This feature supports per primary PLMN basis configuration whether to allow
automatic X2 setup by USE_NBR_NO_X2 (CHG-PLMNANR-ENB).
When eNB needs to setup X2 connection with new detected eNB, it checks X2
setup possibility associated with the primary PLMN Id of the eNB. If disabled for
the PLMN Id, eNB does not initiate X2 setup.
Per Carrier based Neighbor Relation Addition

This feature supports per carrier based automatic NR addition, that is,
Confidential
enable/disable per carrier basis ANR by ANR_ALLOW (CHG-EUTRA-FA),

ANR_TARGET_MCC, and ANR_TARGET_MNC (CHG-PLMNANR-ENB). When
new neighbor cell is detected for a disabled carrier, eNB ignores the new detected
cell. The eNB performs automatic NR addition, only when detecting new cell of an
enabled carrier.
QCI Enable/Disable per PLMN

In LTE, QoS configurations of UE bearer (QCI) are mainly under control of MME
and HSS/PCRF. However, in MOCN RAN sharing scenario, the host operator may
want to control the bearers QCI provided to partner operators and disable some
QCI bearer that the partner operator does not used due to some business
consideration.
This feature provides a scheme to flexible enable/disable of specific QCI bearer
per PLMN basis by USED_FLAG (CHG-PLMNQCI-FUNC) of each QCI. The
enabled/disabled QCIs range is 0 - 255 including standardized QCIs (1 - 9) and
operator specific QCIs (128 - 254). Furthermore, the configuration supports up to
6 operators.
The eNB checks the bearer’s QCI parameter that requested to setup in the
following procedures, if the disabled QCI is requested then reject the request.
• Initial Context Setup
• E-RAB Setup
• E-RAB Modify
• Handover Resource Allocation/Handover Preparation (S1 and X2 respectively)
The statistic related with the rejection is also provided. The PLMN0QCIReject -
PLMN5QCIReject is pegged when rejection happens.
SYSTEM OPERATION
How to Activate
Preconditions
• License key is required to activate this feature.
• Run CHG-ENBPLMN-INFO and CHG-CELLPLMN-INFO to configure
PLMN IDs to be used in a specific eNB.
• Multiple PLMNs can be configured for the carrier to be shared in a MOCN

Confidential
cell.
• Run CHG-PLMNQCI-FUNC to configure QCI function utilization per PLMN.
• Run CHG-PLMNSIGTIMER-INFO to configure signaling inactivity time.
• Run CHG-INACT_TIMER to configure data inactivity time per QCI.
• Run CHG-UEAMBR-CTRL to configure data rate per PLMN for UE-AMBR
feature.
• Run CHG-CELLPLMN-CAC/CHG-QCAC-PARA/CHG-QCACQ-PARA to
configure threshold or data rate per PLMN for Call Admission Control (CAC)
feature.
• Run CHG-PLMNANR-ENB to enable automatic X2 interface connection.
• Run CHG-EUTRA-FA to enable automatic neighbor relation configuration.
• Run CHG-DRX-INF to configure DRX feature including time used.
• Run CHG-PLMNQCI-FUNC to disable QCI function utilization per PLMN.
• Run CHG-PLMNSIGTIMER-INFO to control signaling inactivity time.
• Run CHG-INACT_TIMER to control data inactivity time per QCI.
• Run CHG-UEAMBR-CTRL to disable UE-AMBR feature controlling data rate
per PLMN.
• Run CHG-CELLPLMN-CAC/CHG-QCAC-PARA/CHG-QCACQ-PARA to
disable Call Admission Control (CAC) feature.
• Run CHG-PLMNANR-ENB to disable automatic X2 interface connection.
• Run CHG-EUTRA-FA to disable automatic neighbor relation configuration.
• Run CHG-DRX-INF to disable DRX feature including time used.
Key Parameters
parameters.
Parameter Descriptions of CHG-PLMNQCI-FUNC/RTRV-PLMNQCI-FUNC
PLMN_IDX number. A PLMN is identified by the Mobile Country Code(MCC) and

Confidential
the Mobile Network Code(MNC).
characteristics.
USED_FLAG whether to use QCI per PLMN
• 0: The corresponding QCI is rejected for UE serving PLMN. If eNB receives a
request to setup this not-allowed QCI, it will reject to setup the bearer and count
the ERAB_QCI_REJECT_PLMN statistics per cell/QCI, according to the UE
serving PLMN.
• 1: The corresponding QCI is allowed for UE serving PLMN.

PLMNSIGTIMER-INFO
PLMN_IDX number. A PLMN is identified by the Mobile Country Code (MCC) and
the Mobile Network Code (MNC).
INTERNAL_SIGNALIN The signaling inactivity time triggered when eNB has no signaling message for
G_INACTIVITY_TIMER certain period defined by this parameter. This parameter can be set for each PLMN.

characteristics.
PLMN_IDX number. A PLMN is identified by the MCC and the MNC.
INTERNAL_USER_INA This parameter is the User inactivity timer value per QCI. A different User inactivity
CTIVITY timer value can be set for each QCI by executing this command. As User inactivity
changing it. It is a timer value that operates in seconds. If the operating User
inactivity timer value is 65535, a call may not be detached for 65535 seconds. This
may cause serious problems for the battery usage of the UE. It is recommended to
use a value less than 30 seconds.
Parameter Descriptions of CHG-UEAMBR-CTRL/RTRV-UEAMBR-CTRL


Confidential
UE_AMBR_OVERRIDE Flag to limit to the UL/DL UE-AMBR value based on PLMN-specific configuration of
_FLAG the eNB by the UL_UE_AMBR/DL_UE_AMBR value.
• 0: UL_UE_AMBR/DL_UE_AMBR value per-PLMN limitation function is not used.
• 1: If UL or DL UE-AMBR value received from MME or eNB exceed configured
UL_UE_AMBR or DL_UE_AMBR value, it is limited to the ulUeAmbr or
DL_UE_AMBR value and the number of limit violation is counted at the
UEAmbrOverride statistics per cell/per UE serving PLMN.
UL_UE_AMBR UL UE-AMBR value to override for the configured PLMN (unit: bps).
DL_UE_AMBR DL UE-AMBR value to override for the configured PLMN (unit: bps).
Parameter Descriptions of CHG-CELLPLMN-CAC/RTRV-CELLPLMN-CAC

CELL_COUNT_CAC_U This parameter indicates whether to execute the call count-based CAC function,
SAGE which is one of the capacity-based Call Admission Control (CAC) functions per cell.
• no_use: The capacity-based CAC function per cell is not performed.
• use: The capacity-based CAC function per cell is performed.
CALL_CAC_THRESH_ The percentage of the allowable calls to the total normal calls or handover calls
FOR_NORMAL without emergency priority. When a normal call or handover call without emergency
priority is requested, if the number of connected calls exceeds MAX_CALL_COUNT
* CALL_CAC_THRESH_FOR_NORMAL (CELL) *
CALL_CAC_THRESH_FOR_NORMAL (PLMN) * the available ratio of the relevant
PLMN designated for NET-SHR, the Capacity-based CAC Fail is generated.
CALL_CAC_THRESH_ The percentage of the allowable calls to the total emergency calls or handover calls
FOR_EMER_HO with emergency priority. When an emergency call or handover call with emergency
priority is requested, if the number of connected calls exceeds MAX_CALL_COUNT
* CALL_CAC_THRESH_FOR_EMER (CELL) *
CALL_CAC_THRESH_FOR_EMER_HO (PLMN) * the available ratio of the relevant
DRB_COUNT_CAC_U This parameter indicates whether to execute the E-UTRAN Radio Access Bearer (E-
SAGE RAB)-based CAC function, which is one of the capacity-based Call Admission
Control (CAC) functions per cell.
• no_use: The E-RAB count-based CAC function per cell is not executed.
• use: The E-RAB count-based CAC function per cell is executed.
DRB_CAC_THRESH_F The percentage of the allowable bearers to the total normal calls. When a normal
OR_NORMAL call of bearer is requested, if the number of connected bearers exceeds
MAX_DRB_COUNT * DRB_CAC_THRESH_FOR_NORMAL (CELL) *
DRB_CAC_THRESH_FOR_NORMAL (PLMN) * the available ratio of the relevant
DRB_CAC_THRESH_F The percentage of the allowable bearers to the total emergency calls or handover
OR_EMER_HO calls. When an emergency call or handover call of bearer is requested, if the number
of connected bearers exceeds MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_EMER_HO (CELL) *
DRB_CAC_THRESH_FOR_EMER_HO (PLMN) * the available ratio of the relevant

Confidential
QOS_CAC_OPTION The policy of the Quality of Service (QoS) based Call Admission Control (CAC) at
the cell level.
• no_use: The QoS based CAC function at the cell level is not used.
• use: The QoS-based CAC function per cell is used.
QOS_POLICY_OPTIO The policy used when executing the Quality of Service (QoS)-based Call Admission
N Control (CAC) function per cell.
• option0: For a GBR bearer newly requested, the PRB usage is calculated based
on the resource type (GBR or non-GBR) of the QCI. Then CAC is executed based
on the calculated PRB usage. Non-GBRs are always allowed.
• option1: For a GBR bearer newly requested, the PRB usage is calculated based
on the priority of the QCI. Then CAC is executed based on the calculated PRB
usage. Non-GBRs are always allowed.
PREEMPTION_FLAG This parameter indicates whether to use pre-emption at the cell level.
• no_use: The Pre-emption function per cell is disabled.
• use: The Pre-emption function per cell is enabled.
QCI_DRB_CAC_USAG This parameter indicates whether to use QCI DRB CAC at the cell Level.
E • no_use: no use
• use: use
Parameter Descriptions of CHG-PLMNANR-ENB/RTRV-PLMNANR-ENB

TARGET_PLMN_IDX This parameter is the PLMN index about target eNB operating ANR function.
The PLMN ID about PLMN index can be changed by parameter of
ANR_TARGET_MCC and ANR_TARGET_MNC.
STATUS This parameter is used to determine whether the target PLMN is used or not.
• N_EQUIP: it is not referred to the PLMN information.
• EQUIP: control the ANR operation in reference to the PLMN information.
ANR_TARGET_MCC This parameter is the MCC for defining Primary PLMN of Neighbor eNB. It is used to
determine the ANR operation per-PLMN about the eNB including the PLMN ID in
Global eNB ID.
ANR_TARGET_MNC This parameter is the MNC for defining Primary PLMN of Neighbor eNB. It is used to
determine the ANR operation per-PLMN about the eNB including the PLMN ID in
Global eNB ID.
USE_NBR_NO_X2 This parameter is used to allow/block X2 connection to the neighbor eNB with
primary PLMN ID which is configured in this PLD when the NBR eNB is added by
ANR function. It is noted that the default operation for the unregistered PLMN (if the
PLMN ID is not defined in this PLD or PLMN status is N_EQUIP) is to allow to make
X2 connections.
• no_use: If the useNBRNoX2 is no_use for the registered target PLMN ID, X2
connection setup is allowed. That is, primary PLMN of the newly registered
neighbor eNB added by ANR function is matched to the target PLMN ID, eNB will
set NO_X2 = false for this newly added eNB to allow to setup X2 connection. Also,
if the eNB receives X2 Setup Request from the unknown eNB, it will add this eNB
as the new neighbor eNB and accept to make X2 connection by setting NO_X2 =
False.
• use: If the useNBRNoX2 is use for the registered target PLMN ID, X2 connection
setup is blocked. That is, primary PLMN of the newly registered neighbor eNB
added by ANR function is matched to the target PLMN ID, eNB will set NO_X2 =
True for this newly added eNB to block to setup X2 connection. Also, if the eNB
receives X2 Setup Request from the unknown eNB, it will add this eNB as the new
neighbor eNB and reject X2 connection by setting NO_X2 = True.

Confidential

FA_INDEX This parameter is the EUTRA frequency index. This value must not exceed the
maximum number of FA supported by the system.
ANR_ALLOW This parameter is the minimum number of valid neighbors for a carrier. This
parameter purpose is to prevent deleting too many neighbors for a specific carrier in
neighbor relation optimizing operation and to support normal operation of the SON
Load Balancing function.
Parameter Descriptions of CHG-DRX-INF/RTRV-DRX-INF

operator optionally. [Related Specifications] 3GPP TS 23.203 [Table 6.1.7]
Standardized QoS characteristics.
DRX_CONFIG_SETUP This parameter is the flag to determine whether to use the CDRX, and which CDRX
mode to use. It has three value options. This parameter is the applied per UE. UE
can know the DRX configuration status through this parameter. The setting of this
parameter depends on the application requirement.
• Setup: normal DRX profile is used in normal status and reportCGI DRX profile is
used in reportCGI status.
• reportCGI: DRX is not used in normal status and reportCGI DRX profile is used in
reportCGI status.
ON_DURATION_TIME This parameter is timer to monitor PDCCH in DRX mode in normal status. (5.7 in TS
R_NORMAL 36.321) Value in number of PDCCH sub-frames: psf1 for 1 PDCCH subframe, psf2
for 2 PDCCH sub-frames and so on. Available values are greater than or equal to 10
ms.
[Related Specification] 3GPP TS 36.321 [5.7], TS 36.331 [6.3.2]
DRX_INACTIVITY_TIM This parameter is the timer to monitor PDCCH in DRX mode in the normal status
ER_NORMAL (5.7 in TS 36.321). Values in number of PDCCH sub-frames: psf1 for 1 PDCCH
subframe, psf2 for 2 PDCCH sub-frames and so on. Available values are greater
than or equal to 10 ms.
[Related Specification] 3GPP TS 36.331 [6.3.2]
DRX_RETRANSMISSI This parameter is the timer to monitor PDCCH in DRX mode in the normal status,
ON_TIMER_NORMAL when the DL retransmission is supposed to be occurred.
LONG_DRX_CYCLE_ The long DRX cycle and DRX start offset values to run onDurationTimer in DRX
START_OFFSET_TYP mode in the normal status. The unit of the long DRX cycle is a sub-frame. If the
E_NORMAL short DRX-Cycle is set to a value, this parameter is set to a multiple of the short
DRX-Cycle. The DRX start offset is set to an integer. For the TDD, DL sub-frame or
UL sub-frame can be set.
[Related Specification] 3GPP TS 36.331
SHORT_DRX_CONFI This parameter is used to indicate whether short DRX mode is supported or not. The

Confidential
G_SETUP support of short DRX mode is optional.
If DRX is configured, long DRX mode is used in default. This parameter is the
applied per UE.
• Release: Short DRX is not used.
• Setup: Short DRX is used.
SHORT_DRX_CYCLE This parameter is the short DRX cycle to run onDurationTimer in DRX mode in the
_NORMAL normal status.
• Available values: multiple of 10 ms
DRX_SHORT_CYCLE This parameter is the timer used to enter long DRX mode in the normal status.
_TIMER_NORMAL
DRX_SELECTION_OR This parameter is the selection order per QCI to select DRX profile. Different DRX
DER parameter values are defined per QCI. If there are several QCI bears coexist in the
system, as eNB only can configures one set to DRX parameter setting to UE, This
parameter is used to differentiate the selection priority of DRX parameter setting.
The selection order per QCI should be decided by referring the QoS requirement of
each QCI. [Related Specification] 3GPP TS 36.331 [6.3.2]
ON_DURATION_TIME This parameter is a timer to monitor the PDCCH in DRX mode in the intra-LTE
R_REPORT_CGI reportCGI status. The value is the number of PDCCH sub-frames: psf1 for 1 PDCCH
subframe, psf2 for 2 PDCCH sub-frames and so on.
DRX_INACTIVITY_TIM This parameter timer to monitor the PDCCH in DRX mode in the intra-LTE
ER_REPORT_CGI reportCGI status. The value is the number of PDCCH subframe: psf1 for 1 PDCCH
subframe, psf2 for 2 PDCCH sub-frames and so on. Defined values in specification
(36.331):
DRX_RETRANSMISSI This parameter is the timer used to monitor the PDCCH in DRX mode in the intra-
ON_TIMER_REPORT_ LTE reportCGI status.
CGI [Related Specification] 3GPP TS 36.331 [6.3.2]
LONG_DRX_CYCLE_ The long DRX cycle and DRX start offset values to run onDurationTimer in DRX
START_OFFSET_TYP mode in the intra-LTE reportCGI status. The unit of the long DRX cycle is a sub-
E_REPORT_CGI frame. If the short DRX-Cycle is set to a value, this parameter is set to a multiple of
the short DRX-Cycle. The DRX start offset is set to an integer. For the TDD, DL sub-
frame or UL sub-frame can be set.
[Related Specification] 3GPP TS 36.331
parameters.
Parameter Descriptions CHG-ENBPLMN-INFO/RTRV-ENBPLMN-INFO
(For PLMN_ID = 0, MCC and MNC should be fixed to primary PLMN.)
PLMN_ID This parameter is the Public Land Mobile Network (PLMN) index. The PLMN ID
MCC Mobile Country Code (MCC) that comprises Public Land Mobile Network (PLMN).
MCC of PLMN_IDX = 0 cannot be changed and used for the representative PLMN,
which is included in the Global eNB ID.
MNC Mobile Network Code (MNC) that comprises Public Land Mobile Network (PLMN).
MNC of PLMN_IDX = 0 cannot be changed and used for the representative PLMN,

Confidential
which is included in the Global eNB ID.
OP_ID This parameter is an operator index which share resources in this system.

PLMN index.
• use: The value of PLMN corresponding PLMN index can be serviced.
• no_use: The value of PLMN corresponding PLMN index not be serviced.
Parameter Descriptions of CHG-QCAC-PARA/RTRV-QCAC-PARA

DL_GBRUSAGE_THR This parameter is the percentage (%) of GBR that can be allocated as downlink for
ESH_NORMAL normal calls. If the downlink GBR PRB usage amount exceeds the entered
parameter ratio when a new call is requested, the QoS CAC Fail is generated.
If this parameter is too high, the system load after CAC is probably too high, which
results in system congestion.
If it is too low, the call requests are more likely to be failed, and some resources may
be idled and wasted.
DL_GBRUSAGE_THR This parameter is the percentage (%) of GBR that can be allocated as downlink for
ESH_HO emergency calls or handover calls. If the downlink GBR PRB usage amount
exceeds the entered parameter ratio when an emergency call or handover call is
requested, the QoS CAC Fail is generated.
UL_GBRUSAGE_THR This parameter is the percentage (%) of GBR that can be allocated as uplink for
ESH_NORMAL normal calls. If the uplink GBR PRB usage amount exceeds the entered parameter
ratio when a new call is requested, the QoS CAC Fail is generated.
UL_GBRUSAGE_THR This parameter is the percentage (%) of GBR that can be allocated as uplink for
ESH_HO emergency calls or handover calls. If the uplink GBR PRB usage amount exceeds
the entered parameter ratio when an emergency call or handover call is requested,
the QoS CAC Fail is generated.
Parameter Descriptions of CHG-QCACQ-PARA/RTRV-QCACQ-PARA

Confidential
characteristics.
DL_QCIUSAGE_THRE This parameter is the percentage (%) of PRB that can be allocated per QoS Class
SH_NORMAL Identifier (QCI) as downlink for normal calls. If the downlink GBR PRB usage
amount exceeds the entered parameter value when a new call is requested, the
QoS CAC Fail is generated.
DL_QCIUSAGE_THRE This parameter is the percentage (%) of PRB that can be allocated per QoS Class
SH_HO Identifier (QCI) as downlink for emergency calls or handover calls. If the downlink
GBR PRB usage amount exceeds the entered parameter value when an emergency
call or handover call is requested, the QoS CAC Fail is generated.
UL_QCIUSAGE_THRE This parameter is the percentage (%) of PRB that can be allocated per QoS Class
SH_NORMAL Identifier (QCI) as uplink for normal calls. If the uplink GBR PRB usage amount
exceeds the entered parameter value when a new call is requested, the QoS CAC
Fail is generated.
UL_QCIUSAGE_THRE This parameter is the percentage (%) of PRB that can be allocated per QoS Class
SH_HO Identifier (QCI) as uplink for emergency calls or handover calls. If the uplink GBR
PRB usage amount exceeds the entered parameter value when an emergency call
or handover call is requested, the QoS CAC Fail is generated.
UNIT_USAGE_MANU This parameter is the PRB usage percentage for manual assignment. It is used if the
AL estimationOption in the RTRV_CELL_CAC is EstimationOption_manual (1) and
valid up to three digits below the decimal point.
Counters and KPIs

E-RAB QCI per- PLMN0QCIReject If the requested QCI of the ERAB is not allowed for the
PLMN rejected PLMN0 (related PLMN ID can be found by the CLI : RTRV-
ENBPLMN-INFO and RTRV-CELLPLMN-INFO with plmnIdx
= 0), eNB will increase this counter. (per Cell/per QCI)
PLMN1QCIReject If the requested QCI of the ERAB is not allowed for the
PLMN1 (related PLMN ID can be found by the CLI : RTRV-

Confidential

=4), eNB will increase this counter. (per Cell/per QCI)
UE-AMBR Override S1APUEAmbrOverride If the PLMN specific UE AMBR control function is turned on
and configured by CLI RTRV/CHG-UEAMBR-CTRL and the
MME sends UL or DL AMBR value larger than the
configured Maximum UE AMBR value by S1 interface so
the AMBR value override occurs, eNB will increase this
counter. (per PLMN/per cell)
X2APUEAmbrOverride If the PLMN specific UE AMBR control function is turned on
and configured by CLI RTRV/CHG-UEAMBR-CTRL and the
neighbor eNB sends UL or DL AMBR value larger than the
configured Maximum UE AMBR value by X2 interface so
the AMBR value override occurs, eNB will increase this
counter. (per PLMN/per cell)
REFERENCE
None

Confidential
Chapter 7 Radio Scheduler
LTE-ME0501, Cell-Specific Reference Signal

INTRODUCTION
Cell-specific Reference Signals (CRS) are transmitted in every downlink subframe
and in every resource block in the frequency domain, thus covering the entire cell
bandwidth. The CRS can be used by the terminal for channel estimation for
coherent demodulation of any downlink physical channel except for PMCH and
for PDSCH in the case of transmission modes 7, 8, or 9, such as non-codebook
based precoding. The CRS can also be used by the terminal to acquire Channel
State Information (CSI). Finally measurements on CRS are used as the basis for
cell-selection and handover decisions.
BENEFIT
• Operator can provide multiple antenna transmission.
• LTE user can estimate downlink channel and demodulate control and traffic
channel data.
DEPENDENCY
E-UTRAN (LTE)
• Others
CRS transmission depends on the number of transmission antennas in the
eNB.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The cell specific reference signal is:
• Used to support CQI reporting, demodulation, cell selection, cell reselection
and handover.

Confidential
• Allocated resource elements which are distributed in both the time and
frequency domains
• Broadcast from antenna ports 0 to 3 during subframes supporting PDSCH
transmission
The cell specific reference signal is only defined for the 15 kHz subcarrier spacing,
that is, it is not supported for the 7.5 kHz subcarrier spacing used for Multimedia
Broadcast Multicast Service (MBMS).
The sequence used to generate each cell specific reference signal onto the set of
resource elements is the same for both FDD and TDD.
In general, the values of the reference symbols vary between different reference
symbol positions and also between different cells. Thus, a cell specific reference
signal can be seen as a two-dimensional cell specific sequence. The period of this
sequence equals one 10 ms frame. Furthermore, regardless of the cell bandwidth,
the reference signal sequence is defined assuming the maximum possible LTE
carrier bandwidth corresponding to 100 resource blocks in the frequency domain.
For cell bandwidths less than the maximum possible value, only the reference
symbols within that bandwidth are actually transmitted.
There are 504 different reference signal sequences defined for LTE, where each
sequence corresponds to one of 504 different physical layer cell identities. During
the cell search procedure the terminal detects the PCI of the cell as well as the cell
frame timing.
Thus, from the cell search procedure, the terminal knows the reference signal
sequence of the cell (given by the physical layer cell identity) as well as the start of
the reference signal sequence (given by the frame timing).
The set of reference symbol positions is outlined in the figure below. The
frequency shift to use in a cell depends on the PCI of the cell such that each shift
corresponds to 84 different cell identities. Thus, the six different frequency shifts
jointly cover all 504 different cell identities. By properly assigning PCI to different
cells, different reference signal frequency shifts may be used in neighboring cells.
The resource element allocation cycles once every 6 physical cell identities, for
example, identity 6 has the same resource element allocation as identity 0. This
corresponds to 1 cycle for every 2 physical layer cell identity groups.
Following figure is CRS as a function of the physical cell identity.

Confidential
Following figure illustrates the reference signal structure in the case of multiple,
more specifically two and four, cell specific reference signals, and corresponding
multiple antenna ports within a cell.
• In the case of two reference signals within a cell, the second reference signal is
frequency multiplexed with the first reference signal, with a frequency domain
offset of three subcarriers.
• In the case of four reference signals, the third and fourth reference signals are
frequency multiplexed and transmitted within the second OFDM symbol of
each slot, thus being time multiplexed with the first and second reference
signals.

Confidential
Obviously, the reference symbol density for the third and fourth reference signals
is lower, compared to the density of the first and second reference signals. The
reason for this is to reduce the reference signal overhead in the case of four
reference signals. More specifically, while the first and second reference signals
correspond to a relative over grid of approximately 5 % (four reference symbols
within a resource block consisting of a total 84 resource elements), the relative
overhead of the third and fourth reference signals is only half of that or
approximately 2.5 %.
The cell specific reference signal represents an overhead which reduces the
number of resource elements available for user plane data:
• Overhead increases when multiple transmit antenna ports are used.
• Overhead increases when using the extended cyclic prefix.
The overhead generated by the cell specific reference signal is presented in the
table below. The number of CRS ports can be configured by parameter
DL_CRS_PORT_COUNT (CHG-CELL-IDLE). Cell lock is needed to configure
the parameter. It is recommended that DL_CRS_PORT_COUNT (CHG-CELL-
IDLE) should be the same as parameter DL_ANT_COUNT (CHG-CELL-IDLE)
which means the number of Tx antenna.
Confidential
Number of antenna ports 1 2 4

Reference signal resource 4 8 12
element per resource block
Overhead (Normal CP) 4/84 = 4.8 % 8/84 = 9.5 % 12/84 = 14.3 %
Overhead (Extended CP) 4/72 = 5.6 % 8/72 = 11.1 % 12/72 = 16.7 %
SYSTEM OPERATION
How to Activate
• When creating the cell, the number of CRS is inputted and it is dependent on
the number of Antenna Port in RF Unit.
• Use the command RTRV-CELL-IDLE to retrieve the current number of CRS
Port.
Key Parameters
Parameter Descriptions of RTRV-CELL-IDLE
DL_ANT_COUNT This parameter is the number of Tx Antenna used by an operating cell.
system.
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME0506, Synchronization Signal

INTRODUCTION
Both the FDD and the TDD versions of LTE broadcast Synchronization Signals in
the downlink direction:
• Primary Synchronization Signal (PSS)
• Secondary Synchronization Signal (SSS)
Synchronization Signals are broadcast within every 10 ms radio frame. The UE
uses the Synchronization Signals to:
• achieve radio frame, subframe, slot and symbol synchronization in the time
domain
• identify the center of the channel bandwidth in the frequency domain
• deduce the Physical layer Cell Identity (PCI)
Detecting the Synchronization Signals is a prerequisite to measuring the cell
specific Reference Signals and decoding the Master Information Block (MIB) on
the Physical Broadcast Channel (PBCH).
BENEFIT
• Operator can make the time synchronization with LTE UE by using
synchronization signal.
• UE can find out a physical cell ID of serving cell by resolving synchronization
signal.
• UE can find out frame and slot starting time by resolving synchronization
signal.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT

Confidential
FEATURE DESCRIPTION
Primary Synchronization Signal

The Primary Synchronization Signal (PSS) is broadcast twice during every radio
frame and both transmissions are identical.
In the case of FDD,
• The PSS is broadcast using the central 62 subcarriers belonging to the last
symbol of time slots 0 and 10.
The PSS is used to:
• achieve subframe, slot and symbol synchronization in the time domain
• identify the center of the channel bandwidth in the frequency domain
• deduce a pointer towards 1 of 3 Physical layer Cell Identities (PCI)
PCI are organized into 168 groups of three, so the Primary Synchronization Signal
identifies the position of the PCI within the group but does not identify the group
itself. The PSS cannot be used to achieve radio frame synchronization because
both transmissions within the radio frame are identical and equally spaced in time.
Secondary Synchronization Signal

The Secondary Synchronization Signal (SSS) is broadcast twice within every radio
frame. The two transmissions of the SSS are different so the UE can detect which
is the first and which is the second.
In the case of FDD:
• The SSS is broadcast using the central 62 subcarriers belonging to the second
to last symbol of time slots 0 and 10.
The SSS is used to achieve radio frame synchronization and deduce a pointer
towards 1 of 168 Physical layer Cell Identity (PCI) groups allows the PCI to be
deduced when combined with the pointer from the PSS. The set of Resource
Elements allocated to the Synchronization Signals is independent of the channel
bandwidth. The UE does not require any knowledge of the channel bandwidth
prior to detecting the Synchronization Signals. The downlink channel bandwidth is
subsequently read from the MIB on the PBCH.
The figure below illustrates the timing of the PSS and SSS for FDD. This example
assumes the normal cyclic prefix because there are seven symbols within each
time slot. The extended cyclic prefix follows a similar pattern except there are only
six symbols within the time slot (the SSS and PSS remain within the last two
symbols of the time slot).

Confidential
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

with this feature.

Confidential
REFERENCE

Confidential
LTE-ME0507, Demodulation Reference Signal

INTRODUCTION
In LTE there are two types of reference signals defined in the uplink.
• Demodulation reference signals, which are transmitted on uplink resources
assigned to the UE, are for coherent demodulation of data and control
information at the eNB. As PUCCH cannot be transmitted simultaneously with
PUSCH, there are demodulation reference signals defined for each of them,
that is, there are demodulation reference signals for PUSCH and demodulation
reference signals for PUCCH.
• Sounding reference signals are wideband reference signals for the eNB to
measure uplink channel quality information for uplink resource allocation.
They are not associated with the transmission of PUSCH or PUCCH.
The reason for having two types of reference signals in the uplink is why
demodulation reference signals in uplink are only transmitted on subcarriers
assigned to the UE unlike the downlink and cannot provide sufficient wideband
channel quality information for resource allocation, particularly over the resource
blocks that are not allocated to the UE.
BENEFIT
eNB can demodulate uplink data and control information by the channel estimate
from this signal.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Reference Signal Sequence

Both the demodulation reference signal and the sounding reference signal are
defined by a cyclic shift of the same base sequence. The generation of the base
sequence depends on the reference signal sequence length.

Confidential
• If m ≥ 3, m is the size of the resource blocks assigned to the UE (the UE is

assigned three resource blocks or more), the base sequence is based on prime-
length Zadoff-Chu sequences that are cyclically extended to the desired length.
• For m = 1 or m = 2, the base sequence form given in [1].
Multiple reference signals can be created by different shifts of the same base
sequence. As the Zadoff-Chu sequence has the property that cyclic shifted versions
of the same sequence are orthogonal to each other, generating reference signals in
such a manner can reduce inter-cell interference for the reference signal
transmission. The orthogonality of reference signals for each UE are only carried
in resource blocks assigned to that UE.
The reference signal in the uplink is always UE-specific.
Resource Mapping of Demodulation Reference Signals

The resource mapping of the demodulation reference signal is different for
PUSCH and PUCCH channels.
For PUSCH, the demodulation reference signal sequence is mapped to resource
elements (k, l) with l = 3 for normal CP and l = 2 for extended CP, with increasing
order first in k and then in the slot number. An example of demodulation reference
signal mapping for PUSCH is shown in the following figure, with the normal CP.
The DM-RS cyclic shift for PUSCH is determined by the configuration
CYCLIC_SHIFT (CHG-PUSCH-IDLE).
The figure below is Resource mapping of DM-RS for PUSCH with the normal CP.
DM-RS location for different PUCCH Formats

PUCCH Format Set of values for I
Normal Cyclic Prefix Extended Cyclic Prefix
1, 1a, 1b 2, 3, 4 2, 3
2 1, 5 3

Confidential
PUCCH Format Set of values for I

2a, 2b 1, 5 N/A
PUCCH supports six different formats, and the resource mapping to SC-FDMA
symbols for different formats is listed in upper table. Note that the number of
PUCCH demodulation reference symbols is different for different formats, which
is related to the number of control symbols for each format. For example, there are
10 CQI/PMI modulated symbols for PUCCH format 2/2a/2b, and there are 2
reference symbols in each slot as shown in upper table, so there are a total of 14
symbols that fill the whole subframe, which is of 14 SC-FDMA symbols. As
PUCCH format 1/1a/1b has fewer information bits than PUCCH format 2/2a/2b,
there are more reference symbols for format 1/1a/1b than there are for format
2/2a/2b, which can be used to improve the channel estimation performance.
Note that due to the resource mapping of PUCCH, the two consecutive slots
shown in the following figure (a) and (b) are at the two edges of the whole
bandwidth.
The figure below is Resource mapping of DM-RS for PUCCH with normal CP.
SYSTEM OPERATION
How to Activate

Confidential
Key Parameters
parameters.
PURPOSE This parameter is to set n (1)_DMRS of PUSCH
ACTIVE_STATE The n (1)_DMRS (Demodulation reference signal) value is cell-specific.
The cyclic shift value of the PUSCH demodulation reference signal is
determined by both n (1)_DMRS value set by this parameter and the n
(2)_DMRS value assigned in DCI format 0.
The reference signal sequence is defined by the cyclic shift of a Zadoff-Chu
base sequence.
The change should be performed as follows:
• Lock the cell at LSM
• Use the command CHG-PUSCH-IDLE to change the configuration of the
Physical Uplink Shared Channel (PUSCH) in the eNB.
• Change the FORCED_MODE value from False to True.
• Change the parameter value and block the cell. And unblock the cell again.
maximum capacity provided to the carrier per system is 1 FA/3 Sector, up to 3
cells are supported
CYCLIC_SHIFT The n (1)_DMRS (Demodulation reference signal) value is cell-specific. The
cyclic shift value of the PUSCH demodulation reference signal is determined by
both n (1)_DMRS value set by this parameter and the n (2)_DMRS value
assigned in DCI format 0. The reference signal sequence is defined by the
cyclic shift of a Zadoff-Chu base sequence.
5 Change the FORCED_MODE value from False to True.
6 Change the parameter value and block the cell. And unblock the cell again.
FORCED_MODE This parameter indicates whether to change the configuration regardless of the
cell status.
Counters and KPIs

with this feature.
REFERENCE

Confidential

Confidential
LTE-ME0508, Sounding Reference Signal

INTRODUCTION
In LTE there are two types of reference signals defined in the uplink.
• Demodulation reference signals, which are transmitted on uplink resources
assigned to the UE, are for coherent demodulation of data and control
information at the eNB.
As PUCCH cannot be transmitted simultaneously with PUSCH, there are
demodulation reference signals defined for each of them, that is, there are
demodulation reference signals for PUSCH and demodulation reference
signals for PUCCH.
• Sounding Reference Signal (SRS) can be used to measure the uplink channel
quality over a section of the channel bandwidth. The eNB can use this
information for uplink frequency selective scheduling and link adaptation.
When uplink/downlink channel reciprocity is assumed, measurements from the
SRS can also be used to support downlink transmission, for example, the SRS
can be used to support Angle of Arrival (AoA) measurements for downlink
beamforming. Channel reciprocity is most applicable to TDD in which case
the same RF carrier is used for uplink and downlink transmissions. The SRS
was introduced within the release 8 version of 3GPP specifications, and was
subsequently enhanced within the release 10 version. Enhancements provide
support for uplink MIMO and rapid triggering of SRS transmissions using a
flag within the DCI.
The reason for having two types of reference signals in the uplink is because,
unlike the downlink, the demodulation reference signals in uplink are only
transmitted on subcarriers assigned to the UE and therefore cannot provide
sufficient wideband channel quality information for resource allocation,
particularly over the resource blocks that are not allocated to the UE. Unlike the
downlink, the reference signal in the uplink cannot be transmitted at the same time
as user data. Instead, the uplink reference signals are time division multiplexed
with the uplink data in the assigned subcarriers. In this way, the power level of the
reference signal can be different from that of the data symbol as they are
transmitted over different SC-FDMA symbols, so the PAPR is minimized over
each SC-FDMA symbol.
BENEFIT
The eNB can estimate uplink channel response by receiving this signal. The
channel estimate is utilized in the next uplink scheduling.
DEPENDENCY
E-UTRAN (LTE)

Confidential
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
SRS is transmitted within the last SC-FDMA symbol at the subframe as shown
below. The sending interval of SRS by a UE is between 2 ms and 320 ms. SRS
sequence provides the index for cyclic shift from 0 to 7. Accordingly, if other
indexes for cyclic shift are used, multiple UEs are possible to transmit SRS at the
same time on the same frequency resources. In addition, SRS is not transmitted
over all subcarriers of RB but it is transmitted in a comb pattern by selecting an
even or odd subcarrier.
If two different transmission comb patterns are used, two UEs with the same cyclic
shift index may transmit SRS on the same time and frequency resources.
The assignment of the subframe resource of the cell for transmitting SRS is set
through srs-SubframeConfig consisting of 4 bits (Cell Specific SRS). Below two
tables represent the indexes for srs-SubframeConfig and the corresponding periods
and offset values of SRS in the case of FDD and TDD specified by 3GPP TS
36.211. For example, if srs-SubframeConfig is set to 3 in an FDD cell, SRS is
transmitted every 5 ms with the subframe offset {0} in the cell. In case of TDD,
srs-SubframeConfig 14 and 15 are not used.
The following table is frame structure type 1 sounding reference signal subframe
configuration.
SRS-SubframeConfig Binary Configuration Period (subframes) Transmission offset
(subframes)
0 0000 1 {0}
1 0001 2 {0}
2 0010 2 {1}
3 0011 5 {0}
4 0100 5 {1}
5 0101 5 {2}
6 0110 5 {3}
7 0111 5 {0, 1}
8 1000 5 {2, 3}
9 1001 10 {0}
10 1010 10 {1}
11 1011 10 {2}
12 1100 10 {3}
13 1101 10 {0, 1, 2, 3, 4, 6, 8}
14 1110 10 {0, 1, 2, 3, 4, 5, 6, 8}

Confidential

(subframes)
15 1111 Inf. N/A
The following table is frame structure type 2 sounding reference signal subframe
configuration.
(subframes)
0 0000 5 {1}
1 0001 5 {1, 2}
2 0010 5 {1, 3}
3 0011 5 {1, 4}
4 0100 5 {1, 2, 3}
5 0101 5 {1, 2, 4}
6 0110 5 {1, 3, 4}
7 0111 5 {1, 2, 3, 4}
8 1000 10 {1, 2, 6}
9 1001 10 {1, 3, 6}
10 1010 10 {1, 6, 7}
11 1011 10 {1, 2, 6, 8}
12 1100 10 {1, 3, 6, 9}
13 1101 10 {1, 4, 6, 7}
14 1110 reserved reserved
15 1111 reserved reserved
The number of RBs over which SRS is transmitted, that is, SRS bandwidth, is
determined by the cell-specific parameter SRS-BandwidthConfig.
An example of SRS bandwidths in10 MHz bandwidth is shown in the table below.
SRS bandwidth SRS-Bandwidth SRS-Bandwidth SRS-Bandwidth SRS-Bandwidth
configuration B_SRS = 0 B_SRS = 1 B_SRS = 2 B_SRS = 3
m_SRS, 0 N0 m_SRS, 1 N1 m_SRS, 2 N2 m_SRS, 3 N3
0 48 1 24 2 12 2 4 3
1 48 1 16 3 8 2 4 2
2 40 1 20 2 4 5 4 1
3 36 1 12 3 4 3 4 1
4 32 1 16 2 8 2 4 2
5 24 1 4 6 4 1 4 1
6 20 1 4 5 4 1 4 1
7 16 1 4 4 4 1 4 1
The number of RBs over which the SRS is transmitted is denoted by m_SRS, 0-
m_SRS, 3.

Confidential
Each value is determined by the cell-specific parameter SRS-BandwidthConfig

and the number of RBs assigned to a UE is determined according to the UE-
specific parameter SRS-Bandwidth between 0 and 3.
For example, if SRS-BandwidthConfig is 3, 36 RBs are assigned to SRS
bandwidth, and if SRS-Bandwidth is configured to 2 for a UE, it transmits SRS in
the size of 4 RBs.
Whether the frequency hopping of SRS is used is determined according to two
UE-specific parameters, SRS-Bandwidth and SRS-Hopping-Bandwidth.
SYSTEM OPERATION
How to Activate
Preconditions
There are no specific preconditions to active this feature.
However, when this feature is configured for smart scheduler, DL Smart feature
(LTE-ME6004) should be enabled.
Activation Procedures
• Run CHG-SRS-IDLE and set SRS_USAGE to enable SRS feature.
For smart scheduler usage, additionally:
• Run CHG-SRS-IDLE and set smartSrsEnable to enable SRS feature for smart
usage.
Deactivation Procedures
• Run CHG-SRS-IDLE and set SRS_USAGE to disable SRS feature.
For smart scheduler usage, additionally:
• Run CHG-SRS-IDLE and set smartSrsEnable to disable SRS feature for
smart usage.
Key Parameters
parameters.
Parameter Description of CHG-SRS-IDLE/RTRV-SRS-IDLE
Confidential
SRS_USAGE This parameter indicates whether the SRS is used/not used.
• no_use: SRS is not used.
• use: SRS is used.
SMART_SRS_ENABLE This parameter indicates which scheduling mode is applied to SRS
resource allocation.
• False: Macro mode
• True: Smart mode
parameters.
Parameter Description of CHG-DPHY-ULSRS/RTRV-DPHY-ULSRS
cells supported by the system.
DURATION The transmission duration of Sounding RS.
• 0: Sounding RS is transmitted only once.
• 1: Sounding RS is transmitted repeatedly until it is disabled.
Parameter Description of CHG-SRS-IDLE/RTRV-SRS-IDLE

FORCED_MODE Whether to set the PLD change regardless of the cell status.
• False: The PLD change is set according to the cell status.
• True: The PLD change is set regardless of the cell status.
Parameter Description of CHG-SNDRS-CONF/RTRV-SNDRS-CONF

ACK_NACK_SRS_SIMUL_TRAN This is defined to enable simultaneous transmission of ACK/NACK or SR,
SMISSION and sounding RS.
• False: Sounding RS is not transmitted. (only PUCCH carrying
ACK/NACK or SR is transmitted)
• True: Sounding RS and PUCCH can be transmitted simultaneously.
The parameters listed below are accessible and configurable when DL Smart
feature (LTE-ME6004) is enabled.
Parameter Description of CHG-DPHY-ULSRS/RTRV-DPHY-ULSRS
SRS_POOL_IDX0 SRS Pool Index array (-1 (0xff): not allocated)

Confidential
Parameter Description of CHG-SRSNBR-CONF/RTRV-SRSNBR-CONF

SRS_NBR_IDX SRS neighbor cell idx.
STATUS The validity of the SRS neighbor cell information.
ENB_ID The eNB ID of the eNB to which SRS neighbor cell to the eNB belongs. If
the enbType value is macro eNB, 20 bit of the value is eNB ID. If the
enbType value is home eNB, 28 bit of the value is eNB ID. It is used when
TARGET_CELL_NUM The local cell ID of SRS neighbor cell to the eNB. It is used when creating
a cell identifier.
CLUSTER_ID This is the cluster ID to which the eNB belongs.
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME0601, RACH Preamble Format 0 to 3

INTRODUCTION
Since the random access mechanism is used by the UE when it is not synchronized
on the uplink a guard time needs to be introduced to avoid collisions with other
transmissions. The duration of the guard time needs to account for the round trip
propagation time and is dependent upon the cell size supported. With propagation
speed of 1 km/3.33 us, approximately 6.7 us of guard time per kilometer is
required to accommodate the round-trip time. To support cell size up to 100 km as
required for LTE, the guard time should be in the range of 670 us. However, this
large guard time is an undesired overhead when the system is deployed with
smaller cells, which are most common.
Therefore, multiple random access preamble formats with both small and large
guard times are defined.
BENEFIT
Enabling this feature can support various cell sizes defined in 3GPP standard.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
• Format 0 to 3 can be used for FDD and TDD commonly
• Format 4 is only available for TDD, and the theoretical available cell range is
under 1.4 km. Currently, RACH format 4 is not available in the PKG.
SYSTEM IMPACT
FEATURE DESCRIPTION
The Physical Random Access Channel (PRACH) is used to transfer the random
access preambles used to initiate the random access procedure. The PRACH does
not transfer any RRC messages nor any application data. The general structure of a
random access preamble is illustrated in the following figure. It includes a cyclic
prefix, a sequence and a guard time.

Confidential
The cyclic prefix is usually required to account for the maximum delay spread,
that is, the maximum delay spread should not exceed the duration of the cyclic
prefix. In the case of the PRACH, the cyclic prefix has to account for both the
maximum delay spread and the maximum cell range. This additional requirement
is caused by the UE transmitting the PRACH before any Timing Advance
instructions have been provided. The guard time duration should be long enough to
accommodate the round trip time. This limits any overlap into the subsequent
subframe, that is, only delay spread components overlap into the subsequent
subframe.
3GPP TS 36.211 specifies the set of four preamble formats for FDD and TDD
presented in following table. These are all based on the structure illustrated in
above figure but have different durations for the cyclic prefix, sequence and guard
time: Format 0 to 3 can be used by either FDD or TDD, and are based on relatively
long preamble sequences. For frame structure type 1 with preamble format 0-3,
there is at most one random access resource per subframe.
Preamble Format Cyclic Prefix Sequence Guard Time Total Length Typical Max.
Duration Duration cell range
0 103.13 us 800 us 96.88 us 1 ms 14.5 km
1 684.38 us 800 us 515.63 us 2 ms 77.3 km
2 203.13 us 1600 us 196.88 us 2 ms 29.5 km
3 684.13 us 1600 us 715.63 us 3 ms 100.2 km
The PRACH parameters shown in the table below require configuration when
planning LTE network. These parameters are broadcast to idle mode UE on the
BCCH using SIB2. They can also be signaled to individual UE in connected mode
using an RRC Connection Reconfiguration message.
Parameters Range Configuration Criteria
PRACH 0 to 63 • Cell range
Configuration • PRACH preamble capacity
Index
• Air interface performance
Zero Correlation 0 to 15 • Cell range
Zone • Air interface performance
Configuration
• Size of root sequence index reuse pattern
High Speed Flag True/False • UE mobility
• Complexity of root sequence index planning
Root Sequence 0 to 837 Should be unique in neighboring cells
Index

Confidential
Parameters Range Configuration Criteria

PRACH 0 to 94 PUCCH resource block allocation
Frequency Offset
The table below presents the PRACH configuration indexes

(PRACH_CONFIG_INDEX (CHG-PRACH-CONF)) for FDD. The PRACH
configuration index also defines the System Frame Number (SFN) and the
subframes during which the PRACH can be transmitted.
The PRACH configuration index determines the preamble format and the
preamble density. The cell range is the most important criteria when selecting the
preamble format. Preamble formats supporting larger cell ranges should not be
selected unless required because they generate larger PRACH overheads, that is,
each preamble occupies an increased number of subframes.
Confidential
In addition, the Zero Correlation Zone Configuration

(ZERO_CORREL_ZONE_CONFIG (CHG-PRACH-CONF)) has an impact upon
cell range and air-interface performance, as well as the size of the re-use pattern
used to allocate the Root sequence index values. The cell radius is limited by
PRACH preamble format as shown below, even though it is decided by zero
correlation zone configuration. For example, the cell radius is about 14.5Km, since
R = min{16 Km, 14.5 Km}, when preamble format 0 and zero correlation zone
configuration of 12 is used assuming high speed flag is set to '0'.
The High Speed Flag (HIGH_SPEED_FLAG (CHG-PRACH-CONF)) can be set to

'false' for the majority of scenarios. It is intended to help tackle the impact of
Doppler at very high speeds. Setting this flag to 'true' complicates the planning of
root sequence index values because the number of preamble sequences generated
from each root sequence becomes variable rather than fixed.
The allocation of root sequence index (ROOT_SEQUENCE_INDEX (CHG-
PRACH-CONF)) values to each cell should be based on a reuse pattern which
ensures that neighboring cells have mutually exclusive sets of root sequences.
PRACH Frequency Offset determines the position of the PRACH preambles in the
frequency domain.
SYSTEM OPERATION

Confidential
How to Activate
Key Parameters
parameters.
Parameter Descriptions of RTRV-PRACH-CONF/CHG-PRACH-CONF
PRACH_CONFIG_INDE Index for the preamble format, subframe sent by preamble, and interval.
X
HIGH_SPEED_FLAG This parameter indicates whether to use unrestricted or restricted set. When this
parameter is set to TRUE, a restricted set is used. When set to FALSE, an
unrestricted set is used.
ZERO_CORREL_ZONE This parameter defines the cyclic shift between two preambles generated by the
_CONFIG same PRACH root sequence. If the air delay (RTD) is larger than the cyclic shift
value, the preamble transmitted by UE is erroneously detected as a different one
and hence detection fails. Therefore, the maximum cell coverage is also
determined by this parameter.
ROOT_SEQUENCE_IN The first logical root sequence index used to create a random preamble. Different
DEX values should be assigned to neighboring cells. Refer the SON Algorithm for
changing this parameter because it affects the entire system.
Counters and KPIs

Random Access DedicatedPreambles The cumulated number of dedicated preambles among
Preambles the periodically collected RACH preambles.
RandomlySelectedPrea The cumulated number of the preambles belonging to
mblesLow Group B among the detected contention based
preambles
RandomlySelectedPrea The cumulated number of the preambles belonging to
mblesHigh Group B among the detected contention based
preambles
RandomAccessRespons The cumulated number of RandomAccessResponse
es (RAR) messages are transmitted.
For this counter, the statistics are collected periodically.

Confidential
REFERENCE

Confidential
LTE-ME0603, Random Access Procedures

INTRODUCTION
The Random Access (RA) procedure is required when making the transition from
RRC idle mode to RRC connected mode, completing an intra system handover or
uplink/downlink data arrives while UE is in the 'non-synchronized' RRC connected
mode state. The random access procedure can be either contention based or non-
contention based. The contention based procedure involves the UE selecting a
random access resource, whereas the non-contention based procedure involves the
eNB allocating the random access resource. The contention based procedure can
be used for all random access reasons. The non-contention based procedure can be
used for handover or the arrival of downlink data.
BENEFIT
• The eNB supports contention based and non-contention based operation of
random access procedures.
• Help in minimizing the chance of collision.
• Non-contention based random access procedure helps UE minimize the chance
of collision.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Contention-based RA Procedure
It consists of four steps shown in the figure below.

Confidential
Step 1: RA preamble transmission:

Random Access Resource Selection
1) Select contention based random access preamble. The number of contention
based random access preambles is configured by
NUMBER_OF_RAPREAMBLES (CHG-RACH-CONF).
2) Determine the next available PRACH Sub-frame.
The contention based procedure starts with the UE selecting a set of resources for
the PRACH in terms of a preamble sequence, and the next available subframe for
PRACH transmission. The preamble sequence is used to differentiate between
multiple UE using the same set of PRACH resource blocks. There are a total of 64
preamble sequences which can be divided into the contention based random access
groups A and B, and non-contention based random access group. The random
access group A size is configured by SIZE_OF_RAPREAMBLES_GROUP_A
(CHG-RACH-CONF). The group B size is determined by
NUMBER_OF_RAPREAMBLES (CHG-RACH-CONF) -
SIZE_OF_RAPREAMBLES_GROUP_A (CHG-RACH-CONF). The next
available subframe is defined by PRACH configuration index broadcast within
SIB2.
Random Access Preamble Transmission
3) Set Preamble Target Power (PREAMBLE_INIT_RCV_TARGET_POWER
(CHG-RACH-CONF)).
4) Request Physical layer to transmit Preamble.
The UE proceeds to transmit the PRACH preamble. UE selects random access
preamble group B when the potential message size is greater than
MESSAGE_SIZE_GROUP_A (CHG-RACH-CONF) and when the pathloss is less
than PCMAX- PREAMBLE_INIT_RCV_TARGET_POWER (CHG-RACH-
CONF) - MESSAGE_POWER_OFFSET_GROUP_B (CHG-RACH-CONF).
Step 2: RA response:
5) Match the preamble to receive the response.
6) Apply the timing advance in the message.
7) Process the Uplink Resource Grant.

Confidential
The Random Access Response (RAR) is sent by the eNB on the Physical
Downlink Shared Channel (PDSCH), and addressed with a preamble ID, the
Random Access Radio Network Temporary Identifier (RA-RNTI), identifying the
time-frequency slot in which the preamble was detected. If multiple UEs had
collided by selecting the same signature in the same preamble time-frequency
resource, they would each receive the RAR. The RAR conveys the identity of the
detected preamble, a timing alignment instruction to synchronize subsequent
uplink transmissions from the UE, an initial uplink resource grant for transmission
of the Step 3 message, and an assignment of a Temporary Cell Radio Network
Temporary Identifier (C-RNTI) (which may or may not be made permanent as a
result of the next step-contention resolution). The RAR message can also include a
‘backoff indicator’ which the eNB can set to instruct the UE to back off for a
period (configured by BACKOFF_INDICATOR (CHG-RACH-CONF)) before
retrying a random access attempt. The UE expects to receive the RAR within a
time window, of which the start and end are configured by the eNB and broadcast
as part of the cell-specific system information. The earliest subframe allowed by
the specifications occurs 2 ms after the end of the preamble subframe, as
illustrated in the figure below.
The figure below shows the RAR consisting of the step 2 message (on PDSCH)
together with its downlink transmission resource allocation message ‘G’ (on the
Physical Downlink Control Channel (PDCCH). If the UE does not receive a RAR
within the configured time window, it retransmits the preamble. The minimum
delay for preamble retransmission after the end of the RAR window
(RA_RESPONSE_WINDOW_SIZE (CHG-RACH-CONF)) is 3 ms. The eNB may
configure preamble power ramping (which is configured by
POWER_RAMPING_STEP (CHG-RACH-CONF))so that the transmission power
for each retransmitted preamble is increased by a fixed step. The following figure
shows Random Access Response.
Step 3: Message 3 transmission:

This message is the first scheduled uplink transmission on the PUSCH and makes
use of Hybrid Automatic Repeat request (HARQ). It conveys the actual random
access procedure message, such as an RRC connection request, tracking area
update, or scheduling request. It includes the Temporary C-RNTI allocated in the
RAR at Step 2 and either the C-RNTI if the UE already has one
(RRC_CONNECTED UEs) or the (unique) 48-bit UE identity. In case of a
preamble collision having occurred at Step 1, the colliding UEs will receive the
same Temporary C-RNTI through the RAR and will also collide in the same
uplink time-frequency resources when transmitting Message 3. This may result in
such interference that colliding UEs cannot be decoded, and the UEs restart the
random access procedure after reaching the maximum number of HARQ
retransmissions (MAX_HARQMSG3_TX (CHG-RACH-CONF)). However, if one
UE is successfully decoded, the contention remains unresolved for the other UEs.
The following downlink message (in Step 4) allows a quick resolution of this
Confidential
contention.
Step 4: Contention resolution message:
The contention resolution message is addressed to the C-RNTI or Temporary C-
RNTI, and, in the latter case, echoes the UE contention resolution identity MAC
control element (CE) contained in the Message 3. It supports HARQ. In case of a
collision followed by successful decoding of the Message 3, the HARQ feedback
is transmitted only by the UE which detects its own UE identity (or C-RNTI);
other UEs understand there was a collision, transmit no HARQ feedback, and can
quickly exit the current random access procedure and start another one. Therefore,
the UE’s behavior upon reception of the contention resolution message has three
possibilities.
• The UE correctly decodes the message and detects its own identity: it sends
back a positive Acknowledgement, ACK.
• The UE correctly decodes the message and discovers that it contains another
UE’s identity (contention resolution): it sends nothing back (Discontinuous
Transmission, DTX).
• The UE fails to decode the message or misses the DL grant: it sends nothing
back (DTX).
• If the contention resolution message is not received within
CONTENTION_RESOLUTION_TIMER (CHG-RACH-CONF) after sending
Message 3, UE recognizes the current random access procedure fails.
Otherwise, UE recognizes the random access procedure is successful.
Non-contention-based RA procedure
The slightly unpredictable latency of the random access procedure can be
circumvented for some use cases where low latency is required, such as handover
and resumption of downlink traffic for a UE, by allocating a dedicated signature to
the UE on a per-need basis. In this case the procedure is simplified as shown in the
figure below. The procedure terminates with the RAR. The following figure shows
non-contention based Random Access Procedure.
Samsung eNB provides the following counters related to RA procedure.

RA counter family:
• RandomlySelectedPreamblesLow: Number of group A preambles received

Confidential
• RandomlySelectedPreamblesHigh: Number of group B preambles received

• DedicatedPreambles: Number of non-contention-based preambles received
• HandoverDedicatedPreambles: Number of non-contention-based preambles
received for handover purpose
• DedicatedPreamblesAssignFail: Number of times a non-contention-based
preamble could not be assigned to a UE because all non-contention-based
preambles were already assigned to other UEs
• RandomAccessResponses: Number of RARs sent by eNB
• RACHUsageAvg: Number of RA preambles received per second
RACH_USAGE counter family:
Counters in this family are pegged based on numberOfPreamblesSent and
contentionDetected IEs included in RACH report sent by the UE in UE
Information Response message.
• PreambleSent1~PreambleSent9: Number of received RACH reports with
numberOfPreamblesSent IE = 1~9
• RACHContention: Percentage of received RACH reports with
contentionDetected IE = TRUE
• RACHReportsRcvNum: Number of RACH reports received
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Description of CHG-RACH-CONF/RTRV-RACH-CONF
NUMBER_OF_RAPRE In each LTE cell, a total of 64 preambles are available for random access procedure.
AMBLES This value indicates the number of non-dedicated preambles for contention-based
random access procedure, except the dedicated ones for non-contention based

Confidential
random access procedure.
SIZE_OF_RAPREAMB This parameter is the number of PreamblesGroup A.
LES_GROUP_A
MESSAGE_SIZE_GR This parameter is message size standard to select PreamblesGroup A. This value
OUP_A indicates the message size allocated for message3 transmission by the preambles in
Preambles Group A.
MESSAGE_POWER_ Power offset standard to select preamble group B. The set of non-dedicated
OFFSET_GROUP_B preambles for random access procedure is subdivided into two subgroups,
preambles group A and preambles group B. This value is used for the initial
preamble transmission power setting and the selection of one preamble group
among those two.
POWER_RAMPING_S This parameter specifies the power ramping steps for preamble transmit power when
TEP preamble transmission counter increases.
PREAMBLE_INIT_RC This parameter specifies the initial target receiving power of preambles. Value dBm-
V_TARGET_POWER 120 corresponds to -120 dBm and so on.
PREAMBLE_TRANS_ This parameter is the maximum number of times to transmit a preamble.
MAX
CONTENTION_RESO This parameter is connection resolution timer per Subframe.
LUTION_TIMER
BACKOFF_INDICATO This parameter setup or release the backoff indicator.
R_SETUP • Release: release.
• Setup: setup.
BACKOFF_INDICATO This parameter specifies the backoff value.
R
MAX_HARQMSG3_TX The maximum number of transmission of
HARQ Msg3.
Parameter Description of CHG-RACH-IDLE/RTRV-RACH-IDLE

RA_RESPONSE_WIN The period per subframe during, which UE waits for RA Response. If the UE does
DOW_SIZE not receive RA Response within this period, it retransmits the preamble.
FORCED_MODE This parameter indicates whether to change the configuration regardless of the cell
status.
Counters and KPIs

Random Access DedicatedPreamble The cumulated number of dedicated preambles among the
Preambles s periodically collected RACH preambles.
RandomlySelected The cumulated number of the preambles belonging to Group
PreamblesLow B among the detected contention based preambles.
RandomlySelected The cumulated number of the preambles belonging to Group

Confidential

PreamblesHigh B among the detected contention based preambles.
RandomAccessRes The cumulated number of RandomAccessResponse (RAR)
ponses messages are transmitted. For this counter, the statistics are
collected periodically.
REFERENCE

Confidential
LTE-ME1001, Variable Number of OFDM

Symbols for PDCCH
INTRODUCTION
The number of resources (OFDM symbols) used in each subframe for PDCCH
shall be dynamic based on the requirement of the Control Channel Element (CCE)
by the load of control signaling. This flexibility allows the control channel
overhead to be adjusted according to the particular system configuration, traffic
scenario and channel conditions.
The PCFICH carries a Control Format Indicator (CFI) which indicates the number
of OFDM symbols (for example, normally 1, 2 or 3) used for transmission of
control channel information in each subframe. There are two special cases: in
subframes containing MBSFN transmissions there may be 0, 1 or 2 for control
signaling, while for narrow system bandwidths (less than 10 resource blocks) the
number of control symbols is increased, and may be 2, 3 or 4 to ensure sufficient
coverage at the cell border.
BENEFIT
• Subscribers may experience higher throughput in downlink in typical
scenarios with low load on PDCCH and high utilization of PDSCH.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
CFI is transmitted via PCFICH and indicates the number of OFDM symbols used
for PDCCH in each DL subframe. The range of CFI value is between 1 and 3. The
larger the CFI value, more symbols are allotted for control region thus the number
of available Control Channel Element (CCE) is increased. CCE is a basic resource
unit used for PDCCH.
As shown in the table below, for the system bandwidth N_RB > 10, the PDCCH
spans 1, 2 or 3 OFDM symbols, given by the value of the CFI; for system

Confidential
bandwidths N_RB < = 10, the PDCCH spans 2, 3, or 4 OFDM symbols, given by
CFI + 1.
Subframe Number of OFDM symbols Number of OFDM symbols
for PDCCH when N_RB > for PDCCH when N_RB <=
10 10
Subframe 1 and 6 for frame structure type 2 1.2 2
MBSFN subframe on a carrier supporting PDSCH, 1.2 2
configured with 1 or 2 cell-specific antenna ports
MBSFN subframe on a carrier supporting PDSCH, 2 2
configured with 4 cell-specific antenna ports
Subframes on a carrier not supporting PDSCH 0 0
Non-MBSFN subframes (except subframe 6 for 1, 2, 3 2, 3
frame structure 2) configured with positioning
reference signal
All other cases 1, 2, 3 2, 3, 4
To accommodate more PDCCH in a subframe, number of available CCE should be

large enough. Keeping large number of CCEs for PDCCH results in higher control
channel overhead and eventually reduces the system efficiency. CFI adaptation in
Samsung LTE system can be turned on or off by parameter
CFI_ADAPT_ENABLE (CHG-MACPDCCH-FUNC). If CFI_ADAPT_ENABLE is
set as 0, CFI is determined as fixed value which is the value of parameter
FIXED_OR_MIN_CFI (CHG-MACPDCCH-FUNC). If CFI_ADAPT_ENABLE =
1, CFI can change dynamically based on the estimation of required CCEs, while
minimum number of CFI is set as the value of parameter FIXED_OR_MIN_CFI.
The estimation of required CCE is based on the result of past scheduling
experience:
N_Required_CCE = N_Used_CCE + N_banned_CCE
,where N_Required_CCE is the number of required CCEs, N_Used_CCE is the
number of assigned CCEs in the last scheduling period, and N_banned_CCE is the
number of unassigned CCEs caused by collision or shortage in the last scheduling
period, respectively. As the next step, N_Required_CCE is averaged by passing
through Infinite Impulse Response (IIR) filter. Finally, eNB decides the number of
OFDM symbols to be used for PDCCH by comparing the number of required
CCEs with the number of available CCEs per CFI.
Condition Determined CFI
Filtered_N_Required_CCE < N_Available_CCE_CFI [1] 1
N_Available_CCE_CFI [1] ≤ Filtered__Required_CCE < N_Available_CCE_CFI [2] 2
N_Available_CCE_CFI [2] ≤ Filtered__Required_CCE 3
In the above table, Filtered_N_Required_CCE is IIR-filtered number of required

CCEs and N_Available_CCE_CFI [N] is the number of available CCEs in CFI N,
respectively. The number of available CCEs is calculated considering the CRS,
PCFICH, and PHICH resources based on the number of resource elements per
symbol number of the control region. The number of available CCEs per CFI is
described in the table below.

Confidential
Number of DL RBs 6 15 25 50 75 100

Number of UL RBs 6 15 25 50 75 100
CRS 1/2 4 1/2 4 1/2 4 1/2 4 1/2 4 1/2 4
CP Type N_G CFI
Normal 0.1667 1 2 1 2 2 4 4 10 10 15 15 20 20
2 4 3 7 5 13 10 26 21 40 32 54 43
3 6 5 12 10 21 18 43 37 65 57 87 76
0.5 1 2 1 2 2 4 4 9 9 14 14 19 19
2 4 3 7 5 12 10 26 20 39 31 52 41
3 6 5 12 10 21 18 42 37 64 56 86 75
1 1 2 1 2 2 3 3 8 8 12 12 17 17
2 4 3 7 5 12 9 25 19 37 29 50 39
3 6 5 12 10 20 17 41 36 62 54 84 73
2 1 2 1 1 1 2 2 6 6 9 9 13 13
2 4 3 6 4 11 8 23 17 34 26 46 35
3 6 5 11 9 19 16 39 34 59 51 80 69
Extended 0.1667 1 2 1 2 2 4 4 10 10 15 15 20 20
2 4 3 7 5 13 10 26 21 40 32 54 43
3 5 5 12 10 21 18 43 37 65 57 87 76
0.5 1 2 1 2 2 4 4 9 9 14 14 19 19
2 4 3 7 5 12 10 26 20 39 31 52 41
3 5 5 12 10 21 18 42 37 64 56 86 75
1 1 2 1 2 2 3 3 8 8 12 12 17 17
2 4 3 7 5 12 9 25 19 37 29 50 39
3 5 5 12 10 20 17 41 36 62 54 84 73
2 1 2 1 1 1 2 2 6 6 9 9 13 13
2 4 3 6 4 11 8 23 17 34 26 46 35
3 5 4 11 9 19 16 39 34 59 51 80 69
SYSTEM OPERATION
How To Activate
Preconditions

Confidential
• Run CHG-MACPDCCH-FUNC, and then set CFI_ADAPT_ENABLE to 1.
• Run CHG-MACPDCCH-FUNC, and then set CFI_ADAPT_ENABLE to 0.
Key Parameters
parameters.
Parameter Descriptions of CHG-MACPDCCH-FUNC/RTRV-MACPDCCH-FUNC
CFI_ADAPT_ENABLE This parameter is used to disable or enable the CFI adaptation.
• 0: Disable
• 1: Enable
parameters.
Parameter descriptions of CHG-MACPDCCH-FUNC/RTRV-MACPDCCH-FUNC
FIXED_OR_MIN_CFI This parameter indicates the fixed value of CFI when CFI adaptation is
disabled or the minimum value of CFI when CFI adaptation is enabled.
Counters and KPIs

Family Display Name Type Name Description
PDCCH Cfi1 The cumulated number of used CFI 1
Cfi2 The cumulated number of used CFI 2
REFERENCE

Confidential


Confidential
LTE-ME1002, CCE Aggregation for PDCCH

INTRODUCTION
A PDCCH carries a message known as Downlink Control Information (DCI),
which includes resource assignments and other control information for a UE or
group of UEs. In general, several PDCCHs can be transmitted in a subframe. Each
PDCCH is transmitted using one or more so-called Control Channel Elements
(CCEs), where each CCE corresponds to nine sets of four physical resource
elements known as Resource Element Groups (REGs). Four QPSK symbols are
mapped to each REG. The resource elements occupied by reference symbols are
not included within the REGs, which means that the total number of REGs in a
given OFDM symbol depends on whether cell-specific reference signals are
present. The concept of REGs (that is, mapping in groups of four resource
elements) is also used for the other downlink control channels (the PCFICH and
PHICH).
Four PDCCH formats are supported, as listed in the table below.
PDCCH Format Number of CCEs (N) Number of REGs Number of PDCCH bits
0 1 9 72
1 2 18 144
2 4 36 288
3 8 72 576
CCEs are numbered and used consecutively, and, to simplify the decoding process,
a PDCCH with a format consisting of n CCEs may only start with a CCE with a
number equal to a multiple of n. The number of CCEs used for transmission of a
particular PDCCH is determined by the eNB according to the channel conditions.
For example, if the PDCCH is intended for a UE with a good downlink channel
(for example, close to the eNB), then one CCE is likely to be sufficient. However,
for a UE with a poor channel (for example, near the cell border) then more CCEs
may be required to achieve sufficient robustness. In addition, the power level of a
PDCCH may be adjusted to match the channel conditions.
BENEFIT
• Cell capacity is increased in cases where all available PDCCH resources are
not needed.
• Subscribers may experience higher throughput in downlink in typical
scenarios with low load on PDCCH and high utilization of PDSCH.
DEPENDENCY
E-UTRAN (LTE)

Confidential
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The aggregation level of PDCCH is adaptively determined based on the channel
status of target UE to control PDCCH reception error rate as well as control
channel overhead.
Decision of CCE aggregation level: The aggregation level of PDCCH is
determined based on SINR_PDCCH of target UE. SINR_PDCCH is calculated by
using SINR_PDSCH which is used in link adaptation and ΔSINR_PDCCH which
is used to maintain PDCCH reception error rate lower than a target value (for
example, 1 %).
The SINR for PDCCH is used in

decision of aggregation level SINR_PDCCH = SINR_PDSCH + ΔSINR_PDCCH
Reception success ΔSINR_PDCCH = ΔSINR_PDCCH + OLRC_step * Target_reception_error_rate
Reception fail ΔSINR_PDCCH = ΔSINR_PDCCH + OLRC_step * (1-Target_reception_error_rate)
From obtained SINR_PDCCH and transition boundary, eNB searches the

aggregation level region where SINR_PDCCH belongs to. If SINR_PDCCH >
transition boundary (X, Y) and SINR_PDCCH <= transition boundary (Y, Z), then
the aggregation level of PDCCH is Y.
CCE aggregation and power boosting for PDCCH: In LTE specification, the
aggregation level of PDCCH, 1, 2, 4 and 8 are supported for UE specific search
space and those of 4 and 8 are supported for common search space. Common
search space is mainly used for the allocation of broadcast control message such as
SIB (System Information Block), RAR (Random Access Response) and paging.
Besides changing CCE aggregation level, the error rate of PDCCH reception can
be controlled by using power boosting of PDCCH. In Samsung LTE system,
instead of increasing aggregation level, CCE aggregation level power boosting is
used to reduce control channel overhead. It is beneficial to increase CCE
Confidential
utilization.
SYSTEM OPERATION
How to Activate
The aggregation level of PDCCH is automatically determined by the aggregation
level adaptation of scheduling operation and cannot be directly controlled by
operator.
Key Parameters
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME1005, Basic DCI Formats

INTRODUCTION
Among the control information in the downlink, the DCI is important as it carries
detailed control information for both downlink and uplink transmissions. The DCI
carries the downlink scheduling assignments, uplink scheduling grants, power
control commands, and other information necessary for the scheduled UEs to
decode and demodulate data symbols in the downlink or encode and modulate data
symbols in the uplink.
BENEFIT
To minimize the signaling overhead, it is desirable that several different message
formats are available. Each DCI contains the minimum payload required for a
particular scenario. For this motivation, several DCI formats are defined in the
standard.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The control channel messages are required to convey various pieces of
information, but the useful content depends on the specific case of system
deployment and operation. For example, if the infrastructure does not support
MIMO, or if a UE is configured in a transmission mode which does not involve
MIMO, there is no need to signal the parameters which are only required for
MIMO transmissions. To minimize the signaling overhead it is therefore desirable
that several different message formats are available. Each DCI contains the
minimum payload required for a particular scenario. However, to avoid too much
complexity in implementation and testing, it is desirable not to specify too many
formats.
DCI is mapped onto the PDCCH channel, and can be used to schedule uplink
resources on the PUSCH or downlink resources on the PDSCH. Alternatively, DCI
can be used to signal Transmit Power Control (TPC) commands for either the

Confidential
PUSCH or PUCCH. Each DCI format includes a 16bit CRC which is scrambled
by an RNTI.
The information content of the different DCI message formats is listed below.
Format 0
DCI Format 0 is used for the transmission of resource grants for the PUSCH. The
following information is transmitted:
• Flag to differentiate between Format 0 and Format 1A
• Resource block assignment
• Modulation and coding scheme
• HARQ information and redundancy version
• Power control command for scheduled PUSCH
• Request for transmission of an aperiodic CQI report
Format 1
DCI Format 1 is used for the transmission of resource assignments for single
codeword PDSCH transmissions (transmission modes 1, 2 and 7). The following
information is transmitted:
• Resource allocation type
• HARQ information
• Power control command for Physical Uplink Control Channel (PUCCH).
Format 1A
DCI Format 1A is used for compact signaling of resource assignments for single
codeword PDSCH transmissions, and for allocating a dedicated preamble
signature to a UE for non-contention based random access. The following
information is transmitted:
• Flag to differentiate between Format 0 and Format 1A
• Flag to indicate that the distributed mapping mode is used for the PDSCH
transmission (otherwise the allocation is a contiguous set of physical resource
blocks). Note that distributed mapping mode is not supported
• Power control command for PUCCH.

Confidential
Format 2
DCI Format 2 is used for the transmission of resource assignments for PDSCH for
closed-loop MIMO operation (transmission mode 4). The following information is
transmitted:
• Resource allocation type
• Power control command for PUCCH
• Modulation and coding schemes for each codeword
• Number of spatial layers
• Precoding information.
Format 2A
DCI Format 2A is used for the transmission of resource assignments for PDSCH
for open-loop MIMO operation (transmission mode 3). The information
transmitted is the same as for Format 2, except that if the eNB has two transmit
antenna ports, there is no precoding information, and for four antenna ports two
bits are used to indicate the transmission rank.
Format 3
DCI Format 3 is used for the transmission of Transmission Power Control (TPC)
commands for the PUCCH and PUSCH with 2bit power adjustments.
SYSTEM OPERATION
How to Activate
The DCI format is automatically determined by scheduler according to the content
of PDCCH at the corresponding subframe and the configured transmission mode.
Key Parameters
Counters and KPIs

with this feature.

Confidential
REFERENCE
[1] 3GPP TS 36.201 “Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical layer; General description”
Physical Channels and Modulation”
Multiplexing and channel coding”
[4] 3GPP TS 36.300 “Evolved Universal Terrestrial Radio Access (E-UTRA) and
description; Stage 2”

Confidential
LTE-ME1101, PDSCH Resource Allocation

INTRODUCTION
In SC-FDMA or OFDM system, the frequency-domain resource allocation
information needs to be signaled to the UE. Because of the large number of
resource blocks within the frequency band, the resource allocation is one of the
largest fields in the downlink control information. In the case of SC-FDMA
uplink, the allocated resource blocks need to be contiguous to guarantee single-
carrier property. While the contiguous resource allocation can be signaled with the
minimum of signaling bits, it also results in limiting the scheduling flexibility. In
the case of OFDM, non-contiguous resource blocks can be allocated thus
providing maximum scheduling flexibility. However, the signaling overhead also
increases for non-contiguous resource block allocation. To provide various choices
of scheduling performance and signaling overhead, multiple resource allocation
types are defined. A contiguous resource allocation scheme is defined for both and
the uplink and the downlink. As pointed out earlier, a contiguous resource
allocation is necessary in the uplink due to single-carrier access. In the downlink,
contiguous resource allocation provides a low overhead alternative while limiting
scheduling flexibility, In addition to contiguous resource allocation, two types of
non-contiguous resource allocation using a bitmap-based signaling are defined for
the downlink.
BENEFIT
Enable to enhance a flexibility in spreading the resources across the frequency
domain to exploit frequency diversity.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
3GPP LTE defines three downlink resource allocation types as follows:

Confidential
Downlink Resource Allocation Type 0

• A type 0 downlink Resource Block allocation can be signaled from the eNB to
the UE using Downlink Control Information (DCI) format 1, 2, 2A.
• An allocation received during downlink subframe ‘n’ defined the allocated
Resource Blocks within the same downlink subframe.
• A type 0 Resource Block allocation uses a bitmap to indicate which Resource
Block Groups (RBG) are allocated to the UE. A single RBG is a set of
consecutive Resource Blocks. The allocated RBG do not need to be
contiguous.
• The number of Resource Blocks within an RBG is predetermined and is a
function of the channel bandwidth.
• PDSCH is not assigned to legacy UEs using type 0 RB allocation if the RBs to
be allocated are included in the RBG which includes the RB reserved for
eMTC.
The RBG size as a function of the channel bandwidth is shown in the table below.
Item 5 MHz 10 MHz 15 MHz 20 MHz
Total Number of Resource Blocks 25 50 75 100
RBG Size (RB) 2 3 4 4
Number of complete RBG 12 16 18 25
Size of remaining RBG 1 2 3 -
Total Number of RBG 13 17 19 25
Size of bitmap (bits) 13 17 19 25
• Each channel bandwidth includes a number of complete RBG. A partial RBG

is also included if the total number of Resource Block is not a multiple of the
RBG size.
• The bitmap signaled using the Type 0 Resource Block allocation includes a
single bit for each RBG. A value of 1 indicates that the RBG has been
allocated to the UE.
The following figure illustrates the RBG for the channel bandwidth of 5MHz.

the UE using Downlink Control Information (DCI) format 1, 2, 2A. An

Confidential
allocation received during downlink subframe ‘n’ defined the allocated

• Type 1 Resource Block allocations are not applicable to the 1.4 MHz channel
bandwidth.
• Type 1 Resource Block allocations are divided into 3 sections: Resource Block
Group (RBG) subset number, Resource Block offset flag, Resource Block
bitmap.
• The RBG sizes are the same as those specified for a Type 0 Resource Block
allocation. The number of RBG subsets is equal to the RBG size.
The RBG size and the number of RBG subsets for each channel bandwidth are
shown in the table below.
Item 5 MHz 10 MHz 15 MHz 20 MHz
Total Number of Resource Blocks 25 50 75 100
RBG Size (RB) 2 3 4 4
Number of complete RBG 2 3 4 4
Size of remaining RBG 1 2 2 2
Total Number of RBG 1 1 1 1
Size of bitmap (bits) 11 14 16 22
• The number of bits used to signal the RBG subset is either 1 or 2 depending on
the number of subsets. The Resource Blocks allocated to a UE always belong
to a single RBG subset.
• The Resource Block offset flag indicates whether the subsequent Resource
Block bitmap should be aligned with the bottom of the lowest Resource Block
within the subset, or aligned with the top of the highest Resource Block within
the subset. This offset is necessary because the bit map is not sufficiently large
to include all Resource Blocks within the subset.
• PDSCH is not assigned to legacy UEs using type 1 RB allocation for the RB
reserved for eMTC.

the UE using Downlink Control Information (DCI) format 1A.
• An allocation received during downlink subframe ‘n’ defined the allocated
• The set of allocated virtual Resource Blocks are mapped onto the set of
allocated physical Resource Blocks.
• Contiguous virtual Resource Blocks are contiguous both before and after
mapping onto their physical Resource Blocks. In this case, the set of allocated
physical Resource Blocks is the same as the set of allocated virtual Resource
Blocks. In addition, the Resource Block allocation is the same in both time
slots belonging to the subframe.

Confidential
• Contiguous allocations can range from a single virtual Resource Block to the
complete set of virtual Resource Blocks spanning the entire channel
bandwidth.
• Contiguous virtual Resource Block allocation is signaled using Resource
Indication Values (RIV). The calculation of the RIV is the same as when
calculating the RIV for type 0 uplink resource allocations.
• PDSCH is not assigned to legacy UEs using type 2 RB allocation for the RB
reserved for eMTC.
Allocation scenario for Resource Allocation Type 0/1/2:

Samsung eNB supports RA Type0, RA Type1 and RA Type2 with localized
VRBs. For transmissions with DCI 1A grant, RA Type2 with localized VRBs is
used. For transmissions with DCI 1, 2, 2A, 2C grant, either RA Type0 or RA
Type1 is decided based on the following conditions:
• Paging, RAR, SIB and CCCH are transmitted on RA Type2 with localized
VRBs.
• All traffic except paging, RAR, SIB, CCCH are transmitted on RA Type0 or 1.
o To prevent TM/DCI mismatch from happening between eNB and UE, RA
Type2 with DCI 1A is exceptionally used during a call setup and hand-
over procedure.
• Only small packets with buffer size less than 2RBG are transmitted on RA
Type1.
o RA Type 1 is used when the number of required RB in consideration of
buffer occupancy is less than 2RBG and allocated RBs are available in any
of the subsets of RA Type1.
Counters
A number of counters are provided to show DL PRB usage in a cell. PrbDLAvg
counter in PRB_QCI family shows the average PRB usage per cell per QCI for
transmitting DL DTCH traffic. TotPrbDLAvg, TotGbrPrbDLAvg, and
TotNGbrPrbDLAvg counters in PRB_TOTAL family show the average DL PRB
usage per cell, average DL PRB usage per cell for GBR traffic, and average DL
PRB usage per cell for NGBR traffic, respectively. Minimum and maximum DL
PRB usage counters are also provided. Refer to Samsung eNB counter description
manual for detailed information about PRB usage counters.
SYSTEM OPERATION
How to Activate
Samsung scheduler determines the PDSCH resource allocation type automatically
based on the DCI format and the traffic type. The operator cannot control this.

Confidential
Key Parameters
Counters and KPIs

PRB Usage PrbDLAvg This counter is cumulated Average PRB usage per
cell per QCI for transmitting DL DTCH traffic
Total PRB Usage TotPrbDLAvg This counter is cumulated Average DL PRB usage
per cell
TotGbrPrbDLAvg This counter is cumulated Average DL PRB usage
per cell for GBR traffic
TotNGbrPrbDLAvg This counter is cumulated Average DL PRB usage
per cell for NGBR traffic
Air MAC Packet AirMacDLByte This counter is cumulated by the number of bytes
of the MAC PDU when there is a MAC PDU that
has successfully transmitted through the PDSCH.
AirMacDLByteCnt The counter is cumulated by 1 when the
AirMacDLByte is collected.
AirMacDLTti This counter is cumulated by 1 when there is a
MAC PDU that has successfully transmitted
through the PDSCH at each TTI.
AirMacDLThruAvg This counter is calculated when measurement
period comes.
AirMacDLEfctivThruAvg This counter is calculated when measurement
period comes.
AirMacDLByteCurr This counter is updated when the AirMacDLByte
collected
AirMacDLThruMin This counter is updated when AirMacDLThru is
smaller than previous value.
AirMacDLThruMax This counter is updated when AirMacDLThru is
greater than previous value.
REFERENCE

Confidential
LTE-ME1503, PUSCH Frequency Hopping

INTRODUCTION
Uplink resource blocks allocated by type 0 resource allocations are always
contiguous. This helps to reduce the peak-to-average ratio of the transmitted signal
and consequently improves the transmit power amplifier efficiency. A drawback of
contiguous allocation is reduced potential for frequency diversity. Allocating a
small number of resource blocks means that the resource allocation spans only a
small bandwidth and the propagation channel is relatively well correlated for all
resource blocks within the allocation.
Allocating a large number of resource blocks increases the potential for frequency
diversity because the resource allocation spans a wider bandwidth.
Uplink frequency hopping provides frequency diversity while allowing the
resource allocations to remain contiguous. This is particularly beneficial to small
resource block allocations which do not inherently benefit from frequency
diversity. Uplink frequency hopping is applicable to type 0 resource allocations
when the frequency hopping flag within DCI format 0 is set to 1.
BENEFIT
Frequency diversity effects can be exploited and interference can be averaged.
DEPENDENCY
E-UTRAN (LTE). When hopping is used, the resource block allocation field
within DCI format 0 includes either 1 or 2 hopping bits. The number of bits is
dependent on the channel bandwidth.
LIMITATION
• Frequency hopping is not applied to type 1 resource allocations, nor to any
uplink resource allocation made using DCI format 4.
• Samsung eNB supports Type2 PUSCH hopping with inter-subframe mode
only.
SYSTEM IMPACT
FEATURE DESCRIPTION
The resource mapper maps the complex-valued modulation symbols in sequence
on to the physical resource blocks assigned for transmission of PUSCH. In LTE,

Confidential
only localized resource allocation is supported in the uplink due to its robustness to
frequency offset compared to distributed resource allocation. Localized resource
allocation also retains the single-carrier property in the uplink transmission. As a
consequence, there is very little frequency diversity gain. On the contrary, in the
downlink it is possible to allocate disjoint sets of resource blocks to a UE to extract
some frequency diversity gain. To alleviate this issue, LTE supports frequency
hopping on PUSCH, which provides additional frequency diversity gain in the
uplink. Frequency hopping can also provide interference averaging when the
system is not 100 % loaded. The PUSCH frequency hopping operation is restricted
for the VoLTE calls with coverage extension purpose under the condition of TTI
bundling enabled.
PUSCH frequency hopping consists of inter-subframe mode and intra-and-inter
subframe mode. In each mode, Type-1 hopping and Type-2 hopping can be
independently operated. Type-2 hopping supports mirroring, which is a
functionality non-supported by Type-1 hopping patterns. Mirroring is a symmetric
hopping pattern of PRB location based on the center frequency.
Samsung eNB support Type-2 PUSCH frequency hopping only since there is no
performance gap in terms of BLER between Type-1 and Type-2 PUSCH
frequency hopping, in addition, Type-2 PUSCH frequency hopping supports
mirroring pattern which reduces non-contiguous segments due to PUSCH hopping.
Type 2 PUSCH Hopping

Hopping mode is determined via cell common parameters in cell processing block
and transmitted to UE, and MAC can operate either Type-1 or Type2 hopping,
based on the given condition.
In inter-subframe hopping mode, the allocated RB is retained in its location within
the slot, but PRB location changes only on re-transmission timing. On the other
hand, in intra-and-inter subframe hopping mode, PRB location changes between
slots. Therefore, intra-and-inter subframe hopping mode has lower performance
gains compared to inter-subframe hopping, since PRB location within the
subframe is changed, which leads to channel estimation performance degradation.

Confidential
Samsung’s UL scheduler only operates inter-subframe mode.

The figure below gives an example of mirroring. Configuring a single subband
represents a special case which generates ‘mirroring’ of the resource block
allocation around the center of the channel bandwidth. The following figure shows
Type 2 hopping with single subband in 5 MHz channel bandwidth (Mirroring).
PUSCH frequency hopping is particularly beneficial to small size of PRB

allocations since channel coherency is well-maintained in a narrow frequency
band. In general, the small PRB size is needed for VoLTE UEs due to small BSR
(small packet size).
In addition, according to 3GPP spec., the PRB size in TTI bundling should be
limited up to 3 PRBs, irrelative to BSR, which is proper to obtain frequency
diversity gain applying PUSCH frequency hopping. PUSCH frequency hopping is
applicable to TTI bundling to enhance VoLTE coverage. TTI bundling is activated
for VoLTE UEs that experiences poor RF condition. As shown in the figure below,
PRB position within TTI bundle is changed according to the mirroring pattern.

Confidential
The PUSCH frequency hopping is activated when

PUSCH_HOPPING_ENABLED (CHG-PUSCH-CONF) is set to TRUE.
SYSTEM OPERATION
How to Activate
Preconditions
QCI1 (VoLTE) bearer has been set up for the corresponding UE.
Run CHG-PUSCH-CONF and set PUSCH_HOPPING_ENABLED to enable
PUSCH frequency hopping.
Run CHG-PUSCH-CONF and set PUSCH_HOPPING_ENABLED to disable
PUSCH frequency hopping.
Key Parameters
parameters.
Parameter Description of CHG-PUSCH-CONF/RTRV-PUSCH-CONF
PUSCH_HOPPING_ENABLED PUSCH freq. hopping can be enabled or disabled by this parameter.

Confidential
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME1504, PUCCH Format

INTRODUCTION
The amount of control information which a UE can transmit in a subframe depends
on the number of SC-FDMA symbols available for transmission of control
signaling data (that is, excluding SC-FDMA symbols used for reference signal
transmission for coherent detection of the PUCCH). The PUCCH supports
different formats depending on the information to be signaled.
BENEFIT
• Minimizes resources needed for transmission of control signaling.
• Maintains the cell radius in Band 13 by relocating PUCCH to the center of the
uplink channel.
DEPENDENCY
• Others: The PUCCH format 1b with channel selection and PUCCH format 3
are used only when Carrier Aggregation (CA) is enabled.
LIMITATION
If PUCCH is located in the center of the uplink channel in Band 13, the peak
uplink throughput for a single UE can be reduced by half.
SYSTEM IMPACT
FEATURE DESCRIPTION
The following topics are discussed in this section:
• PUCCH formats 1, 1A, 1B, 2, 2A, 2B, and 3
• Location change of PUCCH between edge and center of the uplink channel for
Band 13
PUCCH Format
The Physical Uplink Control Channel (PUCCH) is used to transfer Uplink Control
Information (UCI). The UCI can be transferred using PUSCH.
The release 8 and 9 versions of 3GPP specifications do not allow an individual UE
to transmit both PUCCH and PUSCH during the same subframe. If a release 8 and
9 UE has application data or RRC signaling to send then UCI is transferred to
Confidential
using PUSCH. A release 8 and 9 UE transfer UCI by using PUCCH if it does not
have any application data or RRC signaling to transfer.
3GPP TS 36.211 and TS 36.213 specify the seven PUCCH formats presented in
table below. PUCCH formats 2a and 2b are not applicable when using the
extended cyclic prefix.
The information transferred by each PUCCH format is listed in the table below.
PUCCH format Number of Bits per FDD/TDD Normal CP Extended CP
Subframe
1 - FDD & TDD Scheduling Request (SR)
1a 1 FDD & TDD 1 x HARQ-ACK
FDD only 1 x HARQ-ACK + SR
1b 2 FDD & TDD 2 x HARQ-ACK or 2 x HARQ-ACK + SR
TDD only Up to 4 x HARQ-ACK with channel
selection
2 20 FDD & TDD CSI report CSI report or CSI
report + up to 2 x
HARQ-ACK
2a 21 FDD & TDD CSI report + 1 x Not Applicable
HARQ-ACK
2b 22 FDD & TDD CSI report + 2 x
HARQ-ACK
3 48 FDD up to 10 x HARQ-ACK, or
up to 10 x HARQ-ACK + SR
TDD up to 20 x HARQ-ACK, or
up to 20 x HARQ-ACK + SR
The PUCCH is able to transfer various combinations of Scheduling Requests (SR),

Hybrid Automatic Repeat request (HARQ) acknowledgements, and Channel State
Information (CSI) reports. The CSI reports can include Channel Quality Indicators
(CQI), Precoding Matrix Indicators (PMI), and Rank Indicators (RI).
In summary:
• PUCCH formats 1, 1a, and 1b transfer HARQ acknowledgements and SRs.
• PUCCH formats 2, 2a, and 2b transfer HARQ acknowledgements and CSI
reports.
• PUCCH format 3 transfers the increased number of HARQ acknowledgements
associated with CA and SR.
• When CA is used, HARQ acknowledgements of multiple serving cells can be
transmitted by using PUCCH format 1b (at most two serving cells) or PUCCH
format 3. When PUCCH format 1b with channel selection is used, two to four
PUCCH resources are allocated and UE transmits PUCCH format 1b on one of
those resources.
The modulation scheme and the number of Resource Elements occupied by each
PUCCH format are presented in table below.

Confidential
PUCCH Format Number of Bits per Modulation Scheme Number of Resource Elements Occupied
Subframe
Normal CP Extended CP
1 - - 48 + 48 = 96 or 48 + 36 = 84
1a 1 BPSK
1b 2 QPSK
2 20 QPSK 60 + 60 = 120
2a 21 QPSK + BPSK 60 + 60 = 120 Not Applicable
2b 22 QPSK + BPSK
3 48 QPSK 60 + 60 = 120 or 60 + 48 = 108
A single PUCCH transmission always occupies two Resource Blocks (RBs),

which are distributed across the two time slots belonging to a subframe.
Each pair of RBs allocated to the PUCCH can be used simultaneously by multiple
UE. The use of different cyclic shifts and different orthogonal spreading codes
allows the eNB to differentiate PUCCH transmissions from multiple UE sharing
pair of RBs.
In Samsung LTE system, numbers of PUCCH RBs are semi-statically determined
according to the tables below and the number of UEs.
In 3CC CA, PUCCH Format 3 is used for SCell ACK/NACK transmission.
System parameter, nFormat3RB, is used to determine the RB number used for
Format3.
PUCCH Relocation for NS-07 Support

Power leakage out of the transmission bandwidth of Band 13 can cause
interference to neighboring public safety spectrum. The eNB operating on Band 13
can signal additional spectrum emission requirements to indicate that the UE meets
additional requirements in a specific deployment scenario, by using NS-07. To
meet these additional requirements, Additional Maximum Power Reduction (A-
MPR) is allowed for the output power, as per 3GPP TS 36.101: User Equipment
(UE) radio transmission and reception. The cell radius is impacted because NS-07
specifies different A-MPR value of each side of PUCCH resource which is located
at the edge of the uplink channel.
To maintain the cell radius, for Band 13, the eNB can relocate PUCCH to the
center of the uplink channel, instead of at the edge. The location of the PUCCH
can be changed through manual configuration.
If PUCCH resources are located at the edge of the uplink channel, PUCCH
resources are increased to a center as the number of UEs increases.
If PUCCH resources are located at the center of the uplink channel, PUCCH
resources for formats 2 and 3 are increased to edges as the number of UEs
increases. However, according to the standard, it is necessary to use the fixed size
of PUCCH resources for format 1 to support the maximum number of UEs in a
cell.

Confidential
The PUSCH must be allocated to the UE in a contiguous chunk. Relocating the

PUCCH to the center results in fragmentation of the resource blocks available for
the PUSCH, and reduces the peak uplink throughput for a single UE.
Figure below depicts the PUCCH located in the edge and center.
Band 13 (700 MHz)
PUCCH (Control Channel)

PUCCH (Control Channel) PUCCH (Control Channel)
PUSCH PUSCH
PUSCH (Traffic Channel) (Traffic Channel) (Traffic Channel)
Direction of PUCCH RB increase Direction of PUCCH RB increase Direction of PUCCH RB increase Direction of PUCCH RB increase
PUCCH located in the edge PUCCH located in the Center
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-ULRESCONF-IDLE/RTRV-ULRESCONF-IDLE
RESOURCE_TABLE_USAGE This parameter is used to determine which UL resource table is used, when
more than one UL resource tables reflecting operator’s request are

Confidential
provided.
START_STATE_IDX This parameter is the start state index of PUCCH/SRS resource allocation
table.
Parameter Descriptions of CHG-PUCCHCONF-IDLE/RTRV-PUCCHCONF-IDLE

FORCED_MODE This parameter is forced mode for changed value. By setting this to True,
the corresponding change command can be executed irrespective of the
lock status of cell.
False: Disable forced mode. Set the value considering the cell status.
True: Enable forced mode. Set the value without considering the cell
status.
CA_CSI_ACK_USAGE This parameter determines whether additional CSI SCell HARQ-ACK
resources for CA is used or not
FORMAT3_ACK_USAGE This parameter determines whether the HARQ-ACK resources with
PUCCH format 3 is used or not
PUCCH_CENTER_MODE This parameter defines "PUCCH Mode".
'0' = Edge mode, '1' = Center mode
Counters and KPIs

this feature.
Total PRB Usage TotPucchPrbULAvg The average use rate for PRBs used to
transmit PUCCH during the collection interval.
TotUsedPucchPrbULNu The number of PRBs used to receive the
m PUCCH during the collection interval.
TotPucchPuschPrbULAv The average use rate for PRBs used to receive
g the PUCCH/PUSCH for the uplink during the
REFERENCE

Confidential
LTE-ME3001, Power Control

INTRODUCTION
The transmit power of the UE can be adjusted through the system parameter
setting for PUCCH and PUSCH. There are two types of power controls for
PUCCH and PUSCH, open-loop and closed-loop. In open-loop power control, UE
performs the power control of PUCCH based on the system parameters setting and
RSRP measurement. In close-loop power control, eNB supports the power control
of PUSCH and PUCCH by sending Transmit Power Commands (TPCs) to UE.
The eNB can adjust the PUSCH transmit power of UE for improving cell
throughput, expanding coverage through interference mitigation or guaranteeing a
proper reception level to satisfy the specific service. eNB can adjust the PUCCH
transmit power of UE for satisfying the target SINR which guarantees the stable
ACK or CQI reception.
BENEFIT
• Improve the cell throughput or expand coverage according to the operating
environment through the close-loop power control.
• Prevent the unnecessary power consumption of the UE maintaining the
connection to serving eNB.
DEPENDENCY
E-UTRAN (LTE)
• Others
No eNB or UE dependency on this feature
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
Improve the cell throughput according to the operating environment.

Confidential
Coverage
Expand the cell coverage according to the operating environment.
Interfaces
None
FEATURE DESCRIPTION
The transmission power of the UE is performed for PUSCH and PUCCH. For
PUSCH, open-loop power control and closed-loop power control are supported.
For PUCCH, closed-loop power control is supported.
PUSCH
In the LTE uplink, the PUSCH transmission power of the UE is under the
following formula as defined in the TS 36.213[1] standard:
(1)
• Pcmax: The maximum power of UE (dBm)

• M_PUSCH (i): No. of PUSCH RBs to transmit in subframe i
• Po_PUSCH: The target value of reception power of PUSCH (dBm). Sum of
P0_NOMINAL_PUSCH and P0_UE_PUSCH for non-SPS or Sum of
P0_NOMINAL_PUSCHPERSISITENT and P0_UE_PUSCHPERSISENT for
SPS.
• alpha: A constant ALPHA deciding the compensation percentage of PL
• PL: The downlink pathloss measured by the UE (dB)
• f (i): The accumulated or absolute value of TPC command received from the
base station based on ACCUMULATION_ENABLED ON/OFF.
The LTE uplink power control may be largely divided into Open-Loop Power
Control (OLPC) and Closed-Loop Power Control (CLPC) and the main features
are as shown below. The activation of the OLPC or CLPC for PUSCH can be
controlled by configuring parameter ACCMULATION_ENABLED (CHG-
ULPWR-CTRL).
Open-Loop Power Control (OLPC)

When ACCMULATION_ENABLED (CHG-ULPWR-CTRL) = OFF, eNB uses
only OLPC for UE power control.
In the LTE uplink, the UE decides the initial transmission power according to the
OLPC and changes the transmission power according to TPC power control
obtained from the eNB. In the OLPC eNB does not determine the target SINR for
each UE. The UE decides transmission power according to formula (1) by
estimating the pathloss between the eNB and the UE, which is obtained by using
the difference between the transmission power and reception power of the
Reference Signal (RS). The transmission power of RS can be identified through
SIB, a broadcast message transmitted from the eNB. In short, the value reflected to

Confidential
the transmission power of the uplink is based on the pathloss of the downlink. And
this pathloss may not be fully compensated according to the alpha value of
Formula (1). In the specifications, eight values including 0, 0.4, 0.5, 0.6, 0.7, 0.8,
0.9, and 1.0 are defined. If the alpha is 0, no pathloss is compensated and if it is 1,
pathloss is fully compensated. This can be controlled by configuring parameter
ALPHA (CHG-PWR-PARA) and default value is 0.8.
If all pathlosses are compensated, unless the UE has the lack of the power, the
signals of all UEs received at the eNB have the same intensity (without fading or
in the long term perspective). If partial compensation is applied, it is possible to
mitigate interference between cells by reducing the transmission power of the UE
in the cell edge area. Also partial compensation increases the SINR of the UE in
the cell-center area relatively higher than the SINR in the cell-middle or cell-edge
areas. Accordingly, this has the advantage to increase cell throughputs.
Closed Loop Power Control (CLPC)

When ACCMULATION_ENABLED (CHG-ULPWR-CTRL) = ON, eNB uses
only CLPC for UE power control.
In the LTE, the eNB can control the transmission power of the UE by transmitting
the TPC (transmit power control) command. The TPC command can be
transmitted to the UE through PDCCH DCI format 0, and the UE reflects the
received TPC command value to the f (i) of Formula (1). The TPC command value
received from the eNB may be applied by accumulating the received value in
accumulated mode. The method for controlling the uplink transmission power of
the UE from the eNB is called Closed Loop Power Control (CLPC) and the main
purposes are as follows:
Maximization of the cell throughput
Throughput maximization means TBS (Transport Block Size) maximization for
each TTI, and this TBS is decided by the combination of number of RB and MCS
as in the specifications. RB size and MCS are affected by PUSCH power control.
For example, if a transmit power per RB increases, allocable number of RB
reduces but MCS may increase. In contrast, if transmit power per RB decreases,
allocable number of RB increases but MCS may decrease. The UL scheduler will
maximize TBS size based on available power and buffer condition of the UE
which can be obtained from PHR (power headroom report) and the BSR (buffer
status report), respectively. UL scheduler will determine possible combinations of
PRB size and MCS based on TBS table, and adjust the transmit power to achieve
the maximum TBS. This functionality is applied to the UEs with large non-GBR
buffer size.
For example, Target SINR is to maximize cell throughput as follows.
• Case1) Low PRB usage or only single large non-GBR buffer UE
o Case 1-1) UE in cell centric region
When the UE’s Tx power is less than maximum power, the UE’s target
SINR can increase or stay according to current MCS level. If MCS does
not reach MaxMCS, target SINR can be increased by 1 dB.

Confidential
o Case 1-2) UE in cell middle/edge region

When the UE’s Tx power reaches maximum power, the UE’s target SINR
can decrease by 1 dB, and it leads to a lower MCS and a lager RB size to
increase TBS.
• Case2) high PRB usage and multiple large non-GBR buffer UEs
o A and B are in cell-edge and cell-centric region, respectively
o A’s Tx power reaches maximum power. A’s target SINR increases, and it
leads to a higher MCS and a smaller RB size.
o B’s Tx power is not maximum power, B’s target SINR increases or stay
according to current MCS level.
If MCS does not reach MaxMCS, target SINR can increase. B can take more
resource after CLPC.
Inter-cell interference reduction

UL scheduler determines the dominant interfering UEs to neighbor cells and
decreases their transmit power. This functionality mitigates the inter-cell
interference, thus it increases the cell-edge UE’s performance and expands the
cell-coverage in interference-limited network environment. It is applied to non-

Confidential
GBR service UEs. VoLTE service UE is excluded from this functionality to

preserve the service quality. The interference reduction can be controlled by
configuring parameter IOT_REDUCTION_SINR_MARGIN (CHG-PWR-PARA).
Guarantee of properly received SINR: If the UE has unnecessarily high
transmission power and received SINR exceeds the required SINR of the
maximum MCS, eNB decreases the UE's transmission power. Or if it fails to
satisfy the required SINR based on the minimum MCS or the target MCS of the
specific service, the transmission power of the UE is increased for stable reception
of PUSCH.
The dominant UL interferers are in the sector edge and they typically have a
higher UL SINR but a lower DL SINR. So, the Interference Reduction decreases
the target SINR when it exceeds the threshold value, which corresponds to each
UE’s DL SINR + IOT_REDUCTION_SINR_MARGIN which has 0.1 dB
resolution. IOT_REDUCTION_SINR_MARGIN is additionally applied to DL
SINR because the UL capacity is degraded while the cell-edge UE’s performance
can be enhanced by Interference Reduction.
Target SINR decision is as follows:

• Target SINR = OLPC SINR + PowerOffset
OLPC SINR is based on OLPC and Power offset is based on the operation of
the Maximization of cell throughput or the Interference Reduction.
OLPC SINR calculation is as follows:
• OLPC SINR = Target Rx power - NI
= Po_PUSCH - (1-ALPHA) * PL - NI
NI is measured value per RB and Po_PUSCH = P0_NOMINAL_PUSCH +
P0_UE_PUSCH for non-SPS or P0_NOMINAL_PUSCHPERSISITENT +
P0_UE_PUSCHPERSISENT for SPS.
For example, the following figure shows OLPC SINR vs pathloss for alpha 0.8,
assuming NI of -118 dBm (IoT 3 dB). The higher Po_PUSCH, the higher SINR,
Higher UL Throughput is achieved but interference may be increased to neighbor
cell. Max. target SINR and min. target OLPC SINR aren’t configurable.

Confidential
PowerOffset Update is as follows. PowerOffset is updated, when

UL_PWR_CTRL_TYPE is set to TRUE.
• For Volte UE, PowerOffset is always 0 because Maximization of the cell
throughput and Interference Reduction aren’t applied. Therefore Target SINR
is determined by OLPC SINR depends on Po_PUSCH
((P0_NOMINAL_PUSCH + P0_UE_PUSCH for non-SPS) or
(P0_NOMINAL_PUSCHPERSISITENT + P0_UE_PUSCHPERSISENT for
SPS)), ALPHA, pathloss and NI. The OLPC SINR corresponds to blue-line in
the figure below.
• For non-volte and UL small non-GBR traffic UE, PowerOffset can be less
than or equal to 0 by Interference Reduction. Therefore Target SINR can be
less than or equal to OLPC SINR. The light green-line and red-line in the
figure below show that target SINR is decreased based on DL SINR +
IOT_REDUCTION_SINR_MARGIN. When target SINR is greater than DL
SINR + IOT_REDUCTION_SINR_MARGIN and min. target SINR,
PowerOffset is decreased by 1 dB. Min. target SINR can be configurable.

Confidential
• For non-volte and UL large non-GBR traffic UE, PowerOffset can be

increased or decreased by Maximization of the cell throughput or Interference
Reduction. But the Interference Reduction is applied only for exceptional
condition not to degrade UL throughput. The exceptional case is when NI per
RB exceeds -105 dBm in a cell. In that case, Interference Reduction is applied
to all non-volte and UL large non-GBR traffic UEs.
PoweOffset is increased in the above case 1-1) and case 2). But PoweOffset is
decreased in the above case 1-2).
PUCCH
The purpose of the power control of PUCCH channel is to guarantee the stabilized
reception of each PUCCH format that is transmitted by the UE. The UE's output
power of PUCCH is decided as follows under the TS 36.213[1] standard:
• Pcmax: The maximum power of UE (dBm)

• h (n_CQI, n_HARQ): number of information bit for CQI or HARQ.
• Po_PUCCH: The target value of reception power of PUSCH (dBm).
Po_nominalPUSCH.
• PL: The downlink pathloss measured by the UE (dB)
• delta_F: The transmission power offset values of other formats compared to
the PUCCH format 1a standard.
• g (i): The accumulated value of the TPC command received from the base
station.

Confidential
Differently from PUSCH, PUCCH compensates all pathlosses measured by the UE

and the number of RB is also set to be 1. In addition, the transmission power is
decided depending on the number of transmission information bits. The eNB
transmits the TPC command to the UE to make the received SINR close to target
SINR. The scheduler generates the TPC command for PUCCH periodically, and it
is transmitted to the UE through the DL assignment.
SYSTEM OPERATION
How to Activate
Preconditions
PUCCH power control is enabled and cannot be disabled by operator.
Operator can choose whether to use open loop power control or closed loop power
control for PUSCH.
• To activate the OLPC for PUSCH, do the following:
Run CHG-ULPWR-CTRL, and then set ACCUMULATION_ENABLED to 0
(FALSE).
• To activate the CLPC for PUSCH, do the following:
Run CHG-ULPWR-CTRL, and then set ACCUMULATION_ENABLED to 1
(TRUE).
PUCCH power control is enabled and cannot be disabled by operator.
PUSCH power control is enabled and operator can choose whether to use OLPC or
CLPC.
Key Parameters
parameters.
Parameter Descriptions of CHG-PWR-PARA/RTRV-PWR-PARA

Confidential
supported by the system. It is determined by FA/Sector. For example, if the maximum
capacity system is 1 FA/3 Sector, up to 3 cells are supported.
P0_NOMINAL_PUSC PUSCH Initial Power value. p0NominalPUSCH value is used in PUSCH power
H control and provided from higher layers. This field is applicable for non-persistent
scheduling, only.
ALPHA Pathloss compensation factor for PUSCH/SRS transmit power of UE. al0
corresponds to 0, al04 to 0.4 and so on.
P0_NOMINAL_PUCC PUCCH Initial Power value. p0Nominal PUCCH value is used in PUCCH power
H control and provided from higher layers.
DELTA_FPUCCHFOR The PUCCH format 1 transmits power offset comparing to that of PUCCH format1a.
MAT1 deltaF_2 corresponds to -2 dB, deltaF0 to 0 dB and deltaF2 to 2 dB, respectively.
DELTA_FPUCCHFOR The PUCCH format 1b transmits power offset comparing to that of PUCCH format1a.
MAT1_B deltaF1 corresponds to 1 dB, deltaF3 to 3 dB and deltaF5 to 5 dB, respectively.
DELTA_FPUCCHFOR The PUCCH format2 transmits power offset comparing to that of PUCCH format1a.
MAT2 deltaF_2 corresponds to -2 dB, deltaF0 to 0 dB, deltaF1 to 1 dB and deltaF2 to 2 dB,
respectively.
DELTA_FPUCCHFOR The PUCCH format2a transmits power offset comparing to that of PUCCH format1a.
MAT2_A deltaF_2 corresponds to -2 dB, deltaF0 to 0 dB and deltaF2 to 2 dB, respectively.
DELTA_FPUCCHFOR The PUCCH format2b transmits power offset comparing to that of PUCCH format1a.
MAT2_B deltaF_2 corresponds to -2 dB, deltaF0 to 0 dB and deltaF2 to 2 dB, respectively.
DELTA_PREAMBLE_ Msg3 transmits power offset comparing to preamble initial target power
MSG3 (preambleInitialReceivedTargetPower in 3GPP TS 36.331). Actual value = IE value *
2 (dB)
DELTA_FPUCCHFOR The PUCCH format 3 transmits power offset comparing to that of PUCCH format1a.
MAT3 deltaF_1 corresponds to -1 dB, deltaF0 to 0 dB and deltaF1 to 1 dB, and so on,
respectively.
DELTA_FPUCCHFOR The PUCCH format 1b with channel selection transmits power offset comparing to
MAT1_B_CS that of PUCCH format1a. deltaF1 corresponds to 1 dB, deltaF2 to 2 dB, respectively.
IOT_REDUCTION_SI PUSCH SINR margin for IoT reduction operation in UL power control. Higher value
NR_MARGIN allows higher PUSCH SINR. (unit: 0.1 dB)
Parameter Descriptions of CHG-DPHY-SPS/ RTRV-DPHY-SPS

P0_NOMINAL_PUSC This parameter specifies the SPS P0 value used in power control. The unit of value is
HPERSISTENT dBm.
P0_UE_PUSCHPERS This parameter specifies the SPS P0 value used in power control, which is
ISTENT determined per UE. The unit of value is dB.
Parameter Descriptions of CHG-ULPWR-CTRL/ RTRV-ULPWR-CTRL

P0_UE_PUSCH The non-persistent scheduling P0 value used in PUSCH power control, which is

Confidential
determined per UE. See 3GPP TS 36.213 [23, 5.1.1.1], unit dB. This field is
applicable for non-persistent scheduling, only.
DELTA_MCSENABLE Whether to use a power offset against other MCSs.
D • ci_en0: 0.
• ci_en1: 1.25.
Refer to 5.1 of 3GPP TS 36.213.
ACCMULATION_ENA Whether to use the accumulation mode and absolute mode in the TPC.
BLED • 0: Accumulation mode is not used.
• 1: Accumulation mode is used.
P0_UE_PUCCH P0 value used in PUCCH power control, which is determined per UE.
P_SRSOFFSET The power offset value between PUSCH and SRS. Parameter for periodic and a
periodic sounding reference signal transmission respectively. See 3GPP TS 36.213
[23, 5.1.3.1]. For Ks = 1.25, the actual parameter value is pSRS-Offset value-3. For
Ks = 0, the actual parameter value is -10.5 + 1.5*pSRS-Offset value.
FILTER_COSFFICIEN Filtering coefficient used to measure RSRP to calculate a path loss.
T
Parameter Descriptions of CHG-ULPWRTYPE-FUNC/ RTRV-ULPWRTYPE-

FUNC
UL_PWR_CTRL_TYP This parameter determines whether to use the Samsung-specific PUSCH power
E control.
• 0: OLPC-based
• 1: Samsung-specific algorithm
UL_SINR_MIN_REQ The minimum target SINR in dB. This value should be smaller than the maximum
target SINR. Otherwise, it causes abnormal power control operation.
Counters and KPIs

Table below outlines the main counters associated with this feature. The SINR and
MCS can be affected since the UL Tx power is controlled according to power
control.
SINR Distribution SinrDistULWbPreComp_Bin0~ The cumulated number of Uplink SINR Binx
SinrDistULWbPreComp_Bin19 before Outer-loop compensation
MCS ULReceivedMcs0~ULReceived The cumulated number of times PUSCH was
Mcs31 received at MCSx. For this counter, statistics are
REFERENCE

Confidential


Confidential
LTE-ME3002, Residual BLER Aware UL Power

Control
INTRODUCTION
The uplink performance degradation can happen from the cell in high interference
condition during the initial attach or handover. This feature presents the power
control operation for the uplink performance stabilization for UEs, which suffer
from low SINR and residual error caused by the interference increment.
BENEFIT
• Improve the degraded quality of service (QOS) including VoLTE rapidly.
• Improve the statistics representing the performance in weak channel conditions
such as the call failure rate, call drop rate, and so on.
DEPENDENCY
• Others
No HW or UE dependency
LIMITATION
None
SYSTEM IMPACT
This implementation can improve the UE performance in rapidly changing
interference environment.
FEATURE DESCRIPTION
The existing power control operation is performed when receiving Power
Headroom Report (PHR) from UEs. However in case of sudden strong
interference the uplink performance is much degraded and thus residual BLER
occurs frequently. PHR reception is not guaranteed or it can be delayed. Therefore
it can take a long time to recover the uplink SINR by increasing the transmit
power. This feature performs the following operations to increase the SINR
rapidly without PHR reception.
When RERROR_TPC_UP_CMD (CHG-PWR-PARA) is greater than 0, eNB
performs residual BLER aware UL power control.
If SINR received by UE is less than the minimum target SINR and the residual
error occurs, UL scheduler generates the power up TPC command in the next UL
grant (DCI format 0) to increase the PUSCH transmission power of the relevant

Confidential
UE. Operator can configure whether to increase +1 dB or +3 dB. If

RERROR_TPC_UP_CMD (CHG-PWR-PARA) is set to 1, TPC command 2 (+1
dB) is generated and if RERROR_TPC_UP_CMD (CHG-PWR-PARA) is set to 2,
TPC command 3 (+3 dB) is generated. However in case the transmission power of
the relevant UE already reaches Pmax, power up TPC command can be neglected
Therefore, UL scheduler also reduces the allocation RB size in the next UL grant
to increase the SINR.
Poor SINR (assume no PHR reception)
Signal Power
Interference Power
Feature Enable
Poor SINR Increased SINR
Signal Power
Interference Power
TPU up command
SYSTEM OPERATION
How to Activate
Preconditions
• A valid license key is required to run the feature on the network
• ACCUMULATION_ENABLED in CHG-ULPWR-CTRL is needed to be 1
(enabled).

Confidential
• Run CHG-PWR-PARA, and then set RERROR_TPC_UP_CMD to 1 or 2.

o If set to 1, the scheduler sends TPC command as 2 (+1 dB) in UL grant.
o If set to 2, the scheduler sends TPC command as 3 (+3 dB) in UL grant.
• Run CHG-PWR-PARA, and then set RERROR_TPC_UP_CMD to 0.
Key Parameters
configuration of this feature.
To activate or deactivate this feature, run the associated commands and set the key
parameters.
Parameter Descriptions of CHG-PWR-PARA/RTRV-PWR-PARA
RERROR_TPC_UP_C This parameter generates the PUSCH TPC up command if residual error occurs and
MD PUSCH SINR is poor. Generated TPC command is sent in the next UL grant (DCI
format 0) with reduced allocated RB size assignment.
• 0: OFF
• 1: ON with TPC +1 dB
• 2: ON with TPC +3 dB
There are no specific parameters for configuration of this feature.
TPC command value also can be configurable by RERROR_TPC_UP_CMD.
Counters and KPIs

SINR Distribution SinrDistULWbPreComp_Bin0~Sin The cumulated number of Uplink SINR Binx
rDistULWbPreComp_Bin19 before Outer-loop compensation
REFERENCE
[1] 3GPP TS 36.213 (Physical layer procedures), section 5.1.1

Confidential
LTE-ME3004, Power Boosting for DL Control

Channels
INTRODUCTION
DL control channels including Physical Control Format Indicator Channel
(PCFICH), Physical Broadcast Channel (PBCH) and Primary and Secondary
Synchronization Signals (SS) should be transmitted to all UEs in the cell. We
provide power boosting scheme to increase the robustness of DL control channels
reception at UE. This document describes how to configure power boosting for DL
control channels.
BENEFIT
• Operator can give better chance for UEs in bad RF condition and cell edge to
decode the broadcast message and to be synchronized with the cell.
DEPENDENCY
E-UTRAN (LTE)
• Others
Changing the DL control channel/signals power boosting requires cell lock
and cell unlock to forced call release operation, hence service interruption is
expected during this process.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature allows operator to configure the power boosting/de-boosting
individually for PCFICH, PBCH and PSS/SSS. The eNB can adjust the
transmission powers for these DL control channels and signals by setting
boosting/de-boosting values (PCFICH_POWER_GAIN, PBCH_POWER_GAIN
and SS_POWER_GAIN). Specifically, the transmission power for each of these
channels and signals is calculated by adding its boosting/de-boosting value to the
default power as follows.
• PCFICH power [dB] = default PCFICH power + PCFICH_POWER_GAIN

Confidential
• PBCH power [dB] = default PBCH power + PBCH_POWER_GAIN

• SS power [dB] = default SS power + SS_POWER_GAIN
The power boosting/de-boosting values (PCFICH_POWER_GAIN,
PBCH_POWER_GAIN and SS_POWER_GAIN) can be changed by using CHG-
PDSCH-IDLE.
For example, if PCFICH_POWER_GAIN is set to 3, then transmission power for
PCFICH is increased by 3 dB from its default value.
SYSTEM OPERATION
How to Activate
• Use the command CHG-PDSCH-IDLE to change the configuration of the
transmission power gain for DL control channels.
• Use the command RTRV-PDSCH-IDLE to retrieve the information about
transmission power gain for DL control channels.
Key Parameters
Parameter Descriptions of RTRV-PDSCH-IDLE/CHG-PDSCH-IDLE
PCFICH_POWER_GAIN This parameter indicates transmit power gain of PCFICH in dB scale.
PBCH_POWER_GAIN This parameter indicates transmit power gain of PBCH in dB scale.
SS_POWER_GAIN This parameter indicates transmit power gain of Primary/Secondary
Synchronization Signal in dB scale.
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
LTE-ME3005, DL Power Allocation

INTRODUCTION
Unlike the uplink power control, there is no explicit feedback from the UEs to
control the eNB transmit power for the downlink power control. The power levels
for dedicated control channels such as PDCCH and PHICH can be determined
based on downlink channel quality feedback from the UEs. The downlink channel
quality feedback is provided by the UEs to support channel sensitive scheduling in
the downlink. Therefore, the downlink transmit power control is fundamentally a
power allocation scheme rather than a power control scheme. Since the control
channel transmissions are spread over the whole system bandwidth, wideband
channel quality information is used to determine the power levels for these control
channels. It should be noted that various channel quality feedback formats are
supported and wideband channel quality is always present in all the feedback
formats to enable power control for the downlink control channels. The downlink
power control determines Energy Per Resource Element (EPRE) prior to cyclic
prefix insertion. The EPRE also denotes the average energy taken over all
constellation points for the modulation scheme applied. The eNB determines the
downlink transmit energy per resource element. A UE may assume the downlink
reference symbol EPRE is constant across the downlink system bandwidth and
constant across all subframes until different reference signal power information is
received.
BENEFIT
Optimized downlink power allocation will have an impact on the performance of
an LTE UE.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
capabilities.
This feature can change the throughput performance of the cell-edge user.

Confidential
FEATURE DESCRIPTION
The eNB determines the downlink transmit energy per resource element. A UE
may assume downlink cell-specific Reference Signal (RS) EPRE is constant across
the downlink system bandwidth and constant across all subframes until different
cell-specific RS power information is received. The downlink cell-specific
reference-signal EPRE can be derived from the downlink reference-signal transmit
power given by the parameter referenceSignalPower provided by higher layers.
The downlink reference-signal transmit power is defined as the linear average over
the power contributions (in [W]) of all resource elements that carry cell-specific
RS within the operating system bandwidth. The ratio of PDSCH EPRE to cell-
specific RS EPRE among PDSCH REs for each OFDM symbol is denoted by
either ρA or ρB according to the OFDM symbol index as given by the table below.
The table below outlines the OFDM symbol indexes within a slot of a non-
MBSFN subframe where the ratio of the corresponding PDSCH EPRE to the cell-
specific RS EPRE is denoted ρA or ρB.
Number of Antenna Ports OFDM symbol indexes within a slot OFDM symbol indexes within a slot
where the ratio of the corresponding where the ratio of the corresponding
PDSCH EPRE to the cell-specific RS PDSCH EPRE to the cell-specific RS
EPRE is denoted by ρA EPRE is denoted by ρB
Normal Cyclic Extended Cyclic Normal Cyclic Extended Cyclic
Prefix Prefix Prefix Prefix
One or Two 1, 2, 3, 5, 6 1, 2, 4, 5 0, 4 0, 3
Four 2, 3, 5, 6 2, 4, 5 0, 1, 4 0, 1, 3
For a UE in transmission mode 8 when UE-specific RSs are not present in the
Physical Resource Blocks (PRB) upon which the corresponding PDSCH is
mapped or in transmission modes 1-7, the UE may assume that for 16 QAM, 64
QAM, spatial multiplexing with more than one layer or for PDSCH transmissions
associated with the multi-user MIMO transmission scheme,
• ρA is equal to δpower-offset + PA + 10log10 (2) [dB] when the UE receives a
PDSCH data transmission using precoding for transmit diversity with 4 cell-
specific antenna ports according to Section 6.3.4.3 of [1]
• ρA is equal to δpower-offset + PA [dB] otherwise
where, δpower-offset is 0 dB for all PDSCH transmission schemes and where PA
is a UE specific parameter provided by higher layers. The cell-specific ratio is
given by the table below. According to cell specific parameter signaled by higher
layers and the number of configured eNB cell specific antenna ports.
The cell-specific ratio ρB/ρA for 1, 2, or 4 cell specific antenna ports
PB ρB/ρA
One Antenna Port Two and Four Antenna Ports
0 1 5/4
1 4/5 1
2 3/5 3/4

Confidential
PB ρB/ρA
One Antenna Port Two and Four Antenna Ports
3 2/5 1/2
Operation of DL Power Allocation

The power of the common RS per resource grid is set to a multiple of the power of
the PDSCH per resource grid by DL_POWER_OPTION (CHG-PDSCH-IDLE).
To this object, PA and PB are automatically determined by
DL_POWER_OPTION (CHG-PDSCH-IDLE). The power of the common RS and
data are calculated as follows;
• Reference Signal Power [dBm] = TX power per path + 10 log10 (No. TX
antennas) - 10log10 (No. DL subcarriers) - PA - 10log10 (No. CRS port)
• PDSCH Power in symbol without CRS [dBm] = ρA + Reference Signal Power
• PDSCH Power in symbol with CRS [dBm] = ρA + Reference Signal Power +
10log10 (ρB/ρA)
For example, if DL_POWER_OPTION (CHG-PDSCH-IDLE) is set to 0 and then
number of CRS is 2, PA and PB are determined as dB-3 and 1, respectively. Then,
the power of the common RS per resource grid is set to the same as that of the data
per resource grid as shown below.
- Tx power per path: 43 dBm

- NO. Tx antennas: 2
- Bandwidth: 10 MHz
- Power option: 0 (same)
CRS Symbol Non-CRS Symbol
18 dBm
Ant.0 15 dBm
18 dBm
Ant.1 15 dBm
If DL_POWER_OPTION (CHG-PDSCH-IDLE) is set to 3 and then number of

CRS is 2, PA and PB are determined as dB0 and 0, respectively. Then, the power
of the common RS per resource grid is a half times as much as that of the data per
resource grid as shown below.

Confidential
- Tx power per path: 43 dBm

- NO. Tx antennas: 2
- Bandwidth: 10 MHz
- Power option: 3 (half)
CRS Symbol Non-CRS Symbol
16 dBm
Ant.0 15 dBm
16 dBm
Ant.1 15 dBm
SYSTEM OPERATION
How to Activate
Preconditions
This feature is basically enabled. Therefore, it does not require addition activation
process for this feature.
Change this parameter value while the eNB is not operating. Changing the
parameter value while the eNB is operating requires special care because it may
cause abnormal operation.
1) Change the FORCED_MODE value from False to True.
2) Change the parameter value and block the cell. And unblock the cell again.
Changing the parameter value while the eNB is operating requires special care
because it may cause abnormal operation.
After change the parameter value, block the cell and unblock it. Otherwise, the
eNB may work abnormally.

Confidential
Key Parameters
parameters.
Parameter Descriptions of RTRV-PDSCH-IDLE/CHG-PDSCH-IDLE
DL_POWER_OPTION This parameter specifies the power setting option. The power of the RS per
resource grid is set to a multiple of the power of the data per resource grid.
The power of the RS per resource grid is set to a multiple of the power of
the data per resource grid.
• option0: The power of the RS per resource grid is the same as that of the
data per resource grid.
• option1: The power of the RS per resource grid is one and a half times
as much as that of the data per resource grid.
• option2: The power of the RS per resource grid is two times as much as
that of the data per resource grid.
• option3: The power of the RS per resource grid is a half times as much
as that of the data per resource grid.
• option4: The power of the RS per resource grid is 0.4 times as much as
• option10: The power of the RS per resource grid is 0.13 times as much
as that of the data per resource grid. Change this parameter value while
the eNB is not operating.
Changing the parameter value while the eNB is operating requires special
care because it may cause abnormal operation.
1 Change the FORCED_MODE value from False to True.
2 Change the parameter value and block the cell, and then unblock the cell
again. Changing the parameter value while the eNB is operating requires
special care because it may cause abnormal operation. After change the
parameter value, block the cell and unblock it. Otherwise, the eNB may
work abnormally.
FORCED_MODE This parameter indicates whether to change the configuration regardless of
the cell status.
• False: It can be used when the cell status is LOCK state.
• True: It can be changed regardless of the cell status.

Confidential
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME3006, AMPR (Additional Maximum

Power Reduction)
INTRODUCTION
UE’s maximum transmission power can be reduced according to the Additional
Maximum Power Reduction (A-MPR). 3GPP defines the allowed A-MPR values
depending on E-UTRA Band and UE power class. The A-MPR values are
determined based on start RB position and RB size defined in 3GPP TS 36.101.
BENEFIT
Interference can be mitigated by allocating all possible PUSCH resources based on
NS-07.
DEPENDENCY
E-UTRAN (LTE)
• Others
A-MPR supported UE is required
LIMITATION
When NS_07 is configured for Band 13 and PUCCH resources are located in the
center, the SRS related parameters should be changed so that location of SRS is
not overlapped to the location of PUCCH(CQI) if SRS operation is required.
When NS_07 is configured, the below features cannot be operated
• UL Frequency Selective Scheduling
• PRB Randomization
• UL Resource Allocation Type1 (Multi-Cluster PUSCH)
SYSTEM IMPACT
TBD
FEATURE DESCRIPTION
A-MPR could reduce UE maximum transmission power according to start RB
position and RB size, as specified in 3GPP TS 36.101: User Equipment (UE) radio
transmission and reception. Especially, an eNB operating on Band 13 can signal
additional spectrum emission requirements to indicate that the UE shall also meet
additional requirements in a specific deployment scenario, by using NS-07.

Confidential
Following table shows the A-MPR for “NS-07”. Depending on the starting PRB
(RBstart) and the number of PRBs (LCRB), the UE will apply a different A-MPR.
A-MPR for NS_07
Parameters Region A Region B Region C
RBstart 0 - 12 13 – 18 19 – 42 43 – 49
LCRB [RBs] 6-8 1 to 5 and 9-50 ≥8 ≥18 ≤2
A-MPR [dB] ≤8 ≤ 12 ≤ 12 ≤6 ≤3
RBstart indicates the lowest RB index of transmitted resource blocks
LCRB is the length of a contiguous resource block allocation
For intra-subframe frequency hopping between two regions, notes 1 and 2 apply on a per slot basis.
For intra-subframe frequency hopping between two regions, the larger A-MPR value of the two regions may
be applied for both slots in the subframe.
A-MPR for NS_07 for Cat-M1

BW [MHz] 5 10
(NBindex, (0, <6) (0, <6) (3, <6) (3, <6) (0, <6) (7, <6)
RBstart)
LCRB [RBs] [>4 and <7] [>1 and ≤4] [>4 and <7] [>1 and ≤4] [>2 and <7] [>2 and <7]
A-MPR [dB] 2 1 2 1 1 1
NOTE 1; NBindex is the narrowband index that is defined in 6.2.7 in [4]. The resource block assignment is
defined within the narrowband as defined in 5.3.3.1.12 and 5.3.3.1.13 in [5].
If this feature is activated by setting ADD_SPECTRUM_EMISSION (CHG-

CELL-INFO) as 7, UEs can be scheduled by considering NS-07. If not, scheduler
does not consider NS-07 (That is, scheduler does not consider interference
mitigation when it allocates resources to UEs).
According to PUCCH management (center or edge), PUSCH would be divided in
multiple regions based on NS-07. Position of the PUCCH can be selected by
setting PUCCH_CENTER_MODE (CHG-PUCCHCONF-IDLE).
• If PUCCH resources are located in the edge, PUSCH is not divided into
multiple regions (that is,, Physically, one group of contiguous PUSCH RBs).
• If PUCCH resources are located in the center, PUSCH is physically divided
into 2 regions (that is,, Physically, two groups of contiguous PUSCH RBs).

Confidential
Band 13 (700 MHz)
PUCCH (Control Channel)

PUCCH (Control Channel) PUCCH (Control Channel)
PUSCH PUSCH
PUSCH (Traffic Channel) (Traffic Channel) (Traffic Channel)
Direction of PUCCH RB increase Direction of PUCCH RB increase Direction of PUCCH RB increase Direction of PUCCH RB increase
PUCCH located in the edge PUCCH located in the Center
Without dependency of PUCCH resource location, AMPR NS-07 specific

scheduler tries to allocate all of remaining PUSCH resources (except PUCCH
resources) to UEs with considering below things for interference mitigation and
throughput increase.
• Scheduler considers UE’s channel quality, UE’s traffic volume, and so on.
• Scheduler considers each AMPR value of NS-07 according to position of
PRBs and length of PRBs when it allocates resources.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CELL-INFO and then set ADD_SPECTRUM_EMISSION to 7.
• Run CHG-CELL-INFO and then set ADD_SPECTRUM_EMISSION to other
value.

Confidential
Key Parameters
parameters.
ADD_SPECTRUM_EMISSION Additional spectrum emission used in an operating cell. A UE can additionally

reduce power from maximum power (see 3GPP TS 36.101, 6.2.4). This
information is broadcasted to the UE through SIB2.
Counters and KPIs

with this feature.
REFERENCE
TBD

Confidential
LTE-ME3101, HARQ in DL and UL

INTRODUCTION
Hybrid Automatic Repeat and request (HARQ) is used for facilitating fast error
detection and correction. HARQ is a stop and wait protocol; subsequent
transmission can take place only after receiving ACK/NACK from the receiving
entity. In case an ACK is received a new transmission is done, else a
retransmission is done. This scheme can be improved by using multiple channels
for supporting HARQ service. In LTE, HARQ is implemented as MAC level (L2)
module called HARQ entity. HARQ entity is associated with N HARQ processes
to implement N stop and wait HARQ protocol
BENEFIT
Operator achieves reliable data transmission by sending a message of
ACK/NACK.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Scheduling HARQ
In the downlink, HARQ is asynchronous and the schedule for HARQ
transmissions is not predeclared to the UEs. When the HARQ blocks are
transmitted they need to be accompanied by control information such as HARQ
process ID, new transmission/retransmission.
This scheme has the following advantages:
• Complete flexibility of scheduling different data flows as per their respective
priorities
• In case of frequency selective fading, link adaptation is possible. As the
resources for HARQ processes are not predetermined, the blocks (new
transmission/retransmission) can be modulated and coded as per the link

Confidential
conditions.
In uplink the HARQ transmission is synchronous, which means that the HARQ
blocks are predetermined for transmission and retransmission. The modulation,
coding scheme for the blocks is predetermined by the eNB. Thus, for uplink
retransmission, there is no need for transmitting control information along with the
HARQ data blocks. The modulation and coding scheme for the different UEs may
be tuned by the eNB.
HARQ in downlink
The downlink HARQ transmission is asynchronous. The UE receives the
information about HARQ transmissions on control channel. Downlink assignments
and HARQ information is transmitted on PDCCH and the Transport Blocks (TBs)
are transmitted on PDSCH. HARQ entity in UE deciphers the HARQ information.
HARQ information consists of parameters such as HARQ process ID, New Data
Indicator (NDI), Redundancy Version (RV), and TB size. HARQ entity maintains
a number of HARQ processes. HARQ information and TB is forwarded by HARQ
entity to relevant process.
A transmission is considered as a new transmission if:
• This is first transmission ever received for this process ID or
• NDI has toggled in HARQ information.
Otherwise, the TB is considered as retransmission. For a new transmission, HARQ
process replaces the old contents of associated HARQ buffer with the new
contents. If the decoding of this data block is successful, the data is handed over to
disassembly and demultiplexing MAC module. If decoding fails, data is preserved
in this buffer. The Maximum re-transmission number of PDSCH is configurable
by parameter DL_MAX_HARQ_TX (CHG-BLER-CTRL). The retransmission is
sent in order of redundancy version 0-2-3-1-0-2-3.
For retransmission, the retransmitted data is soft combined with old buffer
contents. If the number of allocated RB of retransmission is different from initial
transmission, MCS 29, 30, 31 are used. Retransmission has the same modulation
order with the initial transmission.
HARQ process decodes the new contents. If the decoding is successful, the
retransmitted block is handed over to disassembly and demultiplexing unit. If the
data has not yet been successfully decoded, UE combines the received data with
the data currently in the soft buffer for this TB. If the TB size is different from the
last valid TB size signaled for this TB, the UE may replace the data currently in
the soft buffer for this TB with the received data because the soft combining is not
possible. HARQ process generates a positive ACK for the successfully decoded
data and negative ACK for the unsuccessful ones. HARQ feedback has a lower
priority than measurement gaps. HARQ feedback is transmitted when
measurement gaps are not scheduled.
DL_HARQ_TRANSMISSION counter family is provided to measure DL HARQ
performance. This family provides the following counters:
• Number of initial transmissions (DLTransmissionRetrans0)

Confidential
• Number of re-transmissions
(DLTransmissionRetrans1~DLTransmissionRetrans6)
• Number of failed transmissions (DLTransmissionNackedRetrans)
• DL residual BLER per transmission
(DLResidualBlerRetrans0~DLResidualBlerRetrans6)
• DL residual BLER after max. HARQ transmissions
(DLResidualBlerRetransNak)
• Average, minimum, and maximum DL residual BLER
(DLResidualBlerRetransAvg, DLResidualBlerRetransMin,
DLResidualBlerRetransMax)
HARQ in uplink
Uplink HARQ is synchronous; UE receives the Uplink grant for transmission on
control channel. The grant indicates control information such as type of
transmission (new/retransmission), redundancy version. Whereas uplink
ACK/NACK are sent on PHICH, uplink grants are sent through PDCCH. If UE
can receive uplink grants, UE determines his own ACK/NACK by considering the
NDI on the received PDCCH instead of referring to PHICH. If NACK is received,
non-adaptive retransmission is planned. If ACK is received, adaptive
retransmission can be planned and HARQ buffer is preserved as-is (till PDCCH
grant indicative of toggled NDI arrives). Samsung eNB triggers adaptive
retransmission by transmitting PDCCH grant for retransmission if PUSCH RB
corresponding to the PDCCH grant for new transmission is not available (occupied
by other UEs or other physical channel) for the retransmission.
On receiving PDCCH grant for new transmission, HARQ entity receives a PDU
for transmission from Multiplexing and Assembly module. HARQ entity delivers
the PDU, uplink grant and HARQ info to HARQ process (that was indicated in
control information) and instructs the HARQ process to transmit the new block.
The HARQ process stores the received PDU in its HARQ buffer and sets the
Incremental Redundancy Version (IRV) indicated in control information. Then
HARQ process instructs the PHY layer to transmit the block.
On receiving the PDCCH grant for retransmission, HARQ entity delivers uplink
grant and HARQ info to relevant HARQ process and instructs it to generate an
adaptive retransmission. HARQ process instructs PHY to retransmit the buffer
contents as per the redundancy version instructed by eNB in control information. If
maximum limit for retransmissions is reached HARQ process flushes the contents
of buffer.
The maximum retransmission number of PUSCH is configurable by parameters
MAX_HARQTX (CHG-TRCH-INF), MAX_HARQTX_BUNDLING (CHG-
TRCH-INF), and MAX_HARQMSG3_TX (CHG-RACH-CONF).
UL_HARQ_TRANSMISSION counter family is provided to measure UL HARQ
performance. This family provides the following counters:
• Number of initial transmissions (ULTransmissionRetrans0)
• Number of re-transmissions

Confidential
(ULTransmissionRetrans1~ULTransmissionRetrans27)
• Number of failed transmissions (ULTransmissionNackedRetrans)
• UL residual BLER per transmission
(ULResidualBlerRetrans0~ULResidualBlerRetrans27)
• UL residual BLER after max. HARQ transmissions
(ULResidualBlerRetransNak)
• Average, minimum, and maximum UL residual BLER
(ULResidualBlerRetransAvg, ULResidualBlerRetransMin,
ULResidualBlerRetransMax)
HARQ ARQ Interaction

ARQ uses the knowledge from HARQ about transmission status of a MAC PDU.
This interaction is useful in handling HARQ residual error cases. HARQ provides
indications to ARQ block when:
• HARQ transmitter reaches maximum retransmissions for a TB without getting
an ACK
• HARQ receiver is able to detect a transmission failure
First indication is called as NACK1 and the second one is called NACK2. We
discuss the two conditions in detail in following sections.
NACK 1
This situation is caused when HARQ block transmissions cannot be successfully
decoded at receiver. After reaching maximum limit for number of retransmission
MAC sends NACK1 indication to RLC layer. On getting this indication ARQ
block in RLC can recode/re-segment the block for transmission. The eNB executes
PDSCH transmission according to the maximum number of HARQ
retransmissions configured by parameter DL_MAX_HARQ_TX (CHG-BLER-
CTRL).
Maximum number of retransmissions in Uplink should be known to the eNB, as
eNB has to stop scheduling retransmissions after UE has reached the maximum
transmissions. The UE executes PUSCH transmission according to the maximum
number of HARQ retransmissions configured by parameter MAX_HARQTX
(CHG-TRCH-INF). While UE is in TTI bundling mode, the UE executes PUSCH
transmission according to the maximum number of HARQ retransmissions
configured by parameter MAX_HARQTX_BUNDLING (CHG-TRCH-INF).
Maximum number of retransmission suited for a connection depends on the type
of QoS. For a real time traffic flow, more than two retransmissions may be
unnecessary.
However, for a file transfer, it is useful to have greater number of retransmissions.
This radio bearer specific maximum limit has to be indicted in UE reports to the
eNB. However, the scheme is prone to failure in case UE reports are received
late/erroneously at the eNB. The other option is to have a common limit for
maximum retransmissions for all the radio bearers. Generation of NACK1 from
MAC to RLC may also be caused if an ACK from receiver is misinterpreted as
Confidential
NACK. This misinterpretation leads to unnecessary retransmissions.
NACK 2
When HARQ receiver transmits NACK for a HARQ block, it expects the block to
be retransmitted. If the receiver sees no transmission in the expected TTI or when
the receiver sees the HARQ process ID rescheduled for a new transmission, the
receiver knows that the NACK has been misinterpreted as ACK by the transmitter.
MAC indicates this to RLC and RLC sends a control message to peer to indicate
the missing block. The scheme requires a request for resource grant for UE and
eNB followed by transmission of control message. Synchronous HARQ was
adopted in uplink to save on control channel resources and this control messaging
becomes overhead.
This NACK2 interaction provides little performance gain compared to added
complexity and has been dropped from recent versions of specifications.
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of RTRV-TRCH-INF/CHG-TRCH-INF
MAX_HARQTX The maximum HARQ Tx per cell. The UE executes PUSCH retransmission in
accordance with this parameter value.
MAX_HARQTX_BUN The maximum HARQ transmission count is sub-frame bundling mode.
DLING
Parameter Descriptions of RTRV-RACH-CONF/CHG-RACH-CONF

MAX_HARQMSG3_T The maximum number of transmission of HARQ Msg3.

Confidential
X
Parameter Descriptions of RTRV-BLER-CTRL/CHG-BLER-CTRL

DL_MAX_HARQ_TX The maximum PDSCH HARQ Tx per cell. The eNB executes PDSCH transmission
in accordance with this parameter value.
Counters and KPIs

Transmission BLER DLResidualBlerRetrans0 The calculated value of PDSCH BLER for the initial
transmission during the collection interval. BLER is the
failure rate for the initial transmission and is a ratio of
the number of times the first re-transmission was
carried out to the number of times the initial
transmission was carried out.
DLResidualBlerRetrans1 The number of PDSCH BLER for the first HARQ
retransmission
DLResidualBlerRetrans2 The number of PDSCH BLER for the second HARQ
retransmission
DLResidualBlerRetrans3 The number of PDSCH BLER for the third HARQ
retransmission
DLResidualBlerRetrans4 The number of PUSCH BLER for the initial HARQ
retransmission
DLResidualBlerRetrans5 The number of PUSCH BLER for the first HARQ
retransmission
DLResidualBlerRetrans6 The number of PUSCH BLER for the second HARQ
retransmission
ULResidualBlerRetrans0 The number of PUSCH BLER for the initial HARQ
retransmission
ULResidualBlerRetrans1 The number of PUSCH BLER for the first HARQ
retransmission
ULResidualBlerRetrans2 The number of PUSCH BLER for the second HARQ
retransmission
ULResidualBlerRetrans3 The number of PUSCH BLER for the third HARQ
retransmission
ULResidualBlerRetrans4 The number of PUSCH BLER for the fourth HARQ
retransmission
ULResidualBlerRetrans5 The number of PUSCH BLER for the fifth HARQ
retransmission
ULResidualBlerRetrans6 The number of PUSCH BLER for the sixth HARQ
retransmission
ULResidualBlerRetrans7 The number of PUSCH BLER for the seventh HARQ
retransmission
ULResidualBlerRetrans8 The number of PUSCH BLER for the eighth HARQ

Confidential

retransmission
ULResidualBlerRetrans9 The number of PUSCH BLER for the ninth HARQ
retransmission
ULResidualBlerRetrans10 The number of PUSCH BLER for the tenth HARQ
retransmission
ULResidualBlerRetrans11 The number of PUSCH BLER for the eleventh HARQ
retransmission
ULResidualBlerRetrans12 The number of PUSCH BLER for the twelfth HARQ
retransmission
ULResidualBlerRetrans13 The number of PUSCH BLER for the thirteenth HARQ
retransmission
ULResidualBlerRetrans14 The number of PUSCH BLER for the fourteenth
HARQ retransmission
ULResidualBlerRetrans15 The number of PUSCH BLER for the fifteenth HARQ
retransmission
ULResidualBlerRetrans16 The number of PUSCH BLER for the sixteenth HARQ
retransmission
ULResidualBlerRetrans17 The number of PUSCH BLER for the seventeenth
HARQ retransmission
ULResidualBlerRetrans18 The number of PUSCH BLER for the eighteenth
HARQ retransmission
ULResidualBlerRetrans19 The number of PUSCH BLER for the nineteenth
HARQ retransmission
ULResidualBlerRetrans20 The number of PUSCH BLER for the twentieth HARQ
retransmission
ULResidualBlerRetrans21 The number of PUSCH BLER for the twenty first
HARQ retransmission
ULResidualBlerRetrans22 The number of PUSCH BLER for the twenty second
HARQ retransmission
ULResidualBlerRetrans23 The number of PUSCH BLER for the twenty third
HARQ retransmission
ULResidualBlerRetrans24 The number of PUSCH BLER for the twenty fourth
HARQ retransmission
ULResidualBlerRetrans25 The number of PUSCH BLER for the twenty fifth
HARQ retransmission
ULResidualBlerRetrans26 The number of PUSCH BLER for the twenty sixth
HARQ retransmission
ULResidualBlerRetrans27 The number of PUSCH BLER for the twenty seventh
HARQ retransmission
HARQ performance for DLDataHARQFail The number of PDSCH HARQ residual failure for UE
Data UE without QCI1 bearer
DLDataHARQSucc The number of PDSCH transmission success for UE
without QCI1 bearer
DLDataHARQFailRate PDSCH HARQ residual BLER for UE without QCI1
bearer
ULDataHARQFail The number of PUSCH HARQ residual failure for UE
without QCI1 bearer
ULDataHARQSucc The number of PUSCH transmission success for UE
without QCI1 bearer

Confidential

ULDataHARQFailRate PUSCH HARQ residual BLER for UE without QCI1
bearer
DLDataHARQInitFail The number of PDSCH HARQ initial transmission
failure for UE without QCI1 bearer
DLDataHARQInitFailRate PDSCH HARQ initial BLER for UE without QCI1
bearer
ULDataHARQInitFail The number of PUSCH HARQ initial transmission
failure for UE without QCI1 bearer
ULDataHARQInitFailRate PUSCH HARQ initial BLER for UE without QCI1
bearer
HARQ performance for DLVoLTEHARQFail The number of PDSCH HARQ residual failure for
Volte bearer VoLTE bearer (QCI1) established UE
DLVoLTEHARQSucc The number of PDSCH transmission success for
VoLTE bearer (QCI1) established UE
DLVoLTEHARQFailRate PDSCH HARQ residual BLER for VoLTE bearer
(QCI1) established UE
ULVoLTEHARQFail The number of PUSCH HARQ residual failure for
ULVoLTEHARQSucc The number of PUSCH transmission success for
ULVoLTEHARQFailRate PUSCH HARQ residual BLER for VoLTE bearer
(QCI1) established UE
DLVoLTEHARQInitFail The number of PDSCH HARQ initial transmission
failure for VoLTE bearer (QCI1) established UE
DLVoLTEHARQInitFailRat PDSCH HARQ initial BLER for VoLTE bearer (QCI1)
e established UE
ULVoLTEHARQInitFail The number of PUSCH HARQ initial transmission
failure for VoLTE bearer (QCI1) established UE
ULVoLTEHARQInitFailRat PUSCH HARQ initial BLER for VoLTE bearer (QCI1)
e established UE
REFERENCE
Medium Access Control (MAC) protocol specification

Confidential
LTE-ME3201, Basic Link Adaptation

INTRODUCTION
The principle of link adaptation is fundamental to the design of a radio interface
which is efficient for packet-switched data traffic. LTE adjusts the transmitted
information data rate (modulation scheme and channel coding rate) dynamically to
match the prevailing radio channel capacity for each user.
For the downlink data transmissions in LTE, the eNB typically selects the
modulation scheme and code rate depending on a prediction of the downlink
channel conditions. An important input to this selection process is the Channel
Quality Indicator (CQI) feedback transmitted by the User Equipment (UE) in the
uplink. CQI feedback is an indication of the data rate which can be supported by
the channel, taking into account the Signal to Interference plus Noise Ratio (SINR)
and the characteristics of the UE receiver.
For the LTE uplink transmissions, the link adaptation process is similar to that for
the downlink, with the selection of modulation and coding schemes also being
under the control of the eNB. An identical channel coding structure is used for the
uplink, while the modulation scheme may be selected between QPSK and 16
QAM, and, for the highest category of UE, also 64 QAM. The main difference
between uplink and downlink is that CQI feedback is used for downlink and the
eNB estimate of the supportable uplink data rate is used for uplink.
BENEFIT
• Match the transmission parameter such as Modulation and Coding Scheme
(MCS) as well as MIMO transmission rank and precoding to the channel
condition on resource allocated by the scheduler.
• Serve the best resource allocation under the restriction of limited resource
pool.
DEPENDENCY
UL 64 QAM capable UE is required (UE-category 5, 8 or UE-categoryUL 5,
8, 13)
E-UTRAN (LTE)
LTE-ME0401 (Downlink QPSK, 16 QAM, 64 QAM Support), LTE-ME0404
(DL 256 QAM), LTE-ME3205 (CQI Correction): This feature describes more
detailed MCS/RB allocation procedure, LTE-ME0402 (Uplink QPSK, 16
QAM Support), LTE-ME0403 (Uplink 64 QAM Support)

Confidential
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Adaptive Modulation and Coding (AMC)

In cellular communication systems, the quality of the signal received by a UE
depends on the channel quality from the serving cell, the level of interference from
other cells, and the noise level. To optimize system capacity and coverage for a
given transmission power, the transmitter should try to match the information data
rate for each user to the variations in received signal quality. This is commonly
referred to as link adaptation and is typically based on Adaptive Modulation and
Coding (AMC).
The degrees of freedom for the AMC consist of the modulation and coding
schemes:
• Modulation Scheme. Low-order modulation (that is, fewer data bits per
modulated symbol, for example, QPSK) is more robust and can tolerate higher
levels of interference but provides a lower transmission bit rate. High-order
modulation (that is, more bits per modulated symbol, for example, 64 QAM)
offers a higher bit rate but is more prone to errors due to its higher sensitivity
to interference, noise and channel estimation errors. Therefore it is useful
when the SINR is sufficiently high.
• Code rate. For a given modulation, the code rate can be chosen depending on
the radio link conditions. A lower code rate can be used in poor channel
conditions and a higher code rate in the case of high SINR. The adaptation of
the code rate is achieved by applying puncturing or repetition to the output of a
mother code.
A key issue in the design of the AMC scheme for LTE is whether all Resource
Blocks (RBs) allocated to one user in a subframe should use the same MCS or
whether the MCS should be frequency dependent within each subframe. In
general, only a small throughput improvement arises from a frequency-dependent
MCS compared to a frequency-independent MCS in the absence of frequency
selective transmission power control. Therefore, the additional control signaling
overhead associated with frequency-dependent MCS is not justified. So, in LTE
the modulation and channel coding rates are constant over the allocated frequency
resources for a given user, and time-domain channel-dependent scheduling and
AMC is supported instead.
In LTE, UE can be configured to report CQIs to assist the eNB to select an
appropriate MCS in the downlink transmissions. The CQI reports are derived from
the downlink received signal quality, typically based on measurements of the
downlink reference signals. The reported CQI is not a direct indication of SINR in

Confidential
LTE. Instead, the UE reports the highest MCS that it can decode with a transport
block error rate probability not exceeding 10 %. Thus, the information received by
the eNB takes into account the characteristics of the UE receiver, and prevailing
radio channel quality.
Hence, a UE that is designed with advanced signal processing algorithms (for
example, using interference cancellation techniques) can report a higher CQI even
in the same channel quality. The list of modulation schemes and code rates, which
can be signaled by means of a CQI value, is shown in the table below. Detailed
PDSCH MCS/RB allocation procedure is described in LTE-ME3205 (CQI
Correction).
CQI index Modulation Approximate code rate Efficiency (information
bits per symbol)
0 No transmission - -
1 QPSK 0.076 0.1523
2 QPSK 0.12 0.2344
3 QPSK 0.19 0.3770
4 QPSK 0.3 0.6016
5 QPSK 0.44 0.8770
6 QPSK 0.59 1.1758
7 16 QAM 0.37 1.4766
8 16 QAM 0.48 1.9141
9 16 QAM 0.6 2.4063
10 64 QAM 0.45 2.7305
11 64 QAM 0.55 3.3223
12 64 QAM 0.65 3.9023
13 64 QAM 0.75 4.5234
14 64 QAM 0.85 5.1152
15 64 QAM 0.93 5.5547
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs


Confidential

DL RI DLReceivedRI0~4 Count of feedback per Rank Indicator
DL CQI DLReceivedCQI0~15 Count of feedback per Wideband Channel
Quality Indicator
DL MCS DLTransmittedMcs0~31 Count of transmission per MCS
MCS ULReceivedMcs0~31 The cumulated number of received PUSCH
per MCS
DLSchedulerMcs0~31 The cumulated number of PRBs assigned to
PDSCH per MCS
ULSchedulerMcs0~31 The cumulated number of PRBs assigned to
PUSCH per MCS
Air MAC Packet AirMacDLThruAvg The calculated number that indicates the
average per second size of MAC PDUs which
were successfully transmitted through PDSCH
AirMacULThruAvg The calculated number that indicates the
average per second size of MAC PDUs which
were successfully received through PUSCH
AirMacDLEfctivThruAvg The overall calculated size of MAC PDUs
which were successfully transmitted through
PDSCH during the collection interval.
AirMacULEfctivThruAvg The overall calculated size of MAC PDUs
SINR Distribution SinrDistULWbPreComp_Bin0~ The cumulated number of Uplink SINR before
19 Outer-loop compensation
• Bin0 (-10~-8 dB)
• Bin1 (-8~-6 dB)
• Bin2 (-6~-4 dB)
• Bin3 (-4~-2 dB)
• Bin4 (-2~0 dB)
• Bin5 (0~2 dB)
• Bin6 (2~4 dB)
• Bin7 (4~6 dB)
• Bin8 (6~8 dB)
• Bin9 (8~10 dB)
• Bin10 (10~-12 dB)
• Bin11 (12~-14 dB)
• Bin12 (14~-16 dB)
• Bin13 (16~-18 dB)
• Bin14 (18~-20 dB)
• Bin15 (20~-22 dB)
• Bin16 (22~-24 dB)
• Bin17 (24~-26 dB)
• Bin18 (26~-28 dB)
• Bin19 (28~-30 dB)
SinrDistULWbPostComp_Bin0 The cumulated number of Uplink SINR after
~19 Outer-loop compensation
• Bin0 (-10~-8 dB)

Confidential

• Bin1 (-8~-6 dB)
• Bin2 (-6~-4 dB)
• Bin3 (-4~-2 dB)
• Bin4 (-2~0 dB)
• Bin5 (0~2 dB)
• Bin6 (2~4 dB)
• Bin7 (4~6 dB)
• Bin8 (6~8 dB)
• Bin9 (8~10 dB)
• Bin10 (10~-12 dB)
• Bin11 (12~-14 dB)
• Bin12 (14~-16 dB)
• Bin13 (16~-18 dB)
• Bin14 (18~-20 dB)
• Bin15 (20~-22 dB)
• Bin16 (22~-24 dB)
• Bin17 (24~-26 dB)
• Bin18 (26~-28 dB)
• Bin19 (28~-30 dB)
REFERENCE

Confidential
LTE-ME3203, Aperiodic CQI Reporting

INTRODUCTION
Quality Indicator (CQI) feedback transmitted by the User Equipment (UE) in the
uplink. CQI feedback is an indication of the data rate, which can be supported by
the channel, taking into account the Signal to Interference plus Noise Ratio (SINR)
There are two types for CQI reporting: Periodic CQI and Aperiodic CQI.
• Periodic CQI: Periodic CQI reporting is semi-statically configured by eNB to
be periodically transmitted on PUCCH.
• Aperiodic CQI: Aperiodic CQI reporting on the PUSCH can be triggered by a
CSI request within DCI format 0 on PDCCH or within random access
response grant belonging to a random access response message on the
PDSCH. The type of CQI report is configured by the eNB by RRC signaling.
BENEFIT
Enables link adaptation by facilitating this feature.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
Aperiodic CQI is not triggered in TTI bundling mode.
SYSTEM IMPACT
FEATURE DESCRIPTION
Aperiodic CQI is sent by PUSCH and be triggered by CQI request field within UL
grant. The type of CQI reporting is configured by eNB by RRC signaling:
wideband reporting, UE-selected sub-band reporting, and higher layer configured
sub-band reporting. In UE-selected sub-band reporting, UE reports average CQI of
M number of preferred sub-band in addition to wideband CQI, while UE reports
wideband CQI and sub-band CQI of all subbands in higher layer configured sub-
band reporting. Because higher layer configured CQI reporting provides more

Confidential
information than UE-selected sub-band reporting, Samsung eNB only operates

higher layer configured CQI reporting as follows: Mode 3-0 and Mode 3-1.
The table below shows feedback information depending on reporting modes.
Mode Feedback information Related Transmission Mode (TM)
3-0 • Wideband CQI TM1, TM2, TM3
• Subband CQI: calculated for each subband
• No differential CQI for Codeword2
3-1 • Wideband PMI TM4
• Subband CQI: calculated assuming the wideband PMI
for each subband
• Wideband CQI: calculated assuming the wideband PMI
When carrier aggregation is enabled, the use of 2 bits for CSI request is applicable.
According to CSI request field, aperiodic CQI reporting is triggered for PCell or
SCell.
Aperiodic CQI reporting can be enabled by using following parameters:
Parameters Command
CQI_REPORT_APERIODIC_SETUP CHG-CQI-REP
CQI_REPORT_APERIODIC_SETUP_R10
CQI_REPORT_APERIODIC_SETUP (CHG-CQI-REP) is for Rel8/9 UE and

CQI_REPORT_APERIODIC_SETUP_R10 (CHG-CQI-REP) is for Rel10 UE.
Samsung eNB triggers Aperiodic CQI reporting when DL data exists.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-CQI-REP and set CQI_REPORT_APERIODIC_SETUP to
ci_Config_Setup for enabling aperiodic CQI report.
• Run CHG-CQI-REP and set CQI_REPORT_APERIODIC_SETUP_R10 to
ci_Config_PcellScellSetup for enabling aperiodic CQI report.

Confidential
• Run CHG-CQI-REP and set CQI_REPORT_APERIODIC_SETUP to
ci_Config_Release for disabling aperiodic CQI report.
• Run CHG-CQI-REP and set CQI_REPORT_APERIODIC_SETUP_R10 to
ci_Config_ReleaseAll for disabling aperiodic CQI report.
Key Parameters
parameters.
Parameter Descriptions of CHG-CQI-REP/RTRV-CQI-REP
CQI_REPORT_APER This parameter is set to enable or disable the use of aperiodic report mode.
IODIC_SETUP • Release: aperiodic report mode is disabled.
• Setup: aperiodic report mode is enabled.
CQI_REPORT_APER Config aperiodic report mode for Rel.10.
IODIC_SETUP_R10 • 0: ci_Config_ReleaseAll
• 1: ci_Config_PcellSetup
• 2: ci_Config_ScellSetup
• 3: ci_Config_PcellScellSetup
Counters and KPIs

DL Wideband CQI DLReceivedCQI0~DLReceivedC The cumulated number that CQIx is received per
QI15 Layer/Codeword.
DL_RI DLReceivedRI1~DLReceivedRI4 The cumulated number that RIx is received.
REFERENCE

Confidential
LTE-ME3205, CQI Correction

INTRODUCTION
The Downlink RB and MCS are determined by considering a reported CQI from
UE. CQI correction compensates possible non-idealities of the link adaptation in
LTE (for example, CQI estimation error of the UE, and CQI quantization error).
BENEFIT
• Enable better link adaptation by using this feature
• Enable downlink radio resource scheduling to serve the best resource
allocation
DEPENDENCY
E-UTRAN (LTE)
LTE-ME3101 (HARQ in DL and UL)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
CQI correction performs CQI adaptation to compensate for possible non-idealities
of the link adaptation in LTE. For this object, IIR filtering process for CQI is
provided, and IIR filtered value is updated whenever a fresh CQI is received. IIR
filtering coefficient for CQI is configurable by parameter
CQI_FILTERING_COEFF (CHG-DLPARA-CTRL). Outer-loop offset value for
PDSCH is managed by eNB and is updated according to whether PDSCH is
received by target UE successfully or not. HARQ feedback is used to detect the
successful reception of PDSCH.
If PDSCH fail is detected, eNB decreases the PDSCH OLRC to better protect
PDSCH. On the contrary, if PDSCH is successfully transmitted to the target UE,
eNB increases the PDSCH OLRC to use more aggressive MCS. To let the PDSCH
initial transmission error rate converge to the target value, Ack and Nack step size
for non-VoLTE UE are calculated as follows:

Confidential
• NACKstep = 0.01 x DL_OLLA_REF_STEP_VALUE (CHG-BLER-CTRL)

• ACKstep = NACKstep x DL_TARGET_BLER (CHG-BLER-CTRL) / (1000 -
DL_TARGET_BLER) (CHG-BLER-CTRL))
Nack step size for VoLTE UE is fixed to 0.25 and Ack step size for VoLTE
UE is calculated as follows:
• ACKstep = 0.25 x VOLTE_DL_TARGET_BLER (CHG-BLER-CTRL) / (1000
- VOLTE_DL_TARGET_BLER) (CHG-BLER-CTRL))
The following figure describes how UE feedback information is managed to
correct the CQI.
Outer-Loop Rate Control (OLRC) compensates CQI estimation error that comes
from UE's channel measurement error as well as the time variation of downlink
channel such that an initial target BLER on PDSCH is satisfied. Furthermore, two
types of OLRC are managed in downlink such as PDSCH OLRC and PDCCH
OLRC. PDSCH OLRC is used to decide the modulation order, TB size, and
coderate for PDSCH. PDCCH OLRC is used to decide the aggregation level of
PDCCH.
PDSCH OLRC is updated based on the HARQ ACK or NACK feedback from UE
while PDCCH OLRC is updated based on the UE's missing of the dedicated
PDCCH.
Based on CQI and PDSCH OLRC, DL MCS & RB are determined as follows:
• [Step1: DL MCS] DL MCS is determined based on Modulation Product code
Rate (MPR), which means achievable bits per RE (= efficiency), estimated by
the procedure below:
a The reported CQI is converted to MPR based on Table 7.2.3-1 (3GPP TS
36.213).
b Converted MPR is filtered whenever a fresh CQI is received, and PDSCH
OLRC is applied to the IIR filtered MPR in dB domain whenever HARQ
feedback are received.
c MPR value is mapped to ITBS in Table 7.1.7.2.1-1 (3GPP TS 36.213).
• [Step2: PRB] The smallest number of PRBs is selected such that the
corresponding TBS is larger than or equal to buffer occupancy.
• [Step3: DL MCS overwrite] This step is 'MCS overwrite'. DL MCS level is
adjusted to the lowest level such that the corresponding TBS is larger than or
Confidential
equal to buffer occupancy. This function is applied to all QCIs, but MCS
overwrite for QCI1 can be configurable by operator. If
TBS_DECISION_QCI1 (CHG-VOLTEDL-SCHED) is set to 1, MCS overwrite
for QCI1 is activated. Otherwise, MCS overwrite for QCI1 is de-activated.
An example of DL MCS and RB decision procedure is illustrated as follows:
Illustrative Example
Assumption:
- Best channel state
- Buffer occupancy = 1500 bits
Transport block size table (3GPP TS36.213)
MCS NPRB
1TBS
index 1 2 3 4
21 19 408 840 1288 1736

22 20 440 904 1384 3) Lower MCS
23 21 488 1000 1480 from 28 to 24
24 22 520 1064 1608 2152
25 23 552 1128 1736 2280
26 24 584 1192 1800 2408
27 25 616 1256 1864 2536
28 26 712 1480 2216 2984
1) MCS = 28 2) Number of PRBs = 3
PRB: physical resource block

TBS: transport block size
Decision procedure for DL MCS & RB mentioned above have the following
effect:
• Step2: DL scheduler can accommodate greater number of UEs or minimize
interference to neighbor cell.
• Step3: DL scheduler allocates no higher MCS than needed, resulting in
improved transmission reliability.
o The activation of TBS decision operation for QCI1 can be controlled by
configuring parameter TBS_DECISION_QCI1 (CHG-VOLTEDL-
SCHED).
For robust transmission of Signaling Radio Bearer (SRB), mprdegrade is
additionally applied to SRB in step1, resulting in lower DL MCS for SRB. The
mprdegrade value for SRB is configurable by parameter SRB_MPR_DEGRADE
(CHG-DLPARA-CTRL).
The following figure shows an illustration of MPR degrade for SRB stability.

Confidential
SYSTEM OPERATION
How to Activate
Preconditions
Refer to the following parameter description.
Key Parameters
This section describes the key parameters of the feature.
parameters.
Parameter Descriptions of RTRV-VOLTEDL-SCHED/CHG-VOLTEDL-SCHED
TBS_DECISION_QCI1 This parameter indicates whether to activate MCS overwrite operation for QCI1
(= VoLTE).
• 0: MCS overwrite for QCI1 is de-activated.
• 1: MCS overwrite for QCI1 is activated.
Parameter Descriptions of RTRV-BLER-CTRL/CHG-BLER-CTRL

Confidential
supported by the system
DLTARGET_BLER This parameter indicates the downlink initial target BLER in 0.1 % unit
DLOLLA_REF_STEP_VAL This parameter indicates the PDSCH OLRC step size in 0.01 dB unit
UE
VOLTE_DL_TARGET_BL This parameter indicates the DL VoLTE target BLER in 0.1 % unit
ER
Parameter Descriptions of RTRV-DLPARA-CTRL/CHG-DLPARA-CTRL

supported by the system
SRB_MPR_DEGRADE This parameter indicates the mprdegrade value for SRB
CQI_FILTERING_COEFF This parameter indicates the coefficient for CQI filtering
Counters and KPIs

DL MCS DLTransmittedMcs0 Count of MCS0 transmission
DLTransmittedMcs1 Count of MCS1 transmission

Confidential

REFERENCE

Confidential
LTE-ME3206, Periodic Channel Status

Reporting
INTRODUCTION
Quality Indicator (CQI) feedback transmitted by User Equipment (UE) in the
uplink. The CQI feedback is an indication of the data rate, which can be supported
by the channel, taking into account Signal to Interference plus Noise Ratio (SINR)
CQI reporting is divided into periodic and aperiodic ones. Periodic CQI reporting
is transmitted in the PUCCH if there is not date being transmitted on the PUSCH.
Aperiodic CQI reporting is always transferred on the PUSCH.
BENEFIT
Enable link adaptation from facilitating this feature
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
UE can be configured to report CQIs to assist the eNB in selecting an appropriate
MCS to use for the downlink transmissions. The CQI reports are derived from the
downlink received signal quality, typically based on measurements of the
downlink reference signals. It is important to note that the reported CQI is not a
direct indication of SINR in LTE. Instead, the UE reports the highest MCS that it
can decode with a transport block error rate probability not exceeding 10 %. Thus
the information received by the eNB takes into account the characteristics of the
UE’s receiver, and not just the prevailing radio channel quality. Hence a UE that is
designed with advanced signal processing algorithms (for example, using
interference cancellation techniques) can report a higher channel quality and,
depending on the characteristics of the eNB’s scheduler, can receive a higher data
rate. The list of modulation schemes and code rates which can be signaled by
Confidential
means of a CQI value is shown in the table below.

CQI Index Modulation Approximate Code Rate Efficiency (Information Bits per Symbol)
0 No Transmission - -
1 QPSK 0.076 0.1523
2 QPSK 0.12 0.2344
3 QPSK 0.19 0.3770
4 QPSK 0.3 0.6016
5 QPSK 0.44 0.8770
6 QPSK 0.59 1.1758
7 16 QAM 0.37 1.4766
8 16 QAM 0.48 1.9141
9 16 QAM 0.6 2.4063
10 64 QAM 0.45 2.7305
11 64 QAM 0.55 3.3223
12 64 QAM 0.65 3.9023
13 64 QAM 0.75 4.5234
14 64 QAM 0.85 5.1152
15 64 QAM 0.93 5.5547
CQI Feedback
For CQI feedback, eNB employs periodic reporting of the CQI and the UE will
transmit the reports using the PUCCH. Only wideband and UE-selected sub-band
feedback is possible for periodic CQI reporting, for all downlink (PDSCH)
transmission modes. The type of periodic reporting is configured by the eNB by
RRC signaling. For the wideband periodic CQI reporting, the period can be
configured to {2, 5, 10, 20, 40, 80, 160} ms, and the UE reports one wideband
CQI value for the whole system bandwidth. In the case of ‘UE selected sub-band’,
the total number of sub-bands N is divided into J fractions called bandwidth parts.
One CQI value is computed and reported for a single selected sub-band from each
bandwidth part, along with the corresponding sub-band index. The value of J
depends on the system bandwidth as summarized in the table below.
Table below outlines the periodic CQI reporting with UE-selected sub-bands: sub-
band size (k) and bandwidth parts (J) versus downlink system bandwidth.
System Bandwidth (RBs) Sub-band Size (k RBs) Number of Bandwidth parts (J)
6-7 NA NA
8-10 4 1
11-26 4 2
27-63 6 3
64-110 8 4

Confidential
Multiple Antenna Transmission Case

Channel Quality Indicator (CQI)
A CQI index is defined in terms of a channel coding rate value and modulation
scheme (QPSK, 16 QAM, 64 QAM) as given in first table of description. In
addition to 4-bit absolute CQI indexes, three differential CQI values are defined to
reduce the CQI signaling overhead. Note that a UE always reports the wideband
CQI even when UE-selected sub-band feedback is used for periodic reporting.
This is the reason why wideband CQI is required for setting the power levels for
downlink control channels that are transmitted in a frequency diverse transmission
format over the wideband to exploit frequency diversity.
Precoding Matrix and Rank Indicator (PMI and RI)
The MIMO transmission rank can be either one or two for the case of two-antenna
ports requiring single-bit rank indicator (RI). The numbers of precoders for the two
antenna ports are four and two for rank-1 and rank-2 respectively. Therefore, the
precoding matrix indicator (PMI) requires two bits for rank-1 and a single bit for
rank-2. For the case of four antenna ports, the MIMO transmission rank can be
one, two, three or four requiring two bit rank indication. The number of precoders
for each rank is 16 and therefore requires four bit PMI indication.
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

DL Wideband CQI DLReceivedCQI0~DLReceived The cumulated number that CQIx is received per
CQI15 Layer/Codeword.
DL_RI DLReceivedRI1~DLReceivedRI The cumulated number that RIx is received.
4
REFERENCE

Confidential
LTE-ME3207, Power Restriction for PDCCH

Region
INTRODUCTION
A Physical Downlink Control Channel (PDCCH) carries detailed control
information, which includes resource assignments for a UE or group of UEs.
PDCCH consists of one or more Control Channel Elements (CCEs), where each
CCE corresponds to nine sets of four physical resource elements. Number of CCEs
for each PDCCH can be 1, 2, 4, or 8, and a PDCCH with more CCEs is required to
achieve robustness in weak channel condition. The other way to adapt channel
condition is to adjust power for a PDCCH. Boosting PDCCH power by 3 dB can
have similar effectiveness as increasing number of CCEs by twice. Because the
increase of number of CCEs causes shortage of PDCCH region, especially when
number of CCEs is 4 or 8, PDCCH power boosting can be an effective method for
channel adaptation. However, PDCCH power boosting may cause total
transmission power to exceed maximum Tx power. This feature restricts total
transmission power not to exceed maximum Tx power even if PDCCH power is
boosted.
BENEFIT
Even if PDCCH power is boosted, total transmission power is guaranteed not to
exceed maximum Tx power.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The physical downlink control channel (PDCCH) carries scheduling assignments
and other information. A PDCCH is transmitted on an aggregation of one or
several consecutive control channel elements (CCEs), where a control channel
elements corresponds to 9 resource element groups. Larger number of CCEs for a
PDCCH means lower coding rate to protect the DCI bits from the propagation
channel. Thus, the reception stability of the PDCCH can be controlled by adjusting

Confidential
the number of CCEs of the PDCCH. The PDCCH supports multiple formats as
listed in the table below.
PDCCH format Number of CCEs (n) Number of REGs Number of PDCCH bits
0 1 9 72
1 2 18 144
2 4 36 288
3 8 72 576
The other way to protect the DCI bits is power boosting for PDCCH. Modulation
for PDCCH is fixed as QPSK, thus EPRE (Energy per RE) can be flexibly
controlled without any signaling to UE. Boosting PDCCH power by 3 dB has
same similar effects as increasing PDCCH format by one level. Larger PDCCH
format uses more CCEs per PDCCH, and causes shortage and higher collision
probability of CCEs in PDCCH region. Especially PDCCH format 3 needs 8
consecutive and unallocated CCEs, so Samsung eNB often uses PDCCH format 2
with 3 dB Boosting instead of PDCCH format 3.
However, transmission power may exceed maximum power if there are a lot of
boosted PDCCHs. The maximum excess of transmission power is as the table
below under assumption that every RE in PDCCH region is boosted as 3 dB.
CFI 1 CFI 2 CFI 3
0.2 dB 0.5 dB 0.8 dB
Samsung eNB supports a solution to restrict actual transmission power under the
maximum power. When CCE_POWER_RESTRICTION (CHG-MACPDCCH-
FUNC) is set as 1, number of allocated CCEs is calculated as twice the allocated
CCEs if CCEs are boosted by 3 dB. Calculated number of CCEs are aggregated,
and restricted by number of total available CCEs. If calculated number of CCEs is
more than the total available, eNB increases PDCCH symbol or terminate PDCCH
resource allocation when PDCCH symbol is already maximum value. Hence, total
PDCCH transmission power cannot exceed maximum power by using this
solution.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-MACPDCCH-FUNC and set CCE_POWER_RESTRICTION as true

(= 1) to enable this function.
• Run CHG-MACPDCCH-FUNC and set CCE_POWER_RESTRICTION as
False (= 0) to disable this function.
Key Parameters
parameters.
Parameter Descriptions of CHG-MACPDCCH-FUNC/RTRV-MACPDCCH-FUNC
CCE_POWER_REST ON/OFF Status of the PDCCH allocation function which constrains PDCCH allocation
RICTION so that the sum of PDCCH transmission power does not exceed the maximum
transmission power.
• 0: This feature is disabled.
• 1: This feature is enabled.
Counters and KPI

PDCCH Cfi1 The cumulated number of used CFI 1
REFERENCE

Confidential
LTE-ME3301, Uplink Scheduler Enhancement

INTRODUCTION
Miscellaneous uplink scheduler enhancement items compose this feature.
BENEFIT
Improvement of scheduling latency and capacity
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
This functionality prevents the unnecessary generation of the UL grant which leads
to UL capacity improvement.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
If RoHC is not enabled, the RTP packet size for IPv6 is larger compared to the
RTP packet size for IPv4 since the IP header size is different as follows.
• RTP/UDP/IP header size
o IPv4: 40 byte
o IPv6: 60 byte
Samsung eNB calculates voice packet size as codec payload size +
MAC/RLC/PDCP header size + RTP/UDP/IP header size. Using the voice packet
size eNB allocates UL resource corresponding to scheduling request transmitted
by VoLTE UE (QCI1 bearer setup UE) to reduce scheduling latency caused by
Confidential
additional BSR transmission. If the calculated voice packet size is underestimated,

eNB allocate more frequently which leads to consume more PDCCH resource for
UL grant
For the efficient UL VoLTE scheduling in MAC scheduler, IP version is indicated
to the MAC scheduler and it allocates UL resource corresponding to the size of
RTP packet. If the parameter SUPPORT_IPV6 (CHG-DPHY-SPS) is set to '0
(False)' and '1 (True)', the indicated IP version is 4 and 6, respectively.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-DPHY-SPS and then set SUPPORT_IPV6 to 1 (TRUE).
• Run CHG-DPHY-SPS and then set SUPPORT_IPV6 to 0 (FALSE).
Key Parameters
parameters.
Parameter Descriptions of CHG-DPHY-SPS/RTRV-DPHY-SPS
SUPPORT_IPV6 This parameter indicates whether to support efficient UL scheduling
considering IP version 6 or not
• False: IPv4 is considered.
• True: IPv6 is considered.

Confidential
Counters and KPIs

Air MAC Packet AirMacULByte This counter is cumulated by the number of bytes
of the MAC PDU when there is a MAC PDU that
has successfully received through the PUSCH.
AirMacULThruAvg The calculated number that indicates the average
per second size of MAC PDUs which were
successfully received through PUSCH during the
AirMacULEfctivThruAvg The overall calculated size of MAC PDUs which
were successfully received through PUSCH during
the collection interval.
REFERENCE
None

Confidential
LTE-ME3304, Scheduling with QoS Support

INTRODUCTION
The LTE scheduler is responsible for dynamically allocating downlink and uplink
resources to the bearers appropriately while meeting their desired QoS level in
both downlink and uplink directions. Proportional Fair (PF) scheduler uses channel
quality (proportional factor) information and average throughput (fairness factor)
as the knobs to determine the priority of scheduling users. When QCI based
priority information is available, along with the scheduling metric, the priority and
delay budget information are used to decide upon the scheduling priority.
BENEFIT
• Operator can differentiate traffic data according to the QoS class of LTE users.
• LTE users can be served QoS with their priority in the system.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
TBD
FEATURE DESCRIPTION
Multi-user scheduling is one of the main features in LTE systems because it is in
charge of distributing available resources among active users to satisfy their QoS
needs. The data channel (that is, PDSCH) is shared with the users, meaning that
the spectrum should be distributed every TTI among them. Packet schedulers (for
both the downlink and the uplink) are deployed at the eNB and work with a
granularity of one TTI and one RBG in the time and frequency domain,
respectively. Resource allocation for each UE is based on the comparison of
scheduling metrics. Information considered in calculating the metric is
summarized as follows.
• Status of transmission queues
For UE with non-zero size of transmission queue is regarded as candidate for
scheduling in a given TTI.
• Channel Quality
Confidential
Reported CQI and RI values can be used to allocate resources to users

experiencing better channel conditions (for example, the higher the expected
throughput, the higher the metric).
• Resource Allocation History
Information about the past achieved performance can be used to improve
fairness (for example, the lower the past achieved throughput, the higher the
metric).
• Quality of Service Requirements
The QCI value associated to each flow might be used to drive specific policies
with the aim of meeting QoS requirements.
Key Design Aspect

• Spectral Efficiency
Effective utilization of radio resources is one of the main goals to be achieved.
To this aim, a specific policy can aim at maximizing, the spectral efficiency
(expressed in bit/s/Hz) by always serving users that are experiencing the best
channel conditions.
• Fairness
A blind maximization of the overall cell throughput surely enables effective
channel utilization in terms of spectral efficiency, but brings to very unfair
resource sharing among users. Fairness is therefore a major requirement that
should be taken into account to guarantee minimum performance also to the
cell-edge users (or in general to users experiencing bad channel conditions).
• QoS Provisioning
QoS aware scheduler differentiates the metric for each QoS class and gives
higher priority to QoS class with higher requirements.
Scheduling Strategies
In this section, we will illustrate different allocation strategies introduced for LTE
systems. To simplify the reading, we have classified them in three groups of
strategies:
1 channel-unaware
2 channel-aware/QoS-unaware
3 channel-aware/QoS-aware
Channel unaware-strategy
First introduced in wired networks, channel unaware strategies are based on the
assumption of time-invariant and error-free transmission media. While their direct
application in LTE is not realistic, they are typically used jointly with channel-
aware approaches to improve system performance.
• Round Robin
It performs fair sharing of time resources among users. In this context, the

Confidential
concept of fairness is related to the amount of time in which the resource is

occupied by a user. Note that this approach is not fair in terms of user
throughput especially in wireless systems, which depend not only on the
amount of occupied resources, but also on the quality of channel conditions.
Channel-aware/QoS-unaware Strategies
Based on the CQI feedbacks, which are periodically or aperiodically reported by
UE, the scheduler estimates the channel quality perceived by each UE. Hence, it
can predict the maximum achievable throughput.
• Maximum C/I Scheduling
The strategy known as Maximum C/I Scheduling aims at maximizing the
overall throughput by assigning RBs to the user that can achieve the maximum
throughput in a given TTI. On the other hand, it performs unfair resource
sharing since users with poor channel conditions (for example, cell-edge users)
will only get a low percentage of the available resources (or in extreme case
they may suffer from starvation).
• Proportional Fair Scheduler
A typical way to find a trade-off between requirements on fairness and spectral
efficiency is the use of Proportional Fair (PF) scheme.
The idea is that the past average throughput can act as a weighting factor of the
expected data rate, so that users in bad conditions are surely served within a certain
amount of time. Scheduling priority used in RB allocation is Proportional Fair (PF)
metric, and PF metric is calculated as follows:
Where, R_k (t) is the available data rate determined by channel quality, and this is
calculated based on the CQI/RI feedback from each UE as well as the occurrence
of ACK or NACK event for the previous allocations. AvgR_k (t) is the UE
average throughput. Parameters α and β are fairness weight and channel quality
weight, respectively. By configuring α and β dominant factor for the PF priority
can be changed. For example if α is greater than β, then fairness between users is
enhanced. On the contrary, if β is greater than α then system throughput can be
enhanced.
Channel-aware/QoS-aware Strategies
Standard allows nine QCI profiles. The eNB also supports configuring operator
specific QCI (128-254). Each QCI profile maps to a set of parameters such as
priority, and service type. The QCI information is received by the eNB from EPC.
Each UE can support more than one bearer and each bearer can be configured with
a specific QCI. The priority is used in the QoS based scheduling to prioritize the
users. The Service Type defines whether the service is a Guaranteed Bit Rate
Service or a Non-Guaranteed Bit Rate Service.
With QoS Based scheduling in Samsung Scheduler, the eNB always prioritizes
scheduling of GBR bearers over non-GBR bearers except QCI 5 (which is
typically configured for IMS Signaling). QCI 5 always has the highest priority.
Among GBR bearers, the QCI Priority and delay metric of the bearer are used to

Confidential
determine the ranking. Among non-GBR bearers only the PF Scheduler parameters
are used to prioritize the bearers.
• Delay Aware Scheduling for GBR bearers:
Where f (P_k) is priority term of user k and D_k (t) is delay term of user k. If
priority is different between users, priority term is used to prioritize and
allocate resource regardless of delay term. Priority value can be set by
PRIORITY (CHG-QCI-VAL).
• PF Scheduling for non-GBR bearers
Where R_k (t) is instantaneous data rate of user k in time t, AvgR_k (t) is
average throughput of user k in time t, α is fairness weight factor, and β is
channel quality weight factor. α and β values can be set by ALPHA and BETA
(CHG-DL-SCHED/CHG-UL-SCHED). For non-GBR bearers, the MAC
scheduler can allocate the resources based on the weight factor additionally
applied to the metric according to QCI of each bearer. As the value of the
weight factor increases, scheduling opportunity for corresponding non-GBR
bearer will increase. Detailed operation is described in LTE-SW4208 QCI-
based non-GBR Throughput Differentiation.
SYSTEM OPERATION
How to Activate
Key Parameters
There are no specific parameters associated with activation and deactivation.
parameters.
Use CHG-QCI-VAL to change the priority of QCI in the scheduling metric of
GBR bearers.

Confidential
Parameter Descriptions of RTRV-QCI-VAL/CHG-QCI-VAL

PRIORITY The priority of the QoS Class Identifier (QCI). The smaller value means the higher
priority.
Use CHG-DL-SCHED and CHG-UL-SCHED to change alpha and beta in the

scheduling metric of non-GBR bearers
Parameter Descriptions of RTRV-DL-SCHED/CHG-DL-SCHED AND RTRV-
UL-SCHED/CHG-UL-SCHED
ALPHA Fairness weight in PF scheduler. The larger alpha is, the better the fairness is.
BETA Channel quality weight in PF scheduler. The larger beta is, the better the channel
efficiency is.
Counters and KPIs

PRB Usage PrbDLAvg The average use rate for PRBs used for each QCI to transmit
DTCH traffic for the downlink during the collection interval.
PrbULAvg The average use rate for PRBs used for each QCI to transmit
DTCH traffic for the uplink during the collection interval.
Total PRB Usage TotGbrPrbDLAvg The average use rate for PRBs used to transmit downlink GBR
traffic during the collection interval.
TotNGbrPrbDLAvg The average use rate for PRBs used to transmit downlink non-
GBR traffic during the collection interval.
TotGbrPrbULAvg The average use rate for PRBs used to transmit uplink GBR
traffic during the collection interval.
TotNGbrPrbULAvg The average use rate for PRBs used to transmit uplink non-
GBR traffic during the collection interval.
REFERENCE

Confidential
LTE-ME3305, Semi-persistent Scheduling

INTRODUCTION
Semi-persistent Scheduling (SPS) allocates periodic resources semi-statically for
applications such as VoIP, instead of dynamic allocation of resources. SPS is
similar to a virtual circuit-based service. It is pre-configured to allow eNB and UE
to interoperate without the physical control channel.
BENEFIT
• Enabling this feature is useful for services such as VoIP for which the data
packets are small, periodic and semi-statically in size.
• This reduces the control signaling overhead and improves capacity.
DEPENDENCY
E-UTRAN (LTE)
LTE-ME3307 (UL sub-frame bundling)
• Others
The UE should support SPS.
LIMITATION
• For TDD, E-UTRAN does not support both TTI bundling and semi-persistent
scheduling at the same time in this release of specification. (3GPP TS. 36.331)
• In Samsung’s VoLTE operation scenario, the SPS is applied only for uplink,
not for downlink. In downlink VoLTE scheduling, the limiting factor
(bottleneck) of the VoLTE user capacity is PDSCH resource rather than
PDCCH resource. So the technical benefit of DL SPS is marginal.
SYSTEM IMPACT
capabilities.
This feature can reduce the control signaling load especially for the VoLTE UE.

Confidential
FEATURE DESCRIPTION
SPS operation
Dynamic scheduling requires sending the specific downlink or uplink resource
assignment message over signaling channel. It is unavoidable for Internet data
scheduling which is un-predictable and bursty. However, the packet transmission
of VoLTE traffic is more predictable in the sense of packet transmission period
and packet size.
By using the predictable nature of VoLTE traffic, SPS method assigns persistently
allocated transmission resources for the initial transmissions of VoIP packets
instead of dynamic scheduling. Due to the small size of VoLTE packet, signaling
overhead for dynamic scheduling can be relatively large for VoLTE call. SPS can
enhance the VoLTE capacity by reducing the signaling overhead in Physical
Downlink Control Channel (PDCCH). Semi-Persistent Scheduling (SPS) allocates
periodic resources semi-statically for applications such as VoIP, instead of
dynamic allocation of resources. SPS is similar to a virtual circuit-based service. It
is pre-configured to allow eNB and UE to interoperate without the physical control
channel.
The following figure shows the operation of SPS.
The initial transmissions of VoIP packets are sent without associated scheduling
control information. The SPS related configuration is configured by the higher
layer (Radio Resource Control, RRC). For example, the packet transmission
interval for initial transmission and SPS-specific UE identifier, that is, SPS C-
RNTI, are configured through RRC message.
SPS-Config::= SEQUENCE {
semiPersistSchedC-RNTI C-RNTI OPTIONAL, -- Need OR

Confidential
sps-ConfigDL SPS-ConfigDL OPTIONAL, -- Need ON

sps-ConfigUL SPS-ConfigUL OPTIONAL -- Need ON
}
SPS-ConfigUL::= CHOICE {
release NULL,
setup SEQUENCE {
semiPersistSchedIntervalUL ENUMERATED {
sf10, sf20, sf32, sf40, sf64, sf80,
sf128, sf160, sf320, sf640, spare6,
spare5, spare4, spare3, spare2,
spare1},
implicitReleaseAfter ENUMERATED {e2, e3, e4, e8},
p0-Persistent SEQUENCE {
p0-NominalPUSCH-Persistent INTEGER (-126..24),
p0-UE-PUSCH-Persistent INTEGER (-8..7)
...
}
}
RRC configuration for SPS is delivered to a UE when the UE establishes VoLTE

(QCI 1) bearer. When QCI 1 bearer is established, the serving eNB includes the
SPS configuration information if scheduling type for QCI 1 bearer is set to SPS
and number of VoLTE UEs (with on-going QCI 1) exceeds a certain threshold for
DL or UL. The detailed conditions and thresholds for SPS configuration (RRC) is
described in the below.
After RRC configuration, actual SPS activation or deactivation is decided by MAC
scheduler. Basically, UL SPS can be activated only when 1) TTI bundling is setup,
2) The supportable TBS > minimum required TBS for SPS, and 3) Talk-spurt is
detected by eNB.
When the above operation condition for SPS activation is satisfied for a specific
UE, QCI 1 bearer is served through SPS. Within a single VoLTE call served by
SPS, the SPS is dynamically activated and deactivated according to the VoLTE
traffic activity. SPS resource is activated during talk spurt while deactivated in
silent period during a VoLTE call. The detailed conditions and recommend
thresholds for activation and deactivation of SPS are described in the below.
According to the traffic activity SPS operates as follows:
During the period of a talk spurt:
• The SPS is activated by sending the specific PDCCH (SPS C-RNTI) with
allocating transmission resources.
• The semi-persistent allocation is released on detection of silence periods.
During a period of silence:
• The Silent Indication Descriptor (SID) packets are scheduled dynamically
every period.
The actual SPS transmission is started at reception of SPS resource allocation
(with NDI = 0) through SPS-C-RNTI over PDCCH. The timing and the allocated
resource in frequency domain become reference for the following semi-
persistently allocated packet transmissions. Based on the SPS interval received
through RRC and the first SPS resource allocation, the next packet can be
transmitted in the same resource block after the configured time interval elapses.

Confidential
As described in the figure below, no additional signaling over PDCCH is required

after the first SPS resource allocation. In Samsung eNB, SPS interval is set to 20
msec.
On the other hand, the HARQ retransmissions may occur unpredictable. In this
case, the resource for HARQ retransmissions of initial packets are assigned by
explicit signaling over PDCCH. The HARQ retransmissions in SPS is also
signaled by using SPS-C-RNTI, but NDI value is set to 1 to be distinguished from
initial packet allocation for SPS.
If the eNB finds that the talk spurt is finished, pre-allocated SPS resource
allocation is released by PDCCH signaling. Then, the incoming packets during
silent spurt, for example, Silence Interval Duration packets that are generated by
the VoIP codec, are allocated through dynamic scheduling. There exists a risk that
UE continuously sends the UL packets if the UE cannot receive PDCCH signaling
indicating SPS release. To reduce the risk, UE implicitly assumes that SPS release
is triggered when a certain number of MAC PDUs not containing any MAC SDUs
have been sent.
If the eNB finds that the talk spurt is started again, the eNB signals SPS resource
allocation again, and pre-allocate the resources periodically.
For SPS, proper TBS parameter (SEMI_PERSIST_SCHED_TBS_UL (CHG-
DPHY-SPS)) should be configured according to codec rate and RoHC, and so on.
The SPS allocation size is with the assumption of perfect RoHC. If the
compression is not perfect due to any reason the amount of reserved resources by
SPS cannot be enough. Then, the rest size of packets is dynamically scheduled by
the scheduler. The recommended TBS size of 41 bytes is calculated as follows:
• Assumption: AMR = WB 12.65 kbps, ROHC function ON
• TBS bit = RTP payload 34 byte + RTP/IP/UDP header 3 byte (assuming
perfect ROHC compression) + Margin 4 byte (including MAC/RLC/PDCP
header, MAC control element)

Confidential
Too large TBS size can increase the number of padding bits while too low TBS
size can also decrease the VoLTE capacity due to frequent fragmentation of
VoLTE packets.
The amount of reserved resources shall be adaptive to channel condition too. SPS
reactivation is triggered if the number of required PRBs increases or decreases due
to radio condition change. During serving VoLTE call, eNB keep monitoring the
required PRBs based on uplink SINR and changes the SPS configuration
(MCS/PRB) adaptively. Detailed conditions for SPS reactivation is described in
the below.
SPS operates in each cell separately. Therefore, the previous SPS context is not
continued after intra-eNB, inter-eNB handovers. SPS can be activated again in the
target cell based on the target cell’s configuration and condition.
Condition for SPS configuration, activation and deactivation

As explained in the above, configuration for SPS is performed in two-folds, which
are RRC configuration (L1) and MAC activation/deactivation (L2).
RRC configuration for SPS is delivered to a UE when the UE establishes VoLTE
(QCI 1) bearer. During QCI 1 bearer establishment, the serving eNB checks the
following conditions and SPS is configured if both the conditions are satisfied.
• SCHEDULING_TYPE (CHG-QCI-VAL) = SPS_Scheduling (for QCI 1)
• The number of VoLTE UEs (QCI 1) >
SPS_APPLY_NUM_UE_THRESH_UL (CHG-DPHY-SPS)
• SPS_ENABLE (CHG-DPHY-SPS) = 1 (TRUE)
The recommended parameter for SPS_APPLY_NUM_UE_THRESH_UL (CHG-
DPHY-SPS) is ‘0’ which means that SPS is used regardless of number of VoLTE
UEs if other conditions are satisfied.
If some QCI bearers are released and the configuration condition is no longer
satisfied, the existing VoLTE calls maintain the SPS configuration while newly
incoming calls are served by dynamic scheduling.
After RRC layer configuration for SPS, activation, deactivation, reactivation of
SPS is controlled in MAC layer.
The conditions for activating uplink SPS are given as follows:
• TTI bundling is setup and
• Supportable TBS > minimum required TBS for SPS and
• Talk-spurt decision by eNB
Supportable TBS is maximally-allocable TBS defined by TBS table [current MCS,
maximally allocable RB]. The MCS is determined by UL SINR and the maximally
allocable RB is determined by PHR. Required TBS size for SPS activation is set to
41 bytes, where 41 bytes is the expected TBS size for a single VoLTE packet. If a
UE’s supportable TBS is smaller than 41 bytes, the VoLTE packets shall be
fragmented and transmitted frequently, and it can cause degradation of service
quality. The minimum required TBS for SPS for activating SPS is not configurable

Confidential
by operator.
The amount of reserved resources shall be adaptive to channel condition too.
Conceptually,
SPS reactivation is triggered if the number of required PRBs increases or
decreases due to radio condition change. SPS reactivation is triggered when:
• All the activation conditions are satisfied and
• The required number of RB required increases or decreases due to radio
condition change. Note that this threshold is currently not controllable from
LSM CLI. Effective value for scheduler implementation is 1.
SPS deactivated on detection of silent spurt or basic condition for SPS (TTI
bundling) is no longer satisfied. SPS deactivation is triggered when one of the
following conditions is met:
• VoLTE call is released.
• On receiving IMPLICIT_RELEASE_AFTER (CHG-DPHY-SPS) consecutive
new MAC PDUs containing zero MAC SDUs, the eNB consider it the implicit
SPS release notification by UE. The parameter is 3GPP standard parameter
and it can be configured by operator.
• On detecting 2 consecutive DTXs in SPS scheduled resources, the eNB
assumes that the SPS has been released by UE. This parameter is an internal
parameter which cannot be flexibly configured.
On release of TTI bundling: when the supportable TBS exceeds the release
threshold.
SYSTEM OPERATION
How to Activate
Preconditions
• LTE-ME3307 (UL sub-frame bundling) is enabled.
• Run CHG-DPHY-SPS and set spsEnable to enable the UL SPS.
• Run CHG-QCI-VAL and set SchedulingType to enable the UL SPS.
DL SPS cannot be activated.

Confidential
• Run CHG-DPHY-SPS and set spsEnable to disable the UL SPS.

• Run CHG-QCI-VAL and set SchedulingType to disable the UL SPS.
DL SPS cannot be deactivated.
Key Parameters
parameters.
Parameter description of CHG-DPHY-SPS/RTRV-DPHY-SPS
SPS_ENABLE This parameter is used to enable to use SPS.
• 0: This feature is not used.
• 1: This feature is used.
Parameter description of CHG-QCI-VAL/RTRV-QCI-VAL

SCHEDULING_TYPE This parameter is the scheduling type of the QoS Class Identifier (QCI).
Entered parameter value is used for scheduling in the MAC layer.
parameters.
Parameter description of CHG-DPHY-SPS/RTRV-DPHY-SPS
SEMI_PERSIST_SCHED_TB This parameter provides information about the combinations of the allocated
S_UL number of RB, MCS and TBS size for UL SPS.
IMPLICIT_RELEASE_AFTER implicitReleaseAfter indicates the empty MAC SDU times before the SPS
release.
Parameter description of CHG-MAC-VOIP/RTRV-MAC-VOIP

SPS_APPLY_NUM_UE_THR This parameter is the threshold number of UEs for UL SPS application.
ESH_UL
Counters and KPIs


Confidential

Semi-Persistent Scheduling ULSpsConfigAtt Counted when eNB has sent the
RRCConnectionReconfiguration message including
UL SPS Configuration Setup to UE.
ULSpsConfigSucc Counted when eNB has received the
RRCConnectionReconfigurationComplete message
for the UL SPS Configuration Setup request from
UE.
ULSpsConfigNoAvg The number of UL SPS configured UEs is counted
every 2 seconds.
Semi-Persistent Scheduling in ULSpsActivationAtt The cumulated count of UL SPS activation attempts
MAC transmitted to UE through PDCCH.
ULSpsDeactivationAtt The cumulated count of UL SPS deactivation
attempts transmitted to UE through PDCCH.
REFERENCE

Confidential
LTE-ME3306, DL Frequency Selective

Scheduling
INTRODUCTION
Frequency selective scheduling is one of the key features to provide high spectrum
efficiency in LTE. To better exploit the channel selectivity, the packet scheduler is
located in the eNB, which allocates physical layer resources for the DL-SCH
transport channels every Transmission Time Interval (TTI). Resource assignment
consists of Physical resource block (PRB) and modulation and coding scheme
(MCS). Such scheduling depends heavily on the channel information available at
the eNB, which is provided by the channel quality indicator (CQI) reporting for
the downlink channel. The frequency selective scheduling allows the scheduler to
take into account of the sub-band CQI information for resource assignment to
exploit the channel variation in both the time and frequency domain.
BENEFIT
• Improve spectral efficiency of each UE, which increases network capacity.
• If there is a certain frequency domain which causes interference to adjacent
cells, this feature can be effective in interference reduction by avoiding the
frequency position affected by interference.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-ME3203 Aperiodic CQI Reporting
Aperiodic CQI reporting is required to operate this feature.
None
Coverage
None

Confidential
Interfaces
None
FEATURE DESCRIPTION
DL frequency selective scheduling improves spectral efficiency by utilizing
frequency selectivity of channel fading.
DL frequency selective scheduling involves in selecting the best sub-bands for RB

allocation. To achieve this, eNB enables UEs to report Sub-band CQI information.
There are two ways for sub-band CQI reporting: Periodic sub-band CQI and
Aperiodic CQI.
In periodic sub-band CQI, a set of contiguous sub-bands is called a bandwidth
part. In case of 20 MHz (100 RBs), 1 sub-band contains 8 RBs and 13 sub-bands
are present. Four bandwidth parts are present: 1 bandwidth part has 4 sub-bands
and the other has 3 sub-bands. In each CQI report period, the UE measures one
bandwidth part and reports the CQI of the best sub-band along with the selected
best sub-band information to the eNB. Each bandwidth part is sequentially cycled
through by UE during each CQI report period. This cycle of bandwidth parts is
repeated for a period before reporting a Wideband CQI (both UE selected sub-
band and Wideband CQI are reported when sub-band mode is enabled)
Aperiodic CQI is sent by PUSCH and is triggered by CQI request field within UL
grant. The type of CQI reporting is configured by eNB by RRC signaling:
wideband reporting, UE-selected sub-band reporting and higher layer configured
sub-band reporting. In UE-selected sub-band reporting, UE reports average CQI of
M number of preferred sub-band in addition to wideband CQI, while the UE
reports wideband CQI and sub-band CQI of all subbands in higher layer
configured sub-band reporting. Because higher layer configured CQI reporting
provides more information than UE-selected sub-band reporting, Samsung eNB
only operates higher layer configured CQI reporting.
Samsung eNB uses only aperiodic CQI for frequency selective scheduling because
sub-band information of periodic sub-band CQI is limited as follows.

Confidential
The UE does not feedback all sub-band CQI information, but only selected sub-
band CQI in bandwidth part. Sub-band CQIs for whole bandwidth are not
transmitted simultaneously, which makes CQI reporting period for entire
bandwidth longer.
This feature is only applicable when aperiodic CQI is activated, and can be turned
on by setting the parameter DL_FSS_FLAG (CHG-DLFSS-INF) as 1. If this
feature is turned on, the eNB uses sub-band CQI information for scheduling
frequency resources, where frequency selective scheduling allows eNB to choose
best (UE, sub-band) pair and allocate it. The below flow diagram describes the
scheduling process when frequency selective scheduling is applied.
If this feature is deactivated or sub-band CQI is not reported, best UE in a TTI is

scheduled regardless of frequency position in non-frequency selective scheduling.
SYSTEM OPERATION
How To Activate
Preconditions
• This feature is operated based on aperiodic CQI. Hence, aperiodic CQI needs
to be setup. Refer to the description of LTE-ME3203 Aperiodic CQI
Reporting.

Confidential
• Run CHG-DLFSS-INF, and then set DL_FSS_FLAG to 1.
• Run CHG-DLFSS-INF, and then set DL_FSS_FLAG to 0.
Key Parameters
parameters.
Parameter Descriptions of CHG-DLFSS-INF/RTRV-DLFSS-INF
DL_FSS_FLAG This parameter indicates whether the DL FSS function is on/off for each
cell.
• 0: DL FSS OFF
• 1: DL FSS ON
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME3307, UL Sub-frame Bundling

INTRODUCTION
When a User Equipment (UE) is at the cell edge, it may undergo power shortage
due to the transmission power limitation. To overcome the power shortage at cell
edge, 3GPP LTE provides TTI bundling operation. When TTI bundling is
configured, HARQ transmissions with incremental redundancy for a transport
block are performed in consecutive four TTIs without waiting for HARQ
feedback.
The eNB accumulates the received energy of all transmissions and sends HARQ
feedback only one time after the last redundancy version of the transport block is
received.
TTI bundling operation reduces the number of required HARQ feedback messages
and gives more HARQ combining gain within VoLTE packet delay budget. Thus,
VoLTE coverage can be extended.
BENEFIT
• The uplink cell coverage for VoLTE is extended by more HARQ combining
gain within VoLTE packet delay budget.
• User's VoLTE experience at the cell edge can be improved.
DEPENDENCY
E-UTRAN (LTE)
• Others
The UE should support TTI bundling.
LIMITATION
• This feature is supported in only FDD.
• This feature is not supported in Indoor Pico eNB.
• Aperiodic CQI is not triggered in TTI bundling mode.
SYSTEM IMPACT
FEATURE DESCRIPTION
TTI bundling (or subframe bundling) is intended to improve the uplink coverage

Confidential
performance of Voice over IP (VoIP), that is, improve air-interface performance in

scenarios where coverage is limited by the UE transmit power capability. The
general concept of TTI bundling is illustrated in the figure below. Each VoIP
transport block is passed to the physical layer where it has CRC bits added before
being channel coded using turbo coding. 4 duplicates of the channel coded
transport block are generated prior to rate matching.
Each duplicate is processed using a different Redundancy Version (RV). This
provides the eNB receiver with an Incremental Redundancy soft combining gain.
The set of codewords are modulated and mapped onto 4 consecutive uplink
subframe.
The following figure shows concept of TTI bundling.
TTI bundling groups 4 consecutive uplink TTI to generate an effective TTI

duration of 4 ms. These consecutive TTIs define the bundle size. 3GPP TS36.321
specifies a fixed bundle size of 4. Transmissions belonging to each bundle size are
sent without waiting for any HARQ acknowledgements. This corresponds to using
autonomous retransmission.
Each bundle of 4 TTI requires a single resource allocation from the eNB and a
single HARQ acknowledgements.
3GPP TS 36.321 specifies that a maximum of 3 resource block can be allocated
when TTI bundling is used. In addition, the modulation scheme is limited to
QPSK. The combination of up to 3 resource blocks and QPSK provides sufficient
capacity to transfer the bit rate required by VoIP. The same modulation and coding
scheme (MCS) and frequency bandwidth are used for all 4 TTI belonging to the
bundle.
The eNB can instruct the UE whether to use TTI bundling within the RRC

Confidential
Connection Setup, RRC Connection Reconfiguration or RRC Connection Re-

establishment messages.
The number of HARQ process is halved from 8 to 4. The eNB generates a single
HARQ acknowledgement for each bundle of 4 TTI. The timing of HARQ
acknowledgement is based on the timing of the last TTI within the bundle, that is,
the acknowledgement is sent 4 subframes after the last TTI in the bundle. The
complete bundle of 4 TTI is retransmitted when a HARQ acknowledgement
indicates that a retransmission is required.
The retransmission delay is 16 subframe (16 ms) when using TTI bundling,
comparing to the retransmission delay of 8 subframes (8 ms) when TTI bundling is
not used.
The figure below illustrates the set of 4 HARQ processes for TTI bundling with
FDD.
Each transmission belonging to a specific HARQ process is separated by 16
subframes.
The following figure shows FDD HARQ processes for TTI bundling.
The maximum number of uplink HARQ transmission is set by using

MAX_HARQ_TX_BUNDLING(CHG-TRCH-INF).
UL subframe bundling lowers effective transmission rate and improves the packet
error rate. Latency is also reduced because waiting time for HARQ ACK/NACK is
not required for the first four re-transmissions. Furthermore, signaling overhead is
reduced for ACK/NACK transmissions. On the other hand, spectral efficiency can
be degraded by applying the UL sub-frame bundling feature.
Setup or release of TTI bundling is instructed by sending RRC message to the UE.
On setup of TTI bundling, the existing/on-going HARQ processes are flushed.
When the measurement gap is configured for a UE for handover while TTI
bundling is operating, some of bundled subframes can be overlapped with the
measurement gap subframes. When the measurement gap is fully overlapped with
TTI bundle (4 consecutive PUSCH), TTI bundle is not transmitted. When the

Confidential
measurement gap is partially overlapped with TTI bundling, only the PUSCHs in
the non-overlapped TTI are transmitted.
On handover preparation, TTI bundling usage is transferred from source cell to
new cell. If TTI bundling is enabled in the target cell, the target cell decides to
apply TTI bundling in the new cell without checking the signaling quality. By
doing so, TTI bundling can be immediately initiated after handover is completed.
TTI bundling can be deactivated later based on enhanced uplink SINR and PHR
performance.
According to 3GPP standard, Periodic CQI cannot be multiplexed on PUSCH in
TTI bundling mode. It can be transmitted only on PUCCH in TTI bundling mode.
On the other hand, Samsung eNB does not configure aperiodic CQI in TTI
bundling to prevent performance degradation by UCI multiplexing.
Whether to use TTI bundling is instructed by RRC message to each UE. For
efficient operation of TTI bundling, the target UE selection is important because
unnecessary UL subframe bundling assignment can degrade the spectral
efficiency. If the UL subframe bundling feature is enabled in an eNB and the FGI
bit for subframe bundling is ‘1’, the eNB checks channel conditions of the UEs
with on-going QCI 1 VoLTE bearer and chooses some UEs in bad channel
condition for TTI bundling. Samsung eNB selects the UEs for TTI bundling by
optimized criterion. After TTI bundling is activated from QCI 1 criteria, all the
traffic as well as the VoLTE traffic is sent through bundled subframes.
Serving eNB setup TTI bundling when the following three conditions are satisfied:
• QCI 1 bearer is established.
• TTI_BUNDLING(CHG-TRCH-INF) = True
• Supportable TBS falls below a certain thresholds for 5 times of consecutive
checking with 100 msec interval, where it indicates bad uplink channel
condition. Supportable TBS is maximally-allocable TBS defined by TBS table
[current MCS, maximally allocable RB]. The MCS is determined by UL SINR
and the maximally allocable RB is determined by power headroom.
TTI bundling is released when one of the following two conditions is satisfied:
• QCI 1 bearer is released. or
• Supportable TBS becomes above a certain thresholds for 5 times of
consecutive checking with 100 msec interval, where it indicates good uplink
channel condition.
Optimized supportable TBS thresholds for TTI bundling setup and release are
given as follows:
• TTIB setup condition: supportable TBS < 41Byte (configurable by setting
TTIB_IN_TBS(CHG-TRCH-INF))
• TTIB release condition: supportable TBS >= 123Byte (configurable by setting
TTIB_OUT_TBS(CHG-TRCH-INF))
The above setup release thresholds are not configurable by operator, and these
thresholds are independent with SPS activation/deactivation thresholds. The
supportable TBS threshold for TTIB setup (41 bytes) threshold is same as the

Confidential
required TBS for a single VoLTE packet. The design philosophy is to setup TTIB
when the single VoLTE packets cannot be transmitted in a single TTI because the
fragmentation of VoLTE packets over multiple TTIs can cause the performance
degradation of voice service. TBS size of 41 bytes is calculated as follows:
• Assumption: AMR-WB 12.65 kbps, ROHC function ON
• TBS bit = RTP payload 34 byte + RTP/IP/UDP header 3byte (assuming
perfect ROHC compression) + Margin 4byte (including MAC/RLC/PDCP
header, MAC control element)
TTIB release condition of 123 bytes is determined to prevent frequent ping-pong
between TTI bundling setup/release which requires the RRC signaling.
Reference value for TTIB setup/release in terms of RSRP value

Note that these reference values are suggested based on rough estimation. It should
be used to get overall understanding only.
• TTIB setup: RSRP -115dBm ~ -120dBm (Pathloss 133dB~138dB)
• TTIB release: RSRP -105dBm ~ -110dBm (Pathloss 123dB~128dB)
Above reference values are given based on following assumptions.
• AWGN channel / Single cell (Without UL interference) / P0-nominal-PUSCH
= -80dBm
• UE Max Tx Power (=23dBm) where invalid if P0-nominal-PUSCH < -80dBm.
• RS power (per RE) = 18dBm
DRX in TTIB mode for handover operation

Samsung eNB, normally, releases the Discontinuous Reception (DRX) for UEs in
TTIB mode. However, it is needed to set DRX to perform handover operation to
femto cells. The eNB indicates measurement configuration with a purpose of
reportCGI to the UE as well as DRX configuration if handover operation to the
femto cell is required.
Disabling TTIB for video call UEs

Video call UEs have additional video traffic by separate bearer for conversational
video packets. However, TTIB mode cannot provide sufficient resource allocation
for both voice and video traffic due to the three-RB limitation in TTIB mode.
Therefore, if an UE have a bearer with specific QCI and ARP values, the eNB
determines that the UE is video call UE and it does not enable TTIB mode for that
UE. The operator can configure a pair of QCI and ARP values that are used for
video bearer by setting VIDEO_CALL_QCI and VIDEO_CALL_ARP (CHG-
MAC-VOIP).
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
• Run CHG-TRCH-INF and set ttiBundling to enable the UL subframe
bundling.
• Run CHG-TRCH-INF and set ttiBundling to disable the UL subframe
bundling.
Key Parameters
parameters.
Parameter description of CHG-TRCH-INF/RTRV-TRCH-INF
TTI_BUNDLING This parameter is used to enable to use TTI bundling.
• 0: This feature is not used.
• 1: This feature is used
MAX_HARQ_TX_BUNDLING The maximum HARQ transmission count is sub-frame bundling mode.
parameters.
Parameter description of CHG-TRCH-INF/RTRV-TRCH-INF
TTIB_IN_TBS Supportable TBS threshold for sub-frame bundling mode setup
TTIB_OUT_TBS Supportable TBS threshold for sub-frame bundling mode release
Counters and KPIs


Confidential

TTI Bundling TtibActAtt Attempt Count of TTIB Activation
TtibActSucc Success Count of TTIB Activation
TtibDeactAtt Attempt Count of TTIB Deactivation
TtibDeactSucc Success Count of TTIB Deactivation
TtibNoAvg Average number of the TTIB Activated UEs
TtibNoMax Maximum number of the TTIB Activated UEs
TTI Bundling Time TtibActTimeAvg Average time of the TTIB activated duration per UE
TtibActTimeRate Percentage of TTIB Activated duration in RRC Holding
Time per UE
TTI Bundling in MAC TotTtibPrbULAvg The average number of PRB usage used for UL Sub-
frame Bundling mode.
REFERENCE

Confidential
LTE-ME3308, UL Frequency Selective

Scheduling
INTRODUCTION
Frequency selective scheduling(FSS) is one of the key features to provide high
spectrum efficiency in LTE. FSS allocates favorable resources where UE can
experience better channel conditions in the frequency domain. Operator can turn
on and off the FSS by system parameters.
BENEFIT
The radio spectral efficiency of edge UE can be enhanced (about 3dB) by
achieving channel selection gain and/or interference reduction gain.
DEPENDENCY
None
LIMITATION
This feature cannot simultaneously operate with A-MPR NS_07-specific
scheduling function.
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-SW0316 Network Signaling Support
None
Coverage
It depends on the interference environment of the network.
Interfaces
None
FEATURE DESCRIPTION
If system parameter SUBBAND_TYPE (CHG-UL-SCHED) is ON, frequency
selective scheduling (FSS) can be applied for the system. FSS operation consists of

Confidential
two steps. The first is to determine the scheduling mode and the second is to
allocate resource.
First, scheduler can determine the scheduling mode at every subframe whether to
apply FSS or non-FSS (or wideband scheduling) according to uplink PRB usage.
FSS or Non-FSS can be chosen for low PRB usage or high PRB usage condition,
respectively. By comparing PRB usage with system parameter, FSS_RB_TH1
(CHG-UL-SCHED), usage condition can be decided.
Due to inherent characteristics of LTE UL, UE can transmit data with contiguous
RBs only. For this reason, UL FSS degrades performance if it is applied when
PRB usage is high. Scheduling mode switching prevents the cell throughput
degradation caused by contiguous resource allocation property in uplink.
Second, if determined scheduling mode is FSS, scheduler allocates the resource to

UE based on the priority of PRB and required PRB size.
Priority of RB reflects radio channel conditions such as interference level.
If determined scheduling mode is non-FSS, scheduler allocates the resource based
on the conventional scheduling.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
• Run CHG-UL-SCHED, and then set SUBBAND_TYPE to 1.
• Run CHG-UL-SCHED, and then set SUBBAND_TYPE to 0.
Key Parameters
parameters.
Parameter Descriptions of CHG-UL-SCHED/RTRV-UL-SCHED
SUBBAND_TYPE This parameter determines the PUSCH allocation scheme
• 0: wideband scheduling (Non frequency selective scheduling)
• 1: Frequency selective scheduling
parameters.
Parameter Descriptions of RTRV-UL-SCHED/CHG-UL-SCHED
FSS_RB_TH1 Number of PRB threshold for a cell to determines whether to apply FSS or
NonFSS for each subframe. If allocated PRB size of a cell is equal or smaller
than this threshold, FSS mode is selected.
Counters and KPIs

SINR Distribution SinrDistULWbPreComp_Bin0 ~ The cumulated number of Uplink SINR Binx
SinrDistULWbPreComp_Bin19 before Outer-loop compensation.
MCS ULReceivedMcs0 ~ The cumulated number of times PUSCH was
ULReceivedMcs31 received at MCSx. For this counter, statistics are
Uplink IOT Level PRB0 ~ PRB99 For this counter, the number of counts of
corresponding level is cumulated by 1 at every
time that IoT for PRB is collected.
REFERENCE
[1] 36.211 Physical channels and modulation
[2] 36.212 Multiplexing and channel coding

Confidential
LTE-ME3309, Resource Allocation

Enhancement for SIB
INTRODUCTION
Samsung eNB supports a resource allocation signaled with PDCCH DCI format
1A to SIB such that a set of contiguously allocated localized virtual resource
blocks (LVRBs) is assigned to SIB. Accordingly, this feature provides dynamic
resource allocation for SIB. It enables the operator can control the RB area and the
amount of RBs for SIB within feasible range to reduce the overhead on PDSCH
caused by SIB under reliable reception of SIB.
BENEFIT
Resource overhead on PDSCH caused by SIB can be adjusted in consideration of
reliable reception of System Information.
DEPENDENCY
E-UTRAN (LTE)
• Others
No eNB or UE dependency on this feature.
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
This feature supports to control the amount of RB allocated to SIB and RB area
within feasible range.
Adjusting resource allocation for SIB may influence SIB reception success rate,
which impacts on RRC re-establishment rate, and so on.
If operator reduces the number of RB allocated to SIB by decreasing
BCCH_SCALING_FACTOR (CHG-MACCTRLCH-FUNC) and/or increasing
BCCH_REDUCE_FACTOR (CHG-MACCTRLCH-FUNC), the network capacity
can be improved because of the reduced overhead on PDSCH caused by SIB.
Confidential
Coverage
Cell coverage is influenced by SIB reception success rate that can be varied with
the number of RBs allocated to SIB.
Interface
None
FEATURE DESCRIPTION
System information consists of Master Information Block (MIB) and System
Information Block (SIB). MIB is transferred using the BCH and PBCH. On the
other hand, SIBs are transferred using the DL-SCH and PDSCH. SIB1 has its own
RRC message whereas other SIBs are encapsulated within more general System
Information RRC message. After reading the MIB, UE acquires scheduling
information for other SIBs from schedulingInfoList in SIB1. A summary of the
information included within the MIB and SIBs is provided in the table below.
System Information Content
Master Information Block Downlink channel bandwidth, PHICH configuration, SFN
System Information Block 1 PLMN Id, tracking area code, cell selection parameters, frequency band, cell
barring, scheduling information for other SIB
System Information Block 2 Access class barring, RACH, BCCH, PCCH, PRACH, PDSCH, PUSCH,
PUCCH parameters, UE timers and constants, uplink carrier frequency
System Information Block 3 Cell reselection parameters
System Information Block 4 Intra-frequency neighboring cell information for cell reselection
System Information Block 5 Inter-frequency neighboring cell information for cell reselection
System Information Block 8 CDMA2000 neighboring cell information for cell reselection
System Information Block 9 Home eNB name
System Information Block 10 Earthquake and Tsunami Warning System primary notification
System Information Block 11 Earthquake and Tsunami Warning System secondary notification
System Information Block 12 Commercial Mobile Alert Service (CMAS) notification
System Information Block 13 MBMS Single Frequency Network (MBSFN) configuration information
System Information Block 14 EAB parameters
The set of Resource Elements used by the MIB on the PBCH is standardized by
3GPP, so does not require any additional signaling, that is, the PBCH occupies the
central 72 subcarriers within the first 4 OFDMA symbols of the second slot of a
radio frame. The same allocation is made for both FDD and TDD. On the other
hand, the set of Resource Elements used by the SIB on the PDSCH is not
standardized by 3GPP, so requires additional signaling to inform the UE of where
to look. The PDCCH is used to provide this additional signaling. The PDCCH
includes a CRC which is scrambled by the System Information RNTI (SI-RNTI) if
it includes resource allocation information relevant to the SIB. The SI-RNTI has
been standardized to have a single fixed value of FFFF.
The eNB is responsible for scheduling the Resource Blocks (RBs) used to transfer
the SIB. The MIB and SIB1 are broadcast at a rate which is specified by 3GPP.
The rate at which other SIBs are broadcast is implementation dependent.
Downlink Control Information (DCI) format 1A and 1C can be used to signal
Confidential
PDSCH resource allocation for the SIB. DCI format 1A supports

localized/distributed resource allocation and DCI format 1C supports distributed
resource allocation. Samsung eNB allocates the SIB in localized manner, so DCI
format 1A is used.
When DCI format 1A is used to schedule resources for the SIB, the modulation
scheme is always QPSK (the modulation scheme specified within the MCS table is
ignored). In addition, the TBS index is set equal to the value of the MCS bits
rather than reading its value from the MCS table. TPC Command is not used for
power control but is used to identify the transport block size (TBS). The most
significant bit is ignored while the least significant bit indicates whether column 2
or column 3 should be selected from within the TBS table, that is, the number of
allocated RBs should be assumed to be either 2 or 3 for the purposes of identifying
the TBS. A value of 0 corresponds to 2 assumed RBs, while a value of 1
corresponds to 3 assumed RBs. In summary, MCS index in the DCI format 1A
represents TBS of the SIB, and link adaptation is done by number of allocated RBs
only.
Samsung eNB supports the function to assign SIB RB offset by

SIB_NON_OVERLAP (CHG-MACCTRLCH-FUNC) parameter. If
SIB_NON_OVERLAP is set to 1, different set of consecutive RBs is allocated to
each cell for SIB with different RB offset determined by PCID. On the other hand,
if this parameter is set to 0, same set of RBs is allocated to all cell except the case
of In band NB-IoT or CAT-M1 support. If In band NB-IoT or CAT-M1 is served
to a UE, RB area for SIB may be different in each cell because RB reserved for In

Confidential
band NB-IoT bearer or RB that can be allocated to CAT-M1 bearer cannot be

allocated to SIB.
Samsung eNB supports to control the number of RBs allocated for SIBs. About the
way to adjust the number of RBs for SIBs, two different cases are categorized
according to the urgency of SIB reception: Normal case and Exceptional case.
Normal Case
In Normal case, a UE reads system information in RRC_IDLE mode to acquire the
parameters to access the network. While reading SIBs to access the network, the
UE does not need to acquire SIBs in urgent because they are repeated periodically.
From 3GPP specification, SIB1 is repeated at every 20 ms and other SIBs are
repeated according to the periodicity indicated by SIB1 in the range of {80 ms,
160 ms, 320 ms, 640 ms, 1280 ms, 2560 ms, 5120 ms}. In normal case, the less
number of RBs can be allocated to SIBs which may reduce resource overhead on
PDSCH and improve the system capacity.
Samsung eNBs control number of RBs for SIBs using two weight factor,
BCCH_SCALING_FACTOR (CHG-MACCTRLCH-FUNC) and
BCCH_REDUCE_FACTOR (CHG-MACCTRLCH-FUNC) in normal case as
follow.
• Number of SIB RBs = (The number of default RB) ×
(BCCH_SCALING_FACTOR) / (BCCH_REDUCE_FACTOR) / 16.
In above, the number of default RBs denotes the fixed number of RBs for SIB
which is determined by TBS of SIB. Samsung employs default RB to guarantee
the target BLER of the SIB transmission to all UE in a cell as 1%. For example,
the number of default RB for 20MHz bandwidth is described in following table.
TBS (byte) Number of default RB (20MHz)
7 8
11 8
18 12
22 16
26 16
28 20
32 20
41 24
49 28
57 32
63 36
73 40
85 44
93 48
105 52
113 56
121 60

Confidential
TBS (byte) Number of default RB (20MHz)

133 64
145 68
161 76
173 80
185 88
201 92
217 96
225 100
233 100
Exceptional case
In case of SI modification, a UE in RRC_CONNECTED should receive new
version of SIB to keep the communication with eNB. If the modified SIB is not
acquired to the UE during the modification period, the communication would be
fail and it causes interference to other UEs.
On the other hand, in case of notification of ETWS or CMAS, UE needs to receive
SIB immediately to response against disasters.
Samsung eNBs control number of RBs for SIBs using one weight factor,
BCCH_SCALING_FACTOR (CHG-MACCTRLCH-FUNC) in exceptional case as
follow.
• Exceptional case of SI modification:
o Number of RBs for SIB1 and SIB 2 = (Number of default RBs) ×
(BCCH_SCALING_FACTOR) / 16
o Number of RBs for other SIBs = (Number of default RBs) ×
(BCCH_SCALING_FACTOR) / (BCCH_REDUCE_FACTOR) / 16
• Exceptional case of emergent SIB notification:
o Number of RBs for SIB1, SIB10, SIB11, SIB12, and SIB14 = (Number of
default RBs) × (BCCH_SCALING_FACTOR) / 16
o Number of RBs for other SIBs = (Number of default RBs) ×
(BCCH_SCALING_FACTOR) / (BCCH_REDUCE_FACTOR) / 16
It is worth to note that the number of RBs for SIB in Normal case is same as that in
Exceptional case if BCCH_REDUCE_FACTOR = 1.
Samsung support SIB repetition for SIBs except SIB1 for Exceptional case. In case
of FDD, SIBs are repeated at most 5 times in subframe #0, subframe #2, subframe
#4, subframe #6, and subframe #8 within SI-window. Especially, if CAT-M1 is
supported, SIBs are repeated at most 4 times in subframe #1, subframe #3,
subframe #7, and subframe #9 within SI-window. On the other hand, in case of
TDD, SIBs are repeated at most 3 times in subframe #0, subframe #4, and
subframe #9.

Confidential
SYSTEM OPERATION
How To Activate
Preconditions
This feature does not need to be activated.
The operator can give the same effect as activation of this feature by changing
BCCH_SCALING_FACTOR, BCCH_REDUCE_FACTOR, and
SIB_NON_OVERLAP from default value, BCCH_SCALING_FACTOR = 16,
BCCH_REDUCE_FACTOR = 1, and SIB_NON_OVERLAP = 0, respectively.
The operator can give the same effect as deactivation of this feature by configuring
BCCH_SCALING_FACTOR, BCCH_REDUCE_FACTOR, and
SIB_NON_OVERLAP as default value, BCCH_SCALING_FACTOR = 16,
BCCH_REDUCE_FACTOR = 1, and SIB_NON_OVERLAP = 0, respectively.
Key Parameters
parameters.
Parameter Descriptions of CHG-MACCTRLCH-FUNC/RTRV-MACCTRLCH-
FUNC
BCCH_SCALING_FACTOR This parameter determines the number of RBs for SIB in exceptional case,
which is given by:
(The number of default RB) × (BCCH_SCALING_FACTOR) / 16.
BCCH_REDUCE_FACTOR This parameter determines the number of RBs for SIB in normal case in
conjunction with BCCH_SCALING_FACTOR, which is given by:
(The number of default RB) × (BCCH_SCALING_FACTOR) /
(BCCH_REDUCE_FACTOR) / 16.
SIB_NON_OVERLAP This parameter determines whether the SIB RB offset is separately assigned by
PCID or not.

Confidential
Counters and KPIs

KPIs affected by the number of PDSCH resource or cell coverage such as DL
effective Tput, RRC Drop Rate, or RRC Re-establishment Rate may be influenced
by this feature.
RRC_REESTAB ConnReEstabAtt The cumulated number of RRCConnectionRe-
establishmentRequest messages received from the UE.
ConnReEstabSucc The cumulated number of RRCConnectionRe-
establishmentComplete messages received from the
UE during the RRC connection re-establishment
procedure.
PRB_TOTAL TotPrbDLAvg The average use rate for PRBs used to transmit
PDSCH/PBCH/PMCH during the collection interval.
TotPrbDLMin The minimum value of TotPrbDLAvg.
TotPrbDLMax The maximum value of TotPrbDLAvg.
REFERENCE
[1] 3GPP TS 36.211 E-UTRA Physical Channels and Modulations
[2] 3GPP TS 36.213 E-UTRA Physical Layer Procedures
[3] 3GPP TS 36.331 E-UTRA Radio Resource Control (RRC) Protocol
Specification

Confidential
LTE-ME3310, VoLTE Concurrent Rank

Adaptation
INTRODUCTION
For VoLTE quality maintenance, a robust connection of VoLTE packets must be
maintained. Especially, an inaccurate UE rank feedback may cause a great volume
of packet loss, resulting in VoLTE quality degradation. To guarantee robust
transmission of VoLTE traffic, transmission rank of VoLTE traffic is fixed to 1
regardless of the rank reported by UE.
BENEFIT
For a UE with multiple bearers including QCI1 bearer, robust transmission of
VoLTE traffic is possible by allocating rank1 regardless of the reported rank in
TTI including QCI1 bearer to be transmitted.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The VoLTE quality degradation is very sensitive to packet delay and packet loss.
Especially, an inaccurate UE rank feedback may cause a great volume of packet
loss as shown below. To guarantee robust transmission of VoLTE traffic,
transmission rank of VoLTE traffic is fixed to 1 regardless of the rank reported by
UE.

Confidential
Inaccurate UE feedback information

: Rank2
Real channel VoLTE

: Rank1 Packet loss !!!
Transmission rank is determined in consideration of conditions below.

• Rank reported from UE
• Buffer occupancy of QCI1 bearer in a particular TTI
For UE with only QCI1 bearer, transmission rank is fixed to 1 as shown below:

Confidential
Buffer occupancy of
other QCI bearers
Time
Buffer occupancy of
QCI 1 bearer
t t + 20 Time
2
Rank reported by UE
1
Time
Tx rank
1
Time
For UE without QCI1 bearer, transmission rank is determined by reported rank as

shown below:

Confidential
Buffer occupancy of
other QCI bearers
Time
Buffer occupancy of
QCI 1 bearer
t t + 20 Time
2
Rank reported by UE
1
Time
2
Tx rank
1
Time
For a UE with multiple bearers including QCI1 bearer, transmission rank is fixed
to 1 only when QCI1 bearer is transmitted. The rank of other bearers is determined
by reported rank as shown below:

Confidential
Buffer occupancy of
other QCI bearers
Time
Buffer occupancy of
QCI 1 bearer
t t + 20 Time
2
Rank reported by UE
1
Time
2
Tx rank
1
Time
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

VoLTE Quality Defect VoLTEDropRate The number of VoLTE Drop rate
VoLTEDLQualityDefectRate The number of DL Quality Defect rate
VoLTEIntraHoSuccessRate The number of VoLTE HO Intra Success rate

Confidential
REFERENCE

Confidential
LTE-ME3312, PRB Randomization

INTRODUCTION
PUSCH start PRB index is the same in all the cells. So, due to PUSCH overlap
between neighboring cells, PUSCH interference on the same frequency band is
high even in low - load scenarios. This feature reduces PUSCH overlap by
randomizing PUSCH start PRB index in each cell. This leads to PUSCH
interference mitigation which is especially effective in low - load scenarios.
BENEFIT
PUSCH interference is mitigated by reducing PUSCH overlap in neighboring
cells.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
SYSTEM IMPACT
capabilities.
Interdependent Feature: LTE-SW0316 Network Signaling Support
PRB randomization reduces UL inter-cell interference by changing the start PRB
index of PUSCH PRB allocation in neighboring cells. It is more effective in low to
medium UL load conditions as there is little or no PUSCH overlap between
neighboring cells if start PRB index is different in neighboring cells. It improves
UL residual BLER and UL MCS allocation. The improvement can be observed
through available counters for UL BLER and UL MCS distribution.
Coverage
None
Interfaces
None
Confidential
FEATURE DESCRIPTION
Even in an environment with low cell loading, inter-cell interference may be high
due to the same PRB allocation start point of each cell. Thus, a method, named
PRB randomization, which differently configures inter-cell PRB allocation start
point is required to reduce the interference. Inter-cell PRB randomization can be
blind-coordinated based on PCID (Physical Cell-ID). In each cell, PUSCH start
PRB index is selected based on PCID. PRB randomization method is more
effective in low to medium load scenarios. In multi-UE environments, the center
UEs in the cells in which start PRB index is decided to be in the middle of UL
band may have loss in terms of throughput because sufficient PRBs may not be
allocated due to resource pre-emption in the middle of UL band. However, peak
throughput can be achieved by the expansion of PRBs if there is no resource pre-
emption in the middle of UL band (single UE peak throughput can be achieved).
Operator can turn this feature ON or OFF and can also configure the number of
cells to be coordinated. Max number of coordinating cells can be up to 9.
The following is a case in which three cells are coordinated. In this case, PUSCH
is divided into 3 parts in the frequency domain (shown by dashed horizontal lines).
Start PRB index for each cell is selected based on the value of (PCID % 3). This
reduces PUSCH overlap between neighboring cells which, in turn, reduces
PUSCH interference in each cell.
The following figure is three cell coordinated PRB randomization
(COORDINATED_CELL_NUM (CHG-PUSCH-CONF) = 3).
The following figure is a case in which two cells are coordinated. In this case, PRB

Confidential
randomization can be operated based on whether PCI is an even or odd number. In

this case, the allocation direction is determined based on whether PCI is even/odd.
In other words, if PCI is an even number, the allocation direction is FORWARD,
and if odd, the direction is REVERSE.
The following figure is two cell coordinated PRB randomization
(COORDINATED_CELL_NUM (CHG-PUSCH-CONF) =2).
In addition, the start PRB index is configurable via PLD parameter

START_PRB_INDEX (CHG-PUSCH-CONF) when
COORDINATED_CELL_NUM (CHG-PUSCH-CONF) is 1.
Counters
SINR and MCS can be affected since the overlapped portions among neighbor
cells are controlled according to the start PRB randomization. We provide
UL_SINR_DISTRIBUTION and MCS families for SINR and MCS, respectively.
SYSTEM OPERATION
How to Activate

Confidential
Preconditions
• Run CHG-PUSCH-CONF and set the parameter
COORDINATED_CELL_NUM to the value larger than 1.
• Run CHG-PUSCH-CONF and set the parameter
COORDINATED_CELL_NUM to 1.
Key Parameters
This section provides the key parameters for activation, deactivation, and
parameters.
COORDINATED_CELL_ Number of cells coordinated by PRB randomization. Allocation start PRB index is
NUM decided based on the computation result of PCID %
COORDINATED_CELL_NUM. However, if COORDINATED_CELL_NUM = 1,
PRB allocation start point becomes a value assigned by START_PRB_INDEX, so
that it can be independently assigned per cell. This value can be selected from [1,
9].
parameters.
START_PRB_INDEX Valid only when COORDINATED_CELL_NUM is 1. Assigns PRB allocation start
index of the cell. This value can be selected in the range from 0 to 99.
Counters and KPIs

Table below outlines the counters associated with this feature.
The SINR and MCS can be affected since the overlapped portions among neighbor
cells are controlled according to the start PRB randomization.
SINR Distribution SinrDistULWbPreComp_Bin0 ~ The cumulated number of Uplink SINR

Confidential

SinrDistULWbPreComp_Bin19 Binx before Outer-loop compensation
MCS ULReceivedMcs0 ~ ULReceivedMcs31 The cumulated number of times PUSCH
was received at MCSx. For this counter,
statistics are collected periodically.
REFERENCE
None

Confidential
LTE-ME3314, Unified PF Scheduling for CA

INTRODUCTION
The feature provides the enhanced scheduling option for CA UE, which controls
the scheduling priority among different component carriers (CCs). The eNB
determines the scheduling priority of CA UEs while exchanging the scheduling
information of each CC. It supports fairness control of UEs among multiple CCs
and the spectrum resources are utilized more effectively among the CCs.
BENEFIT
• Fairness control between CA UE and non-CA UE among multiple CCs
• Load balancing between inter-CC by scheduling more on less loaded CC(s)
• Improvement on effective throughput by scheduling more on the CC(s) of
good channel condition
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
• To apply this feature, both PCell and SCell should be activated(CHG-DLCA-
SCHED, CA_FAIR_OPTION (1)).
• If there is any UE operating as inter-BBU CA (non-ideal backhaul), this
functionality is not applied to such a UE.
SYSTEM IMPACT
capabilities.
With this feature, effective throughput can be improved.
FEATURE DESCRIPTION
The feature 'Unified PF Scheduling for CA' can be activated and deactivated on
per cell basis. (CHG-DLCA-SCHED, CA_FAIR_OPTION)
• CA_FAIR_OPTION (0) : default scheduling option, that is, unified PF

Confidential
scheduling for CA is not applied to the cell

• CA_FAIR_OPTION (1) : enhanced scheduling option, that is, unified PF
scheduling for CA is applied to the cell
Feature Operation
In the enhanced scheduling option eNB calculates the multi-carrier PF metric from
CA UE’s aggregated throughput of all CCs, while in the default option it
calculates the single-carrier PF metric from each CC separately.
Table below outlines the case study of fairness control between CA UE and non-
CA UE.
Default scheduling option Unified PF scheduling option
(CHG-DLCA-SCHED/ (CHG-DLCA-SCHED/
CA_FAIR_OPTION(0)) CA_FAIR_OPTION(1))
Scheduling priority Within CC, CA UE has the same For system perspective, scheduling
priority as non-CA UE. Thus, CA priorities of CA UE and non-CA UE
UE has more priority among are same except when there are
multiple CCs compared with non- some system resources remaining
CA UE in the system perspective. in a few CCs.
CASE01 CA UE is serviced from all CCs, so CA UE and non-CA UEs are
it takes more resources than non- allocated almost same.
All CCs are high loaded with non-
CA UEs. (non-CA UEs which belong to the
CA UEs
CC with lowest load)
CASE02 CA UE is serviced from all CCs Mostly CA UE is serviced in low
even though it is already serviced loaded CC(s), thus having non-CA
Only a few CCs are highly loaded
enough from low loaded CC(s). UE to get more opportunity in high
with non-CA UEs. loaded CC(s).
CASE03 CA UE is serviced from all CCs. CA UE is serviced from all CCs.
All CCs are low loaded. For multiple CA UEs, each CA UE
is serviced mainly from the CC of
good channel condition.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-DLCA-SCHED and set CA_FAIR_OPTION to 1.

Confidential
• Run CHG-DLCA-SCHED and set CA_FAIR_OPTION to 0.
Key Parameters
parameters.
Parameter Descriptions of CHG-DLCA-SCHED/RTRV-DLCA-SCHED
CA_FAIR_OPTION This determines whether to enable or disable this feature:
• This feature is not used.
• This feature is used.
parameters.
CA_FAIR_OPTION This determines whether to enable or disable this feature:
• This feature is not used.
• This feature is used.
Counters and KPIs

with this feature.
REFERENCE

Confidential


Confidential
LTE-ME3401, Paging DRX

INTRODUCTION
In LTE, DRX mode can be enabled in both RRC_IDLE and RRC_CONNECTED
states.
In the RRC_IDLE state, the UE is registered with the Evolved packet system
Mobility Management (EMM) but does not have an active session. In this state the
UE can be paged for DL traffic, and this DRX mode can be called as paging DRX.
UE can also initiate UL traffic by requesting RRC connection with the serving
eNB. DRX mode can also be enabled in RRC_CONNECTED state. In the
RRC_CONNECTED state DRX mode is enabled during the idle periods during
the packet arrival process, and this DRX mode can be called as active DRX. When
there are no outstanding/new packets to be transmitted/received, eNB/UE may
initiate the DRX mode.
BENEFIT
Enabling this feature results in longer battery life times.
DEPENDENCY
MME
E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
When the UE does not have packets to be received and/or transmitted for a
specific period, the eNB may initiate the release of UE RRC connection and
request MME to release the UE S1 connection. Furthermore, eNB removes the
UEs context. MME and SGW only remove the eNB specific part of the UE
context.
During the idle mode, the UE wakes up periodically to listen to the DL
transmissions, following the DRX cycle. During the idle mode, the mobility is
fully controlled by the UE, since the network is not aware of the UE existence

Confidential
continuously. The UE should perform the signal quality measurements with

respect to the serving and neighboring eNBs according to measurement thresholds
recommended by the serving eNB. Based on the signal quality measure, the UE
selects a new serving eNB when the UE moves away from the current serving
eNB. When the system information advertised by the new serving eNB does not
include its tracking area, the UE will perform a tracking area update to indicate its
presence so that the network knows where to page the UE in case of DL data
transfer. The UE may be paged by the network when there is data addressed to that
particular UE. The UE returns to RRC_CONNECTED mode as soon as packet
arrival is detected.
Two parameters Default DRX Cycle and nB (CHG-PCCH-CONF) are transmitted
in SIB2 which allow UEs to calculate the period and determine when to wake up
to monitor for the paging message. Default DRX Cycle can be set by configuring
parameter DEFAULT_PAGING_CYCLE (CHG-PCCH-CONF), and nB can be set
by configuring parameter N_B (CHG-PCCH-CONF).
During the idle mode, the UE wakes up periodically to listen to the DL
transmissions, following the DRX cycle.
The following figure shows paging procedure.

Confidential
1) When the S-GW receives a downlink data packet for a UE, it buffers the
downlink data packet and identifies which MME is serving that UE.
2) The MME responds to the S-GW with a Downlink Data Notification Ack
message.
3) The MME sends a Paging message to eNBs belonging to the tracking areas in
which the UE is registered.
4) The eNB calculates the paging occasion for the paged UE, and the paging is
transmitted at the time of the UE paging occasion.
The Paging occasion will depend on whether DRX is utilized. If UE-specific DRX
is not configured by the upper layer, the eNB will then utilize
DEFAULT_PAGING_CYCLE (CHG-PCCH-CONF) configuration parameter
value as the default DRX cycle. After transmission of the Paging message, the
eNB will peg the AttPaging counter to keep track of number of paging attempts.
5) When UE receives a paging indication, the UE initiates the UE triggered
Service Request procedure.
The UE in RRC idle mode uses DRX to reduce power consumption. The DRX
cycle determines how frequently UE check for paging messages. The default DRX
cycle is broadcast within System Information Block 2 (SIB2). It can have values of
32, 64, 128 or 256 radio frames. These figures correspond to time intervals of 320,
640, 1280 and 2560 ms.
The UE can also propose its own DRX cycle length within the Attach Request and
Tracking Area Update Request messages. The set of allowed values are the same
as those used within SIB2. When eNB receives UE-specific DRX cycle from
MME in paging message, the smaller of the two DRX cycles is used, such as the
minimum of the default DRX cycle and the UE specific DRX cycle.
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-PCCH-CONF/RTRV-PCCH-CONF

Confidential
DEFAULT_PAGING_CYCLE This parameter is required to calculate the paging frame and paging
occasion.
When DRX is used, the UE monitors a single paging occasion per DRX cycle.
If UE specific DRX is not set by the upper layer, the defaultPagingCycle is
applied as the default DRX cycle.
N_B This parameter required to calculate the paging frame and paging occasion
using the TS.36.304 method, which is a multiple of the parameter
DEFAULT_PAGING_CYCLE. Related Specifications: 3GPP TS 36.304
Counters and KPIs

Paging DiscardedNbr Paging record count discarded in the eNB
AttPaging Paging transmission attempt count
REFERENCE

Confidential
LTE-ME3402, Active DRX

INTRODUCTION
In LTE, discontinuous reception (DRX) is one of the techniques to lower the
battery power consumption of UEs. Packet data traffic is very bursty because data
is transmitted for a short period and then, there is no transmission for a long time.
From a data delivery delay point of view, it is better if a UE observes downlink
control signal in each subframe and reacts instantly according to the traffic
condition to receive uplink scheduling grant or downlink data transmission.
However, power consumption of the UE is also an important point. From this point
of view, DRX technique improves power consumption of the UE in active (or
RRC_CONNECTED) state.
BENEFIT
This feature lowers the power consumption of UEs, resulting in longer battery life
times.
DEPENDENCY
LIMITATION
When eDRX cycle is configured, legacy long DRX cycle should be set to
2560 ms and user & signaling inactivity timers should be set to longer than
10.24 s.
SYSTEM IMPACT
capabilities.
None
This feature allows the UEs to go into power-saving mode when they are inactive
in both DL and UL. So, it increases the battery life of the UEs.
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
In LTE, a UE in DRX mode does not monitor PDCCH and goes to power saving
mode. These parameters are configured via higher layer signaling and are
described in following table.
DRX Parameters Description
DRX Cycle Specifies the periodic repetition of on-duration followed by a possible period
of inactivity
On Duration timer Specifies the number of consecutive subframes at the beginning of a DRX
cycle
DRX Inactivity Timer Specifies the number of consecutive PDCCH-subframes after successfully
decoding a PDCCH indicating an initial UL or DL user data transmission for
the UE
DRX Retransmission Timer Specifies the maximum number of consecutive PDCCH-subframes for as
soon as a DL retransmission is expected by the UE
DRX Short Cycle Specifies the periodic repetition of the On Duration followed by a possible
period of inactivity for the short DRX cycle
DRX Short Cycle Timer Specifies the number of consecutive subframes for which the UE follows the
short DRX cycle after the DRX Inactivity Timer has expired
DRX Start Offset Specifies the subframe where the On DurationTimer starts in DRX cycle
These DRX parameters are mapped into as follows:

DRX Parameters Configurable parameters Related Command
DRX Cycle LONG_DRXCYCLE_START_OFFSET_TYPE_NORMA CHG-DRX-INF
L
On Duration timer ON_DURATION_TIMER_NORMAL
DRX Inactivity Timer DRX_INACTIVITY_TIMER_NORMAL
DRX Retransmission DRX_RETRANSMISSION_TIMER_NORMAL
Timer
DRX Short Cycle SHORT_DRXCYCLE_NORMAL
DRX Short Cycle Timer DRX_SHORT_CYCLE_TIMER_NORMAL
The eNB generates DRX Start Offset using DRX Cycle and sends it to UE in RRC
msg.
The general concept of active DRX is illustrated in figure below.

Confidential
An inactivity timer is started after each period of activity. This timer defines the
number of consecutive inactive subframes which the UE must experience before
using DRX mode. The timer is stopped and re-started if there is any activity while
it is running. The UE monitors the PDCCH continuously while the inactivity timer
is running. When the inactivity timer expires, there is an optional period of short
DRX cycle. Short DRX cycle is used because in general, the probability of further
activity is greater during the time window immediately after any previous activity.
The eNB instructs the UE whether it should use short DRX cycle. If short DRX
cycle is not used, long DRX cycles starts after inactivity timer expiry. By default,
Samsung eNB uses long DRX cycle only because short DRX cycle signaling can
be a burden on signaling compared to its effectiveness in lowering UE's power
consumption.
The eNB can instruct the UE to enter DRX mode immediately using the DRX
Command MAC control element. The DRX Command MAC control element does
not have any payload. It is signaled simply by sending a DL-SCH MAC sub-
header with the Logical Channel Identity (LCID) set to 11110. Also, it is noted
that UEs in RRC_CONNECTED mode are required to complete handovers when
moving from one cell to another. In this case, a UE must exit DRX to send an UL
RRC Measurement Report message when the signal strength from a neighboring
cell becomes sufficiently strong to trigger a handover.
Enhancement for eMTC UEs

The eMTC UE-specific DRX can be turned ON or OFF using the IS_EMTC_DRX
flag. If this flag is TRUE, then eMTC UE-specific DRX parameters are used.
Otherwise, legacy UE DRX parameters are used. The following eMTC UE-
specific DRX parameters are available. Their functions are the same as the
corresponding DRX parameters for legacy LTE UEs. These parameters can be
configured separately for CE mode A and B.
• ON_DURATION_TIMER_CE_MODE
• DRX_INACTIVITY_TIMER_CE_MODE
• DRX_RETRANSMISSION_TIMER_CE_MODE
• DRX_UL_RETRANSMISSION _TIMER_CE_MODE
• LONG_DRX_CYCLE_TYPE_CE_MODE
• SHORT_DRX_CONFIG_SETUP_CE_MODE
• SHORT_DRX_CYCLE_CE_MODE
• DRX_SHORT_CYCLE_TIMER_CE_MODE
Enhancement for NB-IoT UEs

The following NB-IoT UE-specific DRX parameters are available. Their functions
are the same as the corresponding DRX parameters for legacy LTE UEs. These
parameters can be configured separately per coverage class and can be changed
using CHG-DRX-INF command.
• ON_DURATION_TIMER_CL1, ON_DURATION_TIMER_CL2,

Confidential
ON_DURATION_TIMER_CL3
• DRX_INACTIVITY_TIMER_CL1, DRX_INACTIVITY_TIMER_CL2,
DRX_INACTIVITY_TIMER_CL3
• DRX_RETRANSMISSION_TIMER_CL1,
DRX_RETRANSMISSION_TIMER_CL2,
DRX_RETRANSMISSION_TIMER_CL3
• DRX_UL_RETRANSMISSION _TIMER_CL1,
DRX_UL_RETRANSMISSION _TIMER_CL2,
DRX_UL_RETRANSMISSION _TIMER_CL3
• DRX_CYCLE_CL1, DRX_CYCLE_CL2, DRX_CYCLE_CL3
Counters
Samsung eNB supports counters related to DRX activation and deactivation for
VoLTE UEs.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-DRX-INF and set DRX_CONFIG_SETUP to enable Active DRX
(LongDRX, shortDRX (optional)).
When ON_DURATION_TIMER_NORMAL or
DRX_INACTIVITY_TIMER_NORMAL parameter is set to high, the portion of
time that a UE keep awake is increased and thus the effect of power saving for the
UE is reduced.
Parameters for Active DRX are separated according to QCI type. In case a UE
opens multiple radio bearer with different QCI type, those parameters of highest
QCI priority is used.
In case of VoLTE (QCI type 1), it is recommended to set the parameters for Active
DRX is set carefully to be aligned with the period of VoLTE traffic.
Recommended Active DRX parameter for QCI type 1 is 20 ms for DRX Cycle and
psf10 for ON_DURATION_TIMER_NORMAL.

Confidential
• Run CHG-DRX-INF and set DRX_CONFIG_SETUP to disable Active DRX.
Key Parameters
parameters.
DRX_CONFIG_SETUP This parameter indicates whether to use the DRX.
• Setup: normal DRX profile is used in the normal status and reportCGI
DRX profile is used in reportCGI status.
• reportCGI: DRX is not used in the normal status and reportCGI DRX
profile is used in reportCGI status.
SHORT_DRXCONFIG_SETUP This parameter indicates whether to use the Short DRX mode.
• ci_Config_Release: Short DRX is not used.
• ci_Config_Setup: Short DRX is used.
Parameter descriptions of CHG-EMTCDRX-INF/RTRV-EMTCDRX-INF

DRX_CONFIG_SETUP_EMTC This parameter is the flag to determine whether to use the CDRX for
eMTC/cat.M1 UE.
• Setup: DRX is used for UE in CE mode A or CE mode B(TBD)
• SetupCeModeA: DRX is only setup for UE in CE Mode A
• SetupCeModeB: DRX is only setup for UE in CE mode B(TBD)
SHORT_DRXCONFIG_SETUP_ This parameter is used to indicate whether short DRX mode is supported or
CE_MODE_A not for UE in CE mode A.
• Release: Short DRX is not used for UE in CE mode A.
• Setup: Short DRX is used for UE in CE mode A.
ON_DURATION_TIMER_R13_ This parameter is used to determine whether R13 onDurationTimer value is
CE_MODE_ASETUP configured for CE mode A UE.
• Release: onDurationTimerR13CeModeA is not used,
onDurationTimerCeModeA value is used.
• Setup: onDurationTimerR13CeModeA is used,
onDurationTimerCeModeA value is not used.
DRX_RETRANSMISSION_TIM This parameter is used to determine whether R13 drx-RetransmissionTimer
ER_R13_CE_MODE_ASETUP value is configured for CE mode A UE.
• Release: drxRetransmissionTimerR13CeModeA is not used,
drxRetransmissionTimerCeModeA value is used.
• Setup: drxRetransmissionTimerR13CeModeA is used,
drxRetransmissionTimerCeModeA value is not used.
E_DRXCONFIG_SETUP_USAG This parameter indicates whether eDRX configuration for connected mode
E_EMTC is used for eMTC/cat.M1 UE

Confidential
• 0: eDRX for connected mode is not used.
• 1: eDRX for connected mode is used.
LONG_DRXCOMMAND_MAC_ This parameter indicates whether long DRX command MAC CE is used for
CE_USAGE_EMTC eMTC/cat.M1 UE.
• 0: long DRX command MAC CE is not used.
• 1: long DRX command MAC CE is used.
parameters.
PLMN_IDX It corresponds to the value of the same plmnIdx of PLDEnbPlmnInf. (In
other words, it is the PLMN ID corresponding to PLMN index that is set in
PLDEnbPlmnInfo (RTRV/CHG-ENBPLMN-INFO).
QCI QoS Class Identifier (QCI) index. The range is from 0 to 255. The standard
QCIs defined in the standard documents is 1 to 9. The user can use QCI
values 0 and 10-255.
ON_DURATION_TIMER_NORM Timer to monitor PDCCH in DRX mode in normal status. (5.7 in 3GPP TS
AL 36.321)
• Value in number of PDCCH sub-frames: psf1 for 1 PDCCH subframe,
psf2 for 2 PDCCH sub-frames and so on (6.3.2 in 3GPP TS 36.331)
{psf1, psf2, psf3, psf4, psf5, psf6, psf8, psf10, psf20, psf30, psf40, psf50,
psf60, psf80, psf100, psf200}
DRX_INACTIVITY_TIMER_NOR Timer to monitor PDCCH in DRX mode in normal status. (5.7 in 3GPP TS
MAL 36.321)
• Value in number of PDCCH sub-frames: psf1 for 1 PDCCH subframe,
psf2 for 2 PDCCH sub-frames and so on (6.3.2 in 3GPP TS 36.331)
{psf1, psf2, psf3, psf4, psf5, psf6, psf8, psf10, psf20, psf30, psf40, psf50,
psf60, psf80, psf100, psf200, psf300, psf500, psf750, psf1280, psf1920,
psf2560, spare10, spare9, spare8, spare7, spare6, spare5, spare4,
spare3, spare2, spare1}
DRX_RETRANSMISSION_TIME The timer used to monitor PDCCH in DRXmode in normal status. {psf1,
R_NORMAL psf2, psf4, psf6, psf8, psf16, psf24, psf33}
LONG_DRXCYCLE_START_OF The long DRX cycle and drx start offset values to run onDurationTimer in
FSET_TYPE_NORMAL DRX mode in normal status. The unit of the long DRX cycle is a sub-frame.
If the short DRXCycle is set to a value, this parameter is set to a multiple of
the short DRX-Cycle. The DRX start offset is set to an integer. For the
TDD, DL sub-frame or UL sub-frame can be set. {sf10, sf20, sf32, sf40,
sf64, sf80, sf128, sf160, sf256, sf320, sf512, sf640, sf1024, sf1280, sf2048,
sf2560} Available Value: multiple of 10 ms
SHORT_DRXCYCLE_NORMAL The short DRX cycle to run onDuration-Timer in DRX mode in normal
status. {sf2, sf5, sf8, sf10, sf16, sf20, sf32, sf40, sf64, sf80, sf128, sf160,
sf256, sf320, sf512, sf640} Available Value: multiple of 10 ms
DRX_SHORT_CYCLE_TIMER_ The timer used to enter long DRX mode in normal status
NORMAL
DRX_SELECTION_ORDER Selection order per QCI to select DRX profile.
ON_DURATION_TIMER_REPO Timer to monitor the PDCCH in DRX mode when intra-LTE reportCGI
RT_CGI status.
• Value is the number of PDCCH sub-frames: psf1 for 1 PDCCH
subframe, psf2 for 2 PDCCH sub-frames and so on. Defined values in

Confidential
specification (36.331): {psf1, psf2, psf3, psf4, psf5, psf6, psf8, psf10,
psf20, psf30, psf40, psf50, psf60, psf80, psf100, psf200}.
DRX_INACTIVITY_TIMER_REP Timer to monitor PDCCH in DRX mode when intra-LTE reportCGI status.
ORT_CGI • Value is the number of PDCCH sub-frames: psf1 for 1 PDCCH
psf20, psf30, psf40, psf50, psf60, sf80, psf100, psf200, psf300, psf500,
psf750, psf1280, sf1920, psf2560, spare10, spare9, spare8, spare7,
spare6, spare5, spare4, spare3, spare2, spare1}.
DRX_RETRANSMISSION_TIME The timer used to monitor PDCCH in DRX mode when intra-LTE reportCGI
R_REPORT_CGI status. Defined values in specification (36.331): {psf1, psf2, psf4, psf6,
psf8, psf16, psf24, psf33}
FSET_TYPE_REPORT_CGI DRX mode when intra-LTE reportCGI status. The unit of the long DRX
cycle is a sub-frame. The DRX start offset is set to an integer. For the TDD,
DL sub-frame or UL sub-frame can be set. Defined values in specification
(36.331): {sf10, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf256, sf320,
sf512, sf640, sf1024, sf1280, sf2048, sf2560}.
ON_DURATION_TIMER_INTER Timer to monitor the PDCCH in DRX mode when inter-RAT reportCGI
_RAT status.
• Value is the number of PDCCH sub-frames: psf1 for 1 PDCCH
psf20, psf30, psf40, psf50, psf60, psf80, psf100, psf200}.
DRX_INACTIVITY_TIMER_INT Timer to monitor PDCCH in DRX mode when inter-RAT reportCGI status.
ER_RAT • Value is the number of PDCCH sub-frames: psf1 for 1 PDCCH
specification (36.331): Enumerated{psf1, psf2, psf3, psf4, psf5, psf6,
psf8, sf10, psf20, psf30, psf40, psf50, psf60, psf80, psf100, psf200,
psf300, psf500, psf750, psf1280, psf1920, psf2560, spare10, spare9,
spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}.
DRX_RETRANSMISSION_TIME The timer used to monitor PDCCH in DRX mode when inter-RAT
R_INTER_RAT reportCGI status. Defined values in specification (36.331): {psf1, psf2, psf4,
psf6, psf8, psf16, psf24, psf33}
FSET_TYPE_INTER_RAT DRX mode when inter-RAT reportCGI status. The unit of the long DRX
cycle is a sub-frame. The DRX start offset is set to an integer. For the TDD,
DL sub-frame or UL sub-frame can be set. Defined values in specification
(36.331): {sf10, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf256, sf320,
sf512, sf640, sf1024, sf1280, sf2048, sf2560}.
For Cat-M1(eMTC) UE, parameter descriptions of CHG-EMTCDRX-INF/RTRV-

EMTCDRX-INF
PLMN_IDX It is corresponded to the value of the same plmnIdx of PLDEnbPlmnInf. (In
other words, it is the PLMN ID corresponding to PLMN index that is set in
PLDEnbPlmnInfo (RTRV/CHG-ENBPLMN-INFO).
QCI QCI(QoS Class Identifier) index. The range is from 0 to 255. The standard
QCIs defined in the standard documents is 1 to 9. The user can use QCI
values 0 and 10-255.
ON_DURATION_TIMER_CE_M This parameter is timer to monitor PDCCH in DRX mode for CE mode A
ODE_A UE. (5.7 in TS 36.321) Value in number of PDCCH sub-frames: psf1 for 1

Confidential
PDCCH subframe, psf2 for 2 PDCCH sub-frames and so on.
DRX_INACTIVITY_TIMER_CE_ This parameter is the timer to monitor PDCCH in DRX mode for CE mode
MODE_A A UE. (5.7 in TS 36.321). Values in number of PDCCH sub-frames: psf1 for
1 PDCCH subframe, psf2 for 2 PDCCH sub-frames and so on.
DRX_RETRANSMISSION_TIM This parameter is the timer to monitor PDCCH in DRX mode for CE mode
ER_CE_MODE_A A UE, when the DL retransmission is supposed to be occurred.
LONG_DRXCYCLE_TYPE_CE_ The long DRX cycle value to run onDurationTimer in DRX mode for CE
MODE_A mode A UE. The unit of the long DRX cycle is a sub-frame.
SHORT_DRXCYCLE_CE_MOD This parameter is the short DRX cycle to run onDurationTimer in DRX
E_A mode for CE mode A UE.
Available values: multiple of 10ms
DRX_SHORT_CYCLE_TIMER_ This parameter is the timer used to enter long DRX mode for CE mode A
CE_MODE_A UE.
ON_DURATION_TIMER_R13_ This parameter is timer to monitor PDCCH in DRX mode for CE mode A
CE_MODE_A UE. (5.7 in TS 36.321) Value in number of PDCCH sub-frames: psf1 for 1
PDCCH subframe, psf2 for 2 PDCCH sub-frames and so on. The available
value options are defined in DRX-config-R13 IE in TS 36.331.
DRX_RETRANSMISSION_TIM This parameter is the timer to monitor PDCCH in DRX mode for CE mode
ER_R13_CE_MODE_A A UE, when the DL retransmission is supposed to be occurred.
The available value options are defined in DRX-config-R13 IE in TS
36.331.
DRX_UL_RETRANSMISSION_ This parameter is the timer to monitor PDCCH in DRX mode for CE mode
TIMER_CE_MODE_A A UE, when the UL retransmission is supposed to be occurred(UL
asynchronous HARQ is used).
DRX_SELECTION_ORDER This parameter is the selection order per QCI to select DRX profile for
eMTC/cat.M1 UE. Different DRX parameter values are defined per QCI.
E_DRXCONFIG_CYCLE_STAR This parameter indicates the configured long DRX cycle value option when
T_OFFSET_TYPE_EMTC eDRX for connected mode is used for eMTC/cat.M1 UE. (Only value of
multiple 10 is operatable).
Counters and KPIs

Active DRX DrxActAtt Counted when eNB has sent the
RRCConnectionReconfiguration message
including Active DRX Setup to VoLTE UE.
DrxActSucc Counted when eNB has received the
RRCConnectionReconfigurationComplete
message for the Active DRX Setup request from
VoLTE UE.
DrxDeactAtt Counted when eNB has sent the
RRCConnectionReconfiguration message
including Active DRX Release to VoLTE UE.
DrxDeactSucc Counted when eNB has received the
RRCConnectionReconfigurationComplete
message for the Active DRX Release request
from VoLTE UE.
DrxNoAvg The number of active DRX activated VoLTE UEs
is counted every 2 seconds.

Confidential
REFERENCE

Confidential
LTE-ME3410, Extended DRX for Idle Mode

INTRODUCTION
The DRX feature is used for UE to reduce power consumption. 3GPP Rel 13
further enhanced the DRX function to allow UE operate in a longer DRX cycle
especially for power consumption sensitive UEs. When eDRX function (eDRX) is
enabled in the cell, eNB support broadcast eDRX related hyper SFN and
eDRXAllowed indicator in SIB1-BR. If the extended DRX cycle is agreed
between UE and MME, MME shall include the eDRX related parameters in the
paging message to eNB. The eNB uses the related eDRX parameter from MME to
determine the paging frame and paging occasion for the eDRX UE.
BENEFIT
This feature saves UE power under eDRX operation.
DEPENDENCY
• Required Network Elements:MME Rel. 13 UE for supporting extended DRX
• Prerequisite Features: LTE-SW1001 Paging; LTE-ME3401 Paging DRX
LIMITATION
• ETWS, CMAS, PWS requirement may not be met when a UE is in eDRX.
• PCCH, BCCH, HSFN number change and subframeBitmap for eMTC/NB-IoT
in system information can only happen in eDRX acquisition period boundary
to align paging occasion location between UE and eNB, therefore delay of
these parameters change on air interface can happen several hours, even in
system or eNB internal S/W block reboot.
• When the maximum eDRX cycle has been changed in MME during system
operation and the corresponding maximum eDRX paging time changed also in
eNB, MME need to notify UE of changed maximum eDRX cycle. If the MME
does not ask UE to update the modified eDRX cycle, UE may not receive the
broadcast paging.
SYSTEM IMPACT
FEATURE DESCRIPTION
Extended DRX for idle mode is introduced in release 13. This feature can help UE
significantly save battery power.

Confidential
The following is a brief overall signaling for eDRX operation:

• For eMTC, the eNB broadcasts Hyper SFN number and eDRX-Allowed is
broadcasted in SIB1-BR (figure below depicts an example of NB-IoT). For
NB-IoT, Hyper SFN number in NB-IoT system in MIB-NB and SIB1-NB.
• The UE and the MME negotiate the idle eDRX parameter during UE initial
attach procedure (and can be updated in TAU procedure), the eDRX
parameters include Paging eDRX Cycle and Paging Time Window (PTW).
• When there is UE specific downlink data, MME shall include the eDRX
paging parameter (Paging eDRX Cycle and PTW) in paging message and send
to eNB.
• The eNB determines the Paging hyper frame, paging frame, paging occasion
(PH/PF/PO), and then page UE via RRC paging procedure (for more details,
refer to 36.304 section 7).
The eNB also supports system information (SI) update notification by broadcasted
paging function in idle eDRX operation. Two special system information update
procedure according to idle eDRX function are introduced:
• eDRX SI update procedure
• Urgent SI update procedure
Extended DRX System Information Update Procedure

As eDRX cycle may longer than BCCH modification period, 3GPP defined a new
IE systemInfoModification-eDRX in the RRC paging message to notify UE of

Confidential
system information update. When some important system information (also called
eDRX SI, for example, information related with UE reachability, PCCH in
SIB2/SIB2-NB) is required to be changed, the eNB pages the UE in advance to
allow UEs operate in eDRX cycle > BCCH modification period to aware of system
information update at eDRX acquisition period boundary. If eDRX SI changed on
eNB, however, the UE side is not aware of the change, the UE may not able to
receive paging message due to the mismatch of paging hyper frame, paging frame
or paging occasion scheduling information. To avoid this scenario happen, the
following paging policy for eDRX SI update notification is applied
• Paging with ‘systemInfoModification-eDRX=TRUE’ should be sent as
follows:
o The eNB supports send paging in advance of SI update time if idle eDRX
is enabled. The maximum eDRX paging time based on an operator
configurable parameter MAX_EDRX_PAGING_TIME (CHG-NBEDRX-
INF/CHG-NBEDRX-INF) (in unit of BCCH modification period,
maximum value is 2.91 hour for NB-IoT. For eMTC, in unit of hyper SFN,
range is 1 - 256) according to the actual maximum eDRX cycle used in the
network. If the actual maximum idle eDRX cycle on MME changed, the
maximum eDRX paging time parameter need to be reconfigured according
to the changed maximum eDRX cycle to ensure the broadcasted paging
time no less than the actual maximum eDRX cycle used in the system.
o Paging with systemInfoModification=TRUE' is included in the last BCCH
modification period
• SI update time satisfy:
o BCCH modification period (BCCH MP)
o eDRX acquisition period boundary
The eDRX parameters for eMTC are as follows:

• CHG-PCCH-CONF
o DEFAULT_PAGING_CYCLE
O CHG-BRPCCH-CONF

Confidential
o N_B
o N_BV1310_USE
o NBV1310
• CHG-BRBCCH-CONF
o MODIFICATION_PERIOD_COEFF
o MODIFICATION_PERIOD_COEFFV1310_USE
• CHG-BRHSFN-CONF
o HSFN_OFFSET
• CHG-BRDLMAC-PARA
o INVALID_SUBFRAME_PAGING
o INVALID_SUBFRAME_SIB1
o INVALID_SUBFRAME_SI_MESSAGE
o INVALID_SUBFRAME_RAR
o INVALID_SUBFRAME_SELECTED
• CHG-PRACH-CONF
o PRACH_CONFIG_INDEX
• CHG-BRDLNB-IDLE
o PAGING_MPDCCH_NB_NUM
• CHG-BRDLREP-CONF
o PAGING_REPETITION_OPTION
The eDRX parameters for NB-IoT are as below:
• SIB2/SIB2-NB: PCCH (CHG-NBPCCH-CONF), BCCH(CHG-NBBCCH-
CONF)
• H_SFNOFFSET (CHG-HYPSFN-CONF)
• NPDSCH_REPETITION_SIB1_NB (CHG-NBSIB-INF)
• DL_BITMAP_CONFIG_SETUP/DL_BITMAP_LENGTH/SUBFRAME_PA
TTERN_LOW/SUBFRAME_PATTERN_HIGH (CHG-NBBITMAP-CONF)
Urgent System Information Updates Procedure

Considering some system parameters may have significant impact to service that
need to be updated on air interface to let UE know as soon as possible, Samsung
provides following urgent SI update procedure. The key system information
parameter includes:
• CellBarred {barred, notBarred}, PLMN Identity list, TAC, eDRX
ON/OFF(eMTC Only)
The above parameters in SIBs have impact to service or paging function. The SI
update at the second BCCH modification period boundary after the parameter
Confidential
change. The paging message that notify of system parameter change is broadcasted
according to a configurable parameter MAX_EDRX_PAGING_TIME (CHG-
EMTCEDRX-INF/CHG-NBEDRX-INF).
Configurable H-SFN Initialization Time

The eNB also supports configurable H-SFN initialization time based on GPS start
time to satisfy loose synchronization requirement with MME.
The H-SFN initialization time meets the following requirements:
• H-SFN = 0 start time shall be configurable by refer to GPS start time at eNB
level.
o Default H-SFN=0 at GPS start time, i.e. at 00:00:00 on 6 January, 1980
o H-SFN start offset can be configurable HSFN_OFFSET (CHG-BRHSFN-
CONF) for eMTC, H_SFNOFFSET (CHG-HYPSFN-CONF) for NB-IoT,
the range are integer value of {0~1048575} in unit is 10ms, where
1048575 means H-SFN wrap around period time (1024 SFN * 1024).
• H-SFN number can be changed during system operation
The H-SFN number at current GPS time (in unit of 10ms) can be calculated by
following formula:
• H-SFN# = ROUNDDOWN ((GPS time - HSFN offset)/1024,0)%1024. Where
GPS time increase by 1 in unit of 10 ms (1 SFN time). The current GPS time is
accumulated value since 00:00:00 on 6 January, 1980.
H-SFN=0 initialization recommends to start at #SFN=0, (i.e. H-SFN=0 start at
GPS time=0). HSFN_offset is recommended to be set to integer times of
1024(where SFN=0),i.e. 0, 1024, 2048, 3072, 4096 …, default value is 0.
After H-SFN number initialization, H-SFN# adds by 1 when SFN # wrap around.
Figures below depict the configurable H-SFN initialization time and H-SFN
number operation after initialization.

Confidential
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-BRHSFN-CONF/RTRV-BRHSFN-CONF
dbIndex This parameter is the index to reference the DB.
hsfnOffset This parameter is the Hyper-System Frame Number (H-SFN) offset. The
value of 1048575 means H-SFN wrap around period time (1024SFN * 1024)
for eMTC/cat.M1 UE.
Counters and KPIs


Confidential
with this feature.
REFERENCE
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) (Release 13)
Resource Control (RRC); Protocol specification (Release 13)
Application Protocol (S1AP) (Release 13)
Equipment (UE) procedures in idle mode (Release 13)
[5] 3GPP TS 23.682 Architecture enhancements to facilitate communications with
packet data networks and applications (Release 13)

Confidential
LTE-ME3501, UL Resource Allocation Type1

(Multi-Cluster PUSCH)
INTRODUCTION
The 3GPP enhances the uplink multiple access scheme by adopting clustered SC-
FDMA. It is similar to SC-FDMA but has the advantage that it allows non-
contiguous (clustered) groups of subcarriers to be allocated for transmission by a
single UE. The uplink transmission by Clustered SC-FDMA is called the resource
allocation type 1, while that of SC-FDMA is called the resource allocation type 0.
BENEFIT
The UE can be assigned the non-contiguous UL resources when the UL band are
split by preoccupying UEs.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
• UE baseband that supports multi-cluster PUSCH transmission.
• UE RF that supports the non-contiguous UL resource allocation for the radio
frequency band
• This features cannot simultaneously operate with A-MPR NS_07 specific
SYSTEM IMPACT
FEATURE DESCRIPTION
From 3GPP Release 10, the UE can support optional PUSCH non-contiguous
transmission (MultiCluster PUSCH transmission). eNB supports this feature when
MULTI_CLUSTER_PUSCH_SUPPORT (CHG-PUSCH-CONF) is set to
“TRUE”. However, this feature depends on UE capabilities for its baseband and
RF. By sending UE capability information (nonContiguousUL-RA-WithinCC-
Info-r10 and nonContiguousUL-RA-WithinCC-Info-r10) to eNB, UE notifies
whether its own baseband and RF support the MultiCluster PUSCH transmission.
The parameter "nonContiguousUL-RA-WithinCC-Info-r10" included in UE
capability information indicates whether the UE baseband is capable of
MultiCluster-PUSCH transmission. If it is indicated as “Supported”, it indicates
Confidential
transmission capability of the UE baseband. And the capability of the RU is

separately indicated by nonContiguousUL-RA-WithinCC-Info-r10 irrelevant from
transmission capability of UE baseband. When both the baseband and RU layer
capability of UE indicate non-contiguous transmission is supported, the UE is
capable of MultiCluster PUSCH transmission.
The resource allocation method for MultiCluster-PUSCH transmission, defined in
3GPP Release 10, is named RA type-1 (Resource allocation type-1). For
differentiation, the existing contiguous UL resource allocation method, supported
in 3GPP Release8/Release9, is named RA type-0 (Resource allocation type-0).
MultiCluster-PUSCH transmission became capable via Clustered SC-FDMA
(Single Carrier Frequency Division Multiple Access) structure. Clustered SC-
FDMA is a clustering function between DFT and IFFT blocks of the transmission
part of the UE, and enables up to 2 clustered DFT outputs to be entered to IFFT.
Therefore, PRB location can be non-contiguously allocated to IFFT input data by
up to 2 clusters.
The MultiCluster-PUSCH transmission operates in 1 CC (Component carrier). If a
UE supports UL-CA (UL Carrier Aggregation), transmission of non-contiguous
UL across multiple CCs is enabled, regardless of multiClusterPUSCH-withinCC-
r10 and nonContiguousUL-RA-WithinCC-Info-r10 information. However, even if
the UE is capable of UL-CA, if non-contiguous UL transmission is not supported
by the above two parameters, non-contiguous PUSCH transmission within CC is
disabled.
The basic unit of MultiCluster-PUSCH transmission, RBG (Resource Block

Group), is defined. MultiCluster-PUSCH transmission is allocable only in units of
RBGs. 3GPP Specifications define RBG size depending on UL-BW. The
following table shows RBG size (P) based on UL-BW, defined in Specifications,
and the number of RBGs based on P. RBG size is the number of PRBs, and the
total number of RBGs (N). For example, the RBG size is 2 and the number of
RBGs is 8 in 3MHz BW system.

Confidential
The following figure is an example of PUSCH area division by RBG in a UL-BW

= 3MHz system. In UL-BW = 3MHz system, the default PRB size is P=2, but
since , the remainder of divided by P is not 0. Thus, although its number of PRBs
is 1 (smaller than P=2), PRB index 14 is managed with a separate RBG. When
PRBs from index 6 to from 8 is occupied by other UE, the two non-contiguous
RBG 3 and RBG 6, except PUCCH region from index 0 to 2 and from 12 to 14 are
used for PUCCH, can be allocated to a UE capable of MutlCluster-PUSCH
transmission.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
Ensure that the following conditions are met before enabling this feature.
• The UE supports this feature in the band class.
• This feature is not supported by L9CA channel card.
• Run CHG-PUSCH-CONF and set MULTI_CLUSTER_PUSCH_SUPPORT to
enable the multi-cluster PUSCH allocation.
• Run CHG-PUSCH-CONF and set MULTI_CLUSTER_PUSCH_SUPPORT to
disable the multi-cluster PUSCH allocation.
Key Parameters
parameters.
MULTI_CLUSTER_PUSCH_SUP This parameter determines eNB to enable Resource allocation type-1
PORT (MultiCluster-PUSCH).
Counters and KPIs

with this feature.
REFERENCE

Confidential


Confidential
LTE-ME6006, PUCCH Over-

Dimensioning/PUCCH Blanking
INTRODUCTION
PUCCH resources are allocated in the edges of the system bandwidth. This is done
to provide frequency diversity. Also, by allocating PUCCH resources at the edges,
the uplink spectrum is not fragmented. Unfragmented spectrum can be used for
bigger PUSCH allocations for a single UE. If more PUCCH resources are needed,
new PUCCH resources are allocated next to previously allocated PUCCH
resource.
However, there can be one problem when PUCCH is allocated at the extreme
edges. In certain geographical areas, multiple Radio Access Network (RAN)
systems might be deployed. Sometimes these RAN systems use frequencies which
might be adjacent causing interference to each other. For example, if a GSM1800
band and a LTE1800 + band are deployed in the same or nearby geographical
areas, there can be interference for both the GSM and LTE systems. For the LTE
RANs, the interference is more likely to affect PUCCH channel regions, as
PUCCH are present in the ends of the system bandwidth. If the PUCCH channel
experiences severe interference caused by signal leakage, the access performance
and the downlink throughput can decrease. This is because, the PUCCH carries
vital information like CSI reports, HARQ feedbacks of downlink and even
scheduling requests for uplink in different uplink formats. The best solution is to
blank or mute these PUCCH regions in the edges affected by the interference. This
function feature utilizes flexible configuration of PUCCH to reduce or prevent out-
of-band interference.
BENEFIT
• The PUCCH can effectively resist interference from the out-of-band spurious
emission. As a result, PUCCH demodulation performance is not impacted.
• Performance metrics such as downlink throughput will also not be impacted
due to out of band interference.
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
This feature can be activated to prevent out-of-band interference from inter-RAT
system.

Confidential
SYSTEM IMPACT
FEATURE DESCRIPTION
The feature blanks or mutes the PUCCH regions affected by the interRAT
interference. This function feature utilizes flexible configuration of PUCCH to
reduce or prevent out-of-band interference.
Blanking of the PRBs cannot be done when the cell is active. Blanking can be
made only in when the cell is idle (Tx OFF).
As depicted in the above figure, some PRBs at the band edges are “blanked” at the
frequency edges, and the PUCCH resource index is allocated after the blanked
PRBs. The eNB can control the size of the PUCCH blanking PRBs. When this
feature is enabled, the first X PRBs of the PUCCH region on either side of the
uplink system bandwidth are not used-These are not allocated to any UE. These
PRBs are the ones, which experience interference. The eNB allocates the PUCCH
resource index after the X PRBs on either side of the system bandwidth. To set the
value of X shown in figure, the operator has to use the configurable system
parameter PUCCH_BLANKING_PRBS (X = PUCCH_BLANKING_PRBS/2).
When a PUCCH resource index (cqi-PUCCH-ResourceIndex) is allocated to a UE,
it avoids the PRB indexes from 0 to (PUCCH_BLANKING_PRBS/2-1), and from
(N_RB_UL-PUCCH_BLANKING_PRBS/2) to (N_RB_UL-1), where
PUCCH_BLANKING_PRBS is the number of PUCCH blanking PRBs configured
by system parameter and N_RB_UL is the number of UL RBs.
SYSTEM OPERATION
How to Activate
The operator can activate or deactivate this feature by setting the parameter
PUCCH_BLANKING_PRBS in PLD.

Confidential
Preconditions
Operator can choose whether configure PUCCH blanking size.
To activate PUCCH over-dimensioning/blanking, do the following:
• Run CHG-PUCCHCONF-IDLE, and then set PUCCH_BLANKING_PRBs >
0.
To deactivate PUCCH over-dimensioning/ blanking, do the following:
• Run CHG-PUCCHCONF-IDLE, and then set PUCCH_BLANKING_PRBs =
0.
Key Parameters
parameters.
• PUCCH over-dimensioning is not used in normal case, so this feature is
disabled by default. It is usually used in special case where LTE frequency
band interferes nearby band or experiences interference by nearby band.
• PUCCH_BLANKING_PRBs cannot be changed dynamically, and it can be
changed only in CELL_IDLE (Tx Off) state.
• This feature is activated when the parameter PUCCH_BLANKING_PRBS is
set to any other value other than 0.
• It is deactivated when PUCCH_BLANKING_PRBS is set to 0.
parameters.
Parameter Descriptions of RTRV-PUCCHCONF-IDLE/CHG-PUCCHCONF-
IDLE
PUCCH_BLANKING_PRBS Defines the number of PUCCH PRBs to blank
Counters and KPIs

with this feature.

Confidential
REFERENCE
[1] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical Channels and Modulation".
[2] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical layer procedures ".

Confidential
Chapter 8 Radio
Transmission
LTE-ME0103, FDD 5MHz Bandwidth

INTRODUCTION
In LTE system, total six channel bandwidths are standardized in 3GPP
specification, 1.4, 3, 5, 10, 15 and 20 MHz channel bandwidth. In this feature, the
5 MHz channel bandwidth configuration is described, which is composed of total
25 Resource Block (RB). One RB is 180 kHz frequency spacing, and the
bandwidth of 4.5 MHz is used for transmission except for guard bandwidth.
Therefore, the spectral efficiency is 90 % for 5 MHz channel bandwidth
configuration.
BENEFIT
An operator can support LTE service with channel bandwidth of 5 MHz.
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
3GPP has specified a set of six channel bandwidths, ranging from 1.4 MHz to 20
MHz. These are outlined in table below.
- Channel Bandwidth
1.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
Number of Resource Blocks 6 15 25 50 75 100
Number of Subcarriers 72 180 300 600 900 1200
The following figure depicts the channel bandwidth and transmission bandwidth
configuration for one EUTRA carrier.

Confidential
Chapter 8 Radio Transmission
• A Resource Block represents the basic unit of resource for the LTE air-
interface. The eNB scheduler allocates Resource blocks to UE when allowing
data transfer.
• The subcarriers belong to the Orthogonal Frequency Division Multiple Access
(OFDMA) technology in the downlink, and the Single Carrier Frequency
Division Multiple Access (SC-FDMA) technology in the uplink.
• There are 12 subcarriers per Resource Block so the number of subcarriers
equals 12 x number of Resource Blocks.
• Each subcarrier occupies 15 kHz so the total subcarrier bandwidth equals
15kHz x number of subcarriers.
• The downlink subcarrier bandwidth includes an additional 15kHz to
accommodate a null subcarrier at the center of all other subcarriers. The null
subcarrier provides 15 kHz of empty spectrum within which noting is
transmitted.
• The total subcarrier bandwidth is less than the channel bandwidth to allow for
the roll-off of emissions and to provide some guard band. The larger channel
bandwidths provide support for the higher throughputs. Smaller channel
bandwidths provide support for lower throughputs but are easier to
accommodate within existing spectrum allocations.
• 3GPP also specifies a subcarrier spacing of 7.5 kHz (in addition to the
subcarrier spacing of 15 kHz). The subcarrier spacing of 7.5 kHz is only used
in cells, which are dedicated to Multimedia Broadcast Multicast Services
(MBMS). There are 24 rather than 12 carriers per resource Block when using
the 7.5 kHz subcarrier spacing so the total bandwidth of a Resource Block
remains the same.
The following figure depicts the time-frequency resource structure in 5 MHz
channel bandwidth LTE system.

Confidential
Figure above presents the time-frequency resource structure for 5MHz channel
bandwidth LTE system. The time-frequency resources are subdivided according to
the following structure:
• The largest unit of time is the 10 ms radio frame, which is further subdivided
into ten 1 ms subframes, each of which is split into two 0.5 ms slots.
• Each slot comprises seven OFDM symbols in the case of the normal cyclic
prefix length, or six if the extended cyclic prefix is configured in the cell.
In the frequency domain, resources are grouped in units of 12 subcarriers (thus
occupying a total of 180 kHz), such that one unit of 12 subcarriers for duration of
one slot is termed a Resource Block (RB). The smallest unit of resource is the
Resource Element (RE), which consists of one subcarrier for duration of one
OFDM symbol. A resource block is thus comprised of 84 resource elements in the
case of the normal cyclic prefix length.
SYSTEM OPERATION
Confidential
How to Activate
Preconditions
• Lock the cell at LSM.
• Run CHG-CELL-IDLE to set DL_BANDWIDTH and UL_BANDWIDTH to
5 MHz.
• Unlock the cell at LSM.
• Run RTRV-CELL-IDLE to retrieve the Evolved Universal Terrestrial Radio
Access Network (E-UTRAN) cell information of the eNB.
• Lock the cell on LSM.
• Run CHG-CELL-IDLE and set DL_BANDWIDTH and UL_BANDWIDTH to an
appropriate bandwidth.
• Unlock the cell on LSM.
Key Parameters
feature.
parameters.
Parameter Descriptions of CHG-CELL-IDLE/RTRV-CELL-IDLE
PHY_CELL_ID This parameter is the Physical cell ID. It is used to allow the UE to
identify the cell in a radio section and the cell specific reference signal. It
should be allocated to avoid conflict between neighbor cells.
CELL_TYPE This parameter is classified into the cell operation type.
• macroCell: Operates many normal cells.
• openCell: Operates a single normal cell.
• hybridCell: Operates CSG cells as well as normal cells.
• csgCell: Operates only Closed Subscriber Group (CSG) cells.
DUPLEX_TYPE This parameter is the duplexing mode that is used while operating the

Confidential
cell.
• FDD: Frequency Division Duplex.
• TDD: Time Division Duplex.
UL_ANT_COUNT This parameter is the number of Rx antennas used by an operating cell.
EARFCN_DL This parameter is the downlink absolute radio frequency channel number
(ARFCN) used in the evolved universal terrestrial radio access network
(E-UTRAN) system of an operating cell. Center frequency must be
changed to E-UTRA absolute radio frequency channel number
(EARFCN). [Related Specifications] Refer to 3GPP TS 36.101, 5.7.3.
EARFCN_UL This parameter is the uplink absolute radio frequency channel number
(ARFCN) used in the Evolved Universal Terrestrial Radio access
Network (E-UTRAN) system of an operating cell. Center frequency must
be changed to EARFCN. [Related Specifications] Refer to 3GPP TS
36.101, 5.7.3.
DL_BANDWIDTH This parameter is the downlink bandwidth used by an operating cell.
• 1.4MHz: 1.4MHz bandwidth that uses 6 Physical Resource Blocks
(RBs).
• 3MHz: 3MHz bandwidth that uses 15 physical RBs.
• 20MHz: 20MHz Bandwidth that uses 100 physical RBs.
UL_BANDWIDTH This parameter is the uplink bandwidth used by an operating cell.
(RBs).
FREQUENCY_BAND_INDICATOR This parameter is the frequency band indicator information, which is
about where the frequency of an operating cell is located. This
information is broadcast to the UE through SIB 1.
GROUP_ID This parameter is the Group ID of the carrier where the cell belongs.
FORCED_MODE This parameter indicates whether to change the configuration regardless
of the cell status.
DL_CRS_PORT_COUNT This parameter is the number of downlink CRS ports that are supported
by the system.
Counters and KPIs

with this feature.

Confidential
REFERENCE
Base Station (BS) radio transmission and reception

Confidential
LTE-ME0104, FDD 10 MHz Bandwidth

INTRODUCTION
In an LTE system, total six channel bandwidths are standardized in 3GPP
specification: 1.4, 3, 5, 10, 15, and 20 MHz channel bandwidth. This feature
describes the 10 MHz channel bandwidth configuration, which is composed of
total 50 Resource Blocks (RBs). One RB is 180 kHz frequency spacing, and of 9
MHz bandwidth is used for transmission except for guard bandwidth. Therefore,
the spectral efficiency is 90 % for 10 MHz channel bandwidth configuration.
BENEFIT
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
3GPP has specified a set of six channel bandwidths, ranging from 1.4 MHz to 20
MHz. These are presented in table below.
- Channel Bandwidth
The following figure defines channel bandwidth and transmission bandwidth


Confidential
• An RB represents the basic unit of resource for the LTE air-interface. The eNB
scheduler allocates RBs to UE when allowing data transfer.
• There are 12 subcarriers per RB so the number of subcarriers equals 12 x
number of RBs.
• Each subcarrier occupies 15 kHz so the total subcarrier bandwidth equals 15
kHz x number of subcarriers. The downlink subcarrier bandwidth includes an
additional null subcarrier of 15 kHz at the center of all other subcarriers. The
null subcarrier is not used for downlink transmission.
the roll-off of emissions and to provide guard band.

Confidential
Figure above presents the time-frequency resource structure for 10 MHz channel
the following structure: the largest unit of time is the 10 ms radio frame, which is
further subdivided into ten 1 ms subframes, each of which is split into two 0.5 ms
slots. Each slot comprises seven OFDM symbols in case of the normal cyclic
prefix length or six if the extended cyclic prefix is configured in the cell. In the
frequency domain, resources are grouped in units of 12 subcarriers (thus
occupying a total of 180 kHz), such that one unit of 12 subcarriers for a duration of
one slot is termed a RB. The smallest unit of resource is the Resource Element
(RE), which consists of one subcarrier for duration of one OFDM symbol. A
resource block is thus comprised of 84 REs in case of the normal cyclic prefix.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
1 Lock the cell on LSM.
2 Run CHG-CELL-IDLE and set DL_BANDWIDTH and UL_BANDWIDTH to
10 MHz.
3 Unlock the cell on LSM.
Run RTRV-CELL-IDLE to retrieve the E-UTRAN cell information of the
eNB.
1 Lock the cell on LSM.
2 Run CHG-CELL-IDLE and set DL_BANDWIDTH and UL_BANDWIDTH to
an appropriate bandwidth.
3 Unlock the cell on LSM.
Key Parameters
feature.
parameters.
PHY_CELL_ID This parameter is the Physical cell ID. It is used to allow the UE to identify the
cell in a radio section and the cell specific reference signal.
It should be allocated to avoid conflict between neighbor cells.
DUPLEX_TYPE This parameter is the duplexing mode that is used while operating the cell.

Confidential
(ARFCN) used in the evolved universal terrestrial radio access network (E-
UTRAN) system of an operating cell. Center frequency must be changed to
E-UTRA absolute radio frequency channel number (EARFCN). [Related
Specifications] Refer to 3GPP TS 36.101, 5.7.3.
(ARFCN) used in the Evolved Universal Terrestrial Radio access Network (E-
UTRAN) system of an operating cell. Center frequency must be changed to
EARFCN. [Related Specifications] Refer to 3GPP TS 36.101, 5.7.3.
• 1.4 MHz: 1.4 MHz bandwidth that uses 6 Physical Resource Blocks (RBs).
• 3 MHz: 3 MHz bandwidth that uses 15 physical RBs.
• 20 MHz: 20 MHz Bandwidth that uses 100 physical RBs.
• 1.4 MHz: 1.4 MHz bandwidth that uses 6 Physical Resource Blocks (RBs).
• 20 MHz: 20 MHz Bandwidth that uses 100 physical RBs.
FREQUENCY_BAND_INDICA This parameter is the frequency band indicator information, which is about
TOR where the frequency of an operating cell is located. This information is
broadcasted to the UE through SIB 1.
FORCED_MODE This parameter indicates whether to change the configuration regardless of
the cell status.
DL_CRS_PORT_COUNT This parameter is the number of downlink CRS ports that are supported by
the system.
Counters and KPIs

with this feature.
REFERENCE
Confidential


Confidential

INTRODUCTION
In LTE system, total six channel bandwidths are standardized in 3GPP
specification: 1.4, 3, 5, 10, 15 and 20 MHz channel bandwidth. This feature
describes 15 MHz channel bandwidth configuration, which is composed of total
75 Resource Block (RB). One RB is 180 kHz frequency spacing, and the
bandwidth of 13.5MHz is used for transmission except for guard bandwidth.
Therefore, the spectral efficiency is 90 % for 15 MHz channel bandwidth
configuration.
BENEFIT
DEPENDENCY
• Network Elements Dependency: MCE
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
3GPP has specified a set of 6 channel bandwidths, ranging from 1.4MHz to
20MHz. These are presented in the table below.
- Channel Bandwidth
The following figure is Definition of Channel Bandwidth and Transmission

Bandwidth Configuration for one E UTRA carrier.

Confidential
data transfer.
kHz x number of subcarriers.
• The downlink subcarrier bandwidth includes an additional 15 kHz to
transmitted.
the roll-off of emissions and to provide some guard band.
• The larger channel bandwidths provide support for the higher throughputs.
Smaller channel bandwidths provide support for lower throughputs but are
easier to accommodate within existing spectrum allocations.
the 7.5 KHz subcarrier spacing so the total bandwidth of a Resource Block
remains the same. 3GPP References: TS 36.101, TS 36.104, TS 36.211
The following figure is time-frequency resource structure in LTE (15 MHz BW).

Confidential
The figure above presents a time-frequency resource structure in 15MHz channel

the following structure: the largest unit of time is the 10 ms radio frame, which is
further subdivided into ten 1 ms subframes, each of which is split into two 0.5 ms
slots. Each slot comprises seven OFDM symbols in the case of the normal cyclic
prefix length, or six if the extended cyclic prefix is configured in the cell. In the
frequency domain, resources are grouped in units of 12 subcarriers (thus
occupying a total of 180 kHz), such that one unit of 12 subcarriers for a duration of
one slot is termed a Resource Block (RB). The smallest unit of resource is the
Resource Element (RE), which consists of one subcarrier for duration of one
OFDM symbol. A resource block is thus comprised of 84 resource elements in the
case of the normal cyclic prefix length.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
• Lock the cell on LSM
• Run CHG-CELL-IDLE and set DL_BANDWIDTH and UL_BANDWIDTH to
15 MHz.
Key Parameters
parameters.
PHY_CELL_ID This parameter is the Physical cell ID. It is used to allow the UE to identify
the cell in a radio section and the cell specific reference signal.
cell.

Confidential
(ARFCN) used in the Evolved Universal Terrestrial Radio access Network
changed to EARFCN. [Related Specifications] Refer to 3GPP TS 36.101,
5.7.3.
(RBs).
(RBs).
of the cell status.
by the system.
Counters and KPIs

with this feature.
REFERENCE

Confidential
[2] 3GPP TS 36.104 Evolved Universal Terrestrial Radio Access (E-UTRA); Base
Station (BS) radio transmission and reception

Confidential

INTRODUCTION
LTE system supports variable channel bandwidth and, total six channel
bandwidths are standardized in 3GPP specification: 1.4, 3, 5, 10, 15, and 20 MHz
channel bandwidth. This feature describes 20 MHz channel bandwidth
configuration, which is composed of total 100 Resource Block (RB). One RB is
180 kHz frequency spacing, and the bandwidth of 18 MHz is used for
transmission. Therefore, the spectral efficiency is 90 % for transmission bandwidth
of channel bandwidth.
BENEFIT
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
3GPP has specified a set of 6 channel bandwidths, ranging from 1.4 MHz to
20MHz. These are presented in the table below.
- Channel Bandwidth
The following figure defines channel bandwidth and transmission bandwidth


Confidential
data transfer.
kHz x number of subcarriers.
• The downlink subcarrier bandwidth includes an additional 15 kHz to
transmitted.
the roll-off of emissions and to provide some guard band.
• The larger channel bandwidths provide support for the higher throughputs.
Smaller channel bandwidths provide support for lower throughputs but are
easier to accommodate within existing spectrum allocations.
the 7.5 kHz subcarrier spacing so the total bandwidth of a Resource Block
remains the same.
SYSTEM OPERATION

Confidential
How to Activate
Preconditions
• Lock the cell on LSM
• Run CHG-CELL-IDLE and set DL_BANDWIDTH and UL_BANDWIDTH to
20 MHz.
Key Parameters
parameters.
PHY_CELL_ID This parameter is the Physical cell ID. It is used to allow the UE to identify
the cell in a radio section and the cell specific reference signal.
cell.

Confidential
(ARFCN) used in the Evolved Universal Terrestrial Radio access Network
changed to EARFCN. [Related Specifications] Refer to 3GPP TS 36.101,
5.7.3.
(RBs).
(RBs).
of the cell status.
by the system.
Counters and KPIs

with this feature.
REFERENCE

Confidential


Confidential
LTE-ME0201, Frame Structure Type 1 (FDD)

INTRODUCTION
The frame structure considers only the time domain. 3GPP TS 36.211 specifies
frame structure Type 1 and Type 2. Frame structure type 1 is applicable to FDD
(both full and half-duplex), whereas frame structure type 2 is applicable to TDD.
In both cases, radio frames are numbered using their System Frame Number
(SFN).
For frame structure type 1, the transmission resource consists of a consecutive
radio frame. Each radio frame is composed of 10 subframes with 1 ms length and
each subframe is also composed of two slots, that is, totally radio frame is a
composition of 20 slots indexed 0 to 19. Each slot has duration of 0.5 ms.
Downlink and uplink transmission of a radio frame is divided in frequency
domain.
BENEFIT
An operator can support FDD-LTE service.
DEPENDENCY
None
LIMITATION
This feature is supported only on FDD.
SYSTEM IMPACT
FEATURE DESCRIPTION
Frame structure type 1 is applicable to both full duplex and half-duplex FDD. In
addition, this frame structure is applicable to both uplink and downlink. Figure
below depicts the frame structure type 1.

Confidential
A length of slot is Tslot = 0.5 ms. Two consecutive slots are defined as a subframe
of length 1 ms. A radio frame of 10 ms is composed of 20 slots, each of which is
numbered from 0 to 19. Channel-dependent scheduling and link adaptation are
determined on a subframe level. Therefore, the subframe duration corresponds to
the minimum Transmission Time Interval (TTI), which is of 1ms duration, less
than a 2 ms TTI for the HSPA and a minimum 10 ms TTI for the UMTS. A shorter
TTI for fast link adaptation is able to reduce delay and better exploit the time
varying channel through channel dependent scheduling.
Typical parameters for frame structure are as follows:
Transmission Bandwidth [MHz] 14 3 5 10 15 20
Occupied Bandwidth [MHz] 1.08 2.7 4.5 9.0 13.5 18.0
Guard Band [MHz] 0.32 0.3 0.5 1.0 1.5 2.0
Sampling Frequency [MHz] 1.92 3.84 7.68 15.36 23.04 30.72
FFT Size 128 256 512 1024 1536 2048
Number of Occupied 72 180 300 600 900 1200
Subcarriers
Number of Resource Block 6 15 25 50 75 100
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME0218, Normal CP
INTRODUCTION
Delay spread is generated by the set of different paths between the transmitter and
receiver when those paths have different delays. For example, a signal following a
direct line-of-sight path would arrive before a different version of the same signal,
which is reflected. An LTE receiver can be operated based on the received signal
without considering delay spread components. The cyclic prefix represents a guard
period at the start of each OFDMA symbol, which provides protection against
multi-path delay spread. The cyclic prefix also represents an overhead, which
should be minimized. The duration of the cyclic prefix should be greater than the
duration of the multi-path delay spread.
BENEFIT
• An operator can provide LTE service without being affected by inter-symbol
interference in normal cell coverage environment.
• End-user can receive LTE service without being affected by inter-symbol
interference in normal cell coverage environment.
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
LTE specifies both normal and extended cyclic prefix lengths. The normal cyclic
prefix is intended to be sufficient for the majority of scenarios, while the extended
cyclic prefix is intended for scenarios with particularly high delay spread.
Durations for the normal and extended cyclic prefix are presented in the table
below.

Confidential
CP is a guard interval to prevent inter-OFDM-symbol interference, which should

be larger than the channel delay spread. Therefore, the length of CP depends on
the environment where the network is operated, and it should not be too large as it
brings a bandwidth and power penalty. LTE defines two different CP lengths: a
normal CP and an extended CP, corresponding to seven and six OFDM symbols
per slot, respectively. The extended CP is for large cell coverage with large delay
spread at a price of bandwidth efficiency.
The normal CP is suitable for urban environment and high data rate applications.
The cyclic prefix is generated by copying the end of the main body of the OFDMA
symbol. These are shown in the following figure.
The signal is continuous at the interface between the cyclic prefix and the main
body of the symbol.
The following figure depicts an example of two delay spread components. The
second delay spread component is received later than the first delay spread
component. A Fast Fourier Transform (FFT) processing window is defined at the
receiver:
• The processing window captures the main body of the OFDMA symbol
belonging to the first delay spread component. The cyclic prefix belonging to
the first delay spread component is discarded
• The processing window captures part of the cyclic prefix and the majority of
the main body of the OFDMA symbol belonging to the second delay spread
component. Sections of the cyclic prefix and main body of the OFDMA
Confidential
symbol, which fall outside the processing window, are discarded.

In the extreme case, where the delay spread is equal to the duration of the cyclic
prefix then the FFT processing window fully captures the cyclic prefix belonging
to the delay spread component and discards a section of the main body of the
OFDMA symbol which has a duration equal to the cyclic prefix. The time domain
representation of each delay spread component within the processing window is
different (as shown in the figure below). However, the frequency domain
representation of each delay spread component within the processing window is
identical.
Figure below depicts delay spread components captured by FFT processing
window at the receiver.
Moving a section of the time domain signal from the end, and adding it to the start
does not change the frequency content of the signal, that is, the signal includes the
same set of frequency domain components and an FFT, which quantifies the set of
frequency domain components included within a time domain signal, generates the
same result. As long as the delay spread is less than the duration of the cyclic
prefix, each delay spread component provides a complete representation of the
signal within the FFT processing window, that is, the same set of frequency
components are generated by the FFT. This avoids the requirement to time
synchronization with individual delay spread components prior to decoding.
SYSTEM OPERATION
How to Activate

Confidential
Key Parameters
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME0219, Extended CP
INTRODUCTION
LTE specifies both normal and extended Cyclic Prefix (CP) lengths. The normal
CP is intended to be sufficient for the majority of scenarios, while the extended CP
is intended for scenarios with particularly high delay spread. In the case of
extended CP, the CP length of 16.7 us (512 Ts) for 15 kHz subcarrier spacing is
the same in all the six symbols. This leads to a CP overhead of 25 %.
BENEFIT
An operator can provide evolved Multimedia Broadcast Multicast Service
(eMBMS) service with this feature.
DEPENDENCY
• Prerequisite Features: eMBMS related features
LIMITATION
None
SYSTEM IMPACT
capabilities.
This feature is only available, when eMBMS service is operated in the operator's
network. The main eMBMS features are LTE-SV0501, eMBMS Basic function
and LTE-SV0504, Multicell and Multicast Coordination (MCE).
None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
The transmitter principle in any OFDMA system is to use narrow, mutually
orthogonal sub-carriers. In LTE, the subcarrier spacing is same regardless of the
total transmission bandwidth. Different subcarriers are orthogonal to each other,
Confidential
since the sampling instant of a single subcarrier; the other subcarriers have a zero
value.
The transmitter of an OFDMA system uses IFFT block to create the signal. Each
input for the IFFT block corresponds to the input representing a particular
subcarrier and can be modulated independently of other subcarriers. The IFFT
block is followed by adding the Cyclic Prefix (CP). The purpose of adding the
cyclic extension is to avoid Inter-Symbol Interference (ISI).
When the transmitter adds a cyclic extension longer than the channel impulse
response, the effect of the previous symbol can be avoided by removing the cyclic
extension at the receiver. The cyclic prefix is added by copying part of the symbol
at the end and attaching it to the beginning of the symbol, used to signal a break in
the transmission or as guard interval and the OFDM symbol seems to be periodic.
This guard interval is designed as such that it exceeds the delay spread in the
environment caused by multi-path effect. Therefore, the aim is to preserve
subcarrier orthogonality by ensuring the time dispersion is shorter than the cyclic
prefix length.
LTE specifies both normal and extended cyclic prefix lengths. The normal cyclic
prefix is intended to be sufficient for the majority of scenarios, while the extended
cyclic prefix is intended for scenarios with particularly high delay spread. The
types of the CP duration for 15 kHz subcarrier spacing are outlined in the
following table.
15 kHz Subcarriers 15 kHz Subcarriers
160 Ts 144 Ts 512 Ts
Duration 5.2 µs 4.7 µs 16.7 µs
Overhead 160/2048 = 7.8 % 144/2048 = 7.0 % 512/2048 = 25 %
While the normal CP is suitable for urban environment and high data rate
applications, the extended CP is for Multimedia Broadcast Multicast Service
(MBMS) and very large cell scenarios with large delay spread at a price of
bandwidth efficiency. The extended CP is defined in 15 kHz subcarrier spacing
and 7.5 kHz subcarrier spacing. The duration of the extended CP is 16.7 us for 15
kHz subcarrier spacing and 33.3 us for 7.5 kHz subcarrier spacing. These durations
are equivalent to the distances of 5 km and 10 km, and the overhead for total
resource is same as 25 %.
SYSTEM OPERATION
How to Activate

Confidential
Key Parameters
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME0401, Downlink QPSK, 16 QAM, 64 QAM

Support
INTRODUCTION
LTE systems employ Adaptive Modulation and Coding (AMC) to take advantage
of channel fluctuations. The basic idea is to transmit as high data rate as possible
when the channel is good, and transmit at a lower rate when the channel is poor to
avoid excessive dropped packets. Lower data rates are achieved by using a small
constellation, such as QPSK, and low rate error correcting codes such as rate 1/3
turbo codes. The higher data rates are achieved with large constellations, such as
64 QAM, and less robust error correcting codes, for example, either higher rate 3/4
codes. To perform AMC, the transmitter must have some knowledge of the
channel condition. Once it does, it can choose the modulation and coding
combination that will achieve the highest possible data rate while still meeting the
target Block Error Rate (BLER), which is usually set as 10 %.
BENEFIT
An operator can provide AMC according to the downlink channel condition.
DEPENDENCY
• Prerequisite Features: LTE-ME3201, Basic Link Adaptation
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Modulation
Resource Elements can be allocated to either a physical channel or a physical
signal.
In the case of physical channels, the modulation scheme applied to a specific
Resource Element depends on the type of physical channel to which the resource
element has been allocated.
Table below outlines the relationship between physical channel and modulation

Confidential
scheme.
Physical Channel Modulation Scheme Bit per Modulation Symbol
PBCH QPSK 2
PCFICH QPSK 2
PDCCH QPSK 2
PHICH BPSK 1
PDSCH QPSK, 16 QAM, 64 QAM 2, 4, 6
PMCH QPSK, 16 QAM, 64 QAM 2, 4, 6
• The PDSCH modulation scheme depends on the RF channel conditions and

the quantity of data to be transferred. The modulation scheme is selected by
the eNB link adaptation.
• The PMCH modulation scheme depends on the throughput requirements of the
broadcast service.
• 64 QAM provides the throughput by generating a single modulation symbol
from a group of 6 bits. 64 QAM requires good signal to noise ratio conditions
at the receiver to avoid misinterpreting one 64 QAM symbol as another.
• Bits are mapped onto the modulation symbols using Gray coding. This
approach helps to minimize bit errors by mapping the bits such that
neighboring modulation symbol differs by only a single bit. If the receiver
misinterprets a modulation symbol for its neighbor then only a single bit error
is introduced. The concept of Gray coding for 16 QAM is depicted in figure
below. The first two bits identify the quadrant while the second two bits
identity the location within the quadrant.
The following figure depicts modulation constellation for 16 QAM:
In the case of physical signals, modulation is not necessary because the signal
itself is a series of complex numbers, which can be mapped directly onto the
appropriate set of resource elements (3GPP reference: TS 36.211).

Confidential
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-ME0402, Uplink QPSK, 16 QAM Support

INTRODUCTION
LTE systems employ Adaptive Modulation and Coding (AMC) to take advantage
of channel fluctuations. The basic idea is to transmit as high data rate as possible
when the channel is good, and transmit at a lower rate when the channel is poor to
avoid excessive dropped packets. Lower data rates are achieved by using a small
constellation, such as QPSK, and low rate error correcting codes such as rate 1/3
turbo codes. The higher data rates are achieved with large constellations, such as
16 QAM, and less robust error correcting codes, for example, either higher rate 3/4
codes. To perform AMC, the transmitter must have some knowledge of channel
condition. Once it does, it can choose the modulation and coding combination that
will achieve the highest possible data rate while still meeting the target Block
Error Rate (BLER), which is usually set as 10 %.
The eNB supports QPSK and 16 QAM as modulation schemes in uplink and
selects an appropriate one according to uplink channel condition. UL 64 QAM is
optional in UE. To support UL 64 QAM, category 5 UE terminals (including UE-
category of 5, 8 or UE-categoryUL 5, 8, 13) need to be commercialized.
BENEFIT
An operator can provide AMC according to the uplink channel condition.
DEPENDENCY
• Prerequisite Features: LTE-ME3201, Basic Link Adaptation
LIMITATION
This feature does not include UL 64 QAM described as a separate feature.
SYSTEM IMPACT
FEATURE DESCRIPTION
Modulation
Resource elements can be allocated to either a physical channel or a physical
signal. In the case of physical channels, the modulation scheme applied to a
specific resource element depends on the type of physical channel to which the
resource element has been allocated.

Confidential
Table below outlines the modulation schemes applied to each uplink physical
channel.
Physical Channel Modulation Scheme Bits per Modulation Symbol
PUCCH BPSK, QPSK 1, 2
PUSCH QPSK, 16 QAM 2, 4
• The PUSCH modulation scheme depends on the RF channel conditions and

the quantity of data to be transferred. The modulation scheme is selected by
the eNB link adaptation.
• The PUCCH modulation scheme depends on the PUCCH format.
• Bits are mapped onto the modulation symbols using Gray coding. This
approach helps to minimize bit errors by mapping the bits such that
neighboring modulation symbol differ by only a single bit. If the receiver
misinterprets a modulation symbol as its neighbor then only a single bit error
is introduced. The concept of Gray coding for 16 QAM is depicted in figure
below. The first two bits identify the quadrant while the second two bits
identify the location within the quadrant.
Figure below depicts modulation constellation for 16 QAM.
In the case of physical signals, modulation is not necessary because the signal
itself is a series of complex numbers, which can be mapped directly onto the
appropriate set of REs (3GPP reference: TS 36.211).
SYSTEM OPERATION
How to Activate

Confidential
Key Parameters
Counters and KPIs

MCS ULReceivedMcs0 to 31 The cumulated number of received PUSCH per
MCS.
ULSchedulerMcs0 to 31 The cumulated number of PRBs assigned to
PUSCH per MCS.
REFERENCE

Confidential
LTE-ME0403, Uplink 64 QAM Support

INTRODUCTION
64 QAM allows 6 bits per modulation symbol, which is 3 times and 1.5 times
higher than that of QPSK or 16 QAM, respectively. It increases the spectral
efficiency and peak data rate. However, this higher order modulation is less robust
against noise and interference, thus it requires a higher SINR to meet the given
Packer Error Rate (PER) requirement. In LTE uplink system, 64 QAM capable UE
can use 64 QAM for MCS of higher than 20.
BENEFIT
64 QAM allows the higher spectral efficiency and peak data rate than that of
QPSK or 16 QAM.
DEPENDENCY
• Radio Technology: E-UTRAN (LTE)
• Others: UL 64 QAM capable UE is required (UE-category 5, 8 or UE-
categoryUL 5, 8, 13).
LIMITATION
None
SYSTEM IMPACT
capabilities.
None
UL capacity improvement exploits higher order modulation (64 QAM).
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Uplink scheduler supports 64 QAM according to UE category information and the
system parameter of ENABLE_SIX_FOUR_QAM (CHG-PUSCH-CONF). If the
parameter is set to FALSE, scheduler does not support 64 QAM. In this case, all
Confidential
UEs only use up to 16 QAM regardless of UE capability.

If the parameter is set to TRUE, scheduler allows 64 QAM for 64 QAM capable
UE (UE-category of 5, 8 or UE-categoryUL 5, 8, 13). These UEs can use 64 QAM
modulation if MCS between 21 and 28 is assigned. 16 QAM capable UEs can use
16 QAM up to MCS 24.
Since there is overlapped MCS range (that is, MCS 21 to 24) between 16 QAM
and 64 QAM, UL scheduler limits the maximum MCS as 20 until the UE category
information is obtained during the attach process. It prevents the uncertainty of
whether UE uses 16 QAM or 64 QAM.
64 QAM
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-PUSCH-CONF and then set enableSixFourQam to 1 (TRUE).

Confidential
• Run CHG-PUSCH-CONF and then set enableSixFourQam to 0 (FALSE).
Key Parameters
configuration of this feature.
To activate or deactivate this feature, run the associated command and set the key
parameter.
enableSixFourQam This parameter indicates whether to support 64 QAM at eNB. 64 QAM capable
UEs use 64 QAM when MCS index of 21-28 is assigned from eNB. If UEs are
not capable of supporting 64 QAM, they can support MCS index up to 24 using
16 QAM.
• False: 64 QAM is not supported.
• True: 64 QAM is supported.
Change this parameter value while the eNB is not operating. Changing the
parameter value while the eNB is operating requires special care because it
may cause abnormal operation.
Counters and KPIs

MCS ULReceivedMcs0 to 31 The cumulated number of received PUSCH per
MCS.
ULSchedulerMcs0 to 31 The cumulated number of PRBs assigned to PUSCH
per MCS.
REFERENCE
TS 36.213 Physical layer procedures

Confidential
LTE-ME0404, DL 256 QAM

INTRODUCTION
256 QAM is selected as a supportable modulation order from LTE release 12 and
can enhance each UE throughput. Especially, 256 QAM is expected to be more
useful in a small cell, because higher SNR can be supported in comparison to a
macro cell.
The existing tables dealing with MCS and TBS up to 64 QAM are modified for
considering 256 QAM in terms of MCS and TBS, to achieve throughput
enhancement via 256 QAM support and CQI conversion into Modulation order
Product Code Rate (MPR).
The present algorithm is to partially modify and complement the existing
algorithm to support 256 QAM. Contents relevant to CQI, MCS, and TBS are
complemented based on the standard.
BENEFIT
• Higher order modulation based on 3GPP Rel.12 Standard.
• More bits of information per symbol: 6 (64 QAM) to 8 (256 QAM).
• Higher spectral efficiency (up to 33 %).
64 QAM 256 QAM
DEPENDENCY
• HW dependency
o Support Channel Cards: Supported in LCC modem only
• Others: DL 256 QAM capable UE is required (UE category 11 to 14)

Confidential
LIMITATION
The eNB can support DL 256 QAM over the channel card based on S8400
modem.
SYSTEM IMPACT
capabilities.
None
In the RRH that does not meet EVM 3.5 %, DL Tput of high SINR area can be
decreased by BLER increase of 256 QAM RB.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
256 QAM support is enabled in category 11 to 14 UEs, and is mandatory for these
categories of UEs. Therefore, to support category 11 to 14 UEs, the corresponding
algorithm is complemented considering 256 QAM support:
SupportedBandEUTRA-v1250::= SEQUENCE {
dl-256QAM-r12 ENUMERATED {supported} OPTIONAL,
ul-64QAM-r12 ENUMERATED {supported} OPTIONAL
}
A 256 QAM supportable UE notifies such ability to the eNB via dl-256 QAM
information element (IE), when increasing UE capability.
As 256 QAM support is added, 4-bit CQI table, modulation and TBS index table,
and transport block size table, previously stated in the specification, were re-
defined in reference [3]. In reference [2], to use such newly defined 4-bit CQI
table, table usage is notified in a field named altCQI-Table in the CQI-
ReportConfig IE of the following RRC message.
altCQI-Table-r12 ENUMERATED {
allSubframes, csi-SubframeSet1,
csi-SubframeSet2, spare1} OPTIONAL -- Need OP
}
If the above field is presented, a newly defined CQI table is used; if not, the
existing CQI table is used. In addition, when using newly defined CQI table, DCI
format 1/1B/1D/2/2A/2B/2C/2D is used, and if the CRC is scrambled based on the
C-RNTI, resources are allocated by considering modulation and TBS index for
PDSCH2, which is newly defined in specification for 256 QAM. To enable DL

Confidential
256 QAM, set STATUS (CHG-DL256QAM-PARA) to 1.

The activation/deactivation function of 256 QAM CQI/MCS table according to the
channel condition is supported for 4 × 4 MIMO and 256 QAM capable UE. In 4 ×
4 MIMO, the throughput performance of 256 QAM can be degraded in a certain
channel condition and SINR range due to the high BLER of 256 QAM. By
limiting the activation of 256 QAM CQI/MCS table for 4 × 4 MIMO capable UE
in only high SINR region, the performance degradation can be minimized. To
enable the activation/deactivation function of 256 QAM CQI/MCS table, set
ADAP_ON_OFF_256QAM (CHG-DLCA-SCHED) to 1.
According to the standard, the activation/deactivation of 256 QAM CQI/MCS
table is accomplished through RRC reconfiguration.
The Hysteresis operation is needed for preventing the ping-pong between 256
QAM activation and deactivation. The performance degradation is possible during
the deactivation of 256 QAM due to Hysteresis operation.
The following figure shows an example of Hysteresis operation.
350
4 x 4 256 QAM Table

300 4 x 4 64 QAM MCS Table
250
200
150
256 QAM Activation Threshold

100 (64 QAM à 256 QAM)
50 256 QAM Deactivation Threshold

(256 QAM à 64 QAM)
0
10 15 20 25 30
To change the activation and deactivation threshold for 4 × 4 MIMO capable UE,
set ACT_THRE_256QAM (CHG-DLCA-SCHED) and DEACT_THRE_256QAM
(CHG-DLCA-SCHED) parameters, respectively. These threshold values are
determined by rank x spectral efficiency x 1024. The efficiency of CQI table in
TS36.213 Table 7.2 [3] can be used to determine the threshold value. For example,
if CQI = 14, the efficiency in the table is 5.1152. The activation threshold can be
determined by 4 (rank) x 5.1152 x 1024 = 20951. Based on the efficiency of CQI
14, the default threshold value for the activation is set to 21000. The default
threshold value for the deactivation is set to 14000 based on CQI 11.

Confidential
SYSTEM OPERATION
How to Activate
Preconditions
• To support this feature, both the eNB and the UE can support 256 QAM.
• This feature is supported in S8400 modem only. The operator need to set
STATUS = 1 in DU30 to turn on DL256 QAM.
• To turn on the activation/deactivation function of 256 QAM CQI/MCS table in
CA, all cells within the CA cluster (PCell and SCells combinations) have to set
ADAP_ON_OFF_256QAM to 1.
To activate this feature do the following:
• Run CHG-DL256QAM-PARA and set STATUS to 1 (TRUE).
To activate the activation/deactivation function of 256 QAM CQI/MCS table for 4
× 4 MIMO capable UE, do the following:
• Run CHG-DLCA-SCHED and set ADAP_ON_OFF_256QAM to 1 (TRUE).
• Run CHG-DL256QAM-PARA and set STATUS to 0 (FALSE). This is a
default value.
To deactivate the activation/deactivation function of 256QAM CQI/MCS table for
4 × 4 MIMO capable UE, do the following:
• Run CHG-DLCA-SCHED and set ADAP_ON_OFF_256QAM to 0 (FALSE).
This is a default value.
Key Parameters
feature.
parameter.
Parameter Description of CHG-DL256QAM-PARA/RTRV-DL256QAM-PARA
Status This parameter determines whether to enable or disable the DL 256 QAM feature:

Confidential
• 0 (FALSE): Not support
• 1 (TRUE): Support
To activate or deactivate the activation/deactivation function of 256 QAM

CQI/MCS table for 4 × 4 MIMO capable UE, run the associated command and set
the key parameter.
Parameter Description of CHG-DLCA-SCHED/RTRV-DLCA-SCHED
ADAP_ON_OFF_256 This parameter determines 256 QAM ON/OFF by 256 QAM reconfiguration
QAM message:
• 0 (FALSE): Not support
• 1 (TRUE): Support
To configure the activation/deactivation function of 256 QAM CQI/MCS table for
4 × 4 MIMO capable UE, run the associated commands and set the key
parameters.
ACT_THRE_256 QAM This parameter determines activation threshold of 256 QAM.
(Rank x spectral efficiency (modulation order x code rate) x 1024)
DEACT_THRE_256 QAM This parameter determines deactivation threshold of 256 QAM.
(Rank x spectral efficiency (modulation order x code rate) x 1024)
Counters and KPIs

Downlink HARQ DLResidualBlerRetrans0_ PDSCH BLER for the initial HARQ transmission
Transmission BLER in 256 QAM during the collection interval. It is the failure rate for
256 QAM supported the initial transmission and is a ratio of the number
of times the first re-transmission was carried out to
the number of times the initial transmission was
carried out for 256 QAM supported UEs.
DLResidualBlerRetrans1_ PDSCH BLER for the first HARQ retransmission for
256 QAM 256 QAM supported UEs.
DLResidualBlerRetrans2_ PDSCH BLER for the second HARQ retransmission
256 QAM for 256 QAM supported UEs.
DLResidualBlerRetrans3_ PDSCH BLER for the third HARQ retransmission for
DLResidualBlerRetrans4_ PDSCH BLER for the fourth HARQ retransmission
256 QAM for 256 QAM supported UEs.
DLResidualBlerRetrans5_ PDSCH BLER for the fifth HARQ retransmission for
DLResidualBlerRetrans6_ PDSCH BLER for the sixth HARQ retransmission for

Confidential

DLResidualBlerRetransMi The minimum PDSCH HARQ transmission number
n_256 QAM among which have positive value between
DLResidualBlerRetrans0_256 QAM and
DLResidualBlerRetrans6_256 QAM. HARQ
transmission number denotes 'X' in that 'Xth HARQ
retransmission' for 256 QAM supported UEs.
DLResidualBlerRetransM The maximum PDSCH HARQ transmission number
ax_256 QAM among which have positive value between
DLResidualBlerRetrans0_256 QAM and
DLResidualBlerRetrans6_256 QAM. HARQ
transmission number denotes 'X' in that 'Xth HARQ
retransmission' for 256 QAM supported UEs.
DLResidualBlerRetransAv The average failure rate of PDSCH HARQ
g_256 QAM retransmissions. The value is calculated in terms of
percentage, where the denominator is set to be the
counts of all retransmissions adding the counts of
initial HARQ transmissions, and the numerator is set
to be the counts of all retransmissions adding the
counts of transmission failures after the maximal
HARQ retransmissions for 256 QAM supported UEs.
DLResidualBlerRetransN The failure rate of PDSCH initial HARQ
ak_256 QAM transmissions after the maximal HARQ
retransmission occurs. It is the ratio of the counts of
transmission failures after the maximal HARQ
retransmissions to the counts of initial transmissions
for 256 QAM supported UEs.
DLTransmissionRetrans0 The cumulated number of initial PDSCH HARQ
_256 QAM transmissions for 256 QAM supported UEs.
DLTransmissionRetrans1 The cumulated number of the first PDSCH HARQ
_256 QAM retransmissions for 256 QAM supported UEs.
DLTransmissionRetrans2 The cumulated number of the second PDSCH
_256 QAM HARQ retransmissions for 256 QAM supported UEs.
DLTransmissionRetrans3 The cumulated number of the third PDSCH HARQ
DLTransmissionRetrans4 The cumulated number of the fourth PDSCH HARQ
DLTransmissionRetrans5 The cumulated number of the fifth PDSCH HARQ
DLTransmissionRetrans6 The cumulated number of the sixth PDSCH HARQ
DLTransmissionNackedR The cumulated number of PDSCH HARQ
etrans_256 QAM retransmission failures after the maximal HARQ
retransmission occurs for 256 QAM supported UEs.
DL MCS in 256 QAM DLTransmittedMcs0_256 The cumulated number of times that MCS 0 to MCS
QAM~DLTransmittedMcs 31 PDSCH is transmitted per Layer/Codeword for
31_256 QAM 256 QAM supported UEs.
DL Wideband CQI in 256 DLReceivedCQI0_256 The cumulated number that CQI0 to CQI15 is
QAM QAM~DLReceivedCQI15 received per Layer/Codeword for 256 QAM
_256 QAM supported UEs.
DLReceivedCQIMin_256 The minimum value of DLReceivedCQI0_256 QAM
QAM to DLReceivedCQI15_256 QAM.
DLReceivedCQIMax_256 The maximum value of DLReceivedCQI0_256 QAM
QAM to DLReceivedCQI15_256 QAM.

Confidential

DLReceivedCQIAvg_256 The average value of DLReceivedCQI0_256 QAM to
QAM DLReceivedCQI15_256 QAM
CQIErase_256 QAM The number of times that CQI erase is received per
layer/codeword for 256 QAM supported UEs.
REFERENCE
[1] 3GPP TS 36.306: Evolved Universal Terrestrial Radio Access (E-UTRA) User
[2] 3GPP TS 36.331: Evolved Universal Terrestrial Radio Access (E-UTRA)
Radio Resource Control (RRC) Protocol specification (Release 12)
[3] 3GPP TS 36.213: Evolved Universal Terrestrial Radio Access (E-UTRA)
Physical layer procedures (Release 12)

Confidential
LTE-ME3010, Timing Advance Control

INTRODUCTION
In wireless system, when multiple UEs transmit signal simultaneously, the arrival
time of the signal received by an eNB is different due to various propagation delay
between UEs and the eNB. To make the transmission time aligned from different
UEs within the receiver window of the eNB, the eNB uses Timing Advance
Command (TAC). This command indicates how much time the UE should
advance or delay the timing of its transmission.
The eNB estimates the UE transmission time when it receives the Random Access
Channel (RACH) preambles from the UE during the random access procedure. It
sends the Random Access Response to the UE to adjust its transmission timing. In
addition, after finishing RACH procedures, the eNB keeps adjusting UE timing
with periodic TAC operation.
BENEFIT
This feature enables UL synchronization.
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The uplink time alignment is maintained by continuous interaction between the
eNB and UE through TAC (Timing Advance Command). If the UE does not
receive TAC within timeAlignmentTimer, it releases the HARQ buffer and
PUCCH/SRS while clearing downlink assignments and uplink grants. In this case,
the only possible UL transmission for the UE is to send Random Access Preamble.
The TimeAlignmentTimer is always restarted whenever the TAC is received.
Each UE presumes that the starting point of the uplink radio frame is (NTA + NTA,
offset)
xTs ahead of the starting point of the downlink radio frame, where:
• NTA is the timing advance value for the corresponding UE ranging from 0 to
20512.
• NTA, offset is predefined in TS36.211 as 0 for FDD LTE and 624 for TD-LTE,

Confidential
respectively.
• Ts is equal to 1/(15000x2048) seconds.
The TAC can control NTA for each UE with a granularity of 16Ts.
Configuration of timeAlignmentTimer
The TimeAlignmentTimer informed by the eNB can be configured by
TIME_ALIGNMENT_TIMER_COMMON (CHG-TIME-ALIGN) to have one of the
following values:
ENUMERATED {sf500, sf750, sf1280, sf1920, sf2560, sf5120, sf10240, infinity}
Where, sf represents sub-frame. It can be indicated through either of the following:
• SIB2 (timeAlignmentTimerCommon): Common to whole UEs in the cell.
• MAC-MainConfig (timeAlignmentTimerDedicated): The UE-specific value
included in the RRC Reconfiguration message.
Types of TAC
The TAC can have two different sizes as follows:
• MAC RAR (Random Access Response): 11 bits
• TAC MAC CE (Control Element): 6 bits
When UL CA is used, the TAC should operate with PCell and SCell, respectively,
that is, multiple timing advance groups should be maintained. For more
information, see LTE-SW5503, UL CA Call Control.
MAC RAR
Initial timing advance is achieved during RACH procedure. Upon receiving
RACH preamble, eNB estimates timing offset and then calculates the absolute
TAC ranging from 0 to 1282 to compensate the timing offset. The eNB sends it to
UE using RAR.
The size of the TAC field is 11 bits, as depicted in figure below:
The TAC field can indicate the value with the range from 0 to 1282, and the UE

Confidential
adjust its NTA with 16x{the value of TAC field}.
TAC MAC CE
After RACH procedure completion, eNB provides relative TAC (the timing
adjustment compared to UE’s current transmission time) based on received
PUSCH signal. TA MAC CE can be triggered if the relative TA value is not equal
to 31, which corresponds to no TA adjustment. To reduce steady-state jitter of
timing advance control, the range of TAC is limited as {30 (1TA delay), 31
(Hold), 32 (1TA advance)} in Samsung eNB.
Since TAC is calculated based on PUSCH signal, there may be no TA adjustment
if there is no received PUSCH. Samsung eNB trigger UL dummy grant if the time
since last received PUSCH exceeds 1 second so that UL timing offset for a UE can
be checked and compensated once in a second at least.
The MAC PDU sub-header identifies the TAC MAC control element with the
LCID value = 11101.
TAC MAC CE has a fixed size and consists of a single octet, as depicted in figure
below.
Where:
• TAG Id (Timing Advance Group Identity): If UL CA is not used, this field is
set to '00' by default.
• Timing Advance Command: This field indicates the value with the range from
0 to 63, and the UE updates its NTA as follows: NTA, new = NTA, old + 16x ({the
value of TAC field}-31).
PDCCH Order after Out-of-Sync Detection

After out-of-sync detection, the eNB is checking in-sync of the UE until the call is
released. During in-sync checking, PDCCH order is periodically transmitted to the
UE so that RACH procedure is triggered by the UE using dedicated preamble.
SYSTEM OPERATION
How to Activate

Confidential
Key Parameters
parameter.
Parameter Description of CHG-TIME-ALIGN/RTRV-TIME-ALIGN
TIME_ALIGNMENT_T This parameter is used to control how long the UE is considered uplink time aligned.
IMER_COMMON Value in number of sub-frames.
Counters and KPIs

Timing Alignment TimeAdvanceSecti This counter is collected when the timing offset estimated using
on0 an RRC ConnectionRequest message is within 0-2 TA.
TimeAdvanceSecti This counter is collected when the timing offset estimated using

Confidential

on30 an RRC ConnectionRequest message is within 768- TA.
RRC Reestablishment RRE_TimeAdvanc This counter is collected when the timing offset estimated using
TA Statistics eSection0 an RRC ConnectionReestablishmentRequest message is within
0-2 TA.
RRE_TimeAdvanc This counter is collected when the timing offset estimated using
eSection1 an RRC ConnectionReestablishmentRequest message is within
3-5 TA.
6-7 TA.
8-10 TA.
11-12 TA.
13-15 TA.
16-17 TA.

Confidential

18-20 TA.
21-22 TA.
23-25 TA.
26-31 TA.
32-38 TA.
39-44 TA.
45-50 TA.
51-63 TA.
64-76 TA.
77-88 TA.
89-101 TA.
102-114 TA.
115-127 TA.
128-152 TA.
153-178 TA.
179-203 TA.
204-229 TA.

Confidential

230-255 TA.
256-319 TA.
320-383 TA.
383-447 TA.
448-511 TA.
512-767 TA.
768- TA.
RRC Connection NormalRelease_Ti This counter is collected when the timing offset estimated most
Normal Release TA meAdvanceSectio recently from Normal RRC ConnectionRelease is within 0-2 TA.
Statistics n0
NormalRelease_Ti This counter is collected when the timing offset estimated most
meAdvanceSectio recently from Normal RRC ConnectionRelease is within 3-5 TA.
n1
meAdvanceSectio recently from Normal RRC ConnectionRelease is within 6-7 TA.
n2
meAdvanceSectio recently from Normal RRC ConnectionRelease is within 8-10
n3 TA.
n4 TA.
n5 TA.
n6 TA.
n7 TA.
n8 TA.
n9 TA.

Confidential

n10 TA.
n11 TA.
n12 TA.
n13 TA.
n14 TA.
n15 TA.
n16 TA.
n17 TA.
meAdvanceSectio recently from Normal RRC ConnectionRelease is within 102-
n18 114 TA.
n19 127 TA.
n20 152 TA.
n21 178 TA.
n22 203 TA.
n23 229 TA.
n24 255 TA.
n25 319 TA.
n26 383 TA.
n27 447 TA.

Confidential

n28 511 TA.
n29 767 TA.
n30 TA.
RRC Connection AbnormalRelease_ This counter is collected when the timing offset estimated most
Abnormal Release TA TimeAdvanceSecti recently from AbnormalRRC ConnectionRelease is within 0-2
Statistics on0 TA.
AbnormalRelease_ This counter is collected when the timing offset estimated most
TimeAdvanceSecti recently from AbnormalRRC ConnectionRelease is within 3-5
on1 TA.
on2 TA.
on3 TA.
on4 TA.
on5 TA.
on6 TA.
on7 TA.
on8 TA.
on9 TA.
on10 TA.
on11 TA.
on12 TA.
on13 TA.

Confidential

on14 TA.
on15 TA.
on16 TA.
TimeAdvanceSecti recently from AbnormalRRC ConnectionRelease is within 89-
on17 101 TA.
on18 114 TA.
on19 127 TA.
on20 152 TA.
on21 178 TA.
on22 203 TA.
on23 229 TA.
on24 255 TA.
on25 319 TA.
on26 383 TA.
on27 447 TA.
on28 511 TA.
on29 767 TA.
on30 TA.
Timing Alignment of HOTimeAdvanceS This counter is collected when the timing offset estimated using
RACH success UE in ection0 the RRC ConnectionRequest for successful HO is within 0-2

Confidential

Handover TA.
HOTimeAdvanceS This counter is collected when the timing offset estimated using
ection1 the RRC ConnectionRequest for successful HO is within 3-5
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
TA.
ection17 the RRC ConnectionRequest for successful HO is within 89-
101 TA.

Confidential

114 TA.
127 TA.
152 TA.
178 TA.
203 TA.
229 TA.
255 TA.
319 TA.
383 TA.
447 TA.
511 TA.
767 TA.
TA.
REFERENCE

Confidential


Confidential
LTE-ME6301, NB-IoT L1/L2 Support

INTRODUCTION
Samsung eNB supports Narrow Band - IoT (NB-IoT) defined in 3GPP Rel13. This
feature supports basic L1/L2 operations and procedures, which include NB-IoT
physical channels (NPBCH, NPDCCH, NPDSCH, NPRACH, and NPUSCH),
MAC and RLC functions.
BENEFIT
An operator can launch an IoT service through NB-IoT technology providing
20dB coverage gain compared to GPRS, long UE battery life and massive UE
connections
DEPENDENCY
• HW dependency:
o Support Channel Cards: According to the DU, RU types, NB-IoT capacity
is different (Some old type DU, RU cannot support this function)
• Network Elements Dependency: MME C-SGN
• Others: NB-IoT UE (Cat.NB1) is required
LIMITATION
Single NB-IoT carrier is supported
SYSTEM IMPACT
capabilities.
None
According to the deployment area of NB-IoT cells and the NB-IoT PRB position,
NB-IoT UL signal can be potential interference sources to LTE within LTE
channel bandwidth.
Coverage
None
Interfaces
None

Confidential
FEATURE DESCRIPTION
Samsung eNB supports basic L1/L2 operations and procedures for NB-IoT defined
in 3GPP Rel13. The eNB supports functions, signals and physical channels
(NPBCH, NPDCCH, NPDSCH, NPRACH, and NPUSCH). Samsung eNB
supports logical channels and transport channels in MAC and RLC, support uplink
and downlink resource scheduling, NPRACH configuration, uplink power control,
and RLC functions. Besides, QCI based scheduling and 20dBm functions are also
supported in eNB.
Physical Layer
This feature supports following physical channels and signals in NB-IoT
downlink:
• Narrowband Physical Broadcast Channel (NPBCH):
o QPSK modulation
o Transmission time interval: 640 ms
o size of the BCH transport block size: 34 bits
o 16 bits CRC
• Narrowband Physical Downlink Control Channel (NPDCCH):
o QPSK modulation
o NPDCCH format 0 and NPDCCH format 1
o Type-1 NPDCCH common search space and Type-2 NPDCCH common
search space
o NPDCCH UE-specific search space
o DCI format N0, DCI format N1, and DCI format N2
o 16 bits CRC
• Narrowband Physical Downlink Shared Channel (NPDSCH)
o QPSK modulation
o 24 bits CRC
• Narrowband Reference Signal (NRS)
o Antenna port 0 and Antenna port 1
• Synchronization signals
o Narrowband primary synchronization signal (NPSS) and Narrowband
secondary synchronization signal (NSSS)
The physical layer supports following physical channels and signals in NB-IoT
uplink:
• Narrowband Physical Random Access Channel (NPRACH)
o Preamble format 0 and Preamble format 1
o Support three NPRACH configurations

Confidential
• Narrowband Physical Uplink Shared Channel (NPUSCH)

o NPUSCH format 1
♦ 3.75 kHz and 15 kHz subcarrier spacing
♦ BPSK and QPSK modulation
♦ single-tone and multi-tone transmission
o NPUSCH format 2
♦ 3.75 kHz and 15 kHz subcarrier spacing
• Demodulation Reference Signal
The physical layer offers data transport services to higher layer via the MAC sub-
layer. This feature supports the following functions to provide the data transport
service in NB-IoT:
• Error detection on the transport channel and indication to higher layers
• FEC encoding/decoding of the transport channel
• Hybrid ARQ soft-combining
• Rate matching of the coded transport channel to physical channels
• Mapping of the coded transport channel onto physical channels
• Power weighting of physical channels
• Modulation and demodulation of physical channels
• Frequency and time synchronization
• Radio characteristics measurements and indication to higher layers
Functions and Logical Channels in MAC Sub-layer

The eNB supports NPRACH configuration to satisfy all UEs’ requirements of
random access in the system and avoid the resources overlapping between
neighbor cells. The eNB supports NPRACH configuration for three coverage
classes, and the MSG2, MSG3, and MSG4 scheduling for contention-based
random access.
The eNB supports single-tone and multi-tone NPUSCH transmission. For single-
tone transmission, there are two numerologies are configurable, i.e.3.75 kHz and
15 kHz. For multi-tone transmission, only 15 kHz numerology is configurable.
The eNB supports NPUSCH format 1(for uplink data) and NPUSCH format 2(for
ACK/NACK). The eNB supports NPDSCH transmission, and format 0 and format
1 NPDCCH transmission. It supports the uplink and downlink scheduling and time
and frequency domain resource allocation. The eNB supports gap configuration.
Functions of RLC Sub-layer

NB-IoT supports data transfer in RLC AM and TM modes, supports ARQ
retransmission, polling and status report procedures for AM RLC entity.

Confidential
Multiple QCI for NB-IoT Bearer

Multiple QCI for NB-IoT bearer is supported in UP optimization. As resources are
shared between radio bearers, the support of multiple QCI can standardize a QCI
with corresponding characteristics for NB-IoT bearer. It can ensure that
applications/services mapped to that QCI receive the same minimum level of QoS
in multi-vendor network deployments. The eNB acquires the QCI from QoS
indicator during E-RAB Setup procedure.
QCI-based Scheduling
QCI based scheduling is supported to provide more flexible scheduling for
different requirements on traffic types (CHG-NBMULTIQCI-CONF). For each
scheduling operation, one or more radio bearers are collected and time and
frequency resource are allocated to the selected radio resources. QCI based
scheduling can take the QCI of the data radio bearer into account the scheduling
priority. QCI based scheduling is supported in DL. The logical channel with higher
QCI priority is scheduled prior to that with lower QCI priority. For the logical
channels with the same QCI priority, round robin scheduling is used among them.
powerClassNB-20dBm Support
In NB-IoT, the maximum transmission power of UE can use 20dBm when UE
report 20dBm capability support by powerClassNB-20dBm in UE capability
transfer procedure. Parameter, defaultUePowerClass (CHG-NBPWR-CTRL), is
used to configure the default of power class of UE. Before the scheduler acquires
UE radio access capability information for the first time, the scheduler uses
defaultUePowerClass as the default power class of the UE. After the UE capability
transfer procedure, the scheduler can acquire the power class of UE through the
value of powerClassNB-20dBm, and then uses this UE power class of the UE.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-NBCELL-CONF and set ADMINISTRATIVE_STATE to
unlocked.

Confidential
• Run CHG-NBCELL-CONF and set ADMINISTRATIVE_STATE to locked.
Key Parameters
parameters.
Parameter Descriptions of CHG-NBCELL-CONF
CELL_NUM Specifies the number of NBIOT cells that are activated/deactivated. In this
release, value range is [-1, 35].
ADMINISTRATIVE_STATE Indicates the state of the NBIOT cell.
• Unlocked: To activate the NBIOT cell.
• Locked: To deactivate the NBIOT cell.
Counters and KPIs

Packet Statistics NB-IoT NB-IOT Air Mac UL/DL bytes statistics for
AIR_MAC_BYTES_CLASS each coverage class
NB-IoT AIR_RLC_BYTES NB-IOT Air RLC UL/DL bytes statistics
RRU NB-IoT_Resource_Usage Statistics on NB-IoT downlink resource usage
(DL) of NPDSCH/NPDCCH.
NB-IoT_Resource_Usage Statistics on NB-IoT uplink resource usage of
(UL) NPUSCH.
Power NB-IoT Power Statistics on average thermal noise.
NB-IoT Path_Power Statistics on average RSSI per antenna.
RA NB-IoT RA_CLASS Statistics on average number of detected
NPRACH preambles per second for each
coverage class.
HARQ NB-IoT Statistics on the number of NPDSCH
DL_HARQ_TRANSMISSIO transmissions.
N_CLASS
NB-IoT Statistics on the number of NPUSCH
UL_HARQ_TRANSMISSIO transmissions.
N_CLASS
AMC NB-IoT_MCS_CLASS Statistics on the number of transmissions of
NPDSCH and NPUSCH per MCS.
NB-IoT Repetition Statistics on the number of transmissions of
PHY channels per repetition.
Paging NB-IoT PAGING Statistics on the number of transmissions of
PHY channels per repetition.

Confidential
REFERENCE

Confidential
LTE-ME6302, NB-IoT Enhanced Link Adaptation

INTRODUCTION
Samsung eNB supports Narrow Band-IoT (NB-IoT) defined in 3GPP Rel13.
According to the 3GPP standard operation, the default MCS for a new traffic is
decided per Coverage Enhancement (CE) level. This feature supports an efficient
MCS assignment per NB-IoT device using the previous traffic transmission
information and a channel status of new traffic.
BENEFIT
The NB-IoT radio resource utilization is enhanced by the reduction of NB-IoT
device communication time, which also results in saving battery life of the NB-IoT
device.
DEPENDENCY
• HW dependency: According to the DU and RU types, NB-IoT capacity is
different (some old type DU and RU cannot support NB-IoT)
• Required Network Elements: MME C-SGN
• Others: NB-IoT UE (Cat.NB1) is required
LIMITATION
Previous traffic transmission information of up to 10,000 NB-IoT devices can be
managed in eNB.
SYSTEM IMPACT
FEATURE DESCRIPTION
According to the 3GPP standard link adaptation, an eNB assigns the default MCS
per CE level in new traffic. If there are many data transmissions during RRC
connection, legacy link adaptation works fine, however, the NB-IoT data is
smaller in sizes and a few numbers of transmissions during the RRC connection.
For NB-IoT device, one DL data reception (for example, application server
operation request) and one UL data transmission (for example, sensing data
transmission) are required.

Confidential
RRC connected period

Real link status
Adapted link status cannot
Idle reach to real link status
period
Default MCS
Adapted link status during RRC connected Time
With this feature, the eNB saves the DL/UL link status of previous traffic
transmission per NB-IoT device and uses it in the next RRC connection.
If the eNB detects the NB-IoT device mobility using the difference between the
saved DL/UL link status and the new link status estimated from RRC connection
request message, then the new link status is used for deciding the new MCS.
Using this feature, the adapted link status can reach to real link status through the
RRC connections and the NB-IoT device battery can be saved.
RRC connected period Adapted link status can

reach to real link status
Real link status
Default MCS
Saved adapted link status is used on the next RRC connection Time
SYSTEM OPERATION
How to Activate
This section provides the information that you need to configure the feature
Preconditions
• Run CHG-NBELA-CONF and set enhancedLinkAdaptationConfig to
ci_NbIot_Config_Setup.
• Run CHG-NBELA-CONF and set enhancedLinkAdaptationConfig to
ci_NbIot_Config_Release.
Key Parameters
feature.
Confidential
parameters.
Parameter Descriptions of CHG-NBELA-CONF/RTRV-NBELA-CONF
enhancedLinkAdaptationConfig This parameter configures whether to setup or release Enhanced Link
Adaptation (ELA).
• Release: The ELA function is not used.
• Setup: The ELA function is used.
Counters and KPIs

with this feature.
REFERENCE

Confidential
Chapter 9 SON
LTE-SO0101, Self-establishment
INTRODUCTION
Self-establishment is to automate eNB commissioning procedure and minimize the
on-site manual operation.
To implement Self-Establishment, the following procedures need to be
implemented.
1 Automatic H/W test
2 Automatic Transport Configuration through DHCP server
3 Certificate Enrolment through CMPv2
4 IPsec tunnel establishment with Security Gateway
5 Planned Transport Configuration download from EMS
BENEFIT
• Self-establishment of eNBs reduces the amount of manual processes involved
in the initial radio parameter auto-configuration such as PCI/RSI/NR,
integration and configuration of new eNBs.
• Self-establishment offers a faster network deployment, reduced costs for the
operator in addition to an integral inventory management system and less
human error.
DEPENDENCY
• Required Network Elements:
DHCP server, DNS Server, SeGW, and PKI (CA/RA) server
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
When installing eNB system, the Self-Establishment function allows eNB to

Confidential
Chapter 9 SON
perform initialization automatically.
Self-Establishment with IPsec

Before eNB installation, information for Self-Establishment with IPsec should be
pre-provisioned to the EMS/DHCP server/DNS server/SeGW/CA/RA server.
Table below outlines Information to be pre-provisioned.
Pre-Provisioned information Target Entity
PSK Each eNB
Different per eNB
SeGW/EMS FQDNs or IPs DHCP server
LSM FQDN to IP address mapping if FQDN is used to get LSM IP address Public DNS server
SeGW FQDN to IP address mapping if FQDN is used to get SeGW IP address Public DNS server
PSK authentication is used. SeGW
: eNB serial number to fixed inner IP address to PSK mapping
Certificate authentication is used.
: Vendor root certificate, Operator root certificate
eNB whitelist to check whether eNB is allowed or not CA/RA
Vendor root certificate
1 Normal Configuration for each eNB EMS
2 IPsec tunnels configuration if required
o SeGW IP address, Encryption algorithm, key length
o Integrity Protection algorithm, key length
Authentication credential (PSK, Samsung certificate) is pre-installed in the eNB at

the factory.
Figure below depicts Self-Establishment (Plug and Play) Procedure with IPsec.

Confidential
Chapter 9 SON
1 The eNB hardware installation is performed.

2 After power on, the eNB hardware test (Power On Self-Test) is performed.
3 If required, eNB acquires the VLAN information to be used by the eNB
through VLAN scanning. (If VLAN is configured at factory or at site
manually, this step can be skipped)
To perform VLAN scanning, environment variable "DEFAULT_VLAN"
should be configured to "SCANNING".
If fixed VLAN values for all eNBs are required for Self-Establishment without
VLAN scanning, environment variable "DEFAULT_VLAN" should be

Confidential
Chapter 9 SON
configured to a specific value at the factory.

4 The eNB obtains eNB IP address and EMS/Security Gateway and PKI
(CA/RA) information from DHCP server.
To get transport related information from DHCP server, environment variable
"BOOTMODE" should be configured to "DHCP".
The IP address/netmask/GW IP of the eNB is given as a response to the DHCP
request.
Other information addresses are given by the option field (Option 43) of the
DHCP response message.
If EMS/SeGW/PKI information is given as FQDN, eNB will query to DNS
server to get each IP address.
The VLAN scanning and IP acquisition processes are as follows.
Figure below depicts VLAN scanning.
Table below outlines DHCP options.

Option Code Description
Option 26 (IPv4 only) N/A MTU size
Option 42 (IPv4) N/A NTP server IP
Option 43 (IPv4) Code 10/11 EMS IP/FQDN
Option 17 (IPv6) Code 20/21 SeGW IP/FQDN
Code 30/31 PKI IP/FQDN
Code 32/33/34/35 PKI Port/Service Protocol/Service
Path/Distinguished Name

Confidential
Chapter 9 SON
Option Code Description

Code 40 Subnet Mask for IPv6
Code 41 Gateway address for IPv6
Code 42 MTU size for IPv6
Code 50 Initial EMS Enable
Option 56 (IPv6) N/A NTP server IP/FQDN
Option 132 N/A VLAN value
1 The eNB requests an issuance of the operator signed certificate via CMPv2 if
IPsec is enabled (IPSECBOOT variable is set to 1) and certificate is used for
authentication method (AUTH METHOD as Certificate).
The eNB has the vendor signed certificate when coming out of the factory, and
uses it to request an issuance of the operator signed certificate.
For details concerning CMPv2, refer to COM-SE0602.
2 The eNB establishes IPsec tunnel to the Security Gateway with the following
IPsec specification.
Table below outlines IPsec specification.
Feature Implementation
IKE version IKEv2
IKE Authentication Operator signed Certificate
Mode Tunneling
NE connection Endpoint to Gateway mode
• Inner IP: Received from Security Gateway
Outer (Transport) IP Received from DHCP server
Security Gateway IP Received from DHCP server
Acquisition
EMS IP Acquisition Received from DHCP server
Number of tunnels 1
1 The eNB sends the registration request message to the LSM.

2 The EMS sends the registration response message to the eNB.
3 The eNB downloads and installs the S/W image and configuration data file
from the LSM.
4 If required, eNB establishes additional IPsec tunnels to Security Gateway by
using downloaded configuration.
5 The eNB performs the S1 setup with the MME.
6 The eNB performs the X2 setup with neighbor eNBs.
7 The eNB reports the Self-Test result to the LSM.
o POST Result
o Inventory Information report

Confidential
Chapter 9 SON
o eNB status (Cell Operation State) report

8 The eNB is ready for service. LSM allows the operator to manage the eNB.
Self-Establishment without IPsec

Before eNB installation, information for Self-Establishment without IPsec should
be pre-provisioned to the EMS/DHCP server/DNS server.
Table below outlines Information to be pre-provisioned.
Pre-Provisioned information Target entity
EMS FQDNs or IPs DHCP server
LSM FQDN to IP address mapping if FQDN is used to get LSM IP address Public DNS server
Normal Configuration for each eNB EMS
Figure below depicts Self-Establishment (Plug and Play) Procedure without IPsec.
1 The eNB hardware installation is performed.

Confidential
Chapter 9 SON
2 After power on, the eNB hardware test (Power On Self-Test) is performed.
3 If required, eNB acquires the VLAN information to be used by the eNB
through VLAN scanning.
(If VLAN is configured at factory or at site manually, this step can be
skipped.)
4 The eNB obtains eNB IP address/LSM IP information from DHCP server.
The IP address/netmask/GW IP of the eNB is given as a response to the DHCP
request.
The LSM IP information is given by the option field (Option 43) of the DHCP
response message.
If EMS information is given as FQDN, eNB will query to DNS server to get
EMS IP address.
5 The eNB sends the registration request to the EMS.
6 The EMS sends the registration response to the eNB.
7 The eNB downloads and installs the S/W image and configuration data file
from the EMS.
8 The eNB performs the S1 setup with the MME.
9 The eNB performs the X2 setup with neighbor eNBs.
10 The eNB reports the Self-Test result to the EMS.
o POST Result
o Inventory Information report
o eNB status (Cell Operation State) report
11 The eNB is ready for service. EMS allows the operator to manage the eNB.
SYSTEM OPERATION
How to Activate
Preconditions
Plug and Play is supported only when DHCP servers support vendor-specific
options.
• Change the environmental variable of BOOTMODE to DHCP.

Confidential
Chapter 9 SON
• Change the environmental variable of BOOTMODE to STATIC.
Key Parameters
Plug and Play feature is operated based on the environment variables as below.
1 PORT CONFIGURATION: port number configuration which is used for
Plug and Play including additional configuration like LAG, MTU.
2 DEFAULT_VLANID (Optional): If not configured, eNB is operated without
VLAN configuration.
Environment Variable Name Range Descriptions
DEFAULT_VLANID SCANNING, • SCANNING: eNB performs VLAN scanning
VLAN_VALUE: 1~4094 • VLAN_VALUE: eNB uses configured VLAN
value.
*) VLAN scanning on IPv6: TBD
3 DEFAULT_IPVER (Optional): If not configured, IPv4 is used.

DEFAULT_IPVER 4 eNB tries IPv4 only.
6 eNB tries IPv6 only.
64 eNB tries IPv6 first and if IPv6 is not working, eNB
tries IPv4.
46 eNB tries IPv4 first and if IPv4 is not working, eNB
tries IPv6.
4 BOOTMODE (Mandatory): Should be configured.

BOOTMODE DHCP eNB receives transport configuration from DHCP.
STATIC eNB uses transport configuration which are
configured in environment variables.
5 IPSEC CONFIG
a IPSECBOOT (Optional): If not configured, IPsec on/off is determined
according to the code 20/21 of DHCP option43 (IPv4)/option17 (IPv6).
IPSECBOOT 1 If code 20/21 of DHCP option43 (IPv4)/option17
(IPv6) is received from DHCP server, eNB will use
received value as Security Gateway information.
If not received from DHCP server, eNB will use
configured value in environment variable as
Security Gateway information.
If no information from DHCP server or
environment variable exists, Plug and Play is
halted.

Confidential
Chapter 9 SON

0 IPsec is always off.
b IPSEC MODE (Optional): If not configured, IPsec is operated in

"CLIENT-SERVER MODE".
IPSECMODE CLIENT eNB will receive INNER IP address from Security
Gateway.
LAN-TO-LAN If INNER IP address is configured in environment
variable, eNB will use configured value.
If not configured, eNB will use OUTER IP address
as INNER IP address.
c SEGW (Optional): Can be configured as IP or FQDN.

If code 20/21 of DHCP option 43 (IPv4)/option 17 (IP6) is received, eNB
will use received value.
If not, eNB will use values configured in environment variable.
SEGW0_IP IPv4/IPv6 Address String SeGW IP Address
format
If IPsec mode is disabled, eNB will ignore this value.

d AUTH METHOD (Optional)
PSK eNB will use PSK authentication for IPsec.
EAP-AKA eNB will use EAP-AKA authentication for IPsec.
Certificate eNB will use Certificate authentication for IPsec.
e PKI INFO 1_ADDRESS (Optional): If IPSEC is enabled & AUTH

METHOD is Certificate, this variable is used.
Can be configured as IP or FQDN
If code 30 or 31 of DHCP option 43 (IPv4)/option 17 (IPv6) is received,
eNB will use that value.
If not received, eNB will use PKI info 1.
f PKI INFO 2 (Optional): If IPSEC is enabled & AUTH METHOD is
Certificate, these variables are used.
PORT If code 32~35 of DHCP option 43 (IPv4)/option 17 (IPv6) are received, eNB
will use those values.
SERVICE PROTOCOL
If not received, eNB will use PKI info 2.
SERVICE PATH
DISTINGUISHED NAME
g CMPv2_INSIDE_SEGW (Optional): If not configured, eNB will operate

Confidential
Chapter 9 SON
as "NO".
CMPv2_INSIDE_SEGW 1 eNB will establish IPsec tunnel before CMPv2.
CMPv2 traffic will go inside IPsec tunnel.
0 eNB will establish IPsec tunnel after CMPv2.
CMPv2 traffic will go outside IPsec tunnel.
6 CLOCK MODE: GPS (Default), GLONASS, Others

7 OTHERS (Optional)
eNB ID VALUE If configured, eNB will use this value as eNB ID.
If not configured, eNB will get eNB ID from EMS.
(eNB ID should be pre-provisioned in EMS in this
case.)
Counters and KPIs

There are no related counters and KPIs.
REFERENCE

Confidential
Chapter 9 SON
LTE-SO0201, Intra-LTE ANR

INTRODUCTION
The Samsung automatic neighbor relation (ANR) automatically configures and
manages the intra-LTE neighbor relation table (NRT), and it aims to maintain the
optimal NRT reflecting changes in the communication environment during the
system operation. Stable UE mobility of Samsung LTE cells can be guaranteed by
optimizing NRT.
The Samsung ANR provides the following functions depending on the SON phase:
• Self-configuration phase
o Initial NRT auto-configuration through O&M: Create an initial NRT by
using the location information of active cells during the eNB or cell
addition procedure.
• Self-optimization phase
o Finds and adds new neighbor cells during HO execution due to UE
mobility.
i Adds new neighbor cells to the NRT based on the UE.
ii Establishes bi-directional NR relations by adding the serving cell to the
NRT of a new neighbor cell with the help of the EMS.
iii Sets the automatic X2 interface between the serving cell and the new
neighbor cell.
o Finds and adds neighbor cells based on ANR specific event (Scheduled
ANR)
i Performs ANR measurement by configuring ANR specific event with
the UE selected among the ones which initially attach or perform
handover to this cell.
ii If the best neighbor cell included in the measurement report (MR)
message triggered by ANR specific event is unknown, adds this cell to
NRT based on the UE.
iii Establishes bi-directional NR relations by adding the serving cell to the
NRT of a new neighbor cell with the help of the EMS.
iv Configures the X2 interface automatically between serving eNB and
new neighbor eNB.
o Adds neighbor cells based on RLF Indication message
♦ If the cell which sent RLF Indication message does not exist in NRT,
eNB adds the cell in NRT.
o ANR control function per carrier/operator
i Prevents adding a new neighbor cell of a specific carrier to NRT by
controlling the ANR measurement by carrier.
ii Prevents the X2 interface from being configured with the neighbor
eNB that belongs to a specific operator by controlling X2
Confidential
Chapter 9 SON
configuration by operator.
iii Prevents adding a new neighbor cell that belongs to a specific operator
by controlling neighbor cell addition function per operator.
o Automatic NRT management function
i NR ranking calculation: The NR ranking is calculated using the
number of MR messages received for HO.
ii NRT size management: The number of NRs in the NRT should be
managed so that it does not exceed the pre-defined maximum size.
◊ Guarantees the minimal number of effective neighbor cells per
carrier when attempting to add a new NR in case that the NRT is
full.
iii Unnecessary NR removal: When the number of MR messages received
for an NR is reduced due to UE not reporting them any longer, this
function removes the NR based on the specific threshold.
iv Management of NR causing HO performance degradation: If the HO
success rate for an NR is extremely low in spite of considerable
number of HO preparation successes, this function removes the NR or
manages it as HO blacklist.
v Invalid NR management: If the number of successive HO failures for
an NR is larger than a threshold, this function removes the NR or
manages it as HO blacklist.
vi HO blacklist management: This function manages the NRs causing HO
performance degradation or invalid NRs as HO blacklist.
o Automatic X2-NRT management function
i X2 NR ranking calculation: X2 NR ranking is calculated using the
number of HO attempts.
ii X2-NRT size management: The number of X2 NRs in X2-NRT should
be managed so that it does not exceed the pre-defined maximum size.
◊ eNB considers the number X2 NRs to be guaranteed per band
indicator
iii Unnecessary X2 NR blacklisting: If ratio of handover attempt to an X2
NR is lower than predefined threshold, this function disconnects X2
link with the unnecessary X2 NR.
iv X2 link restoring: If ratio of S1 handover attempt to an X2 NR is larger
than predefined threshold, this function restores the X2 link with the
X2 NR.
o Creation of the neighbor cell list used in measurement configurations
o The eNB creates the best neighbor cell list including a maximum of 32
cells for each carrier in the descending order of ranking, for the purpose of
joint optimization with the Samsung MRO function.

Confidential
Chapter 9 SON
BENEFIT
This feature can reduce CAPEX and OPEX costs for configuring and managing
the NRT of the LTE cells.
The system performance indicators such as HO success rate and call drop rate can
be improved by configuring NRT optimized for coverage and air status of each
LTE cell. This guarantees reliable mobility of the UEs in the RRC_CONNECTED
mode.
DEPENDENCY
• Related Radio Technology:
E-UTRAN (LTE)
• Prerequisite Features:
LTE-SW5012 (Operator Specific Feature Activation): To use the X2 setup
on/off per PLMN function, operator should purchase license key of this
feature.
• Others:
For UE-based NR addition, UE should support the E-UTRAN cell global
identifier (ECGI) acquiring function. To use Initial NRT auto-configuration
and NRT re-initialization, location information of the cell should be
configured. Location information can be set by operator or Auto GPS function
when adding a new cell.
LIMITATION
Bi-directional NR addition is possible only when the new neighbor cell belongs to
the same EMS as the serving cell. Bi-directional NR relations cannot be
established with the neighbor cells that are located in a different EMS or that
belong to a different vendor.
SYSTEM IMPACT
• X2 Interface Management: X2 Interface Management feature manages the
signaling associations between eNBs, surveying X2 interface and recovering
from errors.
• PCI Auto-configuration: PCI Auto-configuration feature automatically detects
PCI conflict between cells and reallocates a new PCI to the cell involved in
PCI conflict.
• RACH Optimization: RACH Optimization feature automatically detects RSI
collision between cells and reallocates a new RSI to the cell involved in RSI
collision.

Confidential
Chapter 9 SON

None
Coverage
Intra-LTE ANR automatically configures NRT optimized for coverage and air
status of LTE cell. This guarantees reliable mobility of the UEs in the
RRC_CONNECTED mode.
Interfaces
Intra-LTE ANR automatically sets up X2 interface with neighbor eNBs and
neighbor information added by Intra-LTE ANR is included in X2 Setup
Request/Response and eNB Configuration Update messages.
FEATURE DESCRIPTION
Architecture
The Samsung ANR function operates in the eNB and EMS. The overall
architecture is shown in the following figure.
Figure below depicts Samsung ANR Architecture.
As shown in figure above, the Samsung ANR function is executed at the eNB
SON Agent and at the EMS SON Manager. The operation of each entity in this
architecture is described below.
Confidential
Chapter 9 SON
As shown in figure above, the Samsung ANR function is executed at the SON
Agent in eNB and at the SON Manager in EMS. The operation of each entity in
this architecture is described below.
• EMS
o SON Manager: NRT Management Function
i Creates initial NRT when adding a new cell.
ii Establishes bi-directional NR relationship based on the EMS (Operator
can select whether to use bi-directional NR addition in SON Property
Window).
• eNB
o SON Agent: NR Detection Function
i Receives the measurement report message for HO from the call
processor.
ii Receives the measurement report message for Scheduled ANR from
the call processor.
iii Acquires the ECGI and the X2 TNL address from the Call Processor.
o SON Agent: NR Add Function
i Adds a neighbor cell by using the ECGI information
ii Adds a neighbor eNB by using the X2 TNL address information.
iii If the configuration of the X2 interface with a specific operator is not
allowed, configure as NO_X2 = True.
o SON Agent: NR Removal/Blacklisting Function
i Deletes the NR by receiving the information on the deletion of the NR
from the Call Processor (Served Cells to Delete IE in the X2 eNB
Configuration Update message).
ii Removes unnecessary NR.
iii Removes the NR that causes HO performance degradation or manages
the NR as HO blacklist.
iv Removes the invalid NR or manages it as HO blacklist.
o SON Agent: NR Ranking Function
i Calculates the ranking of NR by using the number of received MR
messages.
ii Sends the NR ranking information to the Call Processor to create the
neighbor cell list for measurement configuration
o SON Agent: NRT Management Function
i Decides whether to perform NR addition/retrieval/attribute value
update/deletion.
ii Synchronizes the NRT with SON Manager in EMS.
iii Manages the NRT size so that it does not exceed the specified
threshold.

Confidential
Chapter 9 SON
◊ Guarantees the minimal number of effective neighbor cells per

carrier when attempting to add a new NR in case that the NRT is
full.
Intra-LTE ANR Function

Self-Configuration Phase-Initial NRT Auto-configuration
The Samsung EMS provides the Cell Management Window with a SON option
box. If the "Initial NRT" option in the box is checked, an initial NRT is generated
using the cells' location information. This information is configured in the EMS
after the software download to the cell has completed. The SON Property Window
in EMS includes the following parameters, which are used to generate the initial
NRT.
1 NRT.type (NRT Type): Decides the initial NRT creation method
2 NRT.multiple (NRT multiplication Factor): A multiple for multiplying R
counts (used in initial NRT creation) and an average distance to the cells
3 NRT.limitDistance (NRT Distance Limit): The maximum distance to the
neighbor cell that can be included in the initial NRT
The Samsung EMS provides the following Initial NRT generation methods.
1 NRT.type = average
o Creation method: Includes neighbor cells in the NRT within the radius of
max{NRT Multiple × Ravg, NRT.limitDistance} up to NRT.size per
carrier registered in EUTRA-FA.
i Ravg: The average distance of R Count of cells within the
NRT.limitDistance.
◊ R Count: The number of cells to be used for the Ravg calculation
ii NRT.size (NRT Size): The number of the initial NRT configurations
2 NRT.type = distance
o Creation method: Includes neighbor cells in NRT within the radius of
NRT.limitDistance up to NRT.size per carrier registered in EUTRA-FA.
3 NRT Type = minimum
o Creation method: Creates an initial NRT in the same way as NRT.type =
average, but the distance to the closest cell among the cells within
NRT.limitDistance is used instead of Ravg.
Self-Optimization Phase-Automatic NRT Management
Finds and Adds New Neighbor Cells during HO Execution due to UE
Mobility
The Samsung NR addition function is triggered by an event where new neighbor
cells are found during the HO execution due to the UE mobility. To add the cell to
the NRT, if an ECGI can be acquired from UE, the UE-based NR addition is
executed. The ECGI can be acquired from the UE when the UE supports ECGI
acquiring function as a UE feature, and the serving cell uses discontinuous
reception (DRX).

Confidential
Chapter 9 SON
The Samsung UE-based NR addition function is triggered when a new neighbor

cell is detected during the HO execution due to the UE mobility. The ECGI of the
new neighbor cell can be acquired from the UE when the UE supports ECGI
acquiring function as a UE feature, and the serving cell uses discontinuous
reception (DRX).
The UE-based NR addition procedure is as follows:
1 The UE performs measurements according to the measurement configuration
transmitted by the serving cell.
2 The UE transmits the measurement report (MR) message to the serving cell.
3 In case that, the serving cell detects the PCI (Unknown PCI) of the new cell
that does not exist in its own NRT, the serving cell checks if condition 1 or
condition 2 is satisfied.
a Condition 1: the UE which sent the MR message does not use GBR
service.
b Condition 2: the UE which sent the MR message uses GBR service but the
value of GBR_REPORT_CGI_OPTION (CHG-SON-ANR) is set as
HoEventAnr or BothAnr.
4 If the condition in step 3 is satisfied, the serving cell transmits the reportCGI
configuration requesting the UE to acquire the ECGI.
a If the ANR measurement for the carrier of a new cell is not allowed, the
neighbor cell is not added (that is, the procedure is terminated).
♦ Setting parameter: ANR_ALLOW (CHG-EUTRA-FA)
◊ ANR_ALLOW: If the parameter is set to "no use", the ANR
measurement is not allowed.
b Command for measurement gap: CHG-MSGAP-INF
♦ GAP_RELEASE_FOR_REPORT_CGI:
◊ True: release previously configured measurement gap when
transmitting reportCGI configuration
◊ False: maintain previously configured measurement gap when
transmitting reportCGI configuration
c Commands for DRX operation setting: CHG-DRX-INF
i QCI: QCI index (1 to 9) used in UE-based NR adding function
ii DRX_CONFIG_SETUP: ci_Config_reportCGI
iii ON_DURATION_TIMER_REPORT_CGI:
ci_onDurationTimer_psf10
iv DRX_INACTIVITY_TIMER_ REPORT_CGI:
ci_drx_InactivityTimer_psf10
v DRX_RETRANSMISSION_TIMER_ REPORT_CGI:
ci_drx_RetransmissionTimer_sf16
vi LONG_DRXCYCLE_START_OFFSET_TYPE_REPORT_CGI:
ci_sf160_chosen
Confidential
Chapter 9 SON
d To handle the exception case of DRX operation, SON Agent runs the
EUTRA_REPORT_CGI_MR_TO_WAIT (CHG-TIMER-INF) timer. If
UE cannot acquire the ECGI/CGI within the time, SON Agent terminates
the DRX operation to return the normal state of service.
5 The UE reads the ECGI of the new cell corresponding to the Unknown PCI in
the DRX period.
6 The UE transmits the measurement report message including the acquired
ECGI to the serving cell.
7 The serving eNB checks whether PLMN ID in MR message is registered in
PLMNBLACK-LIST (Command: CHG-PLMNBLACK-LIST).
a In case that the PLMN ID is registered in PLMNBLACK-LIST and its
USED_FLAG = use,
i If EUTRA_BLOCK_FLAG = True, serving eNB terminates ANR
operation.
ii If EUTRA_BLOCK_FLAG = False, serving eNB performs step 8.
b In case that the PLMN ID is not registered in PLMNBLACK-LIST or the
PLMN ID is registered and its USED_FLAG = no_use,
♦ Serving eNB performs step 8.
8 The serving eNB acquires the IP address (X2 TNL address) of the new eNB
from the MME.
9 The serving eNB adds the new cell to its NRT and records the new neighbor
cell is added by UE based ANR in OWNER_TYPE (RTRV-NBR-EUTRAN)
of neighbor list.
10 The serving eNB reports to the EMS that the new cell added to its NRT.
11 The EMS adds the serving cell to the new cell's NRT and records the new
neighbor cell is added by bi-directional NR addition function in
OWNER_TYPE (RTRV-NBR-EUTRAN) of neighbor list. (If bi-directional
NR addition function is enabled in SON Property Window).
12 The serving eNB and new eNB determine whether to establish X2 connection
as follows (This function can be used if operator purchases the license key of
LTE-SW5012).
a If the configuration of the X2 interface for the PLMN of the new eNB is
allowed, serving eNB sends X2 Setup Request to the new eNB.
b If the configuration of the X2 interface for the PLMN of the new eNB is
not allowed, set NO_X2 = True for the neighbor eNB
♦ X2 interface configuring command by PLMN: CHG-PLMNANR-ENB
◊ ANR_TARGET_MCC: MCC of Neighbor eNB
◊ ANR_TARGET_MNC: MNC of Neighbor eNB
◊ SE_NBR_NO_X2: In case of use, set NO_X2 = True for the
neighbor eNB with the PLMN.
Figure below depicts the UE-based NR addition procedure.

Confidential
Chapter 9 SON
Finds and Adds New Neighbor Cells Based on the ANR Specific-event and
Renewal of NR Info. (Scheduled ANR)
Samsung ANR supports the additional NR adding function, called Scheduled
ANR, which finds and adds new neighbor cells during the scheduled period. The
operator can control the schedule of Scheduled ANR by adjusting the
DAY/HOUR/MINUTE/DURATION for the Intra-LTE ANR operation.
(Command: CHG-ANR-SCHED)
The LTE cell decides which UEs will perform the function among the ones who
initially attach or enter the cell due to a handover according to the UE search rate
set by each cell (ANR_UE_SEARCH_RATE_TOTAL). Then, the LTE cell
decides which the selected UE measures among the LTE intra-frequency
(ANR_UE_SEARCH_RATE_INTRA_FREQ), the LTE inter-frequency
(ANR_UE_SEARCH_RATE_INTER_FREQ), and the Inter-RAT carriers. (These
Confidential
Chapter 9 SON
parameters can be configured by the command CHG-SONFN-CELL.) For

example, if the LTE network has two carriers and the UTRAN network has a few
carriers, assume that the UE search rates are configured as
ANR_UE_SEARCH_RATE_TOTAL = 5 %,
ANR_UE_SEARCH_RATE_INTRA_FREQ = 40 %,
ANR_UE_SEARCH_RATE_INTER_FREQ = 40 %, and
ANR_UE_SEARCH_RATE_UTRAN = 20 %. Then, 2 % of UEs for the LTE
intra-frequency, 2 % of UEs for the LTE inter-frequency, and 1 % of UEs for the
UTRAN carriers will perform measurement for this function.
The Samsung Scheduled ANR operation procedure is as follows:
1 When the time comes to start the function, the LTE cell selects the target UE
and the target carrier. The target UE is selected from the ones which initially
attach or enter the cell due to a handover. Then, the LTE cell sends the RRC
Connection Reconfiguration message to the target UE including the ANR
measurement configuration with target carrier to the target UE.
a The function checks whether the UE supports intra/inter-frequency ANR
operation based on the FeatureGroupIndicators IE included in the UE-
EUTRA-Capability IE
i Intra-frequency ANR support: 17th bit = 1
ii Inter-frequency ANR support: 18th bit = 1 & 25th bit = 1
b Target UE selection
i Generates three random number (N1, N2, N3) ranging from 0 to 1
ii If N1 < ANR_UE_SEARCH_RATE_TOTAL, the LTE cell selects the
UE
c Target carrier selection
i According to the UE Capability, the method to select the target carrier
for ANR is as follows:
◊ If the UE supports the LTE intra/inter-frequency ANR and the
UTRAN ANR operation, sets the intervals for the LTE intra-
frequency (ANR_UE_SEARCH_RATE_INTRA_FREQ: y1), the
LTE inter-frequency
(ANR_UE_SEARCH_RATE_INTER_FREQ: y2), and the
UTRAN carriers (ANR_UE_SEARCH_RATE_UTRAN: y3). In
this case, the intervals are separated into 3 parts:
.
◊ If the UE supports only the LTE intra/inter-frequency ANR
operation, sets the intervals for the LTE intra-frequency
(ANR_UE_SEARCH_RATE_INTRA_FREQ: y1), the LTE inter-
frequency (ANR_UE_SEARCH_RATE_INTER_FREQ: y2). In
this case, the intervals are separated into 2 parts:
.
◊ Selects one among intra-frequency ANR, inter-frequency ANR,
and UTRAN ANR according to the random value N2.
ii When the LTE intra-frequency ANR is selected, the UE performs
Confidential
Chapter 9 SON
ANR measurement for intra-frequency.

iii When the LTE inter-frequency ANR is selected and there are more
than 1 inter-carrier, eNB sets the interval for each UE-supportable
inter-carrier with the ANR_UE_SEARCH_RATE (CHG-EUTRA-FA)
in the ascending order of the carrier index
◊ x_{k}: ANR_UE_SEARCH_RATE set to k^{th} inter-carrier
index
◊ the interval for k^{th} carrier
a) Minimum value in the interval: (if k = 0, the value

is 0)
b) Maximum value in the interval:

◊ After selecting one among UE-supportable LTE inter-carriers
according to the random value N3, the UE performs periodical
measurement for the target inter-frequency.
d ANR measurement configuration setting
i If the selected carrier is intra-frequency
◊ ReportConfigEUTRA: configures ANR specific A3 event
ii If the selected carrier is inter-frequency
◊ If A2 event is used for inter-frequency ANR
a) ReportConfigEUTRA: configures ANR specific A2 event
◊ If A2 event is not used for inter-frequency ANR or the eNB
receives MR message corresponding to the ANR specific A2 event
a) MeasObjectEUTRA: Sets the target carrier
b) ReportConfigEUTRA: configures ANR specific A4 event
c) Configures measurementGap
2 The UE transmits the measurement report (MR) message corresponding to
the ANR measurement configuration to the serving cell.
3 If the serving cell perceives that the PCI of the best neighbor cell in the MR
message does not exist in its NRT, the serving cell checks if condition 1 or
condition 2 is satisfied.
a Condition 1: the UE that sent the MR message does not use GBR service.
b Condition 2: the UE which sent the MR message uses GBR service but the
value of GBR_REPORT_CGI_OPTION (Command: CHG-SON-ANR) is
set as ScheduledAnr or BothAnr.
4 If the condition in step 3 is satisfied, the serving cell performs the UE-based
NR addition.
a If the ANR measurement for the carrier of a new cell is not allowed, the
neighbor cell is not added.
b Please refer to the 4-12 of Section Finds and Adds New Neighbor cells

Confidential
Chapter 9 SON
during HO Execution due to UE Mobility for the detail operation of the

next procedure.
5 The serving cell runs NR information update procedure based on Validity
Check Flag, if PCI of best neighbor cell existed in NRT is reported.
a If the value of Validity Check Flag is True, nothing occurs.
b If the value of Validity Check Flag is False, serving cell sends
RRCConnectionReconfiguration message to UE for ECGI/PCI acquisition.
Then, the serving cell updates NRT, if it is necessary.
i If the ECGI acquired by the UE exists in the NRT:
◊ Maintains NR information if the PCI of the NR is same with the
PCI acquired by the UE.
◊ Changes the PCI of the NR as the PCI acquired by the UE if the
PCI of the NR is different from the PCI acquired by the UE.
ii If the ECGI acquired by the UE does not exist in the NRT: Adds the
new NR in the NRT by using the information acquired by the UE.
The Scheduled NR addition function is shown below.
Figure below depicts procedure of scheduled NR adding function based on UE.

Confidential
Chapter 9 SON
Adds New Neighbor Cells based on RLF Indication Message

In case that served cell (Cell A) of Samsung eNB (eNB 1) receives RRC
Connection Reestablishment Request message from a UE, eNB 1 checks if the
previous serving cell (Cell B) of the UE is its served cell.
1 If Cell B is not served cell of eNB 1, eNB 1 transmits RLF Indication
message to the all cells, which have the same PCI as the PCI in RRC
Connection Reestablishment Request message. eNB 2 which received RLF
Indication message from eNB 1 checks that Cell B satisfies all the following
conditions.
a ANR_ENABLE = Auto or Manual (Command: CHG-SONFN-CELL)
b "ANR_ALLOW = True" for the carrier in which Cell A is operating
(Command: CHG-EUTRA-FA)
c RLF_INDICATION_USAGE_FLAG = True (Command: ACHG-SON-
ANR)
eNB 2 checks that Re-establishment cell ECGI in RLF Indication message
(Cell A’s ECGI) exists in NRT of Cell B if Cell B satisfies the above
conditions. If Cell A does not exist in NRT of Cell B, eNB 2 adds Cell A in
Confidential
Chapter 9 SON
NRT of Cell B and records the new neighbor cell (Cell A) is added by RLF
Indication based ANR in OWNER_TYPE (RTRV-NBR-EUTRAN) of
neighbor list.
2 If previous serving cell (Cell B) of the UE is served cell of eNB 1 but the
previous serving cell is not Cell A, eNB 1 checks that Cell B satisfies all the
following conditions.
a ANR_ENABLE = Auto or Manual (Command: CHG-SONFN-CELL)
b "ANR_ALLOW = True" for the carrier in which Cell A is operating
c RLF_INDICATION_USAGE_FLAG = True (Command: CHG-SON-
ANR)
eNB 1 checks that Cell A exists in NRT of Cell B if Cell B satisfies the above
conditions. If Cell A does not exist in NRT of Cell B, eNB 1 adds Cell A in
NRT of Cell B and records the new neighbor cell (Cell A) is added by RLF
Indication based ANR in OWNER_TYPE (RTRV-NBR-EUTRAN) of
neighbor list.
Figure below depicts Procedure of NR addition based on RLF Indication message.
Automatic NRT Management Function

The Samsung periodic NRT management procedure uses the following steps:
1 The serving cell collects the statistics of the number of MR messages
received for the HO to neighbor cells included in the NRT.
2 When calculate the NR ranking arrives, the serving cell calculates the ranking
of the NRs included in the NRT based on the collected statistics.

Confidential
Chapter 9 SON
3 The serving cell considers the NR with a low number of MR messages for
HO as unnecessary and removes it from the NRT.
4 The serving cell considers the NR with an extremely low HO success rate as
a HO performance degradation causing NR and then, the serving cell
removes it from the NRT or manages it as HO blacklist.
In addition, if a NR satisfies the predefined condition by analyzing HO preparation
failure cause, Samsung ANR removes the invalid NR from the NRT or manages it
as HO blacklist.
Figure below depicts Periodical NRT management procedure.
1) NR Ranking Calculation
The NR ranking reflects the validity or importance of an NR included in the NRT.
The Samsung eNB defines the NR ranking attribute as having the higher ranking
when more MR messages are received as the HO for the NR is triggered.
The NR ranking is performed as follows:
1 The NR ranking calculation is performed at a specified interval.
o NR ranking interval: RANK_PERIOD (CHG-SON-ANR)
2 The NR related to ranking calculation should be included in the NRT at least
for more than the ranking calculation interval.
3 The ranking value calculated in the previous interval is used for calculating
current ranking of the NR.
Figure below depicts the NR ranking operation with an example.

Confidential
Chapter 9 SON
The NR ranking is calculated based on statistics. To compare the rankings of NRs,

the period for collecting the statistics should be the same among the NRs. In the
previous figure, New NR (NR j) is added at 16:00, the statistics for NR is collected
only for 11 hours. On the other hand, the statistics for the NR previously added
(NR i) is collected for 24 hours. Since the comparison of the ranking between NR i
and NR j is imbalanced, we distinguish the ranking calculation method for these
two NRs.
The NR Ranking is calculated as follows:
1 The currentRank value for the NR i which is in the NRT for more than one
NR ranking calculation period as follows:
o k: current ranking calculation time

o ω: IIR filter coefficient that gives some weights to the previous rank value
and the current statistics
o : The rank value calculated in the last period
o : The number of MR message received for the NR i, which is
collected from the previous ranking calculation point k-1 to point k
o : The number of TooLateHoRlfBeforeTriggering
statistics for NR i
o : The number of ECGI acquisitions for NR i
2 The currentRank value for the NR i which is in the NRT for less than a NR
ranking calculation period as follows:
o From the NR ranking calculation point k,
currentRank i (k) = −1
♦ Maintain the value at-1 until the NR Ranking calculation period.

o At the next ranking calculation point k + 1,

Confidential
Chapter 9 SON
♦ At k + 2 (next ranking calculation time after k + 1), the rank value of

NR i is calculated as the same way as NR i which had been in the NRT
for more than one NR ranking calculation period.
3 Calculation of "k" (Ranking calculation time)
Each eNB calculates the rank of NR in every ranking update period. The eNB
starts to calculate the rank at [rankStartHour (H): rankStartMinute (M)] +
rankOffsetTime.
o rankStartHour: exact hour when eNB starts NR ranking calculation
♦ System parameter: RANK_START_HOUR (CHG-SON-ANR)
o rankStartMinute: exact minute when eNB starts NR ranking calculation
♦ System parameter: RANK_START_MINUTE (CHG-SON-ANR)
o rankOffsetTime = [eNBID % rankDuration] (M): randSec (S)
♦ eNBID % rankDuration: reminder of value of eNBID divided by
rankDuration
♦ rankDuration: total number of spreading time of ranking calculation
duration belongs a certain EMS
♦ System parameter: RANK_DURATION (CHG-SON-ANR)
♦ randSec: randomly selected integer value from 0 to 59
o Ranking calculation time of each eNB may be scattered from
[rankStartHour (H): rankStartMinute (M)] to [rankStartHour (H):
rankStartMinute (M)] + rankDuration.
2) NRT Size Management
The MAX_NRT_SIZE presents maximum number of NRs that can be included in
the Intra-LTE NRT. NRT size management is performed as follows.
1 MAX_NRT_SIZE: Unless a service provider requests for a separate value,
default value is set as 256. (Command: CHG-SON-ANR)
2 Intra-LTE NRT is managed so that no more NRs than the MAX_NRT_SIZE
could be included.
When the attempt of adding a new NR occurs, in the situation where the existing
number of NRs is as many as MAX_NRT_SIZE in Intra-LTE NRT, the following
operations are performed depending on the ANR setting mode.
3 ANR_ENABLE = "Auto" or "Manual" (Command: CHG-SONFN-CELL)
o Reason for new NR addition attempt
i NR addition by UE-based ANR function
ii NR addition by EMS-based bi-directional addition function
iii Manual addition by the operator
o Operation procedure
i In case of carriers which NRs in NRT are larger than

Confidential
Chapter 9 SON
MIN_NRT_SIZE_CARRIER (i),
◊ Parameter for setting the minimal number of effective neighbors by
carrier: MIN_NRT_SIZE_CARRIER (Command: CHG-EUTRA-
FA)
If the MAX_NRT_SIZE change attempting value is larger than the
value adding the sum of MIN_NRT_SIZE_CARRIER (i) for all
carriers and the number of NR belonging to the HO blacklist, it
changes.
ii Among the NRs with CurrentRank ≠ -1,
◊ The NR whose CurrentRank = -1 is excluded from the list of
removal since it existed less than the NR ranking interval in NRT.
iii The lowest ranking NR with the remove attribute (T) is deleted and a
new NR is added.
iv In case of "Manual addition by the operator": the new NR is not added.
4 ANR_ENABLE = Off (Command: CHG-SONFN-CELL)
o Reason for new NR addition attempt
i NR addition by EMS-based bi-directional addition function
ii Manual addition by the operator
o Operation procedure
i In case of NR addition by EMS-based bi-directional addition function:
Same as the operating procedure 1.
ii In case of "Manual addition by the operator": the new NR is not added.
Figure below depicts the ranking based NR removal function used to manage the
NRT size.
3) Unnecessary NR Removal
When the network is stabilized through the network optimization, this function

Confidential
Chapter 9 SON
removes NRs, which cannot receive MR messages among the NRs included when
the network was initially created, so that only valid NRs could be included in the
NRT. The operator can control this function’s ON/OFF state, and at the NR
ranking calculation point k, the serving cell removes the NR i, which meets all the
following conditions.
1 ANR_ENABLE = Auto or Manual (Command: CHG-SONFN-CELL)
2 NR_DEL_FLAG = True (Command: CHG-SON-ANR)
o NR_DEL_FLAG: ON/OFF control flag that determines the operational
status.
3 "ANR_ALLOW = True" for the carrier in which NR i is operating
(command: CHG-EUTRA-FA)
4
o CumulatedMRi (k): The number of MR messages received for NR i during
TH_TIME_NR_DEL period at the NR ranking calculation point k
o : The number of
TooLateHoRlfBeforeTriggering statistics for NR i during
TH_TIME_NR_DEL (CHG-SON-ANR) period at the NR ranking
calculation point k
o : The number of ECGI acquisitions for NR i during
TH_TIME_NR_DEL period at the NR ranking calculation point k
o TH_NUM_MR_NR_DEL (CHG-SON-ANR): The threshold value to
decide unnecessary NR
5 "IS_REMOVE_ALLOWED = True" for NR i (command: CHG-NBR-
EUTRAN)
The serving cell reports the results to EMS if NR i is removed from NRT.
Figure below depicts the statistics based NR removal function used to delete
unnecessary NRs.
4) Management of NR Causing HO Performance Degradation

Confidential
Chapter 9 SON
If a new cell located nearby has the same PCI as the PCI of a distant NR, which is
included in the NRT at the initial network formation, the UE transmits a
measurement report message for HO while moving to the new cell, the serving cell
wrongly recognizes the PCI in the message as belonging to the distant NR.
Therefore, UE fails the HO execution.
Figure below depicts the management scenario of the NR causing HO performance
degradation.
In the previous figure, the UE moves toward the neighbor cell (ECGI = 1002) and
transmits the measurement report message including PCI = 20 by HO triggering to
the serving cell (ECGI = 1000). The serving cell completes HO preparation using
the NR (ECGI = 1001) included in the NRT, and then transmits the HO command
message received from the NR. However, UE is moved to the new cell (ECGI =
1002), thus HO execution fails. As shown in figure above, Samsung ANR removes
the HO performance degradation causing NR from the NRT or manages it as HO
blacklist.
The operator can control this function’s ON/OFF state, and at the NR ranking
calculation point k, the serving cell removes the NR i from the NRT or manages it
as HO blacklist which meets all the following conditions.
1 ANR_ENABLE = Auto or Manual (command: CHG-SONFN-CELL)
2 WRONG_NR_DEL_FLAG = True (command: CHG-SON-ANR)
o WRONG_NR_DEL_FLAG: ON/OFF control flag that determines the
operational status.
3 "ANR_ALLOW = True" for the carrier in which NR i is operating
4
o : The number of HO preparation successes
collected for NR i during TH_TIME_NR_DEL (CHG-SON-ANR) at the
NR ranking calculation point k
o TH_HO_PREP_SUCC_NR_DEL (CHG-SON-ANR): The threshold value

Confidential
Chapter 9 SON
of HO attempts to decide HO performance degradation causing NR
5 &
o : The number of HO success collected for NR i
during TH_TIME_NR_DEL period at the NR ranking calculation point k
o TH_HO_SUC_RATE_NR_DEL (CHG-SON-ANR): The threshold value
of the HO success rate to decide HO performance degradation causing NR
6 "IS_REMOVE_ALLOWED = True" for NR i (command: CHG-NBR-
EUTRAN)
The serving cell reports the results to EMS if NR i is removed from NRT or
managed as HO blacklist.
5) Management of Invalid NR
Based on the statistics on the HO preparation failure causes, this function removes
NRs, which have invalid neighbor information or manages the NRs as HO
blacklist. The operator can control this function's ON/OFF state. The eNB collects
statistics per HO preparation failure cause as follows.
1 If HO preparation to an NR fails, eNB checks whether the HO preparation
failure cause is registered in NBRDEL-CAUSE.
a If the HO preparation failure cause is registered in NBRDEL-CAUSE,
eNB increases internal counter by 1 for the HO preparation failure cause of
the NR.
b If the HO preparation failure cause is not registered in NBRDEL-CAUSE,
eNB maintains the internal counter of HO preparation failure cause of the
NR.
2 If HO to an NR succeeds, eNB resets internal counters of all HO preparation
failure causes for the NR to 0.
If the internal counter of the HO preparation failure cause for and NR exceeds
the predefined threshold for each HO preparation failure cause, eNB
immediately deletes the NR from the NRT or manages the NR as HO blacklist.
The threshold can be configured by operator for each HO preparation failure
cause. In case of deleting the NR or managing the NR as HO blacklist, the
eNB reports the results to EMS.
To use this function, following parameter configuration is required.
1 ANR_ENABLE = Auto or Manual (command: CHG-SONFN-CELL)
2 NBR_DEL_CAUSE_FLAG = True (command: CHG-NBRDEL-CAUSE)
3 Threshold > 0 per Cause
Table below outlines S1 HO preparation failure causes.
Causes Meaning
Handover Failure In Target The handover failed due to a failure in target EPC/eNB or target system.
EPC/eNB Or Target System
TS1RELOCprep Expiry Handover Preparation procedure is canceled when timer TS1RELOCprep
expires.

Confidential
Chapter 9 SON
Causes Meaning
Cell not available The concerned cell is not available.
Unknown Target ID Handover rejected because the target ID is not known to the EPC.
Unknown PLMN The MME does not identify any PLMN provided by the eNB.
Table below outlines X2 HO preparation failure causes.

Causes Meaning
TRELOCprep Expiry Handover Preparation procedure is canceled when timer TRELOCprep
expires.
Cell not available The concerned cell is not available.
6) HO Blacklist Management
1 Serving cell can manage a NR as HO blacklist if the NR is determined as the
invalid NR or the NR causing HO performance degradation in case of
BLACK_LIST_MGMT_FLAG = True (command: CHG-SON-ANR)
o In case of BLACK_LIST_MGMT_FLAG = False, the eNB removes the
invalid NR or the NR causing HO performance degradation from the NRT.
2 Serving cell performs validation check for the NR managed as HO blacklist
by acquiring ECGI of the NR through reportCGI once during ranking period.
3 NRs can be changed from HO blacklist to the HO whitelist for the following
cases
o ECGI information of the NR is changed by reportCGI operation.
o The value of hand-in statistics for the HO blacklist NR is larger than
TH_HAND_IN_4_BLACK_2_WHITE (CHG-SON-ANR).
o Operator changes the HO attribute of the NR from HO blacklist to HO
whitelist.
Serving cell reports the results to EMS if the status of an NR is changed from HO
blacklist to HO whitelist due to the reason that the value of hand-in statistics for
the NR is larger than TH_HAND_IN_4_BLACK_2_WHITE.
Automatic X2-NRT Management Function
1) X2 NR Priority (Ranking) Calculation
The X2 NR ranking (priority) means the validity or significance of the X2 NR
included in X2 NRT. Samsung Intra-LTE ANR function defines that the X2 NR
ranking attribution has higher ranking as the more number of S1/X2 HO triggering
for X2 NR increases. X2 NR ranking is operated in the method shown below.
1 The X2 NR ranking calculation is performed after cell NR ranking.
2 The X2 ranking value used between the ranking calculation intervals uses the
ranking value calculated in the previous interval.
X2 NR ranking uses S1/X2 HO statistics and is calculated as shown below.
1 Collecting HOIn (i) statistics for X2 NR i in X2 NRT

Confidential
Chapter 9 SON
o Receive HANDOVER REQUEST (S1/X2).

o Index eNB i corresponding to the top ECGI in Last Visited Cell
Information IE included in UE History Information IE.
o Increase HOInS1 (i) or HOInX2 (i) by HO triggering type.
o HOIn (i) = HOInS1 (i) + HOInX2 (i)
2 Collecting HOOut (i) statistics for X2 NR i in X2 NRT
o Transmit HANDOVER REQUIRED (S1) or HANDOVER REQUEST
(X2).
o Increase HOOutS1 (i) or HOOutX2 (i) for eNB i as target of HO.
o HOOut (i) = HOOutS1 (i) + HOOutX2 (i)
3 Calculating the currentX2Rank value by X2 NR as follows:
o
o k: X2 NR ranking calculation time
o ω: IIR filtering coefficient
o previousX2Ranki (k): X2 rank value calculated in the previous interval
♦ I: Total number of X2 NRs in X2 NRT

♦ HOOut (i): S1/X2 HO-Out attempt count to neighbor eNB i at this
interval
♦ HOIn (i): S1/X2 HO-In attempt count collected to neighbor eNB i at
this interval
4 Setting the currentX2Rank value for the new X2 NR j which existed within
the NR ranking calculation period in X2 NRT
o
♦ DEFAULT_VALUE_X2: configurable system parameter
2) X2-NRT Size Management
MAX_X2_NRT_SIZE (CHG-SON-ANR) means the maximum number of X2
NRs, which can be included in the Intra-LTE X2 NRT, and is operated as the
following:
1 MAX_X2_NRT_SIZE: Different initial value can be set per service provider.
2 The eNB does not include X2 NRs more than X2 NRT hard limit in Intra-
LTE X2-NRT. Also, it manages the number of X2 NRs included in the Intra-
LTE X2-NRT not to exceed the MAX_X2_NRT_SIZE every ranking period.
3 If the operator configures the X2GuaranteedBandInfo to maintain minimum
number of X2 Links for a specific band indicator, the eNB performs X2 NR
deletion function for X2-NRT size management by considering the value of
the parameters in X2GuaranteedBandInfo.
When an attempt occurs to add a new X2 NR, in the situation where there exist X2

Confidential
Chapter 9 SON
NRs as many as MAX_X2_NRT_SIZE in Intra-LTE X2 NRT, eNB allows X2 NR

addition until X2-NRT hard limit size. If there is a request for adding a new X2
NR when there exist X2 NRs as many as X2-NRT hard limit, eNB deletes a X2
NR with the lowest CURRENT_X2_RANK among the X2 NRs with
NO_REMOVE = False (command: CHG-NBR-ENB) and NO_X2 = True
(command: CHG-NBR-ENB). If there is no X2 NR with NO_X2 = True, eNB does
not add the new X2 NR.
The eNB manages the number of X2 NRs included in the Intra-LTE X2-NRT not
to exceed the MAX_X2_NRT_SIZE every ranking period through following
operation.
1 Include in X2-NRT in order of X2 ranking among X2 NRs as NO_REMOVE
= True.
2 In the order of index of band indicator in X2GuaranteedBandInfo, includes
the X2 NRs which supports the band indicator in the X2-NRT from the order
of higher X2 ranking until the number of X2 NR reaches
MIN_X2_NRT_SIZE (CHG-SON-ANR).
o If the number of X2 NRs in X2-NRT is larger or equal to
MAX_X2_NRT_SIZE at step 2, omit step 3.
o Through the steps 1 and 2, the number of X2 NRs can be larger than
MAX_X2_NRT_SIZE.
3 Includes X2 NR in the X2-NRT from the order of higher X2 ranking until the
number of X2 NR reaches MAX_X2_NRT_SIZE.
Figure below depicts X2-NRT Size Management operation.
3) Unnecessary X2 NR Blacklisting
To reduce X2 signaling load caused by invalid X2 NR, if ratio of handover attempt
to an X2 NR is lower than predefined threshold, this function disconnects the X2
link with the unnecessary X2 NR. The operator can control this function’s

Confidential
Chapter 9 SON
ON/OFF state by configuring NR_X2_BLACK_ENABLE. At the X2 NR ranking

calculation point k, the serving eNB disconnects X2 Link by changing the attribute
of noX2 of X2 NR i which meets all the following conditions from False to True.
1 SON_X2_MGMT_ENABLE = Auto (command: CHG-SONFN-ENB)
2 NR_X2_BLACK_ENABLE = Auto (command: CHG-SONFN-ENB)
3 &
o : The average occurrence ratio of handover to X2
NR i during thTimeNrDel at the X2 NR ranking calculation point k
♦ WEIGHT_TH_X2_BLACK (CHG-SON-ANR): weight factor for

determining the threshold for judging the X2 NR as an invalid X2 NR
♦ : the number of X2 NRs which exist in X2-NRT more
than TH_TIME_NR_DEL (CHG-SON-ANR)
4 NO_REMOVE = False for X2 NR i (command: CHG-NBR-ENB)
Figure below depicts the statistics based X2 NR removal function.
4) X2 Link Restoring
eNB restores the X2 Link of the X2 NR by changing the attribute of NO_X2 from
True to False if the CURRENT_X2_RANK is larger than the predefined threshold
at X2 NR ranking calculation point. The operator can control this function’s
ON/OFF state by configuring NR_X2_RE_ENABLE. At the X2 NR ranking
calculation point k, the serving eNB restores X2 Link by changing the attribute of
NO_X2 of X2 NR i which meets all the following conditions from True to False.
1 SON_X2_MGMT_ENABLE = Auto (command: CHG-SONFN-ENB)
2 NR_X2_RE_ENABLE = Auto (command: CHG-SONFN-ENB)
3 &
o WEIGHT_TH_X2_RE (CHG-SON-ANR): weight factor for determining
Confidential
Chapter 9 SON
the threshold for judging the X2 NR as an X2 NR to be restored
o : the number of X2 NRs which exist in X2-NRT more than

ranking calculation period (rankPeriod)
4 NO_REMOVE = False for X2 NR i (command: CHG-NBR-ENB)
Creates Neighbor Cell Lists for Measurement Configuration
The LTE cell can transmit to a UE the measurement configurations of a maximum
of 32 frequencies and information of a maximum of 32 neighbor cells for each
configuration (cell individual offset). The cell individual offset is a parameter that
optimizes and improves each NR’s HO performance in the Samsung MRO
function. For the purpose of joint optimization with the Samsung MRO function,
the Samsung ANR function configures a maximum of 32 neighbor cell lists for
each frequency measurement configuration in the order of ranking. HO
performance can be improved when the cell individual offset value optimized for
each neighbor cell is transmitted to the UE in the order of the nearest coverage
with the serving cell. The procedure for this operation is as follows.
1 NRs with IS_HO_ALLOWED = True (command: CHG-NBR-EUTRAN) and
IS_REMOVE_ALLOWED = False (command: CHG-NBR-EUTRAN) are
configured in the neighbor cell list in the order of ranking.
2 (If it is not filled) NRs with IS_HO_ALLOWED = True and
IS_REMOVE_ALLOWED = True are configured in the neighbor cell list in
the order of ranking.
SYSTEM OPERATION
How to Activate
Preconditions
The UE must support Intra-LTE ANR capability (that is, the UE capability &
related feature group indicator bits are set to "1").
• The ANR_ENABLE value must be set to "Manual" or "Auto".
• To enable periodic Intra-LTE ANR functionality, the
PERIODIC_ANR_FLAG value must be set to "True".
• The ANR_UE_SEARCH_RATE_TOTAL value must greater than "0".
• For Intra-Frequency periodic ANR functionality, the
ANR_UE_SEARCH_RATE_INTRA_FREQ value must greater than "0".
• For Inter-Frequency periodic ANR functionality, the
ANR_UE_SEARCH_RATE_INTER_FREQ value must greater than "0".

Confidential
Chapter 9 SON
• The concerned E-UTRA FA's ANR_UE_SEARCH_RATE value must greater

than "0".
• The DRX_CONFIG_SETUP value must be set to "Drx_Config_Setup" or
"Drx_Config_reportCGI".
• The GBR_REPORT_CGI_OPTION must be set to "Allow" to enable ANR
function for UE with GBR Bearer (for example, QCI=1)
1 The eNB chooses an UE for periodic Intra-LTE ANR by ANR UE selection
rules.
2 In case that the Intra-LTE ANR UE is selected, the eNB configures ANR
specific measurement configuration for the UE (at this time, measurement
duration timer is started in the eNB).
3 The UE periodically measures and reports to the eNB based on ANR specific
measurement configuration.
4 When the eNB receives non-neighbor E-UTRA cell from the UE, the eNB
requests cell global identity to the UE (using reportCGI configuration).
5 If the eNB successfully obtains the non-neighbor E-UTRA cell's CGI from
the UE, the eNB registers the new E-UTRA cell into the own neighbor DB.
6 The eNB removes ANR specific measurement configuration from the UE
when the measurement duration timer is expired for Periodic ANR only.
(For mobility based Intra-LTE ANR) In case of the UE receives handover related
measurement report (that is, Event A3 or Event A5) from the UE, the eNB perform
from steps 4 and 5.
• The ANR_ENABLE value must be set to "Off".
• To disable periodic Intra-LTE ANR functionality, the
PERIODIC_ANR_FLAG value must be set to "False".
Key Parameters
parameters.
Parameter Descriptions of CHG-SONFN-CELL/RTRV-SONFN-CELL
ANR_ENABLE The parameter is used to control the Intra-LTE Automatic Neighbor Relation
(ANR) operation in three modes.
• Off: The Intra-LTE ANR function is not performed (NR ranking calculation is
performed).
• Manual: Operator approval is required for NR deletion. Other ANR functions
are performed automatically.

Confidential
Chapter 9 SON
• Auto: All ANR functions are performed automatically.
parameters.
Parameter Descriptions of CHG-SONFN-ENB/RTRV-SONFN-ENB
SON_X2_MGMT_ENABLE The flag controlling whether the automatic X2 interface management function
is performed or not.
• Off: The automatic X2 interface management function is not performed.
• Auto: The automatic X2 interface management function is performed (X2
ranking calculation and the size management of X2 Neighbor Relation Table
(NRT)).
SON_X2_DEL_ENABLE The flag controlling whether the automatic X2 interface deletion function is
performed or not.
• Off: The automatic X2 interface deletion function is not performed.
• Auto: The automatic X2 interface deletion function is performed.

PERIODICAL_ANR_FLAG The flag controlling whether the periodic neighbor cell adding function is
performed or not, for the E-UTRAN system.
• FALSE (0): The periodic neighbor cell adding function is not performed for
the E-UTRAN system.
• TRUE (1): The periodic neighbor cell adding function is performed for the E-
UTRAN system.
ANR_UE_SEARCH_RATE_ The total searching rate of UE, which performs the Automatic Neighbor
TOTAL Relation (ANR) measurement for intra-frequency EUTRAN neighbor cells in
the periodic neighbor cell adding function with a specific schedule.
ANR_UE_SEARCH_RATE_I The searching rate of UE, which performs the Automatic Neighbor Relation
NTRA_FREQ (ANR) measurement for intra-frequency EUTRAN neighbor cells in the
periodic neighbor cell adding function with a specific schedule.
ANR_UE_SEARCH_RATE_I The searching rate of UE, which performs the Automatic Neighbor Relation
NTER_FREQ (ANR) measurement for inter-frequency EUTRAN neighbor cells in the
periodic neighbor cell adding function with a specific schedule.
ANR_MEAS_DURATION_IN The duration of Automatic Neighbor Relation (ANR) measurement of UE to
TER_FREQ add E-UTRAN inter-frequency neighbor cells in the periodic neighbor cell
adding function. If the timer set to this parameter value is expired, serving cell
releases the corresponding setting of ANR measurement for the UE.
Parameter Descriptions of CHG-SON-ANR/RTRV-SON-ANR

MAX_NRTSIZE The maximum size of Neighbor Relation Table (NRT), which includes E-
UTRAN neighbor cells, for a given served cell. The number of Neighbor
Relations (NRs) in NRT should be managed so that it cannot exceed this
parameter value.
LSM_USAGE_FLAG The flag controlling whether LTE System Manager (LSM)-based new neighbor

Confidential
Chapter 9 SON
cell adding function is performed or not.
• False (0): The LSM-based new neighbor cell adding function is not
performed.
• True (1): The LSM-based new neighbor cell adding function is performed.
RANK_PERIOD The period for ranking calculation of Neighbor Relations (NRs), used in the
periodic NR ranking calculation function.
FILTERING_COEFF The Infinite Impulse Response (IIR) filtering coefficient used in the calculation
of current rank of neighbor cell in the periodic NR ranking calculation function.
The current rank is obtained based on the previous rank and the statistics of
Measurement Report (MR) for the current period, with this parameter.
NR_DEL_FLAG The flag controlling whether the function for deleting unnecessary Neighbor
Relations (NRs) is performed or not. If the statistics of Measurement Report
(MR) collected during a specific threshold time (TH_TIME_NR_DEL) for a
given NR is below a specific threshold (TH_NUM_MR_NR_DEL), the NR is
determined as unnecessary.
• False (0): Deletion of unnecessary NRs is not performed.
• True (1): Deletion of unnecessary NRs is performed.
TH_TIME_NR_DEL The threshold of time duration for collecting statistics, used in Neighbor
Relation (NR) removal function which deletes NRs being unnecessary or
degrading the Handover (HO) performance (Unit: day). If the statistics of
Measurement Report (MR) collected during a specific threshold time
(TH_TIME_NR_DEL) for a given NR is below a specific threshold
(TH_NUM_MR_NR_DEL), the NR is determined as unnecessary. If, for a
given NR, the HO attempt count collected during a specific threshold time
(TH_TIME_NR_DEL) exceeds a specific threshold (TH_HO_ATT_NR_DEL)
and the HO success count is below a specific threshold
(TH_HO_SUCC_NR_DEL), the NR is determined as degrading the HO
performance.
TH_NUM_MR_NR_DEL The threshold of statistics for Measurement Report (MR), used for deleting
unnecessary Neighbor Relations (NRs). If the statistics of MR collected during
a specific threshold time (TH_TIME_NR_DEL) is below this parameter value,
the NR is determined as unnecessary. The statistics of MR for a given
neighbor cell means the number of MR messages for this cell, triggered by HO
or periodic neighbor cell adding function.
WRONG_NR_DEL_FLAG The flag controlling whether the function of deleting Neighbor Relations (NRs)
degrading the handover (HO) performance is performed or not.
• False (0): Deletion of NRs degrading the HO performance is not performed.
• True (1): Deletion of NRs degrading the HO performance is performed.
TH_HO_SUC_RATE_NR_D The Handover (HO) success rate threshold value used for deleting the
EL Neighbor Relations (NRs) which degrade the handover (HO) performance. If
the HO success rate for a specific NR at the instant of NR ranking is below this
value, the NR is deleted from NRT (or blacklisted).
TH_HO_PREP_SUC_NR_D The Handover (HO) preparation success count threshold used for deleting the
EL Intra-LTE Neighbor Relations (NRs) which degrade the HO performance. If the
HO preparation success count collected exceeds this parameter value, it is
determined that the HO preparation success count condition is satisfied for
deleting the NRs which degrade the HO performance.
MAX_X2_NRT_SIZE The maximum size of X2 Neighbor Relation Table (X2 NRT). The number of
X2 Neighbor Relations (NRs) in X2 NRT should be managed so that it cannot
exceed this parameter value.
DEFAULT_VALUE_X2 For a given new neighbor eNB added in the X2 Neighbor Relation Table (X2
NRT), the default value set to the current X2 rank of this eNB at the first X2
ranking calculation time.
TH_X2_DEL Threshold value for deletion of unnecessary X2 NR.

Confidential
Chapter 9 SON
GBR_REPORT_CGI_OPTIO This parameter is the flag controlling whether to configure reportCGI to the UE
N with GBR bearer for Intra-LTE ANR purpose.
• Off (0): reportCGI is not configured.
• ScheduledAnr (1): reportCGI can be configured for Scheduled ANR.
• HoEventAnr (2): reportCGI can be configured for HO event based ANR
• BothAnr (3): reportCGI can be configured for Scheduled and HO event
based ANR.
RLF_INDICATION_USAGE_ This parameter is the flag that determines whether RLF Indication based
FLAG neighbor relation (NR) addition function is disabled or enabled
• False: RLF Indication based NR addition function is disabled
• True: RLF Indication based NR addition function is enabled
Parameter Descriptions of CHG-ANR-SCHED/RTRV-ANR-SCHED

ANR_STATE The flag controlling whether periodic neighbor cell adding operation is
performed or not.
• Inactive (0): Periodic neighbor cell adding operation is not performed.
• Active (1): Periodic neighbor cell adding operation is performed.
DAY The day of the week on which the periodic neighbor cell adding operation is
performed.
HOUR The start hour on which the periodic neighbor cell adding operation is
performed.
MINUTE The start minute on which the periodic neighbor cell adding operation is
performed.
DURATION The duration of time on which the periodic neighbor cell adding operation is
performed (Unit: hour).

ANR_UE_SEARCH_RATE The searching rate of UE which performs the Automatic Neighbor Relation
(ANR) measurement for corresponding carrier in the periodic neighbor cell
adding function with a specific schedule (unit: %).
MIN_NRT_SIZE_CARRIER This parameter is the minimum number of valid neighbor should be existed by
carrier. The purpose of this parameter is to prevent too much deletion for a
specific carrier in neighbor relation optimizing operation and to support Son
Load Balancing function's normal operation.
ANR_ALLOW The flag controlling whether new neighbor cell adding function for
corresponding carrier is performed or not, in the Automatic Neighbor Relation
(ANR) function.
• no_use (0): New neighbor cell adding function for corresponding carrier is
not performed
• use (1): New neighbor cell adding function for corresponding carrier is
performed

Confidential
Chapter 9 SON

QCI QCI index (Currently used index: 1 to 9
DRX_CONFIG_SETUP Whether to use the DRX.
• ci_Config_Release: DRX is not used.
• ci_Config_Setup: normal DRX profile is used in normal status and reportCGI
DRX profile is used in reportCGI status.
• ci_Config_reportCGI: DRX is not used in normal status and reportCGI DRX
ON_DURATION_TIMER_RE Timer to monitor the PDCCH in DRX mode when reportCGI status. Value is
PORT_CGI the number of PDCCH sub-frames: psf1 for 1 PDCCH subframe, psf2 for 2
PDCCH sub-frames and so on.
DRX_INACTIVITY_TIMER_R Timer to monitor PDCCH in DRX mode when inter-RAT reportCGI status.
EPORT_CGI Value is the number of PDCCH sub-frames: psf1 for 1 PDCCH subframe, psf2
for 2 PDCCH sub-frames and so on.
DRX_RETRANSMISSION_TI The timer used to monitor PDCCH in DRX mode when inter-RAT reportCGI
MER_REPORT_CGI status.
LONG_DRXCYCLE_START The long DRX cycle and drx start offset values to run onDurationTimer in DRX
_OFFSET_TYPE_REPORT_ mode when inter-RAT reportCGI status. The unit of the long DRX cycle is a
CGI sub-frame. If the short DRX-Cycle is set to a value, this parameter is set to a
multiple of the short DRX-Cycle. The DRX start offset is set to an integer. For
the TDD, DL sub-frame or UL sub-frame can be set.

EUTRA_REPORT_CGI_MR_ The time to wait for reception of reportCGI MeasurementReport (Intra-LTE)
TO_WAIT
Parameter Descriptions of CHG-PLMNANR-ENB/RTRV-PLMNANR-ENB

ANR_TARGET_MCC It is the MCC for defining Primary PLMN of Neighbor eNB. It is used to
determine the ANR operation per-PLMN about the eNB including the PLMN ID
in Global eNB ID.
ANR_TARGET_MNC It is the MNC for defining Primary PLMN of Neighbor eNB. It is used to
determine the ANR operation per-PLMN about the eNB including the PLMN ID
in global eNB ID.
USE_NBR_NO_X2 It is used to allow/block X2 connection to the neighbor eNB with primary PLMN
ID, which is configured in this PLD when the NBR eNB is added by ANR
function.
It is noted that default operation for the unregistered PLMN (if the PLMN ID is
not defined in this PLD or PLMN status is N_EQUIP) is to allow making X2
connection.
• no_use: If the useNBRNoX2 is CI_no_use for the registered target PLMN
ID, X2 connection setup is allowed. That is, primary PLMN of the newly
registered neighbor eNB added by ANR function is matched to the target
PLMN ID, eNB will set NO_X2 = false for this newly added eNB to allow to
setup X2 connection. Also, if the eNB receives X2 Setup Request from the
unknown eNB, it will add this eNB as the new neighbor eNB and accept to
make X2 connection by setting NO_X2 = False.
• use: If the useNBRNoX2 is CI_use for the registered target PLMN ID, X2

Confidential
Chapter 9 SON
connection setup is blocked. That is, primary PLMN of the newly registered
neighbor eNB added by ANR function is matched to the target PLMN ID,
eNB will set NO_X2 = True for this newly added eNB to block to setup X2
connection. Also, if the eNB receives X2 Setup Request from the unknown
eNB, it will add this eNB as the new neighbor eNB and reject X2 connection
by setting NO_X2 = True.
Parameter Descriptions of CHG-NBR-ENB/RTRV-NBR-ENB

CURRENT_X2_RANK The current X2 rank of corresponding EUTRAN neighbor eNB.
PREVIOUS_X2_RANK The previous X2 rank of corresponding EUTRAN neighbor eNB.
NO_X2_HO This parameter is the flag to determine whether X2 or S1 HO is used between
X2 NR only when X2 status is in service.
• False (0): X2 HO is used for X2 NR HO
• True (1): X2 HO is not used. S1 HO is used X2 NR HO
Parameter Descriptions of CHG-PLMNBLACK-LIST/RTRV-PLMNBLACK-

LIST
USED_FLAG It shows whether PLMN is used or not.
• no_use: not used
• use: used
MCC It refers to Mobile Country Code (MCC).
Enter a three-digit number with the numbers in each digit being 0~9.
MNC It refers to Mobile Country Code (MCC).
Enter a three or two-digit number with the numbers in each digit being 0~9.
EUTRA_BLOCK_FLAG This attribute indicates whether to apply the PLMN blacklist about the E-UTRA
neighbor.
• False: Not apply the PLMN Blacklist to the E-UTRA neighbor.
• True: Apply the PLMN Blacklist to the E-UTRA neighbor.
Parameter Descriptions of CHG-MSGAP-INF/RTRV-MSGAP-INF

GAP_RELEASE_FOR_REP This parameter is the flag controlling whether to release measurement gap or
ORT_CGI not when eNB commands to perform reportCGI to UE. This flag is only used
when reportCGI is configured with DRX
• False (0): eNB does not release measurement gap when configuring
reportCGI to UE.
• True (1): eNB releases measurement gap when configuring reportCGI to UE
GAP_USE_FOR_REPORT_ This parameter indicates whether to use the measurement gap for reportCGI
CGI in case that si-RequestForHo and DRX cannot be configured for reportCGI.
• False (0): measGap for reportCGI is not configured.
• True (1): measGap for reportCGI is configured.
GAP_PATTERN_FOR_REP This parameter is the measurement gap pattern used for reportCGI. A gap
ORT_CGI pattern is used to configure gap offset during MeasGapConfig configuration. If
it is gapPattern0, a gap offset (0-39) corresponding to Gap Pattern ID 0 is

Confidential
Chapter 9 SON
configured. If it is gapPattern1, a gap offset (0-79) corresponding to Gap
Pattern ID 0 is configured. This parameter is applied only when the
GAP_USE_FOR_REPORT_CGI is set to True.
Counters and KPIs

Tables below outline the main counters associated with this feature.
Counters related with Intra-LTE ANR function
HO IntraEnbPrepSucc The number of Intra-eNB handover preparation
success to intra-eNB neighbor cell.
IntraEnbSucc The number of Intra-eNB handover execution
success to intra-eNB neighbor cell.
InterX2OutPrepSucc The number of X2 HO preparation success to inter-
eNB neighbor cell.
InterX2OutSucc The number of X2 HO execution success to inter-
eNB neighbor cell.
InterS1OutPrepSucc The number of S1 HO preparation success to inter-
eNB neighbor cell.
InterS1OutSucc The number of S1 HO execution success to inter-
eNB neighbor cell.

STAT_SON_INTEGRATED IntraLTEHoSuc_Integ For all X2 and S1 Ho success cases. If the Cause
of the UE Context Release Command is not "HO
Success", counter shall not be increased.
Tables below outline the main Key Performance Indicators (KPIs) associated with
this feature
KPIs related with Intra-LTE ANR function
KPI Name Description
EutranMobilityHOIntra Intra-eNB handover success rate of E-UTRAN mobility
EutranMobilityHOX2Out X2 handover success rate of E-UTRAN mobility
EutranMobilityHOS1Out S1 handover success rate of E-UTRAN mobility
CallDropRatio Call drop rate
Call Faults related with Intra-LTE ANR function

Call Release Cause Description
C_ECCB_TMOUT_intra_Han The target cell cannot receive the RRC Connection Reconfiguration Complete
doverCmdComplete message during the intra-HO.
C_X2AP_CauseMisc_unspe The call is released after the target eNB receives a handover cancel message
cified from the source eNB.
C_X2AP_no_radio_resource The Sin receives the handover preparation failure message because the Ten
s_available_in_target_cell cannot check the targetCellID included in the handover request message as it

Confidential
Chapter 9 SON
Call Release Cause Description

is not a cell under the target eNB.
REFERENCE
[1] 3GPP TS 36.300: E-UTRA and E-UTRAN; overall description Stage 2
(Release 12).
[2] 3GPP TS 36.331: E-UTRAN; Radio Resource Control (RRC); Protocol
specification (Release 12).
[3] 3GPP TS 36.902: E-UTRAN; Self-configuring and self-optimizing network
(SON) use cases and solutions.
[4] 3GPP TS 32.500: E-UTRAN; Concepts & Requirements.
[5] 3GPP TS 32.501: E-UTRAN; Self-configuration of network elements; OAM
Requirements for Self-Configuration Use Cases.
[6] 3GPP TS 36.413: E-UTRAN; S1 Application Protocol (Release 12).
[7] 3GPP TS 36.423: E-UTRAN; X2 Application Protocol (Release 12).

Confidential
Chapter 9 SON
LTE-SO0202, Inter-RAT ANR (HRPD)

INTRODUCTION
Samsung Inter-RAT ANR (HRPD) automatically configures and manages inter-
RAT (HRPD) Neighbor Relation Table (NRT). This operation can guarantee the
stable inter-RAT mobility from LTE to HRPD system.
Samsung Inter-RAT ANR (HRPD) provides the following functions:
• Self-configuration Phase
o Automatic configuration of the initial inter-RAT (HRPD) NRT by O&M:
Generates Initial Inter-RAT (HRPD) NRT by using the information on
operational HRPD carriers and the location of the HRPD cell during the
eNB or cell addition in the EMS.
• Self-optimization Phase
o Finding new Inter-RAT (HRPD) neighbor cells and adding it to the inter-
RAT (HRPD) NRT
o Inter-RAT (HRPD) NRT management
i Calculation of Neighbor Relation (NR) ranking
ii Inter-RAT (HRPD) NRT size management
iii Unnecessary Inter-RAT (HRPD) NR removal
BENEFIT
• This feature can reduce CAPEX and OPEX costs, which have been spent to
configure and manage the inter-RAT (HRPD) NRT of LTE cells.
• The system performance indicators such as HO success rate and call drop rate
can be improved by configuring Inter-RAT (HRPD) NRT optimized for
coverage and air status of each LTE cell. This guarantees reliable mobility of
the UEs in the RRC_CONNECTED mode.
DEPENDENCY
E-UTRAN (LTE) CDMA (2G)
• Others:
To use Initial Inter-RAT (HRPD) NRT auto-configuration and Inter-RAT
(HRPD) NRT re-initialization, location information of the cell should be
configured. Location information can be set by operator or Auto GPS function
when adding a new cell.

Confidential
Chapter 9 SON
LIMITATION
None
SYSTEM IMPACT
None
None
Coverage
Inter-RAT ANR (HRPD) automatically configures Inter-RAT NRT optimized for
coverage.
Interfaces
None
FEATURE DESCRIPTION
Architecture
Samsung Inter-RAT ANR (HRPD) operates in eNB and EMS. The architecture is
as shown in the following figure.
Figure below depicts Samsung Inter-RAT ANR Architecture.

Confidential
Chapter 9 SON
Samsung Inter-RAT ANR (HRPD) is performed in the SON Agent of eNB and the
SON Manager of EMS and the operation by each entity is as follows:
• EMS
o SON Manager: NRT Management Function
♦ Initial Inter-RAT (HRPD) NRT configuration
• eNB
o SON Agent: NR Detection Function
♦ Finds unknown neighbor cell by configuring ANR measurement
configuration to UE.
o SON Agent: NR Add Function
i Requests to acquire CGI information on the unknown neighbor cell.
ii After receiving the CGI information, add a new neighbor cell to the
inter-RAT (HRPD) NRT.
o SON Agent: NRT Management Function
i Calculates NR ranking by using the number of MR messages for each
neighbor cell during the operation of adding periodically new neighbor
cells and inter-RAT mobility.
ii If a new neighbor cell is found in the situation that NRT is full, eNB
deletes the NR with the lowest rank and then adds the new one.

Confidential
Chapter 9 SON
iii When the number of MR messages received for an Inter-RAT (HRPD)

NR is reduced due to UE not reporting them any longer, eNB removes
the Inter-RAT (HRPD) NR based on the specific threshold.
Inter-RAT (HRPD) ANR Function

Self-Configuration Phase-Initial Inter-RAT NRT Auto Configuration
If Initial Inter-RAT (HRPD) NRT option is checked when adding a new cell, EMS
configures the Initial Inter-RAT (HRPD) NRT by using the information on
operational HRPD carriers and the location of already inputted HRPD cells in
EMS. Operator can find Initial Inter-RAT (HRPD) NRT option in Cell
Management Window in EMS. In the SON Property Window in EMS, operator
can set the following parameters used for the configuration of the initial inter-RAT
(HRPD) NRT.
1 Inter-RAT (HRPD) NRT Limit Distance: The maximum distance to the
HRPD cell which can be included to the initial inter-RAT (HRPD) NRT
2 Inter-RAT (HRPD) NRT Size: The maximum number of HRPD cells which
can be included to the initial inter-RAT (HRPD) NRT
Samsung EMS provides how to create the initial inter-RAT (HRPD) NRT as
follows:
1 EMS sorts the of the Inter-RAT (HRPD) carriers according to the index of
the Inter-RAT (HRPD) carrier (the carrier with low index has higher
priority).
2 EMS configures the initial Inter-RAT (HRPD) NRT by including the closest
neighbor cells as many as Inter-RAT (HRPD) NRT Size per carrier up to
Inter-RAT (HRPD) NRT hard limit from the first carrier in the above sorted
list.
Self-Optimization phase-Automatic Inter-RAT NRT Management
Finding New Neighbor Cells and Adding it to the Inter-RAT NRT
According to the specification, UEs can detect the HRPD cells only in the list sent
by eNB. Thus, it is necessary to configure a separate RRC message to detect
unknown HRPD cells. Samsung Inter-RAT ANR (HRPD) periodically performs
the operation of adding new HRPD neighbor cells. The operator can control the
schedule of Inter-RAT ANR (HRPD) by adjusting the
DAY/HOUR/MINUTE/DURATION for the inter-RAT ANR (HRPD) operation.
1 Operational interval setup: DAY/HOUR/MINUTE/DURATION
o Command: CHG-ANR-SCHED
♦ DAY: Day of the periodical operation of ANR (Possible to set "daily")
♦ HOUR: The time of starting the periodical operation of ANR
♦ MINUTE: The minute of starting the periodical operation of ANR
♦ DURATION: The duration of the periodical operation of ANR
2 Setup related to the selection of UE to be operated
o Rate of the UEs that perform operations
Confidential
Chapter 9 SON
(ANR_UE_SEARCH_RATE_TOTAL)
♦ Command: CHG-SONFN-CELL
♦ The rate of the UEs that perform the periodical ANR operation among
the UEs that attempt to access an initial call as its own cell or perform
HO preparation for HO-in during the period of periodical ANR
operation
o Rate of HRPD selection of UEs that perform operations
(ANR_UE_SEARCH_RATE_HRPD)
♦ Command: CHG-SONFN-CELL
o Rate of selecting the operational carriers (ANR_UE_SEARCH_RATE)
♦ Command: CHG-HRPD-FREQ
♦ The rate of each carrier selecting the periodical ANR operation
3 Addition of new neighbor cells to inter-RAT NRT by using HRPD band
supporting UEs
The procedure for the operation of adding a new HRPD neighbor cells is as
follows.
1 When it reaches at the time of the periodical addition of a new neighbor cell,
eNB (i) selects a UE for periodical operation of ANR, (ii) selects HRPD as
the network to perform ANR, and (iii) selects an operating carrier of HPRD
to send a RRC Connection Reconfiguration message that sets ANR
measurement configuration.
(i) The eNB selects a UE for periodical ANR operation among UEs that
attempt to access an initial call as its own cell during the period of ANR
operation or perform HO preparation for HO-in.
a The eNB checks whether the inter-RAT ANR (HRPD) operation is
supported by using the information included in the UE-EUTRA-Capability
IE of the selected candidate UE.
i Check the support by using the band information included in
SupportedBandListUTRA IE.
ii Check whether 19th bit = 1 & 23th bit = 1 in FeatureGroupIndicators
IE.
b The eNB selects a UE as follows.
i Create a random number between 0 and 1 for the UE that supports the
inter-RAT (HRPD) ANR operation (Nrandom).
ii If Nrandom < ANR_UE_SEARCH_RATE_TOTAL, the UE performs
the periodical operation of adding a new neighbor cell.
(ii) The eNB selects HRPD as the Inter-RAT network that will perform the
ANR operation.
o The possibility to select HRPD is determined based on the value of
ANR_UE_SEARCH_RATE_HRPD.
(iii) The eNB selects a carrier among HRPD carriers that will make the
periodical ANR operation.
Confidential
Chapter 9 SON
a Sets the scope of each HRPD carrier between 0 and 1 in order of carrier
index by using the value of ANR_UE_SEARCH_RATE configured in the
HRPD carrier.
♦ x_{k}: k ANR_UE_SEARCH_RATE set in the carrier.
♦ Scope of Carrier k
◊ Minimum value of scope: (Provided that if k = 0,

the minimum value = 0)
◊ Maximum value of scope:

b Selects the carrier according to the value of random number created
between 0 a0nd 1.
(iv) The eNB makes ANR measurement configuration as follows.
a If A2 event is used for inter-RAT ANR
♦ ReportConfigEUTRA: configures ANR specific A2 event
b If A2 event is not used for inter-RAT ANR or the eNB receives MR
message due to ANR specific A2 event
♦ ReportConfigInterRAT configuration: periodical {purpose =
reportStrongestCellsForSON}
◊ maxReportCells = 1 (Restriction in specification)
◊ reportAmount = 1 (Restriction in specification)
♦ MeasurementGap configuration
2 The eNB checks whether an unknown physical cell ID is included after the
MR message corresponding to ANR Measurement Configuration is received
from the UE.
a If the Inter-RAT (HRPD) cell in periodical MR is unknown cell and its
signal strength is exceeds the predefined threshold, the eNB performs step
3.
b If the Inter-RAT (HRPD) cell in periodical MR is known cell and
validation check is not performed for the cell, the eNB performs step 3.
3 Transmit the RRC Connection Reconfiguration message that requests the UE
to acquire the CGI of the target cell.
a ReportConfigInterRAT configuration: periodical {purpose = reportCGI}
b How to configure DRX
♦ Command: CHG-DRX-INF
◊ QCI: QCI index to operate the periodical addition of a new
neighbor cell (1 to 9)
◊ DRX_CONFIG_SETUP: ci_Config_reportCGI
◊ ON_DURATION_TIMER_INTER_RAT:
ci_onDurationTimer_psf10

Confidential
Chapter 9 SON
◊ DRX_INACTIVITY_TIMER_INTER_RAT:
ci_drx_InactivityTimer_psf100
◊ DRX_RETRANSMISSION_TIMER_INTER_RAT:
ci_drx_RetransmissionTimer_sf16
◊ LONG_DRXCYCLE_START_OFFSET_TYPE_INTER_RAT:
ci_sf2560_chosen
4 The UE acquires the CGI of a new cell corresponding to the unknown
physical cell ID in the DRX section for Inter-RAT.
5 It sends the MR message including the CGI information acquired to the
serving cell.
6 The serving cell updates NRT by using the CGI information obtained from
the UE.
7 It transmits the updated NRT information to EMS to synchronize NRT
information between two entities.
Figure below depicts Procedure of periodical NR adding function.
Inter-RAT (HRPD) NRT Management

The procedure of Samsung Inter-RAT ANR (HRPD) for calculating the NR
ranking is as shown below.
1 The serving cell collects the information on the statistics of MR messages

Confidential
Chapter 9 SON
during the operation of adding new neighbor cells for the neighbor cells
included in NRT or the operation of inter-RAT mobility.
2 When it reaches the time of calculating NR ranking, the serving cell
calculates the ranking of NRs included in the inter-RAT (HRPD) NRT by
using the collected statistical information.
Figure below depicts Periodical NR ranking calculation procedure.
1) Periodical Calculation of NR Ranking

NR ranking means the degree of validity or significance of the NRs included in the
inter-RAT NRT. Samsung eNB defines that NRs, which get more counts of
receiving MR messages due to the triggered inter-RAT mobility and have more
MR messages received during the operation of periodically adding new neighbor
cells are ranked higher. The operation of NR ranking is as shown below.
1 The calculation of NR ranking is performed at a certain interval.
o NR ranking interval: RANK_PERIOD (CHG-SON-ANR)
2 The NR related to ranking calculation should be included in the Inter-RAT
(HRPD) NRT at least for more than the ranking calculation interval.
3 The ranking value calculated in the previous interval is used for calculating
current ranking of the NR.
NR ranking is calculated in the following method:
1 The currentRank value of NR i in the inter-RAT NRT for more than the NR
ranking calculation interval
currentRank_{i}(k) = (1 - ω)·previousRank_{i}(k) + ω·NMR_{i}(k)
Confidential
Chapter 9 SON
NMR_{i}(k) = NPSHOMR_{i}(k) + NREDIRMR_{i}(k) +

NIRATANR_{i}(k)
o k: The time of calculating NR ranking
o ω: Filtering coefficient for moving averaging
o previousRank_{i}(k): The ranking value calculated at the previous interval
o NMR_{i}(k): The counts of receiving MR messages for Cell i collected
from k-1 as the time of calculating the just previous ranking to k and
composed of the items below.
♦ NPSHOMR_{i}(k): The count of receiving MR messages by the
satisfaction of B2 event during the performance of PSHO for Cell i
♦ NREDIRMR_{i}(k): The count of receiving MR messages by the
satisfaction of B2 event during the performance of redirection with SI
for Cell i
♦ NIRATANR_{i}(k): The number of receiving MR messages by the
setting of reportStrongtestCellsForSON during the operation of adding
a new neighbor cell
2 The currentRank value of NR j in the inter-RAT NRT for less than the NR
ranking calculation interval
a At k as the time of calculating NR ranking,
currentRank_{j}(k) = -1
♦ Keep as -1 until the time of the second NR ranking calculation.
b At k + 1 as the time of calculating next ranking,
currentRank_{j}(k + 1) = NMR_{j}(k + 1)
NMR_{j}(k + 1) = NPSHOMR_{j}(k + 1) + NREDIRMR_{j}(k + 1) +
NIRATANR_{j}(k + 1)
♦ If the number of receiving the MR message for NR j is 0, save as 0.
2) Handling Full Inter-RAT NRT Situation
If a new neighbor cell is found while the inter-RAT NRT is full, perform the
operation under the ANR configuration mode as follows:
1 INTER_RAT_ANR_ENABLE_HRPD = Auto or Manual (command: CHG-
SONFN-CELL)
a Causes of attempts at adding a new NR
i Add a neighbor cell by the ANR function periodically.
ii Add an operator manually.
b Operation
i Among NRs with the properties of CURRENT_RANK ≠ -1 & Status
(EQUIP) & HO (T) & Remove (T),
ii Delete the lowest ranked NR and then add a new one.
1) If CURRENT_RANK of NRS with the properties of

Confidential
Chapter 9 SON
CURRENT_RANK ≠ -1 & Status (EQUIP) & HO (T) & Remove (T)

in i of the procedure is -1 and there are two or more lowest ranked NRs
or all NRs are in the same ranking in ii) of the procedure: Delete the
NR whose time of adding the NRT is fastest and then add a new NR.
2 INTER_RAT_ANR_ENABLE_HRPD = Off
a Causes of attempts at adding a new NR: Operator attempts to add a new
NR.
b Operation: A new NR is not added.
3) Unnecessary Inter-RAT NR Removal
When the network is stabilized through the network optimization, this function
removes Inter-RAT NRs, which cannot receive MR messages among the Inter-
RAT NRs included when the network was initially created, so that only valid
Inter-RAT NRs could be included in the NRT. The operator can control this
function’s ON/OFF state, and at the NR ranking calculation point k, the serving
cell removes the Inter-RAT NR i which meets the following conditions.
1 INTER_RAT_ANR_ENABLE_HRPD = Auto or Manual & (command:
CHG-SONFN-CELL)
2 NR_DEL_FLAG_HRPD = True & (command: CHG-SON-ANR)
o NR_DEL_FLAG_HRPD: ON/OFF control flag that determines the
operational status.
3 CumulatedMRi (k) ≤ TH_NUM_MR_NR_DEL_INTER_RAT &
o CumulatedMRi (k): The number of Inter-RAT MR messages received for
NR i during TH_TIME_NR_DEL period at the NR ranking calculation
point k
o TH_NUM_MR_NR_DEL_INTER_RAT: The threshold value to decide
unnecessary Inter-RAT NR (command: CHG-SON-ANR)
4 "IS_REMOVE_ALLOWED = True" for Inter-RAT NR I (command: CHG-
NBR-HRPD)
SYSTEM OPERATION
How to Activate
Preconditions
• The eNB must support LTE to CDMA (HRPD) interworking functionality.
• The UE must support Inter-RAT CDMA (HRPD) ANR capability (that is, UE
capability & related feature group indicator bits are set to "1").
• The UE has no GBR bearer (for example, QCI = 1).

Confidential
Chapter 9 SON
• Run CHG-SONFN-CELL and set INTER_RAT_ANR_ENABLE_HRPD to
"Auto" or "Manual".
• Run CHG-SONFN-CELL and set ANR_UE_SEARCH_RATE_TOTAL value
to greater than "0".
• Run CHG-SONFN-CELL and set ANR_UE_SEARCH_RATE_HRPD value
to greater than "0".
• Run CHG-ANR-SCHED and set ANR_STATE value to "anrActive" (that is,
Periodic ANR functionality is scheduled).
• Run CHG-UTRA-FA and set the concerned HRPD carrier's
ANR_UE_SEARCH_RATE value to be greater than "0".
• Run CHG-DRX-INF and set DRX_CONFIG_SETUP value to be
"Drx_Config_Setup" or "Drx_Config_reportCGI".
• Run CHG-SONFN-CELL and set INTER_RAT_ANR_ENABLE_HRPD to
"Off".
• Run CHG-SONFN-CELL and set ANR_UE_SEARCH_RATE_HRPD value
to be greater than "0".
Key Parameters
parameters.
INTER_RAT_ANR_ENABLE The CDMA2000 HRPD Automatic Neighbor Relation (ANR) operation is
_HRPD controlled in 3 modes.
• Off (0): The CDMA2000 HRPD ANR function is not performed (NR ranking
calculation is performed).
• Manual (1): Operator approval is required for NR deletion. Other ANR
functions are performed automatically.
• Auto (2): All ANR functions are performed automatically.
ANR_UE_SEARCH_RATE_ The total searching rate of UE which performs the ANR measurement in the
TOTAL periodical ANR operation with a specific schedule.
ANR_UE_SEARCH_RATE_ The searching rate of UE which performs the Automatic Neighbor Relation
HRPD (ANR) measurement for CDMA2000 HRPD neighbor cells in the periodic
neighbor cell adding function with a specific schedule.
ANR_MEAS_DURATION_H The duration of Automatic Neighbor Relation (ANR) measurement of UE to
RPD add CDMA2000 HRPD neighbor cells in the periodic neighbor cell adding
function. If the timer set to this parameter value is expired, serving cell
releases the corresponding setting of ANR measurement for the UE.

Confidential
Chapter 9 SON
Parameter Descriptions of CHG-ANR-SCHED/CHG-ANR-SCHED

ANR_STATE This parameter indicates whether the Automatic Neighbor Relation (ANR)
function is performed periodically according to the currently active schedule.
• Inactive (0): The ANR function is not performed periodically.
• Active (1): The ANR function is performed periodically.
DAY This parameter is the day of the week on which the Automatic Neighbor
Relation (ANR) function is performed periodically.
HOUR This parameter is the hour (h) at which the Automatic Neighbor Relation (ANR)
function is performed periodically.
MINUTE This parameter is the minute (min) at which the Automatic Neighbor Relation
(ANR) function is performed periodically.
DURATION This parameter is the hour (h) at which the Automatic Neighbor Relation (ANR)
function is performed periodically.
Parameter Descriptions of CHG-HRPD-FREQ/RTRV-HRPD-FREQ

ANR_UE_SEARCH_RATE The searching rate of UE which performs the ANR measurement for the
corresponding carrier.

DRX_CONFIG_SETUP This parameter indicates whether to use the DRX.
• Release (0): DRX is not used.
• Setup (1): normal DRX profile is used in normal status and reportCGI DRX
• reportCGI (2): DRX is not used in normal status and reportCGI DRX profile
is used in reportCGI status.
ON_DURATION_TIMER_INT This parameter is timer to monitor the PDCCH in DRX mode when inter-RAT
ER_RAT reportCGI status.
Value is the number of PDCCH sub-frames: psf1 for 1 PDCCH subframe, psf2
DRX_INACTIVITY_TIMER_I This parameter is timer to monitor PDCCH in DRX mode when inter-RAT
NTER_RAT reportCGI status.
Value is the number of PDCCH sub-frames: psf1 for 1 PDCCH subframe, psf2
DRX_RETRANSMISSION_TI The timer used to monitor PDCCH in DRX mode when inter-RAT reportCGI
MER_ INTER_RAT status.
LONG_DRXCYCLE_START The long DRX cycle and drx start offset values to run onDurationTimer in DRX
_OFFSET_TYPE_INTER_R mode when inter-RAT reportCGI status. The unit of the long DRX cycle is a
AT sub-frame. If the short DRX-Cycle is set to a value, this parameter is set to a
multiple of the short DRX-Cycle. The DRX start offset is set to an integer. For
the TDD, DL sub-frame or UL sub-frame can be set.
Parameter Descriptions of CHG-SON-ANR/RTRV-SON-ANR

Confidential
Chapter 9 SON
IRAT_RANK_PERIOD This parameter is the period used for periodic calculation of Inter Radio
Access Technology (Inter-RAT) Neighbor Relation (NR) Ranking during
operation.
IRAT_FILTERING_COEFF This parameter is the IIR filtering value used for calculating the current rank
during Inter Radio Access Technology (Inter-RAT) Neighbor Relation (NR)
Ranking calculation. The current rank value is calculated as the average of the
previous rank value and the statistics value of the Measurement Report (MR)
for the current period. The IIR filtering value is a weighting applied to the MR
statistics of the current period.
NR_DEL_FLAG_HRPD This parameter is the flag controlling whether the function for deleting
unnecessary Inter-RAT (HRPD) Neighbor Relations (NRs) is performed or not.
If the statistics of Measurement Report (MR) collected during a specific
threshold time (TH_TIME_NR_DEL) for a given NR is below a specific
threshold (TH_NUM_MR_NR_DEL_INTER_RAT), the NR is determined as
unnecessary.
• False (0): The deletion of unnecessary Inter-RAT (HRPD) NRs is not
performed.
• True (1): The deletion of unnecessary Inter-RAT (HRPD) NRs is performed.
Counters and KPIs

Inter-RAT MR Count hrpdB2MR Measurement report message triggered by PSHO,
Redirection, SRVCC, and CCO.
hrpdPeriodicalMR Measurement report message triggered by CSFB
and periodical NR adding function.
REFERENCE
[1] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2 (Release 9)
specification (Release 9)
[4] 3GPP 32.500: E-UTRAN; Concepts & Requirements
[5] 3GPP 32.501: E-UTRAN; Self-configuration of network elements; OAM
Requirements for Self-Configuration Use Cases

Confidential
Chapter 9 SON
LTE-SO0301, PCI AutoConfiguration

INTRODUCTION
There are 504 Physical-layer Cell Identities (PCIs) in an LTE system. The PCIs
are grouped into 168 unique physical-layer cell-identity groups and each group
contains three unique identities. PCI of a cell, , is uniquely defined by a
number in the range of 0 to 167, representing physical-layer cell-identity
group, and a number in the range of 0 to 2, representing the physical-layer
identities within the physical-layer cell-identity group.
PCIs are used for synchronization and reference signal generation, which are
involved in cell selection, handover and channel estimation procedures. PCIs are
also used for physical channel scrambling of the DL and UL, resource element
mapping, cyclic shift and hopping.
Samsung PCI AutoConfiguration feature carries out initial PCI auto-configuration
when adding a new cell. In addition, it performs PCI collision/confusion detection
and PCI reallocation for PCI optimization of the network. This feature is
performed by eNB and EMS, respectively. The eNB performs it for the detection
of PCI collision and confusion with 2-tier neighbor list. EMS carries out for PCI
allocation and reallocation.
Samsung PCI optimization policy is as follows:
• PCI allocation should meet the collision-free and confusion-free condition.
• PCI allocation should reduce cell-specific reference signal (CRS) interference.
BENEFIT
• This feature reduces CAPEX/OPEX required for network installation and
expansion.
• This feature improves users' mobility performance between cells.
DEPENDENCY
• Interfaces & Protocols: To detect PCI conflict between the cells in different
eNBs, X2 interface should be established.
• Others: To use Initial PCI auto-configuration and PCI re-initialization, location
information of the cell should be configured. Location information can be set
by operator or by Auto GPS function when adding a new cell.

Confidential
Chapter 9 SON
LIMITATION
• If antenna azimuth/beamwidth of each cell is not exactly configured, the
performance of PSS Interference based PCI allocation/reallocation function
may be degraded.
• To change the status of the cell with invalid PCI to unlock, the operator should
manually change the value of the PCI different from current value or allocate
valid PCI to the cell by using PCI re-initialization function before changing the
status.
• PCI AutoConfiguration function allocates PCI of LTE cell and NB-IoT cell to
the same value when NB-IoT cell paired with LTE cell operates in In-band
mode.
SYSTEM IMPACT
capabilities.
Intra-LTE ANR: Intra-LTE ANR feature optimizes Neighbor Relation Table
(NRT) by automatically adding new neighbor cells based on UE measurement
reports and deleting neighbor cells based on handover statistics.
None
Coverage
PCI Auto-configuration automatically detects PCI conflict and resolves it. This
guarantees reliable mobility of the UEs when the UEs are moving between cells.
Interfaces
If PCI of a cell is changed by PCI Auto-configuration feature, the results are
propagated by X2 eNB Configuration Update message.
FEATURE DESCRIPTION
The Samsung PCI Auto-configuration is performed in the SON Agent of eNB and
the SON Manager of EMS.
Figure below depicts Samsung PCI optimization architecture.

Confidential
Chapter 9 SON
Operations of each entity are as follows:

• EMS: SON Manager
o PCI Management Function
i The EMS allocates PCI to newly added cell
ii The EMS selects PCI reallocation cell upon receiving the PCI
collision/confusion notification.
iii PCI reallocates a new PCI to the cell whose PCI is changed.
iv The EMS triggers PCI Reallocation Timer to the other cell involved in
PCI conflict.
• eNB: SON Agent
o PCI Collision/Confusion Detection Function
i The eNB detects PCI collision/confusion using the X2 Setup Request,
X2 Setup Response, eNB Configuration Update, and RLF Indication
messages forwarded by the Call Processor.
ii The eNB detects a PCI collision/confusion using the PCI and ECGI
information received from the Neighbor Detection Function.
o PCI Management Function

Confidential
Chapter 9 SON
i The eNB detecting PCI collision/confusion transmits a PCI conflict

notification to the EMS and stores it in the DB.
ii The other eNB having PCI conflicted cell runs a PCI Reallocation
Timer when EMS requests it to run the timer.
iii The other eNB having PCI conflicted cell requests a new PCI
allocation to the EMS when the timer is expired.
PCI Auto-configuration
The PCI auto-configuration function is performed in the EMS. EMS aims to
allocate PCIs based on the distance between cells to avoid PCI collision/confusion.
It determines the reference distance from the newly added cells and then allocates
PCIs which can avoid PCI collision/confusion between the cells within the
reference distance.
Figure below depicts a brief overview of the PCI auto-configuration.
There are following two kinds of situation to avoid when PCI auto-configuration is
performed.
PCI Collision
• Definition: Two adjacent cells with overlapped coverage use the same
frequency and PCI.
• Problem: Handover ambiguity occurs because the UE existing on the border of
the two cells cannot distinguish the serving cell and the neighbor cell.
Figure below depicts PCI collision.

Confidential
Chapter 9 SON
PCI Confusion
• Definition: Two neighbor cells adjacent of the serving cell (cell B) use the
same frequency and PCI.
• Problem: Handover ambiguity occurs because the cell B cannot distinguish
which is the correct target cell based on the PCI in MR.
Figure below depicts PCI confusion.
The PCI auto-configuration operates as follows:

1 The EMS receives latitude/longitude coordinates of the newly added cell
from the operator or the GPS during eNB addition.
2 After completing eNB addition in EMS Data Base (DB), EMS selects
Physical Layer Identity (PLI) and PCI of the added cell. At this instant, value
of PCI_ALLOC_STATUS (RTRV-CELL-IDLE) is tempAlloc.
o In case that an operator manually configured latitude/longitude of the
added cell at the eNB addition, EMS selects PLI and PCI of the added cell
at the instant that eNB completes software download.
o In case that an operator used Auto GPS function at the eNB addition, EMS
selects PLI and PCI of the added cell at the instant that latitude/longitude
of the added cell is updated by GPS.
3 When the EMS selects PLI of the added cell, following two modes are used.
PLI selection should be done before PCI selection.
o Location-based mode: The EMS selects PLI of the added cell so that PLI

Confidential
Chapter 9 SON
of the cell is different from the PLIs of the adjacent cells in the same
location.
o PSS Interference Based mode: The EMS selects PLI of the added cell so
that strength of the PSS interference from adjacent cells for the PLI is
minimized.
4 When EMS selects PCI of the added cell, the following two modes are used.
PCI is selected according to the PLI selected above.
o Location-based mode: The EMS selects the PCI other than the ones used
by all cells that are managed by the same EMS within the reference
distance (D) from the added cell. If the cells within the reference distance
(D) use all allocable PCIs, The EMS selects the PCI by using the
maximum reuse distance. Maximum reuse distance means the maximum
distance between cells which the same PCI can be reused within "D".
o PSS Interference-based mode: The EMS selects the PCI other than the
ones used by the cells in the virtual 2-tier NRT. If the cells in the virtual 2-
tier NRT use all allocable PCIs, EMS selects the PCI by using the
maximum reuse distance.
5 EMS allocates the selected PCI to the added cell. Then, value of
PCI_ALLOC_STATUS is changed from tempAlloc to realAlloc. If
PCI_ALLOC_STATUS is not set to realAlloc, the status of the cell cannot be
changed to "unlocked".
Reference Distance Calculation for PCI Auto-configuration
When allocating a PCI to newly added cell, the EMS selects the PCI which is not
used by the cells within the reference distance (D) from the newly added cell. D is
calculated as follows.
• D = MAX (R * R_Multi, LimiDist)
o R = Inter-site distance
o R_multi = [1, 4]
o LimitDist = [1, 100] km
The following explains the meaning of the parameters used for calculating
reference distance (D):
1 R is the Inter-site distance. Samsung support three different kinds of Inter-site
distance R calculation mode. The operator can choose them in PCI Type
menu of EMS SON Property GUI.
o Minimum: Distance of the nearest neighbor cell is used as R
o Distance: Operator-configured distance is used as R
o Average: Average distance with cell inside LimitDist is used as R
2 R_multi is a scaling parameter for expanding Inter-site distance R. The
operator can adjust the number of cells within the distance D with R_multi
which is determined with PCI Multiplication Factor in the EMS SON
Property Window.
3 LimitDist is the minimum of the effective Distance D when allocating PCI.
Even through dense deployment area, each cell should consider minimum
Confidential
Chapter 9 SON
distance LimitDist for PCI auto-configuration. Operators can change

LimitDist value using PCI Distance Limit in the EMS SON Property
Window.
Primary Synchronization Signal (PSS) Interference Avoidance
The assignment of PCI value to a cell is defined with two parameters: physical-
layer cell identity groups and Physical Layer Identity (PLI). Before the EMS
assigns the unique PCI value to a cell, it chooses PLI value (that is, PSS) for each
cell to reduce CRS interference between source and neighboring cells. If Initial
PCI Configuration is set to PSSInterferenceBased mode, following algorithm is
performed for selecting PLI.
During the deployment of a new cell, the EMS selects the cells within the
reference distance and sorts the cells in accordance with their distance. EMS
defines SameLocationCellGroup and makes the cells with the same location
belong to SameLocationCellGroup. The EMS then makes the possible PLI sets for
the cells in SameLocationCellGroup.
Figure below depicts PSS interference avoidance for three cells with the same
location.
For each PLI set, the EMS calculates inter-cell interference which is calculated by
using location information, antenna azimuth and beam width of each cell. The
EMS chooses the PLI set with the minimal inter-cell interference as optimal PLI
set and use it for selecting PCI value.
Figure below depicts the PSS interference avoidance for four cells.

Confidential
Chapter 9 SON
If there are more than one SameLocationCellGroup, the EMS calculates

interference for each SameLocationCellGroup and sorts them in the descending
order of the interference. Then, EMS chooses PLI set for each
SameLocationCellGroup from SameLocationCellGroup with higher interference.
The obtained PLI values for all cells are used to select PCI values.
Initial PCI Allocation for NB-IoT Cell
PCI Auto-configuration provides the functionality that allocates a PCI to NB-IoT
cell according to the operation mode of the NB-IoT cell when adding a new NB-
IoT cell.
In case of adding a new NB-IoT cell operating in In-band mode, the EMS allocates
NB-IoT cell the same PCI used by the paired LTE cell.
PCI Optimization
PCI Collision/Confusion Detection
The PCI collision/confusion detection function is performed in the SON Agent of
the eNB. When PCI collision/confusion is detected, the SON Agent reports the
occurrence of PCI conflict and the 2-tier neighbor relation table (2TierNRT)
information to the SON Manager of the EMS.
• PCI conflict is detected when the following event occurs
o PCI is changed by operator
o New neighbor relation is added by operator or through ANR operation
o X2 Setup Request/Response or X2 eNB Configuration Update message is
received from neighbor eNB.
• Pre-requisite information for detecting PCI conflict is as follows.
o NRT
o 2TierNRT
A serving cell is aware of only its immediate neighbor cell (that is, NRT) and does
not know its 2-tier neighbor information. Thus, when an eNB receives X2 Setup

Confidential
Chapter 9 SON
Request/Response or eNB Configuration Update message from its neighbor eNBs,

the eNB updates 2TierNRT information of its cells. This 2TierNRT information is
used for detecting PCI conflict and for selecting a new PCI.
Figure below depicts PCI collision/confusion detection.
1 If the served cell or neighbor cell information is changed, an X2 eNB

configuration update message is transferred.
2 Based on the X2 eNB configuration update message, the eNB updates NRT
and 2TierNRT of its cells and checks if there is PCI conflict.
3 If PCI conflict is detected, the eNB reports it to the EMS with 2-tier PCI list.
4 The EMS selects a new PCI based on the 2-tier PCI list.
5 The EMS allocates the new PCI to the cell involved in PCI conflict.
PCI Collision Detection based on UE Mobility
The PCI collision detection function based on UE mobility focuses on the
resolution of PCI conflict between neighboring eNBs when UE moves from one
cell coverage to other one. By using this function, the PCI collision can be
detected even though there is no neighbor relation between two adjacent cells. UE
cannot successfully perform HO: RLF occurs due to RF degradation and UE tries
to synchronize with the target cell. The UE requests RRC Connection Re-
establishment to the target cell; however, the request is rejected, because the target
cell does not have the UE Context.
• PCI collision detection occurrence
o The UE moves from the serving cell to the target cell
o The UE experiences RLF event
o The UE tries RRC Re-establishment (RRE) procedure in the target cell

Confidential
Chapter 9 SON
o The eNB of the target cell can detect PCI that can be potentially involved
in the PCI collision
• Condition for PCI collision detection
There are three defined conditions that control PCI collision detection:
o Condition 1: PCI in UE-Identity and PCI of the cell that receives Re-
establishment request from UE are the same.
o Condition 2: C-RNTI in UE-Identity has already existed in the cell that
receives Re-establishment request from UE
o Condition 3: Short MAC-I in UE-Identity is not identical to Short MAC-I
that is calculated by the target cell
PCI collision is detected if condition 1 is satisfied and condition 2 is not
satisfied, or all three conditions are satisfied at the same time.
• Pre-requisite
SON Manager at EMS differentiates PCI conflict message and PCI collision
notification
Figure below depicts Samsung Femto PCI collision detection based on UE
mobility.
Once SON Manager at EMS receives the notification of the PCI collision from
eNB, the SON manager reallocates the PCI of the cell reporting PCI collision
notification.
To exclude the redundancy of notification of PCI collision EMS saves PCI
collision event and waits until PCI reconfiguration period starts. In this case, EMS
begins to resolve PCI collision one by one during PCI reconfiguration period. If
another timer that relates to PCI confusion event is running, the EMS turns off the
timer.
PCI Conflict Detection based on RLF Indication Message
If Cell A of eNB 1 receives RRC Connection Reestablishment Request message
from a UE, eNB 1 checks if it has the context of the UE. If eNB 1 does not have
the UE Context, it transmits RLF Indication message to the eNB 2 which has UE’s

Confidential
Chapter 9 SON
previous serving cell (Cell B). After receiving RLF Indication message, Cell B
checks if there is PCI conflict by checking following conditions. If the following
two conditions are satisfied, Cell B transmits PCI conflict event to the SON
Manager in the EMS.
• Re-establishment cell ECGI (Cell A) in RLF Indication message is not
included in its own NRT.
• PCI and EARFCN of Re-establishment cell are the same to the cell already
registered in its own NRT.
Once the SON Manager in the EMS receives PCI conflict detection event from
Cell B of eNB 2, it determines the PCI reallocation cell based on ECI information
and reallocates a new PCI to the cell based on 2TierNRT information.
Figure below depicts the procedure of PCI conflict detection based on RLF
Indication message.
PCI Reallocation Cell Selection

Though PCI conflict always happens in pair, it is enough to reallocate PCI to one
cell. When EMS receives the PCI conflict report from the eNB, it determines one
cell to change PCI as follows.
• If a cell which is involved in PCI conflict reports the PCI conflict event
o If the EMS manages the two cells which are involved in PCI conflict
♦ The EMS reallocates a new PCI to the cell which reports PCI conflict
event.
Confidential
Chapter 9 SON
♦ The EMS triggers PCI Reallocation Timer to the other cell. The value
of PCI Reallocation Timer is determined by
TH_PCI_REALLOCATE_LATENCY (CHG-SON-PCI).
o If the EMS manages only one cell among the cells which are involved in
PCI conflict
♦ If the cell has higher ECI, EMS reallocates a new PCI.
♦ If the cell has lower ECI, EMS triggers PCI Reallocation Timer.
• If a cell which is not involved in PCI conflict reports the PCI conflict event
o The EMS reallocates a new PCI to the cell having higher ECI.
o The EMS triggers PCI Reallocation Timer to the cell having lower ECI.
If the PCI reallocation cell successfully changes its PCI, the eNB managing the
cell sends its neighbor eNBs the eNB Configuration Update message to inform the
change of the PCI. If the other cell involved in PCI conflict recognizes the
resolution of the PCI conflict through eNB Configuration Update message, the cell
cancels the PCI Reallocation Timer. If the PCI Reallocation Timer is expired, the
cell recognizes that the PCI conflict is not resolved and requests the EMS to
reallocate a new PCI.
If the EMS receives UE mobility based PCI collision detection event, it selects the
cell, which reported PCI collision detection event as PCI reallocation cell.
PCI Reallocation
After selecting the target cell for PCI reallocation, EMS selects a new PCI for the
target cell. There are two types of PCI reallocation methods: PLI Maintenance
Based and PSS Interference Based. Operator can choose them in PCI
Reconfiguration Method of EMS SON Property Window. In case that LTE cell has
paired NB-IoT cell operating in In-band mode, EMS allocates NB-IoT cell the PCI
allocated to the paired LTE cell when allocating PCI to the LTE cell.
• PLI Maintenance Based PCI reallocation
The PLI Maintenance Based PCI reallocation procedure is as follows;
1 The EMS receives 2TierNRT PCI list from eNB (The 2TierNRT PCI list is
composed considering one-way neighbor relation).
2 The EMS makes available PCI pool by excluding the following from the PCI
whitelist.
o The PCIs that have different PLI from that of the PCI used before
o The PCIs in the 2TierNRT PCI list
3 The EMS reconfigures a new PCI from available PCI pool.
• PSS Interference Based PCI reallocation
The PSS Interference Based PCI reallocation procedure is as follows;
1 The EMS receives 2TierNRT PCI list from eNB (the 2TierNRT PCI list is
composed considering one-way neighbor relation).
2 The EMS selects the PLI that minimizes PSS interference from adjacent cell

Confidential
Chapter 9 SON
3 The EMS makes available PCI pool by excluding the following from the PCI
whitelist.
o The PCIs that have different PLI from the PLI selected in step 2
o The PCIs in the 2TierNRT PCI list
4 The EMS reconfigures a new PCI from available PCI pool.
PCI Optimization Tool in EMS

PCI reservation
PCI Auto-configuration provides a function for setting PCI whitelist to prevent the
assignment of specific PCI, a whitelist can be set. The PCI whitelist can be set in
SON Property window in EMS.
• PCI White List: The PCI White List values can be set range from single to
multiple. For example, 0, 100-500 means PCI can be set 0 and from 100 to
500.
Time to Trigger PCI Change
After detection of PCI conflict, eNB reports this event to EMS. EMS saves PCI
conflict event and waits until PCI Reconfiguration Start Time start. When EMS
meet PCI Reconfiguration Start Time, then begin to resolve PCI conflict event one
by one during PCI Reconfiguration Period. PCI reconfiguration start time and
period can be set in "SON Property" in EMS.
• PCI Reconfiguration Start Time: scheduled start time for changing conflicted
PCI.
• PCI Reconfiguration Period: the period for changing conflicted PCI.
SYSTEM OPERATION
How to Activate
Preconditions
• The PCI optimization function is activated in the LSM
To activate this feature, PCID_ENABLE_ENHANCED value must be set to
Manual or Auto or Scheduled.
• The eNB monitors X2 Setup Request, X2 Setup Response, and X2 eNB
Configuration messages.
• The eNB delivers PCI conflict information to the LSM when the PCI collision
or confusion is detected.
Confidential
Chapter 9 SON
• If the new PCI is reassigned from the LSM, the eNB applies the new PCI to
the system.
To activate PCI collision detection based on UE mobility information feature,
PCI_COLLISION_DETECT_FLAG value must be set to True.
• To deactivate this feature, PCID_ENABLE_ENHANCED value must be set to
Off.
• To deactivate PCI collision detection based on UE mobility information
feature, PCI_COLLISION_DETECT_FLAG value must be set to False.
Key Parameters
parameters.
The following tables show SON property for NRT auto-configuration in LSM.
SON property for PCI auto-configuration
R Count The number of Cell to calculate an average of NRT, PCI and RSI.
• The number of cell for calculations should be equal or less than that of the R
count, and also a cell should be within the initDistance.
• Range: 1 - 32
PCI Types A decision criterion of an effective radius on PCI allocations.
• Distance: A value based on a fixed distance.
• Average: Use the R value, derived from an average of distances between a
PCI and cells.
• Minimum: Use the R value, derived from a minimum distance between a PCI
and the nearest cell.
PCI Multiplication Factors An increase range for calculating an effective distance on PCI allocations.
• Range: 1 - 4
PCI Distance Limits A minimum effective radius on PCI allocations.
• Range: 1 - 100
Initial PCI Configurations Select an initial PCI allocation algorithm.
• LocationBased: Without using tier-2 NBR, allocate PCIs based on a distance.
• PSSInterferenceBased: Allocate PCIs that show the minimum PSS
interruption.
Pico PCI White List Set Pico PCI White List
• Can set up to 10 ranges.
• In case of entering none or space: allocated Pico PCI of that range
• Can set as number or number-number. (for example, 0 - 100, 150 - 200, 300)
Macro PCI White List Set Macro PCI White List
• Can set up to 10 ranges.
• In case of entering none or space: allocated Macro PCI of that range

Confidential
Chapter 9 SON
• Can set as number or number-number. (ex: 0-100, 150-200, 300)
PCI Reconfiguration Modes A way to change the cell status after PCI allocations.
• cellAdminShutDown: Unlock à Shutting down.
• cellAdminLock: Unlock à Locked.
PCI Reconfiguration Timeout A timeout value on cell status changes.
• Range: 0 - 60 minutes
PCI Reconfiguration Select a PCI reallocation Algorithm.
Methods • PLIMaintenanceBased: Select a PCI value not used by 2 tier neighbor cells
while maintaining PLI.
• PSSInterferenceBased: Select a PCI value not used by 2 tier neighbor cells
while considering PSS interference.
PCI Reconfiguration Start Execution time for a PCI schedule mode modification.
Time • Range: 0 - 23 hours
PCI Reconfiguration Periods Periods for scheduled PCI reallocation from start time
• Range: 1 - 23 hours
PCI Manual Applications PCI Manual Application Timeout.
Waiting Time • Range: 0 - 4320 in minutes
• If you input zero or nothing, unable to use a manual application waiting time.
Parameter Descriptions of CHG-SONFN-ENB/RTRV-SONFN-ENB

PCID_ENABLE_ENHANCE The Self-Organizing Networks (SON) Physical Cell Identity (PCI) optimization
D function is controlled in three modes.
• Off: 2tier PCI list management through X2 monitoring is only performed.
• Manual: 2tier PCI list management through X2 monitoring and PCI
collision/confusion detection is automatically performed. For the PCI
reallocation function, PCI for a cell is reallocated with operator approval.
• Auto: 2tier PCI list management through X2 monitoring and PCI
collision/confusion detection, PCI reallocation functions are performed
automatically.
• Scheduled: 2tier PCI list management through X2 monitoring and PCI
collision/confusion detection is automatically performed. For the PCI
reallocation function, PCI for a cell is automatically reallocated during the
pre-defined time set by operator.
PCI_COLLISION_DETECT_ This parameter corresponds to the flag for PCI Collision Detection. If the value
FLAG of the parameter is set 0, pciCollisionDetectionFlag is switched off, if the value
of the parameter is set 1, pciCollisionDetection is switched on.
parameters.
Parameter Descriptions of CHG-SON-PCI/RTRV-SON-PCI
TH_PCI_REALLOCATE_LA This parameter is the standby time (min) for requesting reallocation of the
TENCY Physical Cell Identity (PCI). If PCI reallocation is not performed normally during
the set time, PCI is reallocated by selecting the other cell involved in the PCI
conflict. If the PCI_Reconfiguration_Modes is set to cellAdminShutDown, it is
recommended that the value of TH_PCI_REALLOCATE_LATENCY is bigger

Confidential
Chapter 9 SON
than PCI_Reconfiguration_Timeout, PCI_Reconfiguration_Modes and
PCI_Reconfiguration_Timeout respectively belongs to Self-Organizing Network
(SON) Property of Entity Management System (EMS).
Counters and KPIs

with this feature.
REFERENCE
[4] 3GPP 32.500: E-UTRAN; Concepts & Requirements
Requirements for Self Configuration Use Cases
[6] 3GPP 32.521: E-UTRAN; Self-Organizing Networks (SON) Policy Network
Resource Model (NRM) Integration Reference Point (IRP); Requirements
Resource Model (NRM) Integration Reference Point (IRP); Information Service
(IS)
[8] 3GPP 32.541: E-UTRAN; OAM Requirements for Self Healing Use Cases

Confidential
Chapter 9 SON
LTE-SO0401, RACH optimization

INTRODUCTION
Random Access Channel (RACH) of an LTE system is the uplink channel defined
in the 3GPP specifications. Depending on the purpose, RACH is classified into
two types, contention based method, and non-contention based method. The
contention based method is used for the initial network connection of the User
Equipment (UE) and the non-contention-based method is used for the connection
to the target cell during the UE's handover. The actual information transmitted to
RACH includes the Zadoff Chu (ZC) sequence whose total length is 839. An LTE
System has total 838 ZC sequences (root sequences) for RACH and one ZC
sequence can be reused by cyclic shifting. The UE transmits one sequence, that is,
Random Access Preamble (RAP) through Physical Random Access Channel
(PRACH) that is the physical channel of RACH to connect initially to the network
or attempt a connection to the target cell. Each cell of an LTE System configures a
RAP set with total 64 consecutive RAPs. As the UE selects and uses any RAPs in
this RAP set, the number of root sequences used in a cell is determined by the
reuse number of one root sequence. A cell can use RAPs by dividing the 64 RAPs
into preambles for random access and the dedicated preambles for handover.
PRACH resource allocation in an LTE System is determined by the PRACH
Configuration Index and PRACH freq-offset. The PRACH Configuration Index
indicates the PRACH allocation interval and the location of the subframe where
PRACH is transmitted. The PRACH freq-offset indicates the location of the
physical resource block where PRACH is allocated. The PRACH Configuration
Index is used to determine the reuse number of root sequence. Each RACH
resource parameter value can be determined with various combinations by
HighSpeedFlag, Zero Correlation Zone Configuration (ZCZC), and Random
Access Preamble format.
Samsung RACH Optimization aims to minimize UE access delay and maximize
UL capacity using various RACH resources. Samsung RACH Optimization
consists of auto-configuration and optimization functions. The auto-configuration
function automatically selects the Root Sequence Index (RSI) of the newly added
cell. It sets the reference distance based on the location of the added cell and
selects RSI of the added cell so that RSI reuse within the reference distance is
minimized. The optimization function performs RSI collision detection and
reallocation, optimization of the number of dedicated preambles, and optimization
of the PRACH parameters such as Preamble Initial Received Target Power, power
ramping step, PRACH Configuration Index, and backoff indicator.
BENEFIT
• This feature can reduce previously spent CAPEX and OPEX cost for
configuring and managing the RSI and PRACH parameters of the LTE cells.
• This feature can minimize UE access delay and maximize UL capacity.

Confidential
Chapter 9 SON
DEPENDENCY
E-UTRAN (LTE)
• Others:
Application of the RSI configuration requires location information of the cell
where the RSI allocation is required. Application of the RACH optimization
needs 3GPP Rel.9 UE support including rachreport in UE information
message.
LIMITATION
• Self-Configuration: The location based RSI allocation method might cause a
RSI collision with a cell that does not use the same EMS.
o Initial RSI allocation/RSI re-initialize functions is not performed if cells'
latitude/longitude information is not configured.
• Self-Optimization: RSI allocation method might cause RSI reallocation failure
when X2 connection is unable between eNBs.
o In manual apply mode of periodic RACH optimization, statistics cannot be
collected during waiting time of operator's manual apply confirmation. In
this case, optimization cannot be performed in the next optimization period
if the amount of collected statistics is not enough to optimization.
o According to 3GPP standard, the range of RSI value is restricted according
to the values of PRACH Configuration Index, ZCZC, and High Speed
Flag. If operator manually configures unavailable combination of RSI,
PRACH Configuration Index, ZCZC, and High Speed Flag, RACH
operation can be affected.
SYSTEM IMPACT
None
• RSI auto-configuration and RSI collision detection/reallocation functions can
improve RACH access performance by avoiding RSI conflict.
• Periodic PRACH parameter optimization function can reduce RACH access
delay and improve RACH success rate by adjusting RACH parameters based
on RACH statistics.
Coverage
If UEs fail random access due to low preamble transmission power, Periodic
PRACH parameter optimization function adjusts preamble transmission power for
random access. This can improve random accesses performance of the UEs in cell
edge area.

Confidential
Chapter 9 SON
Interfaces
X2 interface may affect the operation of RSI conflict detection.
Interface between eNB and EMS may affect the operation of RACH Optimization.
FEATURE DESCRIPTION
Architecture
The Samsung RACH Optimization operates in the eNB SON Agent and EMS
SON Manager. The overall structure is as follows.
The figure below depicts Samsung RACH Optimization Architecture.
Each entity’s operation is as follows

• EMS: SON Manager
o RSI Management Function
i Allocates RSI to newly added cell
ii Selects RSI reallocation cell upon receiving the RSI collision
notification.
iii Transmits a new RSI to the cell whose RSI is changed.
iv Triggers RSI Reallocation Timer to the other cell involved in RSI
collision.

Confidential
Chapter 9 SON
o RO Parameter Control Function

♦ Supports control of PRACH Configuration Index whenever eNB
requests change of Random Access opportunity.
• eNB: SON Agent
o RO Statistic Management
♦ Collects and accumulates the RO-related statistics information from
the UE and eNB.
♦ Receives changed RO-related parameters and transmits to the Radio
Resource Control (RRC) block.
o RO Parameter Control Function
♦ Changes RO parameters at every RACH parameter decision interval
based on accumulated RACH statistics.
o RSI Collision Detection Function
♦ Detects RSI collision through the
ENB_CONFIGURATION_UPDATE message received from the call
processor.
Note: In case that Manual apply option is used
(RACH_OPT_ENABLE/RSI_CONFLICT_ENABLE = Manual, command: CHG-
SONFN-CELL), the optimization/re-allocation process is active as usual but the
change in RACH optimization parameter (that is, PRACH Configuration Index) or
the reallocation of RSI can only proceed on manual confirmation by the operator.
Self-Configuration Procedure
RSI Auto-configuration
Samsung RSI auto-configuration is performed in EMS and aims to allocate RSI
that minimizes RSI range overlap between adjacent cells. The RSI auto-
configuration function operates based on the distances from newly added cell to
other currently operating cells that use the same EMS. The nearby cells are
selected as the virtual neighbor and the used RSI set is calculated as the union of
the RSIs used by the virtual neighbors. RSI is allocated by selecting an available
RSI range among RSIs in the whole RSI pool excluding the used RSI set.
Figure below depicts Used RSI set configuration.

Confidential
Chapter 9 SON
RSI auto configuration involves the following operation.

1 The operator inputs the parameters related to RO of the SON Property
window of EMS.
2 When installing a cell, EMS receives the latitude and longitude coordinates of
the installed cell through the operator or GPS.
3 The distances to the currently operating cells that use the same carrier among
the cells within the already input NRT distance threshold are calculated, and
in order of proximity, the “NRT Size” numbers of cells are selected to
configure the virtual NRT.
4 Used RSI set is configured by collecting RSIs that are used by cells in virtual
NRT.
5 An available RSI set is configured in the whole RSI pool by excluding the
used RSI set.
6 RSI is allocated by selecting an allocable RSI range (consecutive RSIs)
among the available RSI set. The property of cyclic use of RSI (for example,
minimum value of RSI is consecutively allocated after allocating maximum
value of RSI) is considered in allocating consecutive RSIs as defined in 3GPP
TS 35.211. In selecting an allocable RSI range, if there is no consecutive RSI
among the available RSI set, eNB includes RSI range which is used in the
farthest cell into the available RSI set, and allocates RSI by selecting an
allocable RSI range among the available RSI set. The eNB repeats step 6
until an RSI can be allocated to the added cell.
As mentioned in document, each cell should use continuous 64 PRACH
preambles.
PRACH preamble can be reused based on the cyclic shift value which defined
3GPP 36.211 as below.
Table below outlines NCS for preamble generation (preamble formats 0-3).

Confidential
Chapter 9 SON
ZeroCorrelationZoneConfig NCS value

Unrestricted set Restricted set
0 0 15
1 13 18
2 15 22
3 18 26
4 22 32
5 26 38
6 32 46
7 38 55
8 46 68
9 59 82
10 76 100
11 93 128
12 119 158
13 167 202
14 279 237
15 419 -
Table below outlines NCS for preamble generation (preamble format 4).
zeroCorrelationZoneConfig NCS value
0 2
1 4
2 6
3 8
4 10
5 12
6 15
7 N/A
8 N/A
9 N/A
10 N/A
11 N/A
12 N/A
13 N/A
14 N/A
15 N/A
Preamble format 4 can only be used in some TDD configurations where RACH
preamble can be sent in place of UpPTS.
NCS represents the number of cyclic shift

Confidential
Chapter 9 SON
If high speed flag (Boolean) is set to 0, then use Unrestricted set. If high speed flag
(Boolean) is set to 1, then use Restricted set.
The number of usable preambles that can be generated based on one RSI is
calculated as Floor (length of a root sequence / NCS). The number of RSIs required
for each cell is calculated as Ceil (the number of preambles required per cell/the
number of reusable preambles). Length of a root sequence is 839 for preamble
format 0~3, and 139 for preamble format 4.
For example, assume that preamble format = 0, ZCZC = 9, high speed flag = 0.
Then, NCS = 59, and the number of usable preamble generated with one root
sequence is calculated as Floor (838/59) = 14. That means one RSI can be reused
for 14 times. As mentioned above one cell needs to have 64 continuous preambles.
So, the number of required RSI for one cell is calculated as Ceil (64/14) = 5.
Therefore, 5 RSIs are required for one cell.
PRACH Position Allocation
In LTE system, time/frequency domain resources used for PRACH preamble
transmission are as follows:
• Time resource: 1~3 subframe of UL frame, position of time domain is
determined according to PRACH Configuration Index.
• Frequency resource: 6 RBs are occupied, position of frequency domain is
determined according to PRACH Frequency Offset.
In heterogeneous network environment, RACH interference between high capacity
(Macro) cell and small capacity (Indoor Pico, Femto) cell can be occur whenever
the same PRACH resource is used in those cells. To avoid the interference, in
Samsung RACH Optimization, different RACH resources are allocated according
to eNB Type.
eNB Type PRACH position in frequency domain
MACRO including OUTDOOR PICO LOW
FEMTO including INDOOR PICO HIGH
Figure below depicts PRACH separation on heterogeneous LTE network (FD-LTE

case).

Confidential
Chapter 9 SON
Self-Optimization
The self-optimization function of Samsung RACH Optimization is divided into the
event triggering operation and the periodic operation that is based on the statistics
information collected during operation. The event triggering RO operation
(RSI_CONFLICT_ENABLE, command: CHG-SONFN-CELL) performs required
operations when one of the following events is occurred during network operation:
i) neighbor relation change, ii) change in RSI of neighbor cell, iii) activation of
RSI collision detection and RSI reallocation function (from "Off" to "On"). The
statistics based periodic RO operation (RACH_OPT_ENABLE, command: CHG-
SONFN-CELL) controls PRACH InitialReceivedTargetPower, power ramping
step, the number of dedicated preambles, PRACH Configuration Index, and
backoff indicator according to periodically obtained RACH-related statistics.
RSI conflict Detection and Reallocation
RSI Collision Detection
RSI collision refers to a situation where two cells in neighbor relation use the same
carrier and RSI. In this case, as the UE of the two cells selects one preamble in an
overlapping RSI range and then transmits the PRACH preamble to attempt the
initial connection to the network, the probability of contention increases.
Therefore, RSI collision can degrade the performance of the initial network access
of UEs. The RSI collision detection function is performed by the SON Agent of
the eNB if RSI collision detection and reallocation function is activated. The RSI
collision detection function is performed for the following cases:
• For the case of two cells with inter-eNB neighbor relation: The function
operates when cell configuration change message is received through X2
interface.
• For the case of Intra-eNB neighbor cell: The function operates when eNB
Configuration update of itself is performed.
The SON Agent reports the occurrence of RSI collision to the SON Manager of
EMS when RSI collision is detected.
RSI Reallocation
The SON Manager of EMS receives RSI collision reports and selects target cells
for RSI reallocation. The selection procedure is as follows:
• Case 1
In case that the function is already activated, the cell which reports RSI
collision is selected as the RSI reallocation cell if the two cells involved in RSI
collision are managed by the same EMS. If not, the cell with higher ECI is
selected as the RSI reallocation cell.
• Case 2
In case that the status of RSI collision detection and reallocation function for a
cell is changed from inactive (off) to active (on) and RSI collision is detected
by the cell, the cell is selected as RSI reallocation cell.
Then SON Manager in EMS requests the selected cell to report the neighbor
relation list. Meanwhile, for (Case 1), EMS transmits a RSI Reallocation Timer
triggering message to the other cell involved in RSI collision. The cell receiving
Confidential
Chapter 9 SON
the message runs RSI Reallocation Timer. The value of RSI Reallocation Timer is
determined by TH_RSI_REALLOCATE_LATENCY (CHG-SON-RO). If the
timer is expired, the cell considers that the RSI reallocation is failed and requests
EMS to reallocate a new RSI. At this point, if X2 message with changed RSI
information is received from the other cell after the RSI Reallocation Timer
started, the timer is stopped. For (Case 2), the operation related to RSI
Reallocation Timer is not performed.
The cell that received the NR list request transmits the NR list to EMS. Then, EMS
configures used RSI set by collecting RSIs used by neighbor cells in the NR list.
Using the used RSI set, EMS finds a new RSI in the same way for the self-
configuration procedure. If no RSI for reallocation is available, EMS does not
reallocate RSI.
If operation mode of RSI conflict detection/reallocation is set to Auto
(RSI_CONFLICT_ENABLE = "Auto") for the RSI reallocation cell, the above
procedure and application of the new RSI value are performed automatically. On
the other hand, if the Manual option is set (RSI_CONFLICT_ENABLE =
"Manual") for the RSI reallocation cell, EMS notifies operator about the
occurrence of RSI collision and necessity of new RSI calculation/apply when EMS
receives RSI collision report and selects the RSI reallocation cell. If operator
confirms, EMS calculates and reallocates a new RSI to the RSI reallocation cell as
in above procedure.
Figure below depicts RSI collision in event triggering RO.
Periodic RACH Optimization

There are two aspects of RACH optimization-(1) optimization of the number of
dedicated preambles and (2) optimization of PRACH Parameters including Initial
ReceivedTargetPower, power ramping step, PRACH Configuration Index, and
backoff indicator. The following figure shows the procedure of RACH
optimization.
Figure below depicts Periodic RACH optimization.

Confidential
Chapter 9 SON
The terms used in the figure above are defined as follows:

• Dedi_Pre_Fail_Ratio_Increase: Average of the dedicated preamble assignment
failure ratios higher than the predefined threshold DEDICATED_INCREASE
(CHG-SON-RO) for each hour.
Dedicated preamble assignment failure ratio = (the number of dedicated preamble

assignment failures during 15 min interval) over (the number of HO preparation
counts during 15 min interval)
• Dedi_Pre_Fail_Ratio_Decrease: Average of the dedicated preamble

assignment failure ratios higher than the predefined threshold
DEDICATED_DECREASE (CHG-SON-RO) for each hour.
• Avg_Pre_Sent_Num_Increase: The fraction of UE Information Response
messages having the value of the field numberOfPreamblesSent higher than
the predefined POWER_INCREASE (CHG-SON-RO) for each hour.
• Avg_Pre_Sent_Num_Decrease: The fraction of UE Information Response
messages having the value of the field numberOfPreamblesSent higher than
the predefined POWER_DECREASE (CHG-SON-RO) for each hour.
• Det_Cont_Ratio_Increase: The fraction of contention detection ratios larger
than CONTENTION_INCREASE (CHG-SON-RO) among contention
detection ratios collected during each hour.
Contention detection ratio = (the number of UE Information messages with

contentionDetected = True during 15 min interval) over (the number of received
UE Information messages during 15 min interval)

Confidential
Chapter 9 SON
• Det_Cont_Ratio_Decrease: The fraction of contention detection ratios larger

than CONTENTION_DECREASE (CHG-SON-RO) among contention
Dedicated Preamble vs. Contention Preamble Adjustment
In LTE, preambles in each cell are divided into two categories of preambles as
follows:
• Random Access Preamble: Preambles used for contention based random
access (RRC Idle to RRC Connected, UL data transfer requiring
synchronization, RRC Connection Reestablishment).
• Dedicated Preamble: Preambles used for non-contention based random access
(HO, DL data available requiring synchronization.
Since total number of available preambles in each cell is limited (64), an optimal
number of dedicated preambles should be determined considering tradeoff
between new subscriber accessibility (contention based random access) and HO
latency (non-contention based random access).
For the purpose, RO control function controls the number of dedicated preamble
dynamically. For example-in a lightly loaded cell with low mobility activity, RO
control function will split the available preambles to allow for more contention
preambles. In a cell with lot of mobility activity and near-capacity user count, RO
control function will split the available preambles to have more dedicated
preambles.
The following figure shows the general flow of contention vs. dedicated preamble
split.
RO statistics management keeps statistics of dedicated preamble usage and

computes a probability of dedicated preamble assignment failure
(Dedi_Pre_Fail_Ratio_Increase and Dedi_Pre_Fail_Ratio_Decrease) based on
DedicatedPreambles- AssignFail OM. Based on Dedi_Pre_Fail_Ratio_Increase
and Dedi_Pre_Fail_Ratio_Decrease, at every RACH optimization period, the eNB
determines whether to increase/decrease the number of dedicated preambles as
follows:
• The number of dedicated preambles is increased by a step (step size = 4) if
Dedi_Pre_Fail_Ratio_Increase is larger than
PROB_DEDICATED_INCREASE (CHG-SON-RO).
• The number of dedicated preambles is decreased by a step (step size =4) if
Dedi_Pre_Fail_Ratio_Decrease is smaller than
PROB_DEDICATED_DECREASE (CHG-SON-RO).
Confidential
Chapter 9 SON
• Otherwise, the eNB determines whether to change PRACH parameters (Initial

Received Target Power, Power Ramping Step, PRACH Configuration Index,
and Backoff Indicator).
Figure below depicts Dedicated vs. common preamble split procedure.
Adjustment of PRACH Configuration Index and Power related Parameters

According to the 3GPP specification, several configuration parameters related to
the configuration of PRACH channel are signaled via
SystemInformationBlockType2. Among the configuration parameters in SIB2,
Periodic RACH Optimization automatically adjusts following parameters.
Table below outlines Configuration parameters.
Parameter Description Allowed Values
powerRampingStep (dB) Specifying power ramping steps 0, 2, 4, 6
for PRACH preamble transmit
power when preamble
transmission counter increases.
preambleInitialReceivedTargetPow Specifying the initial target -120, -118, -116, -114, -112, -110,
er (dBm) receiving power of PRACH -108, -106, -104, -102, -100, -98, -
preambles. 96, -94, -92, -90
prachConfigIndex Specifying the PRACH preamble Refer to Tables below
format, subframe sent by
preamble, and interval.
Since PRACH is a common uplink control channel, it is wasteful to allocate

RACH region in all sub-frames. The eNB can choose to declare the location of
subframe and the periodicity of PRACH based on prachConfigIndex. The
following figure shows the mapping of prachConfigIndex to physical location of
PRACH region.
Table below outlines PrachConfigIndex to RACH region mapping (FDD).

Confidential
Chapter 9 SON
Table below outlines PrachConfigIndex to RACH region mapping (TDD).

Confidential
Chapter 9 SON

Confidential
Chapter 9 SON
Note that configuring PRACH Configuration Index (PRACH_CONFIG_INDEX

command: CHG-PRACH-CONF) implicitly configures the preamble format to be
used. Also, RACH Optimization will not modify PRACH Configuration Index in
such a way as to change the preamble format that was initially configured by the
operator (that is, that is, PRACH Configuration Index can be adapted within the
scope of the configured preamble format (via the initially configured PRACH
Configuration Index)
The eNB performs statistical analysis of RACH related OMs and optimizes RACH
configuration based on performance. The following figure gives an overview of
optimization algorithm.
Figure below depicts RACH optimization for PRACH configuration.
Whenever UE succeeds in achieving RACH access, eNB transmits UE

Information Request message with "rach-ReportReq = True" to the UE. Then, UE
transmits UE Information Response message including the number of preambles
sent for successful RACH access (numberOfPreamblesSent) and the indicator
whether the UE has experienced contention during RACH access
(contentionDetected). Upon receiving the UE Information Response message, RO
statistic management in eNB collects RACH related statistics on
numberOfPreamblesSent and contentionDetected.
At every RACH Optimization period, if the number of dedicated preambles is not
changed, eNB optimizes Initial Received Target Power, Power Ramping Step, and
PRACH Configuration Index as follows:
1 If Avg_Pre_Sent_Num_Increase is larger than PROB_POWER_INCREASE
(CHG-SON-RO), eNB checks Det_Cont_Ratio_Increase.
a If Det_Cont_Ratio_Increase is larger than
PROB_CONTENTION_INCREASE (CHG-SON-RO), the eNB inform
EMS that random access opportunity should be increased. Then, EMS
adjusts PRACH Configuration Index of the cell in a way to increase
random access opportunity considering neighboring cells.
[This is a scenario where UEs are not able to capture PRACH channel due
to less opportunities, which is causing a lot of preamble collision.]
b If Det_Cont_Ratio_Increase is smaller than
PROB_CONTENTION_INCREASE (CHG-SON-RO), eNB increases
preambleInitialReceivedTargetPower by 1 step (the step size for this

Confidential
Chapter 9 SON
increase is 2 dB) to make UEs to transmit preambles with higher Tx

power. If preambleInitialReceivedTargetPower is larger than
preambleInitialReceivedTargetPower_max, power ramping step (indicated
by the parameter POWER_RAMPING_STEP (CHG-RACH-CONF)) is
increased by 1 step (the step size for this increase is 2 dB) instead of
preambleInitialReceivedTargetPower.
[This is a scenario where UEs are not able to capture PRACH channel due
to inadequate preamble power and thus take more retries.]
2 If Avg_Pre_Sent_Num_Decrease and Det_Cont_Ratio_Decrease are smaller
than PROB_POWER_DECREASE (CHG-SON-RO) and
PROB_CONTENTION_DECREASE (CHG-SON-RO) respectively, Random
Access Opportunity and Random Access Power are lowered.
a The eNB requests decrease of random access opportunity to EMS. Upon
receiving the request, EMS adjusts PRACH Configuration Index in a way
to decrease random access opportunity.
b The eNB decreases power ramping step by 1 step if current power ramping
step is larger than POWER_RAMPING_STEP_MIN (CHG-SON-RO).
Otherwise, preambleInitialReceivedTargetPower is reduced by 1 step.
Backoff Indicator Adjustment for RACH optimization
Backoff Indicator (BI) is an optional parameters used to adjust preamble
retransmission timing whenever random access of UE is failed. Samsung
implementation modifies the Backoff value only under the limited conditions of
excessive contention and only if PRACH opportunity parameters cannot be
modified any further. Value of BI is defined in 3GPP specification as following
Table.
Table below outlines Backoff Parameter Value.
Index Backoff Parameter value (ms)
0 0
1 10
2 20
3 30
4 40
5 60
6 80
7 120
8 160
9 240
10 320
11 480
12 960
13 Reserved
14 Reserved
15 Reserved

Confidential
Chapter 9 SON
BI is utilized in Random Access as follows. If eNB transmits Random Access

Response (RAR) message with BI = 3 (30 ms), all UEs receiving the RAR
message select random time between 0 and 30 ms and delay preamble
retransmission timing by the randomly selected time if they fail random access.
When BI_OPT_ENABLE (CHG-SONFN-CELL) is set to 1 by operator (this will
automatically reset the value of BACKOFF_INDICATOR (CHG-RACH-CONF) to
0), the eNB performs BI optimization according to the following procedures.
These procedures are executed at RACH optimization period if the number of
dedicated preambles is not changed in the RACH optimization period:
1 If Avg_Preamble_Sent_Num_Increase and Det_Cont_Ratio_Increase are
larger than PROB_POWER_INCREASE (CHG-SON-RO) and
PROB_CONTENTION_INCREASE (CHG-SON-RO) respectively, eNB
determines whether current random access opportunity is currently reached to
maximum or not.
a If random access opportunity can be increased, eNB requests EMS to
increase random access opportunity. Then, EMS adjusts PRACH
Configuration Index to increase random access opportunity.
b If random access opportunity cannot be increased because it already
reached to maximum value, eNB increases BI by BI_SIZE.
c In step B, if the Backoff indicator already reached the maximum allowed
value (BI_Max) then the Backoff indicator is not changed.
2 If Avg_Preamble_Sent_Num_Decrease and Det_Cont_Ratio_Decrease are
smaller than PROB_POWER_DECREASE (CHG-SON-RO) and
PROB_CONTENTION_DECREASE (CHG-SON-RO) respectively, eNB
determines whether current BI is 0 or not.
a If BI is not 0, the eNB reset BI to 0.
b Otherwise, random access opportunity or preamble transmission power
related parameters are reduced.
Fall Back Operation
Periodic RACH optimization supports fall back operation to prevent degradation
of HO and RACH performance. If the function determines that the RACH
performance is degraded after automatic parameter adjustment (Decrease power
and opportunity), related parameters automatically return to the previous values.
The cases where fall back is performed are as follows:
1 If periodic RACH optimization has decreased the number of dedicated
preambles, eNB monitors the HO statistics collected for T_PERIOD_TEMP
(CHG-SON-RO) and calculates Dedi_Pre_Fail_Ratio_Increase based on the
statistics. If Dedi_Pre_Fail_Ratio_Increase is higher than
PROB_DEDICATED_INCREASE (CHG-SON-RO), the function changes
the number of dedicated preambles to the previous value.
2 If periodic RACH optimization has decreased the RACH power related
parameters, that is, power ramping step and initial received target power, or
has reduced RACH resources (PRACH Configuration Index), eNB monitors
Confidential
Chapter 9 SON
the RACH statistics collected for T_PERIOD_TEMP (CHG-SON-RO), and

calculates Avg_Pre_Sent_Num_Increase based on the statistics. If
Avg_Pre_Sent_Num_Increase is higher than PROB_POWER_INCREASE
(CHG-SON-RO), the function changes the adjusted parameters to the
previous values.
SYSTEM OPERATION
How to Activate
Preconditions
• The RACH optimization function is activated in the EMS.
• The UE supports RACH report functionality (that is, UE Information
procedure). The X2 messages include PRACH Configuration information.
• BACKOFF_INDICATOR_SETUP should be set to Setup for performing
Backoff Indicator Optimization by running CHG-RACH-CONF.
• Run CHG-SONFN-CELL and set RACH_OPT_ENABLE to Auto or Manual
to activate RACH optimization feature.
• Run CHG-SONFN-CELL and set RSI_CONFLICT_ENABLE to Auto or
Manual to activate RS conflict detection and RSI reallocation feature.
1 For RACH optimization, the eNB requests RACH report information to the
UE that is connected to the serving (that is, Attach or Idle-to-Active cases) or
target cell (for example, Handover case).
2 The eNB successfully performs UE Information procedure with the UE and
then controls related counters using received RACH report information.
3 For RS collision detection and RSI reallocation, the eNB monitors the X2
Setup Request, X2 Setup Response and X2 eNB Configuration Update
messages.
4 The eNB checks if RS collision occurs using the received RACH
configuration information.
5 If RS collision is detected, the eNB reports RS conflict message to the EMS.
6 If new RSI is reallocated from the EMS, the eNB adapts new RSI value to the
system.
Confidential
Chapter 9 SON
• Run CHG-SONFN-CELL and set RACH_OPT_ENABLE to Off to deactivate

RACH optimization feature.
• Run CHG-SONFN-CELL and set BI_OPT_ENABLE to Off to deactivate
Backoff Indicator optimization.
• Run CHG-SONFN-CELL and set RSI_CONFLICT_ENABLE to Off to
deactivate RS collision detection and RSI reallocation feature.
Key Parameters
parameters.
The operator can set the operation mode of the Samsung RACH Optimization
function to activate/deactivate the mode through the following commands and
parameter.
RACH_OPT_ENABLE This parameter indicates whether to enable the Rach Optimized function (one
of the SON functions).
• Off: The function is turned off.
• Manual: When the parameter value is changed by an algorithm, this
change is applied after confirmation of operator.
• Auto: When the parameter value is changed by an algorithm, this change is
applied automatically.
BI_OPT_ENABLE The parameter is used to control the Backoff Indicator Optimization operation
in two modes.
• Off: BI Optimization is disabled.
• On: BI Optimization is enabled.
RSI_CONFLICT_ENABLE This parameter indicates whether to enable RootSequenceIndex (RSI) SON
function (one of the SON functions).
• Manual: When RootSequenceIndex is conflicted in a certain cell, Conflict
Detection and resolve is done after confirmation of operator.
• Auto: When RootSequenceIndex is conflicted in a certain cell, Conflict
Detection is done automatically.
parameters.
Table below outlines SON property for RSI auto-configuration in LSM.
R Count Number of Cell to use for calculating average of NRT, PCI, RSI.
RSI Type Criteria of the effective radius when allocating RSI. Can set to minimum,
average or distance.

Confidential
Chapter 9 SON
• minimum: using R as distance with nearest neighbor cell.
• distance: criteria of fixed distance.
• average: use of R multiplied by RSI Multiple as effective radius where R is
the distance obtained by averaging the inter-site distance with the neighbor
cells in the nearest order (The number of neighbor cells is R Count).
RSI Multiplication Factor Expansion range of calculating the effective distance when allocating RSI.
RSI Distance Limit Minimum of the effective radius when allocating RSI.
Parameter Descriptions of CHG-SON-RO/RTRV-SON-RO

T_PERIOD The period of statistics monitoring. This value (1Day/1Week/1Month,
default=1Month) is used for triggering the RACH parameter control.
• one_day: RO is triggered based on handover statistics collected for 1 day.
• one_week: RO is triggered based on handover statistics collected for 1
week.
• one_month: RO is triggered based on handover statistics collected for 1
month.
T_PERIOD_TEMP The period of fallback statistics monitoring. This value (1Hour/1Day/1Week,
default=1Week) is used for checking a fault where RACH performance is not
temporarily met after the RACH parameter is changed.
• one_hour: Fallback for RO based on the handover statistics collected for 1
hour.
• one_day: Fallback for RO based on the handover statistics collected for 1
day.
• one_week: Fallback for RO based on the handover statistics collected for 1
week.
RACH_FILTERING_COEFF The coefficient applied to filtering when processing RACH statistics data.
F (n) = (1-rachFilteringCoeff) x F (n-1) + rachFilteringCoeff x CurrentValue
DEDICATED_INCREASE The threshold that increases the number of dedicated preambles.
DEDICATED_DECREASE The threshold that decreases the number of dedicated preambles.
PROB_DEDICATED_INCREA The probability that increases the number of dedicated preambles.
SE
PROB_DEDICATED_DECRE The probability that decreases the number of dedicated preambles.
ASE
DEDICATED_MAX The maximum value of the number of dedicated preambles.
{n0, n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60}
DEDICATED_MIN The minimum value of the number of dedicated preambles.
{n0, n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60}
POWER_INCREASE The threshold that increases preamble Tx-related power resources.
POWER_DECREASE The threshold that decreases preamble Tx-related power resources.
PROB_POWER_INCREASE The probability that increases preamble Tx-related power resources.
PROB_POWER_DECREASE The probability that decreases preamble Tx-related power resources.
PREAMBLE_INITIAL_RECEI The maximum value of initial received target power.
VE_TARGET_POWER_MAX {dBm-120, dBm-118, dBm-116, dBm-114, dBm-112, dBm-110, dBm-108,
dBm-106, dBm-104, dBm-102, dBm-100, dBm-98, dBm-96, dBm-94, dBm-
92, dBm-90}
PREAMBLE_INITIAL_ The minimum value of initial received target power.

Confidential
Chapter 9 SON
RECEIVED_TARGET_POWE {dBm-120, dBm-118, dBm-116, dBm-114, dBm-112, dBm-110, dBm-108,
R_MIN dBm-106, dBm-104, dBm-102, dBm-100, dBm-98, dBm-96, dBm-94, dBm-
92, dBm-90}
POWER_RAMPING_STEP_M The maximum value of ramping step. {dB0, dB2, dB4, dB6}
AX
POWER_RAMPING_STEP_M The minimum value of ramping step. {dB0, dB2, dB4, dB6}
IN
CONTENTION_INCREASE The threshold that increases PRACH configuration index.
CONTENTION_DECREASE The threshold that decreases PRACH configuration index.
PROB_CONTENTION_INCR The probability that increases PRACH configuration index.
EASE
PROB_CONTENTION_DECR The probability that decreases PRACH configuration index.
EASE
TH_RSI_CONFLICT_REPOR This parameter represents the RSI conflict report holding time when an RSI
T_HOLD conflict event was already issued. The eNB starts the RSI conflict report
holding timer with this parameter value after a notify specific RSI conflict
event to the LSM. While this timer is running, the same RSI conflict event is
not reported to the LSM. New RSI conflict reports are stored and a
notification to the LSM is sent after the RSI conflict report holding timer
expires (unit: seconds).
TH_RSI_REALLOCATE_LAT This parameter represents the waiting time for RSI reallocation request. The
ENCY eNB receives an XCHG-RSI-TIMER command from the LSM and starts the
RSI reallocation timer using this parameter value. The timer is stopped when
the RSI reallocation accomplishes within the waiting time. However, if the RSI
reallocation is not performed within the waiting time and the timer expires,
then the eNB will send an RSI reallocation request message (SON RSI
REALLOC TIMEOUT) to the LSM (unit: minutes).
BI_SIZE Step size for BI increase. Its value means the number of index increased
when BI optimization algorithm decides to increase BI.
Ex) If BI_SIZE = 2, BI value is changed from 0ms (0) to 20 ms (2), from 10ms
(1) to 30 ms (3), and so on.
BI_MAX Maximum value of BI that can be adjusted by BI optimization.
Parameter Descriptions of CHG-PRACH-CONF/RTRV-PRACH-CONF

PRACH_CONFIG_INDEX Index for the preamble format, subframe sent by preamble, and interval.
ROOT_SEQUENCE_INDEX The first logical root sequence index used to create a random preamble.
Different values should be assigned to neighboring cells. Be cautious to
change because it cause inter-cell interference among the cells with same
physical root sequence. Please refer to the SON Algorithm for changing this
parameter because it affects the entire system.
PRACH_POSITION Provides information about PRACH position between two possible positions
adjacent to PUCCH.
• 0: low position
• 1: high position

Confidential
Chapter 9 SON
Parameter Descriptions of CHG-RACH-CONF/RTRV-RACH-CONF

SIZE_OF_RA_PREAMBLES_ This parameter is the number of preambles group A.
GROUP_A
POWER_RAMPING_STEP This parameter specifies the power ramping steps for preamble transmit
power when preamble transmission counter increases.
PREAMBLE_INIT_RCV_TAR This parameter specifies the initial target receiving power of preambles.
GET_POWER Value dBm-120 correspond to-120 dBm and so on.
BACKOFF_INDICATOR_SET This parameter setup or release the backoff indicator.
UP • Release: release.
• Setup: setup.
BACKOFF_INDICATOR This parameter specifies the backoff value.
Counters and KPIs

Random Access Preambles DedicatedPreambles The cumulated number of dedicated
preambles among the periodically
collected RACH preambles.
DedicatedPreamblesAssignFail The number of failures to get dedicated
preamble allocation after requesting the
dedicated preamble from the RRC to the
MAC.
RandomlySelectedPreamblesLow The cumulated number of the preambles
belonging to Group A among the
detected contention based preambles.
RandomlySelectedPreamblesHigh The cumulated number of the preambles
belonging to Group B among the
detected contention based preambles.
RACHUsageAvg The average of RACH usage rates that
were collected during the collection
interval.
HandoverDedicatedPreambles The cumulated number of dedicated
preambles due to Handover order
among the periodically collected RACH
preambles.
RandomAccessResponses The cumulated number of
RandomAccessResponse (RAR)
messages are transmitted. For this
counter, the statistics are collected
periodically.
RACH Usage PreambleSent1 Count when the number of RACH
preamble sent is 1.
PreambleSent2 Count when the number of RACH
preamble sent is 2.
Preamblesent3 Count when the number of RACH
preamble sent is 3.
preamble sent is 4.

Confidential
Chapter 9 SON

preamble sent is 5.
preamble sent is 6.
preamble sent is 7
preamble sent is 8
preamble sent is 9
RACHContention Ratio of RACH contention occurrence.
RACHReportsRcvNum Count when rachReport is received.
REFERENCE
[4] 3GPP 32.500: E-UTRAN; Self-Organizing Networks (SON); Concepts and
requirements
[5] 3GPP 32.501: E-UTRAN; Self-configuration of network elements; Concepts
and requirements
(IS)
[8] 3GPP 32.541: E-UTRAN; Self-Organizing Networks (SON); Self-healing
concepts and requirements

Confidential
Chapter 9 SON
LTE-SO0402, NB-IoT RACH Optimization

INTRODUCTION
In NB-IoT, three coverage classes exist per each cell. Different NPRACH
parameters can be configured for different coverage classes. NPRACH position in
radio resources is defined by NPRACH resource periodicity, NPRACH starting
time, and NPRACH frequency location in subcarrier offset. Note that NPRACH
starting time should be less than NPRACH resource periodicity.
Neighboring NB-IoT cells should use different positions of NPRACH to minimize
RACH performance degradation. For this, the NB-IoT RACH Optimization
feature supports automatic configuration of NPRACH parameters, that is,
NPRACH starting time and NPRACH frequency location in subcarrier offset, for
newly installing NB-IoT cell in a way to avoid overlapping of NPRACH with
neighboring cells.
BENEFIT
• An operator can reduce cost and time for configuring NPRACH parameters in
NB-IoT networks.
• Random access performance of NB-IoT networks can be improved by
avoiding NPRACH resource overlap.
DEPENDENCY
• HW dependency: This feature can be supported for DU types supporting NB-
IoT.
• Related Radio Technology : NB-IoT
• Others: Positioning information of NB-IoT cell should be input, or automatic
position information update function should be turned on.
LIMITATION
The position of NPRACH resources among neighboring cells can be overlapped,
since the number of possible NPRACH resource positions is limited.
SYSTEM IMPACT
capabilities.
None
NPRACH Parameter Optimization function can reduce RACH access delay and

Confidential
Chapter 9 SON
improve RACH success rate by allocating different NPRACH parameters

Coverage
None
Interfaces
The interface between the eNB and the LSM is affected to support NPRACH
optimization.
FEATURE DESCRIPTION
In the NB-IoT network, to improve the performance of the RACH connection of
the UE, adjacent cells must allocate NPRACH (NB-IoT Physical Random Access
Channel) to different radio resource locations.
For this, the NB-IoT RACH Optimization feature supports an initial NPRACH
parameter (nprach-StartTime, nprach-SubcarrierOffset) auto-allocation operation.
NPRACH Parameter Auto-configuration

The NPRACH parameter combination (nprach-StartTime, nprach-
SubcarrierOffset) is automatically configured for newly installing NB-IoT cell.
The function is performed by LSM and operates based on the distance between
NB-IoT cells.
Figure below depicts auto configuration procedure of NPRACH parameter.

Confidential
Chapter 9 SON
Figure 1. Samsung NPRACH Parameter Auto-configuration Procedure and Architecture
SYSTEM OPERATION
How to Activate
Preconditions
Ensure that the following conditions are met before enabling this feature.
• ADV_INDOOR_DIST should be selected.
• LCC should be selected.
• LTE cell should have the frequency and bandwidth that can be added NB-IoT
cell.
To activate this feature through LSM, do the following.
1 Open Configure | Create eNB | Step 2 or Configure | Cell Management
window.
2 Add new cell under preconditions.
3 Change Status of NB-IoT cell to EQUIP.
4 Change Initial NPRACH to ON.
Confidential
Chapter 9 SON
To deactivate this feature through LSM, do the following:
1 Open Configure | Create eNB | Step 2 or Configure | Cell Management
window.
2 Add new cell under preconditions.
3 Change Status of NB-IoT cell to EQUIP.
4 Change Initial NPRACH to OFF.
5 Input NPRACH parameters by manual.
Key Parameters
Parameter Descriptions
If ON, then NPRACH parameters will be filled by SON algorithm.
Initial NPRACH
If OFF, then NPRACH parameters should be filled by user.
Parameter Descriptions
NPrachStartTimeCL1 NPrach start time for Coverage Level 1.
NPrachSubCarrierOffsetCL1 NPrach subcarrier offset for Coverage Level 1.
REFERENCE
specification
[3] 3GPP 36.211: E-UTRA; Physical channels and modulation
[5] 3GPP 32.500: E-UTRAN; Self-Organizing Networks (SON); Concepts and
requirements
[6] 3GPP 32.501: E-UTRAN; Self-configuration of network elements; Concepts
and requirements

Confidential
Chapter 9 SON

(IS)

Confidential
Chapter 9 SON
LTE-SO0403, eMTC RACH Optimization

INTRODUCTION
Random Access Channel (RACH) of an LTE system is the uplink channel defined
in the 3GPP specifications. For eMTC UEs, the same signals and channels are
used for random access as a legacy LTE. However, different RACH parameters
can be used for eMTC UEs. The eMTC RACH Optimization feature minimizes
eMTC UE access delay and improves RACH success rate of eMTC UE by
optimizing eMTC RACH resources. The feature optimizes the eMTC PRACH
parameters such as Preamble Initial Received Target Power, Power Ramping Step
and Backoff Indicator.
BENEFIT
• This feature can reduce CAPEX and OPEX cost for configuring and managing
the PRACH parameters for the eMTC UE.
• This feature can minimize UE access delay by optimizing RACH attempt rate
and initial received target power.
DEPENDENCY
• Related Radio Technology: E-UTRAN(LTE)
• Others: Application of the eMTC RACH optimization needs 3GPP Rel.13
eMTC UE support including rach-report in UE information message.
LIMITATION
None
SYSTEM IMPACT
None
This feature reduces random access delay of eMTC UE and improves eMTC
RACH success rate by adjusting eMTC RACH parameters based on eMTC RACH
statistics.
Coverage
If eMTC UEs fail random access due to low preamble transmission power, this
feature adjusts preamble transmission power for random access. This can improve
random accesses performance of the eMTC UEs in cell edge area.
Interfaces
None

Confidential
Chapter 9 SON
FEATURE DESCRIPTION
If many eMTC UEs attempt to access the network, random access performance
can be degraded due to RACH preamble collision. When an eMTC UE in poor
coverage condition tries to access the network with low transmission power, the
UE may fail to access the network. The eMTC RACH Optimization (RO) feature
optimizes the eMTC PRACH parameters such as Preamble Initial Received Target
Power, Power Ramping Step, and Backoff Indicator (BI) to improve random
access performance degraded due to the above reasons.
eMTC RACH Optimization Procedure

This feature adjusts of power related parameters (Preamble Initial Received Target
Power and Power Ramping Step) and Backoff Indicator based on eMTC RACH
statistics.
Figure below depicts the eMTC RACH optimization procedure.

Confidential
Chapter 9 SON
The terms indicated in the figure above are defined as follows:

• Avg_Pre_Sent_Num_Increase: The fraction of UE Information Response
messages with the value of the field numberOfPreamblesSent higher than the
predefined BR_POWER_INCREASE (CHG-SON-RO) for each hour.
• Avg_Pre_Sent_Num_Decrease: The fraction of UE Information Response
messages with the value of the field numberOfPreamblesSent higher than the
predefined BR_POWER_DECREASE (CHG-SON-RO) for each hour.
• Det_Cont_Ratio_Increase: The fraction of contention detection ratios larger
than BR_CONTENTION_INCREASE (CHG-SON-RO) among contention
Contention detection ratio = (the number of UE Information messages with

contentionDetected = True during 15 min interval) over (the number of received
UE Information messages during 15 min interval))
• Det_Cont_Ratio_Decrease: The fraction of contention detection ratios larger

than BR_CONTENTION_DECREASE (CHG-SON-RO) among contention
Optimization of Power related Parameters and Backoff Indicator

According to the 3GPP specification, several configuration parameters related to
the configuration of PRACH channel are signaled via

Confidential
Chapter 9 SON
SystemInformationBlockType2. Among the configuration parameters in SIB2, this

feature adjusts the following parameters automatically.
Table 1. Configuration Parameters

Parameter Description Allowed Values
powerRampingStep (dB) Specifying power ramping steps for 0, 2, 4, 6
PRACH preamble transmit power
when preamble transmission
counter increases.
preambleInitialReceivedT Specifying the initial target receiving -120, -118, -116, -114, -112, -110, -108, -
argetPower (dBm) power of PRACH preambles. 106, -104, -102, -100, -98, -96, -94, -92, -90
Backoff Indicator (BI) is an optional parameters used to adjust preamble

retransmission timing whenever random access of UE is failed. Samsung
implementation modifies the Backoff value under the conditions of excessive
contention. The value of BI is defined in 3GPP specification as cited in table
below.
Table 2. Backoff Parameter Value

Index Backoff Parameter value (ms)
0 0
1 10
2 20
3 30
4 40
5 60
6 80
7 120
8 160
9 240
10 320
11 480
12 960
13 Reserved
14 Reserved
15 Reserved
BI is used in random access procedure as follows:

If the eNB transmits Random Access Response (RAR) message with BI=3 (30
ms), all UEs receiving the RAR message select random time between 0 and 30 ms
and delay preamble retransmission timing by the randomly selected time if they
fail random access.
The BI optimization function can be enabled or disabled by using the system
parameter (BR_BI_OPT_ENABLE of CHG-SONFN-CELL). If

Confidential
Chapter 9 SON
BR_BI_OPT_ENABLE is set to True, the value of BACKOFF_INDICATOR

(CHG-BRRACH-CONF) is automatically reset to 0.
The eNB performs statistical analysis of eMTC RACH related OMs and optimizes
eMTC RACH configuration based on performance.
Whenever the UE succeeds in random access, the eNB transmits UE Information
Request message with "rach-ReportReq=True" to the UE.The UE then transmits
the UE Information Response message including the number of preambles sent for
successful RACH access (numberOfPreamblesSent) and the indicator whether the
UE has experienced contention during RACH access (contentionDetected). Upon
receiving the UE Information Response message, eMTC RO statistic management
in eNB collects RACH related statistics on numberOfPreamblesSent and
contentionDetected.
At every eMTC RACH optimization period, the eNB optimizes initial received
target power and power ramping step as follows:
1 If Avg_Pre_Sent_Num_Increase is larger than
BR_PROB_POWER_INCREASE (CHG-SON-RO), the eNB checks
BR_BI_OPT_ENABLE and Det_Cont_Ratio_Increase.
o If "BR_BI_OPT_ENABLE = True (CHG-SONFN-CELL)" and
"Det_Cont_Ratio_Increase is larger than
BR_PROB_CONTENTION_INCREASE (CHG-SON-RO)", the eNB
increases BI by BI_SIZE. If the Backoff Indicator already reached the
maximum allowed value (BI_MAX), then the Backoff Indicator is not
changed. This is a scenario where UEs are not able to capture PRACH
channel due to less opportunities, which is causing a lot of preamble
collision.
o If "BR_BI_OPT_ENABLE = False" or "Det_Cont_Ratio_Increase is
smaller than or equal to BR_PROB_CONTENTION_INCREASE", the
eNB increases preambleInitialReceivedTargetPower by 1 step (the step
size for this increase is 2 dB) to make UEs to transmit preambles with
higher Tx power. If current preambleInitialReceivedTargetPower is equal
to BR_PREAMBLE_INITIAL_RECEIVED_TARGET_POWER_MAX,
power ramping step (indicated by POWER_RAMPING_STEP (CHG-
BRRACH-CONF)) is increased by 1 step (the step size for this increase is 2
dB) instead of increasing preambleInitialReceivedTargetPower. This is a
scenario where UEs are not able to capture PRACH channel due to
inadequate preamble power and thus take more retries.
2 If Avg_Pre_Sent_Num_Decrease and Det_Cont_Ratio_Decrease are smaller
than BR_PROB_POWER_DECREASE (CHG-SON-RO) and
BR_PROB_CONTENTION_DECREASE (CHG-SON-RO) respectively, the
eNB checks BR_BI_OPT_ENABLE and the value of Backoff Indicator.
o If "BR_BI_OPT_ENABLE = True" and "Backoff Indicator ≠ 0”, the eNB
decreases BI by BR_BI_SIZE.
o If "BR_BI_OPT_ENABLE = False" or "Backoff Indicator = 0", the eNB
decreases power ramping step by 1 step. If current power ramping step is
equal to BR_POWER_RAMPING_STEP_MIN (CHG-SON-RO),
preambleInitialReceivedTargetPower is reduced by 1 step instead of
Confidential
Chapter 9 SON
decreasing power ramping step.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-SONFN-CELL/RTRV-SONFN-CELL to enable
BR_RACH_OPT_ENABLE to AutoMode, and to control Backoff Indicator,
set BR_BI_OPT_ENABLE to ON.
To deactivate this feature,
• Set BR_RACH_OPT_ENABLE and BR_BI_OPT_ENABLE to OFF.
Key Parameters
parameters.
BR_RACH_OPT_ENABLE This parameter indicates whether to enable the eMTC RACH Optimization
function.
BR_BI_OPT_ENABLE The parameter is used to control the Backoff Indicator Optimization
operation.
parameters.
Parameter Descriptions of CHG-SON-RO/RTRV-SON-RO
BR_POWER_INCREASE The threshold that increases eMTC preamble Tx-related power resources
BR_POWER_DECREASE The threshold that decreases eMTC preamble Tx-related power resources.
BR_PROB_POWER_INCREAS The probability that increases eMTC preamble Tx-related power resources.
E

Confidential
Chapter 9 SON
BR_PROB_POWER_DECREAS The probability that decreases eMTC preamble Tx-related power resources.
E
BR_PREAMBLE_INITIAL_REC The maximum value of initial received target power for eMTC.
EIVED_TARGET_POWER_MA
X
BR_PREAMBLE_INITIAL_REC The minimum value of initial received target power for eMTC.
EIVED_TARGET_POWER_MIN
BR_POWER_RAMPING_STEP The maximum value of ramping step for eMTC.
_MAX
BR_POWER_RAMPING_STEP The minimum value of ramping step for eMTC.
_MIN
BR_CONTENTION_INCREASE The threshold that increases eMTC RACH opportunity.
BR_CONTENTION_DECREAS The threshold that decreases eMTC RACH opportunity.
E
BR_PROB_CONTENTION_INC The probability that increases eMTC RACH opportunity.
REASE
BR_PROB_CONTENTION_DE The probability that decreases eMTC RACH opportunity.
CREASE
BR_BI_SIZE Step size for eMTC BI increase. Its value means the number of index
increased when BI optimization algorithm decides to increase BI.
BR_BI_MAX Maximum value of eMTC BI that can be adjusted by BI optimization.
Counters and KPIs

with this feature.
REFERENCE
specification
[3] 3GPP TR 36.902: E-UTRAN; Self-configuring and self-optimizing network
(SON) use cases and solutions
[4] 3GPP TS 32.500: E-UTRAN; Self-Organizing Networks (SON); Concepts and
requirements
[5] 3GPP TS 32.501: E-UTRAN; Self-configuration of network elements;
Concepts and requirements
[6] 3GPP TS 36.211: E-UTRA; Physical Channels and Modulation
[7] 3GPP TS 36.321: E-UTRAN; Medium Access Control (MAC) protocol
specification

Confidential
Chapter 9 SON
LTE-SO0501, Intra-LTE MRO

INTRODUCTION
Samsung MRO automatically optimizes the HO performance during system
operation, to improve HO success rate and to reduce ping-pong HO. Samsung
MRO is triggered at regular intervals and controls HO parameters based on the HO
statistics collected during the interval. The HO-related statistics used by Samsung
MRO include all the HO-related problems specified in 3GPP standard (Too-late
HO/Too-early HO/HO to Wrong Cell). RLF Indication messages and Handover
Report messages delivered through X2 interface are used to collect statistics on the
above problems. For this operation, eNB saves the information about served cells
of neighbor eNB which is included in X2 Setup Request/Response and eNB
Configuration Update messages. The eNB uses this information to transmit RLF
Indication and Handover Report messages. Samsung MRO algorithm defines
separate HO success rate for MRO by using HO and MRO statistics. Moreover, it
is used for determining the following:
• Whether it is needed to change HO parameters by using the HO success rate
for MRO;
• Whether the HO related problem was resolved by CIO adjustment by MRO
algorithm.
The HO-related problems based on the 3GPP Release 9 standard are collected
through the RRC connection reestablishment request message. This message is
transmitted to the target cell for re-establishment which is decided through cell
search process when the UE fails the HO operation or experiences RLF within a
short time during the HO operation or after the completion. After a UE
experiences above-mentioned problem, the 3GPP Release 10 standard provides the
method that may collect the HO-related problems even at the failure in cell search
or in the process of RRC connection reestablishment. If a UE fails in the operation
of RRC connection re-establishment, the UE transits to the RRC_IDLE mode and
performs the RRC connection setup operation to the cell detected through the cell
search process. In this process, the UE reports information on RLF or HO failure
related problem (rlf-report-r9) experienced just before RRC connection setup to
the serving cell through UE information procedure. Then, the serving cell collects
HO-related problem using this information or transmits RLF Indication message
including rlf-report-r9 to RLF source cell of the UE to the source cell can collects
the HO-related problem.
Samsung MRO controls CIO, the HO parameter that changes HO triggering point
at the neighbor cell’s level. If the HO success rate per each neighbor cell satisfies
the KPI, Samsung MRO adjusts the CIO value to reduce the ping-pong HO. If HO
success rate is not satisfied, the function changes the CIO value based on the
tendency of the HO-related problems. It also monitors if the HO or call drop rate
performance is sharply degraded for a certain period after changing the CIO value.
If so, it performs parameter rollback action to return to the previous CIO value.
The A2 event is used to activate measurement gap for inter-frequency
measurement. Thus, Samsung MRO adjusts A2 threshold to optimize performance
of inter-frequency HO by changing the point of measurement for inter-frequency
Confidential
Chapter 9 SON
neighbor cell. MRO algorithm controls the A2 threshold after adjusting CIO value
of each inter-frequency neighbor cell. It also performs parameter rollback action
by monitoring HO and call drop rate after changing A2 threshold value.
BENEFIT
• This feature can reduce CAPEX and OPEX expenses used to enhance HO
performance during the system operation.
• As the optimized HO is performed in consideration of coverage and air status
of each neighbor cell, it provides great user experience through maximum
performance with high HO success rate and low call drop rate. The eNB uses
the RSRP/RSRQ of serving cell and best neighbor cell. The information is
reported by UE and shared between eNBs via X2. If there is no neighbor cell
that has stronger signal strength than the source cell, the algorithm decides that
there is a coverage hole between two cells.
DEPENDENCY
• Interfaces & Protocols: To activate the MRO function, the X2 interface must
be established with neighbor eNBs.
• Others: HO-related problems based on the Release 10 standard may be
collectible only when the UE supports a function of including r10-related
information to the rlf-report-r9 information.
LIMITATION
None
SYSTEM IMPACT
capabilities.
Intra-LTE ANR: Intra-LTE ANR feature optimizes Neighbor Relation Table
(NRT) by automatically adding new neighbor cells based on UE measurement
reports and deleting neighbor cells based on handover statistics.
None
Coverage
Intra-LTE MRO automatically detects handover problem for each neighbor cell
and resolves it by changing handover parameters. This guarantees reliable mobility
of the UEs when the UEs are moving between cells.

Confidential
Chapter 9 SON
Interfaces
To collect handover problems between the cells in different eNBs, eNBs exchange
X2 messages such as RLF Indication and Handover Report.
FEATURE DESCRIPTION
Samsung MRO function works in eNB. Figure below depicts the overall
architecture of the function.
In the above architecture, Samsung MRO function is performed by the SON agent
of eNB and the block operates for each eNB.
The detailed procedures are as follows:
• SON Agent: HO-related problem detection function
a Receives the RLF Indication/Handover Report message from X2.
b Receives UE context from RRC.
c Collects and delivers the statistics on the causes of HO-related problems to
OAM.
• SON Agent: HO parameter control triggering function
a Monitors the result of MRO algorithm.
Confidential
Chapter 9 SON
b Monitors change in HO or call drop rate performance for certain period

after change of CIO and A2 threshold.
c Collects statistics on HO and HO-related problems from OAM.
d Determines whether to change HO parameters.
e Triggers HO parameter control action and delivers the MRO algorithm
input.
• SON Agent: HO parameter control function
a Controls HO parameters to reduce Ping-pong HO.
b Controls HO parameters based on the HO-related problems.
c Provides the changed CIO and A2 threshold to OAM.
MRO Function
Collection of Handover-related Problem Statistics
Collection of HO-related Problem Statistics based on 3GPP Release 9
Specification
In Samsung MRO function, HO-related problems based on the 3GPP Release 9
standard are collected in MRO RLF Classification counter family. 3GPP Release 9
based HO-related problem for VoLTE UE is collected in MRO RLF VOICE
Classification counter family separately from HO-related problem for Data UE,
but CoverageHole and CoverageHoleN statistics are not separated. For eMTC
UEs, 3GPP Release 9 based HO-related problem statistics are not collected.
Samsung MRO excludes the HO-related problem caused by the HO whose
purpose is not coverage based HO. For example, following are excluded from HO-
related problem.
• HO-related problem after performing MLB (Mobility Load Balancing), RLF
Triggered HO, Shutting down with Forced HO, or Cell off with Forced HO
• HO-related problem due to the HO parameter changed by eICIC (enhanced
Inter-Cell Interference Coordination), HetNet Mobility Enhancement, or UE
Level Ping-pong HO Minimization.
Table below outlines HO-related problem classification based on 3GPP Release 9
spec.
Time that RLF Re-establishment cell
occurs
Serving cell Target cell Other Cell
Before HO (2) TooLateHO
(1) CoverageHole N/A
initiation (RLFBeforeTriggering)
After HO (4) TooLateHO (6) HOtoWrongCell,
triggering (3) CoverageHoleN (RLFAfterTriggering) HwcReestablish
(5) CoverageHoleN (RLFAfterTriggering)
During HO (4) TooLateHO (6) HOtoWrongCell,

(7) TooEarlyHO
execution (RLFAfterTriggering) HwcReestablish
(HOFailure)
(5) CoverageHoleN (RLFAfterTriggering)

Confidential
Chapter 9 SON
After HO (8) TooEarlyHO

(10) HOtoWrongCell,
execution (RLFAfterHO)
(9) CoverageHoleN HwcReestablish
(RLFAfterHO)
The details of statistics items mentioned in the above table are as follows:
(1) CoverageHole
1 RLF occurs without any HO initiation in UE.
2 The UE requests for RRC Connection Reestablishment to the serving cell.
3 If there is an RLF report and the coverage hole conditions are satisfied, the
serving cell collects the statistics of CoverageHole.
4 If there is an RLF report and the coverage hole conditions are not satisfied,
the serving cell does not collect the statistics of CoverageHole.
5 If there is no RLF report, the serving cell collects the statistics of
CoverageHole.
(2) TooLateHORLFBeforeTriggering
1 RLF occurs without any HO initiation in UE.
2 The UE requests for RRC Connection Reestablishment to the other cell.
3 The cell transmits the RLF Indication message to the serving cell through the
X2 interface.
4 The serving cell collects the statistics with other cells.
(3) CoverageHoleN
1 The UE transmits the MR message initiated by triggering HO.
serving cell collects the statistics of CoverageHoleN with another cell.
the serving cell does not collect the statistics of CoverageHoleN with another
cell.
CoverageHoleN with another cell.
(4) TooLateHORLFAfterTriggering
2 The UE fails to receive a HO Command message from the service cell, or
fails to perform HO with the target cell after receiving a HO command
message.
3 The UE requests for RRC Connection Reestablishment to the target cell.
4 The UE informs the target cell if it retains information on RLF report during
RRC connection re-establishment procedure with the target cell. (If the UE
retains information on the RLF report, RLF report is provided through the UE
Information procedure.)
Confidential
Chapter 9 SON
5 The target cell transmits the RLF Indication message to the serving cell
through the X2 interface. (This message contains the RLF report if it is
acquired.)
the serving cell collects the statistics of TooLateHORLFAfterTriggering with
the target cell.
TooLateHORLFAfterTriggering with the target cell.
(5) CoverageHoleN
fails to perform HO with the target cell after receiving a HO Command
message.
3 The UE requests for RRC Connection Reestablishment to the target cell.
4 The UE informs the target cell if it retains information on RLF report during
RRC connection re-establishment procedure with the target cell. (If the UE
retains information on the RLF report, RLF report is provided through the UE
Information procedure.)
5 The target cell transmits the RLF Indication message to the serving cell
through the X2 interface. (This message contains the RLF report if it is
acquired.)
serving cell collects the statistics of CoverageHoleN with the target cell.
(6) HOtoWrongCellRLFAfterTriggering, HwcReestablishRLFAfterTriggering
fails to perform HO with the target cell after receiving a HO Command
message.
3 The UE requests for RRC Connection Reestablishment to the other cell, not
to the serving cell or the target cell.
4 The other cell transmits the RLF Indication message to the serving cell
through the X2 interface.
5 The serving cell collects the HOtoWrongCellRLFAfterTriggering statistics
with the target cell.
6 The serving cell collects the HwcReestablishRLFAfterTriggering statistics
with the other cell to which UE perform RRC Connection Reestablishment.
(7) TooEarlyHOHOFailure
2 The UE receives the HO Command message from the serving cell.
3 The UE fails HO with the target cell.

Confidential
Chapter 9 SON

5 The serving cell collects the statistics with the target cell.
(8) TooEarlyHORLFAfterHO
3 The UE successfully performs the HO with the target cell.
4 The UE creates RLF in a short period (Tstore_ue_cntxt).
5 The UE requests for RRC Connection Reestablishment to the previous
serving cell.
6 The serving cell transmits the RLF Indication message to the target cell
7 The target cell transmits the Handover Report message to the serving cell
8 The serving cell collects the statistics with the target cell.
(9) CoverageHoleN
1 The UE transmits the MR message by HO triggering.
4 The UE generates RLF in a short period (Tstore_ue_cntxt).
5 The UE requests for RRC connection reestablishment to the existing target
cell.
target cell collects the statistics of CoverageHoleN with the serving cell.
the target cell does not collect the statistics of CoverageHoleN.
8 If there is no RLF report, the target cell collects the statistics of
CoverageHoleN with the serving cell.
(10) HOtoWrongCellRLFAfterHO, HwcReestablishRLFAfterHO
4 The UE creates RLF in a short period (Tstore_ue_cntxt).
5 The UE requests for RRC Connection Reestablishment to the other cell, not
to the serving cell or the target cell.
6 The other cell transmits the RLF Indication message to the target cell through
the X2 interface.
7 The target cell transmits the Handover Report message to the serving cell
Confidential
Chapter 9 SON
8 The serving cell collects the HOtoWrongCellRLFAfterHO statistics with the

target cell.
9 The serving cell collects the HwcReestablishRLFAfterHO statistics with the
other cell to which UE perform RRC Connection Reestablishment.
Collection of HO-related Problem Statistics based on 3GPP Release 10
Specification
Samsung MRO function collects the HO-related problems based on the 3GPP
Release 10 in MRO RLF at RRC Connection counter family by using the rlf-
report-r9 information acquired through the UE information procedure after the
completion of the RRC connection establishment procedure of the UE. If the UE
experiences RLF or fails the HO operation, it logs the event. If the UE fails in re-
establishing RRC connection, it re-performs the process of RRC connection
establishment to the cell detected by the cell search process after transition to the
RRC_IDLE mode. If the UE sets rlf-InfoAvailable-r10 as true in the RRC
connection setup complete message during the process, the serving cell performs
the UE information procedure to obtain the rlf-report-r9 information of the UE.
The r10-related information added to the existing rlf-report-r9 in the Release 10
standard is as follows:
1 failedPCellId-r10
a If the UE goes through the RLF: ECGI of the serving cell connected at the
time of the generation of the RLF (cellGlobalId-r10)
b If the UE fails the HO operation: pci-arfcn-r10 of the HO target cell
(Information on PCI (physCellId-r10) and frequency (carrierFreq-r10))
2 reestablishmentCellId-r10: ECGI of the cell that transmits the RRC
connection reestablishment request message after the cell search process after
the UE experiences RLF or fails the HO operation
3 timeConnFailure-r10
a If the UE goes through the RLF: The period from the time of receiving the
latest HO Command message to the RLF occurrence time.
b If the UE fails the HO operation: The period from the time of receiving the
latest HO Command message to the time of failing the HO operation
4 connectionFailureType-r10
a If the UE goes through the RLF: rlf
b If the UE fails the HO operation: hof
5 previousPCellId-r10: ECGI of the cell that sent the latest HO Command
message.
In Samsung MRO function, the cell with which UE establishes RRC connection
collects the information of the HO-related problem by itself if failedPCellId-r10 in
the rlf-report-r9 information matches its own PCI. This reduces the X2 messaging
overhead for collecting information of the HO-related problem. If failedPCellId-
r10 is different from its own PCI, it transmits the RLF Indication message to the
cell which served the UE before RLF by type of connection failure. In Samsung
MRO function, the statistics are collected only if the RRC connection setup cell

Confidential
Chapter 9 SON
and the reestablishment cell are identical to determine the HO-related problem
based on Release 10. If one of following conditions is satisfied, Samsung MRO
function considers that RRC connection setup cell and the reestablishment cell are
identical:
1 If the reestablishmentCellId-r10 value exists in rlf-report-r9 and it is identical
to the ECGI of the RRC connection setup cell.
2 If there is no reestablishmentCellId-r10 value in rlf-report-r9 and the best
neighbor cell based on the signal strength is the RRC connection setup cell.
o The best neighbor cell refers to the highest upper cell of
measResultNeighCells in rlf-report-r9.
In Samsung MRO function, the HO-related problems based on the Release 10
standard are subdivided and collected as follows. For eMTC UEs, 3GPP Release
10 based HO-related problem statistics are not collected.
Table below outlines HO-related problem classification based on 3GPP Release 10
spec.
Time that RLF RRC connection setup cell
occurs
Serving cell Target cell Other Cell
Before HO (1) CoverageHole N/A (2) TooLateHO
initiation & After (RLFBeforeTriggering)
HO triggering
During HO (3) TooEarlyHO (HOFailure) (4) CoverageHoleN (5) HOtoWrongCell
execution (RLFAfterTriggering)
After HO (6) TooEarlyHO (7) CoverageHoleN (8) HOtoWrongCell

execution (RLFAfterHO) (RLFAfterHO)
The collection status of each item referred to in the above table is as follows:
(1) CoverageHole
1 The UE has been connected for the Tstore_ue_cntxt time or more in the
existing serving cell.
2 The UE experiences the RLF before HO initiation.
3 The UE fails the RRC Connection Reestablishment operation.
4 The UE succeeds the RRC Connection Setup process.
5 It is checked that the newly connected cell is the existing serving cell of the
UE by using the rlf-report-r9 information acquired from the UE.
6 The newly connected cell collects the statistics by using the rlf-report-r9
information.
(2) TooLateHORLFBeforeTriggering
1 The UE has been connected for the Tstore_ue_cntxt time or more in the
existing serving cell.
2 The UE experiences the RLF before HO initiation.
Confidential
Chapter 9 SON

5 Ensure that the newly connected cell is a cell other than the existing serving
cell of the UE by using the rlf-report-r9 information acquired from the UE
and transmit the RLF Indication message to the existing serving cell (RLF
source cell).
6 The existing serving cell collects the statistics for the other cell by using the
rlf-report-r9 information.
(3) TooEarlyHOHOFailure
3 The UE fails HO to the target cell.
5 The UE succeeds the RRC Connection Setup procedure.
7 The newly connected cell collects the statistics for the HO target cell by using
the rlf-report-r9 information.
(4) CoverageHoleN
6 It is checked that the newly connected cell is the HO target cell of the UE by
using the rlf-report-r9 information acquired from the UE.
7 The newly connected cell collects the statistics for the existing serving cell by
using the rlf-report-r9 information.
(5) HOtoWrongCellRLFAfterTriggering
cell and HO target cell of the UE by using the rlf-report-r9 information
acquired from the UE and transmit the RLF Indication message to the
existing serving cell (RLF source cell).
7 The existing serving cell collects the statistics for the HO target cell by using

Confidential
Chapter 9 SON

(6) TooEarlyHORLFAfterHO
3 The UE succeeds HO to the target cell.
4 The UE experiences RLF in a short period (Tstore_ue_cntxt).
8 The newly connected cell collects the statistics for the HO target cell by using
(7) CoverageHoleN
7 It is checked that the newly connected cell is the HO target cell of the UE by
using the rlf-report-r9 information acquired from the UE.
8 The newly connected cell collects the statistics for the existing serving cell by
using the rlf-report-r9 information.
(8) HOtoWrongCellRLFAfterHO
cell and HO target cell of the UE by using the rlf-report-r9 information
acquired from the UE and transmit the RLF Indication message to the
existing serving cell (RLF source cell).
8 The existing serving cell collects the statistics for the HO target cell by using
Detection of Ping-pong Handover

Confidential
Chapter 9 SON
Ping-pong HO means a problem of HO being generated from one cell to the other
and then returning to the original cell again within a short time. In this case,
because the HO to the other cell causes the waste of network resources due to
unnecessary operations, such HO generation must be minimized. To detect the
occurrence of the ping-pong HO generation, before HO to the cell, the HO target
cell uses the Last Visited E-UTRAN Cell Information IE including (1) the cell
information visited before and (2) the information on the time of staying in the
cell. The IE is included in the UE History Information IE of the X2 HANDOVER
REQUEST/S1 HANDOVER REQUIRED messages for HO preparation. The
procedure of the HO target cell for collecting the ping-pong HO statistics is as
follows:
1 Acquire the Last Visited E-UTRAN Cell Information IE for the UE.
2 The HO target cell searches the latest visited records in the Last Visited E-
UTRAN Cell Information IE when the UE completes the RRC connection.
a Time of receiving the RRC connection reconfiguration complete message
from the HO-in UE.
b Time of receiving the RRC connection reestablishment complete message
from the HO-in UE.
3 If the cell finds itself and one of the following conditions is satisfied, the cell
calculates the sum of the time of staying the cells visited just before itself.
a HO cause does not exist in the Last Visited E-UTRAN Cell Information
IE.
b HO cause exists and the value is "Handover Desirable for Radio Reason".
4 The sum of the time of staying the cells ("Time UE stayed in Cell" IE or
"Time UE stayed in Cell Enhanced Granularity" IE) visited (Cell1, …, Celln)
just before itself is satisfied, the HO target cell collects the ping-pong HO
statistics for the Cell 1.
o PINGPONG_HANDOVER_TIMER: The base time value to detect the

occurrence of the ping-pong HO (Unit: second, Command: CHG-SON-
MRO).
Detection of Coverage Hole
Samsung MRO function detects and compiles statistics on coverage holes based on
the RLF report included in the RLF indication message. In Samsung MRO
function, the target cell acquires RLF report information from UE through the
following procedures:
2 The UE fails to receive a HO command from the service cell, or fails to
perform HO with the target cell after receiving a HO command.
3 The UE requests for RRC connection reestablishment to the target cell.
4 If RLF report information is included in the RRC connection reestablishment
complete message, UE sets the rlf-InfoAvailable-r9 IE value in this message

Confidential
Chapter 9 SON
to True.
5 The target cell sets the rlf-ReportReq IE value in the UE information request
message to True.
6 The UE includes the RLF report information (RLF-Report-r9) in the UE
information response message.
Out of the RLF report information transmitted by UE, measResultLastServCell
contains the serving cell measurement results before RLF, and
measResultNeighCells contains the measurement results of the neighbor cells
before RLF. The cell that makes the highest result is placed at the top, and other
cells are lined up in the descending order. If MeasConfig contains
MeasObjectEUTRA of different EUTRA frequencies, MeasResultList2EUTRA
contains carrier frequency information and the corresponding
MeasResultListEUTRA information.
Samsung MRO function decides the occurrence of coverage hole in the method
shown below depending on available information including RSRP of the serving
cell (RSRP_{ServingCell}), RSRQ of the serving cell (RSRQ_{ServingCell}), and
RSRP of the best neighbor cell (RSRP_{BestNeighborCell}) in the RLF report
information transmitted by the target cell.
• Case1
If the information on RSRP and RSRQ of the serving cell and the RSRP of the
best neighbor cell is collected, deciding the occurrence of coverage hole as
follows:
a Calculate SINR (SINR_{ServingCell}) based on the serving cell by using
the collected information.
b Calculate SINR (SINR_{BestNeighborCell}) based on the best neighbor
cell by using the collected information.
c SINR = MAX (SINR_{ServingCell}, SINR_{BestNeighborCell})
d If SINR < Threshold_{CoverageHole}, decide as coverage hole.
• Case2
If the information on RSRP and RSRQ of the serving cell is collected,
deciding the occurrence of coverage hole as follows:
a Calculate SINR (SINR_{ServingCell}) based on the serving cell by using
the collected information.
b If SINR_{ServingCell} < Threshold_{CoverageHole}, decide as coverage
hole.
• Case3
If the information on RSRP of the serving cell and RSRP of the best neighbor
cell is collected, deciding the occurrence of coverage hole as follows:
o If RSRP_{BestNeighborCell} - RSRP_{ServingCell} < 0, decide as
coverage hole.
In event of [Case1] and [Case2], if the coverage hole conditions are satisfied, the
RF status in the RLF occurring area is considered poor and then it is decided as the

Confidential
Chapter 9 SON
RLF occurrence by the coverage hole. In event of [Case3], if the coverage hole
conditions are satisfied, it means that there is no neighbor cell with the RSRP
better than the RSRP of the serving cell in the RLF occurring area and therefore, it
is decided as the RLF occurrence by the coverage hole.
Figure below depicts the situation where the Samsung MRO function detects
coverage hole.
Control of Handover Parameter

Samsung MRO algorithm is performed in the following procedures, and the detail
procedure is illustrated in Figure Handover parameter control algorithm:
1 At the end of MRO algorithm period (T_PERIOD, command: CHG-SON-
MRO), if the number of Effective HO attempts for a neighbor cell is larger
than the threshold (N_HANDOVER_THRESH, command: CHG-SON-MRO),
eNB controls CIO of the neighbor cell as follows. If the number of Effective
HO attempts for a neighbor cell is less than N_HANDOVER_THRESH, eNB
counts Effective HO attempts of the neighbor cell without initializing the
number of Effective HO attempts.
a If Effective HO success rate by neighbor cell ≥
HANDOVER_SUCCESS_KPI (CHG-SON-MRO) and
PINGPONG_CONTROL = On (command: CHG-SON-MRO), the
Samsung MRO function raises HO margin by adjusting the CIO value to
decrease ping-pong HO.
b If Effective HO success rate by neighbor cell ≥
HANDOVER_SUCCESS_KPI and PINGPONG_CONTROL =
On_pingpongHOStatBased and occurrence rate of Ping-pong HO ≥
TH_PINGPONG (CHG-SON-MRO), the Samsung MRO function raises
HO margin by adjusting the CIO value to decrease ping-pong HO.
c If Effective HO success rate < HANDOVER_SUCCESS_KPI
i If Too-late HO problem occurrence rate > Too-early HO problem
occurrence rate and Too-late HO problem occurrence rate > HO-to-
wrong-cell problem occurrence rate, the function reduces the HO
margin by extending the CIO value to advance the HO point.
ii If Too-late HO problem occurrence rate < Too-early HO problem
occurrence rate or Too-late HO problem occurrence rate < HO-to-
wrong-cell problem occurrence rate, the function raises HO margin by
Confidential
Chapter 9 SON
reducing the CIO value to put off the HO point.

iii If the rates of generating all HO-related problems are identical, keep
the CIO value.
iv Otherwise, the function reduces the HO margin by extending the CIO
value.
2 The eNB controls A2 threshold according to the result of CIO change after
controlling CIO of all neighbor cells. Detail operation is as follows.
a The eNB increases A2 threshold if increasing CIO did not improve the
Effective HO success rate for inter-frequency HO.
b The eNB decreases A2 threshold if “Effective HO success rate per each
inter-frequency neighbor cell ≥ HANDOVER_SUCCESS_KPI" and “there
is no change in CIO of each inter-frequency neighbor cell.
3 The eNB monitors Effective HO success rate and call drop rate during the
statistics collection period to determine HO parameter rollback
(T_PERIOD_TEMP + T_PERIOD_TEMP_EXTENSION,CHG-SON-MRO)
after applying the changed CIO and A2 Threshold.
a If the Effective HO success rate or call drop rate is deteriorated, eNB
rollbacks the HO parameters to the previous value of CIO and A2
Threshold.
b If the Effective HO success rate or call drop rate is improved or
maintained, eNB maintains the changed CIO and A2 Threshold.
Figure below depicts Handover parameter control algorithm.

Confidential
Chapter 9 SON
• # of Effective HO Failures = Sum of HO-related problems collected by Intra-

LTE MRO
• # of Effective HO successes = # of HO successes excluding the HO success
case regarded as Effective HO Failure
• # of Effective HO Attempts = # of EffectiveHandoverSuccesses + # of
EffectiveHandoverFailures
• Effective HO Success Rate = # of EffectiveHandoverSuccesses/# of
EffectiveHandoverAttempts
EMS Load Distribution Method by the MRO Function
The CIO controlled by Samsung MRO algorithm as a system parameter consists of
the attributes of the NRT management object (ExternalEutranCellFDDLogic).

Confidential
Chapter 9 SON
Accordingly, if the CIO value per neighbor cell in the NRT of each cell is changed
by the MRO function, an NRT update notification message is transmitted to the
EMS for synchronizing the NRT management object. If all cells connected to the
EMS perform MRO function at the identical time, the instantaneous load to the
EMS may overwhelm it. Thus, Samsung MRO function provides the following
EMS load distribution method.
1 All eNBs connected to the EMS perform the MRO function during the time
from 00:00 to 03:00.
2 Each eNB decides the time of performing its MRO function by using its
eNBID
o Time of performing MRO function of eNB i: TMRO(i)
3 Each eNB executes MRO algorithm in the order of the served cell index at
the time of performing its MRO function determined in Procedure 2.
HO Parameter Optimization Result Reporting Function
If CIO value of a neighbor cell is changed by the MRO function, eNB transmits
the relevant event to EMS.
In addition, at the situation where the CIO value by the MRO function operated in
the eNB must be changed, if the changing operation fails, the eNB transmits the
event of informing the failure to the EMS.
SYSTEM OPERATION
How to Activate
Preconditions
• The UE supports RLF report functionality (For Intra-LTE MRO
enhancement).
To activate basic Intra-LTE MRO, MOBILITY_ROBUSTNESS ENABLE value
must be set to Auto.
The eNB analyses which handover problem (for example, Too Early HO, Too Late
HO, HO to Wrong Cell, Ping-pong HO) is occurred based on Samsung MRO
handover problem detection algorithm.
If handover problem is detected, the eNB increases related counter by one.
• Every MRO period, the eNB performs Intra-LTE MRO statistics data analysis
and determines whether to change handover parameters for solving handover
problems.

Confidential
Chapter 9 SON
• In the result of inter-RAT MRO execution algorithm at every MRO period,

IND_OFFSET (that is, Cell Individual Offset) parameter value of neighbor
cell may be adjusted automatically.
To activate Intra-LTE Inter-frequency MRO, INTER_FREQ_CONTROL value
must be set to True.
• To deactivate basic Intra-LTE MRO, MOBILITY_ROBUSTNESS ENABLE
value must be set to Off.
• To deactivate Intra-LTE Inter-frequency MRO, INTER_FREQ_CONTROL
value must be set to False.
Key Parameters
parameters.
The operator can use the following commands and parameter to set the operation
mode of the Samsung MRO function to Auto/Off, or to retrieve the current
operation mode:
MOBILITY_ROBUSTNE Whether to enable the Coverage and Capacity Optimization (CCO) SON function,
SS_ENABLE (one of the SON functions).
• Auto: When the parameter value is changed by an algorithm, this change is
applied automatically.
parameters.
Parameter Descriptions of CHG-SON-MRO/RTRV-SON-MRO
T_PERIOD The parameter indicates the operation period for the Mobility Robustness
Optimization (MRO) function. The MRO algorithm is performed based on the
handover and Radio Link Failure (RLF) statistics collected during this parameter
value.
• one_day: MRO function is triggered based on the statistics collected for 1 day.
• one_week: MRO function is triggered based on the statistics collected for 1 week.
T_PERIOD_TEMP The parameter indicates the value of the timer which monitors the following
situation occurs: the performance of either HO or call drop rate during this
parameter value is degraded when compared with that during the previous period.
• one_hour: The statistics is collected for 1 hour to monitor the fallback situation.
• one_day: The statistics is collected for 1 day to monitor the fallback situation.
HANDOVER_SUCCES The parameter indicates the threshold for HO success Key Performance Indicator
S_KPI (KPI) to trigger the MRO algorithm (unit: %). The MRO algorithm is triggered if the
HO success rate is lower than this parameter value.
N_HANDOVER_THRES The parameter indicates the threshold for the HO attempt count to trigger the MRO

Confidential
Chapter 9 SON
H algorithm. The MRO algorithm is triggered if the HO attempt count collected during
the period (T_PERIOD) is higher than this parameter value.
OFFSET_MAX The maximum value allowable for the HO margin when Event A3 is used to the HO
triggering condition in E-UTRAN system (Unit: dB). The HO margin in Event A3 is
equal to as follows: HO margin = ofs - ofn + ocs - ocn + hys + off and the Cell
Individual Offset (CIO) parameter controlled by the MRO algorithm indicates ocn.
The value of CIO is optimized as satisfying the condition that HO margin is equal to
or less than this parameter value.
OFFSET_MIN The minimum value allowable for HO margin when Event A3 is used to the HO
triggering condition in E-UTRAN system (unit: dB). The HO margin in Event A3 is
equal to as follows: HO margin = ofs - ofn + ocs - ocn + hys + off and the Cell
Individual Offset (CIO) parameter controlled by the MRO algorithm indicates ocn.
The value of CIO is optimized as satisfying the condition that HO margin is equal to
or greater than this parameter value.
PINGPONG_CONTROL This parameter is the flag controlling whether the operation of ping-pong Handover
(HO) reduction is performed or not.
• Off: The operation of ping-pong HO reduction is not performed.
• On: The operation of ping-pong HO reduction is performed.
• Ping pong HO Stat Based: The operation of ping-pong HO reduction is performed
if ping-pong HO rate is greater than or equal to TH_PING_PONG.
PINGPONG_HANDOVE The parameter indicates the threshold of time to detect the occurrence of the ping-
R_TIMER pong HO (unit: second).
TH_CALL_DROP_RAT The parameter indicates the threshold for the call drop rate used to the fall-back
E condition after decreasing the CIO value for reducing ping-pong HO occurrence
(unit: %).
INTER_FREQ_CONTR This parameter is the flag controlling whether the MRO function for inter-frequency
OL neighbor cell is performed or not.
• False: The MRO function is not performed for inter-frequency neighbor cell.
• True: The MRO function is performed for inter-frequency neighbor cell.
TH_PING_PONG The parameter indicates the threshold related to the occurrence rate of Ping-pong
handover to trigger Ping-pong handover statistics-based Ping-pong handover
minimization algorithm (Unit: %). If the occurrence rate of Ping-pong handover
collected during the statistics period is higher than this threshold, it satisfies the
triggering condition of the algorithm.
T_PERIOD_TEMP_EXT This parameter is used to increase the value of the timer for monitoring the
ENSION temporarily unsatisfactory HO performance after the HO parameter change by the
MRO algorithm.
Counters and KPIs

MRO RLF Classification CoverageHole Number of RLF/HO failures due to the coverage hole.
CoverageHoleN Number of RLF/HO failures due to the coverage hole
toward Cell N.
TooEarlyHoFailure The number of too-early handovers after transmitting
the handover command.
TooEarlyHoRlfAfterHo The number of too-early handovers after completing
the handover process.
TooLateHoRlfBeforeTrig The number of RLFs before triggering the handover.
gering

Confidential
Chapter 9 SON

TooLateHoRlfAfterTrigge The number of RLFs after the handover command is
ring transmitted.
WrongCellRlfAfterTrigger The number of handovers to a wrong cell before
ing transmitting the handover command.
WrongCellRlfAfterHo The number of handovers to a wrong cell after
transmitting the handover command.
PingpongHandover The number of ping-pong handovers detected by the
ping-pong detection algorithm.
MRO RLF Voice TooEarlyHoFailureVoice The number of too-early handovers after transmitting
(For VoLTE) the handover command. (For VoLTE)
TooEarlyHoRlfAfterHoVo The number of too-early handovers after completing
ice (For VoLTE) the handover process.(For VoLTE)
TooLateHoRlfBeforeTrig The number of RLFs before triggering the
geringVoice (For VoLTE) handover.(For VoLTE)
TooLateHoRlfAfterTrigge The number of RLFs after the handover command is
ringVoice (For VoLTE) transmitted.(For VoLTE)
WrongCellRlfAfterTrigger The number of handovers to a wrong cell before
ingVoice (For VoLTE) transmitting the handover command.(For VoLTE)
WrongCellRlfAfterHoVoic The number of handovers to a wrong cell after
e (For VoLTE) transmitting the handover command.(For VoLTE)
PingpongHandoverVoice The number of ping-pong handovers detected by the
(For VoLTE) ping-pong detection algorithm.(For VoLTE)
MRO RLF at RRC CoverageHoleAtSetup Occurrence in radio link failure by a coverage hole in a
Connection serving cell RRC reestablishment in the serving cell.
CoverageHoleAtSetupN RRC reestablishment in the target cell during or after
handover.
TooEarlyHoFailureAtSet RRC reestablishment in the source cell without the
up terminal moving to the target cell due to the attempt for
too-early handover.
TooEarlyHoRlfAfterHOAt Occurrence in radio link failure after the terminal moves
Setup to the target cell due to the attempt for too-early
handover RRC reestablishment in the source cell.
TooLateHoRlfBeforeTrig Occurrence in radio link failure in the serving cell by
geringAtSetup failing to attempt the handover even though the
terminal has moved to another cell RRC
reestablishment in the serving cell.
HoToWrongCellRlfAfterT RRC reestablishment by the terminal in other cell while
riggeringAtSetup the handover procedure is not complete by attempting
at the handover to the cell where the terminal is not
located.
HoToWrongCellRlfAfterH Occurrence in radio link failure in the target cell after
OAtSetup completion of handover by attempting at the handover
to the target cell RRC reestablishment in other cell by
the terminal.
Intra-eNB Handover IntraEnbPrepSucc The cumulated number when the RRC connection
reconfiguration message is transmitted to the UE since
preparation is completed for handover to the target cell
between the inner blocks when intra HO is judged in
the handover decision after a measurement report
message is received from the UE.
IntraEnbSucc The cumulated number when the target cell normally
receives the RRC connection reconfiguration complete

Confidential
Chapter 9 SON

message from the UE by performing intra HO.
X2 Out Handover InterX2OutPrepSucc The cumulated number when a RRC Connection
Reconfiguration message is transmitted to the UE
since a HandoverRequestAcknowledge message is
received from the target eNB after a HandoverRequest
message is transmitted to the target eNB due to inter
X2 HO being judged in the HO decision after a
MeasurementReport message is received from the UE.
InterX2OutSucc The cumulated number when an UE context release
command is normally received by the source eNB
when the target eNB receives a RRC connection
reconfiguration complete message from the UE after
the source eNB transmits a
RRCConnectionReconfiguration message to the UE
through inter X2 HO execution.
Table below outlines the KPI associated with this feature.

Mobility EutranMobilityHoIntra The calculated HOIntra success rate of E-UTRAN
mobility.
EutranMobilityHOX2Out The calculated HOX2Out success rate of E-UTRAN
mobility.
REFERENCE
[1] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2 (Release
10).
[3] 3GPP 36.423: E-UTRAN; X2 application protocol (X2AP) (Release 10).
use cases and solutions.
[5] 3GPP 32.500: E-UTRAN; Concepts & Requirements.
Requirements for Self Configuration Use Cases.

Confidential
Chapter 9 SON
LTE-SO0505, UE Level Ping-pong HO

Minimization
INTRODUCTION
UE Level Ping-pong HO Minimization (UPM) feature reduces the number of
unnecessary ping-pong handovers (HOs) by adjusting the HO parameters on a per-
UE basis. To this end, eNB detects a UE that is experiencing frequent ping-pong
HOs between two cells. Then, eNB applies modified HO parameter to the UE to
avoid more ping-pong HOs between those two cells.
BENEFIT
Reducing ping-pong HO can free up additional network resources otherwise
wasted on unnecessary HO signaling. This can also translate into cutting any
OPEX previously assigned to resolve such issues.
The reduction of ping-pong HOs can provide a more seamless service with fewer
delays and call drops.
DEPENDENCY
E-UTRAN (LTE)
• Others:
Determining the "serving cell" of ping-pong UEs based on cell-load is
conditional on the availability of neighbor load information.
LIMITATION
None
SYSTEM IMPACT
LTE-SO0501 Intra-LTE MRO
It is recommended to set the period of the network quality monitoring function less
than the algorithm period of Intra-LTE MRO.
LTE-SW2001, Intra-LTE Mobility Load Balancing
It is recommended to set the cell load threshold for UPM less than the threshold
for Intra-LTE Mobility Load Balancing.
LTE-ME4003, FeICIC
UPM does not change the UE-specific CIO of the partner neighbor cells for

Confidential
Chapter 9 SON
FeICIC.
None
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
If a UE stays at a location where signal strengths from two cells are almost same,
the UE may be continuously handed over between them due to RF fluctuation.
UPM adjusts the HO parameter on a per-UE basis to reduce upcoming
unnecessary HOs (for example, ping-pong HOs).
The figure below depicts UE experiencing frequent ping-pong HOs.
When a UE is handed over from one cell to another, the source cell provides the
target cell with the UE’s history information. The UE history information (found
in the UE History Information IE) contains the identities of previously visited cells
as well as the time UE spent in each cell.
Using the UE history information, eNB determines if the UE has experienced a
ping-pong HOs or not. A UE is said to have experienced a ping-pong HO if it has
returned to its original cell within PINGPONG_HANDOVER_TIMER (CHG-
SON-MRO). The figure below shows how eNB utilizes the UE history information
to detect ping-pong HOs.
Figure below depicts Ping-Pong detection using UE History Information.

Confidential
Chapter 9 SON
UPM operation consists of following four parts.

• Detection of a UE experiencing frequent ping-pong HOs
• Decision on whether to adjust the HO parameter of the frequent ping-pong UE
• Application of UE-specific HO parameter to the frequent ping-pong UE
• Network quality monitoring (periodic operation)
Detection of a UE Experiencing frequent ping-pong HOs

A UE experiencing frequent ping-ping HOs is detected if the number of its ping-
pong HOs exceeds a pre-configured ping-pong count threshold
(TH_PP_HO_COUNT, Command: CHG-SON-UPM) within a pre-configured time
window (PP_HO_TIME_WINDOW, Command: CHG-SON-UPM). The figure
below illustrates how a frequent ping-pong UE is detected.
Figure below depicts Fig3: Frequent ping-pong UE detection using UE History
Information
In the figure above, at the time of handover to cell B, cell B detects 2 ping-pong
HOs between cell A and cell B during "Time Window" and then cell B decides
that a frequent ping-pong UE is detected.
Decision on whether to adjust the HO Parameter of a frequent ping-pong UE

When eNB detects a frequent ping-pong UE, the eNB determines whether to adjust
the HO parameter of the frequent ping-pong UE based on the "serving cell"
decision mode (HO_PARA_ADJUST_DECISION_MODE, Command: CHG-
SON-UPM). There are two "serving cell" decision modes as follows:

Confidential
Chapter 9 SON
• If HO_PARA_ADJUST_DECISION_MODE = pp_ho_reduction_mode,
o HO parameter of the detected UE is adjusted to reduce the number of ping-
pong HOs
• If HO_PARA_ADJUST_DECISION_MODE = cell_load_based_mode
o eNB determines whether to adjust HO parameter of the detected UE
considering cell loads of the HO source and HO target cells
Application of UE-specific HO Parameter to a frequent ping-pong UE

If eNB decides to adjust HO parameter of the frequent ping-pong UE, the eNB
configures the UE with a modified CIO, called "UE-specific CIO", for the problem
neighbor cell. This UE-specific CIO lowers the possibility of any more ping-pong
HO between the two cells. When the frequent ping-pong UE is detected at the first
time (that is, the number of ping-pong HOs within the pre-configured time window
is equal to TH_PP_HO_COUNT), eNB uses the initial offset value
(CIO_INITIAL_OFFSET, Command: CHG-SON-UPM) for an adjustment to the
UE-specific CIO. Then, eNB increases the offset value for the adjustment by
CIO_WEIGHT (CHG-SON-UPM) as the number of ping-pong HOs within the pre-
configured time window increases by 1.
Figure below depicts UE-specific CIO Adjustment.
Network Quality Monitoring (periodic operation)

In every network quality monitoring period (STATS_CHECK_PERIOD,
Command: CHG-SON-UPM), eNB automatically updates the minimum value of
the UE-specific CIO for each neighbor cell. If the ratio of "Too Late HOs and HOs
to Wrong Cell caused by UPM function" to "Total HO Attempts" is larger than
pre-defined threshold (TH_TOO_LATE_TO_WRONG_CELL_HO_FAIL_RATE,
Command: CHG-SON-UPM), the minimum value of the UE-specific CIO is
increased to prevent network quality degradation. If the ratio is less than or equal
to the pre-defined threshold, minimum value of the UE-specific CIO can be
decreased.
SYSTEM OPERATION

Confidential
Chapter 9 SON
How to Activate
Preconditions
• License for the "UE Level Ping-pong HO Minimization" function needs to be
acquired.
• Run CHG-SONFN-CELL and set SON_UPM_FUNC_ENABLE for UPM target
cell to sonSoAutoApply.
• Run CHG-SONFN-CELL and set SON_UPM_FUNC_ENABLE for UPM target
cell to sonSoFuncOff.
Key Parameters
parameters
SON_UPM_FUNC_ENABLE This parameter represents whether UE level Ping-pong HO Minimization
(UPM) function is enabled or not.
• sonSoFuncOff (0): disabled
• sonSoAutoApply (1): enabled
parameters.
Parameter Descriptions of CHG-SON-UPM/RTRV-SON-UPM
PP_HO_TIME_WINDOW This parameter is used to configure the time window used to detect UE in ping-
pong HO. A UE is detected as ‘candidate UE in ping-pong HO’ if the condition
“In the last PP_HO_TIME_WINDOW seconds, TH_PP_HO_COUNT times of
ping-pong HO happens” is satisfied
TH_PP_HO_COUNT This parameter is used to configure the number of ping-pong HO to detect the
UE in ping-pong HO. A UE is detected as ‘candidate UE in ping-pong HO’ if the
condition “In the last u PP_HO_TIME_WINDOW seconds, TH_PP_HO_COUNT
times of ping-pong HO happens” is satisfied
STATS_CHECK_ENABLE This parameter represents whether the network quality monitoring is enabled. If
this parameter is enabled, minimum value of CIO to neighbor cell is adjusted by
network quality monitoring.
• sonSoFuncOff: disabled

Confidential
Chapter 9 SON
• sonSoAutoApply: enabled
STATS_CHECK_PERIOD This parameter is used to configure the period of network statistics collection for
UE level ping-pong HO minimization operation
TH_STATS_CHECK_NUM_ This parameter is used to configure the threshold number of HOs in network
HO quality monitoring
If the number of collected HOs in STATS_CHECK_PERIOD is less than
TH_STATS_CHECK_NUM_HO, the network quality monitoring is not applied
TH_TOO_LATE_TO_WRO This parameter is used to configure the threshold for Handover (HO) failure rate
NG_CELL_HO_FAIL_RATE caused by ‘too late HO~’ and ‘HO to wrong cell~’ failure
Minimum CIO to each neighbor cell is adjusted based on
TH_TOO_LATE_TO_WRONG_CELL_HO_FAIL_RATE
WEIGHT_NET_QUAL_MO This parameter is used to configure the weighting factor of
NITORING_PERIOD STATS_CHECK_PERIOD to define network quality monitoring period for
decreasing minimum CIO
If the network quality measured in previous (STATS_CHECK_PERIOD
WEIGHT_NET_QUAL_MONITORING_PERIOD) period is greater than
TH_TOO_LATE_TO_WRONG_CELL_HO_FAIL_RATE, minimum CIO is not
decreased
MAX_CIO_REDUCTION This parameter is used to configure the maximum value that CIO could be
reduced from cell level CIO
TH_CELL_LOAD This parameter is used to configure the threshold of cell load
If the cell load is greater than TH_CELL_LOAD, a UE in ping-pong HO is NOT
tried to be camped in the cell
CIO_INITIAL_OFFSET This parameter is used to configure the initial offset of Cell Individual Offset
(CIO) for detected UE in ping-pong HO
CIO_WEIGHT This parameter is used to configure the weighting factor of Cell Individual Offset
(CIO) for the excessive number of detected ping-pong HO
HO_PARA_ADJUST_DECI The parameter is used to configure the operation mode of UE level ping-pong
SION_MODE HO minimization. For the detected UE in ping-pong HO, CIO (Cell Individual
Offset) is decided to be adjusted or not depending on the value of this
parameter
• (PP_HO_REDUCTION_MODE): CIO of the detected UE is adjusted to
reduce the unnecessary ping-pong HO
• (CELL_LOAD_BASED_MODE): CIO of the detected UE is adjusted if cell
load of current cell is equal to or lower then thCellLoad and cell load is equal
to or greater than lower than the ping-pong cell's load
Counters and KPIs

UPM RLF Classification TooEarlyHoFailureUpm The number of RRE to Source Cell due to RLF after
eNB sent handover command to the neighbor cell
applied UE specific CIO by UE level Ping-pong
handover Minimization function but UE failed to
camp to the target cell.
TooEarlyHoRlfAfterHoU The number of RRE to Source Cell due to RLF right
pm after UE performed successful handover to the
neighbor cell applied UE specific CIO by UE level
Ping-pong handover Minimization function.
TooLateHoRlfBeforeTri The number of RRE to the neighbor cell applied UE

Confidential
Chapter 9 SON

ggeringUpm specific CIO by UE level Ping-pong handover
Minimization function due to RLF before eNB triggers
to handover.
TooLateHoRlfAfterTrigg The number of RRE to Target Cell due to RLF after
eringUpm eNB sent handover command to the neighbor cell
WrongCellRlfAfterTrigg The number of RRE to Other Cell due to RLF after
eringUpm eNB sent handover command to the neighbor cell
WrongCellRlfAfterHoUp The number of RRE to Other Cell due to RLF right
m after UE performed successful handover to the
UpmHoPrepSuccess The number of Handover preparation success to the
UpmHoSuccess The number of Handover execution success to the
Ping-pong Handover Pingpong1 The number of Ping-pong handover happened once.
Classification
Pingpong2 The number of Ping-pong handover happened twice.
Pingpong3 The number of Ping-pong handover happened three
times.
Pingpong4 The number of Ping-pong handover happened four
times.
Pingpong5 The number of Ping-pong handover happened five
times.
Pingpong6 The number of Ping-pong handover happened six
times.
Pingpong7 The number of Ping-pong handover happened seven
times.
Pingpong8 The number of Ping-pong handover happened eight
times.
REFERENCE
(Release 12).
[3] 3GPP TS 36.902: E-UTRAN; Self-configuring and self-optimizing network

Confidential
Chapter 9 SON
(SON) use cases and solutions.

[4] 3GPP TS 32.500: E-UTRAN; Concepts & Requirements.
[5] 3GPP TS 32.501: E-UTRAN; Self-configuration of network elements; OAM
Requirements for Self Configuration Use Cases.
[6] 3GPP TS 36.413: E-UTRAN; S1 Application Protocol (Release 12).
[7] 3GPP TS 36.423: E-UTRAN; X2 Application Protocol (Release 12).

Confidential
Chapter 9 SON
LTE-SO0601, Sleeping Cell Detection

INTRODUCTION
Sleeping Cell Detection feature automatically finds sleeping cells by detecting the
absence of normal processing without any alarm noticed by eNB. This feature can
detect "Zero Call Occurrence Cell", "Zero Call with Hand-in Failure Occurrence
Cell", "Low Call Occurrence Cell", and "Abnormal Call Occurrence Cell" by
analyzing Call Release Reason (CRR) statistics.
BENEFIT
Using this feature, cells in abnormal conditions without any explicit alarm can be
automatically detected for efficient management.
DEPENDENCY
None
LIMITATION
This feature can operate properly after 8 days from EMS installation.
SYSTEM IMPACT
None
None
Coverage
None
Interfaces
Interface between eNB and EMS may affect the operation of Sleeping Cell
Detection.
FEATURE DESCRIPTION
Sleeping cell detection feature can detect the cells in abnormal condition without
generating any explicit alarm by analyzing CRR statistics. Operator can select one
or more conditions for detecting sleeping cells among the following 4 options.
Operator can configure whether to use each option and the thresholds used for
each option through Sleeping Cell Detection Window GUI in EMS.
• Zero Call Occurrence Cell: Detects sleeping cell by monitoring "the number
of normal CRRs in the previous week" and "the number of current normal

Confidential
Chapter 9 SON
CRRs."
• Zero Call with Hand-in Failure Occurrence Cell: Detects sleeping cell by
monitoring "the number of hand-in failure CRRs" and "the number of current
normal CRRs."
• Low Call Occurrence Cell: Detects sleeping cell by monitoring the reduced
amount of "current normal CRRs" compared to "normal CRRs in previous
week."
• Abnormal Call Occurrence Cell: Detects sleeping cell by monitoring the
ratio of "abnormal CRRs" to "total CRRs."
Procedure of Sleeping Cell Detection

Sleeping Cell Detection operates in the following order. If any sleeping cell
condition is met, an alarm is automatically generated and notified to operator.
1 EMS starts Sleeping Cell Detection operation at every 15 minutes.
2 When the detection time arrives, EMS checks the following exception cases.
o The status of the cell is locked.
o CRR statistics in 15 min statistics is NG (No Data).
o CRR statistics does not exist in Database.
o Previous sleeping cell detection operation is not yet finished.
o Alarms are already issued for the eNB
o Sleeping Cell Detection feature is not enabled to the eNB.
3 If a cell (or an eNB) meets any of the above exception cases, EMS does not
evaluate whether the cell is sleeping cell. If not, for evaluating whether the
cell is sleeping cell, EMS classifies CRRs of the cell by using the information
collected in CSL counter family for the monitored range. The monitored
range means the duration for checking whether the cell is sleeping cell or not.
4 EMS checks if a cell corresponds to any sleeping cell case based on the
activated options among the following 4 options.
o Zero call occurrence cell detection: Sleeping cell alarm is generated if all
the following conditions are satisfied.
♦ Average number of normal CRRs ≤ Normal CRR
◊ Average number of normal CRRs: Average number of normal
CRRs during 15 minutes for the monitored range
♦ Average number of normal CRRs in previous week ≥ Base Normal
CRR
♦ Number of normal CRRs just before monitored range ≥ Previous
Normal CRR
◊ Number of normal CRRs: The number of normal CRRs during 15
minutes
o Zero call with hand-in fail occurrence cell detection: Sleeping cell alarm is

Confidential
Chapter 9 SON
generated if all the following conditions are satisfied.

♦ Average number of normal CRRs ≤ Normal CRR
♦ Average number of Hand-in failure CRRs ≥ Hand-in fail CRR
o Low call occurrence cell detection: Sleeping cell alarm is generated if all
the following conditions are satisfied.
♦ Average number of normal CRRs in previous week ≥ Base Normal
CRR
♦ Ratio of normal CRRs to normal CRRs in previous week ≤ Ratio of
normal CRR
♦ Ratio of abnormal CRRs to total CRRs ≥ Ratio of abnormal CRR
♦ Number of normal CRRs just before monitored range ≥ Previous
Normal CRR
o Abnormal call occurrence cell detection: Sleeping cell alarm is generated
if all the following conditions are satisfied.
♦ Average number of normal CRRs ≥ Base Normal CRR
♦ Ratio of abnormal CRRs to total CRRs ≥ Ratio of abnormal CRR
5 If the cell does not correspond to any sleeping cell case, and
o If a sleeping cell alarm does not exist, EMS exits sleeping cell detection
operation for the cell.
o If a sleeping cell alarm exists, EMS clears the existing sleeping cell alarm
for the cell.
6 If the cell corresponds to any sleeping cell case, and
o If a sleeping cell alarm does not exist, EMS generates a sleeping cell
alarm. The cause of the sleeping cell alarm can be found in the additional
information of the alarm.
o If a sleeping cell alarm exist, EMS check whether the cause of the alarm is
changed or not.
♦ If the cause of the alarm is not changed, EMS exits sleeping cell
detection operation for the cell.
♦ If the cause of the alarm is changed, EMS updates the sleeping cell
alarm to the changed cause.
Figure below depicts Flow chart of the sleeping cell detection operation.

Confidential
Chapter 9 SON
SYSTEM OPERATION
How to Activate
The following figure shows GUI for sleeping cell detection configuration
parameter setting. Description of each parameter for sleeping cell detection
configuration can be found in the table below.
Figure below depicts Sleeping cell detection configuration list window.

Confidential
Chapter 9 SON
If you want to change the parameters for detecting sleeping cell of an eNB,
double-click the row for the eNB listed in the sleeping cell detection configuration
list. After entering sleeping cell setting window, you can set function ON/OFF,
threshold for each option, and parameters for three periods (range, start hour, and
end hour). By clicking the "Apply" button, you can apply configuration for
sleeping cell detection for the eNB.
Key Parameters
Figure below depicts Sleeping cell setting window.

Confidential
Chapter 9 SON
The detailed descriptions of "Sleeping Cell Setting" parameters are as follows:

Parameters for sleeping cell setting
Parameter Description Range Default Value
Enable This parameter is used to ON/OFF
enable/disable sleeping cell
detection feature on an eNB
basis.
PERIOD_1ST Range (unit: 15 Duration for checking whether 0-48 0
min) the cell is sleeping cell or not
during period first.
Start Hour The start time of the period 0-23 0
first; it should be equal to or
less than the period first end
hour.
End Hour The end time the period first; it 1-24 1
should be equal to or greater
than the period first start hour.
PERIOD_2ND Range (unit: 15 Duration for checking whether 0-48 0
during period second.
Start Hour The start time of the period 0-23 0
second; it should be equal to
or greater than the period first
end hour and should be equal
to or less than the period
second end hour.
End Hour The end time of the period 1-24 1
second; it should be equal to
or greater than the period
second start hour.
PERIOD_ALL Range (unit: 15 Duration for checking whether 1-48 24
when the detection time is not
in Period 1 or 2.
Base Normal CRR Threshold for the number of 0-2684435455 100
normal CRR to prevent false
detection of Sleeping Cell
Previous Normal CRR Threshold for the number of 0-2684435455 100
normal CRR of previous period
to prevent false detection of
Sleeping Cell
Zero Call Normal CRR Threshold for the number of 0-2684435455 0
normal CRR to detect Zero
Call cell
Hand-in fail CRR Threshold for the number of 0-2684435455 10
CRR about hand-in failure to
prevent false detection of Zero
Call cell
Low Call Ratio of normal Threshold for the ratio of 0-100 30
CRR current normal CRR to the that
of previous week to detect Low
Call cell
Ratio of Threshold for the ratio of 0-100 10
abnormal CRR to total CRR to

Confidential
Chapter 9 SON
Parameter Description Range Default Value

abnormal CRR detect Low Call cell
Abnormal Call Ratio of Threshold for the ratio of 0-100 10
abnormal CRR abnormal CRR to total CRR to
detect Abnormal Call cell
Counters and KPIs

Counters related with sleeping cell detection
CSL No_FAULT The call is terminated normally.
S1AP_cs_fallback_triggered It occurs when the call is released
because the inter-RAT redirection
occurs due to CSFB.
S1AP_interrat_redirection It occurs when redirection is
processed normally due to the inter-
FA redirection.
S1AP_redirection_towards_1x The call is released due to redirection
RTT to 1xRTT.
ECC_USER_INACTIVITY It occurs when the MACB block
detects the user inactivity and notifies
the fact to the ECCB block due to no
traffic transmission during the given
period (user inactivity time) for a
specific UE.
ECC_INTER_FA_REDIRECTI It occurs when the redirection to the
ON inter FA is handled.
GUI for Sleeping Cell Detection

Among the eNBs of which condition are not in the exception case for sleeping cell
detection, if a cell corresponds to any sleeping cell case, sleeping cell detection
alarm is generated and is reflected on the Event Viewer as shown in the following
figure.
Figure below depicts Sleeping cell detection alarm is generated.
When a sleeping cell detection alarm is generated, the sleeping cell detection alarm
can be cleared if the cell does not correspond to any sleeping cell case.
The cleared sleeping cell detection alarm is reflected on the Event Viewer as
shown in the following figure.
Figure below depicts Sleeping cell detection alarm is cleared.

Confidential
Chapter 9 SON
REFERENCE
None

Confidential
Chapter 9 SON
LTE-SO0603, Sick Cell Detection

INTRODUCTION
The sick cell detection feature provides the user interface showing whether the cell
state reaches the performance limit based on the performance statistics at the
normal or warning state. Accordingly, the system operator can easily know
whether the cell reaches the performance limit in the use of wireless or backhaul
resources through the sick cell detection feature.
BENEFIT
If a warning frequently occurs in the same cell over a certain period, the system
operator may recognize the necessity of expansion of cell or backhaul.
DEPENDENCY
• Others:
eNB should provide the statistics used for the calculation of the cell state to
EMS.
LIMITATION
EMS can calculate the cell state for 2 hours (1 day) when the statistics for 15
minutes (1 hour) are is used if statistics for the period are stored in EMS.
SYSTEM IMPACT
None
None
Coverage
None
Interfaces
Interface between eNB and EMS may affect the operation of Sick Cell Detection.
FEATURE DESCRIPTION
eNB Load Definition

The Sick Cell Detection feature provides a GUI showing the state (normal or
warning) of a cell that reaches the performance limit in the use of wireless or
backhaul resources for a certain period. The system operator can check the eNB

Confidential
Chapter 9 SON
traffic statistics (minimum, average, and maximum) for a certain period (day,
hour) through the Sick Cell Detection GUI in EMS.
Table below outlines Congestion-indicating Metric by using eNB Counter.
eNB Status Quality Indicator eNB Counter Congestion-indicating Metric
Insufficient air Air Resource Usage DL/UL PRB (*) Usage (Normalized NGBR DL Throughput
resources per UE < DL)
Number of RRC RRC connected User
Connected Users (Normalized NGBR UL Throughput
per UE < UL)
Air Throughput DL/UL Throughput
Insufficient Backhaul Usage Rx/Tx Backhaul Usage (Rx Backhaul Usage > RX) &&
backhaul Air Resource Usage DL/UL PRB (*) Usage (Normalized NGBR DL Throughput
resources per UE < DL)
Number of RRC RRC connected User (Tx Backhaul Usage > TX) &&
Connected Users (Normalized NGBR UL Throughput
Air Throughput DL/UL Throughput per UE < UL)
(*) PRB: Physical Resource Block
Setting the thresholds (DL, UL, RX, TX)

DL, UL, RX, and TX are thresholds to decide the state of the wireless and
backhaul resource. The operator can configure these thresholds according to the
throughput policy and actual network operation scenario. Table 2 shows an
example of default values for the thresholds used in Samsung Sick Cell Detection
feature.
Table below outlines Setting the Thresholds (example).
Threshold Samsung Default Value
DL 512 kbps
UL 128 kbps
RX 70 %
TX 70 %
Criteria for Determining Load Status

Congestion-indicating Metric for Air Resources
In general, wireless resources are preferentially allocated to guaranteed bit rate
(GBR) traffic and the left wireless resources are allocated to non-guaranteed bit
rate (NGBR) traffic. Accordingly, whenever the number of users who use NGBR
traffic increases, the NGBR throughput per user decreases. On assumption that the
service quality of the GBR traffic was guaranteed all the time, the dropping of
NGBR throughput per user below a threshold can be used as a ground for judging
insufficient wireless resources.
At the time, when the user uses the low-capacity service, even though the wireless
resources are sufficient, the NGBR throughput could be reduced. Therefore, the
throughput of the user must be normalized by the PRB usage to judge the
degrading of the throughput by performance limit.
The formula for defining the normalized NGBR throughput of each user is as
follows:

Confidential
Chapter 9 SON
where "Available PRB for NGBR users" means the maximum available wireless
resources to be used for NGBR users and it can be expressed as the sum of current
PRB usage of the NGBR traffic and the remaining PRB usage.
Figure below shows an example of the calculation of the normalized NGBR
throughput by user.
Figure below depicts Example of Normalized NGBR DL Throughput per UE.
Congestion-indicating Metric for Backhaul Resources

If the backhaul resources are not sufficient, the whole throughput is degraded due
to the backhaul bottleneck phenomenon even though the wireless resources are
sufficient. Accordingly, the degradation of the NGBR throughput of the user can
be used as a reference for judging the insufficient backhaul resources. However,
the backhaul usage may easily increase in excess of the threshold even though a
small number of users transmit or receive much traffic. Therefore, the Sick Cell
Detection feature uses both the per-UE NGBR throughput and the backhaul usage
as a ground for the insufficient backhaul resources.
SYSTEM OPERATION

Confidential
Chapter 9 SON
How to Activate
Preconditions
Run GUI for configuration parameter setting.
• In LSM, select PERFORMANCE-Sick Cell Detection.
• Use the [15 Mins] or [Hourly] radio button to set the statistics type to search.
• Use the [Period] field to set a period to search. (Only the statistics data for this
period is retrieved.)
• Use the [Search] button to search the traffic statistics for the period specified.
Refer to the Analysis result column in the results table.

(This is an example of analysis results and User Interface can be upgrade)
• When the data is retrieved, traffic statistics for eNBs registered for the current
LSM is shown in a table. Traffic levels exceeding the judging thresholds are
indicated in red.
• eNBs with the statistics that exceed the processing performance limit are
marked as Warning in the Analysis Result column.
This feature needs not to be deactivated.
Key Parameters
There is no specific parameter associated with this feature.

Confidential
Chapter 9 SON
Counters and KPIs

There is no specific counter or Key Performance Indicator (KPI) associated with
this feature.
REFERENCE
None

Confidential
Chapter 9 SON
LTE-SO0801, PA Bias Control

INTRODUCTION
The purpose of Samsung ES is to reduce the operator’s OPEX and carbon dioxide
emission by saving power consumption of the eNB without any loss of coverage or
quality of service (QoS) during the eNB operation. PA Bias Control function is a
technology that reduces unnecessary energy consumption of the RU by controlling
drain bias voltage of the RU PA while the eNB transmits downlink data.
Samsung eNB operates in "Normal Mode" if PA Bias Control function is not
active. Samsung eNB operates in either "ES Mode" or "Normal Mode" if this
function is active. In ES mode, the drain bias voltage of the RU PA is lowered and
DL traffic is limited according to the changed bias voltage.
Samsung eNB selects either the "Normal Mode" or the "ES Mode" as the
operation mode according to the two types of mechanisms. The following table is
a way of determination for execution mode and its relation to operation style of
Samsung ES.
Operation style of Samsung ES Execution mode determination
Manual Apply Based on pre-defined time schedule
Automatic Apply Based on automatic and periodic traffic analysis
BENEFIT
• Operator can reduce OPEX by saving RU power consumption
• RU power consumption can be saved without coverage loss
DEPENDENCY
E-UTRAN (LTE)
LIMITATION
• PA bias control function cannot be used when RU is shared by multi RATs or
multi eNBs.
• PA bias voltage can be controlled per RU.
• PA bias control function cannot be applied to the cell that has channel
bandwidth with 1.4 MHz and 3 MHz.
• PA bias control function cannot be applied to small cell systems.
• PA bias control function cannot be operated with eMTC function

Confidential
Chapter 9 SON
SYSTEM IMPACT
• LTE-SO0802, Cell on/off in Multi-carrier site
PA Bias Control operates with lower priority than LTE-SO0802. A cell will
execute only LTE-SO0802 if PA Bias Control is configured as function ON
with LTE-SO0802 concurrently.
• LTE-SO0804, DL MIMO TX Branch on/off
PA Bias Control and LTE-SO0804 cannot be configured as function ON
concurrently.
PA Bias Control feature limits the number of allocated RBs in energy saving
mode. The peak throughput is decreased according to the limited number of RBs.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Architecture
The following figure shows the structure of the Samsung ES function. EMS and
eNB have blocks related to the ES function.
Figure below depicts Architecture of Samsung ES Functionality.

Confidential
Chapter 9 SON
The role of the ES-related function of EMS SON-manager is to support the system
operator to set ES function-related settings and to transmit the settings to eNB
OAM. There are three categories of the setup information transmitted to eNB
OAM by the SON-manager.
• Enable/disable settings of the ES function
• Automatic apply (traffic analysis/prediction)-related parameter settings
• Manual apply (pre-defined schedule based ES)-related parameter settings
EMS SON-manager also receives reports on the operation status of eNB ES
function.
Function blocks for the implementation of the ES in eNB are the SON-Agent,
OAM, scheduler and RU control blocks.
1 SON-Agent of eNB
This function block determines the operation mode based on the configured ES
mechanism type and transfers the result of operation mode to the scheduler
and RU PA.
2 OAM of eNB
This function block collects statistics information from the scheduler and
provides it to the SON-Agent. Also, OAM performs as a bridge of information
transfer between EMS SON-Manager and eNB SON-Agent.
3 Scheduler of eNB
This function block performs the resource allocation restriction/release
function according to the operation mode, as instructed by the SON-Agent
function block.
4 RU control of eNB
The RU control block communicates with the SON-Agent function block to
control the bias voltage of the power amplifier according to the operation
mode.
Operation
The following figure shows the overall operating procedure of the PA Bias Control
function described in this document.
The following symbols are used:
• X (i): traffic load estimation value during the time interval [i, i + 1].
• Y (i): traffic load measurement value during the time interval [i, i + 1].
• Mode (i): eNB operation mode during the time interval [i, i + 1].
• Mode (i, p): time interval [i, i + 1] consists of “P” number of short time
intervals, and Mode (i, p) indicates the eNB operation mode during the pth
short time interval.
Figure below depicts Overall operating procedure of Energy Saving function.

Confidential
Chapter 9 SON
Operation when Energy Saving function is disabled

If PA Bias Control function is disabled, eNB runs in normal mode. This function is
disabled if ENERGY_SAVINGS_ENABLE parameter in CHG-SONFN-CELL
command is set to "Off".
Operation when Energy Saving function is running in Manual mode
If PA Bias Control function is enabled in "Manual mode", operator needs to
configure the time schedule table for ES. The time schedule can be configured per
cell in one hour step. This function runs in Manual mode if
ENERGY_SAVINGS_ENABLE parameter in CHG-SONFN-CELL command is
set to "Manual". In manual mode, time schedule for energy saving function can be
set by configuring WEEK_DAY, HOUR and ES_STATE parameters in CHG-ES-
SCHED command. The following table shows the format of time schedule table.
Day of the week Hour block Time interval eNB operation mode

Confidential
Chapter 9 SON
Sunday 0 00:00-01:00 Either normal mode or Energy Saving mode
1 01:00-02:00 Either normal mode or Energy Saving mode
︙ ︙ ︙
Monday 0 00:00-01:00 Either normal mode or Energy Saving mode
︙ ︙ ︙
︙ ︙ ︙ ︙
Saturday 0 00:00-01:00 Either normal mode or Energy Saving mode
︙ ︙ ︙
Operation when Energy Saving function is running in Automatic mode

If PA Bias Control function is enabled in “Automatic mode”, the function runs
based on automatic and periodic traffic analysis. The following actions are
executed every hour.
1 Analyzes the traffic load in the past
2 Using the data, eNB estimates the traffic load required for the next 1 hour.
3 Based on the traffic analysis and estimation, selects whether to run in ES
Mode or Normal Mode for the next 1 hour.
4 Instructs each of the eNB function blocks to perform the actions
corresponding to the selected operation mode.
This function runs in Automatic mode if ENERGY_SAVINGS_ENABLE
parameter in CHG-SONFN-CELL command is set to "Auto".
Traffic Prediction
The traffic load for the upcoming 1 hour is predicted as follow. The larger value
among the two metrics is selected for determination of the execution mode.
• Time series average of the traffic load at the same hour for past D days (The
day D can be set by configuring DATA_VALIDITY parameter in CHG-ES-
COM command)
• Weighted moving average of the traffic load for the recent M hours (Moving
average can be set by configuring MOVING_AVERAGE_VALIDITY and
MOVING_AVERAGE_WEIGHT parameters in CHG-ES-COM command)
Determination of Execution Mode
PA Bias Control function determines the operation mode for the upcoming 1 hour.
If the estimated traffic load is equal or less than the threshold for ES mode, eNB
operates in ES mode.

Confidential
Chapter 9 SON
Operation in ES Mode
If the operation mode is determined as ES mode, RU PA drain bias voltage is
changed to lower level. Moreover, RB allocation is restricted to avoid traffic loss.
• Normal Mode
o PA drain bias voltage: normal (for example, 30 V)
o Available resource block (RB) allocation: 100 % of system bandwidth
(BW)
• ES Mode
o PA drain bias voltage: low (for example, 26 V)
o Available RB allocation: limited to about 50 % of system bandwidth (BW)
The following figure shows an example of PA bias voltage change operation in
RU.
The time duration operated in ES mode for this function is collected as the
following statistics.
• Family name: PA_BIAS_MODE
• Type name: PaBiasModeTime
Conditions for stopping ES Mode
Even when running in the ES Mode, eNB ceases ES mode and reverts to Normal
mode if eNB encounters a sudden increase of traffic or malfunction of eNB. The
operation mode of eNB changes to Normal mode if at least one of the following
conditions is satisfied:
• Traffic load > ES_MODE_RB_ALLOCATION_THRESHOLD *
ALLOCATION_REDUCTION_FACTOR
• BLER for Nth retransmission > Re_Tx_BLER_TH
• Ratio of Nth retransmission > Re_Tx_TH
• Ratio of Radio Link Failure > RLF_TH
These thresholds can be set by configuring RE_TX_THRESHOLD,
BLER_THRESHOLD, RLF_THRESHOLD and
Confidential
Chapter 9 SON
ALLOCATION_REDUCTION_FACTOR parameters in CHG-ES-COM

command.
SYSTEM OPERATION
How to Activate
Preconditions
Run CHG-SONFN-CELL and set ENERGY_SAVINGS_ENABLE to manual or
auto.
Run CHG-SONFN-CELL and set ENERGY_SAVINGS_ENABLE to off.
Key Parameters
parameters.
Parameter Descriptions of RTRV-SONFN-CELL/CHG-SONFN-CELL
ENERGY_SAVINGS_ENAB Controls SON Energy Saving in 3 modes.
LE • Off: The Energy Saving functions except for traffic analysis is disabled.
• Manual: The Energy Saving function in accordance with the schedule set by
the operator is enabled.
• Auto: The Energy Saving functions based on the information obtained from
traffic analysis is enabled.
parameters.
Parameter Descriptions of CHG-ES-SCHED/RTRV-ES-SCHED
WEEK_DAY The day for which the Energy Saving function is operated according to the
schedule.
HOUR This parameter is the activation time (h) of the energy saving feature according
to the schedule.

Confidential
Chapter 9 SON
ES_STATE This setting is required for enabling the energy saving feature using the
schedule.
• Inactive: The energy saving feature does not run.
• Active: The energy saving feature runs based on the schedule.
SCHEDULED_ES_MODE ES Mode type in which the Energy Saving function is operated during one hour
according to the schedule.
Parameter Descriptions of CHG-ES-COM/RTRV-ES-COM

DATA_VALIDITY This parameter is the number of days of traffic analysis to be used in
calculating the estimates for determining Energy Saving (ES) mode. For traffic
estimation, the average traffic load statistics are calculated for the specified
time over the last 15 days or the last 30 days as determined by this parameter.
MOVING_AVERAGE_VALI This parameter determines how many hours of data are used for calculating
DITY the traffic estimates. When this parameter value is determined, it is weighted
with the MOVING_AVERAGE_WEIGHT parameter for calculating the traffic
estimates.
MOVING_AVERAGE_WEIG This parameter is the weight of the recent hours to apply moving average for
HT calculating the traffic estimates. When the number of hours (h) of data to use is
determined by the MOVING_AVERAGE_VALIDITY parameter, this parameter
value is used as weights for data of each hour for calculation. Also, the first
weight of this parameter indicates the most recent hour. If
MOVING_AVERAGE_VALIDITY is 2 hours and this parameter is 50, 50, 0, 0,
0, 0, 0, 0, 0, 0, it means that a weighting of 50 % is applied to the last 2 hours.
RE_TX_THRESHOLD This parameter is the N-1th retransmission (N-1 retransmission count of
PDSCH HARQ) threshold value for determining system abnormality. The unit
used is %. This refers to the ratio of the fourth value over the sum of the first
through Nth values of the number of DL transmission values in the statistics
item DL-HARQ status. If the number of DL transmission value exceeds the
major alarm threshold value, it is deemed as a system abnormality. Before
starting the Self-Organizing Network (SON) Energy Saving (ES) feature, it
must be determined whether the current system status is normal. Therefore, if
the system is in abnormal status, the energy saving mode is disabled and the
normal mode is enabled. The energy saving feature remains disabled until the
system abnormality is resolved.
(N is maximum number of transmission which an operator setting)
In case of RE_TX_THRESHOLD parameter, set the value considering N value
ex) if N = 1 (retransmission 0), RE_TX_THRESHOLD value has to be set 100
(%).
BLER_THRESHOLD This parameter is the N-1th retransmission BLER (PDSCH BLER for the N-1
HARQ retransmission) threshold value for determining system abnormality.
The unit used is %. This means the BLER for the N-1th transmission among
the DL residual BLER values of the statistics item DL-HARQ status. If the DL
residual BLER value exceeds the major alarm threshold value, it is deemed as
a system abnormality. Before starting the Self-Organizing Network (SON)
Energy Saving (ES) feature, it must be determined whether the current system
status is normal. Therefore, if the system is in abnormal status, the energy
saving mode is disabled and the normal mode is enabled. The energy saving
feature remains disabled until the system abnormality is resolved.
RLF_THRESHOLD RLF Threshold for system abnormality.
ALLOCATION_REDUCTION Allocation Reduction Factor for Traffic Abnormality
_FACTOR

Confidential
Chapter 9 SON
AUTO_ES_MODE ES Mode when Energy Saving is operated by Auto Apply.
ABNORMALITY_PERIOD Determining period for traffic and system abnormality.
Parameter Descriptions of RTRV-ES-TYPE

ES_MODE_INDEX This parameter is the index used for saving the information of each Energy
Saving (ES) mode.
ES_MODE_TYPE This parameter is the Energy Saving (ES) mode to be activated when the traffic
load estimate is lower than ES_MODE_ENTERING_THRESHOLD and
ES_MODE_LEAVING_THRESHOLD.
• Normal: Runs on Normal Mode Voltage and RB count.
• Mode (#): Runs with variable voltage and RB count according to the mode.
The higher the mode, the less voltage and RB count are used to save
energy.
ES_MODE_PREDICTION_T ES Mode Prediction Threshold
HRESHOLD
ES_MODE_RB_ALLOCATI ES Mode RB Allocation Threshold
ON_THRESHOLD
Counters and KPIs

1 DL PRB Usage
This is a statistical indicator that indicates the traffic load of each cell.
Statistics for predicting the traffic for each cell
DL PRB Usage TotPrbDl PRB usage of Downlink DTCH traffic
2 DL Status ReTx Ratio and DL Status ReTx BLER

This is a statistical indicator used to determine whether to stop the execution of
Energy Saving mode.
Statistics for determining operation mode of Samsung ES function
Downlink HARQ DLResidualBlerRetrans0 PDSCH BLER for the initial HARQ transmission
Transmission BLER during the collection interval. It is the failure rate
for the initial transmission and is a ratio of the
number of times the first re-transmission was
carried out to the number of times the initial
DLResidualBlerRetrans1 PDSCH BLER for the first HARQ retransmission
DLResidualBlerRetrans2 PDSCH BLER for the second HARQ
retransmission
DLResidualBlerRetrans3 PDSCH BLER for the third HARQ retransmission
DLResidualBlerRetrans4 PDSCH BLER for the fourth HARQ
retransmission

Confidential
Chapter 9 SON

DLResidualBlerRetrans5 PDSCH BLER for the fifth HARQ retransmission
DLResidualBlerRetrans6 PDSCH BLER for the sixth HARQ retransmission
DLTransmissionRetrans0 The cumulated number of initial PDSCH HARQ
transmissions
DLTransmissionRetrans1 The cumulated number of the first PDSCH HARQ
retransmissions
DLTransmissionRetrans2 The cumulated number of the second PDSCH
HARQ retransmissions
DLTransmissionRetrans3 The cumulated number of the third PDSCH
DLTransmissionRetrans4 The cumulated number of the fourth PDSCH
DLTransmissionRetrans5 The cumulated number of the fifth PDSCH HARQ
retransmissions
DLTransmissionRetrans6 The cumulated number of the sixth PDSCH
REFERENCE

Confidential
Chapter 9 SON
LTE-SO0802, Cell On/Off in Multi-carrier Sites

INTRODUCTION
This feature supports macro cell on/off functionality in multi-carrier environment.
By switching off unnecessary cells, the power consumption can be reduced.
Moreover, an RU transmission power can be saved when all cells in the RU are
switched off.
To minimize service impact to UEs, this feature operates in the environment that
multi-carriers are overlapped in a co-located site.
There are two types of cell On/Off mechanisms. One is predefined time schedule-
based cell On/Off and the other is traffic load-based.
BENEFIT
An operator can save OPEX without service impact by saving power consumption
of eNBs in multi-carrier sites. The eNB can be operated with only the required
cells for the low traffic load case by applying this feature.
DEPENDENCY
None
LIMITATION
• Multi cells need to be overlapped in a co-located site.
• This function cannot be operated with eMTC function.
SYSTEM IMPACT
capabilities.
LTE-SO0801, PA Bias Control/LTE-SO0804, DL MIMO Tx Branch on/off
The operator can configure this feature as "ENABLED" or "DISABLED", and so
do LTE-SO0801 and LTE-SO0804. In case LTE-SO0801, LTE-SO0804 and this
feature are configured as "ENABLED", the eNB executes only cell On/Off in
multi-carrier site function because cell On/Off in multi-carrier site feature is
operated with higher priority than LTE-SO0801 and LTE-SO0804.
The cell can be out of service if it is in off state due to cell On/Off in multi-carrier
site feature.

Confidential
Chapter 9 SON
Coverage
The cell can be out of service if it is in off state due to cell On/Off in multi-carrier
site feature. However, it does not make coverage hole because the basic coverage
cell will not become off.
Interfaces
Cell On/Off in multi-carrier site feature affects the following X2 interfaces:
• The eNB Configuration Update message is transferred to notify the result of
cell switch off.
• The Cell Activation message is transferred to cells in off state in case of high
traffic load.
FEATURE DESCRIPTION
Figure below depicts the architecture of cell On/Off function
The operator can configure policies for cell On/Off function using EMS. The
function operates according to the configured policies.
The role of each blocks participating in this function is as follows.
• EMS: The EMS provides GUI for configuring policies for operator and
transfers the configured policies to eNB.
• Call S/W block: The Call S/W block executes cell On/Off function according
to the policies configured by operator. It releases calls in the cell in case of cell
switch off condition and transfer the result of cell switch off to neighbor cells.
Moreover, cell activation can be executed when traffic load is higher than over

Confidential
Chapter 9 SON
pre-configured threshold.
• OAM S/W block: The OAM S/W block executes TX path on/off in RU by
sending message according to the result of this function.
Operation
The concept of cell off operation is depicted in figure below.
The cell switch off operation can be executed only for the cells that are co-located
in a same site. The target cell to switch off will release existing call by forced
handover. When all calls are released in the cell, the cell is switched off and the
cell is managed as dormant cell.
Cell On/Off Schemes
There are two types of cell On/Off schemes:
• Predefined time schedule-based
• Traffic load-based
In case of time schedule-based scheme, the eNB executes the cell On/Off function
based on the pre-configured time schedule by operator. Operator can configure
time schedule of cell On/Off in one-hour step. The eNB executes cell switch off at
the pre-configured time.
In case of traffic load based scheme, the eNB executes the cell On/Off function
based on the traffic load history. The eNB executes traffic load analysis in every
hour. For specific time duration, the eNB executes cell switch off if the average
traffic load is lower than pre-defined threshold.
Detailed Process of Cell Off
The detailed process of cell Off is as follow.
1 Policy configuration
The operator needs to configure the following policies for cell On/Off function
and can configure the policies by EMS GUI or CLI.
o Cell On/Off scheme: Time schedule-based/Traffic load-based

Confidential
Chapter 9 SON
(ES_CELL_OFF_MODE in CHG-SONFN-CELL CLI or EMS GUI)

o Cell Off options: Forced HO, Timer (ES_CELL_OFF_MODE,
ES_CELL_OFF_TIMER_ENABLE, and ES_CELL_OFF_TIMER in
CHG-GRCREL-CONF CLI or EMS GUI)
o FA priority for cell On/Off (PRIORITY_FOR_ES_CELL_ON_OFF in
CHG-EUTRA-FA CLI or EMS GUI)
o Traffic threshold for cell On/Off (can be set by only EMS GUI)
o Co-located NBR cells (can be set by only EMS GUI)
o Time schedule for Time-schedule based scheme (can be set by only EMS
GUI)
o Tx power control option (can be set by only EMS GUI)
2 Deciding whether to try cell Off
The eNB decides whether to try cell off or not by two kinds of cell On/Off
scheme. One is predefined time schedule-based and the other is traffic load-
based.
3 Deciding whether to execute cell Off
The eNB monitors traffic load statistics and decide whether to execute cell
On/Off by checking the latest traffic load statistics. If the latest traffic load
statistics is higher than pre-defined threshold, the eNB does not execute cell
Off and tries again at next statistic collecting duration.
4 Executing cell Off
If cell Off execution is decided, the eNB does not allow newly incoming call
to the cell. Moreover, forced handover can be executed for faster cell Off
execution according to operator configuration. In this case, forced handover
for the emergency calls or high priority calls can be prohibited. Cell Off is
executed if no call exists in the cell, and the result of cell Off is transferred to
neighbor cells.
The time duration of Cell Off is collected as the following statistics.
o Family name: CELL_UNAVAILABLE
o Type name: CellUnavailableTimeES
If tx power control option is configured, tx power control is controlled instead
of executing Cell Off.
The operational flow of cell Off is depicted in figure below.

Confidential
Chapter 9 SON
Detailed Process of Cell On

1 Transferring Cell Activation message
The eNB checks traffic load statistics of active cell and transfers Cell
Activation message to dormant cell among co-located cells if traffic load is
higher than pre-defined threshold.
2 Executing cell On
The dormant cell that receives Cell Activation message executes cell On.
The operational flow of cell On is depicted in figure below.

Confidential
Chapter 9 SON
SYSTEM OPERATION
How to Activate
Preconditions
• License is needed to use this feature.
EUTRA-FA.
• Use the command CHG-SONFN-CELL to set ES_CELL_OFF_MODE to
ScheduleBased or trafficBased.
• If you want to use forced handover for faster graceful cell Off, use the
command CHG-GRCREL-CONF to set ES_CELL_OFF_MODE to
"withForcedHo".
• If you want to use timer-based release for active calls, use the command CHG-
GRCREL-CONF to set ES_CELL_OFF_TIMER_EABLE to "On".
• Use the command CHG-GRCREL-CONF to set ES_CELL_OFF_TIMER,

Confidential
Chapter 9 SON
when you want to reconfigure timer for timer-based release.

• If FA priority of the cell is set to 7, the cell is not off although
ES_CELL_OFF_MODE is activated.
The operator can disable this feature by settings ES_CELL_ON_OFF_ENABLE to
Off using CHG-SONFN-CELL command.
Key Parameters
Parameter Descriptions of RTRV-SONFN-CELL/CHG-SONFN-CELL
ES_CELL_ON_OFF_ENABLE This parameter indicates whether to enable the ES Cell OnOff.
There are 3 modes (Off, ScheduleBased, TrafficBased). If the parameter is
Off, this cell is excluded CellOnOff.
PRIORITY_FOR_ES_CELL_ This is priority for FA of cell on target. The cells of FA allocated priority 7 are
ON_OFF excluded in candidate cell off.
In the dedicated Cell On/Off GUI on LSM

CELL_OFF_LOAD_THRESH This is a threshold parameter for triggering cell off.
OLD A cell load is lower than this threshold for triggering cell off.
CELL_ACT_LOAD_THRESH This is a threshold parameter for activating cell on.
OLD It is lower than this threshold for triggering cell off.
When a cell load is bigger than this threshold, the cell activates NBR dormant
cells.
CELL_OFF_RELIABILITY This parameter is a condition for reliability that shall be satisfied in cell off
decision.
A ratio of sum of bin counts shall excess this value for cell off.
CELL_ACT_RELIABILITY This parameter is a condition for reliability that shall be satisfied in cell
activation decision.
A ratio of sum of bin counts shall excess this value for cell activation.
Parameter Descriptions of RTRV-GRCREL-CONF/CHG-GRCREL-CONF

ES_CELL_OFF_MODE This parameter is used to set cell-off for energy saving operation mode when
estate, and esModeType (of CellEnergySavingStatus) is transited to enable
and cell_off. There are normal and withForcedHo that triggers On-Demand
Forced HO at transition to cell-off.
ES_CELL_OFF_TIMER_ENA This parameter is used to enable or disable timer operation. If you set this

Confidential
Chapter 9 SON
BLE parameter to ON, the timer is triggered at transition to set cell-off for energy
saving. And then, it makes eNB forcibly release remained active calls in the
cell under cell-off for energy saving, when timer is expired.
ES_CELL_OFF_TIMER This parameter is used to set timer duration in esCellOffTimer.
Counters and KPIs

ODHO_X2_OUT OnDemandHoOutAtt This type is counted by sending X2 handover
request with Switch off ongoing cause
OnDemandHoOutSucc This type is counted by receiving UE context
release command triggered by On-demand
handover in Source eNB
ODHO_X2_IN OnDemandHoInAtt This type is counted by receiving X2 handover
request with Switch off ongoing cause
OnDemandHoInSucc This type is counted by sending UE context
release command triggered by On-demand
handover from Source eNB
ODHO_S1_OUT OnDemandHoOutAtt Counted when the cause of S1 HO Request
transmission is Miscellaneous::O & M
Intervention.
OnDemandHoOutSucc Counted if the UE performs OnDemand Ho-
based HO when the Source eNB successfully
receives UE Context Release Request message.
OnDemandHoOutAttTo Counted when the cause of UTRAN HO Request
UTRAN transmission through S1 is Miscellaneous::O & M
Intervention.
OnDemandHoOutSuccT Counted if the UE performs OnDemand Ho-based
oUTRAN HO when the Source eNB successfully receives
UE Context Release Request message.
ODHO_S1_IN OnDemandHoInAtt Counted when the cause of HO Request
reception through S1 is Miscellaneous::O & M
Intervention.
OnDemandHoInSucc Counted if the UE performs OnDemand Ho-based
HO when the target eNB successfully sends HO
Notify message.
ODHO_INTRA_OUT OnDemandHoIntraOutA Counted when the eNB attempts Intra HO out
tt caused by OnDemand forced HO.
OnDemandHoIntraOutS Counted if the UE performs OnDemand forced
ucc HO when the Source eNB successfully successes
Intra HO out.
ODHO_INTRA_IN OnDemandHoIntraInAtt Counted when the eNB receives a request of Intra
Hand-In caused by OnDemand forced HO.
OnDemandHoIntraInSu Counted if the UE performs OnDemand Ho-based
cc HO when the target eNB successfully Hand-in.
ODHO_REDIRECTION RedirectionToLTEByOn This type is counted by conducting redirection to
DemandHo LTE (On-demand handover)
RedirectionToWCDMAB This type is counted by conducting redirection to
yOnDemandHo WCDMA (On-demand handover)
RedirectionToGERANB This type is counted by conducting redirection to
yOnDemandHo GERAN (On-demand handover)

Confidential
Chapter 9 SON

RedirectionToHRPDBy This type is counted by conducting redirection to
OnDemandHo HRPD (On-demand handover)
CcoToGERANByOnDe This type is counted by conducting CCO to
mandHo GERAN (On-demand handover)
ODHO_TIMER_RELEASE ReleaseCntByTimer Forced released UE by timer expiration
REFERENCE
[1] 3GPP TS 36.423 (Rel.11)
[2] 3GPP TS 32.551 (Rel.11)
[3] 3GPP TS 36.300 (Rel.12)

Confidential
Chapter 9 SON
LTE-SO0804, DL MIMO TX Branch On/Off

INTRODUCTION
Energy Saving (ES) function controls the Downlink (DL) Transmitter (Tx) Branch
to lower the power consumption of eNB. The purpose of Samsung ES function is
to reduce the operator’s OPEX and carbon dioxide emission by saving power
consumption of eNB without any loss of coverage or QoS during eNB operation.
DL Tx Branch On/Off function disables some transmission branches of the RU
with two or more downlink transmitting branches A branch means the combination
of PA modules and connected antennas.
Samsung eNB operates in the "Normal Mode" if DL Tx Branch On/Off function is
not active. eNB operates either in "ES Mode" or "Normal Mode" if this function is
active. In ES mode, some of the RU Tx branches are switched off and DL traffic is
limited according to the decreased number of RU Tx branches.
Samsung eNB selects either the "Normal Mode" or the "ES Mode" as the
operation mode according to the two types of mechanisms. The following table is
a way of determination for execution mode and its relation to operation style of
Samsung ES.
Types of Samsung ES mechanism Execution mode determination
Manual Apply Based on pre-defined time schedule
Automatic Apply Based on automatic and periodic traffic analysis
BENEFIT
• Operator can reduce OPEX by saving RU power consumption
• RU power consumption can be saved without coverage loss
DEPENDENCY
• HW dependency:
Channel card with Samsung Baseband Modem 8200 or later.
E-UTRAN (LTE)
LIMITATION
• DL MIMO Tx Branch on/off function cannot be used when RU is shared by
multi RATs or multi eNBs.
• DL MIMO Tx Branch on/off function cannot be adapted to the cell that has
channel bandwidth with 1.4 MHz and 3 MHz.
• DL MIMO Tx Branch on/off function cannot be applied to small cell systems.

Confidential
Chapter 9 SON
• DL MIMO Tx Branch on/off function can be applied to the following

configurations: 2CRS 2Tx, 2CRS 4Tx with CDD and 2CRS 8Tx with CDD
(Cannot be executed when Beamforming is operating)
• DL MIMO Tx Branch on/off function cannot be operated with eMTC function
SYSTEM IMPACT
• LTE-SO0801, PA Bias Control
DL MIMO Tx Branch on/off and LTE-SO0801 cannot be configured as
function ON concurrently.
• LTE-SO0802, Cell on/off in Multi-carrier site
DL MIMO Tx Branch on/off operates with lower priority than LTE-SO0802.
A cell will execute only LTE-SO0802 if DL MIMO Tx Branch on/off is
configured as function ON with LTE-SO0802 concurrently.
DL MIMO Tx Branch on/off feature limits the number of allocated RBs in energy
saving mode. The peak throughput is decreased according to the limited number of
RBs.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
Architecture
The following figure shows the structure of the Samsung ES function. EMS and
eNB have blocks related to the ES function.
Figure below depicts Structure of Samsung ES function

Confidential
Chapter 9 SON
The role of the ES block of EMS SON-manager is to support the system operator
to set ES function-related settings and to transmit the settings to eNB OAM. There
are three categories of the setup information transmitted to eNB OAM by the
SON-manager.
• Enable/disable settings of the ES function
• Automatic apply (traffic analysis/prediction)-related parameter settings
• Manual apply (pre-defined schedule based ES)-related parameter settings
EMS SON-manager also receives reports on the operation status of eNB ES
function.
Function blocks for the implementation of the ES in eNB are the SON-agent,
OAM, MODEM, scheduler and RU.
1 eNB SON-agent determines eNB’s operating mode based on the configured
ES mechanism type and transfers the result of operation mode to the
MODEM, scheduler and the RU.
2 eNB OAM collects PM statistics information and provides it to SON-Agent.
Also, OAM performs as a bridge of information transfer between EMS SON-
manager and eNB SON-agent.
3 When eNB SON-agent decides eNB's operating mode, eNB scheduler block
limits the number of scheduled RBs or releases the limitation of the number
according to the decided eNB operating mode. In addition, the scheduler
delivers the operating mode to modem.
4 The modem combines Tx signal of all paths to keep CRS signal
5 The RU control block communicates with the SON-Agent function block to
control the Tx branch on/off according to the operation mode
Operation
The following figure shows the overall procedure of DL MIMO Tx Branch on/off
function described in this document.
The following symbols are used:
• X (i): traffic load estimation value during the time interval [i, i + 1].
• Y (i): traffic load measurement value during the time interval [i, i + 1].
• Mode (i): eNB operation mode during the time interval [i, i + 1].
• Mode (i, p): time interval [i, i + 1] consists of “P” number of short time
intervals, and Mode (i, p) indicates the eNB operation mode during the pth
short time interval.
Figure below depicts the Overall procedure of Samsung ES function.

Confidential
Chapter 9 SON
Operation when Energy Saving function is disabled

If DL MIMO Tx Branch on/off function is disabled, eNB runs in normal mode.
This function is disabled if ENERGY_SAVINGS_ENABLE parameter in CHG-
SONFN-CELL command is set to "Off".
Operation when Energy Saving function is running in Manual mode

If DL MIMO Tx Branch on/off function is enabled in “Manual mode”, operator

Confidential
Chapter 9 SON
needs to configure the time schedule table for ES. The time schedule can be
configured per cell in one hour step. This function runs in Manual mode if
set to "Manual". In manual mode, time schedule for energy saving function can be
set by configuring WEEK_DAY, HOUR and ES_STATE parameters in CHG-ES-
SCHED command.
Sunday 0 00:00-01:00 Either normal mode or Energy Saving mode
︙ ︙ ︙
Monday 0 00:00-01:00 Either normal mode or Energy Saving mode
︙ ︙ ︙
︙ ︙ ︙ ︙
Saturday 0 00:00-01:00 Either normal mode or Energy Saving mode
︙ ︙ ︙
Operation when Energy Saving function is running in Automatic mode

If the system operator enables the Energy Saving function in "Automatic mode",
energy saving function runs based on automatic and periodic traffic analysis. In
automatic mode, the SON-Agent function block of eNB performs the following
actions every hour.
1 Analyzes the traffic load for "D" number of days in the past leading up to the
present moment.
2 Using this data, estimates the traffic load required for the next 1 hour.
3 Based on the traffic analysis and estimation, selects whether to run in ES
Mode or Normal Mode for the next 1 hour.
4 Instructs each of the eNB function blocks to perform the actions
corresponding to the selected operation mode.
Energy Saving function runs in Automatic mode if
set to "Auto".
Traffic Prediction
The traffic load for the upcoming 1 hour is predicted as follow. The larger value
among the two metrics is selected for determination of the execution mode.
• Time series average of the traffic load at the same hour for past D days (The
day D can be set by configuring DATA_VALIDITY parameter in CHG-ES-
COM command)

Confidential
Chapter 9 SON
• Weighted moving average of the traffic load for the recent M hours (Moving
average can be set by configuring MOVING_AVERAGE_VALIDITY and
MOVING_AVERAGE_WEIGHT parameters in CHG-ES-COM command)
Determination of Execution Mode
DL MIMO Tx Branch on/off function determines the operation mode for the
upcoming 1 hour. If the estimated traffic load is equal or less than the threshold for
ES mode, eNB operates in ES mode.
Operation in ES Mode
If the operation mode is determined as ES mode, some of Tx branches are
disabled. Moreover, RB allocation is restricted to avoid traffic loss.
The following is an example of the Normal mode and ES mode operation in case
of the RU with two Tx branches:
• Normal Mode
o Tx branch 0 (Tx antenna-0 and the related PA module): enabled
o Available RB allocation: 100 % of system BW
• Saving Mode
o Tx branch 1 (Tx antenna-1 and the related PA module): disabled
o Available RB allocation: about half of system BW
The time duration operated in ES mode for this function is collected as the
following statistics.
• Family name: DL_MIMO_TX_PATH_OFF_MODE
• Type name: DLMimoTxPathOffModeTime
Conditions for stopping ES Mode
Even when running in the ES Mode, eNB ceases ES mode and reverts to Normal
mode if eNB encounters a sudden increase of traffic or malfunction of eNB. The
operation mode of eNB changes to Normal mode if at least one of the following
conditions is satisfied:
• Traffic load > ES_MODE_RB_ALLOCATION_THRESHOLD *
ALLOCATION_REDUCTION_FACTOR
• BLER for Nth retransmission > Re_Tx_BLER_TH
• Ratio of Nth retransmission > Re_Tx_TH
• Ratio of Radio Link Failure > RLF_TH
These thresholds can be set by configuring RE_TX_THRESHOLD,
BLER_THRESHOLD, RLF_THRESHOLD and
ALLOCATION_REDUCTION_FACTOR parameters in CHG-ES-COM
command.

Confidential
Chapter 9 SON
SYSTEM OPERATION
How to Activate
Preconditions
A valid license key is required to activate this feature.
Run CHG-SONFN-CELL and set ENERGY_SAVINGS_ENABLE to manual or
auto.
Run CHG-SONFN-CELL and set ENERGY_SAVINGS_ENABLE to off.
Key Parameters
parameters.
ENERGY_SAVINGS_ENABL Controls SON Energy Saving in 3 modes.
E • Off: The Energy Saving functions except for traffic analysis is disabled.
• Manual: The Energy Saving function in accordance with the schedule set
by the operator is enabled.
• Auto: The Energy Saving functions based on the information obtained from
traffic analysis is enabled.
parameters.
Parameter Descriptions of CHG-ES-SCHED/RTRV-ES-SCHED
WEEK_DAY The day for which the Energy Saving function is operated according to the
schedule.
HOUR This parameter is the activation time (h) of the energy saving feature
according to the schedule.
ES_STATE This setting is required for enabling the energy saving feature using the
schedule.

Confidential
Chapter 9 SON
• Inactive: The energy saving feature does not run.
• Active: The energy saving feature runs based on the schedule.
SCHEDULED_ES_MODE ES Mode type in which the Energy Saving function is operated during one
hour according to the schedule.
Parameter Descriptions of CHG-ES-COM/RTRV-ES-COM

DATA_VALIDITY This parameter is the number of days of traffic analysis to be used in
calculating the estimates for determining Energy Saving (ES) mode. For
traffic estimation, the average traffic load statistics are calculated for the
specified time over the last 15 days or the last 30 days as determined by this
parameter.
MOVING_AVERAGE_VALIDI This parameter determines how many hours of data are used for calculating
TY the traffic estimates. When this parameter value is determined, it is weighted
with the MOVING_AVERAGE_WEIGHT parameter for calculating the traffic
estimates.
MOVING_AVERAGE_WEIGH This parameter is the weight of the recent hours to apply moving average for
T calculating the traffic estimates. When the number of hours (h) of data to use
is determined by the MOVING_AVERAGE_VALIDITY parameter, this
parameter value is used as weights for data of each hour for calculation.
Also, the first weight of this parameter indicates the most recent hour. If
MOVING_AVERAGE_VALIDITY is 2 hours and this parameter is 50, 50, 0, 0,
0, 0, 0, 0, 0, 0, it means that a weighting of 50 % is applied to the last 2
hours.
RE_TX_THRESHOLD This parameter is the N-1th retransmission (N-1 retransmission count of
PDSCH HARQ) threshold value for determining system abnormality. The unit
used is %. This refers to the ratio of the fourth value over the sum of the first
through Nth values of the number of DL transmission values in the statistics
item DL-HARQ status. If the number of DL transmission value exceeds the
major alarm threshold value, it is deemed as a system abnormality. Before
starting the Self-Organizing Network (SON) Energy Saving (ES) feature, it
must be determined whether the current system status is normal. Therefore,
if the system is in abnormal status, the energy saving mode is disabled and
the normal mode is enabled. The energy saving feature remains disabled
until the system abnormality is resolved.
(N is maximum number of transmission which Operator Setting)
In case of RE_TX_THRESHOLD parameter, set the value considering N
value
Ex.) if N = 1 (retransmission 0), RE_TX_THRESHOLD value has to be set
100 (%).
BLER_THRESHOLD This parameter is the N-1th retransmission BLER (PDSCH BLER for the N-1
HARQ retransmission) threshold value for determining system abnormality.
The unit used is %. This means the BLER for the N-1th transmission among
the DL residual BLER values of the statistics item DL-HARQ status. If the DL
residual BLER value exceeds the major alarm threshold value, it is deemed
as a system abnormality. Before starting the Self-Organizing Network (SON)
Energy Saving (ES) feature, it must be determined whether the current
system status is normal. Therefore, if the system is in abnormal status, the
energy saving mode is disabled and the normal mode is enabled. The energy
saving feature remains disabled until the system abnormality is resolved.
RLF_THRESHOLD RLF Threshold for system abnormality.
ALLOCATION_REDUCTION_ Allocation Reduction Factor for Traffic Abnormality

Confidential
Chapter 9 SON
FACTOR
AUTO_ES_MODE ES Mode when Energy Saving is operated by Auto Apply.
ABNORMALITY_PERIOD Determining period for traffic and system abnormality.
Parameter Descriptions of RTRV-ES-TYPE

ES_MODE_INDEX This parameter is the index used for saving the information of each Energy
Saving (ES) mode.
ES_MODE_TYPE This parameter is the Energy Saving (ES) mode to be activated when the
traffic load estimate is lower than ES_MODE_ENTERING_THRESHOLD and
ES_MODE_LEAVING_THRESHOLD.
• Normal: Runs on Normal Mode Voltage and RB count.
• Mode (#): Runs with variable voltage and RB count according to the mode.
The higher the mode, the less voltage and RB count are used to save
energy.
ES_MODE_PREDICTION_TH ES Mode Prediction Threshold
RESHOLD
ES_MODE_RB_ALLOCATIO ES Mode RB Allocation Threshold
N_THRESHOLD
Counters and KPIs

The eNB SON agent predicts the traffic for each cell during the specified time
interval by using the following PM statistic data items.
Total PRB Usage TotPrbDLAvg The average use rate for PRBs used to transmit
PDSCH/PBCH during the collection interval.
REFERENCE

Confidential
Chapter 9 SON
LTE-SO0807, Dynamic PA on/off

INTRODUCTION
Dynamic PA on/off reduces energy consumption of the RU by executing PA
on/off dynamically.
RU monitors DL traffic and executes symbol level PA on/off in real time.
PA is off if baseband IQ data is 0 for a specific time duration, and it is on if
baseband IQ data is not 0.
BENEFIT
Operator can reduce OPEX by saving RU power consumption
DEPENDENCY
• HW dependency:
RU should support Dynamic PA on/off function
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
Overall Procedure
The overall procedure of Dynamic PA on/off function is as follow.
If this function is activated by operator, the function activation message is
transferred to RU. Then, RU will execute symbol level PA on/off according to DL
traffic.
If this function is deactivated by operator, the function deactivation message is
transferred to RU. Then, RU will not execute PA on/off even if there is no DL
traffic.
The function is activated or deactivated by setting
DYNAMIC_PA_CTRL_SWITCH parameter in CHG-RRH-CONF command.

Confidential
Chapter 9 SON
Dynamic PA on/off Operation

When the function is activated, RU monitors and analyzed baseband IQ data in
real time. PA bias is off if the baseband IQ data is 0 for a specific time duration.
Following figure represents an example of Dynamic PA on/off operation. RU PA
is on in case that symbols are used by control or data channels. RU PA is off in
case of unused symbols.
SYSTEM OPERATION
How to Activate

Confidential
Chapter 9 SON
Preconditions
RRH has to support Dynamic PA on/off Function.
Run CHG-RRH-CONF and Set DYNAMIC_PA_CTRL_SWITCH to On.
Run CHG-RRH-CONF and Set DYNAMIC_PA_CTRL_SWITCH to Off.
Key Parameters
feature.
parameters.
DYNAMIC_PA_CTRL_SWIT This determines whether to enable or disable this feature:
CH • 0 (Off): This feature is not used.
• 1 (On): This feature is used.
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
Chapter 9 SON
LTE-SO0811, Channel Card On/Off

INTRODUCTION
The existing energy saving functions concentrated on reducing power consumption
of RU. The Channel Card On/Off feature saves power consumption of DU. Power
consumption needed for a channel card can be saved when all cells in the channel
card are switched off.
BENEFIT
This feature saves power consumption of DU.
DEPENDENCY
• HW dependency:
o Modem on/off support: LCC1-B6A and LCC4
o Can be supported for Macro system
• Prerequisite Features: LTE-SO0802, Cell On/Off in Multi-carrier Site
LIMITATION
The first modem in a channel card is excluded for the target of Modem on/off
function.
SYSTEM IMPACT
capabilities.
None
It requires a couple of minutes to switch On a channel card.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
To activate this feature, the LTE-SO0802, Cell on/off in Multi-carrier site feature

Confidential
Chapter 9 SON
should be supported. ES_CELL_ON_OFF_ENABLE in RTRV-SONFN-CELL

indicates whether LTE-SO0802 feature is activated or deactivated. The detailed
configuration method of the feature is described in the feature description of LTE-
SO0802.
In case that the operator activates the Channel Card On/Off feature; a channel card
is turned Off when all cells in the channel card are switched off by LTE-SO0802
function.
Inversely, a channel card that is already turned Off by Channel Card On/Off
feature is turned On when at least one cell in the channel card is switched on by
LTE-SO0802 function. The function is activated or deactivated by setting
ES_CC_POWER_OFF_ENABLE in CHG-SONFN-ENB command.
If various carriers exist in a channel card, the channel card Off event occurs rarely.
The Modem On/Off function can be supported for the cases. In case that the
Modem On/Off function is activated by operator, a modem will be turned Off
when all cells in the modem are switched Off by LTE-SO0802 function.
Inversely, a modem that is already turned Off by Modem On/Offfunction will be
turned On when at least one cell in the modem is switched On by LTE-SO0802
function.
Figure below is an example of channel card off scenario.
FA#2 cells (cell#0, cell#1 and cell#2) are grown at channel card#2. All FA#2 cells
can be switched Off by cell On/Off function. Because FA#0 and FA#1 cells exist
at the co-located site, switching Off all of the FA#2 cells does not make coverage
hole. Channel card#2 will be turned Off after all FA#2 cell are switched Off.

Confidential
Chapter 9 SON
SYSTEM OPERATION
How to Activate
Preconditions
Run CHG-SONFN-CELL and set ES_CELL_ON_OFF_ENABLE to ON for all
cell in channel card.
• Run CHG-SONFN-ENB and set ES_CC_POWER_OFF_ENABLE to ON.
o If all cells in the channel card are off by energy saving cell off function,
then the channel card goes off.
• Run CHG-SONFN-ENB and set ES_DSP_POWER_OFF_ENABLE to ON.
o If all cells in the DSP are off by energy saving cell off function, then the
DSP goes off.
• Run CHG-SONFN-ENB and set ES_CC_POWER_OFF_ENABLE to OFF.
• Run CHG-SONFN-ENB and set ES_DSP_POWER_OFF_ENABLE to OFF.
Key Parameters
parameters as a table callout.
Parameter Descriptions CHG-SONFN-CELL/RTRV-SONFN-CELL
This parameter indicates whether to enable the ES Cell OnOff. There are
ES_CELL_ON_OFF_ENABLE 3modes (Off, ScheduleBased, TrafficBased). If the parameter is Off, this cell
is excluded CellOnOff.
Parameter Descriptions Parameter Descriptions CHG-SONFN-ENB/RTRV-

SONFN-ENB
Whether to enable the channel card power off for energy saving function.
ES_CC_POWER_OFF_ENABL
E
• On: The function is turned on.
Whether to enable the DSP power off for energy saving function.
ES_DSP_POWER_OFF_ENAB
LE
• On: The function is turned on.

Confidential
Chapter 9 SON
There are no specific parameters for configuration.
To check the power on/off status of channel, use below command
Parameter Descriptions of RTRV-PRCES-STS
This parameter is the id for each unit. Each id is unique within the specified
UNIT_ID
unit type
The status of channel card power off by energy saving function.
• NORMAL: the status of channel card is not controlled by energy saving.
ES_CC_STATE
• ES_POWER_OFF: the status of channel card is power off by energy
saving.
The status of DSP power off by energy saving function.
The status of DSP power off by energy saving function.
• NOT_SUPPORTED: the DSP power control by energy saving is not
ES_DSP_STATE
supported.
• NORMAL: the status of DSP is not controlled by energy saving.
• ES_POWER_OFF: the status of DSP is power off by energy saving.
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
Chapter 9 SON
LTE-SO0901, Minimization Drive Test

Optimization
INTRODUCTION
Minimization of Drive Test (MDT) is a standardized mechanism to collect the
network performance measurements from the commercial UEs with possibly the
location information. The collected UE measurement results can be utilized for
various purposes, for example, network parameter optimization, coverage hole
detection, and so on. Operator can save the cost for network optimization by using
MDT feature.
Samsung MDT supports two modes of operations, that is, Immediate MDT and
Logged MDT. Immediate MDT is targeted on the UEs in Active mode while
Logged MDT is performed by the UEs in Idle mode.
BENEFIT
• Operator can save the cost for collecting the network performance
measurement data.
• End-used service quality can be enhanced thanks to efficient network
optimization conducted by using MDT data
DEPENDENCY
MME TCE server
E-UTRAN (LTE)
• Others:
For Signaling-based MDT, the core network entities shall support the
corresponding functions.
LIMITATION
• For Logged MDT, UE shall support the corresponding functions (Rel.10 or
later).
• Number of UEs for reporting M2, M3 and M4 is limited to 6 UEs per cell.
• Collection periods of M2, M3, M4 are fixed as 2.56 s.
• M5 (Scheduled IP Throughput) and Angle of Arrival (in ECID raw data)
information trace is not available.

Confidential
Chapter 9 SON
SYSTEM IMPACT
None
None
Coverage
None
Interfaces
Added or modified MDT information may affect interface with External Server, so
it is required to discuss in advance.
FEATURE DESCRIPTION
Optimization of radio network performance is very important task for mobile
operators. Conventionally, operators conduct drive test to collect the radio
measurement, and parameter optimization is performed based on the gathered
information. Mobile operators have spent a lot of time and money for conventional
drive test and network optimization.
Minimization of Drive Test (MDT) feature is introduced in 3GPP Rel.10 to
provide more cost-efficient method to measure and optimize the network
performance. Since the mobile devices exist over whole network areas, MDT
procedure utilizes UE's measurement capability to acquire the information of
network. Through the standardized MDT procedures, operators order some UEs to
measure the network performance, and collect the measured data in the server
which is called Trace Collection Entity (TCE) in 3GPP specification. Then, the
collected information can used for many purposes including coverage hole
detection, capacity optimization, and so on.
MDT Configuration parameters may be delivered to the target UE and
measurement data can be collected by the UE itself during idle state (Logged
MDT), or MDT data collection can be done at the serving eNB by reusing the
existing RRM procedures while the target UE stays in connected state (Immediate
MDT).
There are two types of methods to configure and manage MDT, which are
Signaling-based MDT and Management-based MDT.
• Signaling based MDT: Used to collect the measurement data of a specific UE
based on IMSI or IMEI SV. The MDT configuration message is sent from
MME to eNB.
• Management based MDT: Used to collect the measurement data in a specific
area. The MDT configuration message is sent directly from RAN OAM server
to (set of) cells without specifying target UEs. Some UEs in the area are
chosen by eNB for MDT operations.
Because MDT management reuses the existing Trace architecture, the two
methods have almost same architecture as Signaling-based and Management-based
Trace methods, respectively.
Confidential
Chapter 9 SON
Table below summarizes the differences of Signaling and Management-based

MDTs.
Signaling-based MDT Management-based MDT
Configuration path (Core) OAM à HSS à MME  (RAN) OAM à eNB
eNB
Reusing trace procedures Signaling based trace, for Management based trace, for
example, Call Trace example, Cell Traffic Trace
Target of configuration Specific subscriber (IMSI) or Specific area, for example, cells,
equipment (IMEI, IMEI SV) TAs
Target UE selection Target UE selection by OAM Target UE selection by eNB
User consent checking User consent checking of the User consent checking is done by
specific UE can be done by HSS eNB at UE selection based on the
before delivering the configuration saved UE context
message.
Session continuity on cell change MDT parameter transfer during No MDT session continuity on cell
handover change (Only user consent
information can be transferred)
Supported MDTs Both Logged and Immediate MDT Both Logged and Immediate MDT
In Signaling-based MDT, a specific UE is chosen by OAM based on IMSI or IMEI

SV. The configuration message including the corresponding MDT parameters is
sent to HSS for checking the user consent. If subscription data of the user allows
MDT, the HSS sends MDT activation message to serving MME of the UE, and the
MME sends it to the serving eNB.
In Management-based MDT, a specific area is chosen for measurement data
collection with MDT parameters. The eNBs in the area choose some UEs and data
collection is done based on the received configuration. The user consent for MDT
is saved in UE context generally during UE attach, and hence the serving eNB can
choose only the UEs which allow Management based MDT data collection.
Figure below depicts concepts for Signaling and Management-based MDT
configurations.

Confidential
Chapter 9 SON
For UE selection in Management-based MDT, Samsung MDT provides the

following options to restrict the scope of chosen users.
• UE capability option: 1) All UEs, 2) Rel. 10 or later UEs only, 3) Rel. 10 or
later + standalone GNSS capable UEs only. Operator may want to collect only
the measurement data with high accuracy.
• UE pickup rate: The probability that a UE is chosen for MDT operation when
the UE satisfies all the requirements for UE selection. Operator may not want
to get measurement data from all the UEs who satisfy the requirements due to
large overhead.
In the RAN’s configuration and operation aspects, there are two types of MDT,
which are Immediate and Logged MDT. Data collection for Immediate MDT is
performed for the connected UEs by eNB, while Logged MDT data collection is
performed by each UE itself during idle mode. Immediate and Logged MDT can
be configured by both Signaling-based and Management-based MDT
configuration procedures.
In Immediate MDT, the following types of measurement data can be collected
while the UE is in connected mode.
• M1: RSRP and RSRQ measurement by UE
• M2: Power Headroom (PH) measurement by UE
• M3: Uplink Received Interference Power of the connected cell (Rel.11)

Confidential
Chapter 9 SON
• M4: DL/UL Data Volume of the UE per QCI (Rel.11)

• RRM: Collecting all the event-triggered measurement reports configured for
RRM purpose (Rel.11)
For collecting data for M1, the eNB configures RRC measurement reporting
trigger to the chosen UE. Reporting trigger for M1 can be 1) Periodic or 2) Serving
cell becomes worse than threshold; Event A2. The UE sends the measurement
report (RSRP and/or RSRQ of serving and neighboring cells) to the serving eNB if
the reporting condition is met, then the serving eNB collects the data and sends it
to the TCE.
On the other hand, no RRC reporting trigger is required for M2 because PHR is
carried by MAC signaling. If MDT data collection for M2 is configured, the
serving eNB collects the PHR information triggered by normal MAC mechanisms.
Similarly, M3 Received Interference Power and M4 Data Volume measurements
are also performed by the eNB itself so that no additional RRC signaling is
required. If RRM is set, all the existing event-triggered measurement reports
configured for RRM purposes are collected, for example, Event A1, A2, A3, A4,
A5, A6, B1, and B2 events. Differently from M1, RRC measurement configuration
is not additionally configured solely for MDT purpose. However the measured
metric is similar to M1, which are RSRP or RSRQ.
Location information can be included in the measured data. Two positioning
methods are supported, that is, Standalone GNSS/GPS and Enhanced Cell ID (E-
CID). If GNSS/GPS positioning method is chosen, the serving eNB request UEs to
include standalone GNSS/GPS location result as the best effort manner. Then the
standalone GNSS/GPS supporting UE can include the detailed location
information if available.
If E-CID method is chosen, the serving eNB collects eNB Rx-Tx Time Difference
and UE Rx-Tx Time Difference which are the raw data for E-CID. The eNB
collect eNB Rx-Tx Time difference value regardless of receiving UE Rx-Tx Time
Difference IE in Measurement Report message when collecting location
information. The serving eNB sends the data to TCE, but calculation of detailed
location based on collected data is out of scope of the eNB. Among E-CID raw
data metrics defined in 3GPP, Angle of Arrival (AoA) trace is not supported.
If either GNSS/GPS or E-CID related data is not available, location may be
estimated based on signal measurement results for M1, that is, RF fingerprint,
according to the TCE implementation.
Configuration message of Immediate MDT mainly contains the following
information:
• List of measurements: M1 (RSRP/RSRQ) and/or M2 (PHR) and/or M3
(Received Interference Power) and/or M4 (Data Volume) and/or RRM
(Measurement report collection triggered by RRM events)
• Reporting trigger: Periodic or Event A2 (Only for M1)
• Report amount: Number of measurement reports sent (Only for M1 +
Periodic)
• Event threshold: Reporting threshold for measurement report (Only for M1 +
Event A2)
Confidential
Chapter 9 SON
• Area scope: Area scope where the MDT data collection should be conducted
• Positioning method: GNSS/GPS and/or E-CID
The eNB immediately starts the MDT operation when it receives the configuration
message and the target user is selected. Because Immediate MDT reuses the
existing 3GPP standard procedures, the operation is mostly transparent to the UEs.
In Logged MDT, only periodic downlink pilot strength measurement can be
performed during idle mode operations. Configuration parameters for Logged
MDT are sent to the UE through RRC signaling procedure after the UE transits to
the connected state. However, the actual data collection is done while the UE is in
idle state. On reception the Logged MDT configuration message over RRC,
Logged MDT-capable UE saves the parameters. Then, the UE starts to collect data
after the UE’s state is changed to idle state by considering the saved MDT
configuration parameters. After the measurement data is collected during idle
mode, UE notifies existence of logged MDT data during RRC connection
establishment procedures. Then, the eNB may request the UE to send the logged
data, and the received data is sent to the proper TCE based on TCE ID in the
logged data.
Configuration message of Logged MDT mainly contains the following
information:
• Logging duration: The timer value for completely stopping the logging job. If
the UE’s state changes from idle to connected state, logging stops for a
moment. However, the timer continues independent of state changes. Logging
will continue if the UE goes to idle before this timer expires.
• Logging interval: Periodicity of measurement during idle mode
• Trace Reference and Trace Recording Session Reference: Uniquely
identifying the MDT session in the whole PLMN
• Area scope: Area scope where the MDT data collection should be conducted
• TCE ID: The ID which uniquely identifying the TCE where the data should be
delivered. All the eNBs maintain the unique mapping table for TCE ID to TCE
IP address.
Figure below depicts the concepts for Immediate and Logged MDT operation.

Confidential
Chapter 9 SON
Additionally, UE RLF reporting (by Rel.9 or later UE) trace and RRC Connection
Establishment Failure (RCEF) reporting (by Rel.11 or later UE) trace are also
supported as management based MDT trace. RAN EMS orders some cells to trace
the RLF or RCEF reports sent by UEs. The, the eNB does not perform any specific
triggering action for the trace but just collects the RLF or RCEF information when
the reporting is received in the specified area. The collected information is sent to
the TCE server.
When management trace/MDT is configured in a specific cell, Trace, Immediate
MDT, Logged MDT, RLF Trace, RCEF Trace can be able to be supported
simultaneously in each cell.
• In LSM, management MDT type can be chosen as bit-map style
• Separate trace session IDs can be used for each type for easy identification
For M2 (PHR), M3 (RIP + UE SINR), M4 (Data volume), eNB supports trace of
whole UE through 6 UEs round robin operation. (Supported only to TCE server,
not LSM)
• At one time, only 6 UEs' information is traced and sent in 2.56 sec period,
however in the next period, next 6 UEs' information is traced.

Confidential
Chapter 9 SON
To prevent eNB from overload caused by logged MDT result collecting, a

configurable timer (0~60 min, default: 10 min) is provided to prevent eNB
collecting logged MDT result since last successful collecting. eNB collects logged
MDT result only in condition that the timer expired and CPU overload is normal.
To prevent external TCE server from overload caused by eNB sending MDT
result, eNB supports a configurable parameter (1~30, default: 1) that can set eNB
to report only the Xth collected MDT result to TCE server (the MDT results
includes M2/M3/M4), for example, if the parameter set to 3, then eNB report the
third collected MDT result to TCE and then reset the report count to 1.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
Chapter 9 SON
• According to TCE interworking environment, TCE information is configured

in the eNB properly.
• UE supports logged measurements in idle mode.
• Run CHG-MDTCTRL-PARA and set
SIG_BASED_IMMEDIATE_MDT_ALLOWED to True to activate signaling
based immediate MDT.
SIG_BASED_LOGGED_MDT_ALLOWED to True to activate signaling
based logged MDT.
MGMT_BASED_IMMEDIATE_MDT_ALLOWED to True to activate
management based immediate MDT.
• Run CHG-MDTCTRL-PARA and set MGMT_LOGGED_MDT_ALLOWED
to True to activate management based logged MDT.
• Run CHG-EUTRA-PRD and set ACTIVE_STATE of MDT purpose to Active
to activate periodic measurement for MDT.
• Run CHG-EUTRA-A2CNF and set ACTIVE_STATE of MDT purpose to
Active to activate A2 event measurement for MDT.
Register MDT (trace) information using LSM GUI (PERFORMANCE à Call
Trace à Register).
Delete MDT (trace) information using LSM GUI (PERFORMANCE à Call Trace
à Delete).
Key Parameters
parameters.
Parameter Descriptions of CHG-MDTCTRL-PARA/RTRV-MDTCTRL-PARA
SIG_BASED_IMMEDIATE_M This parameter shows the whether to permit to the Signaling Based
DT_ALLOWED Immediate MDT on demand.
• False: Signaling Based Immediate MDT request is not allowed.
• True: Signaling Based Immediate MDT request is allowed.
SIG_BASED_LOGGED_MDT This parameter shows the whether to permit to the Signaling Based Logged
_ALLOWED MDT on demand.
• False: Signaling Based Logged MDT request is not allowed.
• True: Signaling Based Logged MDT request is allowed.

Confidential
Chapter 9 SON
MGMT_BASED_ This parameter shows the whether to permit to the Management Based
IMMEDIATE_MDT_ALLOWE Immediate MDT on demand.
D • False: Management Based Immediate MDT request is not allowed.
• True: Management Based Immediate MDT request is allowed.
MGMT_BASED_LOGGED_M This parameter shows the whether to permit to the Management Based
DT_ALLOWED Logged MDT on demand.
• False: Management Based Logged MDT request is not allowed.
• True: Management Based Logged MDT request is allowed.
Parameter Descriptions of CHG-EUTRA-PRD/RTRV-EUTRA-PRD

PURPOSE This parameter is the purpose of using EUTRA periodic reportConfig. The
ReportStorngestCells is used as ActiveLB, and so on. through neighbor cell
signal measurement. The ReportCGI is used to acquire the CGI information
of a neighbor eNB and mainly used for the purpose of ANR.
• Mdt
ACTIVE_STATE This parameter indicates whether EUTRA periodic report is enabled/disabled.
If this parameter setting is changed, it will affect the SON operation (for
example, ANR) because EUTRA Periodic Event is utilized for SON such as
reportCGI which is used for ECGI request during ANR.
• Inactive: EUTRA periodic report is not used.
• Active: EUTRA periodic report is used.

• Mdt
frequency. This change is applied to the UE from next RRC signaling
setting is not updated to the current active UEs.
parameters.
Parameter Descriptions of CHG-MDTCTRL-PARA/RTRV-MDTCTRL-PARA
IGNORE_MGMT_BASED_ According to the Specification, the Management Based MDT is allowed when
MDT_ALLOWED Management Base MDT Allowed IE is included in the Initial Context Setup
Request, X2 Handover Request, S1 Handover Request message. However, by
this parameter the Management Based MDT can be allowed even if
Management Base MDT Allowed IE is not included in the message.
• False: Allow to the case where the management Base MDT Allowed IE is

Confidential
Chapter 9 SON
included.
• True: Allow to the case where the management Base MDT Allowed IE is not
included.
UE_SELECTION_METHOD This parameter represents the UE selection method in which it considers the
UE Release version and location capability When selecting the management
Based MDT Object UE.
• allRelease: Do all terminals with the selection object regardless of Release.
• aboveRelease10: Do the terminal that is the Release 10 or greater, with the
selection object.
• aboveRelease10WithLocationInfoCapable: Do the terminal which is the
Release 10 or greater and in which the supplying of location information is
possible with the selection object.
RADIO_RESOURCE_USAG This parameter represents the threshold regarding the radio resource amount
E_THRESHOLD used when selecting the Immediate Based MDT object UE. It does not select
as MDT perform object UE if the load of MDT subject cell is this value or
greater.
MDT_UE_PICKUP_RATE This parameter represents the selection rate which is used when selecting the
Management Based MDT object UE. If the random number generated between
0 is this value or less, select as MDT object UE.
RETRIEVE_LOGGED_MDT This parameter represents whether to execute the UE Information process in
_RECONFIGURATION_ALL case the logMeasAvailable is instructed in the RRC Connection
OWED Reconfiguration Complete message.
• False: the UE Information procedure due to the logMeasAvailable instruction
of the RRC Connection Reconfiguration Complete message is not allowed.
• True: the UE Information procedure due to the logMeasAvailable instruction
of the RRC Connection Reconfiguration Complete message is allowed.
RETRIEVE_LOGGED_MDT This parameter represents whether to execute UE Information process in case
_REESTABLISH_ALLOWE the logMeasAvailable is instructed in the RRC Connection Reestablishment
D Complete message.
of the RRC Connection Reestablishment Complete message is not allowed.
of the RRC Connection Reestablishment Complete message is allowed.
RETRIEVE_LOGGED_MDT This parameter represents whether to execute UE Information process in case
_SETUP_ALLOWED the logMeasAvailable is instructed in the RRC Connection Setup Complete
message.
of the RRC Connection Setup Complete message is not allowed.
of the RRC Connection Setup Complete message is allowed.
MAX_IMMEDIATE_MDT_U This parameter represents the object terminal count permitted at the
E_COUNT Management Based Immediate MDT. Allow on the terminal Immediate MDT
measurement configuration setting up within this parameter setting value.
MAX_LOGGED_MDT_UE_ This parameter represents the number of terminals which can be setup for the
COUNT Management Based MDT while considering the system load. This does not
include the Logged MDT object terminal selection from new calls.
LOGGED_MDT_RTRV_HO This parameter indicates time of interval for retrieve logged (MBSFN) MDT
LD_TIMER measurement information from UE.
Value 0 means that holding timer is not operated.

Confidential
Chapter 9 SON
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP 37.320: UTRA and E-UTRA; Radio measurement collection for
Minimization of Drive Tests (MDT); Overall description; Stage 2 (Release 10)
[2] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2 (Release
10)
[4] 3GPP 36.413: E-UTRAN; S1 Application Protocol (S1AP) (Release 10)
[5] 3GPP 36.423: E-UTRAN; X2 Application Protocol (X2AP) (Release 10)
[6] 3GPP 32.421: Telecommunication management; Subscriber and equipment
trace; Trace concepts and requirements (Release 10)
trace; Trace control and configuration management (Release 10)
trace; Trace data definition and management (Release 10)

Confidential
Chapter 10 Services
LTE-ME3317, UL allocation enhancement for

VoLTE
INTRODUCTION
Uplink scheduler allocates the UL resource according to the received scheduling
request (SR) or buffer status report (BSR). When SR delay or outdated BSR
occurs, UL scheduling delay can increase. This leads to degradation of voice
quality and voice user capacity. This feature enhances UL scheduler by UL buffer
prediction.
BENEFIT
• Operator can provide improved voice service with enhanced voice quality by
reduced voice delay.
• Voice user capacity can be improved.
DEPENDENCY
Related Radio Technology
• E-UTRAN (LTE)
LIMITATION
None
SYSTEM IMPACT
• Voice UE capacity improvement.

Confidential
Chapter 10 Services
FEATURE DESCRIPTION
In UE congestion environment, most of UL resource allocation is triggered by the

received BSR. Voice packets generated after receiving a BSR can be transmitted
after receiving the next BSR. This causes UL scheduling delay.
The following figure shows operation of enhanced UL allocation scheme.

Confidential
Chapter 10 Services
The eNB predicts the amount of the generated voice packets at UE side. When a
UE is chosen to be allocated, the eNB tries to allocate the predicted amount of the
accumulated voice packets. This reduces the voice delay in the UE congestion
environment.
SYSTEM OPERATION
How to Activate
Preconditions
There are no specific preconditions to active this feature.
• Run CHG-MAC-VOIP and then set BufferPredictionEnable to 1 (TRUE).
• Run CHG-MAC-VOIP and then set BufferPredictionEnable to 0 (FALSE).

Confidential
Chapter 10 Services
Key Parameters
parameters.
Parameter Descriptions of CHG-MAC-VOIP/RTRV-MAC-VOIP
BUFFER_PREDICTION_ENABLE Configuration for enabling/disabling UL buffer status prediction for
VoLTE
Counters and KPIs

this feature.
PDCP_LOSS PdcpSduLossRateUL The calculated average loss rate of uplink DRB
Packet that is received in the PDCP
REFERENCE
None

Confidential
Chapter 10 Services
LTE-SV0101, IMS based Emergency Call

Support
INTRODUCTION
To support IP Multimedia Subsystem (IMS) emergency call, eNB performs
emergency call specific admission control, security handling and mobility control.
BENEFIT
Operator can provide Emergency service to its subscribers while they are staying
in E-UTRAN.
LTE users can do an emergency call while staying in E-UTRAN, as well as in
legacy CS network.
DEPENDENCY
EPC, and IMS deployment
• Others:
IMS capable device
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
IMS Emergency call support indication is provided to inform the UE that
emergency bearer services are supported. If IMS connectivity via MME is
supported and IMS Emergency call is available, eNB broadcasts IMS Emergency
call support indicator via SIB1.
SystemInformationBlockType1-v920-IEs ::= SEQUENCE {

ims-EmergencySupport-r9 ENUMERATED {true} OPTIONAL, -- Need OR
cellSelectionInfo-v920 CellSelectionInfo-v920 OPTIONAL, -- Cond
RSRQ
nonCriticalExtension SystemInformationBlockType1-v1130-IEs OPTIONAL
}
Operator can change the indicator based on IMS deployments and the indicator
can be configured via LSM using IMS_EMERGENCY_SUPPORT (CHG-CELL-

Confidential
Chapter 10 Services
INFO).
eNB identifies an emergency call based on the RRC establishment cause from UE.
When new emergency call is requested, eNB performs the emergency call specific
admission control. This is achieved by applying higher threshold as decision
criteria of CAC for emergency calls (including handover calls) than normal calls.
If at the time of an IMS emergency call origination, the UE is already RRC
connected to an EPC that does not support IMS emergency calls, it should
autonomously release the RRC connection and originate a fresh RRC connection
in a cell that is capable of handling emergency calls.
Security procedures are activated for emergency calls with "NULL" algorithms.
During handover from cell in non-restricted area to restricted area, security is
handled normally with normal key derivation and so on. for both the intra-LTE
and inter-RAT handover.
SYSTEM OPERATION
How to Activate
Preconditions
Run CHG-CELL-INFO and set IMS_EMERGENCY_SUPPORT as True.
Run CHG-CELL-INFO and set IMS_EMERGENCY_SUPPORT as False.
Key Parameters
parameters.
IMS_EMERGENCY_SUPPORT This parameter indicates whether to support emergency calls or not.
This information is broadcasted to UEs through SIB 1.
• False: An operating cell does not support IMS Emergency.
• True: An operating cell supports IMS Emergency.

Confidential
Chapter 10 Services
IMS_EMERGENCY_SUPPORT This parameter indicates whether to support emergency calls or not.
This information is broadcasted to UEs through SIB 1.
• False: An operating cell does not support IMS Emergency.
• True: An operating cell supports IMS Emergency.
Counters and KPIs

with this feature.
REFERENCE

Confidential
Chapter 10 Services
LTE-SV0105, eMPS (Enhancements for

Multimedia Priority Service) support
INTRODUCTION
Multimedia Priority Service (MPS) is introduced for supporting end-to-end
priority treatment in call/session origination/termination. This feature includes
differentiated admission control for high priority calls for MPS and preemption of
normal calls in congested situation.
BENEFIT
Operator can provide higher priority for MPS subscribers over normal subscribers.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
MPS is introduced to provide certain subscribers priority access on access radio
network resources in congestion. The following three functionalities are used to
support MPS: call admission control, preemption, and paging priority.
The eNB treats a call connection request having establishmentCause in
RRCConnectionReqeuest message set to "highPriorityAccess" with higher priority
over other types of calls. For high priority calls, a different set of call admission
control thresholds, that is,
CALL_CAC_THRESH_FOR_HIGH_PRIORITY_ACCESS (CHG-CELL-CAC),
are applied. This reserves a portion of network resources for high priority calls.
When there is no available resource for the high priority call (in the situation
where even the reserved resources are all occupied by existing high priority and
emergency calls), eNB preempts an existing normal call to accept the high priority
call.
During E-RAB setup procedures, a high-priority bearer (with lower value of
Allocation and Retention Priority, ARP) can preempt an existing low-priority
bearer (with higher value of ARP) in congestion. The preemption is executed only
if Pre-emption Capability of the high priority bearer is "may trigger pre-emption",

Confidential
Chapter 10 Services
and Pre-emption Vulnerability of the low priority bearer is pre-emptable.

For terminated calls for MPS, the eNB provides paging priority. When a paging
message from MME contains paging priority information element, the eNB put
this paging request in front of normal paging requests in its paging queue. Two
levels of paging priority (high or normal priority) are supported.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-ENB-CAC and set HIGH_PRIORITY_ACCESS_TYPE to
emergencyType.
• Run CHG-ENB-CAC and set HIGH_PRIORITY_ACCESS_TYPE to
normalType.
Key Parameters
parameters.
HIGH_PRIORITY_ACCESS_TYPE This parameter determines the type of a highpriorityaccess call.
• If the type is normalType, the eNB handles the highpriorityaccess as
a normal call.
• If the type is emergencyType, the eNB handles the highpriorityaccess
as an emergency call.
• If the type is independentOperationType, the eNB handles the high
priority access all to use distinguished threshold for CAC.
parameters.

Confidential
Chapter 10 Services

HIGH_PRIORITY_ACCESS_TYPE This parameter determines the type of a highpriorityaccess call.
• If the type is normalType, the eNB handles the highpriorityaccess as
the normal call.
• If the type is emergencyType, the eNB handles the highpriorityaccess
as the emergency call.
• If the type is independentOperationType, the eNB handles the high
priority access all to use distinguished threshold for CAC.
Counters and KPIs

The cumulated number indicates the number
ReceivedS1apPriorityPaging of received S1AP Paging messages with the
Paging Priority IE.
PRIORITY_S1AP_PAGING
The cumulated number indicates the number
DiscardedS1apPriorityPaging of discarded S1AP Paging messages with
Paging Priority IE.
REFERENCE
[1] 3GPP TS 36.331, Evolved Universal Terrestrial Radio Access (E-UTRA);
Radio Resource Control (RRC) protocol specification (Rel. 10)
[2] 3GPP TS 36.413, Evolved Universal Terrestrial Access Network (E-UTRAN);
S1 Application Protocol (S1AP) (Rel. 10)
[3] 3GPP TS 23.272, Circuit Switched Fallback in Evolved Packet System (Rel.
10)

Confidential
Chapter 10 Services
LTE-SV0201, CMAS (Commercial Mobile Alert

Service)
INTRODUCTION
Commercial Mobile Alert Service (CMAS) is a public warning system to notify
military threats, kidnapping, or disasters. CMAS warning notification is composed
of multiple short text messages and they support multiple/concurrent
transmissions. When an eNB receives CMAS warning notification from an MME,
it uses SIB12 to notify UEs in the designated areas which have been specified by
the warning notification provider. The presence of a CMAS warning notification
in SIB12 is informed by paging message. If the UE receives a paging message
including the cmas-Indication, it starts receiving the CMAS warning notification in
SIB12
BENEFIT
Operator can provide public warning notifications to its subscribers while they are
staying in E-UTRAN.
Users can be notified for public warning messages from network, and then they
can avoid some disasters or accidents.
DEPENDENCY
MME that supports CMAS, and CBC required
• Others:
CMAS capable device
LIMITATION
Verification test with the supported device, EPC and CBC is needed.
SYSTEM IMPACT
FEATURE DESCRIPTION
The following figure shows overall operation of the CMAS public alarm system.

Confidential
Chapter 10 Services
The CMAS warning notification transmission procedure is as follows.

Confidential
Chapter 10 Services
1 The CBE (for example, Information Source such as PSAP or Regulator)

sends emergency information (for example, "warning type", "warning
message", "impacted area", "period") to the CBC.
2 Using the "impacted area" information, the CBC identifies which MMEs
need to be contacted and determines the information to be place into the
Warning Area Information Element. Then CBC sends a Write-Replace
Warning Request message containing the warning message to be broadcast
and the delivery attributes to MMEs, that is, Message identifier, Serial
number, Tracking Area list, Warning Area, and so on.
3 The MME sends a Write-Replace Warning Response message that indicates
to the CBC that the MME has started to distribute the warning message to
eNBs.
Then, the CBC may confirm to the CBE.
4 The MME forwards Write-Replace Warning Request message to eNBs. The
MME shall use the Tracking Area list to determine the eNBs in the delivery
area.
If the Tracking Area list is empty the message is forwarded to all eNBs that are
connected to the MME.
5 When reception of the Write-Replace Warning Request message from the
MMEs, eNB checks the Message identifier and Serial number fields within
the warning message for duplicate detection. If any redundant messages are
detected only the first one received is broadcasted by the cells. The eNBs
return a Write-Replace Warning Response message to the MME, even if it
was a duplicate. If, in a certain area, broadcast of one or more message are
already on going and if the Concurrent Warning Message Indicator IE is
present, the received warning message are broadcasted. Up to 5 concurrent
warning message transmissions are supported.
6 The eNB shall use the Warning Area information to determine the cell(s) in
which the message is to be broadcast. The eNB broadcasts the message
frequently according to the attributes set by the CBC that originated the
Warning Message distribution.
During CMAS warning notification, eNB also indicates CMAS warning
notification via Paging. The CMAS warning notification termination procedures
also take place in 1 to 5.

Confidential
Chapter 10 Services
1 The CBE requests stop of emergency broadcast to the CBC.

2 The CBC identifies which MMEs need to be contacted and CBC sends a Stop
Warning Request message to MMEs.
3 The MME sends a Stop Warning Response message that indicates to the CBC
that the MME has started to distribute the warning message to eNBs. Then,
the CBC may confirm to the CBE.
4 The MME forwards Kill Request message to eNBs. The MME shall use the
Tracking Area ID list to determine the eNBs that may have warning message
broadcast ongoing. If the Tracking Area ID list is empty the message is
forwarded to all eNBs that are connected to the MME.
5 When reception of the Kill Request message from the MMEs, eNB checks
the Message identifier and Serial number fields within the request message.
The eNBs return a Kill Response message to the MME.
6 The eNB shall stop broadcasting the warning message identified by the
Message identifier and Serial number in the areas identified by Warning Area
IDs.
If the Warning Area is absent, it shall be interpreted as all cells on the eNB.
SIB12 is used to transmit CMAS warning notification. The CMAS warning

Confidential
Chapter 10 Services
notification has message identifier, serial number, warning type, warning message
contents (warning message segment), and data coding scheme received to the S1
Write-Replace Warning message. The CMAS warning notification can be
transmitted in partition and the warning message segment type and warning
message segment number are included in the SIB12 as the information indicating
partitioned transmission.
SYSTEM OPERATION
How to Activate
Preconditions
There are no preconditions to activate this feature.
To activate this feature, the operator should set SIB12_PERIOD to the default
value using CHG-SIB-INF command
To deactivate this feature, the operator should set SIB12_PERIOD to not_used=7
using CHG-SIB-INF command.
Key Parameters
SIB12_PERIOD This parameter is the transmission period for the system information block type
12 of the cell in the eNB. SIB12 contains a CMAS notification.
• ms80: 80 ms.
• ms160: 160 ms.
...
• ms5120: 5120 ms.
SI_WINDOW This parameter is the System Information (SI) window size of a cell in the eNB.
Each SI message is associated with one SI-window, and does not overlap with
the SI-windows of other SI messages. That is, one SI is sent to one SI window.
The length of SI-window is the same for all SI messages. The corresponding SI
message in the SI-window is sent repeatedly.


Confidential
Chapter 10 Services
PWS_FAIL_RESTART_IND This parameter indicates whether to use PWS Failure Indication and PWS
_USAGE Restart Indication.
Counters and KPIs

CMAS WRWarningRequestAtt Total CMAS Write-Replace Warning Request
attempt count
WRWarningRequestDiscard Total CMAS Write-Replace Warning Request
discard count
WRWarningRequestSucc Total CMAS Write-Replace Warning Request
success count
WRWarningRequestFail Total CMAS Write-Replace Warning Request
failure count
KillRequestAtt Total CMAS KillRequest attempt count
KillRequestDiscard Total CMAS KillRequest discard count
KillRequestSucc Total CMAS KillRequest success count
KillRequestFail Total CMAS KillRequest failure count
PwsRestartIndication The number of PWS Restart Indication
messages sent to MME
PwsFailureIndication The number of PWS Failure Indication
messages sent to MME

S1AP_MSG S1apPwsRestartIndication The number of S1apPwsRestartIndication
messages transmitted by the eNB
S1apPwsFailureIndication The number of S1apPwsFailureIndication
messages transmitted by the eNB
REFERENCE

Confidential
Chapter 10 Services
LTE-SV0301, A-GNSS (LPP)

INTRODUCTION
GNSS refers to various satellite systems such as Global Positioning System (GPS)
and Global Orbiting Navigation Satellite System (GLONASS). The traditional
standalone GNSS receiver in the mobile device is solely responsible for receiving
GNSS signals and estimating its position. The receiver needs to acquire GNSS
signals through a search process which can take up to several minutes. For
example, if the UE is in an indoor area or surrounded by tall buildings, it takes
long time to search satellites (usually need to find 3 or 4 satellites) or even fails to
detect the satellite signal.
The E-SMLC provides "Assistance Data" (which names this feature as "A"-GNSS)
to the UE so that the GNSS receiver can expedite the GNSS signal acquisition
process.
A-GNSS speeds up positioning performance and helps to save battery power.
The protocol for the delivery of Assistance Data between E-SMLC and UE is
called LPP (LTE Positioning Protocol).
BENEFIT
• Operator can provide location based services to their subscribers with a faster
positioning feature.
• User can perform faster positioning and save battery power.
DEPENDENCY
MME E-SMLC
• Others:
Supported by Rel-9 UE with the GNSS receiver
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The E-SMLC sends "Assistance Data" to the UE by LPP messages so that the
GNSS receiver can acquire the GNSS signal fast.

Confidential
Chapter 10 Services
Assistance Data Transfer Procedure as follows:

• E-SMLC-initiated Assistance Data Delivery Procedure
• UE initiated Assistance Data Transfer
These LPP messages are carried as transparent PDUs across intermediate network
interfaces using the appropriate protocols (for example, S1-AP over the S1-MME
interface, NAS/RRC over the Uu interface).
The Assistance Data may include following:
• Reference Time
• Reference Location
• Ionospheric Models
• Earth Orientation Parameters
• GNSS-GNSS Time Offsets
• Differential GNSS Corrections
• Ephemeris and Clock Models
• Real-Time Integrity
• Data Bit Assistance
• Acquisition Assistance
• Almanac
• UTC Models

Confidential
Chapter 10 Services
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

with this feature.
REFERENCE
[2] 3GPP TS36.455 Evolved Universal Terrestrial Radio Access (E-UTRA); LTE
Positioning Protocol (LPP)
UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in
E-UTRAN

Confidential
Chapter 10 Services
LTE-SV0302, Enhanced Cell ID

INTRODUCTION
This feature improves the accuracy in location estimation compared to the
traditional Cell ID method in 3G networks.
The Enhanced Cell ID (E-CID) method utilizes the following additional
measurements information to improve the accuracy:
• UE Measurements
o RSRP: Reference Signal Received Power
o RSRQ: Reference Signal Received Quality
o UE Rx-Tx time difference
• eNB Measurements
o eNB Rx-Tx time difference
o Timing Advance
BENEFIT
• Operator can improve the accuracy of location based services.
• Users can enjoy more accurate location based services such as maps and
navigations.
DEPENDENCY
MME E-SMLC
E-UTRAN (LTE)
• Others:
The interaction between eNB and E-SMLC is based on LPPa protocol
LIMITATION
External E-SMLC server is needed
SYSTEM IMPACT

Confidential
Chapter 10 Services
FEATURE DESCRIPTION
Samsung's enhanced cell ID positioning method complies with the method defined
in 3GPP 36.305, which is LPPa based UL E-CID method. Downlink E-CID
method is LPP based and transparent to eNB and is out of scope of this feature.
This feature support on demand and periodic E-CID methods, and the following
figure shows the call flow for E-CID positioning method.

Confidential
Chapter 10 Services
The following LPPa messages are used to exchange information between eNB and
E-SMLC
• E-CID Measurement Initiation Request/Response/Failure
• E-CID Measurement Report
• E-CID Measurement Failure Indication/Termination
The E-CID measurement initiation function is a procedure that the E-SMLC
requests the E-CID measurement result from the eNB to calculate the position of
the UE.
The eNB operates as follows depending on the contents of the E-CID
measurement initiation request message transmitted by the E-SMLC.
• If the value of the report characteristics is "on demand": Transmits the E-CID
MEASUREMENT INITIATION RESPONSE message (and the measurement
result) including the requested value.
• If the value of the report characteristics is "periodic": Starts the periodic report
timer and transmits the E-CID MEASUREMENT INITIATION RESPONSE
message (excluding the measurement result). Then transmits the periodic E-
CID measurement report to the E-SMLC.
eNB support configuration of following measurement in serving cell:
• Timing Advance type 1 and 2
• RSRP
• RSRQ
eNB support the following measurements in neighbor cells
• RSRP
• RSRQ
The above serving cell and neighbor cells (SLR5.0) measurements is forwarded to
E-SMLC for position calculation.
eNB enhanced TA1 measurement reporting in SLR6.0 (included UE Rx-Tx time
difference) that is, TA1 = (eNB Rx-Tx time difference) + (UE Rx-Tx time
difference).
Samsung also provides a scheme to support pre-rel 9 UE TA1 measurement in
SLR6.0. As pre-rel9 UE does not support UE Rx-Tx time difference measurement,
Samsung eNB supports to measure the TA1 based on both Timing Advance during
Random Access procedure (also called TA2) and Timing Advance command sent
by MAC Control Element (considered as TA offset).
SYSTEM OPERATION

Confidential
Chapter 10 Services
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-POS-CONF/RTRV-POS-CONF
maximum capacity system is 1 FA/3 Sector, up to 3 cells are supported.
LATITUDE The latitude of the cell for providing the OTDOA function. The UE location
information included in the cell can be calculated using the latitude value.
LONGITUDE The longitude of the cell for providing the OTDOA function. The UE location
information included in the cell can be calculated using the longitude value.
HEIGHT The altitude of the cell for providing the OTDOA function. The UE location
information included in the cell can be calculated using the altitude value.
UNCERTAINTY_SEMI_MAJ The uncertainty of semi major. The uncertainty, which the user enters directly.
OR It can be calculated by a formula of r = 10 * (1.1k-1).
UNCERTAINTY_SEMI_MIN The uncertainty of semi minor. The uncertainty, which the user enters directly.
OR It can be calculated by a formula of r = 10 * (1.1k-1).
ORIENTATION_OF_MAJOR The orientation of the major axis, which the user directly enters the value
_AXIS chosen from 0 to 179.
UNCERTAINTY_ALTITUDE The uncertainty of altitude tolerance, which the user enters directly. It can be
calculated by using a formula of h = 45 * (1.025k-1).
CONFIDENCE The confidence (%) of location service.
Counters and KPIs

with this feature.
REFERENCE
Positioning Protocol A (LPPa)
E-UTRAN

Confidential
Chapter 10 Services
Requirements for support of radio resource management
[7] 3GPP TS 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA),
Radio Resource Control (RRC) Protocol specification

Confidential
Chapter 10 Services
LTE-SV0303, OTDOA
INTRODUCTION
In the Observed Time Difference of Arrival (OTDOA) positioning method, UE
makes an observation of the time difference of arrival of the Reference Signal (RS)
from two or more eNBs. Then, the position of the UE can be calculated based on
the known position of the eNBs and the time differences.
The time difference between the RS from the serving cell and the neighbor cells is
called Reference Signal Time Difference (RSTD). To measure the RS from
(probably far away) neighbor cells, a special positioning signal is defined in
Release 9 and called Positioning Reference Signal (PRS). PRS was introduced to
improve the "hearability" of neighboring cells within completing measurements
for the downlink OTDOA positioning method. 3GPP recognized that the
hearability of the existing cell-specific reference signals was not sufficient to
support the OTDOA positioning method. Hearability can be challenging as a result
of neighboring cells being co-channel with the serving cell, especially at locations
where the serving cell signal strength is high.
For E-SMLC, UE provides RSTD information through the LPP protocol layer and
the eNB provides PRS and base station information through the LPPa protocol
layer. Then, E-SMLC makes a final decision on the position of the UE. MME
transparently relays LPP and LPPa layer information to E-SMLC.
BENEFIT
• Operator can provide an OTDOA-based location service.
• End users can enjoy more accurate location-based services such as maps and
navigations.
DEPENDENCY
E-UTRAN (LTE)
• Others:
o UE that support OTDOA based on 3GPP Release 9 or later version.
o MME to support LPPa protocol
o E-SMLC to support OTDOA
o eNB that support PRS
o Precise synchronization between eNBs is required for better accuracy
(GPS synchronization is recommended)
o SFN must be synchronized between eNBs

Confidential
Chapter 10 Services
LIMITATION
• Air interface throughput is impacted due to PRS broadcasting as there is no
PDSCH data in the subframe where PRS located.
• In rural areas, there are fewer measureable cells which may impact accuracy.
• PRS subframe configuration needs to be manually planned to ensure no
overlapping with PBCH, SIBs, Paging and Measurement Gap scheduling.
• No SON Functionality is available to support automatic PRS configuration,
PRS configurations will have to be manually planned and configured.
SYSTEM IMPACT
capabilities
PRS occupy PRB resources, therefore, air throughput is impacted by enabling this
feature.
FEATURE DESCRIPTION
The OTDOA positioning method makes use of Reference Signal Time Difference
(RSTD) measurements from the UE. The RSTD quantifies the subframe timing
difference between a reference cell and a neighboring cell. The accuracy of the
positioning calculation is improved if the UE can provide RSTD measurements
from an increased number of cells. RSTD is measured in units of Ts (1/30720 ms)
and is reported to the Enhanced Serving Mobile Location Center (E-SMLC) where
the location calculation is completed. E-SMLC is a network element within the
operator's infra network.
UE receives an LTE Positioning Protocol (LPP) Provide Assistance Data message
from E-SMLC. This message is packaged by MME as a NAS message before
being packaged by eNB as an RRC message. The Provide Assistance Data
message includes information regarding both the reference and neighboring cells.
The reference cell does not have to be the current serving cell for the UE.
Positioning reference signals (PRS) are able to coexist with both the cell specific
reference signals and the physical layer control information at the start of each
subframe (PCFICH, PHICH, PDCCH). Positioning reference signals occupy an
increased number of resource elements within a subframe relative to the cell
specific reference signals to help improve RSTD measurement accuracy. The
sequence used to generate the positioning reference signal is a function of the
physical cell identity (PCI) and the cyclic prefix duration (normal or extended).
Positioning reference signals are broadcast using antenna port 6. They are not
mapped onto resource elements allocated to the PBCH, Primary synchronization
signal nor secondary synchronization signal. Positioning reference signals are only
defined for the 15 kHz subcarrier spacing. They are not supported for the 7.5 kHz
subcarrier spacing used by Multimedia Broadcast Multicast Services (MBMS).
The figure below illustrates examples of the positioning reference signal for

Confidential
Chapter 10 Services
normal cyclic prefix. There is a dependency upon the number of antenna ports
used for the cell specific reference signal. Additional symbols are used by the cell
specific reference signal when broadcast from 4 antenna ports.
The figure below is Mapping of positioning reference signals (normal cyclic
prefix).
PRS configuration parameters include PRS Bandwidth, PRS Configuration Index,

Number of Consecutive Downlink Subframes and PRS Muting Configuration.
• PRS Bandwidth: The bandwidth that PRS occupied can be configured by
PRS_BANDWIDTH (CHG-POS-CONF). The positioning reference signal
bandwidth is signaled to the UE with a value of 6, 15, 25, 50, 75 or 100
resource blocks. The positioning reference signal bandwidth is always
centered around the middle of the channel bandwidth. The positioning
reference signal configuration index is used to define both a periodicity and
subframe offset for the timing of the positioning reference signal. The look-up
table presented below is used to link the configuration index to the periodicity
and subframe offset. The table below is Positioning Reference Signal subframe
configuration.
• PRS Configuration Index: PRS Configuration Index (IPRS) defines the
periodicity (TPRS) and subframe offset (ΔPRS) for the timing of the PRS that
can be configured by PRS_CONFIG_INDEX (CHG-POS-CONF). The
following table shows the relation among these parameters.

Confidential
Chapter 10 Services
• Number of Consecutive Downlink Subframes: The number of consecutive

downlink subframes that can be configured by NUM_OF_DL_FRAME (CHG-
POS-CONF) defines the number of subframes during which the positioning
reference signal is broadcast within each positioning reference signal period.
The number of consecutive downlink subframes can be configured with values
of 1, 2, 4 or 6 subframes.
• PRS Muting Configuration: PRS muting that can be configured by
PRS_MUTING_CONFIG_SIZE/ PRS_MUTING_CONFIG_VALUE (CHG-
POS-CONF) consist of either 2, 4, 8 or 16 bits map sequence. The periodicity
of the muting pattern is defined by the length of the bits map. The PRS
positioning occasion will not exist in the subframe if the corresponding bit is
set to 0.
Based on 3GPP 36.211, PRS is not transmitted in RE allocated to PBCH, PSS, and
SSS and UE only uses PRS except resources allocated to PBCH, PSS, and PSS,
SSS. PBCH and synchronization signal are transmitted in subframe #0 and
bandwidth (6RB), where the corresponding resources are allocated due to this, can
transmit PRS to only 38 % (FDD) or 50 % (TDD) among total REs available for
PRS allocation. Therefore, when configuring PRS configuration index in PLD in
Samsung systems, it is suggested to operate without transmitting PRS in subframe
#0.
To allocate PDSCH and PRS to the same RB, it needs to puncture PDSCH in RE
to where PRS is transmitted, and this can cause performance decrease of PDSCH
reception and PRS reception of neighbor cell. Therefore, Samsung does not
transmit PDSCH in RBs where PRS is allocated. In case of Paging and SIB1
transmitted to a fixed subframe, it is assumed there is no PRS when UE decodes
the corresponding traffic and if this is not the case, PRS is received. Therefore, if
one of either Paging/SIB1 or PRS needs to puncture the other, the reception
performance of Paging/SIB1 or PRS decreases. Thus, it is suggested to service
providers to operate without transmitting PRS in subframe (= 5, 9) to where
Paging/SIB1 is transmitted, when setting up PRS configuration index.
UE interworks with E-SMLC with LPP interface, which is transparent to eNB that
is, out of scope of this feature. The detailed procedures are defined in 3GPP
TS36.305 and TS36.355.
eNB interworks with E-SMLC with LPPa interface. OTDOA Information
Exchange procedure is used to allow the E-SMLC request the eNB to transfer
OTDOA information to the E-SMLC.

Confidential
Chapter 10 Services
The procedure consists of the following messages:

• OTDOA Information Request/Response/Failure
After the eNB receives the OTDOA information request message from the E-
SMLC, the OTDOA information transfer function performs according to
reception of the requested information and it performs as follows.
o If it received OTDOA cell information: It transmits the OTDOA
INFORMATION RESPONSE message including the ODTOA cell
information.
o If it fails to receive OTDOA cell information: It transmits OTDOA
INFORMATION FAILURE message including the cause (value) of the
failure.
The following are OTDOA Cell Information:
• PCI
• Cell ID
• TAC
• EARFCN
• PRS Bandwidth
• PRS Configuration Index
• CP Length
• Number of DL Frames
• Number of Antenna Ports
• SFN Initialization Time
• E-UTRAN Access Point Position
• PRS Muting Configuration
To implement RSTD measurement, the UE need some assistance date sent from E-
SMLC via LTE Positioning Protocol (LPP) interface. UE receives an LPP Provide
Assistance Data message from the E-SMLC. This message is packaged by the
MME as a NAS message before being packaged by the eNB as an RRC message.
The Provide Assistance Data message includes information regarding both the
reference and neighboring cells.

Confidential
Chapter 10 Services
The content of the reference cell information is presented in the table below.
Similar information is also provided for each of the neighboring cells.
Information Element
physCellId
cellGlobalId
earfcnRef
antennaPortConfig
cpLength
prsInfo prs-Bandwidth
prs-ConfigurationIndex
numDL-Frames
prs-MutingInfo
After receiving the OTDOA assistance data, UE shall start RSTD measurement
and report the measurement results to E-SMLC through LPP interface where the
location calculation is completed.
Measurement Gap Exclusion

To ensure UE can perform RSTD measurement, measurement gap shall not be
scheduled in the subframes where PRS located, otherwise RSTD measurement can
fail when UE are doing inter-FA/RAT measurement.
eNB support excluding specified measurement gap offsets and the exact excluded
gap offset is configurable (gap pattern 0: 0~39; gap pattern 1: 0~79; by
GAP_PATTERN_ID (CHG-MGAPEXCLUDE-INF)) to ensure all UE to receive
PRS. The excluded offset can be one offset or combination of several offsets. The
measurement gap offset exclusion can be enable/disabled (ON/OFF) by
MEAS_GAP_OFFSET_EXCLUDED (CHG-POS-CONF).
Operator can configure the starting offset and rang of consecutive gap offset by
GAP_START_OFFSET/ GAP_OFFSET_RANGE (CHG-MGAPEXCLUDE-INF).
Starting gap offset range is 0~39 or 0~79 considering of gap pattern, while rang of
consecutive gap offset number can be 1~15. For an example, if starting offset set
to 0 and offset range set to 15, then gap offset 0~14 are excluded.
Inter-frequency RSTD Measurement Support

In OTDOA positioning method, especially in inter frequency cell deployment, E-
SMLC may request UE to perform inter frequency RSTD measurement to improve
the accuracy by obtaining more RSTD measurement results. This feature enables
eNB to configure to start or stop the requested measurement gap sent from UE by
a new introduced Release 10 RRC procedure "Inter-frequency RSTD measurement
indication". After eNB receive the requested measurement gap from UE, eNB may
start to configure the gap as UE requested or ignore the gap configuration if the
requested gap is not acceptable in the system based on operator's configuration.
Currently, 3 options are provided for operator to control eNB action when
receiving UE's "inter-frequency RSTD measurement indication" message

Confidential
Chapter 10 Services
controlled by RSTD_MEAS_GAP_OPTION (CHG-MSGAP-INF):

• Ignore: eNB ignore UE request, the measurement gap is not assigned to UE.
The purpose of this option is to limit the impact to current UE performance as
measurement gap may have bad impact to the performance.
• Accept: eNB always accept UE request. The purpose of this option is to ensure
the UE to receive inter-frequency RSTD measurement for better accuracy of
LCS.
• Measurement Gap Algorithms based: In this option, if the UE requested
measurement gap offset can be accepted by the current measurement gap
allocation algorithms then the gap is allocated to UE, if the UE requested
measurement gap offset cannot be accepted by the current measurement gap
allocation algorithms then the requested gap is ignored.
Operator Configurable PRS Power Boosting

This feature supports PRS power boosting with respect to average maximum
power. To ensure good RSTD measurement performance, PRS power is
configured a little bit higher power. The configurable range is from 0 dB to 7.75
dB by 0.5 dB step by PRS_POWER_BOOST_OFFSET (CHG-POS-CONF)
SYSTEM OPERATION
How to Activate
Preconditions
Core Network and UE must support OTDOA feature.
• (For OTDOA) Run CHG-POS-CONF and set OTDOA_ENABLE to True.
• (For measurement gap exclusion) Run CHG-POS-CONF and set
MEAS_GAP_OFFSET_EXCLUDED to True.
• (For PRS power boost) Run CHG-POS-CONF and set
PRS_POWER_BOOST_OFFSET to greater than "0".
• (For Inter-Frequency RSTD measurement gap assignment) Run CHG-
MSGAP-INF and set RSTD_MEAS_GAP_OPTION to AlwaysAccept or
ByAlgorithm.
• (For OTDOA) Run CHG-POS-CONF and set OTDOA_ENABLE to False.
• (For measurement gap exclusion) Run CHG-POS-CONF and set
MEAS_GAP_OFFSET_EXCLUDED to False.

Confidential
Chapter 10 Services
• (For PRS power boost) Run CHG-POS-CONF and set

PRS_POWER_BOOST_OFFSET to "0".
• (For Inter-Frequency RSTD measurement gap assignment) Run CHG-
MSGAP-INF and set RSTD_MEAS_GAP_OPTION to Ignore.
Key Parameters
parameters.
OTDOA_ENABLE If the otdoaEnable value is set to True to execute OTDOA included in the UE
Positioning function, an eNB transmits a PRS signal and a UE transmits related
configuration, and so on. to the eNB. If the otdoaEnable value is set to False,
an eNB does not transmit PRS but transmits the information of the cell.
MEAS_GAP_OFFSET_EXC This attribute represents that measurement gap offset exclusion function is
LUDED activated or deactivated.
PRS_POWER_BOOST_OF This parameter is the PRS power boosting offset value. When the operator
FSET enters the value, the eNB transmits the value to the MAC layer.
Parameter Descriptions of CHG-MSGAP-INF/RTRV-MSGAP-INF

RSTD_MEAS_GAP_OPTIO This parameter indicates the methods how to allocate MeasurementGap when
N eNB receives an InterFreqRSTDMeasurementIndication from UE.
parameters.
LATITUDE This parameter is the latitude of each cell to provide the OTDOA function. The
latitude can be used to calculate the UE location information in a cell. The
format used is "A BBB:CC:DD.DDD".
• A: hemisphere. "N" or "S".
• BBB: degrees. 0~90.
• CC: minutes. 0~59.
• DD.DDD: seconds. 00.000~59.999.
LONGITUDE This parameter is the longitude of each cell to provide the OTDOA function.
The longitude can be used to calculate the UE location information in a cell.
The format used is "A BBB:CC:DD.DDD".
• A: hemisphere. "E" or "W".
• BBB: degrees. 0~180.

Confidential
Chapter 10 Services
• CC: minutes. 0~59.
• DD.DDD: seconds. 00.000~59.999.
HEIGHT This parameter is the height information for each cell.
The altitude of each cell to provide the OTDOA function. The altitude can be
used to calculate the UE location information in a cell. The format used is
"AAAA.AA m".
• AAAA.AA: Sea level altitude. The range is from -1000.00 m to 4000.00 m.
The unit "m" must be included. For example, 53.85 m.
UNCERTAINTY_SEMI_MAJ This parameter is the tolerance and the operator must enter it directly. The
OR tolerance value can be computed by the formula r = 10 * (1.1k-1).
UNCERTAINTY_SEMI_MIN This parameter is the tolerance and the operator must enter it directly. The
OR tolerance value can be computed by the formula r = 10 * (1.1k-1).
ORIENTATION_OF_MAJOR This parameter is the value of orientation of major axis; for which the operator
_AXIS directly enters a value between 0-179.
UNCERTAINTY_ALTITUDE This parameter is the altitude tolerance and the operator must enter it directly.
The tolerance value can be computed by the formula h = 45 * (1.025k-1).
CONFIDENCE This parameter is the accuracy of GPS service (%).
The closer the value is to 100 %, the higher the accuracy.
PRS_CONFIG_INDEX This parameter is the PRS configuration index. When the operator enters the
value, the eNB transmits the value to the MAC layer.
NUM_OF_DL_FRAME This parameter is the number of downlink frames. When the operator enters
the value, the eNB transmits the value to the MAC layer. Values from 0 to 3 are
mapped with sf1, sf2, sf4, and sf6. It is the value for transmitting to MAC Layer
without being used in the signal processing block.
PRS_MUTING_CONFIG_SI This parameter is the PRS muting configuration size value. When the operator
ZE enters the value, the eNB transmits the value to the MAC layer.
If a bit is set to "0", it indicates that the PRS is muted in the corresponding PRS
positioning occasion (numbering from any sub frame for which SFN=0) in a
periodic cycle of length equal to the length of the bit string.
PRS_MUTING_CONFIG_V This parameter is the PRS muting configuration value. When the operator
ALUE enters the value, the eNB transmits the value to the MAC layer.
PRS_ BANDWIDTH The positioning reference signal (PRS) bandwidth value. If an operator enters
this value, the eNB forwards the value to the MAC layer.
Parameter Descriptions of CHG-MGAPEXCLUDE-INF/RTRV-MGAPEXCLUDE-

INF
GAP_PATTERN_ID This attribute represents a measurement gap identity (that is, 0 or 1).
GAP_START_OFFSET This attribute represents a start offset of measurement gap which is excluded
range: 0~79.
GAP_OFFSET_RANGE This attribute represents an offset range of measurement gap is excluded. (for
example, In case gapStartOffset value is 0 and the gapOffsetRange value is
15, the total 15 value is excluded from the measurement gap offset assignment
till 0~14.)
Counters and KPIs

with this feature.

Confidential
Chapter 10 Services
REFERENCE
Positioning Protocol A (LPPa)
E-UTRAN
Requirements for support of radio resource management

Confidential
Chapter 10 Services
LTE-SV0401, Vocoder Rate Adaptation

INTRODUCTION
Previously, the eNB introduced various features to reduce the voice packet size to
improve capacity and coverage for VoLTE service, such as RoHC, and short
sequence numbers (that is, RLC UM mode with 5 bit sequence number and PDCP
7 bit sequence number). In addition to that, 3GPP defines adaptation mechanism to
support vocoder rate change in LTE networks. Based on cell load condition, the
eNB marks Explicit Congestion Notification-Congestion Experienced (ECN-CE)
flag within IP header of VoLTE packets. This enables the eNB to control ECN-
triggered codec rate reduction at UE side. At busy hour, the eNB can accept more
VoLTE UEs in the cell at a tradeoff for some voice quality. Additionally, the eNB
marks ECN-CE for the UE that is moved to the cell edge to further extend VoLTE
coverage.
BENEFIT
Operator can accept more VoLTE users in congestion situation and provide
extended VoLTE coverage.
DEPENDENCY
None
LIMITATION
The UE should support ECN-triggered adaptation.
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature supports ECN-based media bit-rate adaptation defined in 3GPP TS
26.114. To enable vocoder rate adaptation, the eNB marks ECN-CE flag in the IP
header of VoLTE packets according to the configured trigger conditions at the
eNB. When a UE receives ECN-CE marked VoLTE packet, it may trigger codec
rate adaptation according to its own adaptation algorithm.
ECN Copying to deliver Information of Backhaul Congestion

When this feature is disabled or any trigger conditions for this feature are not met,
the eNB does not proactively marks ECN-CE flag. According to IETF RFCs [5,
6], ECN-CE can be marked by intermediate routers during delivery to the eNB. In
such cases, the eNB simply relays (that is, copy) the ECN field of outer IP header

Confidential
Chapter 10 Services
of GTP tunnel to the ECN field of inner IP header as following figure shows.
ECN Marking for Codec Rate Adaptation

For the purpose of vocoder rate adaptation, the eNB can proactively mark ECN
field of IP header. As the following figure shows, the eNB marks ECN field of
inner IP header as ECN-CE flag when it decides to activate vocoder rate
adaptation at the UE based on configured trigger conditions.

Confidential
Chapter 10 Services
The following figure shows overall procedure for vocoder rate adaptation.
1 The ECN-capable UE sends voice packets with ECN-ECT marked in the IP

header.
2 The eNB checks whether any trigger conditions are met or not for ECN
marking.
3 The eNB marks downlink voice packet with ECN-CE ("11").

Confidential
Chapter 10 Services
4 If the UE receives ECN-CE marked voice packet, UE decides codec rate

reduction and requests codec mode change toward the peer UE via RTCP-
APP-CMR or CMR in the RTP payload. (UE functionality)
5 If the peer UE receives CMR, the UE changes codec rate in accordance with
received CMR if available. (UE functionality)
Uplink ECN marking has a similar operation to downlink ECN marking.
Trigger Condition for ECN Marking

Samsung eNB supports two kinds of trigger conditions: Air resource congestion
and UE's signal quality. Each condition can be independently enabled.
1 Air resource congestion of a cell
If the congestion level exceeds thresholds, the eNB marks all voice packets
with ECN-CE. This operation is performed for DL and UL, respectively, with
separate thresholds. Operator can enable/disable this function via
PRB_QCI_ENABLE configuration parameter (CHG-CELLECN-CTRL). The
thresholds can be configured by
PRB_DL_THRESHOLD/PRB_UL_THRESHOLD via CHG-CELLECN-
CTRL.
2 UE's signal quality
For UE's signal quality-based ECN marking, the eNB supports ECN marking
start/stop operation based on reported mobility event of Event A1, which
means serving becomes better than threshold, and Event A2, which means
serving, becomes worse than threshold. To activate this operation, operator
should configure A1/A2 measurement report configuration with purpose of
ECN.
If the eNB receives an A2 measurement report of ECN purpose from the UE,
the eNB starts to mark ECN-CE to voice packets for the target UE. Also, if the
eNB receives an A1 measurement report of ECN purpose from the UE, the
eNB stops ECN-CE marking. Operator can configure RSRP/RSRQ threshold
to trigger A1/A2 mobility event via
A1_THRESHOLD_RSRP/A1_THRESHOLD_RSRQ (CHG-EUTRA-A1CNF)
and A2_THRESHOLD_RSRP/A2_THRESHOLD_RSRQ (CHG-EUTRA-
A2CNF). Also, operator can enable/disable this function via
MR_EVENT_ENABLE configuration parameter (CHG-CELLECN-CTRL).
SYSTEM OPERATION
How to Activate
Preconditions
This feature shall be working with UE which supports "rate adaptation" according
Confidential
Chapter 10 Services
to ECN field.
Run CHG-CELLECN-CTRL and set RATE_ADAPT_ENABLE to 1 to enable the
ECN marking for this feature. (SET PRB_QCI_ENABLE or
MR_EVENT_ENABLE as "1")
Run CHG-CELLECN-CTRL and set RATE_ADAPT_ENABLE to 0 to disable the
ECN marking.
Key Parameters
parameters.
Parameter Descriptions of CHG-CELLECN-CTRL/RTRB-CELLECN-CTRL
PRB_UL_THRESHOLD This parameter is uplink PRB threshold to check cell (uplink) congestion state.
Value is displayed as (* 1000), and this value is just percentage threshold of
PRB usage.
PRB_DL_THRESHOLD This parameter is uplink PRB threshold to check cell (downlink) congestion
state.
Value is displayed as (* 1000), and this value is just percentage threshold of
PRB usage.
parameters.
Parameter Descriptions of CHG-EUTRA-A1CNF (Q)/RTRV-EUTRA-A1CNF
(Q)
• MeasGapDeact: Used to disable measurement gap and forwards A1 event
reception measurement gap release information.
• CaPeriodicMr: For Periodic Measurement Report based Carrier Aggregation.
• CaInterFreq: For Inter-Frequency Carrier Aggregation.
• Ecn: used to MR for ECN marking/marking stop.
Parameter Descriptions of CHG-EUTRA-A2CNF (Q)/RTRV-EUTRA-A2CNF

(Q)

Confidential
Chapter 10 Services
• LteHo: Used for Gap Activate.
• LteBlind: Used for Blind HO.
• IRatHo: Used for IRAT HO.
...
• Ecn: used to MR for ECN marking/marking stop.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TR 23.860 Enabling Coder Selection and Rate Adaptation for UTRAN
and E-UTRAN for Load Adaptive Applications; Stage 2
[2] 3GPP TS 26.114 IP Multimedia Subsystem (IMS); Multimedia Telephony;
Media handling and interaction
[5] IETF RFC 3168-The Addition of Explicit Congestion Notification (ECN) to IP
[6] IETF RFC 6679-Explicit Congestion Notification (ECN) for RTP over UDP

Confidential
Chapter 10 Services
LTE-SV0404, VoLTE Quality Enhancement

INTRODUCTION
With VoLTE quality enhancement, an eNB provides following functions to
improve voice quality over LTE:
• VoLTE-aware UL grant
• VoLTE-specific parameter setting
• Reduction of the packet loss during handover
Volte quality enhancement includes user-plane optimization on scheduler, RLC,
and PDCP layer. In addition, the eNB collects VoLTE-related statistics such as
VoLTE call drop rate, VoLTE handover success ratio, VoLTE HARQ
performance, VoLTE channel quality, and so on.
BENEFIT
VoLTE quality is sensitive to delay, jitter, and bursty packet losses. Intelligent UL
grant scheduling for UL transmission of VoLTE packets is beneficial to improve
VoLTE quality by avoiding the unnecessary delay in the cases that the scheduling
request of UE is not successfully received by the eNB. Moreover, VoLTE HARQ
success rate in downlink is increased for VoLTE service compared to other
services, by applying more robust air transmission. Specifically during handover,
this feature helps to reduce bursty VoLTE packet losses.
DEPENDENCY
None
LIMITATION
• Impact on DL cell throughput: Resource Block (RB) usage for VoLTE packets
is increased due to conservative RB allocation for VoLTE user HARQ re-
transmissions in downlink. Thus, the remaining RBs for other services may be
reduced.
• Impact on UL cell throughput: VoLTE-aware UL grant function allocates UL
grants more than requested by UEs.
SYSTEM IMPACT

Confidential
Chapter 10 Services
FEATURE DESCRIPTION
VoLTE-aware UL Grant
UEs need to send the Buffer Status Report (BSR) to the eNB to obtain uplink grant
for sending uplink data. If the eNB does not recognize the BSR correctly, the
uplink grant is not allocated to UEs, and thus uplink packet transmission is delayed
for hundreds milliseconds, which causes unnecessary mute.
The VoLTE-aware UL grant function is a technique for the eNB to estimate
whether the UE has a packet to transmit based on the previous the UE’s buffer
state information. Uplink scheduler allocates uplink grant even when no
scheduling request is received, based on the recent non-zero BSR of the UE, under
the following conditions: 1) the internal buffer occupancy of the UE is calculated
as zero after 32 ms or 2) receiving zero BSR from the UE after 70 ms.
VoLTE Specific Parameter Setting

To reduce VoLTE packet loss and delays, the eNB sets the target BLER lower
than the conventional services. As the target BLER affects MCS selection, MCS is
allocated conservatively for VoLTE. The default value 2.7 % is recommended for
VoLTE. The operator can control by VOLTE_DLTARGET_BLER and
VOLTE_ULTARGET_BLER in CHG-BLER-CTRL.
To further increase HARQ success rate, DL scheduler allocates eight times more
RB for second re-transmission onwards. If the increased RB count is greater than
maximum PDCSCH RB allocation limit, then maximum possible RBs are
allocated. For increased RB allocation, MCS is still maintained same as previous
transmission and hence code-rate of this re-transmission reduces which helps to
improve HARQ success rate.
Reduction of the Packet Loss during Handover

During handover, RLC layer at the eNB performs RLC Re-establishment as soon
as RRC layer at the eNB sends the Handover Command message to lower layers.
When RLC Re-establishment is performed, the eNB buffer is flushed and the RLC
state variables and timers are reset. Any uplink VoLTE packets that arrive at the
eNB afterwards are lost.
However, Handover Command may take a while to reach to a UE via HARQ/ARQ
retransmissions according to the channel condition. In this case the UE will keep
sending uplink VoLTE packets over the air until it receives Handover Command
and these packets is lost at the eNB even if HARQ transmission is successful.
To prevent such packet loss during handover, the eNB postpones performing RLC
Re-establishment. That is, it normally processes the packets successfully received
in uplink until the handover procedure is completed.

Confidential
Chapter 10 Services
To reduce the packet loss further in downlink during handover, the PDCP layer at
the eNB mirrors a certain number of downlink VoLTE packets. During handover,
the source eNB forwards the mirrored VoLTE packets to the target eNB. The
number of VoLTE packets mirrored in PDCP layer is set to be one by default.

Confidential
Chapter 10 Services
These functions help to reduce the chance of packet loss of VoLTE service during
handover.
SYSTEM OPERATION
How to Activate
Key Parameters
This section describes the key parameters of the feature.
Refer to below parameter description.
parameters.
Parameter Descriptions of CHG-BLER-CTRL/RTRV-BLER-CTRL
VOLTE_DL_TARGET_BLER This parameter indicates the DL VoLTE target BLER in 0.1 % unit.
VOLTE_UL_TARGET_BLER This parameter indicates the UL VoLTE target BLER in 0.1 % unit.
Counters and KPIs

VoLTE Quality Defect VoLTE_UlQualityDefect The number of QCI #1 bearers, which has NO
RTP Interval during specific amount of time for
UL VoLTE Packet.
VoLTE_DlQualityDefect The number of QCI #1 bearers, which has NO
RTP Interval during specific amount of time for
DL VoLTE Packet.

VoLTE Handover VoLTE_IntraEnbAtt Intra handover attempt count
VoLTE_IntraEnbPrepSuc Successful intra handover preparation count
c
VoLTE_IntraEnbSucc Successful intra handover execution count
VoLTE_InterX2OutAtt X2 handover attempt count
VoLTE_InterX2OutPrepS Successful X2 handover preparation count

Confidential
Chapter 10 Services

ucc
VoLTE_InterX2OutSucc Successful X2 handover execution count
VoLTE_InterS1OutAtt S1 handover attempt count
VoLTE_InterS1OutPrepS Successful S1 handover preparation count
ucc
VoLTE_InterS1OutSucc Successful S1 handover execution count

VoLTE Ho Time VoLTE_IntraHoTime_Av When Intra eNB Handover is completed, this
g statistic is collected.
VoLTE_IntraHoTime_Mi This counter is updated when
n VoLTE_IntraHoTime_Avg is collected and it is
low than previous maximum value.
VoLTE_IntraHoTime_Ma This counter is updated when
x VoLTE_IntraHoTime_Avg is collected and it is
greater than previous maximum value.
VoLTE_IntraHoTime_Cnt This counter is cumulated when
VoLTE_IntraHoTime_Avg is collected
VoLTE_IntraHoTime_Tot This counter is cumulated when
VoLTE_IntraHoTime_Avg is collected
VoLTE_X2HoTime_Avg When X2 Handover is completed, this statistic
is collected.
VoLTE_X2HoTime_Min This counter is updated when
VoLTE_X2HoTime_Avg is collected and it is
VoLTE_X2HoTime_Max This counter is cumulated when
VoLTE_X2HoTime_Avg is collected
VoLTE_X2HoTime_Cnt This counter is cumulated when
VoLTE_X2HoTime_Tot This counter is cumulated when
VoLTE_S1HoTime_Avg When S1 Handover is completed, this statistic
is collected.
VoLTE_S1HoTime_Min This counter is updated when
VoLTE_S1HoTime_Avg is collected and it is
VoLTE_S1HoTime_Max This counter is cumulated when
VoLTE_S1HoTime_Avg is collected
VoLTE_S1HoTime_Cnt This counter is cumulated when
VoLTE_S1HoTime_Tot This counter is cumulated when

VoLTE Quality VoLTE_DropRate The number of VoLTE Drop rate
VoLTE_UlQualityDefect The number of UL Quality Defect rate
Rate

Confidential
Chapter 10 Services

VoLTE_DlQualityDefect The number of DL Quality Defect rate
Rate
VoLTE_IntraHoSuccess The number of VoLTE HO Intra Success rate
Rate
VoLTE_X2HoSuccessRa The number of VoLTE HO X2 Success rate
te
VoLTE_S1HoSuccessRa The number of VoLTE HO S1 Success rate
te

HARQ performance for Volte DLVoLTEHARQFail The cumulated number that DL VoLTE (QCI =
bearer 1) bearer is failed to transmit after maximal
HARQ retransmissions during collection
interval.
DLVoLTEHARQSucc The cumulated number that DL VoLTE (QCI =
1) bearer is succeeded to transmit at initial
transmission or before maximal HARQ
retransmissions during collection interval.
DLVoLTEHARQFailRate This counter is failure rate of DL VoLTE (QCI =
1) bearer collected periodically.
ULVoLTEHARQFail The cumulated number that UL VoLTE (QCI =
1) bearer is failed to transmit after maximal
HARQ retransmissions during collection
interval.
ULVoLTEHARQSucc The cumulated number that UL VoLTE (QCI =
1) bearer is succeeded to transmit at initial
transmission or before maximal HARQ
retransmissions during collection interval.
ULVoLTEHARQFailRate This counter is failure rate of UL VoLTE (QCI =
1) bearer collected periodically.

CQI for DL Volte bearer DLVoLTECQI0 The cumulated number that CQI 0 of DL
VoLTE bearer is received per layer/codeword
DLVoLTECQI1 The cumulated number that CQI 1 of DL

Confidential
Chapter 10 Services

DLVoLTECQIErase (reserved) The cumulated number that CQI
erase of DL VoLTE bearer is received per
layer/codeword
DLVoLTECQIMin The minimum value of
DLVoLTECQI0~DLVoLTECQI15
DLVoLTECQIMax The maximum value of
DLVoLTECQIAvg The average value of

Bin distribution of SINR for UL ULVoLTESinrDistPreCo The cumulated number of UL VoLTE bearer
Volte bearer mpBin0 SINR Bin0 (-10 to -8 dB) before Outer-loop
compensation
ULVoLTESinrDistPreCo The cumulated number of UL VoLTE bearer
mpBin1 SINR Bin1 (-8 to -6 dB) before Outer-loop
compensation
compensation
compensation
compensation
mpBin5 SINR Bin5 (0 to 2 dB) before Outer-loop
compensation
compensation
compensation

Confidential
Chapter 10 Services

compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
ULVoLTESinrDistPostCo The cumulated number of UL VoLTE bearer
mpBin0 SINR Bin0 (-10 to -8 dB) after Outer-loop
compensation
compensation
compensation
compensation
mpBin4 SINR Bin4 (-2 to 0 dB) after Outer-loop
compensation

Confidential
Chapter 10 Services

mpBin5 SINR Bin5 (0 to 2 dB) after Outer-loop
modification
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
compensation
REFERENCE
None

Confidential
Chapter 10 Services
LTE-SV0406, VoLTE Coverage Enhancement

INTRODUCTION
VoLTE service is one of the most important services in LTE networks. However,
VoLTE coverage was usually worse than the voice coverage of 2G/3G. Thus,
3GPP has introduced various techniques to improve VoLTE coverage such as sub-
frame bundling (TTI bundling) and RoHC and so on. In addition to that, Samsung
supports features for VoLTE coverage enhancement, which consists of VoLTE
packet segmentation, PUSCH frequency hopping, and Robust HARQ.
BENEFIT
Operator can provide further enhanced VoLTE coverage and improved voice
quality at cell edge.
DEPENDENCY
• Others:
UE should support sub-frame bundling (TTI bundling) and PUSCH frequency
hopping. This feature requires LTE-ME3307 UL Sub-frame Bundling and LTE-
ME1503 PUSCH Frequency Hopping.
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
This feature provides enhanced VoLTE coverage by further utilizing time and
frequency resources for TTI bundling-enabled UEs. This feature consists of the
following three sub-functions:
• VoLTE packet segmentation
• PUSCH frequency hopping
• Robust HARQ
VoLTE Packet Segmentation in TTIB Mode

Packet segmentation reduces the instantaneous bitrate by segmenting a voice-
packet into multiple MAC PDUs. This feature is used in conjunction with PUSCH
Hopping/TTI bundling feature. Dynamic Scheduling is used by the eNB to

Confidential
Chapter 10 Services
schedule resources for these UEs, instead of Semi-Persistent Scheduling. Each

Voice packet received in RLC is segmented into two RLC segments, which is a
special functionality done when this feature is enabled. (Note that the eNB's uplink
scheduler grants UL resource considering packet segmentation and actual RLC
segmentation operation is performed at the UE side.) In a TTI, only one RLC
segment among two is transmitted in PUSCH, the PUSCH size remains the same
as it was for full Voice packet transmission. A lower instantaneous bitrate (due to
half segmented voice packet transmission) requires lower MCS at the same PRB
cost, thus lower uplink SINR. The MCS is reduced compared to the full voice
packet transmission; the reduction in MCS forces the UE to segment its voice
packet in to two. However, segmenting the Voice packet and sending it as two
different transmissions increases the latency. Compared to the benefit we get from
this feature this disadvantage is acceptable. Moreover, this latency can be
accommodated within the Voice packet delay budget.
The following figure shows time utilization for VoLTE packet transmissions. In
the conventional VoLTE, time resources are under-utilized by its low duty cycle.
In Samsung VoLTE coverage enhancement, a VoLTE packet is segmented at RLC
layer according to UE’s signal quality. This makes time resources are more
utilized and increases duty cycle.
PUSCH Frequency Hopping in TTIB Mode

PUSCH frequency hopping helps in mitigating the effects of frequency selective
fading, common in wireless systems, due to multipath-channel and user-mobility.
Frequency selective fading can result in deep nulls in signal power of some
frequencies. In LTE, frequency selective fading can cause long-term interference
in some PRBs. Such a scenario can lead to HARQ failure, if all HARQ
retransmissions are assigned to the same PRB set. Spreading the UL resources
across the frequency domain to exploit frequency diversity provides diversity gain
in frequency selective fading scenarios.
In LTE, only localized resource allocation is supported in the uplink due to its
robustness to frequency offset compared to distributed resource allocation.
Localized resource allocation also retains the single-carrier property in the uplink
transmission. As a consequence, there is very little frequency diversity gain. On
the contrary, in the downlink, it is possible to allocate disjointed sets of resource
blocks to a UE to extract some frequency diversity gain. To alleviate this issue,
LTE supports frequency hopping on PUSCH, which provides additional frequency
diversity gain in the uplink. Frequency hopping can also provide interference
averaging when the system is not 100 percent loaded. There are two types of
PUSCH hopping: Type-1 and Type-2 PUSCH frequency hopping. Samsung
Confidential
Chapter 10 Services
supports Type-2 PUSCH frequency hopping with inter sub-frame (enabled by

higher layer signaling) and mirroring.
Robust HARQ in TTIB Mode

This function provides a robust coding gain by increasing maximum HARQ
transmission. Each successive HARQ retry increases the probability for successful
decoding. Actual transmissions exceeding 5 HARQ re-transmissions only occur
for UEs in cell-edge conditions. Generally, Samsung eNB uses a maximum of 5
HARQ Transmissions (1 new transmission + 4 Re-Transmissions). For cell edge
UEs with Voice traffic the maximum re-transmission is increased (for example 7
re-transmissions). The maximum number of HARQ retransmissions is operator
configurable via MAX_HARQTX_BUNDLING configuration parameter (CHG-
TRCH-INF). Increasing the HARQ re-transmission increases the latency of a

Confidential
Chapter 10 Services
voice packet. This can be acceptable because this latency can be accommodated
within voice packet delay budget.
SYSTEM OPERATION
How to Activate
Preconditions
• Run CHG-PUSCH-CONF, and then set PUSCHhoppingEnabled as True.
• Run CHG-PUSCH-CONF, and then set PUSCHhoppingEnabled as False.
Key Parameters
parameters.
PUSCHhoppingEnabled This parameter enable PUSCH frequency hopping
• True: Enabled
• False: Disabled
parameters.
Parameter Descriptions of CHG-TRCH-INF/RTRV-TRCH-INF
maxHARQTxBundling Maximum number of UL HARQ transmission (including initial transmission) for
sub-frame bundling mode (TTIB mode)

Confidential
Chapter 10 Services
Counters and KPIs

this feature.
PDCP_LOSS PdcpSduLossRateUL Intra-eNB handover success rate of E-UTRAN
mobility.
REFERENCE

Confidential
Chapter 10 Services
LTE-SV0501, eMBMS Basic Function

INTRODUCTION
eMBMS (Evolved Multimedia Broadcast Multicast Services) is LTE broadcast
service that uses MBSFN (Multimedia Broadcast Single Frequency Network) by
transmitting the identical waveforms at the same time through multiple cells.
MCE, a new network entity, allocates and schedules the same radio resource to the
multiple cells for MBSFN transmission. To provide eMBMS service, additional
entities such as MBMS-GW and BM-SC are required. This feature introduces
eMBMS network architecture, protocol stacks, area configuration, call flow and
eNB basic functions to support eMBMS.
BENEFIT
• Multicast services can be provided such as live broadcasting, venue casting,
and so on.
• Operator can enhance unicast throughput by offloading popular contents to
multicast.
DEPENDENCY
o MCE MBMS-GW BM-SC
• Interfaces & Protocols:
o M1, M2, M3
o None
• Others:
o None
LIMITATION
• 1 MTCH per 1 PMCH, 15 MBMS bearers per Cell
• eNB cannot guarantee MBMS service for M1 BH delay of more than 20
seconds due to the buffering memory limitation
• BCCH modification period and MCCH modification period shall be the same.
• Samsung eNB can interwork only with Samsung MCE because there are some
Samsung proprietary protocols for the M2 interface between the eNB and the
MCE.

Confidential
Chapter 10 Services
SYSTEM IMPACT
None
FEATURE DESCRIPTION
eMBMS Network Architecture

For eMBMS service, MCE, MBMS-GW, and BM-SC must be added to the
conventional LTE system. In addition, the SW package of eNB, MME, and LSM
must be upgraded to support eMBMS. Samsung MBMS-GW can be integrated
with PGW without requiring external server whereas Samsung MCE requires
centralized external server. Backhaul routers between MBSM-GW and eNB must
support IP multicast. M1 interface (user plane, 3GPP TS25.446) between MBMS-
GW and eNB is used while M2 (control plane, 3GPP TS36.443) interface between
eNB and MCE and M3 interface (control plane, 3GPP TS36.444) interface
between MCE and MME are used.
eMBMS Protocol Stacks

Protocol stack of the control plane is shown in the figure below.
Protocol stack of the user plane is shown in the figure below.

Confidential
Chapter 10 Services
Area Configuration
• MBMS Service Area is defined as the area within which data of a specific
MBMS session are sent. MBMS Service Areas are decided when BM-SC
initiates MBMS Session Start Request and it consists of a set of cells that
broadcast the same MBMS service. MBMS Service Areas can be overlapped
geographically. When MBMS Service Area ID is "0", it means that all of the
MBMS capable cells that belong to the corresponding PLMN shall broadcast
the session (3GPP TS23.003). MBMS Service Area is set by a cell basis with
CHG-MBSFN-INFO CLI command through the eNB or the LSM.
• MBSFN Synchronization Area is an area of the network where all eNBs can
be synchronized and perform MBSFN Transmission. The eNBs shall be
synchronized in terms of SFN (System Frame Number) over the same carrier
frequency and bandwidth. MBSFN Synchronization Area ID is configured
automatically or can be set manually by switching
"mbsfnSyncAreaIdAutoEnable" parameter on or off after running CHG-ENB-
MBMSINFO CLI per cell through the eNB or the LSM. Automatic
configuration is recommended due to the convenient configuration of multiple
MBSFN Synchronization Area IDs needed to support of multiple bandwidths
(5, 10, 15, 20 MHz) in an MCE. An eNB belongs to only one MBSFN
synchronization area. MBSFN Synchronization Area ID has the value between
0 and 65535 (3GPP TS36.443).
• MBSFN Area is an area which consists of a group of cells within an MBSFN
Synchronization Area, which are coordinated to achieve an MBSFN
Transmission. MCE applies the same scheduling algorithm for all cells that
belong to the same MBSFN Area. MBSFN Areas can overlap as a cell
supports up to 8 different MBSFN Areas. A guideline for MBSFN Area
configuration follows:

Confidential
Chapter 10 Services
o An eNB does not support multiple MBSFN Areas that has a common
MBMS Service Area ID.
o An eNB does not support a scenario that multiple MBSFN Areas within an
eNB deliver the same MBMS service.
For eMBMS service, operator shall configure MBSFN Synchronization Area ID

(SYNC in the figure below) and MBMS Service Area ID (SA in the figure below)
for each cell. Operator can configure this information through LSM and this
information is downloaded when eNB starts up. When the eNB initializes, it will
perform the M2 Setup procedures with the MCE. In the M2 SETUP REQUEST
message, the eNB shall include the MBSFN Synchronization Area ID and MBMS
Service Area ID for each cell. The MCE will then find MBSFN Area ID from the
configuration data, based on the MBSFN Synchronization Area ID and MBMS
Service Area ID. This means that operator shall pre-configure MBSFN Area IDs
(MA in the figure below) in the MCE so that each MBSFN Area ID has a different
set of MBSFN Synchronization Area ID and MBMS Service Area ID. The
MBSFN Area ID information is delivered to the eNB in the M2 SETUP
RESPONSE message. If the eNB fails to find an MBSFN Area ID that is mapped
to the MBSFN Synchronization Area ID and MBMS Service Area ID, then the
operator will be informed of the provisioning error. MBSFN Area can be retrieved
per cell with RTRV-ENBMBSFN-STS CLI command through the eNB or the
LSM. MBSFN Synchronization Area ID and MBMS Service Area ID should be
the same in the same MBSFN Area. If they are not properly configured, eMBMS
data cannot be broadcast over the target MBMS Service Area. The following table
shows an example where MBSFN Areas are configured through LSM. For each
MBSFN Area configured, additional system parameters shall be configured
properly. This information is downloaded to MCE when the MCE starts up.

Confidential
Chapter 10 Services
Call Flows
Session Start
The call flow as shown below explains the MBMS Session Start procedure.

Confidential
Chapter 10 Services
1) When booting up, MCE performs M3 Setup procedures with MME by sending
M3 Setup Request message to MME.
2) When booting up, eNB performs M2 Setup procedures to MCE. Even if there is
no cell registered in a MBMS Service Area, it performs the M2 Setup procedures,
in which case, the M2 Setup Request message does not include the cell registered
to any MBMS Service Area. The MCE responses with M2 Setup Response
message.
3) and 4) eNBs which established M2 connection update SIB1 and SIB2 and
broadcast SIB 13 and MCCH.
5), 6), and 7) MBMS Session Start Request message is delivered from BM-SC to
MCE. Based on MBMS Service Area information in the message, MBMS-GW
and MME route the message to the appropriate MCEs that serve the MBMS

Confidential
Chapter 10 Services
Service Area.
8) MCE delivers the MBMS Session Start Request message to all eNBs registered
in the MBMS Service Area requested from the MBMS session setup message.
9) After receiving the MBMS Session Start message, the eNB uses the given TNL
address to join the IP multicast service and prepares to receive a multicast packet
from the BM-SC.
10) The MCE performs the function of allocating resources for the eMBMS
session and sends the MBMS Scheduling Information to the eNBs of the MBSFN
Areas that includes the MBMS Service Area. Depending on the MBSFN Area, the
scheduling information can be different.
11) and 12) eNBs broadcast the updated SIB1, SIB2, SIB13 and MCCH. The
system information change notification must be performed at least 5.12 seconds
before the eNB starts to transmit MBMS data for the newly added channel.
13) After the Minimum Time to MBMS Data Transfer that BM-SC specifies in the
MBMS Session Start message, the BM-SC starts to transmit MBMS packets to
MBMS-GW. When transmitting MBMS data, BM-SC marks a time stamp to each
packet for data transmission synchronization between eNBs.
14) MBMS-GW multicasts a packet received from the BM-SC to eNBs.
15) The eNBs broadcast the data of each MBMS session according to the
scheduling information received from the MCE.
Session Stop
The call flow as shown below explains the MBMS Session Stop procedure.

Confidential
Chapter 10 Services
1), 2), and 3) MBMS Session Stop Request message is delivered from BM-SC to
MCE. Based on MBMS Service Area information in the message, MBMS-GW
and MME route the message to the appropriate MCEs that serve the MBMS
Service Area.
4) MCE delivers the MBMS Session Stop request message to all eNBs registered
in the MBMS Service Area requested from the MBMS Session Stop message.
5) After receiving the MBMS Session Stop message, the eNB un-subscribes the
IP multicast channel.
6) The MCE performs the function of withdrawing resources for the stopped
eMBMS session and sends the MBMS Scheduling Information to the eNBs of the
MBSFN Areas that includes the MBMS Service Area.
before the changed data transmission.
Session Update
The call flow as shown below explains the MBMS Session Update procedure.

Confidential
Chapter 10 Services
1) MBMS Session Update Request message is delivered from BM-SC to MBMS-

GW.
2) Based on MBMS Service Area information in the message, MBMS-GW
delivers MBMS Session Start/Update/Stop Request message to the appropriate
MMEs. If the message is MBMS Session Start Request message or MBMS
Session Stop message, the MME that receives the message proceeds with the
session start or stop procedures of the above Session Start or Session Stop. If the
message is MBMS Session Update message, the MME delivers M3AP MBMS
Session Start/Update/Stop Request message to the appropriate MCEs. If the
message is M3AP MBMS Session Start Request message or M3AP MBMS
Session Stop message, the MCE that receives the message proceeds with the
session start or stop procedures of the above Session Start or Session Stop. If the
message is M3AP MBMS Session Update message, the MCE delivers M2AP
MBMS Session Start/Update/Stop Request message to the appropriate eNBs.
before the changed data transmission.
Basic Functionality for eMBMS

• eMBMS cells shall transmit MBMS data in MBSFN subframes. MBSFN
subframe is only defined for the extended cyclic prefix because the delay
spread between transmissions receiving from multiple MBMS cells is
expected to be relatively large.

Confidential
Chapter 10 Services
• Antenna port 4 is used to transmit MBMS data.

• MBSFN reference signals (RS) are spaced more closely in the frequency
domain than for the non-MBSFN transmission, reducing the separation to
every other subcarrier instead of every sixth subcarrier. This improves the
accuracy of the channel estimation that can be achieved for the longer delay
spreads.
• eNB provides IPv4 and IPv6 multicast functionality. eNB can join a specific
multicast group that MCE provides in MBMS Session Start Request message.
• eNB uses SIB2, SIB3, SIB13, SIB15 (Rel-11), and SIB16 (Rel-11) for
eMBMS. SIB2 and SIB13 information shall be consistent. Regarding this, they
need to be scheduled in the same SIB group that has the same System
Information Periodicity.
• In addition, eNB shall broadcast SIB3 that has eMBMS related information.
"NeighCellConfig" IE in SIB3 can help UE make a fast decision about the
change of MBSFN configuration when it moves from cell to cell. When the
neighbor cells have the same MBSFN subframe configuration as the serving
cell, the parameter must be set to "10".
IP Multicast
Link redundancy is provided for M1 interface. If the primary M1 interface goes
down, the eNB will try to send IGMP join message through the secondary M1
interface. If eNB receives multicast packets from both M1 interfaces, it processes
the packets received from the interface that the eNB joined through and the other
packets are discarded.
M2 Interface
Samsung eNB can interwork only with Samsung MCE because there are some
Samsung proprietary interfaces for M2 interface between the eNB and the MCE.
Samsung proprietary M2 interface includes:

Confidential
Chapter 10 Services
• SFN synchronization procedure: Non-standard messages between the MCE

and the eNB
• Proprietary use of "LCID" parameter: In the "MBMS Session List per PMCH
Item" IE of M2AP MBMS SCHEDULING INFORMATION message. The
value of LCID ranges from 0 to 128 instead of 0 to 28 to identify the session
that the MCCH Update Time is applied to.
For M2 interface, the operator can configure IP addresses separated from the eNB
IP addresses that are used for S1 interface, which allows network separation
between S1 and M2. M2 IP address which supports both IPv4 and IPv6 can be
configured with CHG-MBMS-SIGIP CLI command through the eNB or the LSM.
Synchronization(M1 interface)
To provide eMBMS service, eNBs that belong to the same MBSFN Area must
broadcast the same data at the same time so that UEs in the border area of multiple
eNBs can combine radio signals from the multiple eNBs to decode MBMS data
without interference.
To schedule for eNBs the same MBMS packet in the same time slot, SYNC
protocol is used between eNB and BM-SC. BM-SC marks a time stamp per each
MBMS packet (SYNC PDU packet). The time stamp for the first transmission
packet shall start with zero and is incremented sequentially until 57343
(synchronization period = 57344) and circulated within 0~57343. Then, the MCE
sends to eNBs the timing (= MCCH Update Time) that the first data packet shall
be transmitted considering "MinimumTimeToMBMSDataTransfer" IE. Samsung
eNB and MCE use the value of MCCH Update Time ranging from 0 to 7. The
SFN value is calculated from that MCCH Update Time x 512 (MCCH
Modification Period). For example, if MCCH Update Time is 2, then the SFN
value is 1024. Then, eNBs send the first MBMS packet in the radio frame of SFN
= 1024. After that, the packet with Time stamp = 8 is broadcast in the radio frame
of SFN = 1032.
Due to the lifecycle of SFN and backhaul delays, eNBs can be confused with the
time stamp. For example, when eNB receives a packet with time stamp that has
just passed in terms of SFN, it will wait for another SFN lifecycle to send out the
packet. Regarding this, eNB can buffer packets up to 20 seconds and it discards
the packet when buffer is overflowed.
Synchronization (M1 interface with other vendor BM-SC)

If eNB is configured to operate with other vendor BM-SC which uses GPS-based
time stamp configuration and whose SYNC period is a multiple of 4096, the
packets in the SYNC sequence with time stamp = x will be sent from the point of
the SFN = (x + alpha) mod 4096 ("alpha" is set to be a multiple of SYNC
Sequence length starting from 0 to 4095) for all eNBs. An eNB supports setting of
"alpha" for compensation of both backhaul jitter and SFN synchronization offset
between eNB and BM-SC to operate with other vendor BM-SC.

Confidential
Chapter 10 Services
eMBMS Statistics and KPI

eNB provides M2 related counters including MBMS Session Start
Request/Response/Failure, MBMS Session Stop Request/Response and MBMS
Session Update Request/Response/Failure. eNB also provides M1 related counters
for SYNC PDU and SYNC sequence per cell and per eNB.
Capacity
Category Capacity
The number of MBSFN Areas 256 per MCE
16 per eNB
8 per Cell
The number of PMCHs 15 PMCHs per MBSFN Area
The number of MBMS bearers (MTCH) 256 MBMS bearers per MCE
240 MBMS bearers per eNB
15 MBMS bearers per Cell
The number of eNBs per MCE 3000 eNBs per MCE
Requirements on BMSC
• Time stamp value of an MBMS session should begin with 0. Duration of
synchronization period is 573440 ms, which is integer times of internal SFN
length (40960 ms) of Samsung eNB.
• BM-SC shall send empty packets which is SYNC PDU Type 0 if there is no
MBMS data to send.
• Synchronization Sequence Length is 80 ms.
• To minimize buffering at eNB, BM-SC shall send eMBMS data at a constant
bit rate within GBR as possible as it can.
• The QCI is decided in consideration of the MCS level. Refer to the QCI to
MCS level mapping table as configured in the LSM. See LTE-SV0511 eMBMS
QoS for details.
SYSTEM OPERATION
How to Activate
Preconditions
• The eNB MBMS service information shall be properly configured.
• The eNB MBSFN information shall be properly configured.

Confidential
Chapter 10 Services
• The eNB MBMS information shall be properly configured.

• Run CHG-ENBMBMSSVC-CONF to configure the eNB MBMS service
information.
• Run CHG-MBSFN-INFO to configure the eNB MBSFN information.
• Run CHG-ENB-MBMSINFO to configure the eNB MBMS information and
then set MBMS_SERVICE_STATE to Active to enable the MBMS service.
Run CHG-ENB-MBMSINFO to set MBMS_SERVICE_STATE to Inactive to
disable the MBMS service.
Key Parameters
parameters.
Parameter Descriptions of CHG-ENB-MBMSINFO/RTRV-ENB-MBMSINFO
CELL_NUM This is the cell number. This is the key index.
MBMS_SERVICE_STATE This determines whether to enable or disable this feature:
• Inactive: This feature is not used.
• Active: This feature is used.
parameters.
Parameter Descriptions of CHG-ENBMBMSSVC-CONF/RTRV-ENBMBMSSVC-
CONF
MCC This is the Mobile Country Code (MCC) that comprises Public Land Mobile
Network (PLMN) for MBMS service.
MNC This is the Mobile Network Code (MNC) that comprises Public Land Mobile
Network (PLMN) for MBMS service.
CELL_RESELECTION_SWI This determines whether to enable or disable the eMBMS cell reselection
TCH functionality:
• Off: This functionality is not used.
• On: This functionality is used.
The eMBMS cell reselection functionality is to assign the highest priority to
EARFCN of eMBMS on the IdleModeMobilityControlInfo IE of the
RRCConnectionRelease message when a UE which is receiving or is
interested to receive eMBMS is transiting to the RRC idle mode.

Confidential
Chapter 10 Services
Parameter Descriptions of CHG-MBSFN-INFO/RTRV-MBSFN-INFO

DB_INDEX This is the DB index.
MBMS_SERVICE_AREA_U This indicates whether to use MBMS Service Area.
SAGE • no_use: The related MBMS Service Area information is not used.
• use: The related MBMS Service Area information is used.
MBMS_SERVICE_AREA_ID This Indicates an MBMS service area including a set of MBMS Service Area
Identities (MBMS SAIs).
Parameter Descriptions of CHG-ENB-MBMSINFO/RTRV-ENB-MBMSINFO

NOTIFICATION_REPETITI This is used to decide actual change notification repetition period.
ON_COEFF
MBMS_SERVICE_STATE This determines whether to enable or disable this feature:
• Inactive: This feature is not used.
• Active: This feature is used.
MBSFN_SYNC_AREA_ID_ This determines whether the value of the MBSFN_SYNC_AREA_ID attribute is
AUTO_ENABLE automatically generated or not:
• Off: The value of the MBSFN_SYNC_AREA_ID attribute is not automatically
generated.
• On: The value of the MBSFN_SYNC_AREA_ID attribute is automatically
generated.
MBSFN_SYNC_AREA_ID This is the MBMS Synchronization Area Identity.
Counters and KPIs

MBMS eNB Signaling M2ConnEstabAtt Counted when the eNB has attempted to transmit the
M2AP M2 SETUP REQUEST message to the MCE.
M2ConnEstabSucc Counted when the eNB has received the M2AP M2
SETUP RESPONSE message from the MCE.
M2ConnEstabFail_ Counted when the eNB has received the M2AP M2
M2AP_CU_FAIL SETUP FAILURE message from the MCE since the M2
setup procedure failed due to a cause defined in the
3GPP TS 36.443 specification.
M2ConnEstabFail_ Counted when the eNB cannot receive the M2AP M2
M2AP_LINK_FAIL SETUP RESPONSE/FAILURE message from the MCE
during the M2 setup procedure.
SessionStartAtt Counted when the eNB has received the M2AP MBMS
SESSION START REQUEST message from the MCE.
SessionStartSucc Counted when the eNB has transmitted the M2AP
MBMS SESSION START RESPONSE message to the
MCE.

Confidential
Chapter 10 Services

SessionStartFail_M Counted when the eNB has transmitted the M2AP
2AP_CU_FAIL MBMS SESSION START FAILURE message to the
MCE since the MBMS session start procedure failed
due to a cause defined in the 3GPP TS 36.443
specification.
SessionStartFail_M Counted when the eNB cannot transmit the M2AP
2AP_LINK_FAIL MBMS SESSION START RESPONSE/FAILURE
message to the MCE during the MBMS session start
procedure.
SessionStopAtt Counted when the eNB has been received the M2AP
MBMS SESSION STOP REQUEST message from the
MCE.
SessionStopSucc Counted when the eNB has transmitted the M2AP
MBMS SESSION STOP RESPONSE message to the
MCE.
SessionStopFail_M Counted when the eNB cannot transmit the M2AP
2AP_LINK_FAIL MBMS SESSION STOP RESPONSE message to the
MCE during the MBMS session stop procedure.
SessionUpdateAtt Counted when the eNB has received the M2AP MBMS
SESSION UPDATE REQUEST message from the MCE.
SessionUpdateSuc Counted when the eNB has transmitted the M2AP
c MBMS SESSION UPDATE RESPONSE message to
the MCE.
SessionUpdateFail Counted when the eNB has transmitted the M2AP
_M2AP_CU_FAIL MBMS SESSION UPDATE FAILURE message to the
MCE since the MBMS session update procedure failed
due to a cause defined in the 3GPP TS 36.443
specification.
SessionUpdateFail Counted when the eNB cannot transmit the M2AP
_M2AP_LINK_FAIL MBMS SESSION UPDATE RESPONSE/FAILURE
message to the MCE during the MBMS session update
procedure.
MBMS eNB Sync SyncPDU_Type0_ Counted when the eNB has received SYNC PDU Type
RxCount 0 by the SYNC handler.
SyncPDU_Type1_ Counted when the eNB has received SYNC PDU Type
SyncPDU_Type3_ Counted when the eNB has received SYNC PDU Type
DroppedSyncSequ Counted when SYNC sequence has been discarded.
enceCount
DroppedSyncPDUC Counted when SYNC PDUs with invalid TEIDs has
ount_INVALID_TEI been dropped.
D The number of dropped SYNC PDUs has been counted.
DroppedSyncPDUB Counted when SYNC PDUs with invalid TEIDs has
yte_INVALID_TEID been dropped.
The number of bytes of dropped SYNC PDUs has been
counted.
REFERENCE
Confidential
Chapter 10 Services
[2] 3GPP TS 29.061 SGmB interface
[3] 3GPP TS 29.274 Sm interface
[4] 3GPP TS 25.446 MBMS Synchronization Protocol (SYNC)
[5] 3GPP TS 36.444 M3AP
[6] 3GPP TS 36.443 M2AP
[7] 3GPP TS36.331 eMBMS RRC
[8] 3GPP TS 22.246 MBMS User Service stage 1
[9] 3GPP TS26.346 Multimedia Broadcast/Multicast Service (MBMS); Protocols
and codecs
[10] 3GPP TS23.246 Multimedia Broadcast/Multicast Service (MBMS);
Architecture and functional description

Confidential
Chapter 10 Services
LTE-SV0503, Multicell and Multicast

Coordination (MCE)
INTRODUCTION
Multicell and Multicast Coordination Entity (MCE) is an entity that conducts
session management and radio resource allocation for eMBMS. Samsung MCE is
a "Centralized MCE" as opposed to a "Distributed MCE", and is provided as an
external server.
BENEFIT
• Operator can provide eMBMS service and increase radio resource utilization.
• Wide MBSFN area is provided to minimize eMBMS interference between
cells.
• Continuous eMBMS service is provided even in case when eNB fails and
restarts.
• Resilient MCE system is provided by 1:1 active and standby redundancy
• Centralized MCE allows larger MBSFN Area (more eNBs) than Distributed
MCE model.
DEPENDENCY
o eNB, MME, MCE, BMSC
o E-UTRAN (LTE)
o M2 I/F, M3 I/F
o LTE-SV0501 (eMBMS Basic Function), LTE-SV0504 (eMBMS Resource
Allocation)
• Others:
o eNB, MME, MBMS GW and BM-SC are required for eMBMS service.
LIMITATION
None

Confidential
Chapter 10 Services
SYSTEM IMPACT
None
FEATURE DESCRIPTION
Samsung MCE is provided as an external server. Advantages of the centralized
MCE architecture are as follows:
• SCTP offloading from MME
• eMBMS service restoration when eNB restarts or fails
• Large size of MBSFN area
MCE is an essential entity for eMBMS service. This feature covers following basic
and advanced MCE functions:
• M2 and M3 interface
• eMBMS session start and stop based on MBMS Service Area
• 1:1 Active and Standby redundancy
• eMBMS session restoration when eNB restarts or fails
Basic Configuration of MCE

PLMN, MCE ID (0~65535), and MCE Name are configured in the MCE with
CHG-MBMSMME-CONF CLI. An MCE supports only either TDD or FDD when
configuring duplex mode of the eNBs connected with the MCE. It can also be
configured with "duplex mode" parameter via CHG-MCE-CONF CLI in the MCE
or the LSM.
SCTP connection related parameters with eNBs or MMEs are configured via
CHG-MCECONN-PARA CLI. Timer value setting for MCE is available with CHG-
MBMS-MCETIMERINFO CLI. CHG-MSIGDSCP-DATA CLI configure Signal
Class ID (0: M2 Signaling, 1: M3 Signaling) within the MCE and its DSCP value.
eNBs IPs in an MCE can be configured with CHG-MBMSENB-CONF CLI through
the MCE or the LSM. MCE can have SCTP connections with maximum 16
MMEs. MME IPs in an MCE can be configured with CHG-MBMSMME-CONF CLI
through the MCE or the LSM.
M2 Interface Management
According to 3GPP TS36.443, MCE and eNB setup M2 connection and support
following procedures.
• M2 Setup procedures to make M2 connection
• M2 Reset procedures
• ENB Configuration Update procedures to update application level eNB
configuration data

Confidential
Chapter 10 Services
• MCE Configuration Update procedures to update application level MCE

configuration data
M3 Interface Management
According to 3GPP TS36.444, MCE and MME setup M3 connection and support
following procedures.
• M3 Setup procedures to make M3 connection
• M3 Reset procedures
• MCE Configuration Update procedures to update application level MCE
configuration data
MBMS Session Management

According to 3GPP TS36.443 and 3GPP TS36.444, MCE supports MBMS session
control functions.
• MBMS Session Start and Stop procedures initiated by MME
• MBMS Session Update procedure initiated by MME
On receiving M3AP MBMS Session Start message from MME, MCE sends
M2AP MBMS Session Start message to eNBs that belong to MBSFN Areas that
support the MBMS Service Area ID specified in the M3AP MBMS Session Start
message. Mapping MBMS Service Area and MBSFN Synchronization Area to
MBSFN Area is configured with CHG-MBSFN-MAPPINGINFO CLI through the
MCE or the LSM.
The "session duration" parameter in MBMS Session Start Request message
decides the session duration. "sessionDurationUpdateSwitch" parameter in CHG-
MBMSMME-CONF CLI switches support function of "session duration update"
which is a non-standard on or off.
Via RTRV-MCESESS-STS CLI, the status of sessions such as TMGI, MME
M3AP ID, MCE M3AP ID, whether the session is ADR (Adaptive Delay
Reduction) applied session or not, MME Index in MCE are retrieved per session
index defined in MCE.
MCE provides M3 related counters per MME including MBMS Session Start
Request/Response/Failure, MBMS Session Stop Request/Response, MBMS
Session Update Request/Response/Failure. MCE provides M2 related counters per
MBSFN Area including MBMS Session Start Request/Response/Failure, MBMS
Session Stop Request/Response, MBMS Session Update
Request/Response/Failure.
MBMS Scheduling Management

Regarding scheduling, subframe allocation type (1 frame allocation or 4 frame
allocation) and MSP (MCH Scheduling Period) are configured with CHG-MCE-
CONF CLI. When MCE performs M2 Setup procedures with eNBs, it delivers
MCCH related BCCH information to configure MCCH in the radio subframe to

Confidential
Chapter 10 Services
eNBs through M2 Setup Response. It can be configured with CHG-MCCH-

RELATEDBCCH CLI through the MCE or the LSM.
For resource allocation and MBMS bearer scheduling, see LTE-SV0504 eMBMS
Resource Allocation.
MCE Redundancy
Samsung MCE provides active and standby redundancy. When an active server
fails, the standby server takes over the role without any service impact. Figures
below depict configuration of MCE. By adding an outer L2 Switch, switch
redundancy can be supported. Active and standby servers share the same IP
interface so that the active and standby architecture is transparent to eNB or MME.
Active server periodically backups data to standby server. When active server fails
(SW or HW fails or board reset), the standby server will take over the role in a few
seconds. After switchover, MCE makes SCTP setup with all of the eNBs, and
MCE also makes SCTP setup with MME. However, these switchover procedures
have no impact on ongoing eMBMS data sessions.
1 Use of one L2 switch
2 Use of two L2 switches (Switch redundancy)

Confidential
Chapter 10 Services
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-MCE-CONF/RTRV-MCE-CONF
DB_INDEX Index of this DB.
MCE_MCC The PLMN information (MCC) of MCE. It is a three-digit number with each
digit being from 0 to 9.
MCE_MNC The PLMN information (MNC) of MCE. It is a three-digit or two-digit number
MCE_ID Index of MCE.
DUPLEX_MODE The duplex mode information of the eNB connected with MCE.
MCE_NAME The Name representing MCE
SUBFRAME_ALLOC_TYPE The MBSFN subframe allocation type. It shall have either oneFrame or
fourFrames.

Confidential
Chapter 10 Services
BMSC_VENDOR The type of BM-SC vendor. It shall have either Samsung BM-SC or other
vendor BM-SC.
Parameter Descriptions of CHG-MBMSENB-CONF/RTRV-MBMSENB-CONF

ENB_INDEX Index of the eNB.
STATUS The validity of the eNB information.
ENB_MCC The PLMN information (MCC) of eNB. It is a three-digit number with each
digit being from 0 to 9.
ENB_MNC The PLMN information (MNC) of eNB. It is a three-digit or two-digit number
ENB_IP_V4 The IP address of the eNB in the IP version 4 format.
ENB_IP_V6 The IP address of the eNB in the IP version 6 format.
Parameter Descriptions of CHG-MBMSMME-CONF/RTRV-MBMSMME-CONF

MME_INDEX Index of MME.
STATUS The validity of the MME information.
MME_IP_V4 The IP address of the MME in the IP version 4 format.
MME_IP_V6 The IP address of the MME in the IP version 6 format.
Parameter Descriptions of CHG-MBSFN-MAPPINGINFO/RTRV-MBSFN-

MAPPINGINFO
MBSFN_AREA_ID Index for changing and retrieving MBSFN area id.
STATUS Status of MBSFN Mapping Info
MBSFN_SYNC_AREA_ID MBSFN Synchronization Area ID
MBMS_SERVICE_AREA_ID MBSFN Service Area ID
Counters and KPIs

MBMS_M2_SETUP M2ConnEstabAtt The count of M2 Session Setup attempts that is
received by the MCE
M2ConnEstabSucc The count of M2 Session Setup successes that is
transmitted by the MCE
M2ConnEstabFail_M The count of release due to the M2 specification
2apCuFail cause during the M2 Session Setup
M2ConnEstabFail_M The count of release due to M2 SCTP Link failure
2apLinkFail during the M2 Session Setup
SessionStartAtt The count of M2 MBMS Session Start request
attempts that is transmitted by the MCE

Confidential
Chapter 10 Services

SessionStartSucc The count of M2 MBMS session start response
success that is received by the MCE
SessionStartFail_CpC The count of release due to reset notification (MCE
cFail failure or block restart) from MMCB or by MCCB
during the M2 MBMS Session Start procedure
SessionStartFail_CpC The count of release due to insufficient capacity-
apaCacFail based MCE resources during the M2 MBMS session
Start procedure
SessionStartFail_M2a The count of release due to the M2 specification
pCuFail cause during the M2 Session Setup
SessionStartFail_M2a The count of release due to M2 SCTP Link failure
pLinkFail during the M2 Session Setup
SessionStopAtt The count of M2 MBMS Session Stop Request
attempts transmitted by the MCE
SessionStopSucc The count of M2 MBMS Session Stop Response
successes received by the MCE
SessionStopFail_CpC The count of release due to reset notification (MCE
cFail failure or block restart) from ECMB or by ECCB during
the M2 Session Stop procedure
SessionStopFail_M2a The released count due to M2 SCTP Link failure
pLinkFail during M2 Session Stop
SessionStartFail_M2 The number of failures due to an exceptional situation
OtherReasons other than the reason specified by the statistics in the
MCE
SessionUpdateAtt The number of M2 MBMS Session Update Request
transmitted from MCE to the eNB
SessionUpdateSucc The number of M2 MBMS Session Update Response
transmitted from eNB to the MCE
SessionUpdateFail_M The number of M2 MBMS Session Update Failure
2AP_CU_FAIL according to cause in 3GPP TS 36.443 specification
SessionUpdateFail_M The number of failure to response in M2 MBMS
2AP_TO Session Update procedure
SessionDrop_M2SCT The cumulate number of dropped sessions when Out
P_OOS of Service occurs on M2 SCTP
SessionDrop_M2Res The cumulate number of sessions that the message
et to eNB contains when MCE receive M2 Reset
(partial), and it sends back M2Session Start Request
to eNB.
MBMS_SESSION_SETUP SessionStartAtt The count of M3 MBMS session start request
attempts received by the MCE
SessionStartSucc The count of M3 MBMS session Start response
successes transmitted by the MCE
SessionStartFail_CpC The count of release due to insufficient capacity-
apaCacFail based MCE resources during the M3 MBMS session
Start procedure
SessionStartFail_M3a The count of release due to the M3 specification
pCuFail cause during the M3 Session Setup
SessionStartFail_M3a The count of release due to M3 SCTP Link failure
pLinkFail during the M3 Session Setup
SessionStopAtt The count of M3 MBMS session stop request attempts
received by the MCE

Confidential
Chapter 10 Services

SessionStopSucc The count of M3 MBMS session stop response
successes transmitted by the MCE
SessionStopFail_CpC The count of release due to reset notification (MCE
cFail failure or block restart) from MMCB or by MCCB
during the M3 MBMS Session Stop procedure
SessionStopFail_M3a The count of release due to M3 SCTP Link failure
pLinkFail during M3 Session Stop
SessionUpdateAtt The number of M3 MBMS Session Update Request
transmitted from the MME to the MCE
SessionUpdateSucc The number of M3 MBMS Session Update Response
transmitted from the MCE to the MME
SessionUpdateFail_M The number of M3 MBMS Session Update Failure
3AP_CU_FAIL according to cause in 3GPP TS 36.444 specification
SessionUpdateFail_M The number of M3 SCTP link failure in M3 MBMS
3AP_LINK_FAIL Session Update procedure
MBMS_M3_SETUP M3ConnEstabAtt The number of M3 Setup Request transmitted from
the MCE to the MME
M3ConnEstabSucc The number of M3 Setup Response received by MME
M3ConnEstabFail_Cp The number of timeout when MCE does not receive
CcFail M3 Setup Response from MME
M3ConnEstabFail_M The number of M3 Setup Failure received by MME
3apCuFail
M3ConnEstabFail_M The number of SCTP link fail during M3 Setup
3apLinkFail procedure.
MBMS_M3_MCE_UPDATE M3MceConfigUpdate The number of M3 MCE Configuration Update
Att transmitted from the MCE
M3MceConfigUpdate The number of M3 MCE Configuration Update Ack
Succ received by MME
M3MceConfigUpdate The number of timeout when MCE does not receive
Fail_CpCcFail MCE Configuration Update Ack from MME
M3MceConfigUpdate The number of M3 MCE Configuration Update Failure
Fail_M3apCuFail received by MME
M3MceConfigUpdate The number of SCTP link fail during M3 MCE
Fail_M3apLinkFail Configuration Update procedure.
MBMS_MBSFN_SESSION SessionStartAtt The number of M2 MBMS Session Start Request
transmitted from MCE to the eNB in MBSFN area
SessionStartSucc The number of M2 MBMS Session Start Response
transmitted from eNB to the MCE in MBSFN area
SessionStartFail The number of M2 MBMS Session Start Failure
transmitted from eNB to the MCE in MBSFN area
this feature.
MBMS_MBSFN_SESSION MSSR Session Start Success Rate in “M2: Session Start
Request” procedure in MCE with each MBSFN area.
MSFR Session Start Failure Rate in “M2: Session Start
Request” procedure in MCE with each MBSFN area.

Confidential
Chapter 10 Services
REFERENCE
[1] 3GPP TS 36.443
[2] 3GPP TS 36.444
[3] 3GPP TS 36.300
[4] 3GPP TS 36.331

Confidential
Chapter 10 Services
LTE-SV0504, eMBMS Resource Allocation

INTRODUCTION
MCE performs an eMBMS scheduler role allocating eMBMS radio resource to
each MBMS session. The eMBMS scheduling is performed for each MBSFN area.
eNB transmits eMBMS data according to the scheduling information provided by
MCE. In addition, MCE performs MBMS session admission control functionality,
where MCE checks the capacity of MBSFN area, MCE, eNB, and cell to decide
whether it accepts the call or not. In addition, MCE maintains allocated resources
and makes an admission decision based on GBR requested in MBMS Session Start
Request from BMSC.
BENEFIT
This feature facilitates efficient radio resource allocation with the statistical
multiplexing of the logical channels into a given physical subframe.
DEPENDENCY
E-UTRAN (LTE)
M2 I/F, M3 I/F
LTE-SV0501 (eMBMS Basic Function)
• Others:
None
LIMITATION
For a 5MHz carrier, an MCS of at least 7 should be used to provide a TBS large
enough to deliver the MCCH in one sub-frame.
SYSTEM IMPACT
PRACH configuration index (see LTE-ME0601) should be decided not to transmit
RAR (Random Access Response) on MBSFN subframes (FDD: #1, #2, #3, #6, #7,
#8).

Confidential
Chapter 10 Services
FEATURE DESCRIPTION
eMBMS Channels
The channels used in LTE eMBMS are largely classified into a logical channel, a
transport channel, and a physical channel and they are mapped with each channel
as shown below.
• Logical channel: MCCH, MTCH
• Transport channel: MCH
• Physical channel: PMCH
eMBMS Radio Resource Allocation

Below is the procedure flow explaining the resource allocation in the MCE. The
MCE performs resource allocation based on the MBSFN area, PMCH, QCI, GBR,
and so on. after receiving the MBMS session start request message from the
BMSC. If the resource allocated for eMBMS is not sufficient, the MCE transmits
the MBMS session start failure (Session Reject) message to the MME.

Confidential
Chapter 10 Services
In Step 0, The MCE decides on which MBSFN area a new session (ID: TMGI) is
started based on the service area ID included to the MBMS session start request
message.
In Step 1, the number of all physical radio subframes for the session in the
MBSFN area decided in Step 0 is calculated with the following process.
• Obtain the data MCS level mapped to the MBSFN area with QCI-Data MCS
Mapping table
• Calculate the number of total available MBSFN subframes within Common
Subframe Allocation Period (CSAP) from MAX_Subframe_num, Radio
Frame Allocation Period (RFAP).
• Obtain the size of data volume that should be transmitted for the session
during CSAP.
• Calculate total number of subframes by applying signaling MCS for the
signaling like MCCH, MSI and applying data MCS for data traffic.
• If the resource is insufficient, reject the request.

Confidential
Chapter 10 Services
In Step 2, a PMCH can be configured by considering MCCH Repetition Period,

CSAP, MCH Scheduling Period (MSP), Radio Frame Allocation Period (RFAP),
Radio Frame Allocation Offset (RFAO) and so on.
Resource Allocator Enhancement

• Interleaved Broadcast (Burst Packet loss resilient) support
When creating a subframe allocation pattern, the distance between subframes is
maximized to make the channel where successive packets are experiencing less
correlated.
Decision of RFAP and MBSFN subframe pattern.

• RFAP and MBSFN subframe allocation pattern (bitmap pattern) are decided
according to the required number of MBSFN subframes as shown in the tables
below.
• RFAO is unique for each MBSFN area.
• CSAP and MSP are fixed to 320 ms.
• The maximum number of MBSFN subframes per a radio frame can be
configured by setting "maxSubframeNum" parameter from 1 to 6 with CHG-
MBMSSCH-INFO CLI command through the MCE or the LSM.
MBSFN Subframe Allocation table for FDD oneFrame

• When 1 MBSFN area is configured, the available RFAPs are 32, 16, 8, 4, 2
and 1.
• When 2 MBSFN areas are configured, the available RFAPs are 32, 16, 8, 4
and 2.
• When 4 MBSFN areas are configured, the available RFAPs are 32, 16, 8, and
4.

Confidential
Chapter 10 Services
• When 8 MBSFN areas are configured, the available RFAPs are 32, 16, and 8.
When MAX_SUBFRAME_NUM’ = 1 When MAX_SUBFRAME_NUM’ = 2
Bit allocation Bit allocation
for each subframe number for each subframe number
# of # of
RFAP 1 2 3 6 7 8 RFAP 1 2 3 6 7 8
Subframes Subframes
32 1x1 1 1 X X X X X 32 1x1 1 1 X X X X 0
16 1x2 2 1 X X X X X 16 1x2 2 1 X X X X 0
8 1x4 4 1 X X X X X 8 1x4 4 1 X X X X 0
4 1x8 8 1 X X X X X 4 1x8 8 1 X X X X 0
2 1x16 16 1 X X X X X 2 1x16 16 1 X X X X 0
1 1x32 32 1 X X X X X 1 1x32 32 1 X X X X 0
1 2x32 64 1 X X X X 1

# of # of
RFAP 1 2 3 6 7 8 RFAP 1 2 3 6 7 8
Subframes Subframes
32 1x1 1 1 X 0 X X 0 32 1x1 1 1 X 0 0 X 0
32 2x1 2 1 X 0 X X 1 32 2x1 2 1 X 0 0 X 1
32 3x1 3 1 X 1 X X 1 32 3x1 3 1 X 1 0 X 1
16 2x2 4 1 X 0 X X 1 16 2x2 4 1 X 0 0 X 1
16 3x2 6 1 X 1 X X 1 16 3x2 6 1 X 1 0 X 1
8 2x4 8 1 X 0 X X 1 8 2x4 8 1 X 0 0 X 1
8 3x4 12 1 X 1 X X 1 8 3x4 12 1 X 1 0 X 1
4 2x8 16 1 X 0 X X 1 4 2x8 16 1 X 0 0 X 1
4 3x8 24 1 X 1 X X 1 4 3x8 24 1 X 1 0 X 1
2 2x16 32 1 X 0 X X 1 2 2x16 32 1 X 0 0 X 1
2 3x16 48 1 X 1 X X 1 2 3x16 48 1 X 1 0 X 1
1 2x32 64 1 X 0 X X 1 1 2x32 64 1 X 0 0 X 1
1 3x32 96 1 X 1 X X 1 1 3x32 96 1 X 1 0 X 1
1 4x32 128 1 X 1 1 X 1

# of # of
RFAP 1 2 3 6 7 8 RFAP 1 2 3 6 7 8
Subframes Subframes
32 1x1 1 1 0 0 0 X 0 32 1x1 1 1 0 0 0 0 0
32 2x1 2 1 0 0 0 X 1 32 2x1 2 1 0 0 0 0 1
32 3x1 3 1 0 1 0 X 1 32 3x1 3 1 0 1 0 0 1

Confidential
Chapter 10 Services

# of # of
RFAP 1 2 3 6 7 8 RFAP 1 2 3 6 7 8
Subframes Subframes
32 4x1 4 1 0 1 1 X 1 32 4x1 4 1 0 1 1 0 1
32 5x1 5 1 1 1 1 X 1 32 5x1 5 1 1 1 1 0 1
16 3x2 6 1 0 1 0 X 1 16 3x2 6 1 0 1 0 0 1
16 4x2 8 1 0 1 1 X 1 16 4x2 8 1 0 1 1 0 1
16 5x2 10 1 1 1 1 X 1 16 5x2 10 1 1 1 1 0 1
8 3x4 12 1 0 1 0 X 1 8 3x4 12 1 0 1 0 0 1
8 4x4 16 1 0 1 1 X 1 8 4x4 16 1 0 1 1 0 1
8 5x4 20 1 1 1 1 X 1 8 5x4 20 1 1 1 1 0 1
4 3x8 24 1 0 1 0 X 1 4 3x8 24 1 0 1 0 0 1
4 4x8 32 1 0 1 1 X 1 4 4x8 32 1 0 1 1 0 1
4 5x8 40 1 1 1 1 X 1 4 5x8 40 1 1 1 1 0 1
2 3x16 48 1 0 1 0 X 1 2 3x16 48 1 0 1 0 0 1
2 4x16 64 1 0 1 1 X 1 2 4x16 64 1 0 1 1 0 1
2 5x16 80 1 1 1 1 X 1 2 5x16 80 1 1 1 1 0 1
1 3x32 96 1 0 1 0 X 1 1 3x32 96 1 0 1 0 0 1
1 4x32 128 1 0 1 1 X 1 1 4x32 128 1 0 1 1 0 1
1 5x32 160 1 1 1 1 X 1 1 5x32 160 1 1 1 1 0 1
1 6x32 192 1 1 1 1 1 1
MBSFN Subframe Allocation Table for FDD fourFrame

• For fourFrame, only two MBSFN areas can be configured.
• When 1 MBSFN area is configured, the available RFAPs are 32, 16, 8, and 4.
• When 2 MBSFN areas are configured, the available RFAPs are 32, 16, and 8.
When MAX_SUBFRAME_NUM’ = 1
Bit allocation Bit allocation Bit allocation Bit allocation
for the first radio frame for the second radio frame for the third radio frame for the fourth radio frame
# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 1x1 1 1 X X X X X 0 X X X X X 0 X X X X X 0 X X X X X

Confidential
Chapter 10 Services

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 1x1 1 1 X X X 0 X 0 X X X 0 X 0 X X X 0 X 0 X X X 0 X

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 1x1 1 1 X 0 X 0 X 0 X 0 X 0 X 0 X 0 X 0 X 0 X 0 X 0 X
32 2x1 2 1 X 0 X 0 X 0 X 0 X 0 X 1 X 0 X 0 X 0 X 0 X 0 X
32 3x1 3 1 X 0 X 0 X 1 X 0 X 0 X 1 X 0 X 0 X 0 X 0 X 0 X
32 4x1 4 1 X 0 X 0 X 1 X 0 X 0 X 1 X 0 X 0 X 1 X 0 X 0 X
32 5x1 5 1 X 0 X 1 X 1 X 0 X 0 X 1 X 0 X 0 X 1 X 0 X 0 X
32 6x1 6 1 X 0 X 1 X 1 X 0 X 0 X 1 X 0 X 1 X 1 X 0 X 0 X
32 7x1 7 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 0 X
32 8x1 8 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X
32 9x1 9 1 X 1 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X

Confidential
Chapter 10 Services

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 10x1 10 1 X 1 X 1 X 1 X 0 X 1 X 1 X 1 X 1 X 1 X 0 X 1 X
32 11x1 11 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 0 X
16 6x2 12 1 X 0 X 1 X 1 X 0 X 0 X 1 X 0 X 1 X 1 X 0 X 0 X
16 7x2 14 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 0 X
16 8x2 16 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X
16 9x2 18 1 X 1 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X
16 10x2 20 1 X 1 X 1 X 1 X 0 X 1 X 1 X 1 X 1 X 1 X 0 X 1 X
16 11x2 22 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 0 X
8 6x4 24 1 X 0 X 1 X 1 X 0 X 0 X 1 X 0 X 1 X 1 X 0 X 0 X
8 7x4 28 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 0 X
8 8x4 32 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X
8 9x4 36 1 X 1 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X
8 10x4 40 1 X 1 X 1 X 1 X 0 X 1 X 1 X 1 X 1 X 1 X 0 X 1 X
8 11x4 44 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 0 X
4 6x8 48 1 X 0 X 1 X 1 X 0 X 0 X 1 X 0 X 1 X 1 X 0 X 0 X
4 7x8 56 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 0 X
4 8x8 64 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X
4 9x8 72 1 X 1 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X 1 X 0 X 1 X
4 10x8 80 1 X 1 X 1 X 1 X 0 X 1 X 1 X 1 X 1 X 1 X 0 X 1 X
4 11x8 88 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 0 X
4 12x8 96 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X 1 X

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 1x1 1 1 X 0 X 0 0 0 X 0 X 0 0 0 X 0 X 0 0 0 X 0 X 0 0
32 2x1 2 1 X 0 X 0 0 0 X 0 X 0 0 1 X 0 X 0 0 0 X 0 X 0 0
32 3x1 3 1 X 0 X 0 0 1 X 0 X 0 0 1 X 0 X 0 0 0 X 0 X 0 0
32 4x1 4 1 X 0 X 0 0 1 X 0 X 0 0 1 X 0 X 0 0 1 X 0 X 0 0
32 5x1 5 1 X 0 X 1 0 1 X 0 X 0 0 1 X 0 X 0 0 1 X 0 X 0 0
32 6x1 6 1 X 0 X 1 0 1 X 0 X 0 0 1 X 0 X 1 0 1 X 0 X 0 0
32 7x1 7 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 0 0
32 8x1 8 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0
32 9x1 9 1 X 1 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0
32 10x1 10 1 X 1 X 1 0 1 X 0 X 1 0 1 X 1 X 1 0 1 X 0 X 1 0
32 11x1 11 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 0 0
32 12x1 12 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
32 13x1 13 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
32 14x1 14 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 1 1 X 1 X 1 0
32 15x1 15 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 0
16 8x2 16 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0

Confidential
Chapter 10 Services

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
16 9x2 18 1 X 1 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0
16 10x2 20 1 X 1 X 1 0 1 X 0 X 1 0 1 X 1 X 1 0 1 X 0 X 1 0
16 11x2 22 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 0 0
16 12x2 24 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
16 13x2 26 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
16 14x2 28 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 1 1 X 1 X 1 0
16 15x2 30 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 0
8 8x4 32 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0
8 9x4 36 1 X 1 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0
8 10x4 40 1 X 1 X 1 0 1 X 0 X 1 0 1 X 1 X 1 0 1 X 0 X 1 0
8 11x4 44 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 0 0
8 12x4 48 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
8 13x4 52 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
8 14x4 56 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 1 1 X 1 X 1 0
8 15x4 60 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 0
4 8x8 64 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0
4 9x8 72 1 X 1 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0 1 X 0 X 1 0
4 10x8 80 1 X 1 X 1 0 1 X 0 X 1 0 1 X 1 X 1 0 1 X 0 X 1 0
4 11x8 88 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 0 0
4 12x8 96 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
4 13x8 104 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 0 1 X 1 X 1 0
4 14x8 112 1 X 1 X 1 1 1 X 1 X 1 0 1 X 1 X 1 1 1 X 1 X 1 0
4 15x8 120 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 0
4 16x8 128 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 1 1 X 1 X 1 1
# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 1x1 1 1 0 0 X 0 0 0 0 0 X 0 0 0 0 0 X 0 0 0 0 0 X 0 0
32 2x1 2 1 0 0 X 0 0 0 0 0 X 0 0 1 0 0 X 0 0 0 0 0 X 0 0
32 3x1 3 1 0 0 X 0 0 1 0 0 X 0 0 1 0 0 X 0 0 0 0 0 X 0 0
32 4x1 4 1 0 0 X 0 0 1 0 0 X 0 0 1 0 0 X 0 0 1 0 0 X 0 0
32 5x1 5 1 0 0 X 1 0 1 0 0 X 0 0 1 0 0 X 0 0 1 0 0 X 0 0
32 6x1 6 1 0 0 X 1 0 1 0 0 X 0 0 1 0 0 X 1 0 1 0 0 X 0 0
32 7x1 7 1 0 0 X 1 0 1 0 0 X 1 0 1 0 0 X 1 0 1 0 0 X 0 0
32 8x1 8 1 0 0 X 1 0 1 0 0 X 1 0 1 0 0 X 1 0 1 0 0 X 1 0
32 9x1 9 1 0 1 X 1 0 1 0 0 X 1 0 1 0 0 X 1 0 1 0 0 X 1 0
32 10x1 10 1 0 1 X 1 0 1 0 0 X 1 0 1 0 1 X 1 0 1 0 0 X 1 0
32 11x1 11 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 0 0
32 12x1 12 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0
32 13x1 13 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0

Confidential
Chapter 10 Services

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 14x1 14 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 1 1 0 1 X 1 0
32 15x1 15 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 0
32 16x1 16 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
32 17x1 17 1 1 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
32 18x1 18 1 1 1 X 1 1 1 0 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
32 19x1 19 1 1 1 X 1 1 1 1 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
16 10x2 20 1 0 1 X 1 0 1 0 0 X 1 0 1 0 1 X 1 0 1 0 0 X 1 0
16 11x2 22 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 0 0
16 12x2 24 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0
16 13x2 26 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0
16 14x2 28 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 1 1 0 1 X 1 0
16 15x2 30 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 0
16 16x2 32 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
16 17x2 34 1 1 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
16 18x2 36 1 1 1 X 1 1 1 0 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
16 19x2 38 1 1 1 X 1 1 1 1 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
8 10x4 40 1 0 1 X 1 0 1 0 0 X 1 0 1 0 1 X 1 0 1 0 0 X 1 0
8 11x4 44 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 0 0
8 12x4 48 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0
8 13x4 52 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0
8 14x4 56 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 1 1 0 1 X 1 0
8 15x4 60 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 0
8 16x4 64 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
8 17x4 68 1 1 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
8 18x4 72 1 1 1 X 1 1 1 0 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
8 19x4 76 1 1 1 X 1 1 1 1 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
4 10x8 80 1 0 1 X 1 0 1 0 0 X 1 0 1 0 1 X 1 0 1 0 0 X 1 0
4 11x8 88 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 0 0
4 12x8 96 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0
4 13x8 104 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 0 1 0 1 X 1 0
4 14x8 112 1 0 1 X 1 1 1 0 1 X 1 0 1 0 1 X 1 1 1 0 1 X 1 0
4 15x8 120 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 0
4 16x8 128 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
4 17x8 136 1 1 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1 1 0 1 X 1 1
4 18x8 144 1 1 1 X 1 1 1 0 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
4 19x8 152 1 1 1 X 1 1 1 1 1 X 1 1 1 1 1 X 1 1 1 0 1 X 1 1
4 20x8 160 1 1 1 X 1 1 1 1 1 X 1 1 1 1 1 X 1 1 1 1 1 X 1 1
# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes

Confidential
Chapter 10 Services

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
32 1x1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
32 2x1 2 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0
32 3x1 3 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0
32 4x1 4 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0
32 5x1 5 1 0 0 0 1 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0
32 6x1 6 1 0 0 0 1 0 1 0 0 0 0 0 1 0 0 0 1 0 1 0 0 0 0 0
32 7x1 7 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 0 0
32 8x1 8 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 1 0
32 9x1 9 1 0 1 0 1 0 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 1 0
32 10x1 10 1 0 1 0 1 0 1 0 0 0 1 0 1 0 1 0 1 0 1 0 0 0 1 0
32 11x1 11 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 0 0
32 12x1 12 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
32 13x1 13 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
32 14x1 14 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 1 1 0 1 0 1 0
32 15x1 15 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 0
32 16x1 16 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
32 17x1 17 1 1 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
32 18x1 18 1 1 1 0 1 1 1 0 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
32 19x1 19 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
32 20x1 20 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1
32 21x1 21 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1
32 22x1 22 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 0 1 1
32 23x1 23 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1
16 12x2 24 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
16 13x2 26 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
16 14x2 28 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 1 1 0 1 0 1 0
16 15x2 30 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 0
16 16x2 32 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
16 17x2 34 1 1 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
16 18x2 36 1 1 1 0 1 1 1 0 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
16 19x2 38 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
16 20x2 40 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1
16 21x2 42 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1
16 22x2 44 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 0 1 1
16 23x2 46 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1
8 12x4 48 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
8 13x4 52 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
8 14x4 56 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 1 1 0 1 0 1 0
8 15x4 60 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 0
8 16x4 64 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
8 17x4 68 1 1 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
8 18x4 72 1 1 1 0 1 1 1 0 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
8 19x4 76 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
8 20x4 80 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1
8 21x4 84 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1

Confidential
Chapter 10 Services

# of
RFAP 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8 1 2 3 6 7 8
Subframes
8 22x4 88 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 0 1 1
8 23x4 92 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1
4 12x8 96 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
4 13x8 104 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
4 14x8 112 1 0 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 1 1 0 1 0 1 0
4 15x8 120 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 0
4 16x8 128 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
4 17x8 136 1 1 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1
4 18x8 144 1 1 1 0 1 1 1 0 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
4 19x8 152 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 0 1 0 1 1
4 20x8 160 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1
4 21x8 168 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1
4 22x8 176 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 0 1 1
4 23x8 184 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1
4 24x8 192 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
MCE Multi-band Support

MBSFN Synchronization Area ID is configured automatically or can be set
manually by switching "mbsfnSyncAreaIdAutoEnable" parameter on or off after
running CHG-ENB-MBMSINFO CLI per cell through the eNB or the LSM. To
support of multiple bandwidths (5, 10, 15, 20 MHz) in an MCE, automatic
configuration shall be selected.

Confidential
Chapter 10 Services
SYSTEM OPERATION
How to Activate
Key Parameters
parameters.
Parameter Descriptions of CHG-MBMSSCH-INF/RTRV-MBMSSCH-INF
MBSFN_AREA_ID This is the MBSFN area identifier.
This value is used for the index to reference a tuple.
STATUS This is the status of MBMS scheduling information:
• N_EQUIP: The MBMS scheduling information of the selected MBSFN area is
invalid.
• EQUIP: The MBMS scheduling information of the selected MBSFN area is
valid.
MAX_SUBFRAME_NUM This is the maximum value of subframe number.
MCH_SCHEDULING_PERI This is MCH Scheduling Period.
OD
QCI_MBMS_IDX This is the index of QCI-MCS table of each MBSFN area.
RFAP This is Radio Frame Allocation Period.
OFFSET This is Radio Frame Allocation Offset.
Parameter Descriptions of CHG-MCE-CONF/RTRV-MCE-CONF

SUBFRAME_ALLOC_TYPE This is the MBSFN subframe allocation type.
Counters and KPIs

with this feature.
REFERENCE
[1] Rel.9 TS 36.300
[2] Rel.9 TS 36.331
[3] Rel.9 TS 36.443

Confidential
Chapter 10 Services
LTE-SV0511, eMBMS QoS

INTRODUCTION
This feature enables operator to control the MCS level per eMBMS session. When
BMSC sends eMBMS Session Start Request message, it includes QCI in the
message. Then, the MCE uses QCI to MCS level mapping table so that it can
decide a corresponding MCS level for the eMBMS session.
BENEFIT
Operator can provide different MCS levels for the same MBMS session depending
on geographical area.
DEPENDENCY
MME MCE BMSC
M2, M3
eMBMS Basic Function (LTE-SV0501), Multicell and Multicast Coordination
(MCE) (LTE-SV0503), eMBMS Resource Allocation (LTE-SV0504) are needed
for eMBMS.
LIMITATION
None
SYSTEM IMPACT
None
FEATURE DESCRIPTION
QCI to MCS Level Mapping

eMBMS bearers (or MBMS bearer) shall be GBR bearers and associated with the
following QoS parameters.
• QoS class Identifier (QCI)
• Allocation and Retention Priority (ARP): Priority level, Pre-emption
Capability, and Pre-emption Vulnerability.
• Maximum Bit Rate (MBR), which should be set to the same as GBR

Confidential
Chapter 10 Services
• Guaranteed Bit Rate (GBR)

Samsung MCE uses a QCI to MCS level mapping table to utilize QCI as defining
of MCS level when BM-SC makes a session. Operator can configure a QCI to
MCS level mapping table in MCE or LSM as shown in the table below with CHG-
MCE-DATAMCSINFO CLI. Use of operator specific QCI (128~254) is
recommended to avoid confusion with standard QCIs. BM-SC and MCE shall
have the same understanding in using those QCIs.
Table below outlines QCI to MCS level mapping table.
eMBMS QCI Resource Type MCS Level Comment
128 GBR 11 -
129 GBR 12 -
130 GBR 13 -
131 GBR 14 -
132 GBR 24 -
133 GBR 25 -
134 GBR 26 -
135 GBR 27 -
136 GBR 28 -
Default GBR 13 Default MCS value is used when
QCI is not specified.
Different Tables per MBSFN Area

MCE provides different QCI to MCS level mapping tables per MBSFN Area.
Operator can define maximum four tables which are pre-configured considering
geographical eNB deployments or radio condition or services. For example, for the
same service, an MBSFN area that covers indoor environment and provides very
strong radio signals may have a different QCI-MCS level mapping from the
mapping for an MBSFN area that covers outdoor rural environment.
SYSTEM OPERATION
How to Activate
Preconditions
Run CHG-MBMSSCH-INF and set QCI_MCS_IDX as 0~3.
Run CHG-MCE-DATAMCSINFO and set DATA_MCS of each QCI.

Confidential
Chapter 10 Services
Key Parameters
parameters.
Parameter Descriptions of CHG-PUSCH-IDLE/RTRV-MBMSSCH-INF
QCI_MCS_IDX This field indicates index of QCI-MCS table of each MBSFN area. (0~3).
parameters.
Parameter Descriptions of CHG-MCE-DATAMCSINFO/RTRV-MCE-
DATAMCSINFO
DATA_MCS This parameter is the value of Modulation and Coding Schemes (MCS) of each
QCI.
Counters and KPIs

with this feature.
REFERENCE
[1] 3GPP TS 36.444 Release 12

Confidential
Chapter 10 Services
LTE-SV0513, eMBMS Service Continuity (SIB15)

INTRODUCTION
In the multi-carrier network where only one carrier provides eMBMS service, UEs
connected to the other carrier cannot recognize the network that provides eMBMS
service on a neighbor carrier. To resolve this problem, 3GPP Release 11
introduced SIB 15 that carries a list of Service Area ID per carrier. On receiving
the SIB15, a UE sends the MBMSInterestIndication message to move to the carrier
that provides an eMBMS service, and then an eNB handovers this UE to the
carrier.
Currently, in Samsung eNB, an operator can configure a maximum of 10 MBMS-
SAIs per carrier that can be broadcast in SIB15.
BENEFIT
Users can receive eMBMS service in multi-carrier environments.
DEPENDENCY
• HW dependency: None
• Required Network Elements: MME MCE BMSC eMBMS support is required.
• Related Radio Technology: E-UTRAN (LTE) Multi-carrier LTE service
environment
• Prerequisite Features: LTE-SV0501, eMBMS basic function and LTE-
SW1007, Inter-frequency Handover
• Others: Release 11 UEs that support eMBMS.
LIMITATION
• Assumes that a maximum of 10 MBMS SAI is provided per carrier.
SYSTEM IMPACT
This feature can be activated only when the LTE-SV0501, eMBMS basic function
and LTE-SW1007, Inter-frequency Handover features are enabled.
FEATURE DESCRIPTION
This feature allows UEs to connect to the MBMS in an MBMS coverage area
regardless of the frequency of the MBMS in the multi-frequency environment.
For this feature, the eNB performs the following functions:
• The eNB announces the frequency information (EARFCN) and SAI (MBMS

Confidential
Chapter 10 Services
Service Area ID) information of the MBMS in SIB15.

• If the eNB receives an MBMSInterestIndication message from the UE, it
performs the inter-frequency handover of the UE to the corresponding
frequency by using the information on the MBMS frequency list (for more
information, see LTE-SW1007, Inter-Frequency Handover).
eMBMS carrier frequency (earfcn) and MBMS Service Area ID can be configured
by using CHG-EMBMS-SC CLI through the eNB or the LSM.
Figure below depicts the eMBMS service continuity message flow.
0) The UE maintains its connection at 2.1 GHz. At this time, the UE refers to the
information in SIB15 and transmits the MBMSInterestIndication message to the
eNB to request the MBMS connection.
1) When the source eNB receives the MBMSInterestIndication message from the
UE, the target frequency is selected by referring to mbms-FreqList.
2) The source eNB performs the inter-frequency handover to the selected target
frequency. At this time, the target frequency is located by using the measurement
gap. The inter-frequency handover to the target frequency is performed when the
MR is received at the signal strength of the target frequency and exceeds a certain
level (measured using Event A4 or Event A5).
3) The target eNB maintains the connection and receives the MBMS.
Figure below depicts the call flow of MBMS interest indication.

Confidential
Chapter 10 Services
After receiving the MBMSInterestIndication message from the UE, the eNB refers
to CarrierFreqListMBMS-r11 in the message and performs the inter-frequency
handover to the target frequency.
For more information about the inter-frequency handover feature, see LTE-
SW1007, Inter-Frequency Handover.
Enhancement for Reselection priority in eMBMS Service UE

If the UE, which is receiving eMBMS service and has sent
MBMSInterestIndication message to eNB, transits to idle mode, the eNB set the
dedicated priority (using Idle mobility) of the carrier frequency in the UE to the
highest ranking through the RRC Release message. Then, the UE can maintain
receiving eMBMS service even in the idle mode.
Enhancement for Supporting UEs Capable of Receiving MBMS on SCell or Non-Serving

Cell
The eNB operation for UE that supports MBMS reception on SCell or
NonServingCell is as follows:
1 When the UE whose UE-EUTRA-Capability IE includes mbms-Scell reports
an MBMSInterestIndication message to the eNB:
o In case that at least one among carrier frequencies indicated in the
MBMSInterestIndication message is configured as an SCell, the eNB does
not trigger inter-frequency handover to receive MBMS service for the UE.
o In case that any carrier among carrier frequencies indicated in the
MBMSInterestIndication message is not configured as an SCell, the eNB
triggers inter-frequency handover to receive MBMS service for the UE.
2 When the UE whose UE-EUTRA-Capability IE includes both mbms-Scell
and mbms-Nonservingcell reports an MBMSInterestIndication message to
the eNB:
o In case that at least one among carrier frequencies indicated in the
MBMSInterestIndication message is included in
supportedBandCombination of the UE, the eNB does not trigger inter-
frequency handover to receive MBMS service for the UE.
o In case that any carrier among carrier frequencies indicated in the
MBMSInterestIndication message is not included in
supportedBandCombination of the UE, the eNB triggers inter-frequency
handover to receive MBMS service for the UE.

Confidential
Chapter 10 Services
eMBMS Receiving UE Pool Management

The eNB manages eMBMS receiving UE pool based on MBMSInterestIndication
message received from the UE.
• If the eNB receives the MBMSInterestIndication message from UE in the
serving cell that is providing the eMBMS service and the message includes the
serving cell frequency, it regards the UE as the eMBMS receiving UE and add
it to an eMBMS receiving UE pool.
• If the eNB receives the MBMSInterestIndication message from UE in the
serving cell that is providing the eMBMS service and the message does not
include the serving cell frequency, it does not include the UE to the eMBMS
receiving UE pool.
• In case of an inter-frequency handover of the UE by MBMSInterestIndication
message at a frequency other than the eMBMS service frequency, the UE is
regarded as the eMBMS receiving terminal and be added to the eMBMS
receiving UE pool.
Enhancement on Setting Cell Reselection Priority for Carrier providing eMBMS Service
The carriers providing eMBMS service can be set as the highest cell reselection
priority by modifying the information on the dedicated cell reselection priority
(that is, IMMCI: IdleModeMobilityControlInfo IE) made by another feature (that
is, cellReselectionPriority 7 configured by another feature needs to be modified to
6).
SYSTEM OPERATION

Confidential
Chapter 10 Services
How to Activate
Preconditions
• Run CHG-SIB-INF, and then set SIB15_PERIOD to one of 80 ms, 160 ms,
... , 5120 ms to set the broadcast interval for SIB15.
• Run CHG-SIB-INF, and then set SIB15_PERIOD to not_used not to
broadcast SIB15.
Key Parameters
parameters.
SIB15_PERIOD This is the broadcast interval for SIB15.
• 80 ms: The broadcast interval for SIB15 is 80 ms.
...
• 5120 ms: The broadcast interval for SIB15 is 5,120 ms.
• not_used: SIB15 is not broadcasted.
parameters.
SIB15_PERIOD This is the broadcast interval for SIB15.
...
• 5120 ms: The broadcast interval for SIB15 is 5,120 ms.
• not_used: SIB15 is not broadcasted.

Confidential
Chapter 10 Services
Parameter Descriptions of CHG-EMBMS-SC/RTRV-EMBMS-SC

E_MBMS_CARRIER_IDX This is the eMBMS service carrier index. This is the key index.
STATUS This specifies whether this tuple information is valid:
• N_EQUIP: This eMBMS service carrier is invalid
• EQUIP: This eMBMS service carrier is valid
EARFCN_DL This is downlink E-UTRA Absolute Radio Frequency Channel Number
(EARFCN) of eMBMS service carrier.
SAI_USAGE This is the usage flag of SAI:
• no_use: This MBSFN area information is not used.
• use: This MBSFN area information is used.
SAI This is the MBMS Service Area Identity (MBMS SAI).
MBMS Service Area (MBMS SA) is defined in 3GPP TS 23.246.
MBMS SA has a MBMS SAI or several MBMS SAIs.
A cell has a MBMS SAI or several MBMS SAIs because it belongs to a MBMS
SA or several MBMS SAs.
Counters and KPIs

MBMS Message MBMSInterestIndication Counted when eNB has received the RRC
MBMSInterestIndication message from UE.
REFERENCE
Resource Control (RRC); Protocol specification (Rel.11)

Confidential
Chapter 10 Services
LTE-SV0514, Adaptive Delay Reduction for

eMBMS
INTRODUCTION
This feature reduces the end to end delay by discarding data packets buffered at
eNBs only at the start of session, which results in pulling up the time from the
perspective of UE.
BENEFIT
In live broadcasting service, the time gap between the video played in device and
the live scene in a stadium is reduced and the UE can watch the synchronized
video display in the stadium.
DEPENDENCY
o MCE MME MBMS-GW BM-SC
o E-UTRAN (LTE)
o M2 I/F, M3 I/F
o LTE-SV0501 (eMBMS Basic Function)
• Others:
o This feature can be enabled only in Samsung MCE and eNB
LIMITATION
• To enable this feature, all the eNBs connected to the MCE shall support a
software package which includes this feature.
• When operating with other vendor BM-SC (not Samsung BM-SC), this feature
is disabled regardless of Enable / Disable setting to mitigate malfunction.
SYSTEM IMPACT
• Samsung proprietary eNB functionality needs to be supported for this feature
(refer to "eNB Functionality" in Feature Description).
• Samsung proprietary BM-SC functionality needs to be supported for this
feature (refer to "BM-SC Functionality" in Feature Description).

Confidential
Chapter 10 Services
FEATURE DESCRIPTION
Basic Concept
BM-SC transmits MBMS data packets with a time stamp. The time stamp for the
first transmission packet shall start with 0 and is incremented sequentially until
57343 (synchronization period = 57344) and circulated within 0~57343. When an
eNB received the first packet with time stamp of 0 at a specific SFN, the different
between the time stamp and the SFN is called Offset. Offset of each eNB may be
different due to backhaul delay, and this means that the amount of packets
accumulated at buffer is different between eNBs.
The concept of this feature is that although the amount of packets buffered at each
eNB is different, by knowing the amount of packets buffered commonly in all
eNBs and discarding it, time gap between the video play and the live scene can be
reduced by the amount of the discarded buffered packets at eNB. This is similar to
eliminating front of movie film, to make earlier showing time.
As shown in the figure below, if the transmission of the first packet having a time
stamp of 0 is scheduled at SFN 518 for all three eNBs by MCE, and Offset of eNB
#1 is 506, and Offset of eNB #2 is 508, and Offset of eNB #3 is 510, the packet
having a time stamp of 6 will be transmitted at SFN 524 for all eNBs.
By gathering the Offset values from all the eNBs, the MCE decides the largest
value among the Offset values. The largest Offset means that the amount of
packets accumulated in its eNB buffer is the smallest among all eNBs, and to
discard packets buffered commonly in all eNBs the largest offset is considered as
New Offset. Then, by sending the New Offset to the all eNBs, all the eNBs change
their Offset to the New Offset.
In the figure below, New Offset for all eNBs is set to 512 considering the largest
Offset = 510 plus margin by MCE. At the scheduled transmission time SFN 518,
then, the time stamp to be transmitted at eNB #1, #2, #3 are all 6 (518-512).
Finally, 60 ms packet delay reduction happens considering that originally the
packet having time stamp of 6 will be transmitted at SFN 524. At eNB #1, #2, #3,
packets having a time stamp of 0, 2, and 4 are discarded.
This occurs only once at the start of a session.

Confidential
Chapter 10 Services
To turn this feature on, "adaptiveDelayReductionUse" parameter through CHG-

MBMSDELAY-INF CLI shall be set to "on". "delayDelta" parameter in the CLI
configures the margin value that uses when calculating New Offset.
Call procedure among eNB, MCE, and BM-SC are as follows: Steps 4 ~ 5 is
executed for the MBMS session configured as
Minimum_Time_To_MBMS_Data_Tansfer = 0.
BM-SC Functionality
BM-SC transmits MBMS data after MBMS Session Start Request message
transmission to MCE after the time specified on
Minimum_Time_to_MBMS_Data_Transfer. During
Minimum_Time_to_MBMS_Data_Transfer time, all eNBs belonging to MBMS
Service Area perform session configuration, radio resource configuration,
multicast joining to prepare MBMS data transmission.
For Adaptive Delay Reduction feature, BM-SC needs to provide following
functions.
• When transmitting MBMS Session Start Request message, BM-SC sets up
"Time_to_MBMS_Data_Transfer = 0" for the live streaming session to
minimize the delay. Then, after sending MBMS Session Start Request, BM-
SC transmits MBMS data packet or empty packet (Type 0).
• Synchronization Sequence Length of session, subject to delay reduction, must
be less than 1.5 second. If Synchronization Sequence Length is greater than
1.5 second, the value of "Minimum_Time_to_MBMS_Data_Transfer" must
not set as "zero". If this session is assigned as the session subject to delay
reduction, even though initially transmitted MBMS packet is lost, time is not
Confidential
Chapter 10 Services
shifted.
MBMS data sent during initial session is lost when time is shifted. This loss will
occur for approximately 5 seconds, until MCE completes the delay reduction
procedure following the start message transmission.
MCE Functionality
MCE performs Adaptive Delay Reduction function for the session configured as
"Time_to_MBMS_Data_Transfer = 0". After receiving MBMS Session Start
Request message from MME, the procedures of MBMS Session Start Request and
MBMS Scheduling Information message transmission to the target eNB is
performed the same way as for normal eMBMS session.
For the Adaptive Delay Reduction enabled session, the eNB is notified that the
corresponding session is delay reduction session through MBMS Session Start
Request message. Afterwards, based on received “DELAY TIME
INFORMATION (SessionID, Offset, and Synchronization Sequence Length)”
from each eNB, MCE detects eNB which was most delayed receiving MBMS
data, and time shift value is determined by the most delayed eNB. MCE transmits
the final offset value to all eNBs to make time shift.
Time shift is applied the same way even when eNB is restarted.
eNB Functionality
For the delay reduction function enabled session, the eNB will discard MBMS data
upon receiving MBMS Session Start Request message until receiving TIME
SHIFT REQUEST. The synchronization sequence length can be acquired through
synchronization sequence learning for the corresponding session. eNB transmits
"the value of synchronization sequence length", "the value of SFN (Offset) when
zero timestamp received" and "Session ID (MCE-MBMS-M2AP-ID)" to MCE
through the DELAY TIME INFORMATION message.
When eNB receives TIME SHIFT REQUEST message, eNB modifies timestamp
of each packets to make radio transmission time shift.
SYSTEM OPERATION
How to Activate
Preconditions
Run CHG-MBMSDELAY-INF and set ADAPTIVE_DELAY_REDUCTION_USE
as On.

Confidential
Chapter 10 Services
Run CHG-MBMSDELAY-INF and set ADAPTIVE_DELAY_REDUCTION_USE
as OFF.
Key Parameters
parameters.
Parameter Descriptions of CHG-MBMSDELAY-INF/RTRV-MBMSDELAY-INF
ADAPTIVE_DELAY_REDUCT This parameter represents On/Off of the Adaptive Delay Reduction
ION_USE functionality.
-
Counters and KPIs

MBMS eNB Sync DroppedSyncPduCount_ The cumulated number of SYNC PDU
ADR discarded by the Adaptive Delay Reduction
functionality.
DroppedSyncPduByte_A The cumulated bytes of SYNC PDU discarded
DR by the Adaptive Delay Reduction functionality.
REFERENCE
None

Confidential
Chapter 10 Services
LTE-SV0517, eMBMS Service Restoration

INTRODUCTION
eMBMS service restoration is a function to recover eMBMS sessions when
eNB/MCE/MME/M2 link/M3 link fail.
BENEFIT
This feature enables MBMS service to continue even after the failure of
eNB/MCE/MME/M2 link/M3 link.
DEPENDENCY
o M2 I/F, M3 I/F
o LTE-SV0503 (Multicell and Multicast Coordination (MCE)), LTE-SV0514
(Adaptive Delay Reduction for eMBMS)
• Others:
o MME that support 3GPP Rel 12.
LIMITATION
To support MCE restoration, Adaptive Delay Reduction for eMBMS (LTE-
SV0514) should be on.
SYSTEM IMPACT
None
FEATURE DESCRIPTION
eMBMS Service Restoration when eNB Fails

When M2 link fails, MCE maintains MBMS service in the event of STCP failure
within time set by "enbFailoverTimer" parameter in CHG-MCECONN-PARA CLI.
SCTP multi-homing for M2 link is supported.
If M2 link is not recovered or the eNB fails, MCE delete all the MBMS sessions.
When M2 link or eNB recovers, the MCE transmits all the MBMS session
information as soon as the eNB and MCE setup M2 connection. Since the eNBs in
the same MBSFN area use the synchronized, the rebooted eNB or M2 link
recovered eNB can keep the restored MBMS sessions synchronized with neighbor
eNBs. The figure below depicts the situation.

Confidential
Chapter 10 Services
MME Restoration Support

In case of MME failure, another MME can send eMBMS Session Start Request
message with "Session Re-establishment Indication" flag when the primary MME
fails. If the session is exists in MCE, MCE will re-associate the eMBMS Session
to the secondary MME that requests session re-establishment and there is no
impact on the eNBs. If the session does not exist, MCE sends M2AP MBMS
Session Start Request to the eNBs. When interworking with Samsung BM-SE, to
support the latter case ADR (Adaptive Delay Reduction: LTE-SV0514) should be
turned on because MCE lost information of real-time time stamp value being
transmitted from the BM-SC and can obtain the information by gathering the real-
time time stamp information from eNBs with ADR. To turn on ADR,
"adaptiveDelayReductionUse" parameter through CHG-MBMSDELAY-INF CLI
shall be set to "on". MBMS Session Start Request message with "Re-establishment
indication" flag may differ from the existing one. In this case, MCE shall send
M2AP MBMS Session Update message to all the eNBs of the corresponding
MBMS Service Area.

Confidential
Chapter 10 Services
MCE and M3 link Restoration

When MCE restarts or it detects a failure in M3 link, it will send M3 Setup
Request to the MME. For this, "restorationSupport" parameter in CHG-MCE-
CONF CLI shall be set to "on". Then, MME sends M3AP MBMS Session Start
Request message to the MCE.
MBMS-GW Restoration
When MCE receives M3AP MBMS Session Start Request message with Session
Re-establishment Indication flag and the session exists, if the M3AP MBMS
Session Start Request message contains a different IP multicast address and/or a
different IP source address for the session, it shall send M2AP MBMS Session
Stop Request message to all eNBs of the MBMS Service Area to let them leave IP
multicast. Then, the MCE shall send M2AP MBMS Session Start Request message
with the updated TNL information to all eNBs of the MBMS Service Area for
eNBs to let them join IP multicast with the updated one.
SYSTEM OPERATION
How to Activate
Preconditions

Confidential
Chapter 10 Services
Key Parameters
Counters and KPIs

eMBMS MCE session-related statistics have the following items (You can retrieve
them by the MME index.).
Node restoration-related parts cannot be checked but you can see that the
MBMS_SESSION_SETUP statistics of the other MME index are increasing.
• MBMS_SESSION_SETUP: SessionStartAtt, SessionStartSucc, etc.
Family Name Counter Name Description
MBMS Session Setup SessionStartAtt Count of M3 Session Start attempts transmitted by the
MME
SessionStartSucc Count of M3 Session Start successes transmitted by
the MCE
SessionStartFail_CP_CAP M3 Session Start failure count. A failure is due to the
A_CAC_FAIL CAC by MCE.
SessionStartFail_M3AP_C M3 Session Start failure count. A failure is due to the
U_FAIL specified cause in specification TS36.444.
SessionStartFail_M3AP_LI M3 Session Start failure count. A failure is due to
NK_FAIL SCTP link failure.
SessionStopAtt Count of M3 MBMS Session Stop received by the
MCE.
SessionStopSucc Count of M3 MBMS Session Stop successes
transmitted by the MCE.
SessionStopFail_CP_CC_ Count of Failure of “M3 MBMS Session Stop” This
FAIL failure is due to reception of RESET during “Session
Strop” procedure or block restart and so on.
SessionStopFail_M3AP_LI Count of Failure of “M3 MBMS Session Stop” This
NK_FAIL failure is due to SCTP link failure.
REFERENCE
[1] 3GPP TS23.007

Confidential
Chapter 10 Services
LTE-SV0520, eMBMS Trace

INTRODUCTION
This feature performs tracing signaling messages of eMBMS in MCE. The
traceable interfaces are M2 and M3 interfaces. This trace result is transmitted to
the EMS.
BENEFIT
This feature allows operator to analyze the signaling messages transmitted and
received in MCE, which can be used for troubleshooting.
DEPENDENCY
MME MCE eNB LSM
LIMITATION
In case of CPU overload status, tracing can be suspended to prevent the negative
impact on the service users.
SYSTEM IMPACT
None
FEATURE DESCRIPTION
This feature performs tracing signaling messages of eMBMS in MCE. Operator
can enable/disable trace by TRACE_ENABLE (CHG-MCETRC-INF). Operator
commands into EMS (Element Management System) to trigger the trace at MCE.
The trace interface can be set by INTERFACES_TO_TRACE (CHG-MCETRC-
INF). The MCE, after receiving the commands from EMS, collects the signaling
message of eMBMS (M2 and M3 interfaces) and reports them to EMS.
The trace results consist of as follows:

Timestamp, Interfaces To Trace, MCE SessId, eNB MBMS M2AP ID, MME

Confidential
Chapter 10 Services
MBMS M3AP ID, TMGI, eNB Association Index, msg Size, direction, Message
Name.
SYSTEM OPERATION
How to Activate
Preconditions
• If CPU Overload status higher than "Clear", eMBMS Trace is paused.
Run CHG-MCETRC-INF and set TRACE_ENABLE as USE.
Run CHG-MCETRC-INF and set TRACE_ENABLE as NO_USE.
Key Parameters
parameters.
Parameter Descriptions of CHG-MCETRC-INF/RTRV-MCETRC-INF
TRACE_ENABLE Check whether eMBMS Trace Enable or not
parameters.
Parameter Descriptions of CHG-MCETRC-INF/RTRV-MCETRC-INF
INTERFACES_TO_TRACE Set Interface for MCE Trace.
Counters and KPIs

with this feature.
(eMBMS Trace Result Data Type is CSV of "string format", as follow.:
timestamp, Interfaces To Trace, MCE SessId, eNB MBMS M2AP ID, MME

Confidential
Chapter 10 Services
MBMS M3AP ID, TMGI, eNB Association Index, msg Size, direction, Message
Name)
REFERENCE
None

Confidential
Chapter 10 Services
LTE-SV1100, TCP Optimization

INTRODUCTION
The TCP optimization feature defined in 3GPP TS 36.323 reduces congestion at
the eNB.
This feature discards downlink PDCP PDU at the eNB per QCI when pre-
configured discard timer expires. It provides discard timer parameter for both DL
and UL. The DL parameter affects downlink at the eNB. However, The UL
parameter is transmitted to UE.
Note that each DL and UL discard timer can be set separately from SLR7.0.
BENEFIT
• Operator can prevent long queuing delay at the eNB.
• Users can experience improved end-user performance in terms of reduced TCP
round-trip time in congestion situation.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
None
TCP optimization can help reduce congestion. It prevents excessive queuing delay
at eNB, thereby reducing the round trip time (RTT) of TCP flow. And low delay
enhance the user experiences.
Coverage
None
Interfaces
None
FEATURE DESCRIPTION
The TCP optimization works for Acknowledged Mode Data (AMD) PDU in the
eNB.

Confidential
Chapter 10 Services
Discard timer value can be configured per QCI for both DL and UL.
This feature does not work when discard timer value is set to Infinity.
The eNB monitors the age of the queued up packets. When the age of a packet
exceeds the discard timer value, the packet is discarded.
If the value of discard timer value is Infinity for the QCI, packet discard operation
does not happen for that QCI.
If the discard timer value is set to a non-Infinity value, packets that are older than
discard timer is discarded. The unit of the discard timer is in milliseconds.
Effect on TCP Congestion Control due to DISCARD TIMER timeout

After the downlink packets are discarded at the eNB, at the affected TCP
sender(s), the congestion window is reduced.
A TCP sender can detect packet loss and adapt its data rate to the available rate.
• If a packet is discarded at the eNB it becomes a signal of light congestion for
the TCP sender.
• If there are many packet discarded at the eNB, it is a signal of serious
congestion.
The congestion window is reduced when a missing packet(s) is detected, thereby
adapting the available rate by reducing the congestion window size.
For more information on Congestion Control at TCP, refer TCP Congestion
Control RFC 2581 and RFC 5681.
SYSTEM OPERATION

Confidential
Chapter 10 Services
How to Activate
Preconditions
Key Parameters
parameters.
Parameter Descriptions of CHG-PDCP-INF/RTRV-PDCP-INF
DISCARD_TIME This parameter is the discard timer value for a packet buffer managed per radio bearer
R (RB) in the PDCP. The PDCP keeps buffering for re-transmission until successful
transmission is confirmed either by a lower layer or the PDCP status report and discards
the packet after the set period has elapsed at UE side.
Parameter set: ms50, ms100, ms150, ms300, ms500, ms750, ms1500, and infinity
DISCARD_TIME This parameter is the discard timer value for a packet buffer managed per radio bearer
R_DL (RB) in the PDCP downlink. The PDCP keeps buffering for re-transmission until
successful transmission is confirmed either by a lower layer or the PDCP status report and
discards the packet after the set period has elapsed.
Parameter set: ms50, ms100, ms150, ms200, ms250, ms300, ms350, ms400, ms450,
ms500, ms750, ms1000, ms1500, ms2000, ms2500, ms3000, ms3500, ms4000, ms4500,
ms5000, and Infinity.
Below is Samsung's recommendation value of PDCP discard timer for DL.

QCI Resource Packet Delay Example Service Samsung's Description
Type Budget recommendation value
of PDCP discard timer
1 GBR 100 ms Conversational 300 ms According to our model,
Voice the PELR can be
controlled to 10-3 with a
delay of about 180 ms or
more.
2 GBR 150 ms Conversational 500 ms In the case of delay
Video (Live sensitive traffic, the PELR
Streaming) level in TS 23.203 may
3 GBR 50 ms Real Time 300 ms affect the quality of
Gaming service, so Samsung has
calculated PDCP discard
timer through appropriate
modeling.
4 GBR 300 ms Non- Infinity • Extremely longer delay,
Conversational especially when 2 or
Video (Buffered

Confidential
Chapter 10 Services
QCI Resource Packet Delay Example Service Samsung's Description

Type Budget recommendation value
of PDCP discard timer
Streaming) more sessions share a
bearer.
5 Non-GBR 100 ms IMS Signaling
• TCP throughput
6 Non-GBR 300 ms Video (BUffered fluctuation due to the
Streaming) late retransmission
TCP-based (for when there are packet
example, www, loss.
e-mail, chat, ftp,
• Throughput degradation
p2p file sharing,
when UE has both DL
progressive and UL TCP traffic.
video, and so
on.)
7 Non-GBR 100 ms Voice, Video 300 ms In the case of delay
(Live Streaming), sensitive traffic, the PELR
Interactive level in TS 23.203 may
Gaming affect the quality of
service, so Samsung has
calculated PDCP discard
timer through appropriate
modeling.
8 Non-GBR 300 ms Video (BUffered 1500 ms Considering per-UE
9 Non-GBR Streaming) throughput and
TCP-based (for conventional network
example, www, delay, shorter timer such
e-mail, chat, ftp, as 500 ms or less than
p2p file sharing, timer can be applied. But,
progressive Samsung recommends
video, and so 1500 ms for stability. It is
on.) enough to ease extremely
longer delay problem
Counters and KPIs

DL PDCP PDU discard rate PdcpPduDiscard Discard rate of PDCP PDUs
RateDL This counter displays the ratio of packets that are
discarded due to DISCARD_TIMER_DL expiry and
the total packets in the buffer over a period of 10
seconds. The units are in ppm (x 10^6).
PdcpPduDiscard The number of PDCP PDUs discarded from DL RLC
CountDL buffer.
PdcpPduReceiv The number of PDCP PDUs received in DL RLC
edCountDL buffer.
REFERENCE
[1] 3GPP TS 36.323 "Packet Data Convergence Protocol (PDCP) specification"

Confidential
Chapter 10 Services
LTE-SV1101, TCP DL AQM (Active Queue

Management)
INTRODUCTION
The large buffer of the eNB for coping with lack of air capacity and unstable /
lossy channel characteristics creates a problem, known as Bufferbloat, which
induces the performance degradation caused by extremely long queuing delay,
Such extreme delay affects QoS and QoE, especially for real-time or delay-
sensitive applications. TCP DL AQM is a feature that prevents bufferbloat
problem through active queue control.
TCP DL AQM enables an eNB to control the continuous increase of queuing
delay. The eNB monitors the queuing delay for each bearer. When the queuing
delay increases, the eNB controls the packet transmission, thereby inducing TCP
congestion control in the TCP sender.
BENEFIT
By controlling the queuing delay without throughput degradation, QoE can be
improved. Specifically, the robustness to packet loss increases. And, stalling of
video streaming service decreases in congestion situation.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
The eNB with TCP DL AQM can control the increase of queuing delay of service
bearer through active queue management. The functions provided by TCP DL
AQM are as follows.
QCI Settings to Control

TCP DL AQM can be set on/off control per QCI by two configuration parameters
AQM_ON_OFF (CHG-AQM-CTRL) and QCI (CHG-AQM-CTRL). The eNB can
perform TCP DL AQM on up to 8 QCIs including QCI 6, 7, 8, and 9. Extra 4
QCIs except QCI 6, 7, 8, and 9 can be chosen by operator.

Confidential
Chapter 10 Services
Monitoring Queuing Delay

TCP DL AQM monitors the queuing delay for each bearer.
Active Queue Management

If the queuing delay of the bearer exceeds the predefined threshold and is
increasing trend, queue management is triggered. When the triggering condition is
satisfied, TCP DL AQM changes the order of the packets in the queue or discards
the packet to be transmitted, thereby inducing TCP congestion control in the TCP
sender.
Changing the order of the packets causes the UE to receive the packet in out-of-
order, thereby inducing 3-dup acks to occur. In the case of multiple flows, it can
take a long time to occur 3-dup acks. In this case, it is effective to reduce the
transmission rate by reducing the TCP congestion window size of the TCP sender
without packet loss. Because there is no packet loss, there is no fluctuation of
throughput at all.
Discarding a packet makes sure that the UE generates 3-dup acks and reduces the
transmission rate by reducing the TCP congestion window size of the TCP sender.
Initially, the queuing delay is increased, AQM is triggered, the packet order is
changed, and the continuous order is changed, but the packet is discarded if the
queuing delay does not decrease.
If the TCP DL AQM is triggered by an increase in queuing delay in the beginning,
it changes the order of the packets. If the queuing delay does not decrease even if
the order of the packets is changed continuously, the packet is discarded.
Collecting Statistics
The eNB collects statistic about the number of re-ordered and discarded packets.
AqmReorderPdcpSduCount and AqmDiscardPdcpSduCount are the number of
total re-ordered and discarded DL PDCP SDUs by AQM operation, respectively.
Operation Details
The eNB performs the following feature-related tasks in a typical scenario:
1 The eNB measures the queuing delay for each bearer at a predetermined
interval T.
2 The queuing delays measured at T1 and T2 are defined as DT1 and DT2,
respectively.
3 If the measured queuing delay DT2 is greater than a predefined threshold,
and it is greater than the previous queuing delay DT1, the order of packets in
the queue is changed such that head-of-line packet is moved to the 5th
position in the queue. Otherwise, TCP DL AQM does nothing. We define
this operation as re-ordering.
4 After T, if the measured queuing delay is not decreasing in spite of previous
re-ordering, the head of line packet is moved to 9th position. Packet re-
ordering continues at every T period with linearly increasing moving distance

Confidential
Chapter 10 Services
(that is,, to 5th position, 9th, 13th, and so on) until the measured queuing
delay decreases. If it decreases, TCP DL AQM initializes with moving
distance 4.
5 If the moving distance increases n-1 consecutive times and nth re-ordering is
triggered where n is the predefined discard parameter, TCP DL AQM
discards the head-of-line packet instead of re-ordering it.
TCP DL AQM operates according to RFC 2581.

However, in some cases, TCP DL AQM may not work properly if TCP version
according to the operating system of the terminal and the server does not follow
the standard operation.
SYSTEM OPERATION
How to Activate
Preconditions
• A valid license key LTESV1101 is required to activate this feature.
• Run CHG-AQM-CTRL and set AQM_ON_OFF to "ON".
• Run CHG-AQM-CTRL and set AQM_ON_OFF to "OFF".
Key Parameters
parameters.
Parameter Descriptions of CHG-AQM-CTRL/RTRV-AQM-CTRL
This parameter is used for assigning QCI to indexId.
• indexId 0: 6
• indexId 1: 7
QCI • indexId 2: 8
• indexId 3: 9
• indexId 4: 0
• indexId 5: 0

Confidential
Chapter 10 Services
• indexId 6: 0
• indexId 7: 0
This parameter is used for enabling/disabling of the functionality of “Active Queue
Management”.
AQM_ON_OFF
• OFF(0): AQM function off
• ON1: AQM function on
Counters and KPIs

Family Display
Type Name Type Description
Name
AqmDiscardPdcpSduCount The number of total discard DL PDCP SDUs by AQM operation.
Packet Drop Rate The number of total reordering DL PDCP SDUs by AQM
AqmReorderPdcpSduCount
operation.
REFERENCE
[1] RFC 5681 - TCP Congestion Control
[2] Gettys, J. Bufferbloat: Dark Buffers in the Internet. IEEE Internet Computing
15(3), 95-96 (2011)

Confidential
Chapter 10 Services
LTE-SV1400, TCP UL Congestion Control

INTRODUCTION
As Transmission Control Protocol (TCP) is a bi-directional protocol, downlink
(DL) TCP sessions require uplink (UL) resources to send the acknowledgement
(ACK) packets. When UL is congested (arising from heavy UL data traffic load),
the TCP ACK packets of DL TCP sessions get delayed. This delay in sending TCP
ACK packets increases TCP Round Trip Time (RTT), which results in degradation
(limitation) in DL throughput. This feature improves TCP DL throughput when
UL is congested by selectively dropping UL packets at the eNB with the purpose
of getting lower TCP RTT.
BENEFIT
With this feature, DL throughput degradation, arising from UL congestion could
be alleviated.
DEPENDENCY
None
LIMITATION
None
SYSTEM IMPACT
When this feature is enabled with UL CA at the same time, UL cell throughput can
be degraded below peak throughput (Scell RB usage can be lower than 100 %) in
the case of the number of concurrent UL uploading UEs in the cell > 50 (limitation
is applied to SLR 7.0.0).
A minor decrease in the uplink TCP throughput is possible, due to discarding of
some UL TCP packets. As the process effectively controls the UL TCP Window,
the long-term average uplink TCP throughput should not have any significant
impact (reduction).
Coverage
None
Interfaces
None

Confidential
Chapter 10 Services
FEATURE DESCRIPTION
The figure below depicts TCP UL Congestion Control.
As shown in above figure (a), when UL is highly congested (estimated by eNB as

UL data traffic load exceeding a certain congestion threshold), TCP ACK packets
for DL TCP sessions get delayed. To reduce UL backlog, the eNB starts
probabilistically discarding some data packets of TCP UL sessions. Above figure
(b) demonstrates that intentional drops of UL TCP data packets reduce UL TCP
congestion window size at UEs. This expedites the transmission of TCP ACK
packets of the TCP DL session. Since only TCP UL data packets are discarded,
UL resource share of TCP ACK packets starts increasing and TCP ACK packets
are transmitted faster than before. Faster transmission of TCP ACK packets helps
in reduction of TCP RTT of DL TCP sessions. This helps in increase of TCP DL
throughput.
For example, let's assume A, B, and C as follows;
• A: UL air resource share of TCP UL data sessions
• B: UL air resource share of TCP acknowledgements (ACK) sessions, such that
A + B = 100 %.
• C: the ratio of throughput for ACK packets over TCP packets (C ≈ TCP ACK
size/(TCP packet size × delayed ACK parameter))
DL throughput is limited by the minimum of DL peak throughput and UL peak
throughput × (A × C + B / C), that is, DL Tput = min{DL peak Tput, UL peak
Tput x (A x C + B / C)}. Hence, improving TCP DL throughput could be achieved
by increasing B. An example scenario with different values of A, B and C are
provided in the table below:
Confidential
Chapter 10 Services
Example Scenario (C = 0.0018, UL Peak: 7 Mbps, DL Peak: 100 Mbps)

A (%) 90 80 70
B (%) 10 20 30
DL Throughput (Mbps) 39.15 78.18 100
SYSTEM OPERATION
How to Activate
Precondition
• Run CHG-ULCC-CTRL and set ulccOnOff as ON.
• Run CHG-ULCC-CTRL and set ulccOnOff as OFF.
Key Parameters
parameters.
Parameter Descriptions of CHG-ULCC-CTRL/RTRV-ULCC-CTRL
ulccOnOff This parameter controls the activation/deactivation of the feature.
There are no specific configuration parameters of this feature.
Counters and KPIs

with this feature.

Confidential
Chapter 10 Services
REFERENCE
None

Confidential
Chapter 10 Services
LTE-SV1500, eMTC
INTRODUCTION
The enhanced Machine-Type Communications (eMTC) feature provides low
complexity and coverage enhancement MTC UEs for cellular IoT applications.
They are well equipped for low device cost, enhanced coverage, long battery life,
and low deployment cost. These characteristics are well suited for high traffic
applications like Surveillance CCTV, Drone, Emergency Disaster, and also for low
traffic applications like locations service, national environment monitoring,
logistics, and vehicle management.
BENEFIT
• Less device cost for 1RX antenna and reduced system bandwidth support.
• Large number of eMTC UEs supported as eMTC are suited for enhanced
coverage.
• Long battery life for eMTC UE.
• Easy deployment as eMTC UEs are deployed in-band in existing LTE carriers.
DEPENDENCY
• HW dependency: Requires a new channel card support for eNB to support
eMTC device.
• Others: Requires Release 13 eMTC capable devices and Core.
LIMITATION
• Samsung eNB does not support the following features for eMTC.
o TDD
o FDD for 1.4Mhz and 3Mhz BW.
• The following features are not applicable for eMTC UE.
o CE mode B
o CE capable LTE UE (any LTE category with CE mode A/B)
o Mobility in Idle Mode (inter-freq)
o Mobility in Connected Mode (inter-freq)
o UL/DL CoMP
o Carrier Aggregation, BCA
o MIMO
o eMBMS
o D2D
Confidential
Chapter 10 Services
o UL/DL FSS
o UL/DL 64QAM, DL 256QAM
o UL Sub-frame Bundling
o PRB Randomization
o Multi-cluster PUSCH
o CRS-IC, Smart CRS-IC
o ICIC, FeICIC
o PRB Resource Sharing per PLMN
o Smart Scheduler interworking features
o Inter-RAT interworking features
o GBR bearers - High Speed Flag
• The following features are exclusive for eMTC.
o DL CoMP
o PA Bias Control
o DL MIMO Tx Branch On/Off
o eMBMS
o Cell On/Off Multi-carrier Sites, Channel Card On/Off.
SYSTEM IMPACT
capabilities.
This feature co-operates with the following features:
• LTE-ME3410 Extended DRX for Idle Mode
• LTE-SW6311 Paging Optimization for Low Complexity and Coverage
Enhanced UE
• LTE-SW0332 UE Category Aware Call Control
• LTE-SW0315 Extended Access Barring (SIB14)
• LTE-SW0504 MME Selection and Load Balancing
• LTE-SW0514 Dedicated Core Network Support
Increasing eMTC resource allocation impacts on legacy LTE cell peak throughput
because eMTC is deployed within legacy LTE system.
Coverage
The coverage can be increased by heavy repetitions for CAT-M1 device up to
+15dB.

Confidential
Chapter 10 Services
Interfaces
Upgrade of 3GPP Rel-13 Interfaces such as RRC, S1AP and X2AP is required.
FEATURE DESCRIPTION
3GPP Release 13 introduces new UE category, CAT-M1 that scale down in
functionalities to bring more efficiencies for the Internet of things.
LTE IoT brings many improvements, including complexity reduction to enable
lower cost devices, more efficient low power modes to deliver long battery life,
and new advanced transmission techniques to deepen coverage.
CAT-M1, defined by the enhanced Machine-Type Communications (eMTC)
standards, provides data rates up to 1 Mbps utilizing 1.4MHz bandwidth (1.08
MHz in-band transmissions of 6 PRBs) and can be deployed to operate within a
regular LTE carrier. CAT-M1 can also support VoLTE and mobility. In enhanced
coverage, it can provide +15dB increased link budget compared to CAT-1, so the
eNB can provide LTE service to CAT-M1 devices deployed deep indoors.
CAT-M1 supports TDD, half-duplex FDD, and full-duplex FDD, reduced
maximum DL/UL Transport Block Size (TBS) of 1000 bits, and single RX
antenna reception.
Narrowbands
LTE system bandwidth is divided into a set of non-overlapping narrowbands
(NBs).
• A narrowband is comprised of continuous six PRBs and total number of NBs
for DL and UL are NDLRB/6 and NULRB/6.
• Remaining PRBs divided evenly at both ends of the system.
• The extra PRBs for odd system BWs are located at the center of the system
BW.

Confidential
Chapter 10 Services
New Physical DL Control Channel

The eNB supports a new physical control channel called as New Physical DL
Confidential
Chapter 10 Services
Control Channel (MPDCCH), which can be transmitted with repetitions and is

defined within 6 PRBs.
MPDCCH is transmitted by using 2, 4, or 6 PRBs and its structure is based on
EPDCCH. MPDCCH supports UE-specific search space (UESS) and Common
Search Space (CSS). MPDCCH can be transmitted with repetition, and maximum
number of repetition and transmission-starting subframes are signaled by SI for
CSS and by RRC message for UESS. PDSCH transmission starts in subframe n+2
and PUSCH transmission starts in subframe n+4 when last repetition of MPDCCH
ends in subframe n.
Types of eMTC Devices

BL UE
A BL (Bandwidth Reduced Low Complexity) UE can operate in any LTE system
bandwidth but with a limited 1.4 MHz channel bandwidth of six PRBs. The BL
UE access a cell only if the MIB of the cell indicates that SchedulingInfoSIB1-BR
is non-zero value. If not, the UE considers the cell as barred.
CE UE (or Non-BL UE)
To access the enhanced coverage of the cell, a UE requires enhanced coverage
functionality such as CE mode A/B. A UE capable of enhanced coverage
functionality, which is not a BL UE, uses legacy system information in normal
coverage, however, uses the specific system information for BL UE in enhanced
coverage.
There are two types of power class for CAT-M1 UE such as power class 3
(=23dBm) and power class 5 (=20dBm).
Operation Mode of BL/non-BL UE

• CE mode A: This mode uses no repetition or small number of repetition up to
32. Operation in CE mode A will have an equivalent coverage as that of CAT-
1 UE. CE mode A is mandatory for BL UE.
• CE mode B: This mode uses large number of repetition up to 2048. CE mode

Confidential
Chapter 10 Services
B has increased coverage up to 15dB compared with CAT-1 UE. This mode is
designed to be used in very poor propagation condition.
The eNB has provided enhancements in Cell Reselection, SI Update as depicted in

figure below.
The eMTC uses legacy LTE PSS and SSS for time/frequency synchronization and
cell identification.

Confidential
Chapter 10 Services
To allow access to CAT-M1 devices, eNB indicates this through the

SchedulingInfoSIB1-BR in Master Information Block (MIB) message and specific
System Information (SI) messages for CAT-M1 devices as depicted in figure
below.
The eMTC functionality can be activated during the cell creation procedure or by
using CHG-CELL-IDLE command in LSM. The cell should be locked before
activating or deactivating eMTC using the command.
When the EMTC_SWITCH is set to "Off", SchedulingInfoSIB1-BR IE in MIB is
set to zero, and all Bandwidth Redeced (BR) version of SI messages are not
transmitted since all resources related with eMTC are withdrawn.
LTE PBCH enhanced to support repetitions at symbol and subframe levels. 5 of

the 10 spare bits from legacy MIB uses to indicate support of BL/non-BL UEs in
the cell and for SIB1-BR scheduling information.
CAT-M1 UE can access a cell only if the MIB indicates its support through the
SchedulingInfoSIB1-BR with non-zero value.
The eNB should support BR version of SIB for eMTC called SIB1-BR, which
provides 1000 bits maximum transmission for SIB broadcast for CAT-M1 devices.
MIB indicates scheduling information for SIB1-BR and SIB1-BR includes
scheduling information for other SI messages. The scheduling information
includes NB indexes, TBS, repetition pattern, and so on. Separated SIB1-BR and
specific SI messages for eMTC are scheduled independently with contents that
may differ. SIB1-BR is transmitted periodically every 80 ms like a SIB1. SIB1-BR
can be repeated a number of times within the period. To decode BR version of SI
message like SIB2 and SIB3, CAT-M1 UE has to interpret the scheduling
information in SIB1-BR such as narrowband index to be monitored, the period of
SIBs, TBS and repetition pattern of SIBs. The transmission and the period of BR
version of SI messages can be configured independently using CHG-BRSIB-INF
command in LSM. For example, the BR version of SIB2 will not be transmitted
when BR_SIB2_PERIOD is set to "not_used".
The eNB supports random access procedure for CAT-M1 UEs. For the UE,
separated PRACH resources and MPDCCH for CSS are scheduled.
The CAT-M1 UE can obtain PRACH configuration after decoding BR version of

Confidential
Chapter 10 Services
SIB2. In PRACH configuration, set of PRACH resources is associated with each

CE level.
After the Cat.M1 UE obtains SIB2-BR including RSRP threshold per CE level and
a set of PRACH Parameters per CE level, it measures RSRP and determines which
CE level is used. Cat.M1 transmits PRACH preamble with repetition
corresponding to the CE level, which it chose. The eNB can identify CE level of
Cat.M1 through PRACH preamble received from Cat.M1.
The UE also indicates its eMTC capability in RRC Connection Setup Complete
and UE Capability Information. The UE indicates whether the UE supports
operation in CE mode B at RRC Connection Setup Complete.
The ue-RadioPagingInfo IE contains UE capability information such as UE
category and Coverage Enhancement mode (CE mode).

Confidential
Chapter 10 Services
Mobility in Connected Mode

Inter-cell mobility in connected mode is provided, if the handover event A3 is
occurred.
When Event A3 for mobility to

Cell #1 Cell #2 neighbors is occurred, Perform
inter-cell HO.
CAT-M1 UE
Figure below depicts the call flow for mobility in connected mode.
CAT-M1 UE Cell A Cell B

Source cell Target cell
VoLTE/Data Check UE capability

for handover
Measurement configuration for neighbor measurement

: Serving freq. with event A2 for measurement activation
Perform serving cell

measurement
Measurement Report
: Event A2 for measurement activation
Measurement configuration for handover

: Target freq.(s) with HO event A3,
measurement gap if required by UE capability
Perform neighbor measurement

(intra-/inter-freq.)
Measurement Report
: Handover event to Cell B
HO triggering
from Cell A to Cell B
Perform HO procedure
(intra-eNB/X2/S1)
The eNB checks whether to support intra-frequency measurement and handover

via Cat-M1 UE capability in the following cases:
• call setup

Confidential
Chapter 10 Services
• hand-in
• RRC connection re-establishment
If a CAT-M1 UE supports the intra-frequency measurement and handover, the
eNB performs the measurement configuration for neighbor measurement including
the serving frequency with Event A2.
When the eNB receives the Event A2 MR from CAT-M1, it performs the
measurement configuration for handover including target frequencies with HO
Event A3. If the UE requires a measurement gap for measurement of target
frequencies based on the UE capability, the measurement gap is also included.
If the eNB receives an Event A3 MR from CAT-M1 UE and the handover to the
target cell (Cell B in figure above) can be possible, it triggers and performs
handover.
Frequency Hopping
Individual frequency hopping per downlink and uplink can be used when system
parameter dl_Unicast_Hopping_Usage for downlink or pusch_Hopping_Enable
for uplink is set to ON. Frequency hopping is applied to SIB1-BR (mandatory
regardless of system parameter configuration) and unicast traffic (determined by
UE capability and eNB). The frequency hopping offset and the interval per
downlink and uplink are broadcasted in SIB1-BR and SIB2-BR respectively. The
frequency hopping offset indicates the narrowband offset between one narrowband
and the next narrowband. MPDCCH or PDSCH hopping narrowband is
determined considering the PCI and the LTE bandwidth. PUSCH hopping
narrowband is determined to the empty narrowband where it is farthest from the
PUSCH main narrowband.
The frequency hopping interval indicates the number of consecutive absolute
subframes over which MPDCCH, PDSCH, or PUSCH stays at the same
narrowband before hopping to another narrowband, and is configured by
dl_Fdd_Hopping_Interval_ModeA for downlink and
ul_FDD_Hopping_Interval_ModeA for uplink.
Repetitions Change
An intra-cell CE level0/1 change is performed in terms of link adaptation, which
changes the number of repetitions for MPDCCH, PDSCH, PUCCH, and PUSCH
according to signal strength environment. Repetition changes for MPDCCH and
PUCCH by link adaptation causes by the RRC Connection Reconfiguration
procedure with eMTC UE.
VoLTE Support
This section describes the functionalities supported for VoLTE service.
Resource Allocation Order
To support VoLTE service for eMTC UEs, the eNB schedules VoLTE packets
with higher priority than packets for other services.
Figure below depicts the resource allocation order for GBR and non-GBR bearers.
Confidential
Chapter 10 Services
Resource Allocation
For GBR Bearers of
LTE UE
Resource Allocation
For GBR Bearers of
eMTC UE
Resource Allocation
For Non-GBR Bearers of
eMTC UE
Resource Allocation
For Non-GBR Bearers of
LTE UE
GBR (like VoLTE) bearers of LTE UE have strictly highest priority. GBR bearers
of eMTC UEs have next highest priority. Therefore, the eMTC VoLTE UE will
have higher priority than UEs with LTE/eMTC non-GBR bearers.
Voice Packet Bundling
A single transmission with a bundle of two or more voice packets can reduce L2-
layer control overhead. The eNB bundles two voice packets for single transmission
by default. At each TTI, the eNB checks Buffer Occupancy (BO) for each VoLTE
bearer. If the size of BO is less than the size corresponding to two voice packets,
the eNB excludes the VoLTE bearer from scheduling candidate in that TTI. The
operator can configure a size of single voice packet via
VOLTE_PKT_SIZE_ROHC_ENABLED. To support flexible bundling operation,
the number of voice packets in a bundle can be increased according to the channel
and the cell congestion status. The more heavily congested, the more voice packets
are bundled.
Restriction of the Maximum Number of Repetitions
An excessive number of repetitions cause VoLTE quality and coverage
degradation due to unsuccessful delivery within VoLTE-specific delay budget or
packet drop from discard timer. The eNB restricts the maximum number of
repetitions for each physical channel. The operator can configure the maximum
repetitions numbers by MPDCCH_MAX_REP_VOLTE (using CHG-BRDLREP-
CONF), PDSCH_MAX_REP_VOLTE (using CHG-BRDLREP-CONF),
PUCCH_MAX_NUM_REPETITION_VOLTE (using CHG-BRMAC-VOIP), and
PUSCH_MAX_NUM_REPETITON_VOLTE (using CHG-BRMAC-VOIP).
Uplink Dummy Grant Operation

As LTE VoLTE scheduler, the eMTC VoLTE scheduler supports an UL dummy
grant operation in silence period. This operation can reduce the UL latency of
VoLTE packet during transition from silence period to talk-spurt period. The
operator can configure transmission interval of UL dummy grant in silence period
by SILENCE_UL_GRANT_PERIOD (using CHG-BRMAC-VOIP).

Confidential
Chapter 10 Services
SYSTEM OPERATION
How to Activate
Preconditions
• The eMTC can be activated during the cell creation procedure.
• The cell should be locked before activating or deactivating eMTC.
• When creating a new FDD cell, set "EMTC_SWITCH" to "On" (restrictions
may apply to specific bandIndicator, bandwidth, and so on.)
• When the cell is already created, run RTRV-CELL-CONF to confirm
ADMINISTRATIVE_STATE for the cell is "locked", and run CHG-CELL-
IDLE and set EMTC_SWITCH to "ON". (Restrictions may apply to specific
bandIndicator, bandwidth, and so on.)
• Run RTRV-CELL-CONF to confirm ADMINISTRATIVE_STATE for the cell
is "locked".
• Run CHG-CELL-IDLE and set EMTC_SWITCH to "OFF".
Key Parameters
parameters.
Parameter Descriptions of RTRV-CELL-IDLE/CHG-CELL-IDLE
This parameter is used to activate or deactivate eMTC feature.
EMTC_SWITCH • Off: eMTC feature is Off.
• On: eMTC feature is On.
Parameter Descriptions of RTRV-BRSIB-INF/CHG-BRSIB-INF
BR_SIB2_PERIOD This parameter is the broadcast interval for SIB2 on BR-BCCH for
eMTC/CAT-M1.
• not_used: Does not broadcast SIB2 on BR-BCCH.

Confidential
Chapter 10 Services
eMTC/CAT-M1.
eMTC/CAT-M1.
eMTC/CAT-M1.
eMTC/CAT-M1.
BR_SI_WINDOW This parameter is the BR-BCCH System Information (SI) window size of a
cell in the eNB. Each SI message is associated with one SI-window, and
does not overlap with the SI-windows of other SI messages. That is, one SI
is sent to one SI window. The length of SI-window is the same for all SI
messages. The corresponding SI message in the SI-window is sent
repeatedly.
BR_SI_REPETITION_PATTER This parameter configures Repetition Pattern for SIBs on BR-BCCH for
N eMTC/CAT-M1.
• 0 : everyRF
• 1 : every2ndRF
• 2 : every4thRF
• 3 : every8thRF
BR_SI_VALIDITY_TIME_R13 This parameter indicates system information validity timer. If set to TRUE,
the timer is set to 3h, otherwise the timer is set to 24h.
BR_WAR_SEGMENT_SIZE This is the Warning Message Segment size of system information block 12
of the cell for BL/CE UEs.
Parameter Descriptions of RTRV-CELL-ACS/CHG- CELL-ACS

BR_CELL_BARRED This parameter indicates whether the cell for eMTC is barred or not. Both
when the cell status becomes Shutdown and when the operator sets this
parameter to barred, the CELL_BARRED value of SIB1-BR becomes
barred and then is broadcasted.
BR_BARRING_CTR_USAGE This parameter represents the how to set the ac-barringInfo parameters of
SIB2 on BR-BCCH.
overload.
BR_BARRING_PLMN_CTR_US This parameter represents how to set the AC-BarringPerPLMN-List-r12
AGE parameters of SIB2 on BR-BCCH
overload.

Confidential
Chapter 10 Services
BR_EAB_CTR_USAGE This parameter represents the how to set the EAB parameters of SIB14 on
BR-BCCH.
• eabManualCtrl: Uses the eab control function manually.
• eabAutoCtrl: Uses the eab control function depending on CPU load state,
MME Overload and Call Count in Cell.
Parameter Descriptions of RTRV-BRBARCOM-PARA/CHG-BRBARCOM-PARA

See LTE-SW2102 for the parameter description of LTE parameters for RTRV-
BARCOM-PARA/CHG-BARCOM-PARA.
Parameter Descriptions of RTRV-BRBARPLMN-PARA/CHG-BRBARPLMN-PARA
See LTE-SW2102 for the parameter description of LTE parameters for RTRV-
BARPLMN-PARA/CHG-BARPLMN-PARA.
Parameter Descriptions of RTRV-BRPRACH-IDLE/CHG-BRPRACH-IDLE

RSRP_THRESHOLD1 This parameter specifies RSRP threshold level to differentiate CE level 0
and CE level 1.
(RSRP-Threshold1 = measured RSRP of UE + 140)
Parameter Descriptions of RTRV-BRPRACH-CONF/CHG-BRPRACH-CONF

NUM_REPETITION_PER_PRE This parameter specifies the number of repetition per PRACH preamble
ABLE_ATTEMPT_CE_LEVEL_0 attempt for CE level 0.
NUM_REPETITION_PER_PRE This parameter specifies the number of repetition per PRACH preamble
ABLE_ATTEMPT_CE_LEVEL_1 attempt for CE level 1.
Parameter Descriptions of RTRV-BRRACH-CONF/CHG-BRRACH-CONF

POWER_RAMPING_STEP This parameter specifies the power ramping steps for preamble transmit
power when preamble transmission counter increases.
PREAMBLE_INIT_RCV_TARG This parameter specifies the initial target receiving power of preambles.
ET_POWER Value dBm-120 corresponds to-120dBm and so on.
MAX_NUM_PREAMBLE_ATTE This parameter is the maximum number of times to transmit a preamble in
MPT_CE_LEVEL_0 CE level 0.
MAX_NUM_PREAMBLE_ATTE This parameter is the maximum number of times to transmit a preamble in
MPT_CE_LEVEL_1 CE level 1.
PREAMBLE_TRANS_MAX This parameter is the maximum number of times to transmit a preamble.

Confidential
Chapter 10 Services
BACKOFF_INDICATOR_SETU This parameter setup or release the backoff indicator.
P • Release: release.
• Setup: setup.
BACKOFF_INDICATOR This parameter specifies the backoff value.
MAX_HARQMSG3_TX This parameter is the maximum number of transmission of HARQ Msg3.
Parameter Descriptions of RTRV-BRPUSCH-CONF/CHG-BRPUSCH-CONF

PUSCH_MAX_NUM_REPETITI This parameter is used to control the maximum repetition number of CE
ON_CE_MODE_A ModeA UE's PUSCH transmission.{0: r1, 1: r2, 2: r4, 3: r8}
PADDING_THRESHOLD This threshold is used for PUSCH excessive padding prevention. If the
padding PDU larger than this threshold is received, then it is considered as
received zero-BSR.
Parameter Descriptions of RTRV-BRPUCCH-CONF/CHG-BRPUCCH-CONF

MSG4_ACK_NUM_REPETITIO This parameter is used to control the repetition number of CE level0 UE's
N_CE_LEVEL_0 ACK/NACK transmission for Msg4.{0: r1, 1: r2, 2: r4, 3:r8}
MSG4_ACK_NUM_REPETITIO This parameter is used to control the repetition number of CE level1 UE's
N_CE_LEVEL_1 ACK/NACK transmission for Msg4.{0: r1, 1: r2, 2: r4, 3:r8}
FORMAT1_ACK_NUM_REPETI This parameter is used to control the repetition number of CE level0 UE's
TION_CE_LEVEL_0 PUCCH format1 transmission.{0: r1, 1: r2, 2: r4, 3: r8}.
Parameter Descriptions of RTRV-BRULHOPPING-IDLE/CHG-BRULHOPPING-

IDLE
UL_FDD_HOPPING_INTERVAL This parameter is used to control the UL hopping interval of eMTC/cat.M1
UE.{0: n2, 1: n4, 2: n8}
Parameter Descriptions of RTRV-BR-RSCUSAGECTRL/CHG-BR-

RSCUSAGECTRL

Confidential
Chapter 10 Services
DL_PRB_USAGE_TH Threshold for resource usage of eMTC PDSCH except for broadcast
UL_PRB_USAGE_TH Threshold for UL resource usage for eMTC/cat.M1 UEs
Parameter Descriptions of RTRV-BRTIME-ALIGN/CHG-BRTIME-ALIGN

TIME_ALIGNMENT_TIMER_C This parameter is used to control how long the eMTC/cat.M1 UE with CE
E_LEVEL0 level 0 is considered uplink time aligned. If the eMTC/cat.M1 UE does not
received Time Alignment(TA) command from eNB during
timeAlignmentTimerCommon, eMTC/cat.M1 UE regards it link failure and
performs random access procedure.
Be cautious if This parameter is set to finite value, eNB needs to transmit
TA command to eMTC/cat.M1 UE. UEs periodically although uplink
timings are correct, which causes unnecessary control overhead.
TIME_ALIGNMENT_TIMER_C This parameter is used to control how long the eMTC/cat.M1 UE with CE
E_LEVEL1 level 1 is considered uplink time aligned. If the eMTC/cat.M1 UE does not
received Time Alignment (TA) command from eNB during
timeAlignmentTimerCommon, eMTC/cat.M1 UE regards it link failure and
performs random access procedure.
Be cautious if This parameter is set to finite value, eNB needs to transmit
TA command to eMTC/cat.M1 UE UEs periodically although uplink timings
are correct, which causes unnecessary control overhead.
Parameter Descriptions of RTRV-BRTRCH-INFO/CHG-BRTRCH-INFO

PERIODIC_BSRTIMER This parameter is the timer for eMTC/cat.M1 UE's BSR(buffer status
report) reporting in TS 36.321. Value in number of subframes. Sf5
corresponds to 5 subframes.
The Periodic BSR Timer type in accordance with the PDB per QCI. For
multiple bearers, the PDB with the smallest value is used.
• sf5: 5 subframes.
• ......
• infinity: no periodic BSR is used.
RETX_BSRTIMER This parameter is the Retx BSR Timer type for eMTC/cat.M1 UE in
accordance with the PDB per QCI. For multiple bearers, the PDB with the
smallest value is used.
MAC_HARQ_TX The maximum HARQ Tx for eMTC/cat.M1 UE per cell. The UE executes
PUSCH retransmission in accordance with this parameter value. In the
standard up to 28 transmissions is allowed including the first transmission.
PERIODIC_PHRTIMER This parameter is the timer for eMTC/cat.M1 UE's power headroom(PHR)
reporting in TS 36.321. Value in number of subframes. Sf10 corresponds
to 10 subframes.
• ...
• infinity: no periodic PHR reporting.

Confidential
Chapter 10 Services
DLPATHLOSS_CHANGE The DLPathloss Change for eMTC/cat.M1 UE's PHR(power headroom)
reporting. Value dB1 corresponds to 1dB and so on. If prohibitPHR-timer
expires and pathloss has changed more than dl-PathlossChange dB, PHR
shall be triggered.
SR_PRPHIBIT_TIMER_CE_M Provide information about SR Prohibit Timer for eMTC/cat.M1 UE CE
ODE_A mode A UE within the cell
Parameter Descriptions of RTRV-BRULBLER-CTRL/CHG-BRULBLER-CTRL

CE_MODEA_TARGET_ULBLE The eMTC/cat.M1 CE modeA PUSCH target BLER in unit of 0.1%.
R
Parameter Descriptions of RTRV-BRMAC-VOIP/CHG-BRMAC-VOIP

VOLTE_PKT_SIZE_ROHC_EN Cell-specific voice packet size (Unit: Byte)
ABLED
VOLTE_MIN_TBS Minimum guaranteed TBS for VoLTE UE (Unit: Byte)
PUSCH_MAX_NUM_REPETIT Maximum allowable PUSCH repetition number for VoLTE UE
ON_VOLTE[3]
PUCCH_MAX_NUM_REPETITI Maximum allowable PUCCH repetition number for VoLTE UE
ON_VOLTE
SILENCE_UL_GRANT_PERIO Uplink dummy grant period in uplink silence period
D
HARQ_DELAY_BUDGET HARQ delay budget by which Maximum number of DL/UL HARQ
transmission is determined
Parameter Descriptions of CHG-BRCQI-REP/RTRV-BRCQI-REP

CQI_REPORT_APERIODIC_SE This parameter is set to enable or disable the use of aperiodic report mode
TUP for eMTC/cat.M1 UE.
• Release: aperiodic report mode is disable.
• Setup: aperiodic report mode is enable.
Parameter Descriptions of RTRV-BR-PWRCTRL/CHG-BR-PWRCTRL

UL_SINR_MIN_REQ_CE The minimum target SINR in dB for eMTC/cat.M1 UEs. This value should
be smaller than maximum target SINR. Otherwise, it causes abnormal
power control operation.
PUCCH_TPC_SETUP Parameter indicates whether PUCCH grouped TPC is configured for
eMTC/cat.M1 UE.
P0_NOMINAL_PUSCH This parameter is the PUSCH Initial Power value for eMTC/cat.M1 UE.
p0NominalPUSCH value is used in PUSCH power control and provided
from higher layers. This parameter is applicable for non-persistent
scheduling, only. This change will be applied to UE's PUSCH transmission
power. In the standard, the configurable range of This parameter is the (-

Confidential
Chapter 10 Services
126~24) in dBm unit. Be cautious to set this parameter to a higher value. A
higher value can increase the SINR of uplink reception from the UE.
However, it can also limit the number of allocation PRB size due to the
power shortage of UE and increase the intercell interference.
[Related Specification] TS 36.213, 5.1.1.1
ALPHA Assign alpha (0, 0.4, 0.5~0.9, 1).
Pathloss compensation factor for PUSCH/SRS transmit power of
eMTC/cat.M1 UE. When alpha is 1, the pathloss is fully compensated by
transmit power and the received power level at eNB remains constant.
When alpha is smaller than 1, the pathloss is partially compensated by
transmit power and the received power level at eNB decreases as
pathloss increases. Al0 corresponds to 0, al04 to 0.4 and so on.
P0_NOMINAL_PUCCH This parameter is the PUCCH Initial Power value for eMTC/cat.M1 UE.
p0Nominal PUCCH value is used in PUCCH power control and provided
from higher layers. This change will be applied to UE. In the standard, the
configurable range of This parameter is the (-128~-96) in dBm unit. eNB
automatically controls the UE's PUCCH transmission power to satisfy the
desired SINR by sending TPC command to UE. Therefore this parameter
change only affects the initial PUCCH transmission power.
[Related Specification] TS 36.213, 5.1.2.1
DELTA_FPUCCHFORMAT1 This parameter determines the PUCCH format 1 transmit power offset
comparing to that of PUCCH format1a for eMTC/cat.M1 UE. This
parameter is the configurable per cell and the offset value is defined as
enumerated{deltaF-2, deltaF0, deltaF2}. deltaF-2 corresponds to -2dB,
deltaF0 to 0dB and deltaF2 to 2dB, respectively.
DELTA_FPUCCHFORMAT2 This parameter determines the PUCCH format 2 transmit power offset
enumerated{deltaF-2, deltaF0, deltaF1, deltaF2}. deltaF-2 corresponds to -
2dB, deltaF0 to 0dB, deltaF1 to 1dB and deltaF2 to 2dB, respectively.
DELTA_FPUCCHFORMAT2_A This parameter determines the PUCCH format 2a transmit power offset
enumerated{deltaF-2, deltaF0, deltaF2}. deltaF-2 corresponds to -2dB,
deltaF0 to 0dB, and deltaF2 to 2dB, respectively.
DELTA_PREAMBLE_MSG3 Msg3 transmission power offset comparing to acknowledged preamble
transmission power for eMTC/cat.M1 UE. This parameter is the signaled
using a value between -1~6 and it actual value is IE value*2 in dB.
IOT_REDUCTION_SINR_MAR PUSCH SINR margin for IoT reduction operation for eMTC/cat.M1 UE in
GIN UL power control. Higher value allows higher PUSCH SINR. (unit : 0.1dB)
P0_UE_PUSCH This parameter is the non-persistent scheduling P0 value used in PUSCH
power control, which is determined per eMTC/cat.M1 UE. This value is
applicable for non-persistent scheduling, only. This change will be applied
to eMTC/cat.M1 UE. UE will apply this power offset for PUSCH
transmission. In the standard, the configurable range of This parameter is
the (-8~7) in dB unit. A higher value can increase the SINR of uplink
reception from the UE. However, it can also limit the number of allocation
PRB size due to the power shortage of UE and increase the intercell
interference.
[Related Specifications] 3GPP TS 36.213 [23, 5.1.1.1].
ACCUMULATION_ENABLED This parameter indicates whether to use the accumulation mode and
absolute mode in transmit power control(TPC) for eMTC/cat.M1 UE.
• 0: Absolute mode is used. UE will apply the instant TPC value.
• 1: Accumulation mode is used. UE will apply the accumulated TPC
value.

Confidential
Chapter 10 Services
[Related Specifications] 3GPP TS 36.213[23,5.1.1.1]
P0_UE_PUCCH This parameter is the P0 value used in PUCCH power control, which is
determined per eMTC/cat.M1 UE. See TS 36.213 [23, 5.1.2.1]. This
change will be applied to UE. UE will apply this power offset for PUCCH
transmission. In the standard, the configurable range of This parameter is
the (-8~7) in dB unit. eNB automatically controls the UE's PUCCH
transmission power to satisfy the desired SINR by sending TPC command
to UE. Therefore this parameter configuration only affects the initial
PUCCH transmission power.
FILTER_COEFFICIENT This parameter specifies the filtering coefficient for eMTC/cat.M1 UE. The
filtering coefficient is used to measure RSRP in order to calculate a path
loss. Specifies the filtering coefficient for RSRP measurements used to
calculate path loss, as specified in TS 36.213 [23, 5.1.1.1]. The same
filtering mechanism applies as for quantityConfig described in 5.5.3.2.
Parameter Descriptions of RTRV-UE-A3CNF/CHG-UE-A3CNF

UE_TYPE This parameter is the ueType
• eMTC : eMTC UE
• Spare1 : spare
PURPOSE This parameter is the purpose of using UE Specific A3 event.
• Spare1 : spare
QCI_GROUP_INDEX QCI Group Index
FA_INDEX The FA_INDEX is a parameter corresponding to the FA_INDEX of EUTRA-
FA.
event A3 triggering. This change will be applied to the UE from next RRC
setting will not be updated to the current active UEs. The higher the
parameter is, the less HO is performed and it can impact HO success rate,
The lower the parameter is, the more frequent HO is performed and it can
cause ping pong. This value needs to be optimized up to site environment.
setting will not beupdated to the current active UEs.

Confidential
Chapter 10 Services
satisfies leaving condition, it is not reported.
signaling overhead.
active UEs.
[Related Specifications] 3GPP TS 36.331"

Confidential
Chapter 10 Services
Parameter Description of RTRV-BRBCCH-CONF/CHG-BRBCCH-CONF

MODIFICATION_PERIOD_CO This parameter indicates modificationPeriodCoeff to determine the actual
EFF BCCH modification period which is expressed as
modificationPeriodCoeff*defaultPagingCycle in number of radio frames.
MODIFICATION_PERIOD_CO This parameter indicates whether to use modificationPeriodCoeff-v1310. If
EFFV1310_USE this parameter is set to CI_use, modificationPeriodCoeff-v1310 = n64 is
used.
Parameter Description of RTRV-BRDLBLER-CTRL/CHG-BRDLBLER-CTRL

MAX_HARQ_DL This parameter configures maximum number of DL HARQ transmissions.
Parameter Description of RTRV-BRDLBH-IDLE/CHG-BRDLBH-IDLE

DL_UNICAST_HOPPING_USA This parameter configures frequency hopping activation/deactivation for
GE MPDCCH/PDSCH of Unicast. (mpdcch-pdsch-HoppingConfig-r13 in
EPDCCH-Config)
Parameter Description of RTRV-BRDLMAC-PARA/CHG-BRDLMAC-PARA

DL_INITIAL_SINR_OFFSET_L This parameter configures SINR offset (dB) which is added to RSRP-
EVEL0 Threshold1 to determine DL initial SINR of CE level 0.
DL_INITIAL_SINR_OFFSET_L This parameter configures SINR offset (dB) which is added to RSRP-
EVEL1 Threshold2 to determine DL initial SINR of CE level 1.
INVALID_SUBFRAME_PAGIN If this parameter is set to True, subframes for LTE paging are excluded
G from BL/CE DL subframes.
INVALID_SUBFRAME_SIB1 If this parameter is set to True, subframes for LTE SIB1 are excluded from
BL/CE DL subframes.
INVALID_SUBFRAME_SI_ME If this parameter is set to True, subframes for LTE SI message are
SSAGE excluded from BL/CE DL subframes.
INVALID_SUBFRAME_RAR If this parameter is set to True, subframes for legacy RAR are excluded
from BL/CE DL subframes.
INVALID_SUBFRAME_SELEC This parameter configures the subframes that are excluded from BL/CE
TED DL subframe. If subframe n is selected, subframes satisfying absolute
subframe number mod 10 = n are excluded from BL/CE DL subframe.

Confidential
Chapter 10 Services
Parameter Description of RTRV-BRDLREP-CONF/CHG-BRDLREP-CONF

SIB1_BR_REPETITION The number of SIB1-BR repetitions per 80ms.
PAGING_REPETITION_OPTIO This parameter configures the rage of repetition for paging MPDCCH.
N • ci_Option0: start repetition = 1, max repetition = 1
RAR_REPETITION_OPTION_ This parameter configures repetition level of RAR MPDCCH for CE level 0
CE_LEVEL0 UE
RAR_REPETITION_OPTION_ This parameter configures repetition level of RAR MPDCCH for CE level 1
CE_LEVEL1 UE
PDSCH_MAX_REP_MODE_A_ This parameter configures whether to select maximum number of PDSCH
USAGE repetitions for CEModeA. When the value is CI_no_use, maximum
repetition number is set to 8. When the value is CI_use, maximum
repetition number is determined by the value of
PDSCH_MAX_REP_MODE_A.
PDSCH_MAX_REP_MODE_A This parameter configures the maximum number of PDSCH repetitions for
CEModeA when the value of PDSCH_MAX_REP_MODE_A_USAGE is
set to CI_use.
Parameter Description of RTRV-BRDLNB-IDLE/CHG-BRDLNB-IDLE

DL_UNICAST_NB_NUM This parameter configures the number of narrowband for DL unicast.
DL_DEDICATED_VOLTE_NB_ This parameter configures whether QCI1 bearer is allocated to dedicated
ENABLE VoLTE NB. This value is valid only if DL_UNICAST_NB_NUM is "2". If
DL_UNICAST_NB_NUM is "2" and this value is "ci_use", QCI1 bearer is
allocated to 1st DL unicast narrowband. If DL_UNICAST_NB_NUM is "2"
and this value is "ci_not_use", QCI1 bearer is allocated to 1st DL unicast
narrowband or 2nd DL unicast narrowband.
Parameter Description of RTRV-BRPCCH-CONF/CHG-BRPCCH-CONF

DB_INDEX INDEX
NB This parameter indicates the NB value for BR/CE UEs.
NBV1310_USE This parameter indicates whether to use nB-v1310.
NBV1310 This parameter indicates nB-v1310 value.
Counters and KPIs


Confidential
Chapter 10 Services

eMTC PDCP Packet per eMTC_PLMN0EnbQciULByte The cumulated eMTC DRB packet bytes of
PLMN PLMN (0) that eNB transmitted to S-GW
eMTC_PLMN0EnbQciDLByte The cumulated eMTC DRB packet bytes of
PLMN (0) that eNB received from S-GW
eMTC_PLMN1EnbQciULByte The cumulated eMTC DRB packet bytes of
PLMN (1) that eNB transmitted to S-GW

eMTC Air Mac Packet CEModeA_AirMacULByte The cumulated size of MAC PDUs which
were successfully received through PUSCH
for CEModeA UEs.
CEModeA_AirMacULByteCnt The collection count of
CEModeA_AirMacULByte
CEModeA_AirMacULTti The cumulated number of TTIs that have
MAC PDUs which were successfully
received through PUSCH for CEModeA UEs.
CEModeA_AirMacULThruAvg The calculated number that indicates the
average per second size of MAC PDUs
PUSCH for CEModeA UEs.
CEModeA_AirMacULEfctivThruAv The calculated average MAC PDU size per
g TTI that have MAC PDUs which were
successfully received through PUSCH for
CEModeA UEs.
CEModeA_AirMacDLByte The cumulated size of MAC PDUs which
were successfully transmitted through
PDSCH for CEModeA UEs.
CEModeA_AirMacDLByteCnt The collection count of
CEModeA_AirMacDLByte
CEModeA_AirMacDLTti The cumulated number of TTIs that have
MAC PDUs which were successfully
transmitted through PDSCH for CEModeA

Confidential
Chapter 10 Services

UEs.
CEModeA_AirMacDLThruAvg The calculated number that indicates the
average per second size of MAC PDUs
which were successfully transmitted through
PDSCH for CEModeA UEs.
CEModeA_AirMacDLEfctivThruAv The calculated average MAC PDU size per
g TTI that have MAC PDUs which were
successfully transmitted through PDSCH for
CEModeA UEs.

eMTC Total PRB Usage CEModeA_TotPrbULAvg The average number of UL PRB usage
allocated for CEModeA UEs.
CEModeA_TotPrbULUsed The cumulated number of UL PRBs
allocated for CEModeA UEs
eMTC_TotPrbULAvailable The cumulated number of UL PRBs available
for eMTC UEs.
CEModeA_TotPrbDLAvg The average number of DL PRB usage
allocated for CEModeA UEs.
Broadcast_TotPrbDLAvg The average number of DL PRB usage
allocated for PBCH, SIB and Paging
CEModeA_TotPrbDLUsed The cumulated number of DL PRBs
allocated for CEModeA UEs
Broadcast_TotPrbDLUsed The cumulated number of DL PRBs
allocated for PBCH, SIB and paging
eMTC_TotPrbDLAvailable The cumulated number of DL PRBs available
for eMTC UEs.

eMTC Power eMTC_InterferencePowerAvg The average value of per-PRB interference
Measurement Info over thermal noise over eMTC Narrowband
region.
eMTC_InterferencePowerTot The cumulated number of
InterferencePowerAvg
eMTC_InterferencePowerCnt The collection count of
InterferencePowerAvg

eMTC Random Access CElevel0_RachPreambleCnt The cumulated number of PRACH
Preambles preambles received from CElevel0 UE
CElevel1_RachPreambleCnt The cumulated number of PRACH
preambles received from CElevel1 UE

eMTC Downlink HARQ CEModeA_DLResidualBlerRetran CEModeA UE's PDSCH BLER for the initial
Transmission BLER s0 HARQ transmission during the collection
interval. It is the failure rate for the initial

Confidential
Chapter 10 Services

transmission and is a ratio of the number of
times the first re-transmission was carried
out to the number of times the initial
CEModeA_DLResidualBlerRetran CEModeA UE's PDSCH BLER for the first
s1 HARQ retransmission
CEModeA_DLResidualBlerRetran CEModeA UE's PDSCH BLER for the
s2 second HARQ retransmission
CEModeA_DLResidualBlerRetran CEModeA UE's PDSCH BLER for the third
CEModeA_DLResidualBlerRetran CEModeA UE's PDSCH BLER for the fourth
CEModeA_DLResidualBlerRetran CEModeA UE's PDSCH BLER for the fifth
CEModeA_DLResidualBlerRetran CEModeA UE's PDSCH BLER for the sixth
CEModeA_DLResidualBlerRetran The minimum PDSCH HARQ transmission
sMin number among which have positive value
between
CEModeA_DLResidualBlerRetrans0 and
CEModeA_DLResidualBlerRetrans6. HARQ
transmission number denotes "X" in that "Xth
HARQ retransmission".
CEModeA_DLResidualBlerRetran The maximum PDSCH HARQ transmission
sMax number among which have positive value
between
CEModeA_DLResidualBlerRetrans0 and
CEModeA_DLResidualBlerRetrans6. HARQ
transmission number denotes "X" in that "Xth
HARQ retransmission".
CEModeA_DLResidualBlerRetran CEModeA UE's average failure rate of
sAvg PDSCH HARQ retransmissions. The value is
calculated in terms of percentage, where the
denominator is set to be the counts of all
retransmissions adding the counts of initial
HARQ transmissions, and the numerator is
set to be the counts of all retransmissions
adding the counts of transmission failures
after the maximal HARQ retransmissions.
CEModeA_DLResidualBlerRetran CEModeA UE's failure rate of PDSCH initial
sNak HARQ transmissions after the maximal
HARQ retransmission occurs. It is the ratio of
the counts of transmission failures after the
maximal HARQ retransmissions to the
counts of initial transmissions.
CEModeA_DLTransmissionRetra The cumulated number of CEModeA UE's
ns0 initial PDSCH HARQ transmissions
ns1 first PDSCH HARQ retransmissions
ns2 second PDSCH HARQ retransmissions
ns3 third PDSCH HARQ retransmissions

Confidential
Chapter 10 Services

ns4 fourth PDSCH HARQ retransmissions
ns5 fifth PDSCH HARQ retransmissions
ns6 sixth PDSCH HARQ retransmissions
CEModeA_DLTransmissionNacke The cumulated number of CEModeA UE's
dRetrans PDSCH HARQ retransmission failures after
the maximal HARQ retransmission occurs.

eMTC Uplink HARQ CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the initial
Transmission BLER s0 HARQ transmission during the collection
interval. It is the failure rate for the initial
transmission and is a ratio of the number of
times the first re-transmission was carried
out to the number of times the initial
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the first
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the
s2 second HARQ retransmission
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the third
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the fourth
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the fifth
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the sixth
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the
s7 seventh HARQ retransmission
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the eighth
CEModeA_ULResidualBlerRetran CEModeA UE's PUSCH BLER for the ninth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the tenth HARQ
s10 retransmission
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the eleventh
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twelfth HARQ
s12 retransmission
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the thirteenth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the fourteenth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the fifteenth HARQ
s15 retransmission
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the sixteenth

Confidential
Chapter 10 Services

CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the seventeenth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the eighteenth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the nineteenth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twentieth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twenty first
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twenty second
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twenty third
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twenty fourth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twenty fifth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twenty sixth
CEModeA_ULResidualBlerRetran CEModeA UE's BLER for the twenty seventh
CEModeA_ULResidualBlerRetran The minimum PUSCH HARQ transmission
sMin number among which have positive value
between
CEModeA_ULResidualBlerRetrans0 and
CEModeA_ULResidualBlerRetrans27.
HARQ transmission number denotes "X" in
that "Xth HARQ retransmission".
CEModeA_ULResidualBlerRetran The maximum PUSCH HARQ transmission
sMax number among which have positive value
between
CEModeA_ULResidualBlerRetrans0 and
CEModeA_ULResidualBlerRetrans27.
HARQ transmission number denotes "X" in
that "Xth HARQ retransmission".
CEModeA_ULResidualBlerRetran CEModeA UE's average failure rate of
sAvg PUSCH HARQ retransmissions. The value is
calculated in terms of percentage, where the
denominator is set to be the counts of all
retransmissions adding the counts of initial
HARQ transmissions, and the numerator is
set to be the counts of all retransmissions
adding the counts of transmission failures
after the maximal HARQ retransmissions.
CEModeA_ULResidualBlerRetran CEModeA UE's failure rate of PUSCH initial
sNak HARQ transmissions after the maximal
HARQ retransmission occurs. It is the ratio of
the counts of transmission failures after the
maximal HARQ retransmissions to the
counts of initial transmissions.
CEModeA_ULTransmissionRetra The cumulated number of CEModeA UE's
ns0 initial PUSCH HARQ transmissions

Confidential
Chapter 10 Services

ns1 first PUSCH HARQ retransmissions
ns2 second PUSCH HARQ retransmissions
ns3 third PUSCH HARQ retransmissions
ns4 fourth PUSCH HARQ retransmissions
ns5 fifth PUSCH HARQ retransmissions
ns6 sixth PUSCH HARQ retransmissions
ns7 seventh PUSCH HARQ retransmissions
ns8 eighth PUSCH HARQ retransmissions
ns9 ninth PUSCH HARQ retransmissions
ns10 tenth PUSCH HARQ retransmissions
ns11 eleventh PUSCH HARQ retransmissions
ns12 twelfth PUSCH HARQ retransmissions
ns13 thirteenth PUSCH HARQ retransmissions
ns14 fourteenth PUSCH HARQ retransmissions
ns15 fifteenth PUSCH HARQ retransmissions
ns16 sixteenth PUSCH HARQ retransmissions
ns17 seventeenth PUSCH HARQ retransmissions
ns18 eighteenth PUSCH HARQ retransmissions
ns19 nineteenth PUSCH HARQ retransmissions
ns20 twentieth PUSCH HARQ retransmissions
ns21 twenty first PUSCH HARQ retransmissions
ns22 twenty second PUSCH HARQ
retransmissions
ns23 twenty third PUSCH HARQ retransmissions
ns24 twenty fourth PUSCH HARQ retransmissions

Confidential
Chapter 10 Services

ns25 twenty fifth PUSCH HARQ retransmissions
ns26 twenty sixth PUSCH HARQ retransmissions
ns27 twenty seventh PUSCH HARQ
retransmissions
CEModeA_ULTransmissionNacke The cumulated number of CEModeA UE's
dRetrans PUSCH HARQ retransmission failures after
the maximal HARQ retransmission occurs.

eMTC DL MCS CEModeA_DLTransmittedMcs0 The cumulated number of times that MCS0's
PDSCH is transmitted to CEModeA per
Layer/Codeword
CEModeA_DLTransmittedMcs1 The cumulated number of times that MCS1's
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
CEModeA_DLTransmittedMcs10 The cumulated number of times that
MCS10's PDSCH is transmitted to CEModeA
per Layer/Codeword
per Layer/Codeword
per Layer/Codeword

Confidential
Chapter 10 Services

per Layer/Codeword
per Layer/Codeword
per Layer/Codeword

eMTC UL MCS CEModeA_ULTransmittedMcs0 The cumulated number of times that MCS0's
PUSCH is received from CEModeA per
Layer/Codeword
CEModeA_ULTransmittedMcs1 The cumulated number of times that MCS1's
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
Layer/Codeword
CEModeA_ULTransmittedMcs10 The cumulated number of times that
MCS10's PUSCH is received from CEModeA
per Layer/Codeword
per Layer/Codeword
per Layer/Codeword

Confidential
Chapter 10 Services

per Layer/Codeword
per Layer/Codeword
per Layer/Codeword

eMTC DL Wideband CQI CEModeA_DLReceivedCQI0 The cumulated number per Layer/Codeword
that CQI0 is received from the CEModeA UE
CEModeA_DLReceivedCQI1 The cumulated number per Layer/Codeword
that CQI1 is received from the CEModeA
UE
UE
UE
UE
UE
UE
UE
UE
UE
UE
UE
UE
UE

Confidential
Chapter 10 Services

UE
UE
CEModeA_DLReceivedCQIMin The minimum value of
CEModeA_DLReceivedCQI0 ~
CEModeA_DLReceivedCQI15
CEModeA_DLReceivedCQIMax The maximum value of
CEModeA_DLReceivedCQIAvg The average value of
CEModeA_CQIErase The cumulated number per Layer/Codeword
that CQIerase is received from the
CEModeA UE

eMTC Handover Intra- eMTC_IntraFreqOutAtt The cumulated number of Outgoing intra-
Frequency Out frequency handover attempt count for eMTC
UE
eMTC_IntraFreqOutPrepSucc The cumulated number of Outgoing intra-
frequency handover preparation success
count for eMTC UE
eMTC_IntraFreqOutSucc The cumulated number of Outgoing intra-
for eMTC UE

eMTC Handover Intra- eMTC_IntraFreqInAtt The cumulated number of Incoming intra-
Frequency In frequency handover attempt count for eMTC
UE
eMTC_IntraFreqInPrepSucc The cumulated number of Incoming intra-
frequency handover preparation success
count for eMTC UE
eMTC_IntraFreqOutSucc The cumulated number of Incoming intra-
for eMTC UE
REFERENCE
[1] TS36.211 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical
channel and modulation
[2] TS36.212 Evolved Universal Terrestrial Radio Access (E-UTRA);
[3] TS36.213 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical

Confidential
Chapter 10 Services
layer procedures
[4] TS36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Universal Terrestrial Radio Access Network (E-UTRAN); Overall description;
Stage 2
[7] TS36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
X2 Application Protocol (X2AP)

Confidential
Chapter 11 System Test and

Analysis
LTE-OM9001, Cell Traffic Trace

INTRODUCTION
This feature provides detailed information at call level on all UEs in a specific cell.
The traceable interfaces are UE-Associated S1, X2 and RRC. This trace result is
transmitted to the LSM or the Trace Collection Entity (TCE) server.
BENEFIT
This feature allows operator to analyze all the signaling messages transmitting and
receiving in a specific cell, which can be used for troubleshooting.
DEPENDENCY
TCE
E-UTRAN (LTE)
LIMITATION
• LSM can act as TCE server but stores simultaneously trace results from up to
6 cells in E-UTRAN system.
• In case of CPU overload status, tracing can be suspended to prevent the
negative impact on the service users.
SYSTEM IMPACT
capabilities.
Interfaces
Added or modified trace information may affect interface with External Server, so
FEATURE DESCRIPTION
Samsung eNB provides 3GPP standard (TS 32.422 & 32.423) based Cell Traffic

Confidential
Chapter 11 System Test and Analysis
Trace.
This feature performs tracing signaling interface messages on all calls in the
specific cell. Operator can control the cell traffic trace using cell ID through LSM.
If trace results are generated, eNB reports it to TCE. Operator can create/configure
some key TCE related parameters TCE_ID, TCE_TYPE, TCE_IPV4, and
STATUS by CRTE-TCE-LIST and CHG-TCE-LIST. Samsung eNB supports
standalone TCE and LSM embedded TCE type that can be configured by
TCE_TYPE (CHG-TCE-LIST/CRTE-TCE-LIST). The following figure shows
standalone TCE scenario.
When several PLMNs are supported in the RAN, for starting Trace the eNB shall
only select UEs where the pLMNTarget = selectedPLMN-Identity that the UE
includes in RRCConnectionSetup message 3GPP TS 36.331
Management based trace procedure is as follows:
• Management Based Trace Activation (New Call)

Confidential
• Management Based Trace Activation (Call undergoing call setup)
• Management Based Trace Activation (Existing Call)

Confidential
• Management Based Trace Deactivation
If a call ends normally by sending a RRC Connection Release message to the UE,
the trace recording session for that call is ended. To stop the tracing for the cell,
the deactivate trace message is sent to the eNB through the LSM.
The cell traffic trace may be disabled depending on CPU overload status to avoid
overload to system. Operator can configure TRACE_DISABLE_CONDITION,
TRACE_RESUME_CONDITION (CHG-ENBOVLD-CTRL) to set the trace
disable/resume condition based on CPU load status.
SYSTEM OPERATION
How to Activate
Preconditions
1 In LSM, select Performance Management | Call Trace

Confidential
2 Select Register
3 Select Management based trace for trace type
4 Input the following parameters
o Target eNB
o List of interface: S1, X2, Uu
o Depth: Minimum, Medium, and Maximum
o Target cell ID
o TCE_IP
o Target MCC
o Target MNC
o Choose Trace Overload Control Flag
1 In LSM, select Performance Management | Call Trace
2 Select a trace in session
3 Click Stop
Key Parameters
parameters.
Parameter Descriptions of RTRV-TCE-LIST/CHG-TCE-LIST/CRTE-TCE-
LIST/DLT-TCE-LIST
tceType This parameter represents the TCE server type and has to one of three below
values.
• standAlone: TCE Server is standAlone Type.
• lsmEmbedded: TCE Server is embedded in LSM
• smartSon: TCE Server is for Smart SON server
Parameter Descriptions of RTRV-ENBOVLD-CTRL/CHG-ENBOVLD-CTRL

traceResumeCondition The Condition to resume Call Trace in eNB
traceDisableCondition The Condition to disable Call Trace in eNB

Confidential
Parameter Descriptions of RTRV-TCE-STS

tceIndex TCE Index
tceId TCE ID
Status TCP connection status retrieved from the kernel. The status shall be represented
as either connected or disconnected
Counters and KPIs

with this feature.
REFERENCE
[3] 3GPP TS32.422 Telecommunication management; Subscriber and equipment
trace; Trace control and configuration management
trace; Trace data definition and management

Confidential
LTE-OM9002, Subscriber and Equipment Trace

INTRODUCTION
Subscriber and equipment trace provide detailed information at call level on
specific mobile(s). This trace data is transmitted to the TCE server
BENEFIT
This feature allows operator to analyze the signaling messages transmitting and
receiving through S1-MME, X2 and Uu interfaces for a designated user, which can
be used for troubleshooting.
DEPENDENCY
MME, TCE
E-UTRAN (LTE)
LIMITATION
• In case of CPU overload status, tracing can be suspended to prevent the
negative impact on the service users.
• An eNB can support the signaling based trace up to 100UEs.
SYSTEM IMPACT
capabilities.
Interfaces
FEATURE DESCRIPTION
Samsung eNB provides 3GPP standard (TS 32.422 & 32.423) based Subscriber
and Equipment Trace.
This feature performs tracing signaling interface messages on a specific UE.
This feature supports mobility. If the Trace Activation IE is contained in the Initial
Context Setup Request message, or Trace Start message is received from the
MME, the eNB starts a trace for the call. If the Trace Activation IE is contained in
the Handover Request message received from the source eNB or the MME in case
of X2 or S1 Handover, the eNB starts a trace for the call.
Confidential
If trace results are generated, eNB reports it to TCE. Operator can create/configure
some key TCE related parameters TCE_ID, TCE_TYPE, TCE_IPV4, and
STATUS by CRTE-TCE-LIST and CHG-TCE-LIST.
Signaling based trace procedure is as follows:

• Signaling Based Trace Activation
• Signaling based trace deactivation

Confidential
If the call ends normally by sending a RRC Connection Release message to the
UE, the trace is ended. To stop the tracing, the deactivate trace message is sent to
the eNB by the MME.
SYSTEM OPERATION
How to Activate
Preconditions
If Trace Activation IE is included in the Initial Context Setup Request message,
the Trace Start message or the Handover Request (S1/X2) message from the
MME, the eNB starts the trace for the call.
• Operator can control the trace disable/resume threshold.
o If cpu state is higher than disable threshold, trace is paused.
o After trace disabled, cpu state is lower than resume threshold, trace is
restart.
• If RRC connection is released, the UE's trace is deactivated.
• If Deactivate Trace message is received from MME for specific UE, the trace
is deactivated.

Confidential
Key Parameters
parameters.
Parameter Descriptions of RTRV-TCE-LIST/CHG-TCE-LIST/CRTE-TCE-
LIST/DLT-TCE-LIST
TCE_TYPE This parameter represents the TCE server type and has to one of three below
values.
• standAlone: TCE Server is standAlone Type.
• lsmEmbedded: TCE Server is embedded in LSM
• smartSon: TCE Server is for Smart SON server
Parameter Descriptions of RTRV-ENBOVLD-CTRL/CHG-ENBOVLD-CTRL

TRACE_RESUME_CONDIT The Condition to resume Call Trace in eNB
ION
TRACE_DISABLE_CONDITI The Condition to disable Call Trace in eNB
ON
Parameter Descriptions of RTRV-TCE-STS

TCE_INDEX TCE Index
TCE_ID TCE ID
STATUS TCP connection status retrieved from the kernel. The status shall be
represented as either connected or disconnected
Counters and KPIs

with this feature.
REFERENCE

Confidential


Confidential
LTE-OM9003, UE Throughput and RF

information Trace
INTRODUCTION
UE Throughput and RF information Trace provides more detailed information
which is vendor specific. The trace result includes throughput and RF information.
The UE Throughput and RF information Trace may be trigged by MME with trace
depth set to Vendor Specific Extension. The result of the trace is transmitted to the
LSM or TCE.
BENEFIT
UE Throughput and RF information Trace helps to analysis traffic (throughput,
and so on.) and RF information per UE.
DEPENDENCY
MME, TCE
• Others
Possible to designate an UE in connection with LSM and CSM
LIMITATION
• In case of CPU overload status, tracing can be stopped to prevent the negative
impact on the service users.
• This trace is performed by the cycle of 2.56 seconds.
• This feature can support up to 6 UEs per cell.
SYSTEM IMPACT
capabilities.
• Cell Traffic Trace: This feature provides detailed information at call level on
all UEs in a specific cell.
• Subscriber and Equipment Trace: This feature provides detailed information at
call level on one or more specific mobile(s).
• Minimization of Drive Test (MDT): This feature is a standardized mechanism
to collect the network performance measurements from the commercial UEs
with possibly the location information.

Confidential

None
Coverage
None
Interfaces
FEATURE DESCRIPTION
This is Samsung proprietary feature. When the signaling trace is activated with
maximum (with Vendor Specific Extension VSE) from MME, eNB activates this
feature for the call. The trace depth is included in “Trace Activation” IE of S1
messages from MME. Trace Activation IE can be included in INITIAL
CONTEXT SETUP REQUEST, TRACE START or the HANDOVER REQUEST
(S1/X2) messages.
If this feature is activated, eNB reports the RF and throughput information to TCE
server periodically. (Refer LTE-OM9002 to the detail description about signaling
based trace)
The following table shows the throughput information items.

Classification Item
PDCP layer (per UE/Bearer) DL/UL PDCP Bytes
Number of DL/UL Packets
Number of Dropped DL/UL PDCP Packets
RLC layer (per UE/Bearer) DL/UL RLC Bytes
Number of DL/UL RLC packets
Number of Lost Packet at RLC DL
Number of DL Retransmitted Packets
Number of Dropped Packet at RLC DL
Number of Delayed Packet at RLC layer
User Plane Latency
MAC layer (per UE/Bearer) DL/UL Traffic Bytes

Confidential
The following table shows the RF information items.

Classification Item Description
MAC layer UL Dynamic UE’s Power Headroom Averaged value of UE’s Power
Scheduling Headroom (dB)
information
BSR(buffer status report) Averaged value of UE’s
information on RBG (Radio BSRinformation (byte)
Bearer Group)
CQI (Channel Quality Accumulated count per CQI level Accumulated count per wideband
Indicator) CQI level (0~15)
DL MCS (Modulation Accumulated statistics per DL Accumulated statistics per DL MCS
and coding scheme) MCS (0~31)
UL MCS (Modulation Accumulated statistics per UL Accumulated statistics per UL MCS
and coding scheme) MCS (0~31)
UL MAC BLER UL BLER # Blocks with CRC error / Total
received MAC PDU (%)
Assigned RB count DL Assigned RE count & RB DL Assigned RE count & RB count
count
Power setting TPC (Transmit power control) PUCCH / PUSCH, per each
information command count command (-1, 0, 1, 3dB : i.e., PUCCH
0 -> -1dB, PUCCH 1 -> 0 dB, PUCCH
2 -> 1dB, PUCCH 3 -> 3dB)
UE location Time Advance Averaged TA (1 TA = 0.52us)
information
MIMO Feedback PMI (Precoder Metric Indicator) PMI count per index (0~3)
count
RI (Rank Indicator) count RI count Per index (0~1)
UE DL RI0 : # of assignment on layer
0
UE DL RI1 : # of assignment on layer
1
During the collection period
HARQ Feedback DL ACK DL Number of HARQ feedback for
information PUCCH (ACK)
DL NACK DL Number of HARQ feedback for
PUCCH (NACK)
DL DTX DL Number of HARQ feedback for
PUCCH (DTX)
UL ACK UL Number of HARQ feedback for
PUCCH (ACK)
UL NACK UL Number of HARQ feedback for
PUCCH (NACK)
SYSTEM OPERATION
How to Activate

Confidential
Preconditions
• If the Trace Activation IE with specific bit value '1' is contained in the Initial
Context Setup Request (S1), Handover Request (X2) or Trace Start (S1)
message received from the MME or the source eNB (HO case), the eNB starts
a trace for the UE. (Refer to Trace Activation in 3GPP 36.413/423)
• When the signaling trace is started with Vendor Specific Extension (VSE), the
eNB active the UE Throughput and RF information Trace function.
• The eNB transmits traffic and RF trace data to LSM every an period.
If the Trace Activation IE with specific bit value '0' is contained in the Initial
Context Setup Request (S1), Handover Request (X2) or Trace Start (S1) message
received from the MME or the source eNB (HO case), the eNB stops a trace for
the UE. (Refer to Trace Activation in 3GPP 36.413/423)
Key Parameters
Counter and KPIs

The information collected as the result of the call detail trace is as follows:
Counter Description How to Check
Equip In case of Equip, transmits the value The operator can check this with
periodically. In case of N_Equip, stops PM statistics in the LSM
transmission.
Trace Reference ID The trace reference ID of the phone The operator can check this with
PM statistics in the LSM
DL PDCP Bytes_TOTAL No. of DL bytes transmitted from S-GW The operator can check this with
to eNB within the collection interval. PM statistics in the LSM
UL PDCP Bytes_TOTAL No. of bytes transmitted to UL within the The operator can check this with
collection interval PM statistics in the LSM
Number of DL PDCP No. of user data packets transmitted to The operator can check this with
Packets_TOTAL UE PM statistics in the LSM
Number of UL PDCP No. of user data packets received from The operator can check this with
Packets_TOTAL UE PM statistics in the LSM
Number of Dropped DL PDCP No. of DL packets dropped from PDCP The operator can check this with
Packets_TOTAL PM statistics in the LSM
Number of Dropped UL PDCP No. of UL packets dropped from PDCP The operator can check this with
Packets_TOTAL PM statistics in the LSM
Active Bearer Count Maximum number of the bearers being The operator can check this with
used in the interval PM statistics in the LSM
Bearer1 ID RB_ID (1~8) The operator can check this with

Confidential
Bearer1 QCI QoS ID The operator can check this with

DL PDCP Bytes_Bearer1 No. of DL bytes transmitted from S-GW The operator can check this with
to eNB within the collection interval. PM statistics in the LSM
UL PDCP Bytes_Bearer1 No. of bytes transmitted to UL within the The operator can check this with
Packets_Bearer1 UE PM statistics in the LSM
Packets_Bearer1 PM statistics in the LSM
Bearer 8 ID RB_ID (1~8) The operator can check this with
Bearer8 QCI QoS ID The operator can check this with
DL PDCP Bytes_Bearer8 DL Byte number of transmit from S-GW The operator can check this with
to eNB for gathering period PM statistics in the LSM
UL PDCP Bytes_Bearer8 No. of bytes transmitted to UL within the The operator can check this with
DL RLC Bytes DL RLC bytes transmitted within the The operator can check this with
UL RLC Bytes UL RLC bytes transmitted within the The operator can check this with
Number of DL RLC Packets DL RLC packets transmitted within the The operator can check this with
Number of UL RLC Packets UL RLC packets transmitted within the The operator can check this with
Operator can check this with No. of lost packets in RLC DL Air section The operator can check this with
PM statistics in the LSM (In case of UL, impossible to measure) PM statistics in the LSM
Number of Lost Packet at RLC
DL
Number of DL Retransmitted Possible to measure accurate losses only The operator can check this with
Packets in the DL AM mode. PM statistics in the LSM

Confidential
Number of Dropped Packet at No. of packets discarded from RLC The operator can check this with
RLC DL PM statistics in the LSM
Number of Delayed Packet at No. of packets delayed from RLC The operator can check this with
RLC layer PM statistics in the LSM
User Plane Latency IP latency (unit = ms) The operator can check this with
Bearer 1 QCI QoS ID The operator can check this with
DL RLC Bytes_Bearer 1 DL RLC bytes transmitted within the The operator can check this with
UL RLC Bytes_Bearer 1 UL RLC bytes transmitted within the The operator can check this with
Number of DL RLC DL RLC packets transmitted within the The operator can check this with
Packets_Bearer 1 collection interval PM statistics in the LSM
Number of UL RLC UL RLC packets transmitted within the The operator can check this with
Number of Lost Packet at RLC No. of lost packets in RLC DL Air section The operator can check this with
DL_Bearer 1 (In case of UL, impossible to measure) PM statistics in the LSM
Packets_Bearer 1 in the DL AM mode. PM statistics in the LSM
RLC DL_Bearer 1 PM statistics in the LSM
Number of Delayed Packet at No. of packets delayed from RLC The operator can check this with
RLC layer_Bearer 1 PM statistics in the LSM
User Plane Latency_Bearer 1 IP latency (unit = ms) The operator can check this with
DL RLC Bytes_Bearer 8 DL RLC bytes transmitted within the The operator can check this with
UL RLC Bytes_Bearer 8 UL RLC bytes transmitted within the The operator can check this with
Number of DL RLC DL RLC packets transmitted within the The operator can check this with
Number of UL RLC UL RLC packets transmitted within the The operator can check this with
Number of Lost Packet at RLC No. of lost packets in RLC DL Air section Operator can check this with PM
DL_Bearer 8 (In case of UL, impossible to measure) statistics in the LSM

Confidential
Packets_Bearer 8 in the DL AM mode. PM statistics in the LSM
RLC DL_Bearer 8 PM statistics in the LSM
Number of Delayed Packet at No. of packets delayed from RLC Operator can check this with PM
RLC layer_Bearer 8 statistics in the LSM
User Plane Latency_Bearer 8 IP latency (unit = ms) The operator can check this with
DL Traffic ratio  DL Traffic Transmitted in DL traffic bytes (integers) The operator can check this with
Bytes (Total of DRBs) Aggregate of 8 DRBs (SRB information PM statistics in the LSM
excluded)
UL Traffic ratio  UL Traffic Transmitted in UL traffic bytes (integers) The operator can check this with
Bytes (Total of DRBs) Aggregate of 8 DRBs (SRB information PM statistics in the LSM
excluded)
Bearer 1 ID RB_ID The operator can check this with
DL Traffic Bytes (DRB #1) DL Traffic Bytes DRB #1 The operator can check this with
UL Traffic Bytes (DRB #1) UL Traffic Bytes DRB #1 The operator can check this with
Bearer 8 ID RB_ID The operator can check this with
DL Traffic Bytes (DRB 8) DL Traffic Bytes DRB #8 The operator can check this with
UL Traffic Bytes (DRB 8) UL Traffic Bytes DRB #8 The operator can check this with
The RF information included in the result of the call detail trace is as follows:
Equip In case of Equip, transmits the value The operator can check this with
periodically. In case of N_Equip, stops PM statistics in the LSM
transmission.
Trace Reference ID The trace reference ID of the phone The operator can check this with
UE’s Power Headroom The average value received during the The operator can check this with
fixed interval (dB) PM statistics in the LSM
A negative number allowed.
BSR (buffer Status Report) The average value received during the The operator can check this with

Confidential

information on RBG (Radio fixed interval (bytes) PM statistics in the LSM
Bearer Group)
CQI 1 Wideband CQI (1-15). Accumulated The operator can check this with
count type by CQI level in the given PM statistics in the LSM
interval
CQI 15 - The operator can check this with
SRS snr Provides SRS received power as the The operator can check this with
mean of the valid value in the given PM statistics in the LSM
interval.
DL MCS 0 Possible to six counts per cell to the The operator can check this with
maximum by phone due to the PM statistics in the LSM
performance issue. Interval of 2.56
seconds
DL MCS 31 Possible to six counts per cell to the The operator can check this with
seconds
UL MCS 0 Possible to six counts per cell to the The operator can check this with
seconds
UL MCS 31 Possible to six counts per cell to the The operator can check this with
seconds
UL BLER No. of CRC error-occurring blocks/no. of The operator can check this with
total blocks received (MAC PDU). (Unit: PM statistics in the LSM
%)
DL assigned RE count DL direction assigned RE count The operator can check this with
DL assigned RB count DL direction assigned RB count The operator can check this with
UL assigned RE count UL direction assigned RE count The operator can check this with
UL assigned RB count UL direction assigned RB count The operator can check this with
TPC for PUCCH[0] (-1 dB) Accumulated PUCCH power control The operator can check this with
statistics (Accumulated value of the TPC PM statistics in the LSM
(transmit power control) command (-1
dB) transmission count)
TPC for PUCCH[1] (0 dB) Accumulated PUCCH power control The operator can check this with
(transmit power control) command (0 dB)
transmission count)
transmission count)

Confidential
transmission count)
TPC for PUSCH[0] (-1 dB) Accumulated PUSCH power control The operator can check this with
transmission count)
TPC for PUSCH[1] (0 dB) Accumulated PUSCH power control The operator can check this with
transmission count)
transmission count)
transmission count)
Time Advance Accumulated value of TA (Average RTD) The operator can check this with
- The unit of raw data provided from MAC PM statistics in the LSM
is the multiple of 0.52 us. In short, the
actual output must be the value of 0.52us
* time advance (Unit: us).
UE -> eNB PMI 0 Information informed by UE (Precoder The operator can check this with
(UL PMI 0) Metric Indicator) index 0 PM statistics in the LSM
UL PMI = PMI received from UE
eNB -> UE PMI 0 Information given by the base station The operator can check this with
(DL PMI 0) (Precoder Metric Indicator) index 0 PM statistics in the LSM
PMI allocated to UE
PMI allocated to UE
PMI allocated to UE

Confidential

PMI allocated to UE
eNB -> UE RI 0 # of assignment on layer 0 (during 2.56 The operator can check this with
(UE DL RI 0) sec) PM statistics in the LSM
eNB -> UE RI 1 # of assignment on layer 1 (during 2.56 The operator can check this with
(UE DL RI 1) sec) PM statistics in the LSM
UE -> eNB RI 0 RI requested by UE-Count by index Operator can check this with PM
(UE UL RI 0) (index 0) statistics in the LSM
UE -> eNB RI 1 RI requested by UE-Count by index The operator can check this with
(UE UL RU 1) (index 1) PM statistics in the LSM
DL ACK DL Number of HARQ feedback for The operator can check this with
PUCCH (ACK) PM statistics in the LSM
DL NACK DL Number of HARQ feedback for The operator can check this with
PUCCH (NACK) PM statistics in the LSM
DL DTX DL Number of HARQ feedback for The operator can check this with
PUCCH (DTX) PM statistics in the LSM
UL ACK UL Number of HARQ feedback for The operator can check this with
PUCCH (ACK) PM statistics in the LSM
UL NACK UL Number of HARQ feedback for The operator can check this with
PUCCH (NACK) PM statistics in the LSM
REFERENCE

Confidential
LTE-OM9004, CSL (Call Summary Log) Report

INTRODUCTION
This feature collects the detail information for a call. The call information, call
duration, or handover information, and so on are automatically collected and
transmitted to the LSM or the external server.
BENEFIT
• An operator can determine UE performance and failure scenarios using CSL
data.
• The operator can analyze the detail information of a call and may use the
results for optimization of the network.
DEPENDENCY
• HW dependency: Supports DU that consists of S8400 mode-based channel
card only.
• Required Network Elements: External server for CSL data is required.
LIMITATION
The CSL data is designed to provide only to the external server considering the
performance. However, an eNB can provide CSL data to LSM for temporary
purpose such as Lab test for the convenience of operator.
SYSTEM IMPACT
capabilities.
Interfaces
Added or modified CSL information may affect interface with external server, so it
is required to discuss in advance.
FEATURE DESCRIPTION
The Call Summary Log (CSL) data is collected by eNB.
When a call is setup, the eNB starts to collect information for the call. If the call is
released, the eNB stops collecting information and reports CSL data to the external
server. The external server (for example, DCM) collects eNB CSLs, and provides
stitching for both eNB CSL and MME PCMD data based on a UE.

Confidential
RTT
Get stitching results
Stitched CSL Aggregation

DCM PCMD
(MME PCMD + eNB CSL) Server
opt.
eNB CSL LSM
The eNB transmits CSL data of all calls (both normal release and abnormal
release) to DCM by default.
If the operator wants to see the CSL data in LSM for temporary purpose, the eNB
can transmit CSL data of abnormal call only to LSM by changing relevant
parameter.
Additional configurations for CSL control are as follows:
• Interface information of external server such as IP version and address.
• Maximum number of re-transmission the CSL data using UDP protocol
(infinity, 1, 2, 3, 4, 5, 6).
The operator can configure the above parameters by using CHG-CSL-INF in
LSM.
The CSL data includes detail information for a call such as call information,
subscriber information, RRC information, call end event, mobility, measurement
reporting, bearer data volume, VoLTE, BLER, capacity, UL power measurement,
and so on.
SYSTEM OPERATION
How to Activate
Key Parameters
There are no specific parameters associated with this feature

Confidential
parameters.
Parameter Descriptions of RTRV-CSL-INF/CHG-CSL-INF
DB_INDEX Index
CSL_SERVER The type of CSL Server.
IP_VER The type of the IP address of the external server for which CSL data (IPV4 or
IPV6) is to be collected.
CSL_SERVER_IPV4 The external CSL server's IP address in the IPv4 format.
CSL_SERVER_IPV6[16] The external CSL server's IP address in the IPv6 format.
CSL_PORT_NUM External Server Port Number to Receive Data
BUFFER_TIME This parameter is for the buffering time for which eNB stores CSL data in the
internal memory to reduce the network load. If the buffering time is set to 10,
all of the CSL data stored in the memory is sent to the CLS server 10 seconds
after the data is created. Note that the CSL data is also transmitted to the CSL
server when the number of CSL data entries stored reaches 10 even within 10
seconds of data creation.
BUFFERING_COUNT The maximum data count one-time transfer.
UDP_ACK_CONTROL This parameter controls the number of CSL data re-transmissions when using
UDP Ack method and transmitting to an external server.
• 0: no retransmission
• 1: 1 retransmission
• 7: Infinity retransmissions
PROTOCOL_SELECTION This parameter configures which transmitting protocol to use when
transmitting CSL to an external server.
• 0: TCP
• 1: UDP Ack
Counters and KPIs

with this feature.
REFERENCE

Confidential
LTE-OM9010, VoLTE Monitoring

INTRODUCTION
Using the third-party's drive test tools to evaluate voice quality is time and cost
consuming. Therefore, it is important for vendors to develop their own
measurement-based evaluation method. Samsung uses VoLTE Monitoring and
Analysis (VoMA) tool to measure the voice quality over LTE such as packet loss,
jitter, MOS and Mute. VoMA is mainly used for volte quality monitoring, volte
quality optimization, VIP call tracing and user complaint handling. VoMA reduces
the necessity of drive tests required for obtaining voice quality. VoMA consists of
two main components; 1) collecting the VoLTE logs from eNBs and 2) analyzing
the collected logs in an external server.
This feature includes the first component that the eNB collects VoLTE logs. The
other component of the analysis of the logs is described in the VoMA server
manuals, which is out of scope.
BENEFIT
Primary benefit of VoMA is the automatic analysis of the VoLTE quality of the
calls (for specified UEs or for the specified time) and the identification of the
problem causes and their locations.
• VoLTE quality monitoring: loss, jitter and delay
• Identification of problem causes: decompression failure due to RoHC error,
loss, duplicated packet, out-of-order, delay
• Isolation of the section that problems occur: UL air, backhaul + core network,
inner eNB, and DL air
DEPENDENCY
None
LIMITATION
The number of simultaneous bearers to be monitored: 6 per cell/20 per eNB
SYSTEM IMPACT
FEATURE DESCRIPTION
VoMA collects the following information from eNB to analyze voice quality.
• PDCP layer at eNB (collect both UL and DL flow)

Confidential
o Arrival time of UL and DL voice packets at PDCP layer

o RoHC encryption and decryption success of UL and DL voice packets
o PDCP sequence number of UL and DL voice packets
o Header information of UL and DL voice packets
♦ IP header (support IPv4 and IPv6)
♦ UDP header
♦ RTP header
o RLC layer at eNB (collect only DL flow)
♦ Reception time of PDCP PDU from PDCP layer to RLC layer
♦ Transmission time of RLC PDU from RLC layer to MAC layer
o MAC layer at eNB (collect only DL flow)
♦ HARQ ACK/NACK information of DL voice packets
♦ HARQ ACK/NACK detection time of DL voice packets
VoMA supports UE Trace mode and Cell Trace mode for VoLTE quality analysis
according to purpose
• UE Trace mode
o Analyze the voice quality of a specific UE
o Use TraceReference ID to select a specific UE
♦ Operator performs a signal trace to UE in advance to obtain
TraceReference ID
o UE trace mode can be enabled by VOMA_USAGE in CHG-VOMA-UE
• CELL Trace mode
o Analyze the voice quality of a non-specific UE
o Sequentially select a VoLTE UE accessed to cell
o CELL Trace mode can be enabled by VOMA_USAGE in CHG-VOMA-
CELL
Note that VoMA has a limitation on the maximum number of concurrent traced
UEs. If the number of concurrently VoMA tracing UEs increases, the processing
load of eNB increases. For stable system operation, the maximum number of
traceable UEs is limited to 6 per cell and 20 per eNB. The operator can configure
the maximum number of traceable UEs by MAX_VOMA_COUNT_ENB and
MAX_VOMA_COUNT_CELL in CHG-ENB-INF.
Figure below depicts VoMA system work mechanism.

Confidential
VoMA server
LSM Output: VoLTE Quality (Loss, Jitter, Mos and Mute)
VoMA Control
VoMA log VoMA log
B/H & Core
eNB eNB
Air Air
Quality from B/H
DL/UL Air Quality (B/H + Core + IMS) DL/UL Air Quality
SYSTEM OPERATION
How to Activate
Preconditions
• To activate this feature, for UE based VoLTE monitoring, an administrator
uses the CHG-VOMA-UE to register Trace Reference of the specific UE for
VoLTE Monitoring.
• It is noted that the administrator has to register signaling based trace for this
UE in advance, to retrieve Trace Reference.
• For each VOMA_INDEX, different trace reference (=
TRACE_REFERENCE_MCC + TRACE_REFERENCE_MNC +
TRACE_ID) is assigned, and if an operator is going to use this trace reference,
VOMA_USAGE is set to be EQUIP.
To activate this feature, for Cell level VoLTE monitoring, an administrator uses
the CHG-VOMA-CELL command to change VOMA_USAGE to be EQUIP for a
specific Cell.
To deactivate this feature, an administrator uses the CHG-VOMA-CELL command
to change VOMA_USAGE not to be EQUIP for a specific Cell.

Confidential
Key Parameters
Parameter Descriptions of CHG-VOMA-UE/RTRV-VOMA-UE
VOMA_USAGE This attribute indicates the UE is used or not for VoMA Trace.
Parameter Descriptions of CHG-VOMA-CELL/RTRV-VOMA-CELL

VOMA_USAGE This attribute indicates the cell is used or not for VoMA Trace.
Parameter Descriptions of CHG-VOMA-UE/RTRV-VOMA-UE
VOMA_INDEX This attribute indicates Trace-Reference index which is on the VoMA Trace.
VOMA_USAGE This attribute indicates the UE is used or not for VoMA Trace.
TRACE_REFERENCE_MCC It is the MCC (Mobile Country Code) of the Trace Reference for which VoMA
trace is triggered.
For example, if the Trace Reference received by S1AP or X2AP message is
43 58 07 00 34 D7, its BCD format PLMN ID is 43 58 07, and MCC is 348.
(Reference: TS 32.423)
TRACE_REFERENCE_MNC It is the MNC (Mobile Network Code) of the Trace Reference for which VoMA
trace is triggered.
For example, if the Trace Reference received by S1AP or X2AP message is
43 58 07 00 34 D7, its BCD format PLMN ID is 43 58 07, and MNC is 570.
(Reference: TS 32.423)
TRACE_ID This attribute indicates decimal format of the Trace ID in the Trace Reference
for which VoMA trace is triggered. For example, if the trace reference
received by S1AP or X2AP message is 43 58 07 00 34 D7, its BCD format
PLMN ID is 43 58 07, and its Trace ID is 00 34 D7 in hexadecimal format and
stored in this attribute as decimal number13527. (Reference: TS 32.423)
VOMA_QCI0 This attribute indicates the first VoMA Trace QCI.
VOMA_QCI0_MAX_LENGTH This attribute indicates maximum length which includes PDCP header and
logging payload for QCI0.
Parameter Descriptions of CHG-VOMA-CELL/RTRV-VOMA-CELL

VOMA_USAGE This attribute indicates the cell is used or not for VoMA Trace.

Confidential
Counters and KPIs

with this feature.
REFERENCE
None

Confidential
LTE-OM9100, Key Performance Indexes

INTRODUCTION
Key performance indicators (KPIs) are used to monitor the quality of service
provided to the end user. They are calculated using counters collected by eNB.
Some KPIs are defined in TS32.450 while others are proprietary to Samsung. This
feature provides a brief introduction to KPIs. For detailed information, refer to
LTE eNB Counter Description manual.
BENEFIT
The operator can monitor the following characteristics of the service provided to
the end user:
• Accessibility
• Retainability
• Integrity
• Availability
• Mobility
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
ACCESSIBILITY
These KPIs show probability for an end-user to be provided with an E-RAB at
request. Probability success rate for E-RAB establishment is calculated by
multiplying the probability success rates for different parts of E-RAB
establishment. Probability success rate of each part of E-RAB establishment is
calculated as successful attempts divided by total number of attempts.
Name Description
ErabAccessibilityInit = (SumRrcConnEstabSucc / SumRrcConnEstabAtt) * Initial E-RAB establishment
(SumS1sigS1ConnEstabSucc / SumS1sigS1ConnEstabAtt) * success rate
(SumErabEstabInitSuccNbr / SumErabEstabInitAttNbr) * 100%.

Confidential
Name Description
ErabAccessibilityAdd = (SumErabEstabAddSuccNbr / Added E-RAB establishment
SumErabEstabAddAttNbr) * 100%. success rate
E-RAB Connection Failure Rate = 0 if SumRrcConnEstabAtt = 0 OR Probability that an end-user is
SumS1sigS1ConnEstabAtt = 0 OR SumErabEstabInitAttNbr = 0. Otherwise, E- not provided with an E-RAB
RAB Connection Failure Rate = 100 - at the initial request
(SumRrcConnEstabSucc/SumRrcConnEstabAtt) *
(SumS1sigS1ConnEstabSucc/SumS1sigS1ConnEstabAtt) *
(SumErabEstabInitSuccNbr/SumErabEstabInitAttNbr) * 100%
RETAINABILITY
This KPI shows how often an end-user abnormally loses an E-RAB during the
time the E-RAB is used.
Name Description
ErabRetainability = (SumRelActive / RetainSessionTimeUE) * 100. Number of E-RABs with data
in a buffer that was
abnormally released,
normalized with number of
data session time units.
INTEGRITY
These KPIs show how E-UTRAN impacts the service quality provided to an end-
user.
Name Description
EutranIpThroughput = IntegrityEutranIpThroughputTot / E-UTRAN IP throughput per
IntegrityEutranIpThroughputCnt QCI
EutranIpLatency = IntegrityEutranIpLatencyTot / IntegrityEutranIpLatencyCnt E-UTRAN IP latency per QCI
AVAILABILITY
This KPI measures the availability of E-UTRAN cell.
Name Description
EutranCellAvailability = ((CellAvailPmPeriodTime - ReadCellUnavailableTime) Percentage of time the cell is
/ CellAvailPmPeriodTime) * 100%. considered available
MOBILITY
These KPIs measure E-UTRAN handover success rates.
Name Description
EutranMobilityHOIntra = (sumHOIntra_Succ / sumHOIntra_Att) * 100%. Intra-eNB handover success
rate
EutranMobilityHOX2Out = (sumHOX2Out_Succ / sumHOX2Out_Att) * 100%. Outgoing X2 handover
success rate
EutranMobilityHOX2In = (sumHOX2In_Succ / sumHOX2In_Att) * 100%. Incoming X2 handover
success rate
EutranMobilityHOS1Out = (sumHOS1Out_Succ / sumHOS1Out_Att) * 100%. Outgoing S1 handover
success rate
EutranMobilityHOS1In = (sumHOS1In_Succ / sumHOS1In_Att) * 100%. Incoming S1 handover
success rate
EutranMobilityHOInterRatHrpd = (sumHOInterRatHrpd_Succ / Inter-RAT optimized HRPD
sumHOInterRatHrpd_Att) * 100%. handover success rate

Confidential
Name Description
EutranMobilityHOInterRatUtranOut = (sumHOInterRatUtranOut_Succ / Outgoing inter-RAT handover
sumHOInterRatUtranOut_Att) * 100%. success rate
EutranMobilityHOInterRatUtranIn = (sumHOInterRatUtranIn_Succ / Incoming inter-RAT handover
sumHOInterRatUtranIn_Att) * 100%. success rate
EutranMobilityHOInter = ((sumHOS1Out_Succ + sumHOX2Out_Succ) / Outgoing handover success
(sumHOS1Out_Att + sumHOX2Out_Att)) * 100%. rate to an eNB of the same
frequency
VOLTE
VOLTE_QUALITY
It measures VoLTE quality for QCI#1 Bearer
Name Description
VoLTEDropRate = SumVoLTECallDropQci / (SumVoLTEEstabInitSuccNbr + The number of VoLTE Drop
SumVoLTEEstabAddSuccNbr + SumVoLTEErabIncomingHoSuccNbr) * 100. rate
VoLTEULQualityDefectRate = (SumVoLTEULQualityDefect / The number of UL Quality
(SumVoLTEEstabInitSuccNbr + SumVoLTEEstabAddSuccNbr + Defect rate
SumVoLTEErabIncomingHoSuccNbr)) * 100.
VoLTEDLQualityDefectRate = (SumVoLTEDLQualityDefect / The number of DL Quality
(SumVoLTEEstabInitSuccNbr + SumVoLTEEstabAddSuccNbr + Defect rate
SumVoLTEErabIncomingHoSuccNbr)) * 100.
VoLTEIntraHoSuccessRate = (SumVoLTEIntraEnbSucc / The number of VoLTE HO
SumVoLTEIntraEnbAtt) * 100. Intra Success rate
VoLTEX2HoSuccessRate = (SumVoLTEInterX2OutSucc / The number of VoLTE HO X2
SumVoLTEInterX2OutAtt) * 100. Success rate
VoLTES1HoSuccessRate = (SumVoLTEInterS1OutSucc / The number of VoLTE HO S1
SumVoLTEInterS1OutAtt) * 100. Success rate
TTIB_TIME
It measures average holding time of the TTIB activated duration per UE and
percentage of Total TTIB Activated duration in Total RRC Holding Time per UE.
Name Description
TtibActTimeAvg = TtibActTimeTot / TtibActTimeCnt Average holding time of the
TTIB activated duration per
UE
TtibActTimeRate = (TtibActTimeTot / (SumReleaseCallHoldingTimeTot * Percentage of Total TTIB
1000)) * 100 Activated duration in Total
RRC Holding Time
SYSTEM OPERATION
How to Activate

Confidential
Key Parameters
Counters and KPIs

Refer to LTE eNB Counter Description.
REFERENCE
[1] LTE eNB Counter Description
[2] 3GPP TS 32.450: Key performance indicators: Definitions.
[3] 3GPP TS 32.425: Performance measurements.
[4] 3GPP TS 32.404: Performance measurements: Definitions and templates.

Confidential
LTE-OM9101, L1 and L2 Counters

INTRODUCTION
Layer 1 (L1) and Layer 2 (L2) counters provide data for statistical analysis at PHY
/ MAC layers. This data is used to monitor E-UTRAN performance. Some of these
counters are defined in TS32.425 while others are specific to Samsung. This
feature provides a brief introduction to counters. Only the counters which are
visible to operators and are collected at PHY / MAC layers are included in this
feature. For detailed information about all available counters, refer to Samsung
LTE system counter description manual.
BENEFIT
The operator can get data to perform statistical analysis related to the following:
• Air MAC/RLC performance
• Radio resource utilization
• Random access performance
• HARQ and AMC performance
• Received/transmitted signal power
• MAC/RLC features
DEPENDENCY
LIMITATION
None
SYSTEM IMPACT
FEATURE DESCRIPTION
AIR MAC/RLC STATISTICS

AIR_MAC_BYTES
Index: cNum
Name Description
AirMacByteUl The sum of the size of the MAC PDU successfully received via PUSCH

Confidential
Name Description
AirMacTtiUl The sum of sections that have the MAC PDU successfully received via
PUSCH during the statistics period.
AirMacUlThru Average size per second of the MAC PDU successfully received via
PUSCH.
AirMacUlEfctivThru Average size of the MAC PDU of the section successfully received via
AirMacByteDl The sum of the size of the DCCT/DTCH MAC PDU that received HARQ
ACK among the MAC PDU transmitted via PDSCH during the statistics
period.
AirMacTtiDl The sum of sections that have the MAC PDU successfully transmitted via
PDSCH during the statistics period.
AirMacDlThru Average size per second of the DCCT/DTCH MAC PDU that received
HARQ ACK among the MAC PDU transmitted via PDSCH during the
statistics period.
AirMacDlEfctivThru Average size of the MAC PDU of the section successfully transmitted via
AirMacUlThruMin Minimum of the average size per second of the MAC PDU successfully
received via PUSCH
AirMacUlThruMax Maximum of the average size per second of the MAC PDU successfully
received via PUSCH
AirMacDlThruMin Minimum of the average size per second of the DCCT/DTCH MAC PDU
that received HARQ ACK among the MAC PDU transmitted via PDSCH
AirMacDlThruMax Maximum of the average size per second of the DCCT/DTCH MAC PDU
ULIpThruVol The cumulated number that indicates the sum of the sizes of MAC SDUs
that were successfully received through the PUSCH during the sample
intervals of all UEs in the collection interval.
ULIpThruTime The cumulated number of TTIs during the sample intervals of all UEs in the
ULIpThruAvg The calculated number that indicates the average per second size which is
derived from that the MAC SDUs that were successfully received through
the PUSCH during the sample intervals of all UEs is divided by TTIs during
the sample intervals in the collection interval.
AIR_MAC_BYTES_PLMN
Index: PLMN, cNum
Name Description
PLMNAirMacULByte The sum of the size of the MAC PDU successfully received via PUSCH
PLMNAirMacULTti The sum of sections that have the MAC PDU successfully received via
PLMNAirMacULThruAvg Average size per second of the MAC PDU successfully received via
PUSCH.
PLMNAirMacULEfctivThruAvg Average size of the MAC PDU of the section successfully received via
PLMNAirMacDLByte The sum of the size of the DCCT/DTCH MAC PDU that received HARQ
period.

Confidential
Name Description
PLMNAirMacDLTti The sum of sections that have the MAC PDU successfully transmitted via
PLMNAirMacDLThruAvg Average size per second of the DCCT/DTCH MAC PDU that received
statistics period.
PLMNAirMacDLEfctivThruAvg Average size of the MAC PDU of the section successfully transmitted via
PLMNAirMacULThruMin Minimum of the average size per second of the MAC PDU successfully
received via PUSCH
PLMNAirMacULThruMax Maximum of the average size per second of the MAC PDU successfully
received via PUSCH
PLMNAirMacDLThruMin Minimum of the average size per second of the DCCT/DTCH MAC PDU
PLMNAirMacDLThruMax Maximum of the average size per second of the DCCT/DTCH MAC PDU
AIR_MAC_BYTES_PCELL
Index: cNum
Name Description
AirMacULByte The sum of the size of the MAC PDU successfully received via PUSCH
AirMacULTti The sum of sections that have the MAC PDU successfully received via
PUSCH during the statistics period
AirMacULThruAvg Average size per second of the MAC PDU successfully received via
PUSCH
AirMacULEfctivThruAvg Average size of the MAC PDU of the section successfully received via
AirMacDLByte The sum of the size of the DCCT/DTCH MAC PDU that received HARQ
period
AirMacDLTti The sum of sections that have the MAC PDU successfully transmitted via
AirMacDLThruAvg Average size per second of the DCCT/DTCH MAC PDU that received
statistics period
AirMacDLEfctivThruAvg Average size of the MAC PDU of the section successfully transmitted via
AirMacULByteCurr The most recently collected AirMacByteUl value
AirMacDLByteCurr The most recently collected AirMacDLByte value
AirMacULThruMin Minimum of the average size per second of the MAC PDU successfully
received via PUSCH
AirMacULThruMax Maximum of the average size per second of the MAC PDU successfully
received via PUSCH
AirMacDLThruMin Minimum value of average size per second of the DCCT/DTCH MAC PDU

Confidential
Name Description
AirMacDLThruMax Maximum value of average size per second of the DCCT/DTCH MAC PDU
AIR_MAC_BYTES_SCELL
Index: cNum
Name Description
AirMacULByte The sum of the size of the MAC PDU successfully received via PUSCH
AirMacULTti The sum of sections that have the MAC PDU successfully received via
AirMacULThruAvg Average size per second of the MAC PDU successfully received via
PUSCH.
AirMacULEfctivThruAvg Average size of the MAC PDU of the section successfully received via
AirMacDLByte The sum of the size of the DCCT/DTCH MAC PDU that received HARQ
period
AirMacDLTti The sum of sections that have the MAC PDU successfully transmitted via
AirMacDLThruAvg Average size per second of the DCCT/DTCH MAC PDU that received
statistics period
AirMacDLEfctivThruAvg Average size of the MAC PDU of the section successfully transmitted via
AirMacULByteCurr The most recently collected AirMacByteUl value
AirMacDLByteCurr The most recently collected AirMacDLByte value
AirMacULThruMin Minimum of the average size per second of the MAC PDU successfully
received via PUSCH
AirMacULThruMax Maximum of the average size per second of the MAC PDU successfully
received via PUSCH
AirMacDLThruMin Minimum value of average size per second of the DCCT/DTCH MAC PDU
AirMacDLThruMax Maximum value of average size per second of the DCCT/DTCH MAC PDU
AIR_RLC_BYTES
Index: cNum, QCI
Name Description
AirRlcULByte Number of bytes transmitted at the RLC as air uplink. Collects the number
of data bytes received by the UE for each cell and QCI.
AirRlcDLByte Number of bytes transmitted at the RLC as air downlink. Collects the
number of data bytes transmitted to the UE for each cell and QCI.

Confidential
Name Description
AirRlcDLByteRe Number of bytes retransmitted at the RLC as air downlink. Collects the
number of data bytes transmitted to the UE for each cell and QCI.
AirRlcULThru Collects the data received from the UE as the air uplink throughput for
each cell and QCI.
AirRlcDLThru Collects the data transmitted to the UE as the air downlink throughput for
each cell and QCI.
IpThru Collects the IP throughput for each cell and QCI using the method
specified in 3GPP TS 32.450.
AirRlcULThruMin Minimum air uplink throughput
AirRlcULThruMax Maximum air uplink throughput
AirRlcDLThruMin Minimum air downlink throughput
AirRlcDLThruMax Maximum air downlink throughput
IpThruMin Minimum IP throughput
IpThruMax Maximum IP throughput
IpThruThpVoDLByte Numerator of IpThru calculation
IpThruThpDLTime Denominator of IpThru calculation
AIR_RLC_BYTES_PLMN
Index: cNum, QCI
Name Description
PLMN0AirRlcULByte Number of bytes transmitted from the RLC as air uplink. Collects the
number of data bytes received by the UE for each cell, QCI, and PLMN.
⋮ ⋮
PLMN5AirRlcULByte Number of bytes transmitted from the RLC as air uplink. Collects the
PLMN0AirRlcDLByte Number of bytes transmitted from the RLC as air downlink. Collects the
⋮ ⋮
PLMN5AirRlcDLByte Number of bytes transmitted from the RLC as air downlink. Collects the
PLMN0AirRlcDLByteRe Number of bytes retransmitted from the RLC as air downlink. Collects the
number of data bytes transmitted to the UE for each cell, QCI, and PLMN.
⋮ ⋮
PLMN5AirRlcDLByteRe Number of bytes retransmitted from the RLC as air downlink. Collects the
number of data bytes transmitted to the UE for each cell, QCI, and PLMN.
PLMN0AirRlcULThru Collects the data received from the UE as the air uplink throughput for each
cell, QCI, and PLMN.
⋮ ⋮
PLMN5AirRlcULThru Collects the data received from the UE as the air uplink throughput for each
cell, QCI, and PLMN.
PLMN0AirRlcDLThru Collects the data received from the UE as the air downlink throughput for
each cell, QCI, and PLMN.
⋮ ⋮
PLMN5AirRlcDLThru Collects the data received from the UE as the air downlink throughput for
each cell, QCI, and PLMN.
PLMN0AirRlcULThruMin Minimum air uplink throughput

Confidential
Name Description
⋮ ⋮
PLMN5AirRlcULThruMin Minimum air uplink throughput
PLMN0AirRlcULThruMax Maximum air uplink throughput
⋮ ⋮
PLMN5AirRlcULThruMax Maximum air uplink throughput
PLMN0AirRlcDLThruMin Minimum air downlink throughput
⋮ ⋮
PLMN5AirRlcDLThruMin Minimum air downlink throughput
PLMN0AirRlcDLThruMax Maximum air downlink throughput
⋮ ⋮
PLMN5AirRlcDLThruMax Maximum air downlink throughput
RADIO RESOURCE UTILIZATION

PRB_QCI
Index: cNum, QCI
Name Description
PrbDl The PRB usage used as the downlink DTCH traffic
PrbUl The PRB usage used as the uplink DTCH traffic
PRB_TOTAL
Index: cNum
Name Description
TotPrbDLAvg The resource used for the PDSCH/PDCCH transmission among the total
downlink resource
TotGbrPrbDLAvg Ratio of the resource used to transmit the GBR traffic against the total
downlink resources.
TotNGbrPrbDLAvg Ratio of the resource used to transmit the non-GBR traffic against the total
downlink resources.
TotPrbULAvg The resource used for the PUSCH transmission among the total uplink
resource
TotGbrPrbULAvg Ratio of the resource used to transmit the GBR traffic against the total
uplink resources.
TotNGbrPrbULAvg Ratio of the resource used to transmit the non-GBR traffic against the total
uplink resources.
TotPucchPrbULAvg The resource used for the PUCCH transmission among the total uplink
resource
TotPucchPuschPrbULAvg The resource used for the PUCCH/PUSCH transmission among the total
uplink resource
TotNgbrSCellPrbDLAvg Ratio of the resource used to transmit the non-GBR traffic of SCell against
the total downlink resources.
TotPrbDLMin The minimum value of TotPrbDLAvg
TotPrbDLMax The maximum value of TotPrbDLAvg
TotPrbULMin The minimum value of TotPrbULAvg

Confidential
Name Description
TotPrbULMax The maximum value of TotPrbULAvg
PRB_TOTAL_PLMN
Index: PLMN, cNum
Name Description
TotPrbDl_PLMN Ratio of resource used for PDSCH/PDCCH transmission against the total
PLMN downlink resource available.
TotPrbDlMin_PLMN Minimum value of PLMNTotPrbDLAvg
TotPrbDlMax_PLMN Maximum value of PLMNTotPrbDLAvg
TotPrbUl_PLMN Ratio of resource used for PUSCH reception against the total PLMN uplink
resource available.
TotPrbUlMin_PLMN Minimum value of PLMNTotPrbULAvg
TotPrbUlMax_PLMN Maximum value of PLMNTotPrbULAvg
PRB_TOTAL_DL_COMP
Index: cNum
Name Description
TotCoMPPrbDLAvg The average number of DL PRB usage allocated for CoMP UEs in
neighbor cells while DL CoMP ON.
TotCoMPPrbDLUsed The cumulated number of DL PRBs allocated for CoMP UEs in neighbor
cells while DL CoMP ON.
TotPrbDLAvailable The cumulated number of PRBs available for DL.
TTIB_MAC
Index: cNum
Name Description
TotTtibPrbULAvg The average number of PRB usage used for UL Sub-frame Bundling
mode.
TotTtibPrbULUsed The cumulated number of PRBs used for UL Sub-frame Bundling.
TotPuschPrbULAvailable The cumulated number of PUSCH PRBs Available for UL.
PRB_VOLTE
Index: cNum
Name Description
TotQCI1PrbULUsed The cumulated number of QCI1 PRBs
TotTtibQCI1PrbULUsed The cumulated number of QCI1 PRBs used for UL Sub-frame Bundling.
PRB_CAT1
Index: cNum
Name Description
Cat1PrbDLNum The cumulated number of downlink PRBs used for Category 1 UEs.
AvailPrbDLNum The cumulated number of PRBs available for the downlink during the
Cat1PrbDLAvg The average use rate for downlink PRBs used for Category 1 UEs.

Confidential
Name Description
Cat1PrbULNum The cumulated number of uplink PRBs used for Category 1 UEs.
AvailPrbULNum The cumulated number of PRBs available for the uplink during the
Cat1PrbULAvg The average use rate for uplink PRBs used for Category 1 UEs.
RRU_MEAS_NEW
Index: cNum
Name Description
RruCceUsageDistDL1 Aggregation level1 of PDCCH DL grant
RruCceUsageDistUL1 Aggregation level1 of PDCCH UL grant
RruCceAllocationFailDLAvg The CCE allocation fail ratio of PDCCH DL grant
RruCceAllocationFailULAvg The CCE allocation fail ratio of PDCCH UL grant
RruPrbDLPcchAvg PCCH PRB Usage
RruPrbDLSrbAvg Downlink SRB (CCCH/DCCH) PRB Usage
RruPrbULSrbAvg Uplink SRB (CCCH/DCCH) PRB Usage
PDCCH
Index: cNum
Name Description
Cfi1 The number of used CFI1
PDCCHCceUsedAgg1 The number of used aggregation level 1 for allocating PDCCH CCE
PDCCHCcePerUser The average number of allocated CCE per UE
SCHE_UE_NUMBER
Index: cNum
Name Description
DLScheduledTTINum The cumulated number of subframes in which the number of the
downlink scheduled UEs is larger than 0.
DLScheduledUEperTTIMin The minimum number of downlink scheduled UEs
DLScheduledUEperTTIMax The maximum number of downlink scheduled UEs
DLScheduledUEAvg The average number of scheduled UEs per downlink scheduled
subframes

Confidential
Name Description
DLScheduledUEAvg0 The average number of scheduled UEs per downlink subframes
DLScheduledUENum The cumulated number of scheduled UEs
DLTTINum The cumulated number of downlink subframes
DLScheduledUEperTTIMinCnt The collection count of DLScheduledUEperTTIMin
DLScheduledUEperTTIMaxCnt The collection count of DLScheduledUEperTTIMax
ULScheduledTTINum The cumulated number of subframes in which the number of the uplink
scheduled UEs is larger than 0.
ULScheduledUEperTTIMin The minimum number of uplink scheduled UEs
ULScheduledUEperTTIMax The maximum number of uplink scheduled UEs
ULScheduledUEAvg The average number of scheduled UEs per uplink scheduled subframes
ULScheduledUEAvg0 The average number of scheduled UEs per uplink subframes
ULScheduledUENum The cumulated number of scheduled UEs
ULTTINum The cumulated number of uplink subframes
ULScheduledUEperTTIMinCnt The collection count of ULScheduledUEperTTIMin
ULScheduledUEperTTIMaxCnt The collection count of ULScheduledUEperTTIMax
POWER_HEADROOM
Index: cNum
Name Description
PhrIndex0 The cumulated count that PhrIndex0 is received
⋮ ⋮
RANDOM ACCESS
RA
Index: cNum
Name Description
HighSpeedMonitoring The number of UEs which are monitored for moving speed
NoofHighSpeed The number of high speed UEs which are monitored
DedicatedPreambles The number of detected dedicated preambles.
DedicatedPreambleAssignFail The number of failures to get dedicated preamble allocation after
requesting the dedicated preamble from the RRC to the MAC
RandomlyselectedpreamblesLow The number of the preambles belonging to Group A among the
detected contention based preambles
RandomlyselectedpreamblesHigh The number of the preambles belonging to Group B among the
detected contention based preambles
RACHUsageAvg Average number of detected preambles
HandoverDedicatedPreambles The cumulated number of dedicated preambles due to HO order among
the periodically collected RACH preambles.
RandomAccessResponses The cumulated number of RandomAccessResponse (RAR) messages
transmitted. For this counter, the statistics are collected periodically.

Confidential
TA
Index: cNum
Name Description
TimeAdvanceSection0 Distance (meter): 0~200, 16TS: from 0 to 2.
TimeAdvanceSection1 Distance (meter): 201~400, 16TS: from 3 to 5.
⋮ ⋮
TimeAdvanceSection30 Distance (meter): 60001~, 16TS: from 768 onwards.
DATA RADIO BEARER STATISTICS

ACTIVE_UE
Index: cNum, QCI
Name Description
UEActiveDl The number of UEs satisfying one or more of the following conditions in a
continuous 20 ms interval (sampling occasion) is summed every 80 ms for
each QCI.
• If there is a DRB which received a buffer occupancy Request from the
RLC
• If there is a DRB which received an HARQ retransmission Request When
a collection interval ends, the average is calculated by dividing the
summed number of UEs by the number of sampling occasions that
occurred.
UEActiveDlTot Sum of UEActiveDLAvg collected
UEActiveUl The number of UEs satisfying one or more of the following conditions in a
continuous 20 ms interval is summed every 80 ms for each QCI.
• If there is a DRB where the uplink data requested to be allocated using
the Buffer Status Report message is waiting
• If there is a DRB which received an HARQ retransmission request When
a collection interval ends, the average is calculated by dividing the
summed number of UEs by the number of sampling occasions that
occurred.
UEActiveUlTot Sum of UEActiveULAvg collected
SumActiveUEDL This counter is the cumulated number per every TTI of DL DRB for each
QCI which receives a buffer occupancy request from the RLC or which has
received a HARQ retransmission request during the sampling period.
SumActiveUEUL This counter is the cumulated number per every TTI of UL DRB for each
QCI where the uplink data requested to be allocated using the Buffer
Status Report message is waiting or which received an HARQ
retransmission request.
UEActiveDLMax The maximum number of DL active UEs for each QCI during the collection
interval.
UEActiveULMax The maximum number of UL active UEs for each QCI during the collection
interval.
IP_LATENCY
Index: cNum, QCI
Name Description
IpLateDL IP Latency in the downlink collected at bearer level
IpLateDLTot Time difference between reception time of IP packet and the time when the

Confidential
Name Description
eNodeB transmits the first block to UE
IpLateDLCnt Number of samples (defined in 3GPP TS 32.450)
PDCP_DELAY
Index: cNum, QCI
Name Description
PdcpSduDelayAvg Average DL PDCP SDU delay
PdcpSduDelayTot Total PDCP SDU delay
PdcpSduDelayCnt Number of PDCP SDUs for which PDCP SDU delay was collected
PDCP_DROP
Index: cNum, QCI
Name Description
PdcpSduDropRateDL The calculated packet drop rate of downlink DRB Packet which is received
in the PDCP
PdcpPduDropRateDL The calculated average DL PDCP SDU drop rate.
ERAB_SESSION_UE
Index: cNum
Name Description
SessionTimeUEAvg Average in-session time per UE
SessionTimeUETot Sum of SessionTimeUEAvg collected
ERAB_SESSION_QCI
Index: cNum, QCI
Name Description
SessionTimeQciAvg Average in-session time per QCI
SessionTimeQciTot Sum of SessionTime SessionTimeQciAvg collected
HYBRID ARQ
DL_HARQ_TRANSMISSION
Index: cNum
Name Description
DLResidualBlerRetrans0 PDSCH BLER for the initial HARQ transmission during the collection
interval. It is the failure rate for the initial transmission and is a ratio of the
number of times the first re-transmission was carried out to the number of
times the initial transmission was carried out.
⋮ ⋮
DLResidualBlerRetrans6 PDSCH BLER for the sixth HARQ retransmission
DLResidualBlerRetransMin The minimum PDSCH HARQ transmission number among which have
positive value between DLResidualBlerRetrans0 and
DLResidualBlerRetrans6. HARQ transmission number denotes 'X' in that
'Xth HARQ retransmission'.

Confidential
Name Description
DLResidualBlerRetransMax The maximum PDSCH HARQ transmission number among which have
positive value between DLResidualBlerRetrans0 and
DLResidualBlerRetrans6. HARQ transmission number denotes 'X' in that
DLResidualBlerRetransAvg Total PDSCH BLER for initial HARQ transmissions. It is the ratio of sum of
PDSCH HARQ retransmissions count to the counts of initial transmissions.
DLResidualBlerRetransNak The failure rate of PDSCH initial HARQ transmissions after the maximal
HARQ retransmission occurs. It is the ratio of the counts of transmission
failures after the maximal HARQ retransmissions to the counts of initial
transmissions.
DLTransmissionRetrans0 The cumulated number of the first PDSCH HARQ retransmissions
⋮ ⋮
DLTransmissionRetrans6 The cumulated number of the sixth PDSCH HARQ retransmissions
DLTransmissionNackedRetrans The cumulated number of PDSCH HARQ retransmission failures after the
maximal HARQ retransmission occurs.
UL_HARQ_TRANSMISSION
Index: cNum
Name Description
ULResidualBlerRetrans0 PUSCH BLER for the initial HARQ transmission during the collection
interval. It is the failure rate for the initial transmission and is a ratio of the
number of times the first re-transmission was carried out to the number of
times the initial transmission was carried out.
⋮ ⋮
ULResidualBlerRetrans27 PUSCH BLER for the twenty seventh HARQ retransmission
ULResidualBlerRetransMin The minimum PUSCH HARQ transmission number among which have
positive value between ULResidualBlerRetrans0 and
ULResidualBlerRetrans27. HARQ transmission number denotes 'X' in that
ULResidualBlerRetransMax The maximum PUSCH HARQ transmission number among which have
positive value between ULResidualBlerRetrans0 and
ULResidualBlerRetrans27. HARQ transmission number denotes 'X' in that
ULResidualBlerRetransAvg Total PUSCH BLER for initial HARQ transmissions. It is the ratio of sum of
PUSCH HARQ retransmissions count to the counts of initial transmissions.
ULResidualBlerRetransNak The failure rate of PUSCH initial HARQ transmissions after the maximal
HARQ retransmission occurs. It is the ratio of the counts of transmission
failures after the maximal HARQ retransmissions to the counts of initial
transmissions.
ULTransmissionRetrans0 The cumulated number of initial PUSCH HARQ transmissions
⋮ ⋮
ULTransmissionRetrans27 The cumulated number of twenty seventh PUSCH HARQ retransmissions
ULTransmissionNackedRetrans The cumulated number of PUSCH HARQ retransmission failures after the
maximal HARQ retransmission occurs.

Confidential
VOLTE_HARQ
Index: cNum
Name Description
DLVoLTEHARQFail The cumulated number that downlink transmission for the VoLTE (QCI=1)
bearer established UE fails after maximal HARQ retransmissions during
DLVoLTEHARQSucc The cumulated number that downlink transmission for the VoLTE (QCI=1)
bearer established UE succeeds during collection interval.
DLVoLTEHARQFailRate This counter is failure rate of downlink for the VoLTE (QCI=1) bearer
established UE.
ULVoLTEHARQFail The cumulated number that uplink transmission for the VoLTE (QCI=1)
bearer established UE fails after maximal HARQ retransmissions during
ULVoLTEHARQSucc The cumulated number that uplink transmission for the VoLTE (QCI=1)
bearer established UE succeeds during collection interval.
ULVoLTEHARQFailRate This counter is failure rate of uplink for the VoLTE (QCI=1) bearer
established UE.
MIMO
Index: cNum, DL Layer
Name Description
PdschBLERperLayer PDSCH BLER for each layer
PuschBLERperLayer PUSCH BLER for each layer
MCS
Index: cNum
Name Description
PdschBLERperMCS0 PDSCH BLER transmitted to MCS 0
⋮ ⋮
PuschBLERperMCS0 PUSCH BLER received from MCS 0
⋮ ⋮
UlReceivedMCS0 The number of times PUSCH of MCS 0 is received
⋮ ⋮
DlSchedulerMCS0 The number of PRBs assigned to PDSCH MCS 0
⋮ ⋮

Confidential
Name Description
UlSchedulerMCS0 The number of PRBs assigned to PUSCH MCS 0
⋮ ⋮
DL_ACK_NACK_DTX_RATIO
Index: cNum, DL Layer, codeword, status
Name Description
DlreceivedAckNackDtxRatio ACK, NACK, DTX ratio
ADAPTIVE MODULATION AND CODING

DL_MCS
Index: cNum, DL Layer, codeword, status
Name Description
DlTransmittedMCS0 The number of times that MCS 0 PDSCH is transmitted per layer/
codeword
codeword
⋮ ⋮
codeword
codeword
DL_LAYER
Index: cNum, DL Layer
Name Description
DlTransmittedLayer Transmission counts per layer for PDSCH
DL_CQI_NEW
Index: cNum, DL Layer, codeword
Name Description
DlReceivedCQIAvg Average value of DL received CQI
DlReceivedCQI0 The number of times that CQI 0 is received per layer/codeword
⋮ ⋮
DlReceivedCQIMin Minimum value of DLReceivedCQI

Confidential
Name Description
DlReceivedCQIMax Maximum value of DLReceivedCQI
CQIErase Number of times layer / codeword CQI is erased
DL_CQI_NEW_PCELL
Name Description
DLReceivedCQI0 Number of receiving CQI 0 for a wideband CQI per layer/codeword
transmitted from CA UE whose the cell is PCell
⋮ ⋮
DLReceivedCQIMin The minimum value of DlReceivedCQI received from CA UE whose cell is
PCell
DLReceivedCQIMax The maximum value of DlReceivedCQI received from CA UE whose cell is
PCell
DLReceivedCQIAvg The average value of DlReceivedCQI received from CA UE whose cell is
PCell
CQIErase Number of times that CQI erase per layer/codeword is received from CA
UE whose cell is PCell
DL_CQI_NEW_SCELL
Name Description
transmitted from CA UE whose the cell is SCell
⋮ ⋮
DLReceivedCQIMin The minimum value of DlReceivedCQI transmitted from CA UE whose the
cell is SCell
DLReceivedCQIMax The maximum value of DlReceivedCQI transmitted from CA UE whose the
cell is SCell
DLReceivedCQIAvg The average value of DlReceivedCQI transmitted from CA UE whose the
cell is SCell
CQIErase Number of times that CQI erase per layer/codeword is received from CA
UE whose cell is SCell

Confidential
DL_VOLTE_CQI
Index: cNum
Name Description
DLVoLTECQI0 The cumulated number per layer/codeword that CQI 0 is received from the
VoLTE (QCI=1) bearer established UE
⋮ ⋮
DLVoLTECQI15 The cumulated number per layer/codeword that CQI 15 is received from
the VoLTE (QCI=1) bearer established UE
DLVoLTECQIErase The cumulated number per layer/codeword that CQI erase is received from
the VoLTE (QCI=1) bearer established UE
DLVoLTECQIMin The minimum value of DLVoLTECQI0 ~ DLVoLTECQI15
DLVoLTECQIMax The maximum value of DLVoLTECQI0 ~ DLVoLTECQI15
DLVoLTECQIAvg The average value of DLVoLTECQI0 ~ DLVoLTECQI15
DL_PMI
Index: cNum
Name Description
DlReceivedPMI0 The number of times that PMI 0 is received
⋮ ⋮
DL_RI
Index: cNum
Name Description
DlReceivedRIAvg Average value of DL received RI
DlReceivedRI0 Reserved
DlReceivedRI1 The number of times that RI 1 is received
CARRIER AGGREGATION
CA_ACT_DEACT
Index: cNum
Name Description
SCellActivation Count of activations (SCell)
SCellDeactivation_TO Count of SCell deactivation occurrences by reason: When deactivation
timer expires (SCell)
SCellDeactivation_Mismatch Count of SCell deactivation occurrence by reason: When CA status of eNB
and that of the UE are different (SCell)
CRNTIcollision The number of Scell Activation fail due to C-RNTI collision (The C-RNTI of

Confidential
Name Description
UE, who requests Scell activation to SCell, is already used in SCell)
SCellActUEAvg The average number of Scell activated Ues
RECEIVED SIGNAL POWER STATISTICS

POWER
Index: cNum
Name Description
InterferencePower Average interference over thermal noise for each PRB
ThermalNoisePower Average Thermal Noise
RssiOverPath Average RSSI for each antenna
RssiPath0 Average RSSI of Antenna #0
RssiPath1 Collected RssiPath0Avg count
DL_ICIC_RNTP
Index: cNum
Name Description
UnresTxPowerAvg The average number of PRBs with unrestricted TX power for RNTP per
PRB during the collection interval.
UnresTxPowerCount The total number of PRBs with unrestricted TX power during the collection
interval.
RNTPCount The number of RNTP per PRB during the collection interval.
UnresTxPowerMaxPerRNTP The maximum number of PRBs with unrestricted TX power for RNTP per
UnresTxPowerMinPerRNTP The minimum number of PRBs with unrestricted TX power for RNTP per
UnresTxPowerMaxPerRNTPC The cumulated update count of UnresTxPowerMaxPerRNTP.
UnresTxPowerMinPerRNTPC The cumulated update count of UnresTxPowerMinPerRNTP.
RSSI_PATH
Index: cNum, RSSIPath
Name Description
RssiPathAvg The average value of RSSI for each path
RssiPathMax The maximum value of RSSI for each path
RssiPathCurr The most recently collected RSSI values for each path
RssiPathTot Sum of RSSI values for each path
RssiPathCnt RSSI values collection count for each path
RssiPathMin The minimum value of RSSI for each path

Confidential
IOT_9LEVEL
Index: cNum, 9Level
Name Description
PRB0 IoT Level Count for PRB0
⋮ ⋮
UL_SINR_DISTRIBUTION
Index: cNum
Name Description
SinrDistULWbPreComp_Bin0 Uplink SINR Bin0(-10~-8dB) count before Outer-loop compensation
SinrDistULWbPreComp_Bin1 Uplink SINR Bin1(-8~-6dB) count before Outer-loop compensation
⋮ ⋮
SinrDistULWbPreComp_Bin18 Uplink SINR Bin18(26~28) count before Outer-loop compensation
SinrDistULWbPreComp_Bin19 Uplink SINR Bin19(28~30) count before Outer-loop compensation
SinrDistULWbPostComp_Bin0 Uplink SINR Bin0(-10~-8dB) count after Outer-loop compensation
SinrDistULWbPostComp_Bin1 Uplink SINR Bin1(-8~-6dB) count after Outer-loop compensation
⋮ ⋮
SinrDistULWbPostComp_Bin18 Uplink SINR Bin18(26~28dB) count after Outer-loop compensation
SinrDistULWbPostComp_Bin19 Uplink SINR Bin19(28~30dB) count after Outer-loop compensation
UL_VOLTE_SINR_DISTRIBUTION
Index: cNum
Name Description
ULVoLTESinrDistPreCompBin0 The cumulated number of uplink SINR of the VoLTE (QCI=1) bearer
established UE is in Bin0(-10~-8dB) before Outer-loop compensation
⋮ ⋮
ULVoLTESinrDistPreCompBin1 The cumulated number of uplink SINR of the VoLTE (QCI=1) bearer
9 established UE is in Bin0 (28~30dB) before Outer-loop compensation
ULVoLTESinrDistPostCompBin0 The cumulated number of uplink SINR of the VoLTE (QCI=1) bearer
established UE is in Bin0 (-10~-8dB) after Outer-loop compensation
⋮ ⋮
ULVoLTESinrDistPostCompBin1 The cumulated number of uplink SINR of the VoLTE (QCI=1) bearer
9 established UE is in Bin19 (28~30dB) after Outer-loop compensation
PUCCH_SINR_DISTRIBUTION
Index: cNum
Name Description
PUCCHSinrDistBin0 The cumulated number of PUCCH SINR Bin0 (-10~-8dB).
PUCCHSinrDistBin1 The cumulated number of PUCCH SINR Bin1 (-8~-6dB).
⋮ ⋮
PUCCHSinrDistBin19 The cumulated number of PUCCH SINR Bin19 (28~30dB).

Confidential
PUSCH_TX_POWER
Index: cNum
Name Description
PhrRxCount This counter is cumulated by 1 when PHR is received.
TxPowerSum This counter is cumulated by the PUSCH Tx Power when PHR is received.
PowerLimitCount This counter is cumulated by 1 if (PHR index - 23) is less than 0 when PHR
is received.
AveragePuschTxPower Average PUSCH transmission power
PowerShortageRatio Percentage of received PHRs with PHR index - 23 < 0.
PUCCH_INTERFERENCE_POWER
Index: cNum
Name Description
PucchInterferencePowerAvg The average value of interference power per PRB in the PUCCH region.
TRANSMITTED SIGNAL POWER STATISTICS

PA_BIAS_MODE
Index: cNum
Name Description
PaBiasModeTime The counter is the energy saving time by PA Bias mode.
DL_MIMO_TX_PATH_OFF_MODE
Index: cNum
Name Description
DLMimoTxPathOffModeTime The counter is the energy saving time by DL MIMO Tx Branch Off mode.
FEATURE-SPECIFIC STATISTICS
SPS_MAC
Index: cNum
Name Description
ULSpsActivationAtt The cumulated count that UL SPS activation attempts transmitted to UE
through PDCCH
ULSpsDeactivationAtt The cumulated count that UL SPS deactivation attempts transmitted to UE
through PDCCH

Confidential
UL_COMP_JR
Index: cNum
Name Description
ULCoMPActivatedUEperTti The average number of uplink CoMP activated UEs per uplink subframes
TotULCoMPActivatedUE The cumulated number of uplink CoMP activated UEs during collection
interval.
TotULTti The cumulated number of uplink subframes during collection interval.
UL_MU_MIMO
Index: cNum
Name Description
ULMuMimoTtiUsage The ratio of uplink MU-MIMO utilized subframes
ULMuMimoPairedUEperTti The average number of uplink MU-MIMO utilized UEs per uplink MU-MIMO
utilized subframes
TotULMuMimoUtilizedTti The cumulated number of uplink MU-MIMO utilized subframes during
TotULTti The cumulated number of uplink subframes during collection interval.
TotULMuMimoPairedUE The cumulated number of uplink MU-MIMO utilized UEs during collection
interval.
PAGING
Index: cNum
Name Description
DiscardedNbr Paging record count discarded in the eNB
AttPaging Paging transmission attempt count
SYSTEM OPERATION
How to Activate
This feature is basically enabled.
The statistical data are collected during the eNB operation and transmitted to the
LSM.
Key Parameters
Counters and KPIs

For detailed information about all available counters, refer to LTE Counter
Description manual.

Confidential
REFERENCE
[1] LTE Counter Description.
[2] 3GPP TS 32.450: Key performance indicators: Definitions.
[3] 3GPP TS 32.425: Performance measurements.
[4] 3GPP TS 32.404: Performance measurements: Definitions and templates.
■

802 eNB (LTE)
Feature Description for SLR 7.0.2_2
Document Version 1.0
© 2018 Samsung Electronics Co., Ltd.

All rights reserved.

ENB (LTE) Feature Description For Release

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ENB (LTE) Feature Description For Release

Uploaded by

Copyright:

Available Formats

802 eNB (LTE)

Document Version 1.0

Document Number: 2600-00LPGMGAP

For questions on the manuals or their content, contact

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 iii

LTE-SW0321, UE Context Management ....................................................................................... 178

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 iv

LTE-SW2003, Idle UE Distribution ................................................................................................ 534

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 v

LTE-ME1001, Variable Number of OFDM Symbols for PDCCH..................................................... 934

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 vi

LTE-SO0301, PCI AutoConfiguration .......................................................................................... 1223

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 vii

Some features, commands, parameters, or counters are not supported by all

Conventions in this Document

Provides information or instructions that you should follow to avoid service

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 viii

File Names and Paths

User Input and Console Screen Output Text

New and Changed Information

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 ix

Types Feature ID, Name

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 x

Organization of This Document

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 xi

Chapter 1 Air Performance

LTE-ME2019, DL SU 2 × 2 MIMO (TM3 and TM4)

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 1

Chapter 1 Air Performance Enhancement

Transmission Mode 3 (DL_MIMO_MODE as 2 (ci_tm3))

Chapter 1 Air Performance Enhancement

Number of Number of CW and Layer mapping Layer Transmission

Transmission Mode 4 (DL_MIMO_MODE as 3 (ci_tm4))

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 3

Chapter 1 Air Performance Enhancement

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 4

Chapter 1 Air Performance Enhancement

Counters and KPIs

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 5

Chapter 1 Air Performance Enhancement

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 6

Chapter 1 Air Performance Enhancement

Interference suppression MRC vector Signal matching

LMMSE Receiver with IRC

estimated channel matrix

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 7

Chapter 1 Air Performance Enhancement

• Interference rejection is achieved by MMSE combining at the eNB receiver.

IRC scheme based on MMSE criterion achieves an optimal balance of noise

Chapter 1 Air Performance Enhancement

Counters and KPIs

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 9

Chapter 1 Air Performance Enhancement

Family Display Name Type Name Type Description

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 10

Chapter 1 Air Performance Enhancement

LTE-ME2022, DL SU 4 × 4 MIMO (TM3 and TM4)

Chapter 1 Air Performance Enhancement

Transmission Mode 3 (DL_MIMO_MODE as 2 (ci_tm3))

2 Only used for retransmission of rank 3

eNB (LTE) Feature Description for SLR 7.0.2_2 v1.0 12

Chapter 1 Air Performance Enhancement

Number of Number CW and Layer Mapping Layer Transmission