ERAN12.1 Feature Description

LTE eRAN12.
1 Feature
Description
Issue 01
Date 2017-03-22
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2017-03-22) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
LTE FDD eRAN12.1 Feature Description
LTE FDD eRAN12.1 Feature Description Contents
Contents
1 LTE Basic Features ........................................................................................................................ 1

1.1 Standards Compliance .................................................................................................................................................. 1
1.1.1 LBFD-001001 3GPP R8 Specifications..................................................................................................................... 1
1.1.2 LBFD-001007 3GPP R9 Specifications..................................................................................................................... 2
1.1.3 LBFD-001008 3GPP R10 Specifications................................................................................................................... 2
1.1.4 LBFD-001009 3GPP R11 Specifications ................................................................................................................... 3
1.1.7 LBFD-001002 FDD mode ......................................................................................................................................... 5
1.1.8 LBFD-001003 Scalable Bandwidth ........................................................................................................................... 6
1.1.9 LBFD-001004 CP length ........................................................................................................................................... 7
1.1.9.1 LBFD-00100401 Normal CP .................................................................................................................................. 7
1.1.10 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM ............................................................ 8
1.1.11 LBFD-001006 AMC ................................................................................................................................................ 9
1.1.12 LBFD-001030 Support of UE Category 2/3/4 ....................................................................................................... 10
1.2 RAN Architecture & Features..................................................................................................................................... 11
1.2.1 LBFD-002001 Logical Channel Management ......................................................................................................... 11
1.2.2 LBFD-002002 Transport Channel Management ...................................................................................................... 12
1.2.3 LBFD-002003 Physical Channel Management ....................................................................................................... 13
1.2.4 LBFD-002004 Integrity Protection .......................................................................................................................... 15
1.2.5 LBFD-002005 DL Asynchronous HARQ ................................................................................................................ 16
1.2.6 LBFD-002006 UL Synchronous HARQ .................................................................................................................. 17
1.2.7 LBFD-002007 RRC Connection Management ........................................................................................................ 18
1.2.8 LBFD-002008 Radio Bearer Management .............................................................................................................. 19
1.2.9 LBFD-002009 Broadcast of system information ..................................................................................................... 20
1.2.10 LBFD-002010 Random Access Procedure ............................................................................................................ 21
1.2.11 LBFD-002011 Paging ............................................................................................................................................ 22
1.2.12 LBFD-002012 Cell Access Radius up to 15km ..................................................................................................... 23
1.2.13 LBFD-002023 Admission Control ......................................................................................................................... 24
1.2.14 LBFD-002024 Congestion Control........................................................................................................................ 25
1.2.15 LBFD-002025 Basic Scheduling ........................................................................................................................... 26
1.2.16 LBFD-002026 Uplink Power Control.................................................................................................................... 27
1.2.17 LBFD-081101 PUCCH Outer Loop Power Control .............................................................................................. 29
Issue 01 (2017-03-22) Huawei Proprietary and Confidential ii

1.2.18 LBFD-002016 Dynamic Downlink Power Allocation ........................................................................................... 30

1.2.19 LBFD-002017 DRX .............................................................................................................................................. 31
1.2.20 LBFD-002018 Mobility Management ................................................................................................................... 32
1.2.20.1 LBFD-00201801 Coverage Based Intra-frequency Handover ............................................................................ 32
1.2.20.2 LBFD-00201802 Coverage Based Inter-frequency Handover ............................................................................ 33
1.2.20.3 LBFD-00201803 Cell Selection and Re-selection .............................................................................................. 35
1.2.20.4 LBFD-00201804 Distance Based Inter-frequency Handover ............................................................................. 36
1.2.20.5 LBFD-00201805 Service Based Inter-frequency Handover ............................................................................... 36
1.2.21 LBFD-002020 Antenna Configuration .................................................................................................................. 37
1.2.21.1 LBFD-00202001 UL 2-Antenna Receive Diversity ........................................................................................... 37
1.2.22 LBFD-002021 Reliability ...................................................................................................................................... 38
1.2.22.1 LBFD-00202101 Main Processing and Transport Unit Cold Backup ................................................................ 38
1.2.22.2 LBFD-00202102 Cell Re-build Between Baseband Processing Units ............................................................ 39
1.2.22.3 LBFD-00202103 SCTP Multi-homing ............................................................................................................... 41
1.2.22.4 LBFD-00202104 Intra-baseband Card Resource Pool (user level/cell level) ..................................................... 42
1.2.23 LBFD-002022 Static Inter-Cell Interference Coordination ................................................................................... 42
1.2.23.1 LBFD-00202201 Downlink Static Inter-Cell Interference Coordination............................................................ 42
1.2.23.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination ................................................................ 43
1.2.24 LBFD-002027 Support of UE Category 1 ............................................................................................................. 44
1.2.25 LBFD-002028 Emergency Call ............................................................................................................................. 46
1.2.26 LBFD-002029 Earthquake and Tsunami Warning System (ETWS) ...................................................................... 47
1.2.27 LBFD-002031 Support of aperiodic CQI reports .................................................................................................. 48
1.2.28 LBFD-002032 Extended-QCI ................................................................................................................................ 49
1.2.29 LBFD-002033 SCTP Congestion Control ............................................................................................................. 50
1.2.30 LBFD-002034 RRU Channel Cross Connection Under MIMO ............................................................................ 51
1.2.31 LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting ............................................................... 53
1.2.32 LBFD-060102 Enhanced UL Frequency Selective Scheduling ............................................................................. 54
1.2.33 LBFD-060103 Enhanced DL Frequency Selective Scheduling ............................................................................. 55
1.2.34 LBFD-070103 Multi-Band Compatibility Enhancement ....................................................................................... 56
1.2.35 LBFD-070101 Uplink Timing Based on PUCCH ................................................................................................. 58
1.2.36 LBFD-070102 MBR>GBR Configuration ............................................................................................................ 58
1.2.37 LBFD-070105 IoT-based PUSCH Power Control ................................................................................................. 59
1.2.38 LBFD-070106 PDSCH Efficiency Improvement .................................................................................................. 60
1.2.39 LBFD-070107 PDCCH Utilization Improvement ................................................................................................. 62
1.2.40 LBFD-081102 PLMN ID Management ................................................................................................................. 63
1.2.41 LBFD-081103 Terminal Awareness Differentiation .............................................................................................. 64
1.2.42 LBFD-081104 UL Compensation Scheduling ....................................................................................................... 64
1.2.43 LBFD-081105 Voice-Specific AMC ...................................................................................................................... 66
1.2.44 LBFD-121102 eRAN12.1 Introduction Package ................................................................................................... 67
1.2.45 LBFD-001015 Enhanced Scheduling .................................................................................................................... 68
1.2.45.1 LBFD-00101501 CQI Adjustment ...................................................................................................................... 68
1.2.45.2 LBFD-00101502 Dynamic Scheduling .............................................................................................................. 69
Issue 01 (2017-03-22) Huawei Proprietary and Confidential iii

1.2.46 LBFD-001027 Active Queue Management (AQM) .............................................................................................. 71

1.2.47 LBFD-001092 CMAS Support .............................................................................................................................. 72
1.3 Transmission & Security............................................................................................................................................. 73
1.3.1 LBFD-003001 Transmission Networking ................................................................................................................ 73
1.3.1.1 LBFD-00300101 Star Topology ........................................................................................................................... 73
1.3.1.2 LBFD-00300102 Chain Topology ........................................................................................................................ 74
1.3.1.3 LBFD-00300103 Tree Topology........................................................................................................................... 75
1.3.2 LBFD-003002 Basic Qos Management ................................................................................................................... 76
1.3.2.1 LBFD-00300201 DiffServ QoS Support .............................................................................................................. 76
1.3.3 LBFD-003003 VLAN Support (IEEE 802.1p/q) ..................................................................................................... 77
1.3.4 LBFD-003004 Compression & Multiplexing over E1/T1 ....................................................................................... 78
1.3.4.1 LBFD-00300401 IP Header Compression ............................................................................................................ 78
1.3.4.2 LBFD-00300402 PPP MUX ................................................................................................................................. 79
1.3.4.3 LBFD-00300403 ML-PPP/MC-PPP ..................................................................................................................... 80
1.3.5 LBFD-003005 Synchronization ............................................................................................................................... 81
1.3.5.1 LBFD-00300501 Clock Source Switching Manually or Automatically ............................................................... 81
1.3.5.2 LBFD-00300502 Free-running Mode ................................................................................................................... 82
1.3.5.3 LBFD-00300503 Synchronization with GPS ....................................................................................................... 83
1.3.5.4 LBFD-00300504 Synchronization with BITS ...................................................................................................... 84
1.3.5.5 LBFD-00300505 Synchronization with 1PPS ...................................................................................................... 85
1.3.5.6 LBFD-00300506 Synchronization with E1/T1 ..................................................................................................... 85
1.3.6 LBFD-003006 IPv4/IPv6 Dual Stack ...................................................................................................................... 86
1.3.7 LBFD-111101 Synchronization with BeiDou .......................................................................................................... 87
1.3.8 LBFD-003007 IP Route Backup .............................................................................................................................. 89
1.3.9 LBFD-001010 Security Mechanism ........................................................................................................................ 89
1.3.9.1 LBFD-00101001 Encryption: AES ....................................................................................................................... 89
1.3.9.2 LBFD-00101002 Encryption: SNOW 3G ............................................................................................................. 90
1.3.9.3 LBFD-00101003 Encryption: ZUC ...................................................................................................................... 91
1.3.10 LBFD-003010 Public Key Infrastructure (PKI) .................................................................................................... 92
1.3.11 LBFD-001018 S1-flex ........................................................................................................................................... 94
1.3.12 LBFD-003012 IP Performance Monitoring ........................................................................................................... 96
1.3.12.1 LBFD-00301201 IP Performance Monitoring .................................................................................................... 96
1.3.12.2 LBFD-00301202 Transport Dynamic Flow Control ........................................................................................... 97
1.3.13 LBFD-002035 Self-configuration .......................................................................................................................... 97
1.4 Operation & Maintenance ......................................................................................................................................... 100
1.4.1 LBFD-004001 Local Maintenance of the LMT ..................................................................................................... 100
1.4.2 LBFD-004002 Centralized U2000 Management ................................................................................................... 101
1.4.3 LBFD-004003 Security Socket Layer ................................................................................................................... 102
1.4.4 LBFD-004004 Software Version Upgrade Management ....................................................................................... 103
1.4.5 LBFD-004005 Hot Patch Management ................................................................................................................. 104
1.4.6 LBFD-004006 Fault Management ......................................................................................................................... 105
1.4.7 LBFD-004007 Configuration Management ........................................................................................................... 106
Issue 01 (2017-03-22) Huawei Proprietary and Confidential iv

1.4.8 LBFD-004008 Performance Management ............................................................................................................. 107

1.4.9 LBFD-004009 Real-time Monitoring of System Running Information ................................................................ 109
1.4.10 LBFD-004010 Security Management .................................................................................................................. 110
1.4.11 LBFD-004011 Optimized eNodeB Commissioning Solution .............................................................................. 110
1.4.12 LBFD-004012 Environment Monitoring ............................................................................................................. 111
1.4.13 LBFD-004013 Inventory Management ................................................................................................................ 112
1.4.14 LBFD-004014 License Management ................................................................................................................... 113
1.4.15 LBFD-004015 License Control for Urgency ....................................................................................................... 114
1.4.16 LBFD-070104 Site Transmission Equipment Fault Detection ............................................................................ 115
1.4.17 LBFD-120101 Antenna Fault Detection .............................................................................................................. 119
1.4.18 LBFD-001024 Remote Electrical Tilt Control..................................................................................................... 120
1.4.19 LBFD-001041 Power Consumption Monitoring ................................................................................................. 121
1.4.20 LBFD-001075 RRU PA Efficiency Improvement ............................................................................................... 121
1.4.21 LBFD-002013 Cell Outage Detection and Compensation ................................................................................... 122
2 LTE Optional Features ............................................................................................................. 125

2.1 Voice & Other Services ............................................................................................................................................. 125
2.1.1 VoLTE .................................................................................................................................................................... 125
2.1.1.1 LOFD-001016 VoIP Semi-persistent Scheduling ............................................................................................... 127
2.1.1.2 LOFD-001017 RObust Header Compression (ROHC) ...................................................................................... 128
2.1.1.3 LOFD-001048 TTI Bundling .............................................................................................................................. 130
2.1.1.4 LOFD-001022 SRVCC to UTRAN .................................................................................................................... 131
2.1.1.5 LOFD-001087 SRVCC Flexible Steering to UTRAN ........................................................................................ 133
2.1.1.6 LOFD-001023 SRVCC to GERAN .................................................................................................................... 134
2.1.2 VoLTE Performance Evolution .............................................................................................................................. 135
2.1.2.1 LOFD-081229 Voice Characteristic Awareness Scheduling ............................................................................... 137
2.1.2.2 LOFD-081219 Inter-eNodeB VoLTE CoMP ...................................................................................................... 139
2.1.2.3 LOFD-111207 VoLTE Rate Control ................................................................................................................... 142
2.1.2.4 LOFD-120204 VoLTE Coverage Enhancement Based on Extended Delay Budget ........................................... 144
2.1.2.5 LOFD-121214 VoLTE Coverage-based CSFB ................................................................................................... 145
2.1.2.6 LOFD-121202 VoLTE User Prior Access ........................................................................................................... 147
2.1.3 CS Fallback............................................................................................................................................................ 148
2.1.3.1 LOFD-001033 CS Fallback to UTRAN ............................................................................................................. 150
2.1.3.2 LOFD-070202 Ultra-Flash CSFB to UTRAN .................................................................................................... 151
2.1.3.3 LOFD-001068 CS Fallback with LAI to UTRAN .............................................................................................. 154
2.1.3.4 LOFD-001088 CS Fallback Steering to UTRAN ............................................................................................... 155
2.1.3.5 LOFD-001052 Flash CS Fallback to UTRAN .................................................................................................... 155
2.1.3.6 LOFD-001034 CS Fallback to GERAN ............................................................................................................. 157
2.1.3.7 LOFD-001053 Flash CS Fallback to GERAN .................................................................................................... 158
2.1.3.8 LOFD-081283 Ultra-Flash CSFB to GERAN .................................................................................................... 159
2.1.3.9 LOFD-001069 CS Fallback with LAI to GERAN .............................................................................................. 161
2.1.3.10 LOFD-001089 CS Fallback Steering to GERAN ............................................................................................. 162
Issue 01 (2017-03-22) Huawei Proprietary and Confidential v

2.1.3.11 LOFD-001035 CS Fallback to CDMA2000 1xRTT ......................................................................................... 163

2.1.3.12 LOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT ........................................................................ 164
2.1.3.13 LOFD-001091 CS Fallback to CDMA2000 1xRTT Based on Frequency-specific Factors ............................. 166
2.1.4 LCS ........................................................................................................................................................................ 168
2.1.4.1 LOFD-001047 LoCation Services (LCS) ........................................................................................................... 168
2.1.5 eMBMS ................................................................................................................................................................. 170
2.1.5.1 LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture ........................................................ 172
2.1.5.1.1 LOFD-07022001 Multi-cell transmission in MBSFN area.............................................................................. 176
2.1.5.1.2 LOFD-07022002 Mixed transmission of unicast and broadcast ...................................................................... 176
2.1.5.1.3 LOFD-07022003 Data synchronization ........................................................................................................... 177
2.1.5.1.4 LOFD-07022004 Session admission control ................................................................................................... 179
2.1.5.2 LOFD-080215 eMBMS Service Continuity ....................................................................................................... 179
2.1.6 Video Service Optimization ................................................................................................................................... 180
2.1.6.1 LOFD-110221 Initial Acceleration ..................................................................................................................... 183
2.1.6.2 LOFD-001026 TCP Proxy Enhancer (TPE) ....................................................................................................... 185
2.1.6.3 LOFD-081202 Busy-Hour Download Rate Control ........................................................................................... 186
2.1.6.4 LOFD-081203 Video Service Rate Adaption ..................................................................................................... 187
2.1.6.5 LOFD-120205 Uplink Coverage Improvement for Video .................................................................................. 189
2.2 Radio & Performance ............................................................................................................................................... 190
2.2.1 2x2 MIMO ............................................................................................................................................................. 190
2.2.1.1 LOFD-001001 DL 2x2 MIMO ........................................................................................................................... 191
2.2.1.2 LOFD-001002 UL 2x2 MU-MIMO.................................................................................................................... 193
2.2.1.3 LOFD-001096 Advanced Receiver (PSIC)......................................................................................................... 194
2.2.2 4x2 Downlink MIMO ............................................................................................................................................ 195
2.2.2.1 LOFD-001003 DL 4x2 MIMO ........................................................................................................................... 195
2.2.3 4-Antenna Receiver Diversity................................................................................................................................ 197
2.2.3.1 LOFD-001005 UL 4-Antenna Receive Diversity ............................................................................................... 198
2.2.3.2 LOFD-001058 UL 2x4 MU-MIMO.................................................................................................................... 199
2.2.4 4x4 Downlink MIMO ............................................................................................................................................ 200
2.2.4.1 LOFD-001060 DL 4x4 MIMO ........................................................................................................................... 200
2.2.5 CoMP ..................................................................................................................................................................... 202
2.2.5.1 LOFD-060201 Adaptive Inter-Cell Interference Coordination ........................................................................... 204
2.2.5.2 LOFD-070208 Coordinated Scheduling based Power Control ........................................................................... 207
2.2.5.3 LOFD-081206 Uplink Coordinated Scheduling ................................................................................................. 210
2.2.5.4 LOFD-001066 Intra-eNodeB UL CoMP ............................................................................................................ 212
2.2.5.5 LOFD-070222 Intra-eNodeB UL CoMP Phase II............................................................................................... 215
2.2.5.6 LOFD-070223 UL CoMP Based on Coordinated eNodeB ................................................................................. 217
2.2.5.7 LOFD-120202 Intra-eNodeB and Inter-eNodeB Uplink Interference Cancellation ........................................... 220
2.2.5.8 LOFD-001012 UL Interference Rejection Combining ....................................................................................... 222
2.2.5.9 LOFD-001094 Control Channel IRC .................................................................................................................. 223
2.2.6 SFN ........................................................................................................................................................................ 224
2.2.6.1 LOFD-003029 SFN ............................................................................................................................................ 226
Issue 01 (2017-03-22) Huawei Proprietary and Confidential vi

2.2.6.2 LOFD-070205 Adaptive SFN/SDMA ................................................................................................................ 229

2.2.6.3 LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU ........................................................................ 231
2.2.6.4 LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on Coordinated BBU ............................................ 234
2.2.6.5 LOFD-081221 Super Combined Cell ................................................................................................................. 236
2.2.7 High Speed Scenario.............................................................................................................................................. 238
2.2.7.1 LOFD-001007 High Speed Mobility .................................................................................................................. 242
2.2.7.2 LOFD-001008 Ultra High Speed Mobility ......................................................................................................... 243
2.2.7.3 LOFD-081228 Handover Enhancement at Speed Mobility ................................................................................ 244
2.2.7.4 LOFD-111209 High Speed Specified Policy Management ................................................................................ 245
2.2.8 QoS ........................................................................................................................................................................ 247
2.2.8.1 LOFD-001054 Flexible User Steering ................................................................................................................ 250
2.2.8.1.1 LOFD-00105401 Camp & Handover Based on SPID ..................................................................................... 250
2.2.8.2 LOFD-001059 UL Pre-allocation Based on SPID .............................................................................................. 252
2.2.8.3 LOFD-081218 Enhanced Extended QCI ............................................................................................................ 253
2.2.8.4 LOFD-001029 Enhanced Admission Control ..................................................................................................... 255
2.2.8.4.1 LOFD-00102901 Radio/transport resource pre-emption ................................................................................. 255
2.2.9 High Load Handling .............................................................................................................................................. 256
2.2.9.1 LOFD-001109 DL Non-GBR Packet Bundling .................................................................................................. 259
2.2.9.2 LOFD-008002 Dynamic Service-Specific Access Control ................................................................................. 259
2.2.9.3 LOFD-070207 Intelligent Access Class Control................................................................................................. 261
2.2.9.4 LOFD-081205 Automatic Congestion Handling ................................................................................................ 262
2.2.9.5 LOFD-110205 Traffic Model Based Performance Optimization ........................................................................ 264
2.2.10 Uplink High Order Modulation ........................................................................................................................... 266
2.2.10.1 LOFD-001006 UL 64QAM .............................................................................................................................. 266
2.2.11 RAN & Terminal Cooperation ............................................................................................................................. 267
2.2.11.1 LOFD-001105 Dynamic DRX .......................................................................................................................... 268
2.2.11.1.1 LOFD-00110501 Dynamic DRX ................................................................................................................... 268
2.2.11.1.2 LOFD-00110502 High-Mobility-Triggered Idle Mode.................................................................................. 269
2.2.11.2 LOFD-080212 SRLTE Optimization ................................................................................................................ 270
2.2.11.3 LOFD-110223 WBB Specified Policy Management ........................................................................................ 272
2.2.12 Inter-RAT Mobility .............................................................................................................................................. 273
2.2.12.1 LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN ....................................................... 275
2.2.12.2 LOFD-001043 Service based inter-RAT handover to UTRAN ........................................................................ 278
2.2.12.3 LOFD-001072 Distance based Inter-RAT handover to UTRAN ...................................................................... 279
2.2.12.4 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering .................................................................................... 280
2.2.12.5 LOFD-070216 Separate Mobility Policies to UTRAN for Multi PLMN ......................................................... 281
2.2.12.6 LOFD-070203 RIM Based LTE Target Cell Selection ..................................................................................... 282
2.2.12.7 LOFD-111204 Separate Mobility Policies to GERAN for Multi PLMN.......................................................... 284
2.2.12.8 LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN ....................................................... 285
2.2.12.9 LOFD-001046 Service based inter-RAT handover to GERAN ........................................................................ 288
2.2.12.10 LOFD-001073 Distance based Inter-RAT handover to GERAN .................................................................... 289
2.2.12.11 LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000 ............................................... 289
Issue 01 (2017-03-22) Huawei Proprietary and Confidential vii

2.2.12.12 LOFD-001111 PS Mobility from E-UTRAN to CDMA2000 HRPD Based on Frequency-specific Factors . 291
2.2.13 Multi-carrier Load Management .......................................................................................................................... 293
2.2.13.1 LOFD-001032 Intra-LTE Load Balancing........................................................................................................ 294
2.2.13.2 LOFD-070215 Intra-LTE User Number Load Balancing ................................................................................. 295
2.2.13.3 LOFD-001044 Inter-RAT Load Sharing to UTRAN ........................................................................................ 297
2.2.13.4 LOFD-001045 Inter-RAT Load Sharing to GERAN ........................................................................................ 298
2.2.13.5 LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells .................................................................... 299
2.2.13.6 LOFD-121201 Multi-band Optimal Carrier Selection ...................................................................................... 300
2.2.14 Spectrum & Site Management ............................................................................................................................. 301
2.2.14.1 LOFD-001051 Compact Bandwidth ................................................................................................................. 304
2.2.14.2 LOFD-001093 PUCCH Flexible Configuration ............................................................................................... 306
2.2.14.3 LOFD-111205 CDMA and LTE Zero Bufferzone (LTE FDD) ......................................................................... 307
2.2.14.4 LOFD-001076 CPRI Compression ................................................................................................................... 310
2.2.15 Coverage Enhancement ....................................................................................................................................... 312
2.2.15.1 LOFD-001009 Extended Cell Access Radius ................................................................................................... 313
2.2.15.2 LOFD-001031 Extended CP ............................................................................................................................. 314
2.2.15.3 LOFD-081223 Extended Cell Access Radius Beyond 100km.......................................................................... 315
2.2.15.4 LOFD-120201 Turbo Receiver ......................................................................................................................... 317
2.3 Networking & Transmission & Security................................................................................................................... 318
2.3.1 Transmission Network Enhancement .................................................................................................................... 318
2.3.1.1 LOFD-003011 Enhanced Transmission QoS Management ................................................................................ 322
2.3.1.1.1 LOFD-00301101 Transport Overbooking ........................................................................................................ 322
2.3.1.1.2 LOFD-00301102 Transport Differentiated Flow Control ................................................................................ 323
2.3.1.1.3 LOFD-00301103 Transport Resource Overload Control ................................................................................. 324
2.3.1.2 LOFD-070219 IP Active Performance Measurement ......................................................................................... 325
2.3.1.3 LOFD-003004 Ethernet OAM ............................................................................................................................ 327
2.3.1.3.1 LOFD-00300401 Ethernet OAM (IEEE 802.3ah) ........................................................................................... 327
2.3.1.3.2 LOFD-00300402 Ethernet OAM (IEEE 802.1ag) ........................................................................................... 328
2.3.1.3.3 LOFD-00300403 Ethernet OAM (Y.1731) ...................................................................................................... 329
2.3.1.4 LOFD-003005 OM Channel Backup .................................................................................................................. 330
2.3.1.5 LOFD-003007 Bidirectional Forwarding Detection ........................................................................................... 331
2.3.1.6 LOFD-003008 Ethernet Link Aggregation (IEEE 802.3ad) ............................................................................... 333
2.3.1.7 LOFD-003016 Different Transport Paths based on QoS Grade.......................................................................... 334
2.3.1.8 LOFD-003017 S1 and X2 over IPv6 .................................................................................................................. 335
2.3.1.9 LOFD-003002 2G/3G and LTE Co-transmission ............................................................................................... 336
2.3.2 Synchronization ..................................................................................................................................................... 338
2.3.2.1 LOFD-003013 Enhanced Synchronization ......................................................................................................... 340
2.3.2.1.1 LOFD-00301301 Synchronization with Ethernet (ITU-T G.8261) .................................................................. 340
2.3.2.1.2 LOFD-00301302 IEEE1588 V2 Clock Synchronization ................................................................................. 342
2.3.2.1.3 LOFD-00301303 Clock over IP (Huawei proprietary) .................................................................................... 345
2.3.2.2 LOFD-003023 IEEE 1588v2 over IPv6.............................................................................................................. 347
2.3.2.3 LOFD-080216 Uu based Soft Synchronization .................................................................................................. 348
Issue 01 (2017-03-22) Huawei Proprietary and Confidential viii

2.3.2.4 LOFD-081220 Inter-BBU Clock Sharing ........................................................................................................... 349

2.3.2.5 LOFD-121212 eNodeB Supporting 1588v2 ATR ............................................................................................... 350
2.3.3 Security .................................................................................................................................................................. 352
2.3.3.1 LOFD-070212 eNodeB Supporting PKI Redundancy ........................................................................................ 353
2.3.3.2 LOFD-081280 eNodeB Supporting Multi-operator PKI .................................................................................... 355
2.3.3.3 LOFD-003014 Integrated Firewall ..................................................................................................................... 357
2.3.3.3.1 LOFD-00301401 Access Control List (ACL) .................................................................................................. 357
2.3.3.3.2 LOFD-00301402 Access Control List (ACL) Auto Configuration .................................................................. 358
2.3.3.4 LOFD-003015 Access Control based on 802.1x................................................................................................. 359
2.3.4 IPsec....................................................................................................................................................................... 360
2.3.4.1 LOFD-003009 IPsec ........................................................................................................................................... 362
2.3.4.2 LOFD-003019 IPsec Tunnel Backup .................................................................................................................. 364
2.3.4.3 LOFD-003024 IPsec for IPv6 ............................................................................................................................. 365
2.3.4.4 LOFD-070211 IPsec Redundancy Among Multiple SeGWs .............................................................................. 366
2.3.4.5 LOFD-081281 eNodeB Supporting IPsec Redirection ....................................................................................... 368
2.3.4.6 LOFD-111203 eNodeB Supporting Digital Certificate Whitelist Management ................................................. 369
2.3.4.7 LOFD-121213 Direct IPsec ................................................................................................................................ 371
2.3.5 RAN Sharing ......................................................................................................................................................... 372
2.3.5.1 LOFD-001036 RAN Sharing with Common Carrier .......................................................................................... 374
2.3.5.2 LOFD-001037 RAN Sharing with Dedicated Carrier......................................................................................... 377
2.3.5.3 LOFD-001086 RAN Sharing by More Operators ............................................................................................... 378
2.3.5.4 LOFD-001112 MOCN Flexible Priority Based Camping ................................................................................... 379
2.3.5.5 LOFD-070206 Hybrid RAN Sharing .................................................................................................................. 380
2.3.5.6 LOFD-070204 Operator Load Based Intra-LTE MLB ....................................................................................... 382
2.3.5.7 LOFD-070213 Fair User Sharing ....................................................................................................................... 383
2.3.5.8 LOFD-070210 Multi Operators SPID Policy ..................................................................................................... 384
2.3.6 Small Cell .............................................................................................................................................................. 385
2.3.6.1 LOFD-001057 Load Balancing based on Transport QoS ................................................................................... 385
2.3.6.2 LOFD-003022 PPPoE......................................................................................................................................... 386
2.3.6.3 LOFD-003031 Horizon Beam-Width Adjustment .............................................................................................. 387
2.4 O&M......................................................................................................................................................................... 388
2.4.1 SON ....................................................................................................................................................................... 388
2.4.1.1 LOFD-002001 Automatic Neighbour Relation (ANR)....................................................................................... 391
2.4.1.2 LOFD-002002 Inter-RAT ANR .......................................................................................................................... 394
2.4.1.3 LOFD-002007 PCI Collision Detection & Self-Optimization ............................................................................ 397
2.4.1.4 LOFD-081225 Neighboring Cell Classification Management ........................................................................... 400
2.4.1.5 LOFD-110219 Auto Neighbor Group Configuration .......................................................................................... 404
2.4.1.6 LOFD-002005 Mobility Robust Optimization (MRO) ....................................................................................... 406
2.4.1.7 LOFD-002015 RACH Optimization................................................................................................................... 408
2.4.1.8 LOFD-081207 Specified PCI Group-based Neighboring Cell Management...................................................... 410
2.4.2 Power Saving ......................................................................................................................................................... 411
2.4.2.1 LOFD-001025 Adaptive Power Consumption .................................................................................................... 412
Issue 01 (2017-03-22) Huawei Proprietary and Confidential ix

2.4.2.2 LOFD-001039 RF Channel Intelligent Shutdown .............................................................................................. 414

2.4.2.3 LOFD-001040 Low Power Consumption Mode................................................................................................. 415
2.4.2.4 LOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage ........................................................... 416
2.4.2.5 LOFD-001056 PSU Intelligent Sleep Mode ....................................................................................................... 417
2.4.2.6 LOFD-001070 Symbol Power Saving ................................................................................................................ 418
2.4.2.7 LOFD-001071 Intelligent Battery Management ................................................................................................. 420
2.4.2.8 LOFD-001074 Intelligent Power-Off of Carriers in the Same Coverage of UMTS Network ............................ 421
3 Acronyms and Abbreviations ................................................................................................. 423
Issue 01 (2017-03-22) Huawei Proprietary and Confidential x

LTE FDD eRAN12.1 Feature Description 1 LTE Basic Features
1 LTE Basic Features
1.1 Standards Compliance

1.2 RAN Architecture & Features
1.3 Transmission & Security
1.4 Operation & Maintenance
1.1 Standards Compliance

1.1.1 LBFD-001001 3GPP R8 Specifications
Availability
This feature is
 applicable to Macro from eRAN1.0
 applicable to Micro from eRAN3.0
 applicable to LampSite from eRAN6.0
Summary
Huawei LTE eNodeB is compliant with 3GPP Release 8 specifications 2009Q3.
Benefits
None
Description
Huawei LTE eNodeB is compliant with 3GPP Release 8 specifications 2009Q3.
Huawei is an active participant and great contributor to 3GPP specification development. This
high-level involvement enables Huawei to actively contribute, and closely follow 3GPP
standard development during Huawei product development. LTE eNodeB supports 3GPP
Release 8 2009Q3.
Issue 01 (2017-03-22) Huawei Proprietary and Confidential 1

Enhancement
None
Dependency
None

Availability
This feature is
Summary
Huawei LTE eNodeB is compliant with 3GPP Release 9 specifications 2010.09 version.
Benefits
None
Description
Release 9 specifications 2010.09 version, which is the latest version of LTE standard.
Enhancement
None
Dependency
None

Availability
This feature is

Summary
Huawei LTE eNodeB is compliant with 3GPP Release 10 specifications.
Benefits
None
Description
Release 10 specifications 2011.03 version.
Enhancement
None
Dependency
None

Availability
This feature is
Summary
Huawei LTE eNodeB is compliant with 3GPP Release 11 specifications.
Benefits
None
Description
Huawei LTE eNodeB is compliant with 3GPP Release 11 specifications released in September
2013.
Huawei is an active participant and contributor to 3GPP specification development. This
high-level involvement enables Huawei to closely follow 3GPP specifications during Huawei
product development.Huawei LTE eNodeB now supports 3GPP Release 11 specifications
released in September 2013.

Enhancement
None
Dependency
None

Availability
This feature is:
 Applicable to Macro from eRAN11.1.
 Applicable to Micro from eRAN11.1.
 Applicable to LampSite from eRAN11.1.
Summary
Huawei eNodeBs comply with 3GPP Release 12.
Benefits
None
Description
high-level involvement enables Huawei to closely follow 3GPP standards development during
Huawei product development. Huawei eNodeBs now work in compliance with 3GPP Release
12 specifications issued in the third quarter of 2015.
Enhancement
None
Dependency
None

Availability
This feature is:
 Available in macro eNodeBs as of eRAN12.1.
 Available in micro eNodeBs as of eRAN12.1.
 Available in LampSite eNodeBs as of eRAN12.1.

Summary
Huawei eNodeBs comply with 3GPP Release 13 specifications issued in the third quarter of
2016.
Benefits
None
Description
Huawei eNodeBs comply with 3GPP Release 13 specifications.
Huawei is an active participant and a major contributor to 3GPP specifications. This
high-level involvement enables Huawei to closely follow the development of 3GPP standards
during Huawei product development. Huawei eNodeBs support 3GPP Release 13 issued in
the third quarter of 2016.
Enhancement
None
Dependency
None
1.1.7 LBFD-001002 FDD mode

Availability
This feature is
Summary
Huawei LTE supports the Frequency Division Duplex (FDD) mode .
Benefits
None
Description
The 3GPP specifications support the FDD mode. In FDD mode, separate frequency bands are
used for the uplink and the downlink.
Enhancement
None

Dependency
 Others
The related network elements (NEs) should support FDD mode.
1.1.8 LBFD-001003 Scalable Bandwidth

Availability
This feature is
Summary
Huawei LTE eRAN1.0 supports the bandwidths of 5 MHz, 10 MHz, 15 MHz, and 20 MHz.
Huawei LTE eRAN2.0 supports two new bandwidths of 1.4 MHz and 3 MHz to extend the
range of bandwidth support for the LTE technology. Micro eNodeB does not support 1.4 MHz
and 3 MHz bandwidth.
Benefits
 Larger bandwidth produces higher throughput and better user experience.
 Flexible bandwidth configuration helps operators use frequency bands.
 Besides the existing bandwidths supported by eRAN1.0, the introduction of 1.4 MHz
and 3 MHz bandwidths enables the flexibility for operators to allocate smaller bandwidth
less than 5 MHz, thus saving radio resources. This is not applicable to Micro eNodeB.
Description
Huawei LTE eRAN2.0 supports the channel bandwidths from 1.4 MHz to 20 MHz, including
1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz. The bandwidth can be configured
by the software.
Enhancement
 In eRAN2.0
Huawei LTE eRAN1.0 supports the bandwidths of 5 MHz, 10 MHz, 15 MHz, and 20
MHz.
Huawei LTE eRAN2.0 supports two new bandwidths of 1.4 MHz and 3 MHz.
Dependency
 UE
UEs should support the same bandwidth as the eNodeB.

1.1.9 LBFD-001004 CP length

1.1.9.1 LBFD-00100401 Normal CP
Availability
This feature is
Summary
In an OFDM symbol, the Cyclic Prefix (CP) is a time-domain replication of the end of the
symbol and is appended to the beginning of the symbol. It provides the guard interval in the
OFDM to decrease the inter-symbol interference due to the multipath delay.
Benefits
The CP is used to decrease the inter-symbol interference due to the multipath delay.
Description
The CP is the guard interval used in the OFDM to decrease the interference due to the
multipath delay.
There are two CP lengths defined in 3GPP specifications: normal CP and extended CP.
In the case of 15 kHz subcarrier spacing, the normal CP corresponds to seven OFDM symbols
per slot in the downlink and seven SC-FDMA symbols per slot in the uplink. The normal CP
length (time) is calculated as follows:
 In the downlink
Normal CP: TCP = 160 x Ts (OFDM symbol #0), TCP = 144 x Ts (OFDM symbol #1 to #6)
 In the uplink
Normal CP: TCP = 160 x Ts (SC-FDMA symbol #0), TCP = 144 x Ts (SC-FDMA symbol #1
to #6)
Where, Ts = 1 / (2048 x Df), Df = 15 kHz
Enhancement
None
Dependency
None

1.1.10 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM,

DL 64QAM
Availability
This feature is
Summary
This feature shows the different modulation schemes supported by the UE and eNodeB.
Benefits
This feature provides a wide range of modulation schemes to be chosen based on the channel
condition. Higher-order modulation schemes, such as DL 64QAM, can be used under
excellent channel conditions to achieve higher data rates, which improves the system
throughput and spectrum efficiency.
Description
This feature provides a wide range of modulation schemes that can be used by both the
eNodeB and the UE in uplink and downlink.
The following modulation schemes are supported:
 Uplink/downlink Quadrature Phase Shift Keying (QPSK)
 Uplink/downlink 16 Quadrature Amplitude Modulation (16QAM)
 Downlink 64QAM
The characteristics are as follows:
 QPSK allows up to two information bits modulated per symbol due to four different
neighboring alternatives.
 16QAM allows up to four information bits modulated per symbol due to 16 different
 64QAM allows up to six information bits modulated per symbol due to 64 different
This feature allows the eNodeB and UE to choose an optimal modulation scheme based on the
current channel condition to achieve the best tradeoff between the user data rate and the frame
error rate (FER) during transmission.
A more favorable channel condition is required to support a higher-order modulation scheme.
For example, when a UE is in a poor radio environment, it may use a low-order QPSK
modulation scheme for uplink transmission to meet the requirement of the call quality. When
a UE is in an excellent radio environment, it can use a high-order QAM modulation (such as
16QAM) scheme for uplink transmission to achieve high bit rates.

Enhancement
None
Dependency
 UE
The UE should support the same modulation scheme.
1.1.11 LBFD-001006 AMC

Availability
This feature is
Summary
The Adaptive Modulation and Coding (AMC) function allows an eNodeB to adaptively select
the optimal Modulation and Coding Scheme (MCS) according to the channel condition. This
improves the spectrum efficiency after the system resource and transmitting power are fixed.
Therefore, the throughput can be maximized and the Quality of Service (QoS) requirements
can be met.
Benefits
The AMC provides the following benefits:
 Maximizes the system throughput by selecting the optimal MCS.
 Meets the QoS requirement (such as the packet loss rate) by selecting the optimal MCS
to achieve the best tradeoff between data rate and block error rate.
Description
The AMC function allows an eNodeB to adaptively select the optimal MCS according to the
channel information. This improves the spectrum efficiency after the system resource and
transmitting power are fixed. Therefore, the throughput can be maximized and the QoS
requirements can be met.
In the uplink, the initial MCS can be selected on the basis of the Signal to Interference plus
Noise Ratio (SINR) of the uplink Reference Signal (RS) measured by the eNodeB. It can also
be adjusted on the basis of whether the uplink transmission involves control signals. Note that
control signals might require a lower-order MCS for ensuring a reliable transmission.
In the downlink, the eNodeB first selects the MCS for each UE based on the CQI reported
from the UE and assigned power for the UE. Then, the eNodeB can adjust the CQI to impact
MCS based on the BLER, in order to maximize the usage of the radio resources.
Enhancement
None

Dependency
None
1.1.12 LBFD-001030 Support of UE Category 2/3/4

Availability
This feature is:
Summary
During configuration and scheduling, eNodeBs must consider the radio access capabilities of
UEs. Five categories have been defined in 3GPP specifications. This feature enables eNodeBs
to support UE categories 2, 3, and 4.
Benefits
eNodeBs now work with UEs of categories 2, 3, and 4.
Description
During configuration and scheduling, eNodeBs must consider the radio access capabilities of
UEs. Five categories have been defined in 3GPP specifications. This feature enables eNodeBs
to support UE categories 2, 3, and 4.
Table 1-1 Downlink physical layer parameter values set by the field UE-Category
UE Category Max. No. of Max. No. of Total No. of Max. No. of

DL-SCH Bits of a Soft Channel Supported
Transport DL-SCH Bits Layers for
Block Bits Transport Spatial
Received Block Multiplexing
Within a TTI Received in DL
Within a TTI
1 10296 10296 250368 1
2 51024 51024 1237248 2
3 102048 75376 1237248 2
4 150752 75376 1827072 2
5 299552 149776 3667200 4

Table 1-2 Uplink physical layer parameter values set by the field UE-Category
UE Category Max. No. of Bits of a Support for UL 64QAM

UL-SCH Transport Block
Transmitted Within a
TTI
1 5160 No
2 25456 No
3 51024 No
4 51024 No
5 75376 Yes
Table 1-3 Total layer-2 buffer sizes set by the field UE-Category
UE Category Total L2 Buffer Size (kBytes)
1 150
2 700
3 1400
4 1900
5 3500
Enhancement
None
Dependency
 UE
The UE category of terminals must be consistent with that supported by eNodeBs.
1.2 RAN Architecture & Features

1.2.1 LBFD-002001 Logical Channel Management
Availability
This feature is

Summary
The logical channels are provided between the Medium Access Control (MAC) layer and the
Radio Link Control (RLC) layer. Each logical channel type is defined according to the type of
the transmitted data. They are generally classified into two types: control channels and traffic
channels.
Benefits
The logical channels are responsible for what type of information is transferred.
Description
The logical channels are provided between the MAC layer and the RLC layer. They are
responsible for "what is transported". They are generally classified into two types:
 Control channels: for transmitting the control plane information
 Traffic channels: for transmitting the user plane information
Control channels include:
 Broadcast Control Channel (BCCH)
 Paging Control Channel (PCCH)
 Common Control Channel (CCCH)
 Multicast Control Channel (MCCH)
 Dedicated Control Channel (DCCH)
Traffic channels include:
 Dedicated Traffic Channel (DTCH)
 Multicast Traffic Channel (MTCH)
Enhancement
None
Dependency
None
1.2.2 LBFD-002002 Transport Channel Management

Availability
This feature is

Summary
Transport channels that are provided between the MAC layer and the physical layer, are
defined according to the type of transmitted data and the method of data transmission over the
radio interface. They are used to offer the information about transmission services for the
MAC and higher layers.
Benefits
The transport channels are responsible for what type of data is transmitted and how the data is
transmitted.
Description
The transport channels are provided between the MAC layer and the physical layer. They are
responsible for what type of data is transmitted and how the data is transmitted over the radio
interface.
Downlink transport channels are classified into the following types:
 Broadcast Channel (BCH)
 Downlink Shared Channel (DL-SCH)
 Paging Channel (PCH)
 Multicast Channel (MCH)
Uplink transport channels are classified into the following types:
 Uplink Shared Channel (UL-SCH)
 Random Access Channel (RACH)
Enhancement
None
Dependency
None
1.2.3 LBFD-002003 Physical Channel Management

Availability
This feature is:
Summary
A physical channel is responsible for coding, hybrid automatic repeat request (HARQ)
processing, modulation, multi-antenna processing, and mapping from the signal to the

appropriate physical time-frequency resources. Based on the mapping, a transport channel at

the transport layer can serve one or multiple physical channels at the physical layer.
Benefits
Each physical channel provides a set of resource blocks for information transmission.
Description
Each physical channel corresponds to a set of resource blocks carrying the information from
higher layers.
Downlink physical channels are divided into the following types:
 Physical Broadcast Channel (PBCH)
 Physical Control Format Indicator Channel (PCFICH)
 Physical Downlink Control Channel (PDCCH)
 Physical HARQ Indicator Channel (PHICH)
 Physical Downlink Shared Channel (PDSCH)
 Physical Multicast Channel (PMCH)
Uplink physical channels are divided into the following types:
 Physical Uplink Control Channel (PUCCH)
 Physical Uplink Shared Channel (PUSCH)
 Physical Random Access Channel (PRACH)
Enhancement
 eRAN11.1
In versions earlier than eRAN11.0, format 2x code channel resources are allocated in
ascending order. In eRAN11.0, they are allocated by preferentially enlarging the code
channel gap on each format 2x RB. As a result, the interference between code channels
decreases, thereby improving CQI demodulation performance and CQI and MCS
reliability.
The OPTISELECTMODE(OPTISELECTMODE) option of the
PUCCHCfg.Format1ChAllocMode parameter is added. It takes effect only when the
PUCCHCfg.DeltaShift parameter is set to DS1_DELTA_SHIFT(ds1). When the
PUCCHCfg.Format1ChAllocMode parameter is set to
OPTISELECTMODE(OPTISELECTMODE), code channels used by each RB in
format 1x are not limited to the first 18 code channels. Instead, the eNodeB selects 18
code channels with the lowest inter-channel interference from all the 36 code channels
for each RB in format 1x and allocates format 1x resources to UEs. The new allocation
method decreases inter-channel interference, improves SRI demodulation performance,
but increases the RBs occupied by the PUCCH.
Dependency
None

1.2.4 LBFD-002004 Integrity Protection

Availability
This feature is:
 Available in macro eNodeBs as of eRAN1.0
 Available in micro eNodeBs as of eRAN3.0
 Available in LampSite eNodeBs as of eRAN6.0
Summary
The feature offers integrity protection for signaling data. It enables the receiving entity (either
UE or eNodeB) to check whether the signaling data has been illegally modified. It encrypts or
decrypts the signaling data by using a certain integrity algorithm through an RRC message.
Benefits
The integrity protection procedure prevents the signaling data from illegal modification.
Description
LTE offers the integrity protection for RRC signaling messages at the PDCP layer. The sender
calculates a message authentication code MAC-I based on the RRC message and some
parameters (such as the key, bearer ID, direction, and count) by using an integrity algorithm,
and then send the code to the receiver together with the message. The receiver recalculates the
code and compares it with the code in the message. If the two codes are inconsistent, the
receiver knows that the message has been modified illegally.
The eNodeB decides which integrity algorithm to use and informs each UE of it through an
RRC message.
Enhancement
 eRAN2.0
In addition to the AES, Huawei eRAN2.0 also supports integrity algorithm SNOW3G.
 In eRAN6.0 (macro eNodeB change only)
Macro eNodeBs also support integrity algorithm ZUC.
 In eRAN7.0 (micro eNodeB change only)
Micro eNodeBs also support integrity algorithm ZUC.
Dependency
 eNodeB
The LBBPc and the BTS3202E do not support the ZUC algorithm.
 UE
The UE should support the same integrity algorithm as the eNodeB.

1.2.5 LBFD-002005 DL Asynchronous HARQ

Availability
This feature is
Summary
The Hybrid Automatic Repeat Request (HARQ) provides robustness against transmission
errors. It is also a mechanism for capacity enhancement. As HARQ retransmissions are fast,
many services allow one or multiple times of retransmissions, thereby forming an implicit
(closed loop) rate-control mechanism. An asynchronous protocol is the basis for downlink
HARQ operation. Hence, downlink retransmissions may occur at any time after the initial
transmission, and an explicit HARQ process number is used to indicate the HARQ process.
Benefits
DL HARQ functionality is a fast retransmission protocol to ensure successful data
transmission from the eNodeB to a UE at the physical layer and MAC layer. A UE can request
for retransmissions of data that was incorrectly decoded through an NACK message and
soft-combine the retransmitted data with the previously received data to improve the decoding
performance.
This feature helps improve user throughput and reduce transmission latency in the downlink.
Description
The HARQ is a link enhancement technique combining Forward Error Correction (FEC) and
ARQ technologies. Compared with the ARQ, the HARQ can provide faster and more efficient
retransmissions with lower transmission latency. In the downlink, if the data received by the
UE is decoded correctly by the FEC and passes the Cyclic Redundancy Check (CRC), the UE
will send an ACK message to inform the eNodeB that the data was received correctly.
Otherwise, the UE will send a NACK message to the eNodeB to request for data
retransmission.
Downlink HARQ is an asynchronous adaptive transmission process, which means that the
scheduler of the HARQ transmission is not predetermined to the UE. In addition, the DL
HARQ information, such as the location of the allocated resource blocks and MCSs, may be
different from that of the previous transmissions.
In LTE specifications, the DL HARQ scheme is based on an Incremental Redundancy (IR)
algorithm. After the retransmitted data is received, the HARQ process in the UE will
soft-combine the retransmitted data with the previously buffered content and then forward the
combined data to the FEC for decoding. The soft-combined data will help increase the
probability of successful FEC decoding, thus increasing the data reception success rate.
In LTE specifications, multiple downlink HARQ processes are adopted to fully utilize system
resources. It greatly improves the system throughput and reduces the latency, but it requires
more buffer space and signaling overhead.

Enhancement
None
Dependency
None
1.2.6 LBFD-002006 UL Synchronous HARQ

Availability
This feature is
Summary
Compared with the downlink HARQ, uplink retransmission is based on a synchronization
protocol. It occurs at a predefined time after the initial transmission and the number of
retransmissions can be implicitly derived.
Benefits
The UL HARQ functionality is a fast retransmission protocol to ensure successful data
transmission from the UE to the eNodeB at the physical layer and MAC layer. An eNodeB
can request for retransmissions of data that is incorrectly decoded and soft-combine the
retransmitted data with the previously received data to improve the decoding performance.
This feature helps improve the user throughput and reduce transmission latency in the uplink.
Description
The HARQ is a link enhancement technique combining FEC and ARQ technologies.
Compared with the ARQ, the HARQ can provide faster and more efficient retransmissions
with lower transmission latency. In the uplink, if the data received by the eNodeB is decoded
correctly by the FEC and passes the CRC check, the eNodeB will send an ACK message over
the PHICH to inform the UE that the data was received correctly. Otherwise, the eNodeB will
send an NACK message to the UE to request for data retransmission.
In eRAN1.0, Uplink HARQ is a synchronization non-adaptive transmission process, which
means that HARQ transmission blocks are predetermined for transmission and retransmission.
In addition, the UL HARQ information, such as the location of the allocated resource blocks
and MCSs, is predetermined by the eNodeB.
In eRAN2.0, Huawei supports a synchronous adaptive UL HARQ transmission. While
retransmitting, the allocated resource block, coding and modulation scheme may be changed
according to the channel quality. But the retransmission transport block size remains the same
as the first transmission.
In LTE specifications, UL HARQ scheme is based on an IR algorithm. After the retransmitted
data is received, HARQ process in the eNodeB will soft-combine the retransmitted data with
the previously buffered content and forward the combined data to the FEC for decoding. The

soft-combined data will help increase the probability of successful FEC decoding, thus
increasing the data reception success rate.
In LTE specifications, multiple uplink HARQ processes are adopted to fully utilize system
resources. It greatly improves the system throughput and reduces the latency, but it requires
more buffer space and signaling overhead.
Enhancement
 In eRAN2.0
Huawei supports a synchronous adaptive UL HARQ transmission. While in eRAN1.0,
Uplink HARQ is a synchronization non-adaptive transmission process.
Dependency
None
1.2.7 LBFD-002007 RRC Connection Management

Availability
This feature is
Summary
RRC connection is the layer 3 connection between the UE and eNodeB. The RRC connection
management aims to manage the layer 3 connection, including establishment, maintenance,
and release of the connection.
Benefits
The RRC connection management is essential from the UE to E-UTRAN, and serves all
service procedures and NAS procedures.
Description
RRC connection management involves RRC connection establishment, RRC connection
reconfiguration, RRC connection re-establishment, and RRC connection release.
 RRC connection establishment: This procedure is performed to establish an RRC
connection. RRC connection establishment involves Signaling Radio Bearer 1 (SRB1)
establishment. The procedure is also used to transmit the initial NAS dedicated
information or messages from the UE to the E-UTRAN.
 RRC connection reconfiguration: This procedure is performed to modify an RRC
connection, for example, to establish, modify, or release radio bearers, to perform
handovers, and to configure or modify measurements. As a part of the procedure, NAS
dedicated information may be transmitted from the E-UTRAN to the UE.
 RRC connection re-establishment: This procedure is performed to re-establish an RRC
connection after a handover failure or radio link failure. RRC connection

re-establishment involves the restoration of SRB1 operation and the re-activation of

security. A UE in RRC_CONNECTED mode, for which security has been activated, may
initiate the procedure in order to continue the RRC connection. The connection
re-establishment will succeed only if the cell has a valid UE context.
 RRC connection release: This procedure is performed to release an RRC connection.
RRC connection release involves the release of the established radio bearers and the
release of all radio resources.
Enhancement
None
Dependency
None
1.2.8 LBFD-002008 Radio Bearer Management

Availability
This feature is
Summary
Radio bearer management aims to manage SRB2 and Data Radio Bearer (DRB). The radio
bearer management includes the establishment, maintenance, and release of radio bearers.
Benefits
This feature provides configuration function of radio resources.
Description
Radio bearer management involves the establishment, maintenance, and release of radio
bearers, as well as the configuration of associated radio resources, for example PDCP, RLC,
logical channel, DRX,CQI, power headroom report (PHR), and physical layer configuration.
The radio bearer management is implemented during the RRC connection reconfiguration
procedure.
Enhancement
None
Dependency
None

1.2.9 LBFD-002009 Broadcast of system information

Availability
This feature is
Summary
System information (SI) includes:
 Basic information for a UE to access the E-UTRAN, such as basic radio and channel
parameters
 Information about cell selection and reselection parameters used by the UE in
RRC_IDLE mode
 Information about neighboring cells
 Important messages that should be sent to each UE, such as earthquake warning
information
The SI broadcasted over the BCCH can be read without setting an RRC connection, and it can
be read by the UE in RRC_IDLE mode and RRC_CONNECTED mode. SI may also be
provided to the UE by means of dedicated signaling, for example, in the case of handover.
Benefits
This feature is the basis for the UE to access the E-UTRAN.
Description
SI is classified into the MasterInformationBlock (MIB) and a number of
SystemInformationBlocks (SIBs):
 MasterInformationBlock defines the information about the most essential physical layers
of the cell required for receiving further system information;
 SystemInformationBlockType1 contains the information for checking whether a UE is
allowed to access a cell and for defining the scheduling of other system information
blocks;
 SystemInformationBlockType2 contains the information about common and shared
channels;
 SystemInformationBlockType3 contains cell re-selection information, mainly related to
the serving cell;
 SystemInformationBlockType4 contains the information about the serving frequency and
intra-frequency neighboring cells related to cell re-selection (including common cell
re-selection parameters for a frequency and cell-specific re-selection parameters);
 SystemInformationBlockType5 contains the information about other E-UTRA
frequencies and inter-frequency neighboring cells related to cell re-selection (including
common cell re-selection parameters for a frequency and cell-specific re-selection
parameters);

 SystemInformationBlockType6 contains the information about UTRA frequencies and

UTRA neighboring cells related to cell re-selection (including common cell re-selection
parameters for a frequency and cell-specific re-selection parameters);
 SystemInformationBlockType7 contains the information about GERAN frequencies
related to cell re-selection (including cell re-selection parameters for each frequency);
 SystemInformationBlockType8 contains the information about CDMA2000 frequencies
and CDMA2000 neighboring cells related to cell re-selection (including common cell
re-selection parameters for a frequency and cell-specific re-selection parameters);
 SystemInformationBlockType9 contains a home eNodeB identifier (HNBID);
 SystemInformationBlockType10 contains an ETWS primary notification;
 SystemInformationBlockType11 contains an ETWS secondary notification.
The paging message is used to inform the UEs in RRC_IDLE and the UEs in
RRC_CONNECTED of the change of the system information.
Huawei eNodeB supports MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, SIB10 and
SIB11.
Enhancement
None
Dependency
None
1.2.10 LBFD-002010 Random Access Procedure

Availability
This feature is:
Summary
Random access is a necessary function of LTE. It enables UE uplink synchronization and
allows the UE to request a connection setup. Random access is performed when any of the
following five events occurs:
 A UE in idle mode attempts its first access to the network.
 An RRC connection is reestablished.
 A handover is performed.
 A UE in connected mode is out of synchronization in the uplink and has received
downlink data.
 A UE in connected mode is out of synchronization in the uplink and has uplink data to
transmit.

Benefits
This feature is the basis for UEs to access the E-UTRAN.
Description
The random access procedure enables a UE to establish uplink timing synchronization and
request setup of a connection to an eNodeB.
This procedure is classified into contention-based random access and non-contention-based
random access. Contention-based random access is applicable to all the preceding five events.
Non-contention-based random access is applicable to only events where a handover is
performed or downlink data is received. After a random access procedure is complete, uplink
and downlink transmission can be performed.
An eNodeB supports these two types of random access procedures. In addition, it supports
random access preamble formats 0–3 and PRACH configurations 0–63, as specified in the
3GPP TS 36.211 protocol.
Enhancement
None
Dependency
None
1.2.11 LBFD-002011 Paging

Availability
This feature is
Summary
The purpose of paging is to transmit paging information to a UE in RRC_IDLE mode, and/or
to inform UEs in RRC_IDLE and UEs in RRC_CONNECTED mode of a system information
change.
Benefits
This feature is used to page a UE or inform UEs of system information change.
Description
E-UTRAN initiates the paging procedure by transmitting the paging message, which can be
sent by the MME or eNodeB.

When an eNodeB receives a paging message from an MME over the S1 interface, the eNodeB
shall perform paging of the UE in cells which belong to tracking areas indicated in the "List
of TAIs" Information Element (IE) in the paging message.
When the system information changes, the eNodeB should inform all UEs in the cell through
paging, and should guarantee that every UE can receive the paging message. That is, the
eNodeB should send the paging message on each possible paging occasion throughout a DRX
cycle. Support for UE discontinuous reception must be broadcasted to the entire cell coverage
area and mapped to physical resources.
Enhancement
None
Dependency
None
1.2.12 LBFD-002012 Cell Access Radius up to 15km

Availability
This feature is
 not applicable to Micro
 not applicable to LampSite
Summary
To improve wireless network coverage, 3GPP TS 36.211 has defined four types of preamble
formats (0, 1, 2, 3) for frame structure type 1, among which the basic format 0 corresponds to
15 km of cell access radius.
Benefits
This feature is used in small cell scenarios.
Description
This feature provides operator with support of 15km cell radius. According to 3GPP TS
36.211, four types of preamble format (0, 1, 2, 3) for PRACH are defined to support different
values of cell access radius, as shown in Table 1-4.
Table 1-4 Preamble formats and cell access radius

Preamble Format TCP TSEQ Cell Access Radius
0 About 15 km
1 About 70 km
2 About 30 km

3 About 100 km
For format 0, the supported cell access radius is about 15 km, which is used in small cell
scenarios, and considered as basic cell radius. For format 3, the supported cell access radius is
about 100 km, which is used in large cell scenarios to enhance the system coverage.
Enhancement
None
Dependency
None
1.2.13 LBFD-002023 Admission Control

Availability
This feature is
Summary
Admission control function ensures the system stability and guarantees the QoS performance
by controlling the establishment of the connections within the maximum resource utilization
while satisfying the QoS requirements.
Benefits
Admission control function provides the following benefits:
 Reducing the risk of cell instability by controlling the number of admitted calls
 Achieving an optimal tradeoff between maximizing resource utilization and ensuring
QoS, by avoiding congestion and checking QoS satisfaction
Description
Admission control is a cell-based operation applied to both uplink and downlink. It is one of
the key Radio Resource Management (RRM) functions. Admission control is performed when
there are new incoming calls or incoming handover attempts. In Huawei admission control
solution, system resource limitation and QoS satisfaction ratio are the main considerations for
admission control.
When a new incoming call or incoming handover request arrives, admission control is first to
check the system resource limitation (including hardware resource usage, and system
overload indication). If any of the resources is found to be limited, the new service request
will be rejected.

If the resource limitation checking passes, for Non-GBR service it will be admitted and for
the GBR service it will check the QoS satisfaction ratio The QoS satisfaction ratio is
evaluated based on the QoS Class Identifier (QCI). If the QoS satisfaction ratio for the
evaluated QoS class is better than a predefined admission threshold, the call request would be
accepted; otherwise, it will be rejected.
Note that an incoming handover request has a higher priority than a new incoming call request,
because admission control gives a preference to an existing call (handover request) over a
new call.
The Allocation/Retention Priority (ARP) can be used to classify Gold, Silver, and Bronze
categories with different admission control thresholds. ARP is an attribute of services and is
inherited from Evolved Packet Core (EPC).
Enhancement
 eRAN7.0
In user admission, UE numbers are reserved for privileged UEs to increase the admission
success rate of these UEs. Privileged UEs include emergency UEs and high-priority UEs
whose cause value of RRC connection establishment request is "highPriorityAccess".
Dependency
None
1.2.14 LBFD-002024 Congestion Control

Availability
This feature is
Summary
The congestion control feature is used to adjust the system loading when the system is in
congestion or the QoS cannot be met.
The main goal of congestion control feature is to guarantee the QoS for the admitted services
while achieving the maximum radio resource utilization.
Benefits
The congestion control feature provides the following benefits:
Prevent system from being unstable due to overload;
Guarantee QoS satisfaction rate of services in the system by effectively reduce the system
loading;

Description
This feature is critical to maintain the system stability and deliver acceptable Quality of
Service (QoS) when the system is in congestion.
In eNodeB, congestion control is provided in which a method are introduced:
The method is to release low-priority services to alleviate the overloaded system, where the
priority is determined based on the ARP assigned to the service.
Enhancement
None
Dependency
None
1.2.15 LBFD-002025 Basic Scheduling

Availability
This feature is
Summary
The basic scheduling feature provides three common scheduling algorithms (MAX C/I and
RR and PF). The operator can select either algorithm.
Benefits
This feature provides the flexibility for the operator to select the scheduling algorithm,
considering the system capacity and fairness among the users.
Description
Scheduling algorithm enables the system to decide the resource allocation for each UE during
each TTI. This feature provides different scheduling algorithms, considering the tradeoff
between system capacity and fairness among the users.
There are three scheduling algorithms provided and the operator can decide which algorithm
to take.
 MAX C/I
 Round Robin
 PF (proportional fair)
With MAX C/I, users are scheduled based on their radio channel quality. The radio channel
quality is the only factor to be considered in this algorithm and therefore, the fairness among
users cannot be guaranteed.

With Round Robin, users are scheduled on turn and neglects of their radio quality. So all the
users have the same chance to get the resource and the fairness among uses is guaranteed. But
the system capacity is lowest among three scheduling algorithms.
With PF, users are scheduled according to the value of R/r, where R is the maximum data rate
corresponding to the channel quality, and r is the average data rate of the user. The PF
scheduler, based on the radio channel quality of an individual user, provides the user with an
average throughput proportional to its average channel quality. This algorithm is typically
used by a wireless system to achieve a moderate cell capacity while to ensure fairness among
users.
Enhancement
 In eRAN2.0
Round Robin is added in this feature.
Dependency
 Other features
This feature does not work with the following eRAN features:
LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB).
1.2.16 LBFD-002026 Uplink Power Control

Availability
This feature is:
Summary
Uplink Power Control is a mandatory feature for an LTE system. This feature allows the
eNodeB to control the uplink transmit power of UEs, whilst reducing the interference with the
neighboring cells to increase system throughput. Uplink power control is applicable to
physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH),
sounding reference signal (SRS), and physical random access channel (PRACH).
Benefits
Uplink power control can reduce the interference between neighboring cells by carefully
controlling the transmit power of UEs and increase the overall throughput of an LTE system.
Uplink power control can also ensure the quality of services, for example, by reducing the
block error rate (BLER). In addition, uplink power control can reduce the power consumption
of UEs.
Description
Uplink power control is one of the most important features for an LTE system. Based on fine
control over the UE transmit power, the interference with the neighboring cells can be

reduced to increase the overall system throughput. Uplink power control includes PUSCH
power control, PUCCH power control, SRS power control, and PRACH power control.
PUSCH power control includes power adjustment for both dynamic scheduling and
semi-persistent scheduling.
For dynamic scheduling:
 Based on the difference between the estimated transmit power spectrum density (PSD)
and the target PSD, the transmit power of the PUSCH is periodically adjusted according
to channel environment changes. If the estimated PSD is greater than the target PSD, the
eNodeB sends a TPC command that orders a decrease of the transmit power. If the
estimated PSD is less than the target PSD, the eNodeB sends a TPC command that
orders an increase of the transmit power.
For semi-persistent scheduling:
 In semi-persistent scheduling, based on the difference between the measured IBLER and
the target IBLER, the transmit power of the PUSCH is periodically adjusted according to
channel environment changes. If the measured IBLER is greater than the target IBLER,
the eNodeB sends a TPC command to the UE that orders an increase of the transmit
power. If the measured IBLER is less than the target IBLER, the eNodeB sends a TPC
command to the UE that orders a decrease of the transmit power.
 The PUSCH TPC commands for multiple VoLTE UEs are sent to the UEs through DCI
Format 3 or 3A, reducing PDCCH signaling overheads.
For PUCCH power control:
 Based on the difference between the measured SINR and the target SINR, the transmit
power of the PUCCH is periodically adjusted according to channel environment changes.
If the measured SINR is greater than the target SINR, the eNodeB sends a TPC
command that orders a decrease of the transmit power. If the measured SINR is less than
the target SINR, the eNodeB sends a TPC command that orders an increase of the
transmit power.
Uplink SRS power control employs a power control mechanism similar to PUSCH power
control with identical parameter settings. Note that the initial power is calculated in the same
way as PUSCH, except that a power offset configured by RRC is added.
In PRACH power control, the UE calculates the transmit power for the initial random access
(RA) preamble based on the estimated downlink path loss and the "expected received power
from UE at eNodeB" obtained by monitoring the broadcast channel. If the RA preamble
attempt fails (for example, no RA preamble response is received from the eNodeB), the UE
increases the transmit power for the next RA preamble attempt based on the settings
configured by the RRC layer.
Enhancement
 eRAN11.1
Initial fast PUCCH power control is introduced to rapidly decrease the PUCCH power of
newly admitted UEs. This ensures that the PUCCH power converges on the target value
quickly, decreases PUCCH interference between neighboring cells, and increases
downlink throughput.
Dependency
None

1.2.17 LBFD-081101 PUCCH Outer Loop Power Control

Availability
This feature is:
 Not applicable to Micro.
Summary
This feature adjusts the target signal to interference plus noise ratio (SINRTarget) of PUCCH
format 1x based on the difference between the measured bit error rate (BER) and target BER
(BERTarget) of PUCCH format 2x to improve the demodulation performance of PUCCH
format 2x.
Benefits
This feature increases downlink throughput by improving the demodulation performance of
PUCCH format 2x in heavy load scenarios.
Description
Outer-loop power control for the PUCCH is controlled by the
CellAlgoSwitch.UlPcAlgoSwitch parameter.
When OuterLoopPucchSwitch of this parameter is selected, this feature dynamically adjusts
the SINRTarget for inner-loop power control of PUCCH format 1x based on the difference
between the measured BER and BERTarget of PUCCH format 2x. This feature implements
PUCCH power control based on channel status. It ensures the demodulation performance of
PUCCH format 2x when PUCCH format 2x experiences higher interference than PUCCH
format 1x.
 If the measured BER is greater than the BERTarget, this feature increases the SINRTarget.
 If the measured BER is equal to the BERTarget, this feature does not change the SINRTarget.
 If the measured BER is less than the BERTarget, this feature decreases the SINRTarget.
Enhancement
None
Dependency
 eNodeB
LBBPc and BTS3202E do not support this feature.
 eCoordinator
None
 UE
None
 Transport network

None
 Core network
None
 OSS
None
 Other features
None
 Others
It is recommended that outer-loop power control for the PUCCH be used together with
inner-loop power control for the PUCCH.
1.2.18 LBFD-002016 Dynamic Downlink Power Allocation

Availability
This feature is:
 Applicable to LampSite from eRAN6.0
Summary
Dynamic Downlink Power Allocation allows an eNodeB to dynamically set the transmitting
power at downlink channels to reduce power consumption while maintaining the quality of
radio links. It provides flexible power allocation for downlink channels based on the user's
channel quality and maintains acceptable quality of the downlink connections.
Benefits
This feature allows flexible power allocation for downlink channels based on the user's
channel quality and maintains acceptable quality of the downlink connections. Therefore, it
can improve the edge user throughput and transmission power usage.
Description
The LTE downlink power allocation consists of several parts corresponding to different types
of downlink channels, such as Physical Downlink Control Channel (PDCCH), Physical
HARQ Indicator Channel (PHICH), Physical Broadcast Channel (PBCH), and Physical
Control Format Indicator Channel (PCFICH).
 A Fixed power setting is performed for the cell-specific reference signal, synchronization
signal, PBCH, PCFICH, and channels carrying common information of the cell such as
PDCCH; since the transmitting power of those signals and channels are needed to ensure
the downlink coverage of the cell.
 SINRRS estimation is based on the CQI report. Based on the difference between the
estimated SINRRS and SINRTarget, the transmitting power of the PHICH is periodically
adjusted according to the path loss and shading. If the estimated SINRRS is less than the
SINRTarget, the transmit power is increased. If SINRRS is smaller than SINRTarget, the
transmitting power is increased. In dynamic scheduling, the transmit power of the

PDCCH is periodically adjusted based on DTX. If the DTX does not meet system
requirements, the transmit power increases.
Enhancement
 eRAN2.0
PDCCH dynamic power control is optimized.
Dependency
None
1.2.19 LBFD-002017 DRX

Availability
This feature is:
Summary
The discontinuous reception (DRX) feature allows a UE in RRC_CONNECTED mode to turn
on or off its receiver based on the configuration delivered by the eNodeB. The UE can receive
data and signaling from the network only when the receiver is turned on.
Benefits
This feature is used to save UE power.
Description
In DRX mode, the UE can be in the active or sleep state. In the active state, the UE monitors
the PDCCH to see whether there is downlink data from the network.
Switching between active and sleep states depends on how the related timers are set, whether
the buffer for HARQ is empty, and whether the UE is in a random access procedure. The
related timers include DRX Inactivity Timer, Contention Resolution Timer, and DRX
Retransmission Timer.
DRX can also be used with the automatic neighbor relation (ANR) feature for cell global
identification (CGI) measurement.
Enhancement
 eRAN3.0
This version supports a maximum of 320 ms long cycles while the earlier versions
support only a maximum of 40 ms long cycles.
 eRAN11.1
Usually, if a UE sends a scheduling request indicator (SRI) to the eNodeB during sleep
time, the UE will enter the active state and the UE power consumption cannot be further

reduced. The current version supports the reconfiguration of SRI offset for DRX. This
function reduces the probability that the UE sends an SRI during sleep time and achieves
a better power saving effect.
Dependency
None
1.2.20 LBFD-002018 Mobility Management

1.2.20.1 LBFD-00201801 Coverage Based Intra-frequency Handover
Availability
This feature is
Summary
Handover functionality is important in any cellular telecommunications network. It is
performed to ensure no disruption to services. Handover plays a significant role in LTE
system performance since its main purpose is to decrease the communication delay, enlarge
the coverage and then enhance the system performance.
Intra-Frequency Handover enables a UE in RRC-CONNECTED mode to be served
continuously when it moves across different cells that are operating at the same frequency.
Benefits
The coverage-based intra-frequency handover feature provides supplementary coverage in
intra-frequency LTE systems to prevent call drop, enable seamless coverage and therefore
improve the network performance and end user experience.
Description
This feature is one of the fundamental functions of an LTE system. The purpose of handover
is to ensure that a UE in RRC-CONNECTED mode is served continuously when it moves.
Handover in LTE is characterized by the handover procedure in which the original connection
is released before a new connection is set up.
Intra-frequency handover refers to the handover between cells operating at the same
frequency band. It can be triggered by coverage or load. In eRAN1.0, the coverage-based
intra-frequency handover is supported.
The intra-frequency handover procedure can be divided into three phases: handover
measurement, handover decision, and handover execution.
E-UTRAN configures the handover-related measurement through the RRC Connection
Reconfiguration message. The UE could measure either Reference Signal Received Power
(RSRP) or Reference Signal Received Quality (RSRQ) for intra-frequency handover.

Upon receiving a measurement report from the UE, the eNodeB makes a handover decision
according to certain triggering criteria. If a handover is required, the handover execution
procedure will be invoked and the UE will be handed over from the source eNodeB to the
target eNodeB. Huawei eRAN1.0 follows the intra-frequency handover procedures specified
in 3GPP TS 36.300.
The following scenarios are considered in the intra-frequency handover:
 Handover between two cells configured in the same eNodeB. No external neighbor cell
is needed. This scenario is not applicable to Micro eNodeB because Micro eNodeB only
supports one cell.
 Handover between two cells configured in different eNodeBs with an X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUEST message
over the X2 interface.
 Handover between two cells configured in different eNodeBs with no X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUIRED message
over the S1 interface.
Enhancement
 In eRAN2.2
Each PLMN id of eNodeB will have its own PLMN list; each PLMN list can contain at
most 8 PLMN Identities; PLMN list is used as an access list for serving cell to judge
whether UE could handover to target cell in Inter-PLMN handover; Other cell, whose
PLMN ids are all different with serving cell PLMN id in which UE is located and at
same time are not in its PLMN list, will not be considered as target cell in handover
process for this UE.
Dependency
None
1.2.20.2 LBFD-00201802 Coverage Based Inter-frequency Handover
Availability
This feature is
Summary
Inter-Frequency Handover enables a UE in RRC-CONNECTED mode to be served
continuously when it moves across different cells that are operating at different frequencies.
Benefits
The coverage-based inter-frequency handover provides supplementary coverage in
inter-frequency LTE systems to prevent call drop, enable seamless coverage, and therefore
improve the network performance and end user experience.

Description
This feature is one of the fundamental functions for an LTE system. The purpose of
inter-frequency handover is to ensure that a UE in RRC-CONNECTED mode is served
continuously when it moves across different cells operating at different frequencies.
The inter-frequency handover procedure can be divided into four phases: measurement
triggering, handover measurement, handover decision, and handover execution.
In inter-frequency handover, neighboring cell measurements are inter-frequency
measurements. The measurement is gap assisted for UEs with one RF receiver. The
measurement is triggered by an event A2 and stopped by an event A1, based on the
monitoring on the value of RSRP or RSRQ.
In inter-frequency handover, the UE sends measurement reports to the eNodeB when the
RSRP or RSRQ meets the criteria set in the measurement configuration.
Upon receiving a measurement report from the UE, the eNodeB makes a handover decision.
If the measurement meets the handover criteria, the eNodeB will perform the corresponding
inter-frequency handover as specified in TS 36.300.
The following inter-frequency handover scenarios are applicable:
 Handover between two cells configured in the same eNodeB. In this case, the UE
performs the handover between two cells configured in the same eNodeB and no
external interface is required. This scenario is not applicable to Micro eNodeB because
Micro eNodeB only supports one cell.
 Handover between two cells configured in different eNodeBs with an X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUEST message
over the X2 interface.
 Handover between two cells configured in different eNodeBs with no X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUIRED message
over the S1 interface.
Enhancement
 eRAN2.2
 eRAN3.0
The inter-frequency handover based on UL power is supported. It guarantees service
continuity in uplink limited power when a UE moves to the cell edge.
 eRAN6.0
The urgent redirection function has been provided by this feature. After a UE accesses a
cell, the eNodeB delivers two sets of event A2 configurations. One is used for triggering
measurements, and the other is used for triggering urgent redirection. The triggering of
event A2 for urgent redirection indicates that the signal quality in the serving cell has
become too poor to provide services for the UE. In this case, the eNodeB blindly
redirects the UE to a neighboring GERAN, UTRAN, or E-UTRAN cell.

Dependency
 UE
UE should support for inter-frequency Gap measurements
1.2.20.3 LBFD-00201803 Cell Selection and Re-selection
Availability
This feature is
Summary
Cell selection/reselection is a mechanism for UE in idle mode to select/reselect a cell to camp
on and to receive the most appropriate service support upon session activation in LTE
systems.
Benefits
This feature provides a mechanism for UE in idle mode to select/reselect a cell to camp on by
supplementary coverage in LTE systems.
This feature facilitates the automatic selection of the network for UE in idle mode and avoids
the complexity of manual operations.
The UE is always bound to a relatively good cell to obtain better service quality.
Description
When UE selects a PLMN or transition from RRC-CONNECTED to RRC-IDLE, cell
selection is required. The Non-Access Stratum (NAS) can determine the RAT(s) in which the
cell selection should be performed, for instance, by indicating the RAT(s) associated with the
selected PLMN and by maintaining a list of forbidden registration areas and a list of
equivalent PLMN. The UE shall select a suitable cell based on idle mode measurements and
cell selection criteria.
UE in RRC_IDLE can perform cell reselection if UE find a cell with a better radio
environment. When camping on a cell, UE shall regularly search for a better cell according to
the cell reselection criteria. If a better cell is found, that cell is reselected.
Absolute priorities of different E-UTRAN frequencies can be provided to the UE in the
system information and optionally in the RRC message releasing the RRC connection.
Compared with Macro eNodeBs, higher priorities will be set for frequencies of Micro
eNodeBs so that the UE prefers to camp on Micro eNodeB cells.
In case a Micro cell is on the same frequency with a Macro cell, the eNodeB configuration
also makes the cell selection or reselection to the Micro cell easier than to the Macro cell.
Enhancement
None

Dependency
None
1.2.20.4 LBFD-00201804 Distance Based Inter-frequency Handover
Availability
This feature is
Summary
Huawei LTE eNodeB supports distance based inter-frequency handover.
Benefits
Better End user Experience (Always Best Connected)
Description
When moving around away from the serving eNodeB with frequency F1, the user may still
experience a relatively strong signal from F1 so that the condition of A2 event can't be
satisfied to trigger an inter-frequency handover, even though the neighboring inter-frequency
eNodeB signal is much better than F1. In order to make the user always keep the best
connection, a distance based inter-frequency handover is employed.
When distance based HO algorithm is used, eNodeB should continuously measure the
distance to each UE based on the TA measurement, once the distance exceeds an operator
configured distance threshold, inter-frequency gap measurements of neighboring eNodeB will
be triggered to find an optimal handover candidate to improve user performance
Enhancement
None
Dependency
 UE
1.2.20.5 LBFD-00201805 Service Based Inter-frequency Handover
Availability
This feature is

Summary
Huawei LTE eNodeB supports service based inter-frequency handover. UE with specific
service would be moved to the cell of the configured frequency.
Benefits
Service Based Inter-frequency Handover is used to improve efficiency and capacity of whole
system.
Description
The operator could configure specific group of policies for service-based inter-frequency
handovers. Each group will be associated with a QCI. The default policy is to prohibit
handovers. A bearer of QCI 5 and QCIs of default bearers are not recommended to be
configured to allow handovers.
When service based Inter-frequency handover algorithm is used, eNodeB should continuously
monitor the UE service state. If QCI (each type of service is mapping to a QCI index) is
changed, inter-frequency measurements of configured group will be triggered to find an
optimal handover candidate.
Enhancement
None
Dependency
 UE
1.2.21 LBFD-002020 Antenna Configuration

1.2.21.1 LBFD-00202001 UL 2-Antenna Receive Diversity
Availability
This feature is
Summary
Receive diversity is a common type of multiple antennas technology to improve signal
reception and to combat signal fading and interference. It improves network capacity and data
rates. Huawei eNodeB supports both RX diversity mode and no RX diversity mode.
Benefits
This feature can improve the receiver sensitivity and uplink coverage.

Description
Receive diversity is a technique to monitor signals at multiple frequencies from the same
signal source, or to monitor time division signals at the same frequency from the same signal
source, in order to combat signal fading and interference.
Receive diversity is one way to enhance the reception over uplink channels, including
PUSCH, PUCCH, PRACH, and SRS.
Huawei eNodeB supports both RX diversity mode and no RX diversity mode. In RX diversity
mode, the eNodeB can be configured with 2 antennas (2-way).
In RX diversity mode, the eNodeB does not require additional devices and works with the
Maximum-Ratio Combining (MRC) or Interference Rejection Combining (IRC) algorithms.
Compared with 1-way reception without RX diversity, 2-way RX diversity requires twice the
number of RX channels. The number of RX channels depends on the settings of the antenna
connectors.
Enhancement
None
Dependency
 eNodeB
RX diversity requires the eNodeB to provide enough RF channels and demodulation
resources that can match the number of diversity antennas.
1.2.22 LBFD-002021 Reliability

1.2.22.1 LBFD-00202101 Main Processing and Transport Unit Cold Backup
Availability
This feature is
Summary
The feature provides cold backup capability to the LMPT (LTE Main Processing and
Transport Unit) or UMPT(Universal Main Processing and Transport Unit) board of Huawei
eNodeB.
Benefits
If there is only one LMPT board configured in the system, the failure of this board will cause
long-time service outage of the base station. However, service can be automatically recovered
within 3 minutes with LMPT redundancy. LMPT redundancy design is helpful for eNodeB to
reach higher availability, greater than 99.999%.

Description
Two LMPT boards are configured in the system. When the system starts, the arbitrator
module located on each LMPT board decides which board becomes active or standby. The
active board handles several control and operation functions and provides for the most
common transport network connectivity requirements. When it detects hardware or software
faults on the board, it will switch to the standby state. Meanwhile, the standby board switches
to the active state. The service can be automatically recovered within 3 minutes. The operator
can also manually trigger LMPT switchover by EMS (Element Management System).
Enhancement
 In eRAN3.0
The UMPT board also supports cold backup capability.
Dependency
 eNodeB
To support this feature, the eNodeB must be configured with two LMPT/UMPT boards.
1.2.22.2 LBFD-00202102 Cell Re-build Between Baseband Processing

Units
Availability
This feature is
Summary
In Huawei eNodeB, multiple LTE Baseband Processing (LBBP) boards can be configured to
serve multiple cells. When an LBBP fails, the cell/cells served by the failed LBBP can be
rebuilt on another operating LBBP with spare resources or on a backup LBBP if available.
Benefits
This feature ensures the cell coverage by cell re-establishment and improves the system
reliability in case of an LBBP failure.
Description
Generally an eNodeB is equipped with multiple LBBP boards that serve multiple cells. The
following figures show the example of configurations of 3*10M 2T2R with CPRI interface
backup respectively.

Figure 1-1 3*10M 2T2R
When an LBBP board fails due to a hardware fault, communication interface failure, or other
faults, the eNodeB is able to detect and locate the failure and tries to choose a target LBBP
board on which the cell/cells are to be rebuilt. The target LBBP should have a CPRI
connection with the RRU serving the cell/cells involved, as shown in the preceding figures.
The selection of a target LBBP board mainly depends on the spare resources at the potential
target LBBP board.
Enhancement
None
Dependency
 eNodeB
The eNodeB should be equipped with at least two LBBP boards.

1.2.22.3 LBFD-00202103 SCTP Multi-homing
Availability
This feature is
Summary
Stream Control Transmission Protocol (SCTP) is the signaling bearer protocol of the S1/X2
interface. It provides the similar service features of TCP and UDP, but ensures reliability,
in-sequence transport of messages with congestion control, and offers multi-homing support
for fault recovery by failover between redundant network paths.
Benefits
This feature provides reliability of signaling bearers.
Description
Figure 1-2 Stream Control Transmission Protocol
SCTP is the signaling bearer protocol of the S1/X2 interface. With this function, one SCTP
association has two paths (IP-couple). An SCTP association is the logical channel between
two SCTP ends. The two paths in one SCTP association are a master path and a slave path.
Generally, the master path is active. When the master path fails, the slave path is activated.
Enhancement
None
Dependency
None

1.2.22.4 LBFD-00202104 Intra-baseband Card Resource Pool (user level/cell

level)
Availability
This feature is
Summary
In this feature, the processing resources in a baseband processing board of Huawei eNodeB
are aggregated into a baseband resource pool in which all they are shared for the load
processing.
Benefits
This feature ensures the stability and robustness of eNodeB, in which the processing resources
are aggregated into a pool to share all load and therefore to prevent individual resource from
outage due to overload. The feature also improves the average cell capacity of eNodeB.
Description
The baseband processing board of Huawei eNodeB consists of several processing resources. A
baseband processing board is capable of supporting multiple cells depending on the
bandwidths. In this feature, the processing resources are aggregated into a resource pool to be
shared for user data processing by multiple cells. A new user will be assigned to a resource
which has the least load. In an occasional situation, if a resource should be overloaded or in
outage, the eNodeB can reduce the load of the individual resource or move its existing users
to other resources.
Enhancement
None
Dependency
 eNodeB
This feature is only applicable to LBBPc.
1.2.23 LBFD-002022 Static Inter-Cell Interference Coordination

1.2.23.1 LBFD-00202201 Downlink Static Inter-Cell Interference
Coordination
Availability
This feature is:

 Not available in micro eNodeBs.

Summary
This feature reduces the downlink inter-cell interference. The basic principle is that the cell
edge users of different neighboring cells are allocated with different starting positions of
frequency-domain resources so as to mitigate interference.
Benefits
This feature reduces the downlink inter-cell interference in lightly loaded scenarios, thereby
improving spectral efficiency and downlink throughput. It also reduces the interference
between the paging messages for UEs in different cells, and the paging success rate is
improved as a result.
Description
In an LTE system, a cell can use the entire system frequency band and therefore it is
inevitable to cause inter-cell interference for a multi-cell deployment. It is important to
develop an efficient solution to mitigate the inter-cell interference in the multi-cell
environment in order to achieve the performance target.
A common solution is to select different starting positions of resource block groups (RBGs)
for neighboring cells in lightly loaded and multi-cell scenarios. In this way, inter-cell
interference is reduced, and spectral efficiency is improved. When a cell suffers unevenly
distributed intra-frequency inter-RAT interference in the downlink, this feature ensures that,
as far as possible, the RBGs allocated in this cell do not overlap with those on the frequency
band with intra-frequency inter-RAT interference, reducing the impact of intra-frequency
inter-RAT interference on network performance.
This feature also enables an eNodeB to allocate RBs in different positions for paging
messages to the cells it serves to reduce interference between paging messages in the cells,
thereby improving paging message demodulation performance and increasing the paging
success rate.
Enhancement
None
Dependency
None
1.2.23.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination
Availability
This feature is:

Summary
This feature reduces the uplink inter-cell interference. The basic principle is that the cell edge
users of different neighboring cells are allocated with different starting positions of
frequency-domain resources so as to mitigate interference.
Benefits
This feature reduces inter-cell interference in lightly loaded scenarios and increases uplink
throughput.
Description
In an LTE system, a cell can use the entire system frequency band and therefore it is
inevitable to cause inter-cell interference for a multi-cell deployment. It is important to
develop an efficient solution to mitigate the inter-cell interference in the multi-cell
environment in order to achieve the performance target.
A common solution is to select different starting positions of frequency-domain resources for
neighboring cells in lightly loaded and multi-cell scenarios. In this way, inter-cell interference
is reduced, and uplink throughput is increased.
Enhancement
None
Dependency
None
1.2.24 LBFD-002027 Support of UE Category 1

Availability
This feature is
Summary
E-UTRAN needs to respect the signaled UE radio access capability parameters when
configuring the UE and when scheduling the UE. There are five categories defined in the
protocol. This feature can enable base station to support UE category 1.
Benefits
This feature can enable base station to support UE category 1.

Description
E-UTRAN needs to respect the signaled UE radio access capability parameters when
configuring the UE and when scheduling the UE. There are five categories defined in the
protocol. This feature can enable base station to support UE category 1.
Table 1-5 Downlink physical layer parameter values set by the field UE-Category
UE Category Maximum Maximum Total number of Maximum
number of number of bits soft channel number of
DL-SCH of a DL-SCH bits supported
transport blocks transport block layers for
bits received received within spatial
within a TTI a TTI multiplexing in
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
Table 1-6 Uplink physical layer parameter values set by the field UE-Category
UE Category Maximum number of bits of Support for 64QAM in UL
an UL-SCH 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
Table 1-7 Total layer 2 buffer sizes set by the field UE-Category
UE Category Total layer 2 buffer size [KBytes]
Category 1 150
Category 2 700
Category 3 1400
Category 4 1900
Category 5 3500

Enhancement
None
Dependency
 UE
UE should support the same category as eNodeB.
1.2.25 LBFD-002028 Emergency Call

Availability
This feature is
Summary
The emergency call service is an operator-assisted service that connects a caller in a
life-threatening or time-critical situation to an emergency service organization.
Benefits
This feature provides all users, even those without SIM, a prioritized connection to an
emergency service organization.
Description
The emergency Call service is an operator-assisted service that connects a caller in a
life-threatening or time-critical situation to an emergency service organization such as police,
hospital and fire station.
New features in E-UTRAN to support emergency call are as follows:
 Support of identifying emergency call users
 Support of special processing such as access class barring and priority handling for the
network access and mobility management
 Support of location service for emergency call users. This function depends on the
feature LOFD-001047 LoCation Services (LCS).
Admission of an emergency call is prioritized over other ongoing sessions in the eNodeB to
enable call completion. Regardless of network features/services activated in the network (for
example, unconditional call-forwarding, or incoming call barring), the Public Safety
Answering Point (PSAP, used in US)/ Emergency Centre (EC, used in Europe) is able to get
emergency caller's location by means of LCS and call back the caller once an emergency call
has been placed. The emergency call, served on LTE with multi-mode terminal, fallbacks to
UMTS or GSM depending upon LTE VoIP support.
Four types of users are permitted to initiate an emergency call:

 Common user: normal subscriber

 Common restricted user: normal subscriber, whose calls are restricted for some reasons
(for example, out of coverage of own PLMN)
 Restricted user with SIM card: User, whose SIM card fails to authenticate, uses IMEI
(International Mobile Equipment Identity) to initiate an emergency call.
 Restricted user without SIM card: User, without SIM card, uses IMEI to initiate an
emergency call
This feature supports 911 Emergency Calls (North America) / 112 Emergency Calls (Europe)
in its SAE/LTE network as defined by 3GPP specification.
Enhancement
None
Dependency
 UE
UE should support IMS based voice service on LTE or voice service on 2G/3G.
 CN
The emergency call should be supported in the core network.
 Other features
The location service for emergency call users function depends on the optional feature
LOFD-001047 LoCation Services (LCS).
 Others
If IMS is not deployed, the support of the optional feature CS Fallback to
GERAN/UTRAN/CDMA2000 will be needed.
1.2.26 LBFD-002029 Earthquake and Tsunami Warning System

(ETWS)
Availability
This feature is
Summary
When an event occurs e.g. an Earthquake, Warning Notification Providers produce Warning
Notification to PLMN operator, PLMN operators distribute Warning Notifications to users by
utilizing Earthquake and Tsunami Warning System(ETWS).
Benefits
 Quick Warning Notification delivery after the occurrence of Earthquake or Tsunami.
 Accurate Warning Notification delivery.

Description
When the occurrence of a disaster e.g. an Earthquake, is detected, Warning Notification
Provider e.g. local government, is responsible for notifying the public as soon as possible.
Figure 1-3 Overview of Earthquake and Tsunami Warning System
Warning Notification Provider may publish Primary Notification to PLMN firstly, the content
of the Primary Notification only includes the most urgent information related to the disaster.
The Notification Area where the Warning Notification is expected to be distributed is also
specified by Warning Notification Provider. While the Primary Notification is delivered by
PLMN to users in the Notification Area, The UE which detects the delivery of the Primary
Notification alerts the user e.g. by sound and vibration.
Warning Notification Provider may publish a Secondary Notification to PLMN secondly. The
content of the Secondary Notification may include additional information, such as instructions
on what to do / where to get help as long as the emergency lasts. The Notification Area is also
specified by Warning Notification Provider. While the Secondary Notification is delivered by
PLMN to users in the Notification Area, The UE which detects the delivery of the Secondary
Notification alerts the users e.g. by specified buzzer and vibration.
While Warning Notification Provider specifies that the Notification should be delivered
periodically, Warning Notification Provider may request the PLMN to stop to disseminate the
notification.
Enhancement
None
Dependency
 UE
UE should support ETWS
 CN
Core Network should support ETWS
1.2.27 LBFD-002031 Support of aperiodic CQI reports

Availability
This feature is

Summary
Aperiodic CQI is reported on PUSCH and the UE can be configured to report periodic CQI
and aperiodic CQI together or individually.
Benefits
Aperiodic CQI can offer more detailed channel quality information which may make the
downlink spectrum efficiency better.
Description
Aperiodic CQI is triggered by the UL scheduler periodically when needed and the CQI
Request field in the UL grant is used to indicate the aperiodic CQI report. Higher
layer-configured reporting modes will be supported, and the given mode is configured by the
RRC.
Higher layer-configured
 Mode 3-0: A wideband CQI and one sub-band CQI for each sub-band are reported.
 Mode 3-1: A wideband CQI and one sub-band CQI for each sub-band per codeword are
reported. A wideband PMI is also reported.
Huawei eNodeB supports aperiodic CQI reporting , the reporting interval depends on the UL
load. The interval will be lengthened adaptively when the UL load is high.
Enhancement
None
Dependency
None
1.2.28 LBFD-002032 Extended-QCI

Availability
This feature is
Summary
Huawei supports extended QoS Class Identifier (extended QCI) (255 QCI including 9
standard QCI defined in 3GPP). Extended QCI can be used as operator defined QCI to
support customized non-GBR service. Extended QCI index can be defined by operator and
need SAE to support it.

Benefits
It can be configurable flexibly by operator and meet multi need of operator who wants to
operate the differentiated service.
Description
This feature supports extended QCI, which means that MME send one extended QCI index in
RAB assignment message. The eNodeB can configure these extended QCI and can be
assigned radio resource differently according to the different QCI number and different
scheduling weight factor.
The extended QCI can be configurable with Gold, Silver, and Bronze, which is the same as
the ARP.
Huawei currently supports extended non-GBR QCI, and the configurable scenario is that
eNodeB get the QCI index firstly, set the ARP and QoS parameter ( PDB, PLER, schedule
weight) related with QCI index.
Enhancement
 eRAN8.1
eNodeBs now support the mapping between user scheduling weight factors and
combinations of ARP and QCI.
Users can be classified into gold, silver, and copper levels by ARP. The scheduling
weight factors for different user levels can be mapped to QCIs 6 through 9. This
mapping takes precedence over the mapping of ARP-irrelevant scheduling weight factors
to the QCIs.
Dependency
 Others
It relates with SAE.
1.2.29 LBFD-002033 SCTP Congestion Control

Availability
This feature is
Summary
If a network has heavy traffic, Stream Control Transmission Protocol (SCTP) congestion
control can be used to prevent SCTP association exceptions caused by SCTP signaling
congestion. SCTP congestion control is triggered when the SCTP resources, including the
central processing unit (CPU) and buffer resources, are insufficient.
In eRAN6.0, only downlink SCTP Congestion Control is supported.

Benefits
This feature enhances the signaling message handling robustness in scenarios where the
network is heavily loaded.
Description
In an LTE system, control plane messages are used to ensure that the E-UTRAN runs properly
and service connections are set up and released properly. The reliability of control plane
messages plays a fundamental role in the LTE system. S1 signaling messages between an
eNodeB and an MME and X2 signaling messages between eNodeBs are transmitted in
compliance with SCTP.
As smartphones and applications such as instant messaging (IM) are popularized, signaling
traffic increases sharply. SCTP resources, including the CPU and buffer resources, become a
bottleneck in scenarios where the service traffic and signaling traffic are heavy. In such
scenarios, SCTP congestion control helps to maintain signaling transmission robustness and
reduce impacts on service key performance indicators (KPIs).
The SCTP congestion control procedure includes SCTP congestion detection, back-pressure,
and signaling congestion control at the application layer. The eNodeB determines whether
SCTP signaling is congested based on the SCTP resource usage. If downlink SCTP signaling
is congested, the eNodeB informs EPC by normal SCTP mechanism. EPC side decreases
signaling traffic to reduce signaling load of eNodeB by congestion control procedure. If
uplink SCTP signaling is congested, the eNodeB informs the application layer of the
congestion by back-pressure.
Enhancement
None
Dependency
 CN
Downlink SCTP control depends on the support of congestion control procedure in EPC
side as defined in RFC 4960.
1.2.30 LBFD-002034 RRU Channel Cross Connection Under

MIMO
Availability
This feature is
Summary
This feature enables eNodeB provides service to one sector through two RRUs. When one
RRU fails, it will not lead to the total outage of that sector.
This feature is changed to basic feature from optional feature since eRAN6.0.

Benefits
When deployed in the field, perhaps the RRU is installed on top of the tower or the base
station is installed in inaccessible area. The equipment cannot be easily maintained. In this
case, if one RRU fails, the sector will be out of service for a long time. However, with this
new scheme, one RRU failure will not cause the outage of the whole sector so that the service
coverage can be ensured.
By reliability prediction, the availability of RRU will increase from 5 nine's (0.99999844) to 6
nine's (0.99999932). In addition, this scheme does not increase any hardware cost.
Description
This scheme can greatly increase equipment reliability with no additional hardware cost. By
utilizing the independency of the MIMO channels, the sector service can be processed
through different RRUs. When one RRU fails, the other RRU can still process the service data
of that sector so the total outage of that sector will not occur. Meanwhile, the performance of
that faulty sector will be decreased. This scheme can be applied in multiple sectors
configuration and MIMO architecture.
Taking 2T2R RRU for example, there are three RRUs (from left to right which are RRU1,
RRU2 and RRU3) The left chart is for the legacy scheme and the right one is for the load
sharing scheme. Antenna 1 is connected to RRU1 and RRU2. Antenna 2 is connected to
RRU2 and RRU3. Antenna 3 is connected to RRU3 and RRU1. In the legacy scheme, when
one RRU fails, the sector connected is totally out of service. While applying MIMO load
sharing scheme, when one RRU, for example RRU1 fails, the other antenna of that sector is
connected to RRU2, service in that faulty sector can still be processed. In the meanwhile, that
operation mode is changed from 2T2R to 1T1R and the performance decreases (such as in
coverage area or throughput). On the other hand, as sector 3 uses one transmit/receive channel
of RRU1, the performance decreases as well. Moreover, because the antenna mode has
change for both sector1 and sector3, it is necessary to reconfigure the cell data, which will
cause 20s outage of service.
Figure 1-4 RRU channel cross connection under MIMO

Figure 1-5 Comparing with no MIMO load Sharing
Enhancement
None
Dependency
 Others
This feature is more suitable for RRUs installed on top of the tower.
1.2.31 LBFD-060101 Optimization of Periodic and Aperiodic CQI

Reporting
Availability
This feature is
Summary
This feature is one of the basic scheduling features. It involves optimization of periodic
channel quality indicator (CQI) reporting and enhancement of aperiodic CQI reporting.
Optimization of periodic CQI reporting prolongs the CQI reporting interval when CQI
reporting period adaptation is enabled.
Enhancement of aperiodic CQI reporting considers the CQI reporting interval and downlink
services. When a UE uses a long CQI reporting interval and performs downlink services,
aperiodic CQI reporting is triggered. The aperiodic CQI reporting interval is shorter than the
periodic CQI reporting interval.

Benefits
Optimization of periodic CQI reporting reduces the consumption of PUCCH resource blocks
(RBs) and therefore makes more RBs available to the PUSCH and increases uplink
throughput.
Enhancement of aperiodic CQI reporting increases the number of CQI reports and downlink
throughput. The downlink gain depends on the UE's CQI measurement performance.
Description
Optimization of periodic CQI reporting prolongs the CQI reporting interval when CQI
reporting period adaptation is enabled. It reduces the consumption of PUCCH RBs and
therefore makes more RBs available to the PUSCH and increases uplink throughput.
Enhancement of aperiodic CQI reporting considers the CQI reporting interval and downlink
services. When a UE uses a long CQI reporting interval and performs downlink services,
aperiodic CQI reporting is triggered. The aperiodic CQI reporting interval is shorter than the
periodic CQI reporting interval. Therefore, enhancement of aperiodic CQI reporting obtains
more CQI reports and achieves higher downlink throughput than periodic CQI reporting.
Enhancement of aperiodic CQI reporting requires additional PDCCH resources.
Enhancement
None
Dependency
None
1.2.32 LBFD-060102 Enhanced UL Frequency Selective Scheduling

Availability
This feature is:
 Applicable to Micro.
 Not applicable to LampSite.
Summary
This feature enables an eNodeB to adaptively select a resource allocation mode based on the
number of UL-synchronized UEs and the number of to-be-scheduled UEs in a cell during
frequency selective scheduling.
Benefits
Interference is reduced and MCSs with higher indexes are used, thereby increasing UE
throughput.

Description
Frequency selective fading occurs due to multipath propagation in radio channel
environments. Frequency selective fading varies slowly with time for a low-mobility UE. In
other words, the fading variance is not great for the UE within the channel coherence time.
SC-FDMA used in the uplink on LTE networks allows resource allocation in sub-bands of
small bandwidths within a large system bandwidth. Channel fading varies with sub-bands. By
leveraging the channel fading variance with sub-bands, frequency selective scheduling
allocates UEs resources on sub-bands with favorable channel quality. Generally, the
distribution of frequency selective fading varies with UEs, that is, the sub-bands with
favorable channel quality for one UE are not completely the same as those with favorable
channel quality for another UE. When each UE is allocated resources on sub-bands with
favorable channel quality, system throughput increases.
When this feature is disabled, an eNodeB uses uplink frequency selective scheduling if the
number of UL-synchronized UEs in a cell is less than or equal to 15 or uses sequential
resource allocation if the number of UL-synchronized UEs in a cell is greater than 15. When
the sequential resource allocation mode is used, UEs experience constant interference because
sequential resource allocation cannot prevent inter-cell interference.
When this feature is enabled, an eNodeB adaptively selects a resource allocation mode based
on the number of UL-synchronized UEs and the number of to-be-scheduled UEs in a cell
during frequency selective scheduling. The adaptive selection reduces interference to UEs and
increases UE throughput.
Enhancement
 eRAN7.0
MCSs are selected based on sub-band SINR for low-mobility UEs during frequency
selective scheduling to increase frequency selective scheduling gains and further increase
the spectral efficiency and throughput for the UEs.
Dependency
 eNodeB
None
1.2.33 LBFD-060103 Enhanced DL Frequency Selective Scheduling

Availability
This feature is:
 Applicable to Micro.
 Applicable to LampSite.
Summary
Multipath propagation of radio signals causes the multipath effect. Radio signals arriving at
the receiver on different paths differ from each other in phase, amplitude, and delay, resulting
in frequency selective fading. To address this issue, the LTE system uses frequency selective
scheduling to improve system performance by leveraging the channel quality difference
between narrow-band frequencies.

Benefits
The transmission of user data on sub-bands with favorable channel quality increases downlink
throughput.
Description
In downlink frequency selective scheduling, an eNodeB calculates the scheduling priorities
based on the subband CQIs reported by UEs and schedules UEs based on the scheduling
priorities of UEs in each subband. As a result, the UEs can be scheduled in the subbands with
the most favorable channel quality.
After downlink frequency selective scheduling is enabled, each resource block group (RBG)
is allocated to the UE with the highest scheduling priority on the corresponding subband,
resulting in an increase in the number of UEs scheduled per TTI. Therefore, it is possible that
more resources are allocated for PDCCH transmissions and fewer resources are available for
PDSCH transmissions, causing a decrease in downlink throughput gains.
In eRAN6.0, the PDCCH symbol number adaptation function is enhanced to balance the
PDCCH symbol number and PDSCH symbol number, enabling frequency selective
scheduling to produce gains in more scenarios.
Enhancement
None
Dependency
None
1.2.34 LBFD-070103 Multi-Band Compatibility Enhancement

Availability
This feature is
Summary
If a cell works at a frequency that belongs to multiple bands, it can be configured as a
multi-band cell.
Benefits
In the case that there are existed different bands in same frequency, UEs support one band can
access a network configured with multiple bands, which can support roaming terminal better.
For example, if a cell is configured with both bands 2 and 25, UEs supporting band 2 or band
25 can access the cell.

Description
According to 3GPP TS 36.331 released before October, 2012, the information about the band
supported by a cell is sent to a UE by using an SIB, and each cell supports only one band. If
the band indicated in the SIB differs from the band supported by the UE, the UE cannot
access the cell.
3GPP TS 36.331, released in October 2012, defines the extended fields for SIBs:
SIB1: contains the multi-band indicator of the serving cell.
SIB2: contains additionalSpectrumEmission of different bands.
SIB5: contains the multi-band indicator of a neighboring cell.
SIB6: contains the multi-band indicator of a UMTS cell.
In LTE FDD eRAN7.0, a cell can work at multiple bands and the preceding types of SIBs are
sent to UEs.
If a UE supports one of the bands at which a cell works, the UE can access the cell.
If a UE supports one of the bands configured for a neighboring cell, the UE can be handed
over to this cell. More candidate cells are therefore available for a UE handover.
If a UTRAN cell is configured with different bands, SIB6 is used to send the band
information to UEs. If a UE supports one of the bands, more candidate cells are available for
inter-RAT cell reselection.
according to 3GPP, the scenario with multi-band Compatibility are:
Frequency Band
700M 12,17
1900M 2, 25
AWS 4, 10
1700M/1800M 3, 9
800M/850M 5, 18, 19, 26, 27
Enhancement
None
Dependency
 UE
UEs must support the parsing and processing of SIBs (SIB1, SIB2, SIB5, and SIB6)
according to the Multi-Band CR used by 3GPP TS 36.331.
 Other features
This feature depends on LBFD-002009 Broadcast of System Information.

1.2.35 LBFD-070101 Uplink Timing Based on PUCCH

Availability
This feature is
Summary
The eNodeB performs uplink timing based on the PUCCH-CQI. CQI stands for channel
quality indicator.
Benefits
Uplink timing based on the PUCCH-CQI eliminates the need to allocate uplink resources
dedicated to uplink timing, thereby improving uplink resource utilization.
Description
Uplink timing is a basic function of the E-UTRAN. In versions earlier than eRAN7.0, uplink
timing based on the sounding reference signal (SRS) or demodulation reference signal
(DMRS) has been used. Uplink timing based on the PUCCH-CQI resource is now introduced
as a supplement.
With this feature, the eNodeB calculates the timing offset by using the PUCCH-CQI. Based
on the results of this calculation, the eNodeB then converts the timing offset into the Timing
Advance Command and sends the command to the UE. The UE uses this information to
adjust the time to transmit uplink signals. The entire process ensures time synchronization
between the UE and the eNodeB.
Enhancement
None
Dependency
 eNodeB
This feature is applicable to neither BTS3202E nor eNodeBs configured with an LBBPc
board.
1.2.36 LBFD-070102 MBR>GBR Configuration

Availability
This feature is

Summary
The eNodeB allows the maximum bit rate (MBR) to be greater than the guaranteed bit rate
(GBR).
Benefits
Setting of the MBR to be greater than the GBR allows applications to take advantage of
additional system capacity when it is available, thereby improving resource utilization and
user experience. For details, see 3GPP TS 23.860.
Description
The definition of MBR allows the increasing real-time services (such as voice and video
services), whose data rates are elastic, to make use of additional network resources that may
be available. The GBR can be set to the minimum data rate at which the real-time services can
be carried, and the MBR can be set to the maximum data rate at which the optimal user
experience is achieved. When the E-UTRAN is not congested and idle network resources are
available, the real-time services carried on the GBR bearers can reach rates between the GBR
and the MBR.
Enhancement
None.
Dependency
None.
1.2.37 LBFD-070105 IoT-based PUSCH Power Control

Availability
This feature is
Summary
When the network is lightly loaded, uplink interference can be mitigated using uplink
frequency selective scheduling or interference-randomization-based scheduling. However,
when the network is heavily loaded in special scenarios such as a concert or soccer match,
neither uplink frequency selective scheduling nor interference-randomization-based
scheduling can effectively mitigate uplink interference. As a result, performance of cell edge
UEs (CEUs) deteriorates.
IoT-based PUSCH Power Control is introduced to decrease inter-cell uplink interference and
improve performance of CEUs in these scenarios. (IoT is short for interference over thermal.)

Benefits
PUSCH power control based on the exchange of overload indications (OIs) between cells
decreases inter-cell uplink interference and increases uplink throughput of CEUs in special
scenarios.
Description
When a heavily-loaded cell detects strong uplink interference, the cell sends UL Interference
Overload Indication to neighboring cells (or sends the LOAD INFORMATION message
containing UL Interference Overload Indication to inter-eNodeB neighboring cells over X2
interfaces). After receiving UL Interference Overload Indication, the neighboring cells adjust
the PUSCH transmit power of UEs in and near the cell center to decrease uplink interference
on their adjacent cells.
In heavily-loaded networks, uplink interference on cells that send UL Interference Overload
Indication decreases, and uplink throughput of CEUs in these cells increases. In the cells that
receive UL Interference Overload Indication, UEs in and near the cell center decrease the
PUSCH transmit power, so uplink throughput of these UEs decreases.
In heavily-loaded networks with strong interference, to better provide LTE services for as
many UEs as possible in special scenarios, uplink coverage of neighboring cells can be
enhanced and user experience of CEUs can be improved at the cost of performance of UEs in
and near the center of a local cell.
Enhancement
None
Dependency
None
1.2.38 LBFD-070106 PDSCH Efficiency Improvement

Availability
This feature is:
Summary
In LTE networks, surplus PDSCH resources are available in scenarios where the maximum
number of transmitted bits in each TTI is less than the supporting bandwidth or traffic volume
to be transmitted is too small.
In large traffic volume scenarios, insufficient PDCCH resources result in a limited number of
UEs to be scheduled in the downlink and a low PDSCH resource utilization.
This feature increases the PDSCH resource utilization in the preceding scenarios, increasing
downlink throughput and improving user experience.

 PDSCH: physical downlink shared channel

 TTI: transmission time interval
 PDCCH: physical downlink control channel
Benefits
This feature improves the PDSCH resource utilization, increasing downlink throughput and
improving user experience.
Description
If surplus resource blocks (RBs) are available in LTE networks, an eNodeB takes the
following measures:
1. When traffic volume remains unchanged, the eNodeB increases the number of scheduled
RBs and lowers the modulation and coding scheme (MCS) index to improve
transmission reliability and user experience.
2. In large traffic volume scenarios, the eNodeB randomly selects a UE with large-size
packets during downlink scheduling and reserves PDCCH resources for the UE. The
eNodeB allocates PDSCH resources to the UE when scheduling the last UE, increasing
PDSCH resource utilization and downlink throughput.
3. When CA is enabled, the eNodeB allocates the total capabilities of a UE among carriers
to ensure the total number of transmitted bits on all carriers reaches the maximum but
does not exceed UE capabilities. If 3CC CA is enabled for UEs of category 6 and the
eNodeB uses only the two-antenna-port configuration, the eNodeB will allocate UE
capabilities in consideration of carrier bandwidths. In other scenarios, the eNodeB
evenly allocates UE capabilities without considering carrier bandwidths. This even
allocation policy causes UE capabilities not to be fully utilized if carrier bandwidths or
antenna port configurations are inconsistent, reducing downlink throughput.
This feature enables the eNodeB to allocate UE capabilities in consideration of carrier
bandwidths and antenna ports when the eNodeB uses the original even allocation policy.
Consequently, UE capabilities allocated to each carrier better match the actual
transmission capabilities. In addition, this feature increases the number of allocated RBs
and lowers the MCS index for CA UEs, improving downlink throughput and user
experience for CA UEs.
Enhancement
 eRAN11.1
When CA is enabled, this feature optimizes the CA capability allocation policy. In
addition, this feature increases the number of allocated RBs and lowers the MCS index
for CA UEs, improving downlink throughput and user experience for CA UEs.
Dependency
 eNodeB
None
 UE
None
None

 Core network
None
 OSS
None
 Other features
MCS selection with prioritized RBs and capability allocation optimization for CA UEs
require the following features:
− LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz
− LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
− LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
1.2.39 LBFD-070107 PDCCH Utilization Improvement

Availability
This feature is
Summary
This feature enables the eNodeB to allocate PDCCH resources more flexibly, reducing the
probability of PDCCH resource allocation failure and improving the PDCCH capacity.
Benefits
This feature increases the number of UEs that can be scheduled per TTI in a heavily loaded
network and increases the system capacity.
Description
A higher PDCCH aggregation level may decrease the number of UEs that can be scheduled
and decrease the system capacity. With this feature, the eNodeB increases the PDCCH
resource allocation success rate by decreasing the PDCCH aggregation level and adjusting the
TX power while ensuring demodulation performance. In this manner, the number of UEs that
can be scheduled and the system capacity increase. As different PDCCH CCEs may overlap,
there is a high probability of PDCCH resource allocation failure for UEs that are scheduled
later. With this feature, if PDCCH resource allocation fails for a UE, the eNodeB allocates
PDCCH resources for the UE again with a different aggregation level and power level while
ensuring demodulation performance. In this manner, the PDCCH resource allocation success
rate and the system capacity increase.
Enhancement
 eRAN8.1

This feature uses a lower PDCCH aggregation level combined with power control to
increase the PDCCH resource allocation success rate and improve the PDCCH capacity.
Dependency
None
1.2.40 LBFD-081102 PLMN ID Management

Availability
This feature is
Summary
This feature manages neighboring cells with specific PLMN IDs in scenarios where the
neighboring cells are near the border of PLMNs or abnormal UEs report invalid PLMN IDs.
This feature helps increase the neighbor relationship management efficiency and improve
operator's OM experience.
Benefits
This feature ensures that the neighbor relationships can be correctly configured when
abnormal UEs report invalid PLMN IDs.
When the neighboring cells are near the border of PLMN, this feature provides differentiated
management to increase the OM efficiency of neighbor relationships.
Description
This feature allows operators to configure different PLMN lists for a local cell:
 If a PLMN is blacklisted, the cells in this PLMN cannot be configured as neighboring
cells of the local cell. If the ID of a PLMN reported by abnormal UEs is an invalid ID,
this PLMN can be blacklisted.
 If a PLMN is graylisted, the cells in this PLMN can be configured as neighboring cells
of the local cell. These neighboring cells are processed specially during query and
automatic removal. A PLMN can be graylisted if this PLMN and the local cell's PLMN
overlap, work on the same frequency, but do not have handover relationships between
them.
 If a PLMN is whitelisted, the cells in this PLMN can be configured as neighboring cells
of the local cell. A PLMN can be whitelisted if this PLMN and the local cell's PLMN
have handover relationships between them.
Enhancement
None

Dependency
None
1.2.41 LBFD-081103 Terminal Awareness Differentiation

Availability
This feature is:
Summary
In live networks, some UEs have incompatibility issues with certain features due to UEs'
internal hardware or software defects. This affects network KPIs. On other occasions, UEs'
requirements for parameters and features vary with UEs' performance. Huawei eNodeBs
support differentiated handling for such UEs.
Benefits
This feature handles UEs' incompatibility issues and improves network KPIs such as the
service drop rate and uplink cell throughput. It configures different parameters and enables
different features for different UEs to achieve the optimal UE performance.
Description
When a Huawei MME identifies that the eNodeB is a Huawei device, the MME informs the
eNodeB of a UE's international mobile station equipment identity and software version
(IMEISV). Then, the eNodeB compares the UE's IMEISV with the IMEISV information
configured for UEs with incompatibility issues on the eNodeB. If they are matched, the
eNodeB performs preset actions on this UE.
Enhancement
This feature now supports differentiated DRX configurations for UEs. For example, the
eNodeB configures performance-oriented DRX parameters for UEs with long battery life and
power-saving-oriented DRX parameters for UEs with short battery life.
Dependency
 Core network
The MME must support the IE "Masked IMEISV" contained in the INITIAL CONTEXT
SETUP REQUEST and HANDOVER REQUEST messages.
1.2.42 LBFD-081104 UL Compensation Scheduling

Availability
This feature is:


Summary
Uplink compensation scheduling enables eNodeBs to schedule a voice user by monitoring the
scheduling interval, thereby decreasing the packet loss rate in the uplink.
Benefits
This feature reduces the uplink packet loss rate.
Description
Uplink compensation scheduling is a technique in which the eNodeB identifies voice users
and, for each voice user, measures the duration in which the user is not scheduled in the
uplink. If the user is not scheduled in the uplink within a specified duration, the eNodeB
delivers the uplink grant to the user, thereby ensuring that voice packets can be transmitted
promptly in the uplink. Uplink compensation scheduling helps reduce the delay for waiting
for voice packets and minimize the packet losses arising when the PDCP discard timer
expires.
Enhancement
 eRAN11.1
The minimum interval for uplink compensation scheduling between talk spurts and silent
periods can be configured. In this way, different compensation scheduling intervals can
be used according to site requirements to balance voice quality and resource
consumption.
Dependency
 eNodeB
None
 eCoordinator
None
 UE
None
None
 CN
None
 OSS
None
 Other features
This feature requires the following features to be activated:
− LBFD-002025 Basic Scheduling
− LOFD-00101502 Dynamic Scheduling

 Others
None
1.2.43 LBFD-081105 Voice-Specific AMC

Availability
This feature is
Summary
This feature applies to voice service. It enables the eNodeB to set an uplink target IBLER for
UEs not in the TTI bundling state to reduce the number of uplink VoLTE packet losses and
shorten VoLTE packet delays.
Benefits
This feature improves the uplink voice performance of UEs not at the cell edge.
Description
The eNodeB adjusts SINRs for UEs to be dynamically scheduled in the uplink based on the
configured uplink target IBLER and then preliminarily selects MCSs for the UEs. The optimal
uplink target IBLER differs in different scenarios and therefore should be configured for
different scenarios. Considering the tradeoff between VoLTE performance and resource
overheads, the default uplink target IBLER is recommended.
Enhancement
None
Dependency
 eNodeB
None
 eCo
None
 UE
None
None
 CN
None
 OSS
None

 Other features
This feature requires the following features:
− LBFD-001006 AMC
− LOFD-00101502 Dynamic Scheduling
Voice-specific MAC and uplink RLC segmentation enhancement can be enabled
simultaneously. Uplink RLC segmentation enhancement takes precedence if its
requirements are met.
 Others
None
1.2.44 LBFD-121102 eRAN12.1 Introduction Package

Availability
This feature is:
Summary
Uplink basic performance improvement:
 The PAMC function optimizes the initial values for AMC and the mapping for MCS
selection to maximize UL perceived throughput. It increases uplink spectral efficiency.
Downlink basic performance improvement:
 The precise MCS adaptation function optimizes MCS selection for retransmission and
CQI adjustment. It improves the accuracy of MCS selection and thereby increases
downlink spectral efficiency.
 The flexible target IBLER adaptation function adopts TBS index thresholds for selecting
different target IBLERs. This helps target IBLER adaptation meet the live network
requirements and increases downlink UE throughput.
Benefits
Uplink basic performance improvement:
 The PAMC function increases uplink UE throughput.
Downlink basic performance improvement:
 This feature increases downlink spectral efficiency and thereby improves downlink
UE-perceived data rates.
Description
The PAMC function obtains statistical characteristics of RRC_CONNECTED UEs through
adaptive learning and optimizes an initial value used in AMC for UEs that newly access a cell.

This function optimizes the mapping for MCS selection with receiver performance and
statistical channel fluctuation characteristics taken into consideration.
The precise MCS adaptation function detects scenarios with conservative initial MCS indexes
for UEs and selects appropriate initial MCS indexes for UEs that initially access the cell or
are handed over from other cells, increasing downlink UE throughput. This function also
efficiently utilizes soft combining with HARQ and selects appropriate MCS indexes for
retransmission, decreasing the number of RBs used for retransmission.
The flexible target IBLER adaptation function optimizes the trigger thresholds of target
IBLER selection for UEs at the cell edge or in the cell center and improves downlink
throughput of such UEs. This function also optimizes the admission threshold of enhanced
target IBLER adaptation in high load scenarios and enlarges the validation range, increasing
downlink UE throughput.
Enhancement
None
Dependency
None
1.2.45 LBFD-001015 Enhanced Scheduling

1.2.45.1 LBFD-00101501 CQI Adjustment
Availability
This feature is:
Summary
This feature allows for downlink channel quality indicator (CQI) adjustment, which is an
enhancement to the conventional adaptive modulation and coding (AMC) feature.
Benefits
This feature offers the following benefits:
 Effectively compensates for the inaccurate CQI measurement and makes the modulation
and coding scheme (MCS) selection more accurate by using a closed-loop mechanism.
 Increases system capacity by selecting more accurate MCSs.
 Allows adaptive CQI measurements for different scenarios and therefore increases
system capacity.

Description
As an enhancement to conventional AMC, downlink CQI adjustment offers more
performance benefits.
With conventional AMC, an eNodeB selects an MCS for a UE based on the reported CQI.
Therefore, the MCS selection is dependent on the reported CQI, which however may be
inaccurate due to UE measurement errors or channel fading. Without a closed-loop feedback
mechanism, the MCS selection based on the inaccurate CQI will cause the block error rate
(BLER) of downlink transmission to fail to approach the target BLER.
CQI adjustment introduces a closed-loop feedback mechanism to compensate for CQI
measurement errors. When selecting an MCS for downlink transmission, the eNodeB now
considers the difference between the measured BLER and the target BLER, in addition to the
CQI and transmit power. Note that the measured BLER is calculated based on the
ACK/NACK to downlink transmission. In addition, the closed-loop mechanism used by CQI
adjustment allows the eNodeB to instruct the UE to change the target BLER for CQI reporting,
maximizing system throughput.
The optimal target initial block error rate (IBLER) is suitable in most cases. In certain
scenarios, however, raising the target IBLER helps increase cell capacity and UEs' spectral
efficiency, especially for UEs at cell edges and UEs running small-packet services. A switch is
currently available for operators to control the target IBLER.
Enhancement
 eRAN6.0
The target IBLER can now be adaptively adjusted for cells.
Dependency
None
1.2.45.2 LBFD-00101502 Dynamic Scheduling
Availability
This feature is:
Summary
Dynamic scheduling helps ensure that UEs' service quality meets their QoS requirements. It
achieves efficient resource utilization. This feature takes fairness among UEs into
consideration. It is used for GBR and non-GBR services.
Benefits
Scheduling is the core function in the LTE system to provide QoS. Huawei scheduling
solution offers the following benefits:
 Ensures that the GBR and non-GBR service quality meets QoS requirements.

 Achieves an optimal tradeoff among throughput, fairness, and QoS.
Description
Scheduling helps efficiently utilize shared-channel resources. In the LTE system, schedulers
allocate resources to UEs every transmission time interval (TTI), that is, every 1 ms to meet
QoS requirements of different services and to achieve a tradeoff between service priorities
and UE fairness.
3GPP has defined nine QoS class identifiers (QCIs) for LTE. Services with the nine QCIs are
classified into GBR and non-GBR services. Scheduling mainly aims to guarantee the bit rates
of GBR services and enforce the aggregate maximum bit rates (AMBRs) of non-GBR
services. It also ensures that the bit rates of non-GBR services do not fall below their
Min_GBR, avoiding the non-GBR services from resource hunger.
Uplink schedulers use the token bucket algorithm for rate control over GBR and non-GBR
services. The proportional fair (PF) algorithm is used as the basic scheduling policy, which
considers the QCI-indicated priorities of services. The highest priorities are assigned to IMS
signaling and GBR services. Semi-persistent scheduling is employed for VoIP services to
ensure voice quality. When receiving congestion indicators from the load control algorithm,
schedulers may lower the guaranteed data rates for GBR services. In addition, the schedulers
consider the input from the uplink inter-cell interference coordination (ICIC) algorithm and
may determine to reduce interference.
Uplink schedulers divide logical channel groups (LCGs) according to operators'
configurations. VoIP services and signaling are assigned to the same LCG, and non-GBR
services can be assigned to two LCGs. This assignment ensures that high-priority non-GBR
services are scheduled in the uplink. The prioritized bit rate (PBR) is not the same as the
Min_GBR. The PBR is configurable by operators.
Downlink schedulers employ an enhanced scheduling policy. Within a given time window, the
schedulers must ensure that the GBR and AMBR requirements of all services are fulfilled.
When calculating the priorities of GBR services, the schedulers consider user channel quality
and service packet delay. When calculating the priorities of non-GBR services, the schedulers
consider the scheduled service throughput, in addition to user channel quality. Semi-persistent
scheduling is also employed for VoIP services, but the bandwidth for VoIP traffic is not
assigned by the schedulers. Enhanced downlink scheduling efficiently achieves an optimal
tradeoff among throughput, fairness, and QoS guarantee. Similar to uplink schedulers,
downlink schedulers consider the input from the downlink ICIC algorithm and may determine
to reduce inter-cell interference.
Non-GBR services, which have lower priorities than GBR services, may fail to be scheduled
upon congestion. To avoid this, downlink schedulers reserve a certain proportion of resources
for non-GBR services.
Enhancement
 eRAN6.0
A certain proportion of resources can now be reserved for downlink non-GBR services to
prevent the services from scheduling failure at congestion.
Dependency
None

1.2.46 LBFD-001027 Active Queue Management (AQM)

Availability
This feature is:
Summary
This feature provides an approach for buffer optimization to interact with the TCP protocol in
a favorable manner and shorten the buffering delay.
Benefits
The Active Queue Management (AQM) feature adjusts the buffer size based on the
transmission rate of the UE, thereby shortening the delay.
Description
In an interactive connection, the packet data to be transferred is typically characterized by
large variations. Therefore, the buffer is introduced to even out the variations. However, if the
buffer is full or overflows, packet loss occurs.
Currently, TCP as the main transport layer protocol is used on the Internet. Packet loss is
regarded as link congestion by TCP, and TCP will correspondingly reduce the data
transmission rate. The TCP protocol is sensitive to the round-trip delay (RTD) and it will take
actions differently in case just one packet is lost or if a burst of packets is lost. In case of
uncontrolled packet loss, it may take a considerable time for the data transmission rate to
increase again, leading to poor radio link usage and causing long delays.
In addition, assume that a user is performing parallel activities, for example, FTP
downloading and web browsing. If the buffer is full due to file downloading, this will cause a
long delay for web browsing.
AQM is provided as an optimized buffer handling method to interact with the TCP protocol in
a favorable manner and reduce the buffering delay.
Operators can activate or deactivate the AQM function.
Enhancement
None
Dependency
None

1.2.47 LBFD-001092 CMAS Support

Availability
This feature is:
Summary
This feature enables an eNodeB to support the commercial mobile alert system (CMAS). With
this feature, an eNodeB will receive warning broadcast requests from MMEs, and then deliver
warning notifications to UEs in RRC_CONNECTED and RRC_IDLE modes by system
information broadcast (SIB).
Benefits
If disasters or other emergencies occur, an eNodeB can promptly send warning notifications
to LTE UEs. The notifications instruct users to take actions to protect themselves and their
families from injuries, threats to life, and property loss.
This feature complies with the laws and regulations of the areas or countries in which
operators use this feature. This feature helps operators fulfill their social responsibility of
protecting customers from harm and improve social reputations of the operators.
Description
CMAS has the following functions:
 Supports requests for starting or stopping CMAS warning broadcast
This feature supports the Write-Replace Warning procedure and Kill procedure defined
in the 3GPP S1 Application Protocol (S1AP) specifications. CMAS warning notifications
can be broadcast for a specified number of times at a specified interval.
 Manages priorities of multiple CMAS warning broadcast tasks
If there are multiple CMAS warning broadcast tasks, an eNodeB adjusts the priorities of
these tasks based on the broadcast interval and the number of broadcast times of each
task. This ensures broadcast fairness among these tasks. The eNodeB can manage a
maximum of 64 CMAS broadcast tasks at a time.
Enhancement
None
Dependency
 UE
UEs must support CMAS.
 Core network
MMEs in the evolved packet core (EPC) must support CMAS.

1.3 Transmission & Security

1.3.1 LBFD-003001 Transmission Networking
1.3.1.1 LBFD-00300101 Star Topology
Availability
This feature is
Summary
Star topology is easy to implement and manage with high reliability. It provides simple
topology between eNodeB interfaces.
Benefits
 The simplest topology
 Simple management and high reliability
Description
Figure 1-6 Star topology
The eNodeB supports star topology. eNodeBs connect to the core network by layer2 or layer3
data network. The interface between the eNodeB and core network element is the S1
interface.
There are also connections between eNodeBs by the X2 interface, which enable information
exchange between the eNodeBs

Enhancement
None
Dependency
None
1.3.1.2 LBFD-00300102 Chain Topology
Availability
This feature is:
 Available in micro eNodeBs (excluding the BTS3912E) as of eRAN3.0.
Summary
The chain topology applies to eNodeBs in strip-shape areas with sparse population.
Benefits
The chain topology can reduce costs of transmission equipment, engineering, construction,
and transmission link lease.
Description
The chain topology applies to eNodeBs in strip-shape areas with sparse population, such as
expressways and railways. In these areas, the chain topology reduces transmission equipment.
However, the chain topology reduces reliability because signals are transferred across many
intermediate devices. The following figure shows the chain topology.
Figure 1-7 Chain topology
Enhancement
None
Dependency
None

1.3.1.3 LBFD-00300103 Tree Topology
Availability
This feature is
Summary
eNodeBs can be connected in tree topology applied to microwave transmission networks.
Benefits
Tree networking is suitable for microwave transmission networks. Tree topology requires
fewer transmission links than star networking.
Description
The eNodeB can be connected in tree topology. In most scenarios, the MW (Microwave)
network is typically in tree topology. It is suitable for the MW network.
The use of transport lines is less than that for star networking. However, tree connections
reduce reliability because signals are transferred across many intermediate systems. A fault
occurring in the upper-level eNodeB may affect the operation of the lower-level eNodeBs.
The networking topology is applicable to a large, sparsely populated area. Capacity expansion
may result in reconstruction of the network.
The following figure shows the tree topology.
Figure 1-8 Tree topology

Enhancement
None
Dependency
 eNodeB
The UMPT card, which provides E1/T1 interfaces, is required.
1.3.2 LBFD-003002 Basic Qos Management

1.3.2.1 LBFD-00300201 DiffServ QoS Support
Availability
This feature is
Summary
Huawei supports DiffServ (Differentiated Services) to provide QoS guarantee by classifying
and managing different traffic in the network.
Benefits
This feature provides a kind of QoS guarantee mechanism. It is a standard mechanism used by
Mainstream vendors.
Description
DiffServ can provide QoS in the network. It is a kind of QoS guarantee mechanism that
classifies and manages different traffic with parameters of IP packets, such as DSCP (DiffServ
Code Point) or TOS (Type of Service).
There are three important concepts in the DiffServ mechanism, including Classification,
Marking, and PHB (Per-Hop Behavior). The relationship between them is that Marking marks
different traffic with different PHBs by Classification.
The definition of PHB is as follows:
 Default PHB is typically for best-effort traffic.
 Expedited Forwarding (EF) PHB is for low-loss and low-latency traffic.
 Assured Forwarding (AF) is a behavior group.
 Class Selector PHB is defined to maintain backward compatibility with the IP
Precedence field.
The classification of LTE traffic is based on QoS Class Indicators (QCIs). With Huawei
configuration tool, users can configure the relationship between QCI and DSCP, i.e. the
Marking way. The DSCP is used to describe the priority of PHB. The table below is an
example of relationship between QCI and DSCP.

Table 1-8 Relationship between QCI and DSCP
Data Type QCI Resource Type DSCP

User plane 1 GBR 46
2 34
3 34
4 34
5 Non-GBR 46
6 18
7 18
8 18
9 0
Control plane - - 48
OM(MML) - - 46
OM(FTP) - - 18
IP clock - - 46
-
Enhancement
None
Dependency
None
1.3.3 LBFD-003003 VLAN Support (IEEE 802.1p/q)

Availability
This feature is
Summary
This feature enables Virtual Local Area Network (VLAN) functionality to provide traffic
differentiation, manage data priority and security scheduling at the MAC layer.

Benefits
 Traffic isolation at the MAC layer
 Priority at the MAC layer
 Security at the MAC layer
Description
The eNodeB supports the Virtual Local Area Network (VLAN) functionality, complying with
the IEEE 802.1p/q protocol. It provides traffic isolation, such as marking different VLANs for
OAM data and traffic data, and priority and security at the MAC layer.
The following two VLAN Marking ways are applicable:
 Marking VLAN tag according to DSCP
 Marking VLAN tag according to the next-hop IP address
Enhancement
None
Dependency
None
1.3.4 LBFD-003004 Compression & Multiplexing over E1/T1

1.3.4.1 LBFD-00300401 IP Header Compression
Availability
This feature is
Summary
IP header compression provides a method to compress IP header information in order to
increase the efficiency of E1/T1 interfaces.
Benefits
IP header compression can save S1/X2 IP transport resource to provide higher transport
efficiency of S1/X2 IP transmission.
Description
This feature focuses on the compression technology in UDP/IP layer.
When UDP/IP/MLPPP/E1/T1 is used for transport, the UDP/IP encapsulation is too large for
packets of small payloads and results in low transport efficiency.

IP header compression is adopted to enhance the transport efficiency. The 28 bytes of UDP/IP
header can be compressed into 4-7 bytes.
Enhancement
None
Dependency
 eNodeB
IP over E1/T1 is used for transport
The peer equipment supported the IP header compression functionality.
 CN
The CN equipment supports the feature.
1.3.4.2 LBFD-00300402 PPP MUX
Availability
This feature is
Summary
PPP MUX (Point-to-Point multiplex) provides a method to multiplex the IP header in order to
increase the efficiency of E1/T1 interfaces.
Benefits
PPP MUX can save S1/X2 IP transport resource to provide high transport efficiency for
S1/X2 IP transmission.
Description
This feature focuses on the multiplex technology in PPP/ML-PPP layer.
When UDP/IP/ML-PPP/E1 is used for transport, the UDP/IP/ML-PPP encapsulation is too
large for packets of small payloads and results in low transport efficiency.
PPP MUX technology is adopted to enhance the transport efficiency. With PPP MUX
mechanism, several IP packets can be multiplexed into one PPP frame to reduce the transport
consumption of PPP.
Enhancement
None

Dependency
 eNodeB
IP over E1/T1 is used for transport
PPP or ML-PPP is used for transport
The peer equipment supports PPP MUX function.
 CN
1.3.4.3 LBFD-00300403 ML-PPP/MC-PPP
Availability
This feature is
Summary
ML-PPP/MC-PPP (Multilink and Multiclass Point-to-Point Protocol) is the extend protocols
of PPP. ML-PPP is a protocol for binding several PPP links to one logic PPP link. The priority
is provided for PPP link traffic via MC-PPP protocol.
Benefits
 Increase the bandwidth of the PPP link.
 Load balancing in multi-PPP links
 Enhance the reliability of the PPP link
 Provide priorities for traffic on PPP link.
 Transport efficiency is enhanced when PPP header compression is used.
Description
PPP is a point-to-point transport protocol. The PPP header compression can be provided to
enhance the transport efficiency.
ML-PPP is an extend protocol of PPP. When ML-PPP is used, several PPP links are bound to
one logic PPP link group. The ML-PPP increases the bandwidth of the PPP link and enhances
the reliability of the PPP link between the eNodeB and the directly connected equipment. If
one link of PPP link group is broken, the ML-PPP will not break. Only thing happen is the
bandwidth decreases correspondingly.
MC-PPP is an extend protocol of PPP. When MC-PPP is used, the traffic on the PPP links can
be marked with different priorities according to DSCP which is mapped to QCI in eNodeB.
The following figure shows the ML/MC-PPP

Figure 1-9 ML-PPP/MC-PPP
Enhancement
None
Dependency
 eNodeB
The peer transport equipment shall support ML-PPP/MC-PPP when ML-PPP/MC-PPP is
used to transport.
E1/T1 interfaces are used.
 CN
1.3.5 LBFD-003005 Synchronization

1.3.5.1 LBFD-00300501 Clock Source Switching Manually or Automatically
Availability
This feature is
Summary
This feature enables manual or automatic switching between clock sources.
Benefits
If unexpected events occur in the current clock sources, the system will not be affected.

Description
The eNodeB can work in multiple clock synchronization modes. The system clock source can
be chosen in a convenient and flexible manner. When one clock source fails, the system clock
can be manually or automatically switched to another available one.
1. For phase synchronization, the clock source can be manually or automatically switched.
Following clock source supports manually switching:
− Synchronization with GPS
− Synchronization with the clock over IP (IEEE 1588V2)
− Synchronization with 1PPS + TOD
Following clock resource supports automatically switching:
− Between GPS and IEEE 1588V2
− Between GPS and 1PPS+TOD
2. For frequency synchronization, the clock source can be manually switched. Following
clock source supports manually switching:
− Synchronization with Ethernet(ITU-T G.8261)
− Synchronization with the clock over IP (IEEE 1588V2)
− Synchronization with the clock over IP (Huawei proprietary solution)
− Synchronization with GPS
− Synchronization with the BITS
− Synchronization with E1/T1 interface
− Synchronization with 1PPS
In addition to the previous clock sources, the eNodeB can work with the local oscillator.
Enhancement
None
Dependency
None
1.3.5.2 LBFD-00300502 Free-running Mode
Availability
This feature is
Summary
The free-running mode is an alternative mode to the clock sources if all clocks fail.

Benefits
When all clock sources are lost, this feature can keep the eNodeB in normal service for up to
90 days.
Description
When all clock sources are lost, the eNodeB internal clock can work in the free-running mode
to keep the eNodeB running.
The enhanced stratum 3 Oven Controlled Crystal Oscillator (OCXO) with a high accuracy
works as the master clock of the eNodeB. The OCXO can keep the eNodeB in normal service
for up to 90 days.
Enhancement
None
Dependency
None
1.3.5.3 LBFD-00300503 Synchronization with GPS
Availability
This feature is
Summary
The eNodeB can work in multiple clock synchronization modes to suit different clock
topologies. Global Positioning System (GPS) can be one of the synchronization sources.
Benefits
This feature provides GPS as one of the synchronization sources. The eNodeB internal clock
can be synchronized with the transport network and no auxiliary clock equipment is needed,
in order to reduce the cost. The synchronized clock is of the required accuracy to meet both
radio frequency and transmission network requirements.
Description
In compliance with 3GPP, the eNodeB clock must have a higher clock precision. The
frequency stability of the 10-MHz master clock of the eNodeB should be lower than ±0.05
ppm.
It is required if a GPS clock is used as the clock source.
The clock signals are processed and synchronized as follows:

The GPS antenna and feeder system receives GPS signals at 1575.42 MHz, and transmits the
signals to the GPS card. The system can simultaneously trace up to eight (normally three or
four) satellites. The GPS card processes the signals and transmits them to the main clock
module.
Enhancement
None
Dependency
None
1.3.5.4 LBFD-00300504 Synchronization with BITS
Availability
This feature is:
 Available to LampSite from eRAN6.0.
Summary
The eNodeB can select the clock synchronization mode according to the clock topology. One
of the clock synchronization modes to be selected is synchronization with the building
integrated timing supply system (BITS).
Benefits
This feature uses the BITS as a synchronization source. The eNodeB internal clock can
synchronize with the transmission network without any auxiliary clock device, which serves
as a cost-effective clock synchronization mode. The synchronization clock meets precision
requirements as well as requirements of radio frequency and transmission network.
Description
According to 3GPP specifications, the eNodeB clock must have high accuracy. The frequency
deviation of the eNodeB's 10 MHz clock from the reference clock source must be less than
±0.05 ppm.
The eNodeB can use an external reference clock to synchronize its clock with the 2 MHz
clock. The reference clock can be the BITS or the 2 MHz clock of the transmission equipment.
The master clock module implements phase locking and frequency dividing to convert the
clock signal into various types that are needed by the eNodeB.
Enhancement
None
Dependency
 eNodeB

The universal satellite card and clock unit (USCU) needs to be configured.
1.3.5.5 LBFD-00300505 Synchronization with 1PPS
Availability
This feature is
Summary
topologies. 1PPS+TOD can be one of the synchronization sources.
Benefits
This feature provides 1PPS+TOD as one of the synchronization sources. The eNodeB
internal clock can be synchronized with the transport network and no auxiliary clock
equipment is needed, in order to reduce the cost. The synchronized clock is of the required
accuracy to meet both radio frequency and transmission network requirements.
Description
ppm.
This feature provides 1PPS+TOD as one of the synchronization sources.
Enhancement
None
Dependency
 eNodeB
USCU(Universal Satellite Card and Clock Unit) card is required
1.3.5.6 LBFD-00300506 Synchronization with E1/T1
Availability
This feature is

Summary
topologies. Synchronization with E1/T1 is one option.
Benefits
This feature provides synchronization with E1/T1 option. The eNodeB internal clock can be
synchronized with the transport network and no auxiliary clock equipment is needed, in order
to reduce the cost. The synchronized clock is of the required accuracy to meet both radio
frequency and transmission network requirements.
Description
ppm.
The clock source of the eNodeB can be synchronized with the E1/T1 line clock sources.
Enhancement
None
Dependency
 eNodeB
UMPT card is required.
1.3.6 LBFD-003006 IPv4/IPv6 Dual Stack

Availability
This feature is
Summary
A fundamental IPv4-to-IPv6 transition technology involves the presence of two Internet
Protocol software implementations in an operating system, one for IPv4 and another for IPv6.
This feature provides support for IPv6 protocol stack. It also enables IPv4 and IPv6 protocol
stack work at the same time. Application level protocols (e.g. S1 and X2) over IPv6 are not
supported by this feature.
Benefits
The key to a successful IPv6 transition is compatibility with the large installed base of IPv4
hosts and routers. Maintaining compatibility with IPv4 while deploying IPv6 will streamline
the task of transitioning the Internet to IPv6.

Description
The most straightforward way for IPv6 nodes to remain compatible with IPv4-only nodes is
by providing a complete IPv4 implementation. IPv6 nodes that provide complete IPv4 and
IPv6 implementations are called "IPv6/IPv4 dual-stack nodes". IPv6/IPv4 dual-stack nodes
have the ability to send and receive both IPv4 and IPv6 packets. They can directly
interoperate with IPv4 nodes using IPv4 packets, and also directly interoperate with IPv6
nodes using IPv6 packets.
Huawei eNodeB could be operated in one of the three modes:
 With IPv4 stack enabled and IPv6 stack disabled.
 With IPv6 stack enabled and IPv4 stack disabled.
 With both stacks enabled.
Enhancement
None
Dependency
None
1.3.7 LBFD-111101 Synchronization with BeiDou

Availability
This feature is available from eRAN11.1.
Summary
BeiDou satellite navigation system is a global satellite navigation system, which provides
all-time, round-the-clock high-precision positioning, navigation, and timing services for users
on the Earth's surface and in the terrestrial space.
In this feature, the eNodeB uses the BeiDou satellite navigation system as the clock source,
implementing frequency synchronization and time synchronization.
Benefits
This feature provides another satellite clock synchronization mode in addition to GPS clock
synchronization.
This feature supports the backup of GPS clock synchronization and BeiDou synchronization,
thereby improving clock reliability.
Description
The eNodeB connects to the BeiDou satellite antenna system through the UMPTb6 or
UMPTe3 board that is configured with a BeiDou satellite receiver, thereby obtaining
synchronization signals from the synchronous satellite system.
Figure 1-10 shows the BeiDou synchronization solution.

Figure 1-10 BeiDou synchronization solution
Enhancement
None
Applicable to
Macro Micro LampSite
Y N N
Dependency
 Base Station
The UMPTb6 or UMPTe3 board that is configured with a BeiDou satellite receiver is
required.
The BeiDou satellite antenna system is required.
 eCoordinator
None
 UE
None
 CN
None

 Other NEs
None
 Other features
Prerequisite features: None
Mutually exclusive features: None
 Others
None
1.3.8 LBFD-003007 IP Route Backup

Availability
This feature is:
Summary
When an active IP route becomes faulty, the standby IP route can take over, thereby
improving the IP route reliability.
Benefits
This feature improves the reliability of the IP layer.
Description
Users can configure two routes with the same destination IP address but different next-hop
addresses and priorities. Usually, the route with the higher priority is active. When this route
fails and stops working (for example, found through network ping), the route with the lower
priority will take over and starts working.
Enhancement
None
Dependency
The peer equipment supports IP Route Backup.
1.3.9 LBFD-001010 Security Mechanism

1.3.9.1 LBFD-00101001 Encryption: AES
Availability
This feature is:


Summary
The encryption function provides confidentiality protection for both signaling data and user
data between the eNodeB and the UE.
Benefits
The encryption function provides confidentiality protection for signaling data and user data in
order to keep them from illegal interception and modification.
Description
LTE handles encryption protection for the RRC signaling and user data. The encryption
function includes both ciphering and deciphering at the PDCP layer. Ciphering is activated by
the initial security activation procedure after the eNodeB receives the UE context from the
EPC. Upon RRC connection establishment, the ciphering algorithm and keys to be used are
generated by the RRC layer, which is common for all radio bearers. Radio bearers carrying
signaling data and those carrying user data use the same configuration.
The ciphering algorithms change only with handovers. The ciphering keys change with
handovers or RRC connection reestablishment. An intra-cell handover procedure may change
the keys of the UE in RRC_CONNECTED state.
From eRAN1.0 onwards, encryption algorithm AES is supported.
Enhancement
None
Dependency
 UE
The UE must support the same encryption algorithm as the eNodeB.
1.3.9.2 LBFD-00101002 Encryption: SNOW 3G
Availability
This feature is:
Summary

Benefits
Description
signaling data and those carrying user data use the same configuration. The ciphering
algorithms change only with handovers. The ciphering keys change with handovers or RRC
connection reestablishment. An intra-cell handover procedure may change the keys of the UE
in RRC_CONNECTED state.
From eRAN2.0 onwards, encryption algorithm SNOW 3G with 128-bit keys is supported.
Enhancement
None
Dependency
 UE
1.3.9.3 LBFD-00101003 Encryption: ZUC
Availability
This feature is:
Summary
Benefits
Description

signaling data and those carrying user data use the same configuration.
The ciphering algorithms change only with handovers. The ciphering keys change with
handovers or RRC connection reestablishment. An intra-cell handover procedure may change
the keys of the UE in RRC_CONNECTED state.
ZUC (Zu Chongzhi, a famous Chinese scientist's name) algorithm is a word-oriented stream
cipher. It takes a 128-bit initial key and a 128-bit initial vector (IV) as input, and outputs a
keystream of 32-bit words (where each 32-bit word is called a key-word). This keystream is
used for ciphering or deciphering.
From eRAN6.0 onwards, encryption algorithm ZUC is supported.
Enhancement
None
Dependency
 eNodeB
LBBPc boards do not support this encryption algorithm.
 UE
1.3.10 LBFD-003010 Public Key Infrastructure (PKI)

Availability
This feature is:
Summary
eNodeBs support PKI, a framework used for certificate authentication. This framework is
used for the IPsec tunnel between an eNodeB and a security gateway (SeGW), or for the SSL
connection between an eNodeB and the OMC.
Benefits
This feature authenticates digital certificates between two network elements (NEs), improving
network security.
Description
PKI provides digital certificate management for NEs. It supports certificate authentication for
the IPsec tunnel between an eNodeB and a security gateway (SeGW), or for the SSL
connection between an eNodeB and the OMC.
Digital certification management includes certificate creation, storage, distribution, and
revocation, and certificate revocation list (CRL) issuance.

In general, a PKI system consists of a Certificate Authority (CA), a certificate repository (CR),
a CRL server, and the users to be authenticated. eNodeBs and SeGWs are the users of a PKI
system. An eNodeB interacts with the CA, CR, and CRL server with assistance of the U2000.
An eNodeB comes preconfigured with certain certificates whose format complies with X.509
V3. After an eNodeB begins operation, its certificates can be replaced.
The following figure shows a typical eRAN certificate application scenario.
Figure 1-11 eRAN certificate application
Enhancement
 eRAN2.0
eNodeBs can update digital certificates automatically through the U2000.
In eRAN2.1, this feature is enhanced to support automatic certificate distribution using
Certificate Management Protocol version 2 (CMPv2). CMP is an Internet protocol used
for X.509 digital certificate creation and management in a PKI system. With the
introduction of CMPv2 between CA and eNodeB, certificate application and update can
be automatically performed. If a large number of base stations are deployed on an
operator's network, CMPv2 can be used to establish direct connections between base
stations and the CA to greatly improve the certificate issuance and update efficiency.
An eNodeB uses CMP to obtain certificates from the CA. This is done through an
CMP-based initial registration/certification message and a key pair update or certificate
update message. Using a CMP-based cross-certification request message, a CA can get a
certificate issued by another CA.
CMP-based messages are encapsulated in HTTP or HTTPs messages.
Dependency
The peer device must support PKI.
 Core network
The CN must support PKI.

1.3.11 LBFD-001018 S1-flex

Availability
This feature is:
Summary
This feature is a part of the MME pool solution and needs to be supported by both the
eNodeB and the MME. It allows an eNodeB to be connected to more than one MME at the
same time.
A Huawei eNodeB supports a maximum of 32 S1 interfaces.
Benefits
This feature enhances the flexibility of S1 interface and provides the following benefits:
 Increases the overall capacity of MME pools.
 Achieves load sharing among MMEs in a pool.
 Avoids the necessity of signaling exchange in the core network when the UE moves in
the MME pool area because the served MME of the UE will not change.
Description
The following figure shows the relationships among MME pools, MME pool areas, and
eNodeBs.

Figure 1-12 Relationships among MME pools, MME pool areas, and eNodeBs
If an eNodeB connects to all the MMEs in an MME pool, the eNodeB must determine the
MME in the pool to which the signaling sent from a UE is sent:
If the UE carries the information of its registered MME in the RRC signaling message, the
eNodeB will select the MME according to this information.
If the UE does not carry the MME information or the registered MME is not connected to the
eNodeB, the eNodeB will select an MME pool and MME based on the following rules:
 Topology-based MME pool selection
The eNodeB selects an MME pool based on the network topology to minimize MME
switching during UE movement.
 Load-based MME selection
The eNodeB selects an MME based on its capacity and load. An MME informs the
eNodeB of its capacity during S1 setup. When the MME is overloaded, it informs the
eNodeB of its load situation and then the eNodeB prevents new UEs from accessing the
MME.
Enhancement
 eRAN6.0
A priority-based MME selection method is introduced. When different priorities are
configured for MMEs or S1 interfaces, an eNodeB preferentially selects the MME with
the highest priority. If multiple MMEs have the same priority, the eNodeB selects the
MME with the lowest load. The eNodeB selects an MME with a low priority only when
all high-priority MMEs are faulty or overloaded.
Dependency
 Core network

MMEs must support the MME pool function.
1.3.12 LBFD-003012 IP Performance Monitoring

1.3.12.1 LBFD-00301201 IP Performance Monitoring
Availability
This feature is:
Summary
This feature enhances the performance management function by providing an end-to-end
network monitoring mechanism, and collects the values of KPIs, including the traffic volume,
packet loss rate, delay, and jitter.
Benefits
 Convenient end-to-end network performance monitoring
 Enhanced system maintainability and testability
 Improved system performance
Description
IP performance monitoring (PM) is a Huawei-private function. It provides end-to-end network
performance monitoring by enabling periodic packet exchange between the two ends. The
eNodeB periodically sends packets to the peer device, for example, the S-GW, which
responds to these packets. The eNodeB acquires the KPIs, for example, the traffic volume,
packet loss rate, delay, and jitter from response packets.
With these KPIs, operators can know the network quality and take necessary measures, such
as network optimization and capacity expansion.
IP PM can also be used for fault location. If LTE NEs such as the eNodeB and S-GW have IP
PM enabled, it is easy to determine whether the fault occurs on transmission network devices
or LTE NEs. If every node on a network has IP PM enabled, faults can be quickly located.
Enhancement
None
Dependency
 Core network
The core network equipment must be provided by Huawei. Huawei EPC versions later
than PS9.2 support this feature.

1.3.12.2 LBFD-00301202 Transport Dynamic Flow Control
Availability
This feature is:
Summary
Transmission Dynamic Flow Control can dynamically adjust flow control parameters
according to the network quality detected using the IP Performance Monitoring (IP PM)
feature.
Benefits
This feature dynamically adjusts flow control parameters according to dynamic changes of
network quality.
Description
In certain scenarios, network quality frequently changes and it is better to dynamically adjust
QoS parameters, such as bandwidth. Transmission Dynamic Flow Control is an effective
method to dynamically adjust flow control parameters according to the network quality
detected using IP PM. It automatically increases bandwidth step by step when the network is
of good quality, and decreases bandwidth when the network is of poor quality.
IP PM provides end-to-end network performance monitoring to acquire network quality
information, such as traffic volume, packet loss rate, delay, and jitter.
Enhancement
None
Dependency
 Other features
This feature requires the LOFD-00301201 IP PM feature.
1.3.13 LBFD-002035 Self-configuration

Availability
This feature is:

Summary
The eNodeB can automatically establish an OM link, obtain the configuration data file and
software from the EMS, and then activate the configuration data file and software
automatically. The configuration data file contains radio parameters and transport parameters.
Finally, the eNodeB performs a self-test and reports the test result to the EMS.
The eNodeB can be triggered automatically by the U2000 or LMT to launch a comprehensive
self-test after the software and configuration data file are loaded. After the test is complete,
the U2000 or LMT can obtain a self-test report.
Benefits
Except hardware installation, no other manual operations need to be performed by field
engineers for the initial eNodeB startup.
Description
When the eNodeB is powered on, it obtains the data required for OM link setup, such as the
IP address, subnet mask, IP address of the EMS, and IP address of the security gateway,
through the DHCP server. If the transport network DHCP server cannot provide such
information, the information must be input into the eNodeBs before installation or through a
USB stick (the USB stick is not specific for site but public for many sites) by field engineers.
When the OM link is established successfully, the eNodeB downloads and activates the
configuration data file and software automatically according to the instruction from the EMS.
Then, the eNodeB performs a self-test to ensure that it is ready to provide services and reports
the test result to the EMS.
For micro eNodeBs, if PPPoE is used for transport authentication, the PPPoE account
information must be pre-configured into the eNodeB before installation or through USB stick
by field engineers.
After the software and configuration data file are downloaded, the U2000 or LMT launches a
comprehensive self-test procedure on the eNodeB. After the test is complete, the U2000 or
LMT obtains a test report, indicating the eNodeB status.
The test report contains the following information:
 eNodeB basic information, such as eNodeB type and name
 Software version information
 Board status information, such as information about the baseband processing units and
RF units
 Transport status information (physical layer and link layer)
 Cell status
Enhancement
 eRAN2.0
a. The eNodeB can automatically establish an IPsec link with the security gateway
during the self-configuration procedure.
b. If the eNodeB is equipped with a GPS device, it can report geographical
information (from the GPS device) to the EMS, and the EMS will automatically
identify the eNodeB by comparing the received geographical information with the
predefined geographical information.

c. Automatic transport setup is supported. The eNodeB has three types of

transport-related interfaces: S1 interface, X2 interface, and OM transport interface.
Accordingly, the eNodeB provides three automatic transport setup processes. The
general network topology is shown in the following figure.
 eRAN2.1
A barcode of eNodeB ID can be scanned into eNodeB by a barcode reader connected to
the USB port of the MPT. The scanned eNodeB ID can be sent to the EMS so that the
EMS automatically identifies the eNodeB. In eRAN3.0, eNodeB ID is replaced by DID.
Figure 1-13 General network topology
The eNodeB has parameters preconfigured before the installation. The parameters
include the MAC address, local OM IP address, and global ID. Preconfigured parameters
do not need to be manually set or modified.
The automatic transport setup procedure is as follows:
a. When the eNodeB is powered on, it automatically negotiates the transport layer
(PHY/MAC) parameters, such as duplex mode, with the peer device. The peer
device can be a LAN switch, router, or another eNodeB.
b. The eNodeB obtains the VLAN ID of peer devices by VLAN scanning so that the
peer devices can correctly receive data from the eNodeB.
c. The eNodeB receives the OM channel parameters from the DHCP server, including
the Internet IP address, Network Element Management (NEM) IP address, SeGW
IP address, and operator CA information such as CA name, IP address, and protocol
type.
d. Based on the operator's CA information, the eNodeB obtains operator certificate
from the CA using the CMPv2 protocol. The certificate is used for SSL and IPsec
authentication.
e. The eNodeB establishes an IPsec tunnel with the SeGW, obtains the Internal IP
address, and establishes the OM channel with the NEM.
f. After the software and configuration file are downloaded and installed, the eNodeB
receives the required transport parameters of the S1 interface from the NEM, such
as the eNodeB traffic IP address and MME SCTP IP address.
g. The eNodeB starts the S1 self-setup procedure and establishes the S1 interface.

This feature provides the X2 self-setup for LOFD-002001 Automatic Neighbour Relation
(ANR). The eNodeB automatically detects new neighboring sites that are not configured
as neighboring sites. After receiving required transport data from the core network, the
eNodeB automatically establishes X2 links with the new sites.
The eNodeB obtains the VLAN ID of peer devices by VLAN scanning so that the peer
devices can correctly receive data from the eNodeB.
Based on the operator's CA information, the eNodeB obtains operator certificate from the
CA using the CMPv2 protocol. The certificate is used for SSL and IPsec authentication.
Based on the configuration of the DHCP server, the eNodeB requests the OM IP address
from either the DHCP server or NMS.
 eRAN3.0
a. The eNodeB supports automatic obtaining and configuring IPv6 transport
information through OAM. This function applies only to macro eNodeBs.
b. The eNodeB supports X2 self-setup for the ANR feature under IPv6. This function
applies only to macro eNodeBs.
c. The eNodeB supports X2 self-setup with IPsec protection on X2 interface links.
d. The eNodeB can obtain the S-GW's IP address from the MME when service is set
up. Based on the IP address, the eNodeB automatically configures the S1-U
interface.
 eRAN11.1
After operators configure an SCTP host on an eNodeB, the eNodeB sends a TAI domain
name or a user-defined domain name to query MME information from the DNS server.
Then, the eNodeB obtains the IP address of the MME corresponding to the domain name.
The eNodeB automatically configures the S1-C interface based on the IP address.
Dependency
 Other features
This feature requires LOFD-002001 Automatic Neighbour Relation (ANR).
1.4 Operation & Maintenance

1.4.1 LBFD-004001 Local Maintenance of the LMT
Availability
This feature is
Summary
This feature is used in local maintenance of eNodeB.

Benefits
Local maintenance of eNodeB is available when centralized U2000 management is not
available, when the transmission between U2000 and eNodeB is not available or when faults
occur and field operation is required.
Description
The Local Maintenance Terminal (LMT) provides the following functions and tools:
 Execution of MML commands
 Querying of eNodeB alarms
 Local eNodeB commissioning functions (applicable, for example, when the transmission
between the Huawei iManager U2000 and eNodeB is not available), such as download
and activation of software
 Local eNodeB expert fault diagnosis functions
 Real-time performance monitoring functions, such as sector performance monitoring,
RRU performance monitoring, spectrum detection
Enhancement
 In eRAN2.0
The LMT functions can be achieved through a web browser.
Dependency
 OSS
A web browser is required to achieve the function.
1.4.2 LBFD-004002 Centralized U2000 Management

Availability
This feature is
Summary
The Huawei iManager U2000 provides FCPSS management functions for operators at the
management center.
Benefits
All LTE network elements can be managed at the management center, which effectively
reduces OPEX.

Description
The Huawei iManager U2000 provides all necessary fault management, configuration
management, performance management, security management and software management
(FCPSS defined by 3GPP) management functions to help operators to manage their network
elements on a sub-network.
FCPSS involves the following contents:
 Centralized fault management
 Centralized configuration management
 Centralized performance management
 Centralized security management
 Centralized software management
Enhancement
None
Dependency
 OSS
The Huawei iManager U2000 is required.
1.4.3 LBFD-004003 Security Socket Layer

Availability
This feature is
Summary
Security Socket Layer (SSL) is a layer between the TCP layer and the O&M application layer.
SSL provides the secured data transfer function between the eNodeB and the Huawei
iManager U2000
Benefits
All remote operation and maintenance tasks are performed through encrypted protocols.
Description
Security Socket Layer (SSL) is a layer between the TCP layer and the O&M application layer.
SSL provides the secured data transfer function between the eNodeB and the Huawei
iManager U2000. All O&M application data transferred through SSL is encrypted. FTP over
SSL is also supported.

Enhancement
 In eRAN3.0
This feature supports TLSv1.2. Transport Layer Security (TLS) and its
predecessor-Secure Sockets Layer (SSL), are cryptographic protocols that provide
communications security between eNodeBs and Huawei iManager U2000 above
Transport Layer. TLSv1.2 is the latest version of TLS series. And TLS1.2 supports
stronger authentication algorithm SHA256.
Dependency
 OSS
1.4.4 LBFD-004004 Software Version Upgrade Management

Availability
This feature is
Summary
This feature provides efficient and correct installation and upgrade of the software and version
management functions.
Benefits
The eNodeB software management enables efficient and correct software installation, upgrade,
and version management.
Description
The eNodeB software management covers the following functions:
 Efficient and correct installation and upgrade of the software
 Automatic compatibility check on the software and hardware versions to verify a
successful software installation and upgrade.
 Automatic data conversion for the software upgrade, which requires no manual
configuration updates.
 Software download by configuration can reduce 30% of the software package size and
shorten the download time. For adding a board, the system supports automatic download
of software files for the board from the Huawei iManager U2000 if the files are not
downloaded to eNodeB previously.
 If the network recovers in 1 hour after breakdown, the system supports resumption of the
software download with no need to download the software from scratch.
 A maximum of 600 eNodeBs can be selected to download and activate the software in
batches automatically.

 Hot patch can be upgraded together with software in Huawei iManager U2000 software
management wizard.
 Version management, for example, the hardware and software version query
The process for upgrading software at a network element involves the following two
activities:
 Downloading the software package from the Huawei iManager U2000 to the eNodeB.
This may take some time because of the limited bandwidth of the OM link but does not
have impacts on services.
 Running the software activation command on the Huawei iManager U2000 client. The
system will automatically load the software to the target boards and activate the software.
To activate the software, the target boards will be reset and the service on the boards will
be interrupted.
The above-mentioned two activities can be done separately. E.g. downloading software
package to eNodeBs at daytime and activating the software at midnight. The separate
software upgrade procedure helps to reduce the risk of software upgrade failures and service
disruption of the sub-network.
Enhancement
None
Dependency
 OSS
1.4.5 LBFD-004005 Hot Patch Management

Availability
This feature is
Summary
This feature provides hot patch management functions, such as installation, uninstall and
rollback.
Benefits
The eNodeB supports the hot patches so that the software bugs can be fixed without
interrupting the ongoing services.
Description
A hot patch is a patch that is used to fix bugs and does not interrupt the ongoing services.
Huawei LTE hot patch management involves the following functions:

 Hot patch installation.

There are two ways to install a released hot patch package on the eNodeB:
 Running only a single installation command: In this way, the patch is downloaded,
loaded, activated and confirmed automatically.
 Running different commands at separate steps of the patch installation: In this way, users
have full control over the installation procedure: download, load, activate and confirm.
 Rollback of the last installed hot patch
 Uninstall of the hot patch
Enhancement
None
Dependency
 OSS
Hot patch management can be implemented on the Huawei iManager U2000 or the
eNodeB LMT.
1.4.6 LBFD-004006 Fault Management

Availability
This feature is
Summary
This feature provides automatic fault supervision and handling of eNodeB.
Benefits
This feature enables the automatic fault supervision of the equipment in the network elements.
With real-time alarm lists and alarm logs, operators can have a comprehensive view of the
actual status of the network at any time.
Description
Fault management involves fault detection, fault handling, fault correlation, and fault
reporting. With these features, operators can be informed as soon as the fault occurs in the
network and take proper actions to minimize or prevent service disruption.
 Fault detection
Fault detection includes physical layer and link layer environment monitoring and KPI
alarm monitoring and other fault detection. A small portion of faults may have a negative
impact on the traffic if self-testing, such as RAM self-testing and transport link loopback
testing, is performed. Among those faults, some are detected automatically in the board
startup phase, and some can be manually triggered by executing fault testing commands.

Fault detection methods are carefully designed to avoid false alarms and intermittent alarms.
 Fault handling
The eNodeB will perform fault isolation and fault automatic recovery to minimize the impacts
on service.
 Fault correlation
Fault management supports a run-time fault correlation handling mechanism and makes it
possible to notify operators of the most important alarms (the root cause and impacts on the
traffic) instead of all the related ones when a fault occurs. The number of alarms can be
greatly reduced in this way, which makes it easier to locate and solve the network problems.
This mechanism is predefined and embedded in the network elements, and operators can
customize more alarm correlation handling rules on the Huawei iManager U2000.
 Fault reporting
Faults are reported to users in the form of alarms. Because of the alarm correlation function,
the information of the correlation between alarms is contained in alarms. If any correlative
alarms occur, operators can get the root alarm by simply right-clicking the service-affecting
faults.
The operators can browse real-time alarm information, query history alarm information, and
store alarm information. The online help provides detailed troubleshooting methods for each
type of alarm.
Enhancement
 In eRAN2.0
Huawei LTE eRAN2.0 supports KPI alarm detection.
 In eRAN2.2
When RRU power supply is AC, RRU could detect AC power down and provide
warning signal to the eNodeB.
Dependency
 OSS
Fault management can be implemented on the Huawei iManager U2000 or the eNodeB
LMT.
1.4.7 LBFD-004007 Configuration Management

Availability
This feature is
Summary
This feature provides online and offline configuration functions which support quick
installation, expansion and configuration of the network.

Benefits
This feature provides a good overview of the current status of the network and supports fast
installation, expansion and configuration of the network.
Description
Configuration management provides operators with a means to collect and manage the data of
the network element. The manageable element data covers the physical aspect (equipment)
and logical/functional aspect (such as cells and links). The graphic user interface makes it
easy to implement the management.
To minimize the impact of reconfiguration on the system, Huawei configuration management
function has the following important features:
 Physical modifications are independent of the related logical modifications.
 All the required modifications to satisfy a defined task are completely checked to ensure
their validity before the modifications can be applied to the eNodeB.
 Configuration data consistency between the NE and the Huawei iManager U2000 are
always ensured.
Both offline configuration and online configuration are supported.
 Offline configuration
CME (Configuration Management Express) is a graphic offline configuration tool. In addition
to general configuration functions, it provides some configuration templates to ease site
deployment jobs. It also provides some GUI wizards to help user to finish capacity expansion
and migration jobs.
 Online configuration
All configuration data can be modified and queried online through MML commands.
Enhancement
 In eRAN2.0
GUI wizards are added to help users with capacity expansion and migration jobs.
Dependency
 OSS
Configuration management can be implemented on the Huawei iManager U2000 or the
LMT.
1.4.8 LBFD-004008 Performance Management

Availability
This feature is

Summary
This feature provides various performance measurement (PM) counters to monitor the
performance of the eNodeB. The real-time KPI monitoring is an enhanced feature to help user
locate performance problems quickly.
Benefits
The performance management function provides an efficient way to monitor the network
performance so that network troubleshooting and optimization can be implemented, and the
real-time KPI monitoring is a more efficient feature.
Description
Performance measurement gives the detailed information of the network. Such information
facilitates troubleshooting and network optimization.
 PM administration
The performance measurement administration provides operators with a means to manage the
available measurements.
For the new commissioning network elements (eNodeB), the predefined performance
measurements will start after initial startup phase. The performance measurements can be
suspended and resumed manually.
The network elements (eNodeB) provide machine-machine interfaces, allowing the Huawei
iManager U2000 to collect the necessary statistics and to set the related parameters including
statistical counters and the measurement period.
The statistics are obtained by the Huawei iManager U2000 in binary format in every
measurement period.
Each eNodeB can store a maximum of 288 files as backups that are useful when data transfer
fails, which makes it possible for the Huawei iManager U2000 to recollect the lost data later.
− If the measurement period is 15 minutes, an eNodeB can store measurement results sampled
in a maximum period of 72 hours.
− If the measurement period is 60 minutes, an eNodeB can store measurement results sampled
in a maximum period of 288 hours.
 PM counters
The PM counters include key counters and other counters. The key counters are used to
generate the key performance indicators (KPIs) of the network, which are defined on the
Huawei iManager U2000, and these counters are predefined and initialized as soon as the
eNodeB starts. The KPIs, related original counters and formulas can be added, modified and
deleted on the Huawei iManager U2000. Other counters reflecting the other aspects of
network performance can be started when needed.
 Real-time KPI monitoring
This feature provides the monitoring of KPIs and graphical representation of network
performance. Therefore, it is convenient for troubleshooting, drive tests and network
optimization. The real-time KPI measurement period of each monitoring task can vary, but
must be a multiple of 30 seconds within the range of 30 seconds to 15 minutes. By default,
eNodeBs of eRAN2.2 and later releases use a monitoring period of 1 minute.

Enhancement
None
Dependency
 OSS
Performance management is implemented on the Huawei iManager U2000 or LMT.
1.4.9 LBFD-004009 Real-time Monitoring of System Running

Information
Availability
This feature is
Summary
This feature provides the function of monitoring the running information of the equipment,
RF system, cells, subscribers and transport links.
Benefits
This feature is convenient for troubleshooting, drive tests and network optimization.
Description
This feature provides real-time monitoring and graphical representation of system operation
information and quality. It is a test facility which helps operators to diagnose faults through
precise information about cells, subscribers and links..
The following monitoring items are supported:
 Equipment running information monitoring: involving clock source quality
 Subscriber-level running information monitoring: involving SIR measurement and UE
TX power
 Cell-level running information monitoring: involving the number of cell users,
throughput, and resource block usage
 Transport link running information monitoring: involving SCTP links and IP paths
 RF monitoring: involving RF performance and RF interference detection
Enhancement
None
Dependency
None

1.4.10 LBFD-004010 Security Management

Availability
This feature is
Summary
This feature provides the user authorization, system data backup and restore, security log
auditing and security-related alarms functions.
Benefits
This feature provides the user authorization and management mechanism to enhance network
security.
Description
Security management covers the following functions to enhance system security:
 User management: This mechanism allows setting of user accounts and permissions, so
that the related authorized groups and operators can be managed.
 System data backup and restoration
 Collection of operation logs and auditing of security logs
 Triggering of alarms when, for example, network attacks are detected or the number of
unauthorized sessions exceeds the preset threshold
Enhancement
 In eRAN2.0
Security alarms are added.
Dependency
 OSS
1.4.11 LBFD-004011 Optimized eNodeB Commissioning Solution

Availability
This feature is

Summary
The optimized eNodeB commissioning solution supports USB commissioning and automatic
obtaining of software and configuration data from the Huawei iManager U2000.
Benefits
This feature simplifies the eNodeB commissioning procedure.
Description
This feature simplifies the on-site commissioning procedure from the following aspects:
 If eNodeB data is ready on the Huawei iManager U2000 and transmission of this
eNodeB is ready, Huawei on-site manual commissioning task is very simple:
 Installing the hardware and powering on the eNodeB
 Waiting for the eNodeB startup
 If field engineer has a laptop, the engineer can use laptop to input DID (Deployment ID).
iManager U2000 can use this information to automatically select a correct configuration
data.
 Or , field engineer can call the administration center and report the Electronic Serial
Number (ESN) of the eNodeB
 In the procedure, the newly installed equipment will automatically set up the connection
with the Huawei iManager U2000 by using DHCP, download software and data from the
Huawei iManager U2000, and install the software.
 USB commissioning is supported. The associated software and data of the eNodeB can
be copied to a USB disk at the administration center. A local commissioning engineer
only needs to obtain the USB disk, install the hardware, and connect the USB disk to the
USB port on the eNodeB. After that, the eNodeB can automatically install the software
and load data, start up, and set up the connection to the Huawei iManager U2000. No
more local configuration is required.
Enhancement
None.
Dependency
 OSS
U2000 or an USB for USB commissioning is required.
1.4.12 LBFD-004012 Environment Monitoring

Availability
This feature is

Summary
This feature provides environment fault alarming and customized environment alarms
functions.
Benefits
This feature enables centralized environment monitoring of Huawei eNodeB equipment.
Description
This feature enables centralized environment monitoring of Huawei eNodeB equipment in
terms of, for example, the temperature, humidity, smoke, water immersion, access control,
and power supply. Besides, Huawei equipment can be connected to third-party analog and
digital sensors, which enable operators to customize environment alarms.
Enhancement
None
Dependency
 OSS
The Huawei iManager U2000 or LMT is required.
1.4.13 LBFD-004013 Inventory Management

Availability
This feature is
Summary
The Huawei iManager U2000 retrieves inventory information automatically from the eNodeB
after commissioning and synchronize the information on the eNodeB every day.
Benefits
With this function, operators can obtain the timely and accurate inventory data of the existing
network for decision making.
Description
Inventory management helps operators to manage the asset information of the network. With
this function, the assets can be queried and managed on the Huawei iManager U2000.
The objects which are managed by this function include physical objects (such as racks,
frames, slots, boards, ports, and fans) and logical objects (such as software and patches).

When requested from the Huawei iManager U2000, an asset information file in .xml format is
generated and is sent to the Huawei iManager U2000. The Huawei iManager U2000 stores the
uploaded information in the network inventory database.
The Huawei iManager U2000 retrieves inventory information automatically from the eNodeB
after commissioning and synchronize the information on the eNodeB every day.
Enhancement
 In eRAN2.0
The Huawei iManager U2000 retrieves inventory information automatically from the
eNodeB after commissioning.
Inventory change notification function has been added to eNodeB. When inventory
changes in eNodeB, a notification will be sent from eNodeB to U2000(Micro eNodeB
will not send this notification), so that the inventory information could be synchronized
quickly between U2000 and eNodeB.
Dependency
 OSS
1.4.14 LBFD-004014 License Management

Availability
This feature is
Summary
This feature involves the eNodeB license control.
Benefits
With this feature, the operators can purchase the license based on the network development,
thus reducing the initial cost of the network deployment.
Description
The license file is used to determine whether the optional features are available and how many
optional features are available.
The license file can be downloaded remotely to the eNodeB. The operators can manage and
query the contents in the license file through the LMT or the U2000 client.
The license file is stored in the eNodeB.

Figure 1-14 License file management
New or upgraded license files can be ordered from Huawei.
Enhancement
None
Dependency
None
1.4.15 LBFD-004015 License Control for Urgency

Availability
This feature is
Summary
With this feature, the license limitation is withdrawn in emergencies, so the operator can
handle the sudden increase of network capacity.
Benefits
This feature helps operator to face the situations where there is an unusual increase of traffic
(sport events, New Year…) by enabling a temporary increase of RAN resource, avoiding
permanent over-dimensioning and thus adapting the capacity costs to the real usage.
Description
The license limitation is withdrawn through manual execution of the MML commands on the
LMT or U2000. Thus, the equipment can be used effectively to optimum capacity.
For each R version, the operation personnel have three chances to withdraw the license
limitation through the MML commands. The operation takes effect immediately after the

commands are executed. The validity period is seven days. When the three chances are used
up, a new chance can be obtained only through the software upgrade.
Enhancement
None
Dependency
None
1.4.16 LBFD-070104 Site Transmission Equipment Fault Detection

Availability
This feature is
 not applicable to Macro
Summary
A small-cell base station and the transmission equipment in direct connection can be bound
together by means of NE self-discovery reports. Transmission Equipment Fault Detection
enables users to query information on the iManager U2000 MBB about the transmission
equipment that is bound to the small-cell base station, including equipment type and MAC
address. This facilitates troubleshooting if the small-cell base station goes out of service or
becomes disconnected. Based on the information queried on the iManager U2000 MBB, users
can easily detect and locate faults on the transmission equipment by using the special network
management system.
Benefits
This feature facilitates fault location. When a small-cell base station goes out of service or
becomes disconnected, this feature enables fault detection on the last-mile transmission
equipment, thereby improving troubleshooting efficiency.
Description
 Process for a small-cell base station to obtain the peer equipment information
Link Layer Discovery Protocol (LLDP) is a layer 2 protocol and is independent of vendors.
Network equipment uses this protocol to claim the equipment identity and performance in the
local subnet. Layer 2 Discovery provides the following information:
- Network equipment and its ports
- Network equipment that is connected on the ports
- Topologies between a small-cell base station and the transmission equipment in direct
connection
The following figure shows the process for a small-cell base station to discover a piece of
peer equipment.

Users enable LLDP between Small cell and Peer network element. The procedure for
discovering the topology between Small cell and Peer NE over LLDP is as follows:
1. Small cell sends Peer NE the LLDP packets containing local information (including
system name, description, port number, and MAC address).
2. Peer NE analyzes the LLDP packets and stores the analysis result into its database. This
analysis result is used as neighbor information that will be accessed when the iManager
U2000 MBB obtains network topology information.
3. Similarly, Peer NE sends Small cell the LLDP packets containing local information.
Small cell analyzes the LLDP packets and stores the analysis result into its database.
4. The iManager U2000 MBB queries LLDP-related information about Small cell to obtain
local information and neighbor information about Small cell and Peer NE. Finally, the
iManager U2000 MBB learns about the topology of the entire network..
 Process for users to query information about the peer equipment of a small-cell base
station
When the transmission equipment is enabled with the LLDP function, users can select a
small-cell base station and activate LLDP and query peer NE information for the small-cell
base station. When users manually query peer NE information, the small-cell base station and
peer NE information is displayed in a table. The table contains the fields Local NE, Local
Port, Peer NE Type, Peer Port, Peer MAC Address, and Peer OM IP. Peer NE Type and
Peer MAC Address are mandatory in the table.

The following figure shows the table that contains the small-cell base station and peer NE
information.
The following flowchart shows the troubleshooting procedure for a small-cell base station.

The troubleshooting procedure for a small-cell base station is as follows:

The fault locating process is as follows:
Step 1 On the iManager U2000 MBB, select the base station that requires fault locating.
Step 2 Right-click the base station and choose Query the Peer Information from the
shortcut menu to query transmission equipment information.
Step 3 Detect the transmission equipment on the iManager U2000 FBB and check whether
the OMCH of the transmission equipment is running properly.
 If so, go to Step 4.
 If not, the bearer network of the base station is faulty. Fault locating ends.
Step 4 Right-click the transmission equipment and choose Continuity Check from the
shortcut menu to locate the fault.
 The transmission equipment is faulty. Fault locating ends.
 If the transmission equipment is running properly, the base station is faulty. Fault
locating
Enhancement
None

Dependency
None
1.4.17 LBFD-120101 Antenna Fault Detection

Availability
This feature is:
 Changed from an optional one (LOFD-002011) into a basic one in eRAN12.1.
Summary
Faults in antenna systems and radio frequency (RF) channels are caused by improper
installation of equipment during project implementation, relocation, or optimization. The
faults may also be caused by natural or external changes.
This feature detects antenna faults for fault diagnosis.
Benefits
This feature detects common antenna faults, increasing fault diagnosis efficiency and
accuracy.
It reduces engineering costs by eliminating the need for RF engineers to measure eNodeBs
using tools onsite.
Description
Antenna systems play an important role in mobile communications. The performance of an
antenna system is affected by the following factors:
 Improper type or location of the antenna system
 Inappropriate parameter settings for the antenna system
 Faulty antenna system
The antenna fault detection system can detect the following faults and raise related alarms:
 Weak received signals
 Imbalance between main and diversity received signals
 Abnormal voltage standing wave ratio (VSWR)
Enhancement
None
Dependency
None

1.4.18 LBFD-001024 Remote Electrical Tilt Control

Availability
This feature is:
 Not available in LampSite eNodeBs.
Summary
Remote Electrical Tilt Control improves the efficiency and minimizes the operation and
maintenance cost of adjusting the downtilt of the antenna. Huawei LTE (remote electrical tilt)
RET solution complies with the AISG2.0 specifications, and it is compatible with AISG1.1.
Benefits
The application of the RET prominently improves the efficiency and minimizes the operation
and maintenance cost of adjusting the downtilt of the antenna. Its application brings the
following benefits:
 The RET antennas at multiple sites can be adjusted remotely within a short period. This
improves the efficiency and reduces the cost of network optimization.
 Adjustment of the RET antenna can be performed in all weather conditions.
 The RET antennas can be deployed on some sites that are difficult to access.
 RET downtilt adjustment can keep the coverage pattern undistorted, and therefore
strengthening the antenna signal and reducing neighboring cell interference.
Description
The RET refers to an antenna system whose downtilt is controlled electrically and remotely.
After an antenna is installed, the downtilt of the antenna needs to be adjusted to optimize the
network. In this situation, the phases of signals that reach the elements of the array antenna
can be adjusted under electrical control, and then the vertical pattern of the antenna can be
changed.
The phase shifter inside the antenna can be precisely adjusted through the step motor outside
the antenna. The downtilt of the RET antenna can be adjusted when the system is powered on,
and the downtilt can be monitored in real time.
Huawei LTE RET solution complies with the AISG2.0 specifications, and it is compatible
with AISG1.1.
Enhancement
None
Dependency
This feature applies only to macro eNodeBs.

1.4.19 LBFD-001041 Power Consumption Monitoring

Availability
This feature is:
Summary
The eNodeB reports the power consumption status to the EMS. Through the EMS, the change
in power consumption of the eNodeB can be monitored by the operator, and a report on the
power consumption can be generated.
Benefits
The eNodeB reports the power consumption status to the EMS. Therefore, the operator can
monitor the power consumption of the eNodeB. With the report on the power consumption,
the operator can exactly know the benefits brought by the decrease in power consumption.
Description
The eNodeB periodically monitors the power of each monitoring point and reports the power
consumption within a period. The EMS receives and collects all data about power
consumption. Through the EMS, the operator can observe the change in the power
consumption and analyze the power consumption according to a statistics report generated by
the EMS.
Enhancement
None
Dependency
 OSS
This feature depends on the OSS feature WOFD-200200 Base Station Power-Saving
Management - LTE.
1.4.20 LBFD-001075 RRU PA Efficiency Improvement

Availability
This feature is:

Summary
This feature monitors the eNodeB transmit power, and dynamically adjusts PA working state
to improve PA efficiency and reduce eNodeB power consumption when RRU transmit power
is low.
This feature is similar to LOFD-001025 Adaptive Power Consumption, but applies to blade
RRUs which utilize new PA technologies. This feature significantly reduces power
consumption and also applies to narrow bandwidth (1.4 MHz, 3 MHz, and 5 MHz).
Benefits
This feature improves PA efficiency and reduces power consumption of the eNodeB.
Description
Lower equipment power consumption helps reduce operators' operating expenses and
improve equipment reliability.
Blade RRUs utilize the latest PA technologies. When RRU transmit power is low, this feature
dynamically adjusts the RRU bias voltage to improve PA efficiency.
Dynamic Adjustment to PA Bias Voltage
In commercial networks, eNodeB traffic load dynamically changes and PA transmit power
changes accordingly. When PA transmit power is high, PA efficiency is high and a high PA
bias voltage is required. When PA transmit power is low, PA efficiency will decrease if PA
bias voltage remains high.
This feature monitors the eNodeB traffic load and decreases PA bias voltage to reduce PA
efficiency based on the real-time traffic load.
This feature only applies to blade RRUs. Compared to LOFD-001025 Adaptive Power
Consumption, this feature is more effective in reducing power consumption and can also be
used at narrow bandwidth (1.4 MHz, 3 MHz, and 5 MHz).
This feature cannot be used with LOFD-001025 Adaptive Power Consumption and only
applies to blade RRUs.
Enhancement
None
Dependency
 eNodeB
The RRU3268 (2600 MHz) must be configured to support this feature.
1.4.21 LBFD-002013 Cell Outage Detection and Compensation

Availability
This feature is:

Summary
This feature automatically detects cell outages and adjusts mobility-related RRM parameters
to compensate for the cells that are down. It shortens the duration of the cell outage, a critical
situation in the network, especially if there is only one frequency or radio access technology
(RAT) available.
Benefits
This feature helps operators reduce the amount of time cells are down and restore as many
subscriber services as possible.
Description
Cell outage is a critical situation, especially if there is only one frequency or RAT available, a
situation that can interrupt services or severely affect KPIs. If there are other frequencies or
RATs available, it is preferable to move UEs from outage cells to these alternative frequencies
or RATs, by triggering handovers instead of increasing the coverage of the surrounding cells.
This feature consists of three functions: cell outage detection, RRM compensation, and cell
outage recovery.
 Cell outage detection
This function consists of real-time monitoring of both pre-defined alarms and cell KPIs.
The system will detect whether a cell is out of service based on the status of certain
pre-defined alarms. KPI monitoring will help to detect outage cells (including sleeping
cells) that have not triggered alarms but still experience cell KPI deterioration. The KPI
thresholds involved are configurable by operators.
In some cases, cell outage can be detected quickly by checking counters related to
eNodeB internal modules. To accelerate the cell outage detection process, this feature
also supports assisted cell outage detection. This method is independent of KPI
measurement. It detects cell outage by checking eNodeB internal parameters every 5
minutes. If the audit result is abnormal, the eNodeB reports the result to the U2000. The
U2000 then determines that a cell outage has occurred.
 RRM compensation
This function adjusts mobility-related RRM parameters so that the UEs can be moved to
the surrounding cells for uninterrupted services. In addition, outage cells are blacklisted
to prevent UEs from neighboring cells from being handed over to, or reselecting to, these
outage cells. The priority for triggering handovers is defined by mobility features
intended to preserve service continuity.
 Cell outage recovery
The system will attempt to recover any cells that it has detected are down.
Once the cells have recovered, the system will stop RRM compensation and roll back
related RRM parameter settings.
Enhancement
 eRAN3.0
Cell outage is detected mainly based on alarms and abnormal KPIs. It takes two
measurement periods to check KPIs. Therefore, the time required by cell outage
detection depends on measurement periods.

 eRAN6.0
Assisted cell outage detection is introduced. eNodeB internal parameters are checked and
abnormal audit results are reported, helping to quickly and accurately detect cell outage.
 eRAN7.0
KPI accumulation is introduced for low-traffic cell outage detection. If the number of
KPI samples within one measurement period is lower than the configured threshold, the
samples will be rolled over into the next measurement period. These samples will
continue to accumulate until the total number of accumulated samples exceeds the
configured threshold. The system will calculate KPIs based on the accumulated samples
in the accumulated measurement periods to detect cell outage.
The system will record the KPIs indicating cell outage detection and cell outage recovery
in CODC SON logs for operator observation and analysis.
Customized KPI detection is introduced. Users can customize the KPIs to be observed
and detection rules to be used as judgment and recovery conditions of abnormal KPIs.
Also the frequency of abnormal events can now be monitored to determine whether KPIs
are abnormal.
RRU failure detection is introduced. The eNodeB now monitors both software and
hardware in real time. If the eNodeB detects an RRU is unavailable for some reason,
such as RF channel failures and link failures, the eNodeB will report these RRU faults to
the U2000. Information related to RRU unavailability will be displayed on the CODC
GUI, allowing for rapid identification of abnormal RRUs in SFN cells.
Dependency
 OSS
This feature requires the OSS feature WOFD-171000 Cell Outage Detection and
Recovery -LTE.
 Other features
This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and
UTRAN, LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN, and
LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000.

LTE FDD eRAN12.1 Feature Description 2 LTE Optional Features
2 LTE Optional Features
2.1 Voice & Other Services

2.2 Radio & Performance
2.3 Networking & Transmission & Security
2.4 O&M
2.1 Voice & Other Services

2.1.1 VoLTE
Overview
Voice over LTE (VoLTE) provides voice services based on the IP multimedia subsystem
(IMS). The VoLTE solution provides the VoLTE feature package and VoLTE Performance
Evolution feature package.
During the first stage of VoLTE network deployment, the VoLTE feature package helps enable
basic or high-definition (HD) VoLTE services and ensure service continuity.
Applications
VoLTE is used to enhance capacity, to improve coverage and quality, to save power, and for
mobility management. The following table describes the features in this package and their
applications.
Applic Feature Description

ation
Capacit LOFD-001016 VoIP This feature is introduced for small-packet services that
y Semi-persistent are periodically transmitted such as VoLTE. Before
enhanc Scheduling UEs enter talk spurts, the eNodeB uses control
ement messages on the PDCCH to allocate fixed resources to
them. Before exiting talk spurts or releasing resources,
the UEs do not need to apply for resource allocation
from the PDCCH again, saving PDCCH resources.


ation
LOFD-001017 This feature compresses voice packet headers to reduce
RObust Header air interface overhead and improve capacity for voice
Compression services.
(ROHC)
Covera LOFD-001048 TTI This feature enables data to be repeatedly transmitted in
ge Bundling multiple consecutive TTIs with different HARQ
improv redundancy versions for UEs with poor signal quality.
ement This increases the once-off transmission success rate.
LOFD-001017 This feature compresses voice packet headers, reducing
RObust Header the size of the entire packet. ROHC reduces voice
Compression packet transmission errors with fewer segments,
(ROHC) enhancing cell-edge coverage for voice services.
Mobilit LOFD-001022 This feature ensures voice service continuity when the
y SRVCC to UTRAN coverage of the E-UTRAN is discontiguous and the
manage E-UTRAN and UTRAN together provide continuous
ment network coverage.
LOFD-001087 This feature enables voice services to fall back to a
SRVCC Flexible configured preferential UTRAN frequency. This
Steering to UTRAN decreases the number of UTRAN frequencies to be
measured, which reduces the measurement time and the
probability of UE errors.
LOFD-001023 This feature ensures voice service continuity when the
SRVCC to GERAN coverage of the E-UTRAN is discontiguous and the
E-UTRAN and GERAN together provide continuous
network coverage.
Value
 Capacity enhancement
VoLTE can improve control and service channel processing capacity for VoLTE-service
UEs. This improvement is defined as an increase in user volume. The feature package
increases the control channel processing capacity by up to 40% for UEs performing
VoLTE services at 12.65 kbit/s, and up to 20% for UEs performing HD VoLTE services
at 23.85 kbit/s. The control channel capacity gains are affected by the following:
− System bandwidth
More system bandwidth means that there are more resources available on the
PDCCH resources but also more users. Therefore, it is more likely that there will be
CCE resource conflicts on the PDCCH, reducing gains.
− Voice coding rate
A lower voice coding rate leads to smaller gains.
− Proportion of UEs that support semi-persistent scheduling
A greater proportion leads to greater gains.
With other conditions unchanged, this feature package reduces the physical resource
blocks (PRBs) occupied by UEs performing VoLTE services using a 12.2 kbit/s AMR

voice coding rate by up to 20%. The service channel capacity gains are affected by the
following:
− Proportion of UEs that support ROHC
− Ratio of IPv6 addresses to IPv4 addresses on the network
A greater ratio leads to greater gains.
− ROHC success rate
A greater ROHC success rate leads to greater gains.
 Coverage improvement
VoLTE can improve coverage for uplink services and decrease the uplink packet loss rate
in weak-coverage areas. The gains are affected by the uplink transmit power. This feature
package provides gains only when the uplink transmit power is limited before the
downlink transmit power is.
Uplink VoLTE coverage is improved by up to 3 dB (the MOS equals 3).
 Mobility management
SRVCC-related features ensure voice service continuity when E-UTRAN coverage is
discontiguous and multiple RANs together provide continuous network coverage.
2.1.1.1 LOFD-001016 VoIP Semi-persistent Scheduling
Availability
This feature is
Summary
Semi-persistent Scheduling is a technique for efficiently assigning resources for spurts of
traffic in a wireless communication system. A semi-persistent resource assignment is valid as
long as more data is sent within a predetermined time period from last sent data, and expires if
no data is sent within the predetermined time period. For VoIP, a semi-persistent resource
assignment may be granted for a voice frame in anticipation of a spurt of voice activity.
Benefits
The semi-persistent scheduling is critical for VoIP services and provides the following
benefits:
 Guarantees the QoS for VoIP services.
 Reduces the control signaling overhead for VoIP transmission.
 Maximizes the resource utilization by dynamically activating/deactivating resource
allocation according to the transition between silent period and talk spurt.
Description
This feature is critical to deliver the voice service with acceptable quality. LTE is optimized in
terms of packet data transfer, and the core network is purely IP packet-based. The voice is

transmitted by means of VoIP instead of using the traditional circuit-based method. To ensure
the voice quality, a semi-persistent scheduling solution is used for VoIP services.
VoIP is a real-time service with small and fixed-length data packets and constant time of
arrival. VoIP traffic consists of talk spurts and silent periods. The Adaptive Multi-Rate (AMR)
codec could yield quiet burst voice traffic. During the talk spurt, VoIP packets normally arrive
at intervals of 20 ms; during the silent period, Silence Indicator (SID) packets arrive at an
interval of 160ms.
The semi-persistent scheduling allocates a certain amount of resources (such as resource
blocks) for the voice call during the call setup period through RRC signaling. The allocation
is semi-persistent and does not need to be requested again through UL/DL control signaling
until the call ends and the resources are released. To allow the maximum resource utilization
during the silent period, the resource allocation will be deactivated by means of explicit
signaling exchanged over the Physical Downlink Control Channel (PDCCH). When the VoIP
call transits from the silent period to the talk spurt, similar PDCCH signaling is used to
activate the semi-persistent resource allocation. The semi-persistent scheduling significantly
reduces the PDCCH overhead and ensures the QoS for VoIP services by reserving the
resources in a semi-persistent fashion. It also improves the resource utilization by dynamically
activating or deactivating resource allocation activities between talk spurt and silent period.
If both VOIP and data traffic are present for an UE, dynamic scheduling is used instead of
semi-persistent scheduling.
Starting from eRAN2.1, when it is 1.4MHz system bandwidth, it will not use semi-persistent
schedule and when it is other system bandwidth, it will preserve some percent of total RB
resource. The reason is that if VOIP occupies a lot of resource, it will impact the schedule of
signal, which is scheduled after VOIP.
Enhancement
None
Dependency
 UE
The UE should support semi-persistent scheduling.
 Others
This feature is not supported in 1.4MHz system bandwidth.
This feature is applicable for VoIP service only.
2.1.1.2 LOFD-001017 RObust Header Compression (ROHC)
Availability
This feature is

Summary
ROHC provides an efficient and flexible header compression mechanism which is particularly
important to improve the bandwidth utilization for VoIP service with small payload size.
Benefits
ROHC can reduce the size of IP packet head and significantly improve the payload/header
ratio for VoIP service with small payload. It also shortens the response time in order to
guarantee the high ratio of link usage between the eNodeB and the UE.
Description
As more and more wireless technologies are being deployed to carry IP traffic, it is a vital
significance to reduce the total size of header of transmission, because the overhead of the
packet is large. This can improve the usage of the bandwidth resources, particularly for
service with small payload (for example, VoIP service).
On an end-to-end transmission path, the entire header information is necessary for all packets
in the flow. However, over a wireless link (a portion of the end-to-end path), some of the
information become redundant and can be reduced over the link, since they can be
transparently recovered at the receiving side.
ROHC protocol provides an efficient, flexible, and future-proof header compression concept
based on compression/decompression of IP/UDP/RTP/ESP packets header. It is designed to
operate efficiently and robustly over various link technologies with different characteristics,
especially for wireless transmission.
In LTE system, the ROHC function is located in Packet Data Convergence Protocol (PDCP)
entities associated with user plane packets. For the UL, the packets are compressed by the UE
and decompressed by the eNodeB; for the DL, the packets are compressed by the eNodeB and
decompressed by the UE.
The relative gain for specific flows or applications depends on the size of the payload used in
each packet. Header compression is expected to significantly improve the bandwidth
utilization for VoIP service with small payload size.
Huawei LTE eNodeB supports profiles 0x0000–0x0004 based on both IPv4 and IPv6 (Micro
eNodeB supports profile 0x0000,0x0001 and 0x0002). Table 2-2 shows the profile identifiers
and their associated header compression protocols.
Table 2-1 ROHC profile identifier and header compression protocol
Profile Identifier Usage:

0x0000 No compression
0x0001 RTP/UDP/IP
0x0002 UDP/IP
0x0003 ESP/IP
0x0004 IP

Enhancement
 In eRAN2.2
for VoIP packets, an additional compression scheme of ROHC which is called the List
Compression is supported.
Dependency
 UE
The UE should support ROHC.
2.1.1.3 LOFD-001048 TTI Bundling
Availability
This feature is:
 Available in LampSite eNodeBs.
Summary
TTI bundling transmission is introduced to improve LTE uplink coverage. The UEs at the cell
edge with poor uplink SINR can retransmit the same data block in continuous subframes by
means of TTI bundling.
Benefits
TTI bundling helps improve uplink coverage and indoor reception for voice.
Description
TTI bundling transmission is introduced to improve LTE uplink coverage. The UEs at the cell
edge with poor uplink SINR can retransmit the same data block in continuous subframes by
means of TTI bundling. The activation and deactivation of TTI bundling transmission is
controlled by the RRC signaling message.
TTI bundling is configured at the RRC layer. TTI_BUNDLE_SIZE specifies the number of
TTIs in a TTI bundle. Within a TTI bundle, HARQ retransmissions are non-adaptive and shall
be performed without waiting for feedback (NACK or ACK) related to previous transmissions
according to TTI_BUNDLE_SIZE. The feedback for a TTI bundle is only received for a
specific TTI corresponding to TTI_BUNDLE_SIZE. A retransmission of a TTI bundle is also
a TTI bundle. TTI_BUNDLE_SIZE is always set to 4.
Enhancement
 eRAN8.1
When performing hybrid services, UEs enter the TTI bundling state if VoIP services
(QCI of 1) are included.
 eRAN12.1
1. The enhanced TTI bundling function introduced in 3GPP Release 12 is supported.

2. In eRAN12.1, the eNodeB can determine whether to stop TTI bundling when the
VoLTE or PPT service bearer is removed (hang-up).
3. TTI bundling is optimized in handover and reestablishment scenarios and can work
with high order MCSs:
(1) For UEs that are in the TTI bundling state before handovers or reestablishments, the
TTI bundling indication in a handover command or reestablishment message is set to
true, indicating that the UE is enabled with TTI bundling.
(2) In versions earlier than eRAN12.1, TTI bundling can work with only MCSs ranging
from 1 to 9. From eRAN12.1 onwards, TTI bundling can work with any MCSs.
Dependency
 eNodeB
None
 eCoordinator
None
 UE
The UE should support TTI Bundling.
None
 Core network
None
 OSS
None
 Other features
This feature does not support the 1.4 MHz system bandwidth.
This feature applies only to VoIP services.
 Others
None
2.1.1.4 LOFD-001022 SRVCC to UTRAN
Availability
This feature is:
Summary
Single Radio Voice Call Continuity (SRVCC) smoothly switches over a UE performing
IMS-based VoIP services in the LTE network to the CS domain of another-RAT network for
voice services, which ensures voice call continuity. This UE cannot work in two or more
modes simultaneously.

Benefits
When a UE moves from E-UTRAN to UTRAN, SRVCC maintains voice call continuity for
the UE.
Description
When a UE moves from E-UTRAN to UTRAN, SRVCC maintains voice call continuity for
the UE.
To ensure that voice services can be transferred from the LTE network to the CS domain
through SRVCC, the upper-layer anchor points of the voice session are set in the IMS.
For SRVCC from E-UTRAN to UTRAN, the MME first receives the handover request from
E-UTRAN with the indication that this is for SRVCC handling, and then triggers the SRVCC
procedure with the MSC Server enhanced for SRVCC through the Sv reference point if the
MME has SRVCC STN-SR information for this UE. The MSC Server enhanced for SRVCC
then initiates the session transfer procedure to the IMS and coordinates it with the CS
handover procedure to the target cell. The MSC Server enhanced for SRVCC then sends the
Forward Relocation Response to the MME, which includes the necessary CS HO command
information for the UE to access the UTRAN.
Handling of any non-voice PS bearer is done by the PS bearer splitting function in the MME.
The MME may suppress the handover of non-voice PS bearer during the SRVCC procedure.
The handover of non-voice PS bearer is performed according to the Inter-RAT handover
procedure defined in 3GPP TS 23.401. During the SRVCC and PS handover, the MME
processes the Forward Relocation Response message sent by the MSC.
The following figure shows the signaling process of SRVCC from E-UTRAN to UTRAN.
Figure 2-1 Signaling process of SRVCC from E-UTRAN to UTRAN
Enhancement
eRAN12.1

The voice quality-based SRVCC from E-UTRAN to UTRAN is supported in eRAN12.1. This
type of SRVCC is triggered based on the UE's uplink or downlink voice packet loss rate. It
provides a best-effort path for the VoLTE UE with poor voice experience due to interference
and high load.
Dependency
 CN
This feature is dependent on IMS multimedia telephony services.
2.1.1.5 LOFD-001087 SRVCC Flexible Steering to UTRAN
Availability
This feature is
Summary
Single radio voice call continuity (SRVCC) flexible steering to UTRAN includes two
functionalities:
 SRVCC only to the highest-priority UTRAN frequency
This functionality is applicable to the operator that has several UTRAN frequencies, and
expects SRVCC call is setup in one frequency first.
 SRVCC to UTRAN for an LCS required VoIP services
With IP multimedia subsystem (IMS) deployed, the E-UTRAN can provide voice over IP
(VoIP) services. However, if evolved packet core (EPC) does not support the location
service (LCS) but which is required by the voice call, an SRVCC procedure can transfer
UE to an LCS capable UTRAN network.
Benefits
SRVCC to the highest-priority UTRAN frequency saves the UE measurement time.
Meanwhile, the operator can assign the highest priority to the UTRAN frequency that covers
the largest area which is often on a lower band. In this way, UE does not need further
handover after SRVCC to UTRAN, thus it improves user experience.
When the EPC connected by the eNodeB does not not support LCS, UE can perform SRVCC
to get a LCS capable voice call.
Description
If an operator has both E-UTRAN and UTRAN networks and UTRAN has multiple
frequencies, it is recommended that lower UTRAN frequencies have higher priority in
SRVCC. With this feature the UE can be transferred to a configured UTRAN frequency with
highest-priority during SRVCC to UTRAN. And the UE which does not support the
configured UTRAN frequency with highest-priority is transferred to other lower-priority
UTRAN frequencies according to measurement result.

If the EPC that an eNodeB connected to does not support LCS, EPC will send a CS fallback
indicator to eNodeB to indicate that. When a VoIP call is setup, the eNodeB will first check
the service type requested by the UE. If the UE requests a VoIP service which needs LCS, the
eNodeB makes UE to perform an SRVCC procedure to an LCS capable UTRAN network.
Enhancement
None
Dependency
 Other features
LOFD-001022 SRVCC to UTRAN and LOFD-001078 E-UTRAN to UTRAN CS/PS
Steering
2.1.1.6 LOFD-001023 SRVCC to GERAN
Availability
This feature is:
Summary
Single Radio Voice Call Continuity (SRVCC) enables a UE performing IMS-based VoIP
services to smoothly switch over from an LTE network to the CS domain of another-RAT
network for voice services, which ensures voice call continuity. This UE cannot work in two
or more modes simultaneously.
Benefits
When a UE moves from the E-UTRAN to the GERAN, SRVCC maintains voice call
continuity for the UE.
Description
To ensure that voice services can be transferred from the LTE network to the CS domain
through SRVCC, the upper-layer anchor points of the voice session are set in the IMS.
In SRVCC from E-UTRAN to GERAN, the MME first receives a handover request from the
E-UTRAN with the indication that this is for SRVCC handling. Then, it triggers the SRVCC
procedure with the MSC server enhanced for SRVCC through the Sv interface if the MME
has session transfer number for SRVCC (STN-SR) information for this UE. The MSC server
enhanced for SRVCC initiates session transfer to the IMS and performs a CS handover to the
target cell in coordination with the IMS. The MSC server enhanced for SRVCC then sends a
Forward Relocation Response message to the MME. The message includes necessary CS
handover command information for the UE to access the GERAN.
The PS bearer splitting function in the MME handles non-voice PS bearers. The MME may
suppress the handover of non-voice PS bearer during the SRVCC procedure. The handover of
non-voice PS bearer is performed in accordance with the inter-RAT handover procedure

defined in 3GPP TS 23.401. During the SRVCC and PS handover, the MME processes the
Forward Relocation Response message sent by the MSC.
The following figure shows the signaling process of SRVCC from E-UTRAN to GERAN.
Figure 2-2 Signaling procedure of SRVCC to GERAN
Enhancement
eRAN12.1
The voice-quality-based SRVCC from E-UTRAN to GERAN is now supported in eRAN12.1.
This type of SRVCC is triggered based on the UE's uplink or downlink voice packet loss rate.
It provides a best-effort path for the VoLTE UE with poor voice experience due to interference
and high load.
Dependency
 Core network
This feature is dependent on IMS multimedia telephony services.
2.1.2 VoLTE Performance Evolution

Overview
Voice over LTE (VoLTE) provides voice services based on the IP multimedia subsystem
(IMS). The VoLTE solution provides the VoLTE feature package and VoLTE Performance
Evolution feature package.
During the second or third stage of VoLTE network deployment, the VoLTE performance
enhancement feature package provides the following functions:
 The ROHC, TTI bundling, and VoLTE rate control features improve coverage.
 The semi-persistent scheduling, ROHC, and voice characteristic awareness scheduling
features enhance capacity.

VoLTE Performance Evolution improves the experience of cell-edge UEs accessing HD voice
services, ensures HD voice service quality during heavy-traffic events, and allows for more
voice-service UEs.
Applications
VoLTE Performance Evolution is used to improve coverage and quality, to save power, and
for mobility management. The following table describes the features in this package and their
applications.
Appl Feature Description

icatio
n
Cover LOFD-111207 VoLTE This feature adjusts the AMR-NB or AMR-WB rate for
age Rate Control uplink voice services depending on the uplink channel
impro quality and voice quality, improving the quality of voice
veme services.
nt
LEOFD-121202 EVS This feature adjusts the EVS-SWB rate for uplink voice
Rate Control services depending on the uplink channel quality and
voice quality, improving the quality of voice services.
LOFD-120204 VoLTE This feature increases the acceptable delay over the Uu
Coverage interface, which reduces uplink packet loss caused by
Enhancement Based on congestion over the Uu interface, and improves uplink
Extended Delay coverage for voice-service UEs.
Budget
Qualit LOFD-081229 Voice During uplink dynamic scheduling, the eNodeB adjusts
y Characteristic the scheduling priorities of UEs based on their waiting
impro Awareness Scheduling times and estimates the voice volume to be dynamically
veme scheduled in the uplink. An independent inactivity timer
nt is configured for voice services. These adjustments
improve voice quality, decrease the service drop rate,
and increase the proportion of satisfied voice-service
users.
LOFD-081219 This feature enables an appropriate coordinated cell to
Inter-eNodeB VoLTE work with the serving cell of a voice-service UE to
CoMP implement UL CoMP. It reduces the number of uplink
transport blocks erroneously transmitted during initial
transmission, and decreases the packet loss rate,
improving voice quality and cell-edge coverage for
voice-service UEs.
LOFD-121202 VoLTE This feature provides special processing for calling UEs.
User Prior Access It increases the probability of successful accesses and
therefore increases the call setup success rate, especially
in heavy-traffic events when the user number is limited.
LOFD-121214 VoLTE When identifying a UE in a weak-coverage area, the
Coverage-based CSFB eNodeB refuses to set up a dedicated voice bearer for
the UE. The IMS then requests that the UE retry CSFB,
helping ensure that the attempted voice call will be
successful.

Value
VoLTE Performance Evolution can improve the coverage for uplink services. Uplink
VoLTE coverage is improved by up to 4.5 dB (the MOS equals 3).
The uplink service channel coverage gains are affected by the following:
− Transmit power
This feature package provides gains only when the uplink transmit power is limited
before the downlink transmit power is.
− Proportion of low signal to interference plus noise ratio (SINR) values
A greater proportion leads to greater gains. Essentially, a larger number of cell-edge
UEs leads to greater gains.
− Proportion of UEs that support EVS voice coding rates, and proportion of voice
adjustment which takes effect
Greater proportions lead to greater gains.
 Quality improvement
VoLTE Performance Evolution can improve voice quality and decrease the packet loss
rate when the traffic volume increases. The uplink packet loss rate of VoLTE services is
decreased by up to 35%.
The voice quality gains are affected by the following:
− User volume
A larger user volume in heavy-traffic events leads to greater gains.
− Discontinuous reception (DRX)
When DRX is enabled, this feature package provides greater gains.
− Proportion of voice-service UEs
2.1.2.1 LOFD-081229 Voice Characteristic Awareness Scheduling
Availability
This feature was introduced in eRAN8.1.
Summary
This feature is implemented based on uplink delay-based dynamic scheduling and uplink
VoLTE volume estimation for dynamic scheduling. This feature adjusts scheduling priorities
and estimates SR data amount accuracy to improve uplink voice performance in heavy traffic
scenarios.
The independent configuration for voice inactivity timer improves user experiences on voice
services.
Benefits
This feature improves uplink voice performance in heavy traffic scenarios.

Description
 Uplink delay-based dynamic scheduling
The eNodeB prioritizes voice packets based on their waiting times and sorts scheduling
priorities. A longer waiting time indicates a higher scheduling priority.
The priorities of voice and data services are sorted in this mode. Within a certain delay
range, the priorities of signaling and voice services are higher than the priority of data
services. This way, voice service quality is improved in heavy-traffic scenarios.
Specifically, voice quality of UEs with poor channel conditions is improved. When
delay-based scheduling applies to data services, the eNodeB makes a balance among
scheduling queues of data services and improves data service throughput in heavy-traffic
scenarios.
 Uplink VoLTE volume estimation for dynamic scheduling
The eNodeB estimates uplink VoLTE volume for dynamic scheduling based on the
VoLTE service model and uplink scheduling intervals:
− During talk spurts, the eNodeB estimates the number of voice packets in the UE
buffer based on their uplink scheduling intervals and then calculates the uplink
VoLTE volume for dynamic scheduling based on the size of a voice packet.
− During silent periods, the eNodeB takes the size of a voice packet as the uplink
VoLTE volume for dynamic scheduling.
When a called UE does not answer the call, the calling UE is released after the UE inactivity
timer expires. In this case, the calling UE in idle mode may be reselected to a cell that does
not support voice services. If the called UE starts to answer the call, the service with QCI of 1
of the calling UE fails to be set up.
With independent configuration for voice inactivity timer, the UEs can distinguish voice and
non-voice scenarios. That is, the length of the UE inactivity timer can be independently
configured to avoid the preceding negative impact.
Enhancement
 eRAN11.1
Delay-based scheduling now applies to both voice and data services.
Applicability
Macro eNodeB Micro eNodeB LampSite eNodeB
Yes Yes Yes
Dependency
 eNodeB
None
 eCoordinator
None
 UE
None
 Core network

None
 Other NEs
None
 Other features
− LBFD-00101502 Dynamic Scheduling
 Others
None
2.1.2.2 LOFD-081219 Inter-eNodeB VoLTE CoMP
Availability
This feature is:
 Available in micro eNodeBs (BTS3203E, BTS3911E, and BTS3912E) as of eRAN11.1.
Summary
When only LOFD-001066 Intra-eNodeB UL CoMP and LOFD-070222 Intra-eNodeB UL
CoMP Phase II are enabled, only intra-BBU intra-BBP or inter-BBP UL CoMP is supported.
When LOFD-081219 Inter-eNodeB VoLTE CoMP works with the preceding two features,
inter-BBU UL CoMP with BBUs connected through an IP RAN (also called through a relaxed
backhaul network) is supported.
When BBUs are located in different places without dedicated transmission links between them,
inter-BBU coordination data can be exchanged through a relaxed backhaul network.
Benefits
This feature allows BBUs to be connected through an IP RAN rather than through USUs.
Without transport network reconstruction, this feature reduces the number of uplink TBs
unsuccessfully transmitted during the initial transmission, number of retransmissions, residual
block error rate (RBLER), and packet loss rate, thereby improving voice quality for UEs in
the overlapping areas between inter-BBU cells.
Description
When transmission conditions are not satisfactory because of transmission delay and
transmission bandwidth, this feature uses the antennas of cells served by different BBUs to
jointly receive signals from a UE. The serving cell and cooperating cells are set up in different
BBUs and have a loose requirement on transmission between BBUs.
This feature requires time synchronization between BBUs (for example, using a GPS clock).
The eNodeB periodically measures one-way transmission delays between the serving cell and
neighboring cells connected through a relaxed backhaul network. If a delay exceeds the
maximum permissible value, the eNodeB disables UL CoMP between these cells.

Figure 2-3 UL CoMP between BBUs connected through a relaxed backhaul network
The following figure illustrates the differences among relaxed backhaul, centralized Cloud
BB, and distributed Cloud BB.
Figure 2-4 Differences among relaxed backhaul, centralized Cloud BB, and distributed Cloud BB
 Cloud BB: Two or more BBUs communicate with each other and process services by physically
connecting the BBUs and USUs using signal cables.
 Centralized Cloud BB: BBUs and USUs are located in the same place, and the length of the signal
cables connecting the BBUs and USUs is less than 100 m.

 Distributed Cloud BB: BBUs and USUs, or the first-level and second-level USUs, are remotely
connected using signal cables with the length less than 10 km.
This feature can be used in the following scenarios:

 Inter-BBU macro-macro UL CoMP
The following figure shows inter-BBU macro-macro UL CoMP.
 Inter-BBU macro-micro UL CoMP

The signals sent by a UE in a macro cell can be jointly received by the macro cell and
micro cells (including those served by LPNs). The joint reception improves the
performance of this UE through coordination.
 Inter-BBU micro-micro UL CoMP
When micro eNodeBs (including LPNs) are adjacent to each other, micro-micro UL
CoMP can be performed. The principles are the same as those for macro-macro UL
CoMP.
Enhancement
 eRAN11.1
− This feature can be used in a HetNet.
− This feature does not require TTI bundling.
Applicability
Yes Yes Yes

Dependency
 eNodeB
− BBP
The LBBPc, LBBPd1, and blade BBU do not support this feature.
Only the UBBPd and UBBPe support VoLTE CoMP in 4R cells.
− Cell
Cells can all be in 1R, 2R, or 4R mode; or some cells are in one of these modes and
others are in another of these modes.
− Micro eNodeB
The BTS3202E does not support this feature.
 eCoordinator
None
 UE
VoLTE must be supported.
A relaxed backhaul network is required.
 Core network
None
 OSS
None
 Other features
Prerequisite features:
− LOFD-001012 UL Interference Rejection Combining
− LOFD-001066 Intra-eNodeB UL CoMP
− LOFD-070222 Intra-eNodeB UL CoMP Phase II
Mutually exclusive features are the same as those for LOFD-070222 Intra-eNodeB UL
CoMP Phase II.
 Others
None
2.1.2.3 LOFD-111207 VoLTE Rate Control
Availability
This feature is introduced in eRAN11.1.
Summary
VoLTE Rate Control adjusts the AMR-NB/AMR-WB rate for uplink voice services depending
on the uplink channel quality and voice quality. The feature helps improve the voice quality
and LTE uplink coverage.
Benefits
This feature helps improve the voice quality and LTE uplink coverage.

Description
Figure 2-5 Before the feature is enabled
Before the feature is enabled, UEs use a fixed coding rate. As shown in Figure 2-5, a UE uses
a high voice coding rate during the access. When the UE moves to a weak coverage area, the
coding rate remains unchanged. As a result, the uplink voice coverage is restricted.
Figure 2-6 After the feature is enabled
After this feature is enabled, the eNodeB adjusts the AMR-NB/AMR-WB rate for uplink
voice services depending on the uplink channel quality and voice quality, as shown in Figure
2-6.
 When the uplink channel quality and voice quality are favorable, a high voice coding
rate is used to further improve the voice quality.
 When the uplink channel quality and voice quality are poor, a low voice coding rate is
used to improve the uplink voice coverage.
Enhancement
None
Dependency
 eNodeB
None
 eCO
None
 UE
None
 CN
None
 Other NEs
None

 Other features
This feature applies only to VoLTE services.
 Others
None
2.1.2.4 LOFD-120204 VoLTE Coverage Enhancement Based on Extended

Delay Budget
Availability
This feature is:
Summary
This feature extends the tolerable air-interface delay for voice over LTE (VoLTE) UEs with
limited uplink coverage. It reduces the probability of uplink packet loss caused by congestion
on the air interface.
Benefits
This feature improves voice quality and enhances uplink coverage for VoLTE UEs.
Description
This feature extends the acceptable air-interface delay and reduces the probability of uplink
packet loss by taking the following measures:
 Optimizes the following settings for the bearer with QCI 1 delivered to each VoLTE UE:
PDCP discard timer, maximum number of HARQ transmissions in the uplink, reordering
timer at the receiver in AM, and reordering timer at the receiver in UM.
 Selects the optimal MCS and number of RBs based on the amount of VoLTE data to be
scheduled.
Enhancement
None

Dependency
 eNodeB
None
 eCoordinator
None
 UE
None
None
 Core network
None
 OSS
None
 Other features
 Others
When this feature is enabled, the maximum number of uplink RLC segments cannot be 0.
This number is determined by one of the following parameters:
− In TTI bundling scenarios: TtiBundlingRlcMaxSegNum
− In scenarios other than TTI bundling: UlVoipRlcMaxSegNum
2.1.2.5 LOFD-121214 VoLTE Coverage-based CSFB
Availability
This feature is:
Summary
This feature determines whether to set up the dedicated voice bearer based on uplink channel
quality. When identifying a UE in a weak-coverage area, the eNodeB refuses to set up the
dedicated voice bearer for the UE, and the IMS requests the UE to retry a CSFB call. This
tries to ensure a successful voice call.
Benefits
This feature prevents UEs initiating VoLTE calls in weak-coverage areas from triggering
SRVCC before alerting (bSRVCC) or SRVCC in alerting phase (aSRVCC), which may cause
handover failures or even call drops. In this way, this feature reduces the call drop rate for
VoLTE UEs.

Description
After this feature is enabled, the eNodeB calculates uplink path loss based on the PHR
reported by a UE and measures uplink SRS or DMRS to obtain the uplink SINR. The eNodeB
determines whether the UE is in a weak-coverage area based on the path loss and SINR. If the
UE is in a weak-coverage area, the eNodeB refuses to set up the dedicated voice bearer. Then,
the IMS requests the UE to retry a CSFB call:
 If the UE acts as a caller, the IMS sends an SIP message (SIP 500/380/503) to the UE,
notifying the UE of initiating a CSFB procedure.
 If the UE acts as a callee, the EPC sends a CS Paging Notification message to the UE,
notifying the UE of initiating a CSFB procedure.
Enhancement
None
Applicability
Yes Yes Yes
Dependency
 eNodeB
None
 eCoordinator
None
 UE
The UE is required to initiate a CSFB call after receiving the SIP 500/503/380 message.
 Core network
The IMS is required to instruct the UE to initiate a CSFB call after receiving a message
indicating the voice service setup failure.
 Other NEs
None
 Other features
This feature requires LOFD-001033 CS Fallback to UTRAN or LOFD-001034 CS
Fallback to GERAN.
Mutually exclusive features:
None
 Others
None

2.1.2.6 LOFD-121202 VoLTE User Prior Access
Availability
This feature is:
Summary
3GPP Release 12 added the cause value "mo-VoiceCall-v1280" for RRC connection setup in
order to identify the calling party of voice services. The eNodeB can enable specific functions
for the identified calling party to improve VoLTE performance.
Benefits
This feature increases the VoLTE service setup success rate in congestion scenarios.
Description
The following figure shows how an eNodeB identifies the calling party of a VoLTE service.
After the calling party is identified based on the RRC connection setup cause, the eNodeB
performs differentiated processing as follows:
1. On a high-traffic network, the eNodeB identifies the calling party in the RRC connection
setup phase and enables certain functions to allow preferential access of the calling party over
data-service UEs and increasing the VoLTE service setup success rate. These functions
include eliminating the restriction of UE number during preallocation for VoLTE services,
optimizing admission and congestion control, optimizing flow control, and raising the
preemption priority of the calling party.
2. After identifying the calling party, the eNodeB performs optimized DRX handling on the
QCI 5 bearer so that SIP messages will be assigned more scheduling opportunities.
Enhancement
None

Dependency
 eNodeB
None
 eCoordinator
None
 UE
The UE must be capable of carrying the cause value of mo-VoiceCall-v1280 in
RRCConnectionRequest messages for VoLTE services.
None
 Core network
None
 OSS
None
 Other features
 Others
None
2.1.3 CS Fallback
Overview
Circuit switched fallback (CSFB) enables UEs to fall back to the UTRAN, GERAN, or
CDMA2000 1xRTT, and provides voice services for the UEs when the following conditions
are met:
 The UEs are in the areas where an E-UTRAN and a UTRAN, GERAN, or CDMA2000
1xRTT overlap.
 The E-UTRAN cannot provide voice services.
The features in this package allow for efficient use of existing CS networks when the IP
multimedia subsystem (IMS) is not yet ready for full commercial deployment.
Applications
The CS Fallback feature package provides basic voice call fallback, reduction of voice call
fallback delay, and flexible policy configuration. The following table lists the features and
their applications.

ation
Basic LOFD-001033 CS When UEs camp on the E-UTRAN, which cannot
voice Fallback to UTRAN provide CS services, these features allow UEs to
call fall back to the UTRAN, GERAN, or CDMA2000
fallbac LOFD-001034 CS 1xRTT, thereby providing voice services for the
k Fallback to GERAN UEs.
LOFD-001035 CS


ation
Fallback to CDMA2000
1xRTT
LOFD-001090 Enhanced
CS Fallback to
CDMA2000 1xRTT
Reduce LOFD-001052 Flash CS The E-UTRAN uses a RIM procedure to obtain
d voice Fallback to UTRAN system information for the UTRAN or GERAN
call cells. In this way, the UEs access the UTRAN or
fallbac LOFD-001053 Flash CS GERAN cells with no need to read the system
k delay Fallback to GERAN information in the cells. This reduces the access
delay.
LOFD-070202 These features enable UEs to fall back to the
Ultra-Flash CSFB to UTRAN or GERAN through the SRVCC
UTRAN procedure. The procedure has CS resources on the
UTRAN or GERAN prepared in advance and omits
LOFD-081283 certain protocol-defined signaling procedures
Ultra-Flash CSFB to during access to the UTRAN or GERAN,
GERAN shortening the voice call fallback delay.
Flexibl LOFD-001068 CS In multi-PLMN or national roaming scenarios,
e policy Fallback with LAI to these features enable UEs to fall back to the
configu UTRAN networks preferred by operators.
ration In a multi-LAC scenario, these features
LOFD-001069 CS
Fallback with LAI to preferentially enable UEs to fall back to UTRAN or
GERAN GERAN cells of the same LAC.
LOFD-001088 CS These features flexibly configure target RATs of

Fallback Steering to fallback based on UE status.
UTRAN
LOFD-001089 CS
Fallback Steering to
GERAN
LOFD-001091 CS During voice call fallback, these features select
Fallback to CDMA2000 frequencies based on frequency-specific factors.
1xRTT Based on
Frequency-specific
Factors
Value
 Basic voice call fallback
In an early phase of evolved packet system (EPS) construction, operators who own a
mature UTRAN or GERAN can protect their investments in legacy CS networks and
reduce their investments in the EPS by using legacy CS networks to provide CS services.

Due to benefits in the technological maturity, industry chain, and deployment costs,
CSFB serves as an interim solution for voice service access before mature commercial
use of IMS.
 Reduced voice call fallback delay
In addition to the value provided by basic voice call fallback, flash CSFB to UTRAN or
GERAN and ultra-flash CSFB to UTRAN shorten the fallback delay.
 Flexible policy configuration
CSFB helps operators flexibly configure RAT and frequency information for CSFB.
In multi-PLMN or national roaming scenarios, these features enable UEs to fall back to
the networks preferred by operators. In a multi-LAC scenario, these features
preferentially enable UEs to fall back to UTRAN or GERAN cells of the same LAC.
2.1.3.1 LOFD-001033 CS Fallback to UTRAN
Availability
This feature is:
Summary
When UE is in the E-UTRAN and UTRAN coverage overlapped area and E-UTRAN cannot
provide CS-domain services for the UE, we can use CS fallback to UTRAN to provide
CS-domain service for the UE.
Benefits
We can use CS fallback to UTRAN to provide CS-domain service for the UE which is
camped in the E-UTRAN that cannot provide any CS-domain service for the UE.
Description
The CS fallback in EPS enables the provisioning of CS-domain services by reuse of CS
infrastructure when the UE is served by E-UTRAN. A CS fallback enabled terminal,
connected to E-UTRAN may use UTRAN to establish one or more CS-domain services. This
function is only available in case E-UTRAN coverage is overlapped by UTRAN coverage.
CS fallback and IMS-based services shall be able to co-exist in the same operator's network.
The CS fallback in EPS function is realized by using the SGs interface mechanism between
the MSC Server and the MME.

Figure 2-7 Network architecture of CSFB to UTRAN
The MGW is not shown in the figure since the CS fallback in EPS does not have any impacts
to the U-plane handling.
Enhancement
 In eRAN6.0
eNodeB can perform circuit switched (CS) fallback to Universal Mobile
Telecommunications System (UMTS) cells based on UMTS cell load information, which
is shared with LTE cells by using the RAN Information Management (RIM) procedure.
Cell load information shared by a radio network controller (RNC) with an eNodeB is
used in target cell selection for CS fallback. This increases the success rate of CS
fallback to the universal terrestrial radio access network (UTRAN), prevents unnecessary
delay and signaling overhead, and improves user experience.
 eRAN12.1
The load-based CSFB function is enhanced. If all the measurement reports are received from
high-load cells, the eNodeB does not immediately trigger handovers or redirections but waits
for a low-load cell's measurement report. This is to improve the success rate of CSFB to
UTRAN.
Dependency
 UE
The UE needs to support CSFB.
 Other features
UTRAN.
 Others
Target load based CS fallback to UTRAN requires the core network and RNC to support
the RIM-based load information transfer to E-UTRAN.
2.1.3.2 LOFD-070202 Ultra-Flash CSFB to UTRAN
Availability
This feature is


Summary
This feature applies to areas where UMTS and LTE networks are deployed and LTE networks
do not support VoIP services.
When a UE initiates a CS service setup request in an LTE cell, this feature enables the RNC to
prepare CS resources before a CS fallback through the SRVCC handover procedure. This
shortens the access delay for the CS fallback and improves user experience.
Benefits
This feature shortens the access delay for CS fallbacks by around 1 second and improves user
experience.
Description
This feature works as follows:
1. When a UE initiates a CS service setup request in an LTE cell, the eNodeB triggers an
LTE-to-UMTS SRVCC handover.
2. Upon identifying the proprietary SRVCC-based CS fallback procedure, the CN sends the
RNC a RELOCATION REQUEST message that includes parameter indications
instructing the RNC to prepare CS resources before a CS fallback.
3. Based on the indications, the RNC prepares the required CS resources. The RNC then
performs special operations to ensure that the CS fallback succeeds.
4. After the CS fallback, the UE and CN skip the authentication and encryption procedures
required by the standard CS fallback procedure.
Figure 2-8 illustrates how this feature works.

Figure 2-8 Working principle of CSFB based on SRVCC
Enhancement
None
Dependency
 eNodeB
None
 UE
UEs must support the LTE-to-UMTS SRVCC handover procedure.
 Transport Network
None
 CN
The MME and MSC are provided by Huawei and both support this feature.
 OSS
None
 Other Features
− LOFD-001033 CS Fallback to UTRAN
− WRFD-160271 Ultra-Flash CSFB
 Others
None

2.1.3.3 LOFD-001068 CS Fallback with LAI to UTRAN
Availability
This feature is
Summary
By using new defined LAI IE, the optimized CSFB process of eNodeB can avoid unnecessary
LAU and reduce the CSFB E2E latency
For the LTE-only operators of whom CSFB must rely on the other UMTS operator, the
optimized CSFB process of eNodeB can also avoid the wrong PLMN selecting in such
Multi-PLMN scenario.
Benefits
When LTE to UMTS CS fallback happens, this feature could reduce the possibility of
Location Area Update (LAU) during fallback. So that the CS fallback delay due to
unnecessary LAU is reduced. In Multi-PLMN scenario this feature could avoid CSFB fail due
to the PLMN updating.
Description
In the coexistence scenario of GUL, The operator make MME and 3G MSC combined attach
policy when MME receive the UE's attach request for any GUL/UL terminal because MME
doesn't know the capability of UE; MME also maintains the mapping relation between the TA
and LA, the LA belongs to the attached 3G MSC;
MME sends the LA to eNodeB through the new defined LAI IE of S1AP, eNodeB can select
the proper RAT and neighbor cell with it. Target cell selection is optimized to avoid
unnecessary LAU, which reduced the CSFB E2E latency.
For the LTE-only operators, their CSFB must rely on the other UMTS operators, The
optimized CSFB process of eNodeB can also avoid the wrong PLMN selecting in such
Multi-PLMN scenario and avoid CSFB fail due to the PLMN updating.
Enhancement
None
Dependency
 UE
UE supports R8 or R9 CSFB.
 CN
MME needs to support the LAI IE.
 Other features
LOFD-001033 CS Fallback to UTRAN.

2.1.3.4 LOFD-001088 CS Fallback Steering to UTRAN
Availability
This feature is
Summary
Huawei eNodeB supports CS fallback flexible steering based on the UE state, to select first
target radio access technology (RAT) as UTRAN, target UTRAN frequency priorities, and
different CS fallback mechanism priorities for UE in each state.
Benefits
This feature allows the UE in idle and active state have separate CS fallback strategy. The
strategy allows the UE to select UTRAN as first priority, based on network load of UTRAN to
define UTRAN frequency priority, and select different CS fallback mechanisms for UE in
different state.
Description
CS fallback flexible steering is performed based on UE states, which are idle (supporting CS
only) and active (supporting CS+PS). For each state, CS fall back behavior could be defined
as following:
 Set UTRAN as first priority of RAT at CS fallback.
 Set priorities of UTRAN frequencies, such as different priorities for R99 and HSPA
frequencies.
 Set priorities of CS fallback mechanisms, including PS handover, PS redirection, and
flash CS fallback.
After selecting the target RAT, to use blind CSFB or CSFB with measurement is a common
setting for the cell, which is not separated for UE states.
Enhancement
None
Dependency
 Other features
LOFD-001033 CS Fallback to UTRAN and LOFD-001078 E-UTRAN to UTRAN
CS/PS Steering.
2.1.3.5 LOFD-001052 Flash CS Fallback to UTRAN
Availability
This feature is


Summary
When the RAN Information Management (RIM) procedure is supported by the core network
of LTE as well as that of UTRAN, the RAN of LTE as well as that of UTRAN and the UE,
Flash CS Fallback will be employed to provide a decreased delay on CS access.
Flash CS Fallback is in compliance with 3GPP R9.
Benefits
Flash CS Fallback to UTRAN provides a decrease in CS service access delay to promote user
experience. About 1 second delay could be reduced compare with normal R8 CS Fallback.
Description
RIM procedure is accomplished with the MME and the GSM/UMTS core network nodes to
forward the request in a transparent manner to the target GSM/UMTS cell and the target cell
encapsulating the SI and sending back to LTE cell.
eNodeB can get the system information of the GSM/UMTS neighbor cells with RIM
procedure according to 3GPP R9. This information can be sent to UE during CS Fallback
procedure so that the system information requiring and updating activities can be omitted or
partially omitted and the delay can be reduced for CS Fallback.
Whether an UE supports 3GPP R9 or not, it will benefit from employing the Blind CS
Fallback strategy, when the blind HO neighbor cells have been configured to a LTE cell.
Using the blind HO neighbor cells will definitely decrease the time delay from measurement
and SI access.
Enhancement
The following adaptive blind CS fallback function has been introduced in eRAN6.0.
In a UMTS+LTE (UL) multi-mode base station, two systems use different antennas. The
E-UTRAN cell edge may not be included in the UTRAN cell coverage. If the E-UTRAN
frequency band is lower than the UTRAN frequency band, the E-UTRAN cell coverage is
greater than the UTRAN cell coverage. In this scenario, eRAN6.0 introduces adaptive blind
CS fallback. With this function, an eNodeB performs blind-handover-based CS fallback and
measurement-based CS fallback for cell center users (CCUs) and cell edge users (CEUs),
respectively. This saves the inter-RAT measurement time for CCUs and increases the CS
fallback success rate for CEUs, both reducing the CS fallback delay.
None
Dependency
 UE
Require R9 UE to support RIM procedure.
 CN
R9 compliant CN to support RIM procedure.

 Other features
LOFD-001033 CS Fallback to UTRAN.
 Others
UTRAN also needs to support RIM procedure.
2.1.3.6 LOFD-001034 CS Fallback to GERAN
Availability
This feature is:
Summary
When a UE is in the E-UTRAN and GERAN coverage overlapping area and E-UTRAN
cannot provide CS services, CS Fallback to GERAN can be used to provide CS services for
the UE.
Benefits
When the UE camps on the E-UTRAN that cannot provide CS services, CS Fallback to
GERAN can be used to provide CS services for the UE.
Description
CSFB in EPS enables operators to reuse existing CS infrastructure, thereby providing CS
services for UEs on the E-UTRAN. UEs that access the E-UTRAN and support CSFB can
establish one or more CS services using the GERAN. This feature can be used only when the
E-UTRAN and GERAN overlap.
On single-operator networks, CSFB and IMS-based services can co-exist.
This feature introduces an SGs interface between the MME and MSC server, as shown in the
following figure:
Figure 2-9 Network architecture of CSFB to GERAN

The MGW is not displayed in the preceding figure because CSFB in the EPS does not affect
the user plane.
Enhancement
None
Dependency
 UE
The UE must support CSFB.
 Other features
UTRAN.
2.1.3.7 LOFD-001053 Flash CS Fallback to GERAN
Availability
This feature is
Summary
When the RAN Information Management (RIM) procedure is supported by the core network
of LTE as well as that of GERAN, the RAN of LTE as well as that of GERAN and the UE,
Flash CS Fallback will be employed to provide a decreased delay on CS access.
Flash CS Fallback is in compliance with 3GPP R9.
Benefits
Flash CS Fallback to GERAN provides a decrease in CS service access delay to promote user
experience. About 2 seconds delay could be reduced compare with normal R8 CS Fallback.
Description
RIM procedure is accomplished with the MME and the GSM/UMTS core network nodes to
forward the request in a transparent manner to the target GSM/UMTS cell and the target cell
encapsulating the SI and sending back to LTE cell.
eNodeB can get the system information of the GSM/UMTS neighbor cells with RIM
procedure according to 3GPP R9. This information can be sent to UE during CS Fallback
procedure so that the system information requiring and updating activities can be omitted or
partially omitted and the delay can be reduced for CS Fallback.
Whether an UE supports 3GPP R9 or not, it will benefit from employing the Blind CS
Fallback strategy, when the blind HO neighbor cells have been configured to a LTE cell.
Using the blind HO neighbor cells will definitely decrease the time delay from measurement
and SI access.

Enhancement
The following adaptive blind CS fallback function has been introduced in eRAN6.0.
In a GSM+LTE (GL) multi-mode base station, two systems use different antennas. The
E-UTRAN cell edge may not be included in the GERAN cell coverage. If the E-UTRAN
frequency band is lower than the GERAN frequency band, the E-UTRAN cell coverage is
greater than the GERAN cell coverage. In this scenario, eRAN6.0 introduces adaptive blind
CS fallback. With this function, an eNodeB performs blind-handover-based CS fallback and
measurement-based CS fallback for cell center users (CCUs) and cell edge users (CEUs),
respectively. This saves the inter-RAT measurement time for CCUs and increases the CS
fallback success rate for CEUs, both reducing the CS fallback delay.
None
Dependency
 UE
Require R9 UE to support RIM procedure.
 CN
R9 compliant CN to support RIM procedure.
 Other features
This feature depends on LOFD-001034 CS Fallback to GERAN.
 Others
GERAN also needs to support RIM procedure.
2.1.3.8 LOFD-081283 Ultra-Flash CSFB to GERAN
Availability
This feature is
 applicable to Macro from eRAN8.1.
 applicable to Micro from eRAN8.1.
 applicable to LampSite from eRAN8.1.
Summary
When a UE initiates a voice service request in a VoIP-incapable E-UTRAN cell within the
overlapping area between the E-UTRAN and a GERAN, this feature triggers a single radio
voice call continuity (SRVCC) procedure to have circuit switched (CS) resources prepared in
the GERAN.
Benefits
This feature decreases the CS fallback (CSFB) delay by about 1.5s and improves user
experience.
Description
The following figure shows the procedure for ultra-flash CSFB to GERAN.

Figure 2-10 Procedure for ultra-flash CSFB to GERAN
When the core network identifies the Huawei proprietary SRVCC procedure for CSFB, it
sends the BSC a handover request message that contains CS-related parameters. As instructed
by the message, the BSC prepares CS resources.
Compared with standard CSFB procedures, this CSFB procedure does not require
authentication, ciphering, or CS bearer setup after the UE is handed over to the GERAN. As a
result, the CSFB delay decreases.
Enhancement
None
Dependency
 eNodeB
None
 UE
UEs must support SRVCC from E-UTRAN to GERAN.
None
 Core network
MMEs and MSCs must be Huawei equipment and support ultra-flash CSFB.
 OSS
None

 Other features
This feature requires the feature LOFD-001034 CS Fallback to GERAN.
 Others
None
2.1.3.9 LOFD-001069 CS Fallback with LAI to GERAN
Availability
This feature is
Summary
By new defined LAI IE, eNodeB can solve the difference of target RAT selecting between
eNodeB and MME , also can solve the difference of target cell selecting due to the
discrepancy between the TA and LA; The optimized CSFB process of eNodeB can avoid
unnecessary LAU and reduce the CSFB E2E latency;
For the LTE-only operator of whom CSFB must rely on the other 2G operator, the optimized
CSFB process of eNodeB can also avoid the wrong PLMN selecting in such Multi-PLMN
scenario.
Benefits
When LTE to GSM CS fallback happens, this feature could reduce the possibility of Location
Area Update (LAU) during fallback. So that the CS fallback delay due to unnecessary LAU is
reduced. In Multi-PLMN scenario this feature could avoid CSFB fail due to the PLMN
updating.
Description
In the coexistence scenario of GUL, The operator make MME and 2G MSC combined attach
policy when MME receive the UE's attach request for any GUL/GL terminal because MME
doesn't know the capability of UE; MME also maintains the mapping relation between the TA
and LA, the LA belongs to the attached 2G MSC;
MME sends the LA to eNodeB though the new defined LAI IE of S1AP, when eNodeB
receives the CSFB and LAI indication, eNodeB can select the proper RAT and neighbor cell.
The optimized CSFB process of eNodeB can avoid unnecessary LAU and reduce the CSFB
E2E latency
For the LTE-only operators of whom CSFB must rely on the other 2G operator, the optimized
CSFB process of eNodeB can also avoid the wrong PLMN selecting in such Multi-PLMN
scenario and avoid CSFB fail due to the PLMN updating.
Enhancement
None

Dependency
 UE
UE supports R8 or R9 CSFB.
 CN
MME needs to support the LAI IE.
 Other features
LOFD-001034 CS Fallback to GERAN.
2.1.3.10 LOFD-001089 CS Fallback Steering to GERAN
Availability
This feature is
Summary
Huawei eNodeB supports CS fallback flexible steering based on the UE state, to select first
target radio access technology (RAT) as GERAN, and different CS fallback mechanism
priorities for UE in each state.
Benefits
This feature allows the UE in idle and active state have separate CS fallback strategy. The
strategy allows the UE to select GERAN as first priority, and select different CS fallback
mechanisms for UE in different state.
Description
CS fallback flexible steering is performed based on UE states, which are idle (supporting CS
only) and active (supporting CS+PS). For each state, CS fall back behavior could be defined
as following:
 Set GERAN as first priority of RAT at CS fallback.
 Set priorities of CS fallback mechanisms, including PS handover, PS redirection, cell
change order/network assisted cell change (CCO/NACC), and flash CS fallback.
After selecting the target RAT, to use blind CSFB or CSFB with measurement is a common
setting for the cell, which is not separated for UE states.
Enhancement
None
Dependency
 Other features
LOFD-001034 CS Fallback to GERAN.

2.1.3.11 LOFD-001035 CS Fallback to CDMA2000 1xRTT
Availability
This feature is
Summary
When an E-UTRAN UE initiates a circuit switched (CS) service in the overlapping area of the
E-UTRAN and a CDMA2000 1xRTT network, the UE can be transferred to the CDMA2000
1xRTT network using CS fallback. .
Benefits
We can use CS fallback to CDMA2000 1xRTT to provide CS-domain service for the UE
which is camped in the E-UTRAN that cannot provide any CS-domain service for the UE.
Description
The CS fallback in EPS enables the provisioning of CS-domain services by reuse of CS
infrastructure when the UE is served by E-UTRAN. A CS fallback enabled terminal,
connected to E-UTRAN may use CDMA2000 1xRTT to establish one or more CS-domain
services. This function is only available in case E-UTRAN coverage is overlapped by
CDMA2000 1xRTT coverage.
CS fallback and IMS-based services shall be able to co-exist in the same operator's network.
The CS fallback in EPS function is realized by using the S102 interface mechanism between
the 1x CS IWS (1xCS Interworking Solution) and the MME. S102 interface provides a tunnel
between the MME and the 1xCS IWS to relay 3GPP2 1xCS signaling messages.

Figure 2-11 CS fallback in EPS architecture
MGW is not shown in the figure since the CS fallback in EPS does not have any impacts to
the U-plane handling.
Enhancement
None
Dependency
 UE
UE needs to support CSFB.
2.1.3.12 LOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT
Availability
This feature is
Summary
If an operator has both a CDMA2000 1xRTT network and an E-UTRAN, UEs in the
overlapping area of these two networks preferentially camp in the E-UTRAN. However, the
operator often prefers that the CDMA2000 1xRTT network and E-UTRAN provide circuit
switched (CS) and packet switched (PS) services for UEs, respectively. To meet such
expectations, enhanced CS fallback has been designed to ensure that UEs are handed over to
the CDMA2000 1xRTT network when initiating CS services in the overlapping area.

Benefits
With enhanced CS fallback, UEs can be quickly transferred from the E-UTRAN to the
CDMA2000 1xRTT network to initiate or receive CS services. This quick transfer improves
user experience. For example, when a UE is transferred to the CDMA2000 1xRTT network to
receive a CS service, the enhanced CS fallback procedure takes only 2 to 3 seconds, which is
obviously faster than 4 to 5 seconds required by the normal CS fallback procedure.
Description
Enhanced CS fallback in the evolved packet system (EPS) enables the provisioning of CS
services for UEs in the E-UTRAN by reusing legacy CS infrastructures. After enhanced CS
fallback to CDMA2000 1xRTT, a UE can establish one or more CS services. This function is
only available when CDMA2000 1xRTT coverage overlaps with E-UTRAN coverage.
Enhanced CS fallback and IMS-based services are able to coexist in the same operator's
network.
Enhanced CS fallback in the EPS is implemented using the S102 interface between the 1xCS
IWS and the mobility management entity (MME). The S102 interface provides a tunnel
between the MME and the 1xCS IWS to relay 3GPP2 1xCS signaling messages. 1xCS IWS is
short for Circuit Switched Fallback Interworking Solution Function for 3GPP2 1xCS.
Figure 2-12 CS fallback in the EPS architecture
S-GW: serving gateway P-GW: PDN gateway

Note: The media gateway (MGW) is not shown in the figure because CS fallback in the EPS
has no impact on user-plane processing
During an enhanced CS fallback procedure, the eNodeB hands over the UE to the target
CDMA2000 1xRTT network to perform CS services. If the UE is performing PS services in
the E-UTRAN, the eNodeB redirects the ongoing PS services to the evolved high rate packet
data (eHRPD) network.

Enhancement
None
Dependency
 eNodeB
GPS hardware required if IEEE1588v2 is not used to provide time(phase) sync.
 UE
UE must support CS fallback and enhanced CS fallback.
 CN
The MME must support CS fallback and enhanced CS fallback.
 Other features
LOFD-001035 CS Fallback to CDMA2000 1xRTT.
If enhanced CS fallback is enabled, the eNodeB includes the CDMA2000 system time in
the system information broadcast. The accuracy of the CDMA2000 system time must be
the same as that of the CDMA2000 1xRTT network, with a positive or negative
difference that is recommended to be less than 3 µs but must be less than 10 µs.
Therefore, this feature requires the feature LOFD-00301302 IEEE1588 V2 Clock
Synchronization for time synchronization or the feature LBFD-00300503
Synchronization with GPS.
The concurrent non-optimized PS handover during an eCSFB procedure depends on
feature LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000.
 Others
The CDMA2000 1xRTT network must support CS fallback and enhanced CS fallback.
Network elements (NEs) on the network include the 1xCS IWS, CBSC, and CBTS.
2.1.3.13 LOFD-001091 CS Fallback to CDMA2000 1xRTT Based on

Frequency-specific Factors
Availability
This feature is
Summary
Using this feature, the eNodeB can transfer E-UTRAN UEs to an operator's CDMA2000
1xRTT frequencies (in one or multiple band classes), based on the specified factors for the
frequencies during circuit switched fallback (CSFB).
Benefits
The factors specified for CDMA2000 1xRTT frequencies are used to balance the loads on
these frequencies during CSFB.

Description
An operator owning multiple CDMA2000 1xRTT frequencies can set a CSFB factor for each
CDMA2000 1xRTT frequency. Based on these factors, the eNodeB determines the following:
 During CSFB, the eNodeB determines the target CDMA2000 1xRTT band class for
redirection.
 During enhanced CSFB (eCSFB), the eNodeB determines which CDMA2000 1xRTT
frequency to measure. Based on these measurement results, the eNodeB transfers the
UEs.
The operator can specify the CSFB factors for CDMA2000 1xRTT frequencies, based on their
respective loads. For example, an operator has two CDMA2000 1xRTT bands: 800 MHz and
2.1 GHz. Generally, frequencies in the 800 MHz band are more heavily loaded than those in
the 2.1 GHz band. To balance the loads between the two bands, the operator sets the factors
for frequencies in the 800 MHz band to smaller values than those for frequencies in the 2.1
GHz band.
The following figure illustrates another example. In this situation, CDMA2000 1xRTT
frequencies 1, 2, and 3 are assigned factors 0.7, 1, and 1, respectively. Then the number of
UEs that fall back to frequencies 1, 2, and 3 will meet the following condition:
Number of UEs on frequency 1:Number of UEs on frequency 2:Number of UEs on frequency
3 = 0.7:1:1
Figure 2-13 CSFB based on factors for CDMA2000 1xRTT frequencies
Enhancement
None
Dependency
 Other features

LOFD-001035 CS Fallback to CDMA2000 1xRTT or LOFD-001090 Enhanced CS

Fallback to CDMA2000 1xRTT.
2.1.4 LCS
Overview
The location service (LCS) is a technology that can be used to determine the geographic
location and velocity of user equipment (UE) by measuring radio signals.
The LCS package uses positioning technologies of LTE cellular networks to determine the
positions of target UEs through signaling interaction between network elements. Using this
solution, network operators can provide location-related services for third parities, such as
data centers, monitoring agencies, and emergency location centers.
Applications
The LCS package includes only one feature: LOFD-001047 LoCation Services (LCS). It can
be used to provide public security, mobile yellow page, and individual security services and
also optimize mobile network design. For details about the applications, see LOFD-001047
LoCation Services (LCS) feature description.
Value
The LCS package includes only one feature: LOFD-001047 LoCation Services (LCS). For the
value of this feature package, see LOFD-001047 LoCation Services (LCS) feature
description.
2.1.4.1 LOFD-001047 LoCation Services (LCS)
Availability
Summary
LoCation Services (LCS) provide methods to physically locate UEs by measuring radio
signals.
Benefits
LCS can be used to obtain UE location data including longitude, latitude, or velocity. This
location data can be used for value-added services, such as navigation or positioning requests
initiated by emergency calls or lawful interception. For example, during the E911 service, the
emergency center can locate the call originator and take proper rescue measures.
Description
LCS enables UE positioning based on radio signal measurement. It requires coordination of
the evolved serving mobile location center (E-SMLC). The E-SMLC can be deployed as an
independent NE in the evolved packet core (EPC) of an LTE network, or embedded into the
MME.
LCS supports positioning based on:

 Cell ID (low positioning accuracy, depending on the radio network density)

 Observed Time Difference of Arrival (OTDOA) (medium positioning accuracy)
 Assisted GPS (A-GPS) (high positioning accuracy)
Positioning is implemented by the E-SMLC and UE. The eNodeB transparently transfers
messages and measurement information between them. The overall process for positioning is
as follows:
1. The MME receives a request for UE positioning or initiates a positioning procedure.
2. The MME sends the positioning request to the E-SMLC.
3. The E-SMLC sends assistance data to the UE and checks the related measurement
information provided by the UE/eNodeB. E-SMLC calculates the location data of the UE
and sends the data to the MME.
If the positioning procedure is initiated by an NE other than the MME, the MME sends the
location data to this NE.
Enhancement
 eRAN11.1
Inter-frequency measurement for OTDOA-based positioning has been added to
eRAN11.1. The eNodeB allocates gaps for the measurement of inter-frequency reference
signal time difference (RSTD) and specifies more positioning reference signals (PRSs)
of neighboring cells for measurement. This measurement improves the success rate and
accuracy of OTDOA-based positioning in multi-frequency non-continuous coverage
scenarios. If a UE that does not support inter-frequency measurement for OTDOA-based
positioning originates an emergency call, the eNodeB can trigger service-based handover,
to hand over the UE to a preset frequency so that the UE can perform intra-frequency
measurements for OTDOA-based positioning. (This is a trial function in eRAN11.1.)
Since eRAN11.1, PRS parameters are configurable, including the signal bandwidth,
transmit periodicity, and number of consecutive downlink subframes used for PRS
transmission.
Applicability
Yes Yes Yes
Dependency
 eNodeB
The LBBPc does not support PRS parameter configuration.
 eCoordinator
None
 UE
UEs must support A-GPS- and OTDOA-based positioning.
 Core network
The MME must be PS9.2 or a later version.
This feature requires support from the E-SMLC.

 Other NEs
None
 Other features
OTDOA-based positioning requires synchronization with the GPS clock.
Uplink E-CID-based positioning requires smart antennas.
Used with LBFD-00201805 Service Based Inter-frequency Handover, OTDOA-based
positioning has a good performance in emergency call scenarios.
 Others
None
2.1.5 eMBMS
Overview
Legacy radio access networks (RANs) provide point-to-point (PTP) unicast bearer services,
for example, file downloading and streaming services. Unicast bearer services do not share
radio and transport resources on RANs even if people are downloading the same files or video
clips. Therefore, congestions occur when large gatherings create hotspots, affecting user
experience.
The evolved multimedia broadcast/multicast service (eMBMS) provides point-to-multipoint
(PTM) transmission. Data is broadcast through Multimedia Broadcast multicast service Single
Frequency Network (MBSFN) subframe transmission over the radio interface to all UEs in
broadcast coverage areas. In this way, largely demanded contents can be transmitted in a
cost-effective way, such as for live broadcast of major matches and hot events, mobile TV
program transmission, and big file pushing.
The current eMBMS solution includes only one feature package.
The current eMBMS feature package consists of the following features:
 eMBMS phase 1 based on centralized MCE architecture
This is the basic eMBMS feature, which uses the 3GPP-defined centralized MCE
architecture to create channels for multimedia broadcast and multicast service
transmission in the E-UTRAN. eMBMS sessions can be started, stopped, or updated
under the control of the evolved packet core (EPC). In an MBSFN area, eMBMS session
data can be jointly transmitted by multiple cells and synchronized between eNodeBs.
 eMBMS service continuity
This feature is used to deploy eMBMS services in multi-carrier scenarios. The eNodeB
uses the new system information message SIB15 to help RRC_IDLE and
RRC_CONNECTED UEs determine the carrier for reception of desired eMBMS
services after UEs inform the eNodeB of their desired services.
Applications
The eMBMS feature package can be used when gathering UEs have a large demand for
services. The following table describes the applications of this feature package.
Appli Feature Description

cation
Gatheri LOFD-070220 This feature is applicable to hotspots with large gatherings


cation
ng eMBMS Phase 1 such as sporting venues or concerts that tend to create
hotspot based on intense demand for a single type of service. It provides
s Centralized MCE channels for point-to-multipoint (P2MP) transmission of
Architecture multimedia broadcast and multicast services, and enables
joint transmission by multiple cells in an MBSFN area as
well as session data synchronization between eNodeBs.
The service data is carried by shared radio interface
channels. Therefore, the service quality is not affected by
the increased number of users, and the number of service
users is not restricted.
Busine LOFD-070220 At business hotspots, such as shopping malls or
ss eMBMS Phase 1 supermarkets, operators may provide advertising and
hotspot based on promotional information broadcasts for cooperative
s Centralized MCE business. The eMBMS feature can be used to enable
Architecture shared channels for advertising and other information
broadcast. Only a fixed amount of radio interface
resources are needed to send such information to all the
UEs in an area, saving resources and improving network
efficiency.
Public LOFD-070220 Governments may need to broadcast disaster warning,
broadc eMBMS Phase 1 weather information, and important events to specific
asting based on areas. When the eMBMS feature is enabled, P2MP
from Centralized MCE broadcast channels quickly and efficiently transmit such
govern Architecture information to all the targeted UEs using a limited amount
ments of radio interface resources. If the legacy unicast services
are used, the same information must be repetitively sent to
each UE, requiring a long time and also a large amount of
resources.
Value
The eMBMS feature package has the following benefits:
 MBSFN transmission enables a UE to combine the MBSFN signals received from
multiple cells as multipath signals from a single cell, thereby mitigating inter-cell
interference and achieving combining gains.
 eMBMS services are broadcast using semi-static configurations of radio interface
resources. Resource use is not prolonged with the increase in the number of MBMS
service users. Therefore, there is no limit on the number of UEs that can receive eMBMS
services.
Both RRC_IDLE and RRC_CONNECTED UEs can receive eMBMS services. There is no limit on the
number of RRC_IDLE UEs that receive eMBMS services. However, the maximum number of
RRC_CONNECTED UEs that receive eMBMS services is subject to the cell capacity expressed in
terms of the number of UEs.
 Broadcast allows resource sharing for in-demand services. It reduces the requirement for
radio interface resources and lowers the risk of network congestion.

MBSFN combination gains of 3 dB to 10 dB can be obtained when more than three cells
comprise an MBSFN area in which cell edge UEs (RSRP ≥-100 dBm and CRS SINR ≥ -3 dB)
can receive signals. (The MBSFN combination gain is the increase in the SINR brought by
broadcast transmission compared with unicast transmission.)
MBSFN combination gains depend on the inter-eNodeB distance. A shorter inter-eNodeB
distance brings more MBSFN combination gains.
2.1.5.1 LOFD-070220 eMBMS Phase 1 based on Centralized MCE

Architecture
Availability
Summary
Huawei eMBMS phase 1 supports transmission of multimedia broadcast multicast service
(MBMS) based on the centralized multi-cell/multicast coordination entity (MCE) architecture,
defined in 3GPP Release 9. This feature provides a platform for multimedia broadcast
services.
Benefits
When operators provide unicast services and there is a large demand for services (for example,
a live broadcast of a football match) on an LTE network, eMBMS offers the following
benefits:
 The UE combines the MBSFN signals received from multiple cells as multipath signals
from a single cell, thereby mitigating inter-cell interference and producing signal
combining gains.
 A stable and bandwidth-guaranteed broadcast offers a satisfactory service experience.
There is no limit on the number of UEs that can receive MBMS services, because
MBMS services are broadcast using semi-static radio resource configurations and the
number of UEs served is not relevant to the amount of allocated resources.
Both RRC_IDLE and RRC_CONNECTED UEs can receive MBMS services, and there is no limit on
the number of RRC_IDLE UEs that can receive MBMS services. However, the maximum number of
RRC_CONNECTED UEs that can receive MBMS services is subject to the cell capacity expressed in a
number of UEs.
 Broadcast allows resource sharing for in-demand services. It reduces requirements for
unicast bearer resources and reduces the risk of network congestion. In addition, it
improves user experience with existing unicast services in a heavily loaded or congested
network.
 eMBMS reduces the need for investment in equipment needed to expand capacity. It
allows operators to develop new value-added services, such as high-definition video, to
increase revenue.
Description
eMBMS-supporting LTE network architecture introduces three new network elements
(NEs)not present in the standard LTE-SAE architecture for unicast services:
 Broadcast multicast service center (BM-SC)

The BM-SC supports service announcement, security management, session management,

transmission proxy, and data synchronization.
 eMBMS gateway (MBMS GW)
The MBMS GW uses IP multicast to forward MBMS user-plane data to eNodeBs over
the M1 interface and transfers MBMS session control messages to MMEs. The MBMS
GW can be co-located with the P-GW.
 MCE
The MCE provides control-plane functions, such as admission control on MBMS
sessions, and time-frequency resource allocation for Multimedia Broadcast multicast
service Single Frequency Network (MBSFN) transmission by all eNodeBs in a single
MBSFN area.
In Huawei eMBMS phase 1, the centralized MCE architecture is used. The MCE is deployed
as a standalone physical entity. The ECO6910, rather than the eNodeB, provides the MCE
functionality. Figure 2-14 shows the network architecture for Huawei eMBMS phase 1.
Figure 2-14 Network architecture for Huawei eMBMS
In eRAN7.0, the frequency bands and bandwidths supported by Huawei eMBMS phase 1 are
as follows:
 Frequency bands: 800 MHz, 1800 MHz, and 2.6 GHz
 Bandwidths: 5 MHz, 10 MHz, 15 MHz, and 20 MHz
Enhancement
 eRAN8.1
Since eRAN8.1, Huawei eMBMS has supported overlapping MBSFN areas. A single cell
can belong to up to three MBSFN areas. The support for MBSFN area overlapping
enables more flexible deployment of eMBMS services, especially when some services
must be transmitted over a wide area and some other services only at hotspot locations.
For MBSFN area overlaps, Huawei eMBMS supports the following subfunctions:
− Configuring the mapping between a single cell and multiple MBSFN areas on the
MCE
− Allocating MBSFN subframes in a centralized mode in overlapping MBSFN areas

At the startup of an MBMS session, the MCE chooses the MBSFN area where the
session is to be delivered. If overlapping MBSFN areas exist in the target region for
session delivery, the MCE chooses the largest MBSFN area that meets the MBMS
service area requirement of the session, and then performs centralized allocation of
MBSFN subframes for cells in the chosen MBSFN area.
The LBBPc and LMPT boards support this feature.
Since eRAN8.1, eNodeBs have been able to broadcast MBMS sessions in different
MBSFN areas at the same time. The application scenarios are as follows:
− RRUs are installed remotely and a single MBSFN area is not able to include all the
cells served by remote RRUs or include both cells served by remote RRUs and cells
served by local RF units.
− The eNodeB operates on multiple frequency bands, and eMBMS is required for
more than one of the bands.
The eNodeB also supports cell-specific PMCH transmit power configuration from
eRAN8.1. If the transmit power of a cell does not reach the licensed value and the
transmit power of an RRU serving the cell does not reach the maximum, you can set the
cell-specific PMCH power offset to increase the PMCH transmit power. Then, an MCS
of a larger index can be used for the MBSFN area that the cell belongs to, so that the
eMBMS service capacity can be improved.
 eRAN11.1
eMBMS is enhanced since eRAN11.1:
− eMBMS can be implemented in RAN sharing scenarios. In scenarios of RAN
sharing with common carriers, RAN sharing with dedicated carriers, or hybrid RAN
sharing, different operators can provide their own eMBMS services in the shared
E-UTRAN.
In the case of multi-operator core network (MOCN), eNodeBs and MCEs are
shared by operators. An MCE connects to different operators' MMEs through
dedicated M3 interfaces. In this way, operators can use their own MMEs to start,
stop, or update their specific eMBMS sessions through the dedicated M3 interfaces.
For a specific eMBMS session of a given operator, an eNodeB will set up a
dedicated M1 interface with the MBMS GW deployed by this operator to transmit
user-plane data of the session.
If the gateway core network (GWCN), eNodeBs, MCEs, and MMEs are shared by
operators. MBMS GWs can be shared or exclusively used by operators. MCEs
communicate with MMEs through the same M3 interface. If operators exclusively
use their own MBMS GWs, an eNodeB sets up a dedicated M1 interface with each
MBMS GW.
− The coordination between the further enhanced inter-cell interference coordination
(FeICIC) and eMBMS features is supported.
FeICIC requires allocation of almost-blank subframes (ABSs), and eMBMS
requires MBSFN subframes. If both of the features are enabled, subframe allocation
must be coordinated, and MBSFN subframes are allocated preferentially to avoid
subframe allocation conflicts.
− eMBMS can be deployed on Supplemental DownLink (SDL) carriers.
SDL carriers are asymmetric carriers that implement downlink transmission only,
for instance, the carriers working on band 29. Since SDL carriers do not perform
uplink transmission, UEs cannot camp on them and can use them only as secondary
carriers for carrier aggregation (CA).
An operator with SDL carriers available can deploy eMBMS only on SDL carriers
or on both SDL and common carriers. If only SDL carriers are used to transmit

eMBMS services, all the subframes on primary carriers are reserved for unicast
services. In this way, sufficient resources can be ensured for eMBMS, and resources
for unicast services are not reduced for CA-incapable UEs.
This is a trial function in eRAN11.1.
− Session preemption based on the ARP is supported.
ARP-based eMBMS session preemption is introduced in 3GPP Release 10. When
MBSFN subframes are insufficient, higher-ARP sessions can preempt MBSFN
subframes used for lower-ARP sessions to ensure successful establishment of
higher-ARP sessions. For example, higher-ARP sessions possibly must be
established upon emergencies to send emergency notifications. This function
enables preemption of only MBSFN subframe. Unicast service resources are not
preempted.
To provide this function, ARP is added to the QoS parameters for eMBMS sessions.
If the available MBSFN subframes are insufficient for a newly initiated eMBMS
session that has a high ARP, MBSFN subframes used to transmit a lower-ARP
session can be preempted to ensure successful initiation of the new session. In this
case, the lower-ARP session is paused and then resumed when the new session
terminates.
Applicability
Yes Yes Yes
Dependency
 eNodeB
None
 eCoordinator
The eCoordinator must be deployed to provide the MCE functionality.
 Core network
This feature requires the support from EPC NEs, including the BM-SC, MBMS-GW and
MBMS-supporting MMEs.
 UE
This feature requires support from UEs. UEs must comply with 3GPP Release 9 or later.
If eMBMS is deployed on an SDL carrier, UEs must comply with 3GPP Release 11 or
later and be capable of receive eMBMS services in secondary cells or non-serving cells.
 Other NEs
The M1, M2, and M3 interfaces must be configured for this feature.
 Other features
This feature requires LBFD-00300503 Synchronization with GPS, LOFD-00301302
IEEE1588 V2 Clock Synchronization, or LOFD-080216 Uu based Soft Synchronization.
 Others
This feature requires time synchronization with the accuracy of ±1.5 μs.

2.1.5.1.1 LOFD-07022001 Multi-cell transmission in MBSFN area
Availability
This feature is
Summary
This feature enables the multi-cell/multicast coordination entity (MCE) to allocate the same
radio resources to all cells within a multimedia broadcast multicast service single frequency
network (MBSFN) area and also enables the cells to use the same time-frequency resources to
transmit the same multimedia broadcast multicast service (MBMS) sessions.
Benefits
This feature ensures synchronization of radio resources configurations between the cells
within an MBSFN area and the continuous coverage of evolved MBMS (eMBMS) services
within the MBSFN area, reducing interference between the cells within the MBSFN area.
Description
All cells within an MBSFN area use the same radio resources and modulation and coding
scheme (MCS) to transmit the same MBMS sessions. If MBMS user data is synchronized, the
MCE sends MBMS Scheduling Information messages to eNodeBs to ensure synchronization
of MBSFN subframes allocated to the cells, increasing eMBMS gains.
Enhancement
None
Dependency
The dependency of this feature is the same as that of LOFD-070220 eMBMS Phase 1 based
on Centralized MCE Architecture.
2.1.5.1.2 LOFD-07022002 Mixed transmission of unicast and broadcast
Availability
This feature is
Summary
This feature supports mixed transmission of broadcast and unicast services in cells based on
time division multiplexing.

Benefits
This feature maximizes radio resource usage in cells within a multimedia broadcast multicast
service single frequency network (MBSFN) area based on the dynamic MBSFN subframe
allocation. MBSFN subframes can be dynamically allocated based on the multimedia
broadcast multicast service (MBMS) session requirements.
Description
Broadcast and unicast services can be transmitted in the same radio frame based on time
division multiplexing. As shown in the following figure, MBSFN subframes transmit
broadcast services and normal subframes transmit unicast services.
In an LTE FDD system, a maximum of six subframes in one radio frame can be configured as
MBSFN subframes for eMBMS. In an LTE TDD system, if uplink-downlink subframe
configuration 5 is used, a maximum of five subframes in one radio frame can be configured as
MBSFN subframes for eMBMS. In Huawei eMBMS solution, MBSFN subframes are
dynamically configured to meet MBMS session requirements. As a result, a radio frame
consists of both MBSFN subframes and normal subframes.
Enhancement
None
Dependency
None.
2.1.5.1.3 LOFD-07022003 Data synchronization
Availability
This feature is

Summary
Multimedia broadcast multicast service (MBMS) user data is synchronized in compliance
with the SYNC protocol.
Benefits
This feature complies with 3GPP specifications and is fundamental to eMBMS.
Description
MBSFN transmission from multiple cells requires not only frequency and phase
synchronization but also MBMS user data synchronization between the cells. Data
synchronization is stipulated in the SYNC protocol. For details, see 3GPP TS 25.446.
The following figure shows the position of the SYNC protocol.
A SYNC protocol data unit (PDU) consists of different fields, depending on the PDU type.
Among the fields, the timestamp and packet number are included in SYNC PDUs of all types.
The timestamp helps ensure that cells in MBSFN transmission send the same MBMS session
at the same time. The packet number is used to detect packet loss, check the packet sequence,
and rearrange SYNC PDUs if the received PDUs are out of sequence. Huawei eMBMS
solution supports SYNC PDUs of types 0, 1 and 3.
Data synchronization requires that the eNodeB and broadcast multicast service center
(BM-SC) be configured with the same synchronization period, synchronization start time, and
synchronization end time. The synchronization period is an integer multiple of 1024 radio
frames and must be less than 10 minutes. In the eNodeB, the integer multiple of 1024 radio
frames is specified by the eNodeB-level parameter SyncPeriod in the MBMSPara MO. This
parameter is set to 58 by default, which represents a synchronization period of 593920 ms.
Enhancement
None
Dependency
The dependency of this feature is the same as that of LOFD-070220 eMBMS Phase 1 based
on Centralized MCE Architecture.

2.1.5.1.4 LOFD-07022004 Session admission control
Availability
This feature is
Summary
The multi-cell/multicast coordination entity (MCE) performs admission control on
multimedia broadcast multicast service (MBMS) sessions initiated by the MME.
Benefits
This feature protects the network against congestion or even collapse caused by excessive
eMBMS sessions while maximizing the radio resource usage for eMBMS services and
maintaining the optimum quality of service (QoS) satisfaction rate of eMBMS services.
Description
Cells within a multimedia broadcast multicast service single frequency network (MBSFN)
area are configured with the same radio resources, and the MCE performs admission control
on MBMS sessions in the cells.
The MME initiates an MBMS session by sending an MBMS Session Start Request message
to the MCE that controls the eNodeBs in the targeted MBMS service area. The message
contains information elements (IEs) MBMS Service Area and MBMS E-RAB QoS
parameters. The MCE performs admission control the MBMS session based on the IEs.
If the available MBSFN subframes are insufficient for the MBMS session in all MBSFN areas
under the MBMS service area, the MCE rejects the MBMS session request.
If the available MBSFN subframes in one MBSFN area supports the MBMS session, the
MCE accepts the MBMS session request. However, only the available MBSFN subframes in
this MBSFN area are used to transmit the MBMS session. The MBSFN subframes in the
other MBSFN areas are used to transmit the MBMS session only when the MBSFN
subframes in these MBSFN areas are sufficient for the MBMS session transmission.
Enhancement
None
Dependency
None
2.1.5.2 LOFD-080215 eMBMS Service Continuity
Availability
This feature is


Summary
This feature is an enhancement to the evolved multimedia broadcast/multicast service
(eMBMS) feature for service continuity according to 3GPP Release 11. When this feature is
activated, UEs can identify MBMS services transmitted at different frequencies in an
inter-frequency networking scenario. Based on the information provided by a UE about the
MBMS service that the UE is interested in, the network formulates an appropriate frequency
camping policy for the UE. Based on this policy, the UE can switch to the right frequency for
reception of the desired MBMS service.
Benefits
This feature improves user experience with MBMS services.
Description
The serving cell of a UE broadcasts all the E-UTRA absolute radio frequency channel
numbers (EARFCNs) and MBMS service area IDs (SAIs) used on the current network. After
receiving the information, a UE identifies the target frequency used to transmit the MBMS
service that the UE is interested in. If in idle mode, the UE directly switches to the target
frequency by cell reselection to receive the desired MBMS service. If in connected mode, the
UE informs the serving eNodeB about the target frequency at which its desired MBMS
service is transmitted, and the eNodeB determines whether to immediately hand over the UE
to the target frequency.
Enhancement
None
Dependency
 UE
UEs must comply with 3GPP Release 11.
 Other features
LOFD-080215 eMBMS Service Continuity requires LOFD-070220 eMBMS Phase 1
based on Centralized MCE Architecture.
2.1.6 Video Service Optimization

Overview
Video services are important services in an LTE network and the proportion of traffic at any
given site that is made up of video services keeps increasing. There are multiple aspects of the
video experience that can be optimized, such as the initial acceleration, the video service rate
adaption, coverage improvement, and TCP optimization.
 Initial acceleration: Initial acceleration improves video experience by shortening the
initial buffering delay. The initial buffering delay is the delay between when the playback

button is clicked and when video playback starts. It is an important indicator for
evaluating video experience.
 Video service rate adaption: During playback, the download rate must be higher than the
rate required by the video playback. Video service rate adaption ensures the video
playback rates and prevents video pauses.
 Coverage improvement: Video experience deteriorates at the cell edge, where the
coverage tends to be poor. The coverage improvement solution improves video
experience at the cell edge.
 TCP optimization: This is a general optimization function for Transmission Control
Protocol (TCP) services that improving video experience optimizing processing at the
TCP layer to increase service rates.
Applications
The video experience optimization feature package improves user experience and coverage.
The following table lists the features and their applications.

cation
User LOFD-110221 A TCP proxy is used during the initial phase of TCP
experi Initial connection setup. When the eNodeB receives TCP packets
ence Acceleration over the S1 interface, it sends a TCP ACK to the server,
impro reducing the round trip time (RTT), and accelerating the TCP
vemen slow startup and the transmission rate during the initial phase
t of TCP connection establishment. The initial video buffering
delay is shortened and user experience is improved.
This feature raises the scheduling priority for UEs that access
a specific DNS server or IP address, reducing service setup
delay and ensuring service rates for these UEs.
LOFD-081203 A service guaranteed bit rate (SGBR) is configured for video
Video Service services and if the data rate for video services is lower than
Rate Adaption the SGBR, the scheduling priority of these video services is
raised to prevent video pauses. As long as the data rate is
higher than or equal to the SGBR, the scheduling priority
remains unchanged.
When video load is imbalanced among multiple carriers, UEs
can be handed over from cells with high video load to those
with light video load, balancing the load between different
frequencies and preventing congestion in certain cells.
There are two ways to identify specific services:
1. A service awareness device integrated into the EPC, or one
provided by a third party, can identify the service and report it
to the eNodeB through the differentiated services code point
(DSCP).
2. The eNodeB can identify the service traffic model based on
the service classification (SC) module.
LOFD-081202 A service maximum bit rate (SMBR) can be configured for
Busy-Hour download services identified by a device on the EPC or
Download Rate provided by a third party. If the download service rate exceeds
Control the SMBR, the eNodeB lowers the priority of download


cation
services, reducing their preempted resources and impacts on
other services.
LOFD-001026 ACK splitting: This function is only available for servers
TCP Proxy running Windows Server 2003. Its use is not recommended. It
Enhancer (TPE) adds the number of TCP ACKs to accelerate the sending rate
of the server.
Enhanced ACK control: When bandwidth is insufficient for
the transmission equipment, this function adjusts the ACK
send rate to prevent packet loss caused by traffic bursts.
MTU control: This function controls the size of the MTU to
prevent IP fragmentation.
Cover LOFD-120205 Timestamp removal removes timestamps, an optional part of
age Uplink the TCP header, to reduce TCP header overhead.
impro Coverage Video TTI bundling transmits different redundancy versions
vemen Improvement for of the same data block to obtain the combined gains and
t Video improve the demodulation capability of the eNodeBs. For
video services, the uplink mainly transmits TCP ACKs, which
are carried by small packets. TTI bundling can improve the
coverage of video services in a way similar to how it
improves coverage for voice services.
Inter-eNodeB UL CoMP for video services, based on the IP
RAN networking, enhances the uplink demodulation over the
air interface and improves coverage in areas where the
coverage is weak.
Value
 User experience improvement
These features are used in a variety of scenarios to improve user experience in the initial
phase of video playback, and during the playback itself.
The initial acceleration feature increases the video rate during the initial phase when the
prerequisites of feature gains are met. Factors that affect initial acceleration gains are as
follows:
− Cell type: Non-high-speed or non-ultra-high-speed cells
− Packet disorder rate and packet loss rate on the network side: These rates must be
lower than 2%. It is recommended that initial acceleration not be used when the
packet disorder rate or the packet loss rate is higher than 2%.
− If the RRC connection reestablishment proportion is greater than 2%, the bit error
rate (BER), RRC connection establishment success rate, RRC connection
reestablishment success rate, call drop rate significantly decrease. It is
recommended that initial acceleration not be used.
The rate adaption feature increases the video service rate when the average UE
throughput during busy hours in a cell is lower than the guaranteed SGBR threshold.
Factors that affect rate adaption gains are as follows:

− The higher the PRB usage is, the higher the probability is that the scheduling
resources are limited and the more gains are yielded by this feature. The feature is
applicable to medium- or heavy-load networks. When the network load is light, the
feature yields no gains, but if the network load is too heavy, it affects other services.
− The more of the video services are optimized, the more video UEs will need to
share the same resources, which reduces the feature gains.
This feature is used to improve coverage for video services, including the uplink
coverage and the video rate for UEs in the weak coverage areas. The feature gains are
affected by the uplink transmit power. There are gains only when the uplink transmit
power is restricted before the downlink transmit power is.
In recommended scenarios, the downlink rate can be improved by up to 50% for a given
position at the cell edge. Factors that affect coverage improvement gains are as follows:
− The feature is suitable for networks where the load is light and the uplink coverage
is limited. It is not appropriate for networks with heavy loads because the downlink
coverage is restricted before the uplink coverage is.
− For Inter-eNodeB UL CoMP, the available bandwidth over the eX2 interface must
be greater than 30 Mbit/s and the transmission delay must be less than 8 ms.
− For video TTI bundling, UEs must support the TTI bundling function.
2.1.6.1 LOFD-110221 Initial Acceleration
Availability
 WTCP proxy is available in macro eNodeBs as of eRAN11.1.
 WTCP proxy is not available in micro eNodeBs.
 WTCP proxy is not available in LampSite eNodeBs.
 Air interface acceleration guarantee for network services is available in macro eNodeBs,
LampSite eNodeBs, BTS3911Es, and BTS3912Es as of eRAN12.1.
Summary
Video services have been developing rapidly and account for an increasingly high proportion
of traffic on LTE networks. User experience with video services determines the overall user
experience with operators' networks.
 WTCP proxy
To improve video service quality, a WTCP proxy function is introduced to the eNodeB based
on characteristics of video services to reduce the initial video playback delay and improve
user experience.
Benefits
 WTCP proxy
This feature minimizes the impact of factors (such as delay and throughput jitter) from the
E-UTRAN side on video services by reducing the initial video buffering delay and mitigating
frame freezing, thereby improving user experience.

Description
The Initial Acceleration feature provides the WTCP proxy function.
 WTCP proxy
The TCP download speed on the Internet is determined by the transmission bandwidth and
round trip time (RTT). The RTT of a downlink TCP packet is measured from the time the
application server sends the packet to the UE to the time a confirmation TCP ACK message is
received. If the RTT decreases, the application server transmits packets at a higher speed,
allowing the UE to enjoy faster access to video data.
The WTCP proxy function in this feature ensures that the eNodeB serves as a proxy during
the initial phase of TCP streaming for HTTP-type video services. Specifically:
The eNodeB responds as a proxy for the UE with a TCP ACK message after receiving a
downlink TCP packet from the application server, reducing RTT. The eNodeB serving as a
proxy for the application server transmits the downlink TCP packet to the UE and processes
the returned TCP ACK message.
This feature increases the rate of delivering packets during TCP slow start, reduces the initial
buffering latency, and improves video service experience.
Enhancement
 eRAN12.1
This feature provides air interface acceleration guarantee for network services for macro
eNodeBs, LampSite eNodeBs, BTS3911Es, and BTS3912Es. The eNodeB must be
equipped with a UMPTa, UMPTb, or UMPTe board to support this function.
Air interface acceleration guarantee for network services identifies services based on the
configured DNS servers and IP addresses. After the UEs that require acceleration
guarantee are identified, continuous preallocation policy is used at the service setup
phase. Uplink packets can be scheduled in time and downlink packets will not enter the
DRX sleep state, reducing service setup delay. During the service, higher uplink and
downlink scheduling priorities are used for these UEs to reduce the service delay and
improve the service rate.
Applicability
Yes Yes Yes
Dependency
 eNodeB
The eNodeB must be equipped with an LBBPd, UBBPd, or UBBPe board, on which the
WTCP proxy function is deployed.
 eCoordinator
None
 UE
None

 Core network
None
 Other NEs
X2 interfaces must be configured between eNodeBs.
 Other features
None
 Others
None
2.1.6.2 LOFD-001026 TCP Proxy Enhancer (TPE)
Availability
This feature is
Summary
The TCP/IP protocol was initially developed for wired transmission and later also used in
wireless network, while the link characteristics in wireless network is quite different from the
wired network. A series of enhancement on TCP functions are implemented in the eNodeB.
This feature enables the performance of the TCP protocol derived from the wired network to
be greatly improved in the wireless network, thus improving user experience and system
efficiency.
Benefits
This feature mitigates the impact of some factors such as packet loss in the RAN side to
improve the performance of TCP data transmission, accelerates the slow startup of the server
during the data transmission, thus greatly improving the TCP transmission performance.
Description
The TCP/IP protocol is extensively used all over the world. It was initially developed for
wired transmission and later also used in wireless networks. However wireless networks have
some characteristics quite different from the wired network. To mitigate this effect, a number
of enhancements have been implemented in the eNodeB.
A TPE (TCP Proxy Enhancer) functionality is implemented in the eNodeB, which improves
the data transmission performance in the wireless network. The TPE processes the TCP/IP
packets by adopting TCP performance optimization technologies such as ACK splitting and
ACK control. This feature accelerates the slow startup of the server and decrease packet drops.
Therefore, this feature greatly improves the TCP transmission performance.
 ACK splitting
In TCP, the congestion window is updated according to the number of received ACK
messages and is expanded by increasing the number of ACK messages. When a slow startup
occurs, ACK splitting can quickly increase the congestion window.

 ACK Control
In LTE system, fluctuations over the air interface are inevitable. Therefore, HARQ/ARQ is
transmitted in the uplink to ensure data is transmitted properly. According to 3GPP
specifications, RLC must cache data and wait until the HARQ/ARQ completed, then hand in
data cached to PDCP in sequence. However, the HARQ/ARQ transmission takes at least 8 ms,
which could be delayed over air interface and burst layer. As a result, downlink TCP services
also burst, and causing packet loss if the buffer size of transmission equipment is limited. The
ACK control function controls the uplink ACK traffic to prevent bursts of downlink data.
 MTU Control
When packet length is greater than PMTU(Path Maximum Transmission Unit), packet is
fragmented on transmission path, which will reduce efficiency of transmission and cause
packet drop probably. MTU Control allows operators to define the packet MSS (Maximum
Segment Size) so the packet fragmentation can be avoided.
Enhancement
 In eRAN6.0
The uplink ACK control function is introduced.
The MTU Control function is introduced .
Dependency
None
2.1.6.3 LOFD-081202 Busy-Hour Download Rate Control
Availability
This feature is
Summary
This feature restricts the data rate of download services during busy hours.
Benefits
The data rate of download services is restricted during busy hours to spare air interface
resources for services with higher priorities.
Description
UEs identify download services through the service identification device of the EPC or a
third-party. The results identified by the service are labeled on the differentiated services code
points (DSCPs) of service packets. The eNodeB identifies these DSCPs and performs
differentiated scheduling based on preset QoS configurations such as priority and service
maximum bit rate (SMBR). When the data rates of download services exceed the configured

SMBR, the eNodeB lowers the scheduling priority of download services to decrease the
resources occupied by such services.
Enhancement
None
Dependency
 eNodeB
None
 eCO
None
 UE
None
None
 CN
None
 OSS
None
 Other Features
None
 Others
This feature is dependent on service identification device, which can be a service
identification entity integrated into the P-GW or a third-party service identification
device purchased by operators.
2.1.6.4 LOFD-081203 Video Service Rate Adaption
Availability
This feature is:
Summary
This feature performs initial video acceleration and service rate guarantee for video services.
Benefits
 Reduced video playback waiting time, improving user experience in playing videos.
 Guaranteed video playback rate, reducing video pauses.

Description
eNodeBs use a service awareness device to identify video services, and then perform
differentiated scheduling based on user-specified QoS information, including priority, service
guaranteed bit rate (SGBR), and phase-based acceleration policy. The following service
identification functions are currently available: differentiated services code point
(DSCP)-based service identification provided by the evolved packet core (EPC), DSCP-based
service identification provided by a third-party device, and service classification (SC)-based
service identification provided by eNodeBs.
When the data rate of video services is lower than the configured SGBR during video
playback, an eNodeB raises the scheduling priority of video services. If the data rate meets the
SGBR, the eNodeB does not adjust the scheduling priority.
If a phase-based acceleration policy is configured, a higher priority and a higher SGBR are
used to guarantee the rate of video services during the initial phase for video services,
increasing the initial video download rate. The initial phase for video services is configurable.
Enhancement
eRAN11.1:
 SC-based service identification
As a service identification function integrated into the eNodeB, SC identifies services
based on the traffic characteristics (for example, the packet size, packet interval, packet
size, and percentages of uplink packets and downlink packets) of known services. The
eNodeB then performs video optimization based on the SC's identification results.
 Multi-frequency video experience coordination
The eNodeB identifies video services using SC, the DSCP-based service identification
function provided by the EPC, or the DSCP-based service identification function
provided by a third-party device, and migrates video service UEs from cells of high
video load to those of low video load. This improves the overall video throughput and
user experience with video services.
This function better balances the distribution of video services on different frequencies,
preventing cell congestion caused by video bursts.
 Video optimization based on SC-based identification results
The eNodeB identifies video services and video types based on SC, and then guarantees
the video service rate based on the specified SGBR. If the video transmission rate is
lower than the SGBR, the eNodeB raises the scheduling priority of video services. If the
video transmission rate is higher than the SGBR, the eNodeB does not adjust the
scheduling priority of video services.
This function increases video throughput and improves video service experience.
Dependency
 eNodeB
The eNodeB must be equipped with a UMPT board, on which video optimization based
on SC's identification results is deployed.
 eCoordinator
None
 UE
None

None
 Core network
None
 OSS
None
 Other features
None
 Others
DSCP-based video service rate adaption requires a service awareness device. The service
identification function must be integrated in the P-GW or provided by a third-party
service awareness device purchased by the operator.
2.1.6.5 LOFD-120205 Uplink Coverage Improvement for Video
Availability
This feature is:
 Available in micro eNodeBs (excluding BTS3202E and BTS3203E) as of eRAN12.1.
Summary
This feature provides inter-eNodeB UL CoMP for video services, video TTI bundling, and
timestamp removal to improve LTE coverage for video services. If the uplink signal to
interference plus noise ratio (SINR) is small, this feature relieves the uplink limitations on
video services and improves downlink coverage of video services for cell-edge UEs.
Benefits
This feature improves video coverage.
Description
Timestamp removal removes timestamps from TCP headers to reduce TCP header overhead
and increase the payload. This is because, the size of a timestamp is generally 12 bytes, and
an uplink TCP ACK contains only header information. After timestamps are removed, the
overhead is reduced significantly. In addition, timestamps are optional for TCP headers, and
removing them has little impact.
Video TTI bundling improves eNodeBs' capability of demodulating UE information by
transmitting redundancy versions of different information to obtain combining gains. As a
transmission characteristic of video services, TCP ACKs with a size of about 54 to 90 bytes
account for a majority of packets transmitted in the uplink, which are small-size packets and
are similar to voice packets. TTI bundling can be used to optimize video services in the uplink,
improving experience of cell edge UEs performing video services.
Inter-eNodeB UL CoMP for video services is based on an IP RAN In weak coverage areas,
UL CoMP is used for video services identified based on SC to improve the uplink

demodulation capability over the air interface and improve the uplink TCP ACK transmission
capability for video services. This function does not require TTI bundling and can be used
when delay is within 8 ms and the inter-eNodeB interaction bandwidth is 30 Mbit/s or higher.
Enhancement
None
Dependency
 eNodeB
The eNodeB must be equipped with a UMPTa, UMPTb, or UMPTe board and a UBBPe,
UBBPd, or LBBPd board.
A UBBPd3 and UBBPd4 in GL or UL dual mode cannot be used for inter-eNodeB UL
CoMP for video services. The RX mode of LBBPd1 and LBBPd2 must be 2R and
non-4R, respectively.
 eCoordinator
None
 UE
Video TTI bundling requires that UEs support TTI bundling.
For inter-eNodeB UL CoMP for video services, the inter-BBU time synchronization
deviation must be within 3 μs, the one-way delay between BBUs must be less than or
equal to 8 ms, and no intermodulation interference or PCI conflict exists.
 Core network
None
 OSS
None
 Other features
SC-based video service identification must be enabled.
 Others
None
2.2 Radio & Performance

2.2.1 2x2 MIMO
Overview
Multiple-input multiple-output (MIMO) is a technology that uses multiple antennas for
transmission and reception in a cell. mxn MIMO indicates that the transmit (TX) side uses m
antennas for transmission and the receive (RX) side uses n antennas for reception.
This document describes multiple-antenna reception and transmission of the eNodeB. Uplink
MIMO is a multiple-antenna reception technology of the eNodeB, and downlink MIMO is a
multiple-antenna transmission technology of the eNodeB.

Applications
2x2 MIMO is a basic configuration of LTE multi-antenna technologies. It is used to expand
uplink and downlink capacity. The following table describes the applications of the feature
package.
Applicatio Feature Description

n
Expanding LOFD-001001 Based on spatial multiplexing, this feature enables a
downlink DL 2x2 MIMO maximum of two layers of data to use the same
capacity time-frequency resource and therefore increases
spectral efficiency. In addition, this feature uses
transmit diversity to achieve diversity gains, improve
signal quality, and increase system throughput.
Expanding LOFD-001002 Based on spatial multiplexing, this feature enables
uplink UL 2x2 two UEs to use the same time-frequency resource for
capacity MU-MIMO data transmission and therefore increases spectral
efficiency and system throughput.
LOFD-001096 This feature works with uplink 2x2 MU-MIMO. It
Advanced Receiver cancels interference between paired UEs based on
(PSIC) iterative detection of the UEs, improving signal
quality and increasing system throughput.
Value
 Expanding downlink capacity
Downlink 2x2 MIMO transmits data at a maximum of two layers to achieve the peak
throughput. It can use transmit diversity to improve UE signal quality in rank-1
transmission and expand downlink capacity.
 Expanding uplink capacity
2x2 MIMO increases the average uplink throughput, relative to uplink 2-antenna receive
diversity. However, many UEs are scheduled when the network is heavily loaded. Uplink
coverage may deteriorate and CEU throughput may decrease when the network
experiences strong interference.
2.2.1.1 LOFD-001001 DL 2x2 MIMO
Availability
This feature is
 applicable to Micro form eRAN3.0

Summary
Two antenna ports are configured in the downlink, and the transmission scheme per user is
dynamically selected between spatial diversity and spatial multiplexing to improve the
downlink throughput and coverage performance.
Benefits
This feature provides the gain of high peak rate and throughput performance using spatial
multiplexing (two code-words) and good cell edge performance using spatial diversity (single
codeword).
Description
The downlink 2x2 MIMO is a critical feature to allow an LTE system to deliver better
performance, such as higher data rates, than the legacy system. Both spatial diversity and
spatial multiplexing are supported as defined in LTE specifications, and since eRAN1.0 the
following four 2x2 MIMO schemes are supported in the downlink:
 Transmit diversity
 Large-delay cyclic delay diversity spatial multiplexing
 Closed-loop spatial multiplexing
 Closed-loop spatial multiplexing using a single transmission layer
Transmit diversity and closed-loop spatial multiplexing using a single transmission layer are
spatial diversity solutions to combat signal fading. Both schemes transmit a single stream (i.e.,
single code-word) and improve the cell edge performance. The former applies the space
frequency block code (SFBC), and is robust to mobility. The latter applies the codebook based
rank-1 precoding and is typically used at low mobility as UE is required to report its preferred
precoding matrix index (PMI) timely.
Large-delay cyclic delay diversity is an open-loop spatial multiplexing scheme with high
robustness to mobility. Closed-loop spatial multiplexing applies the codebook based feedback
and is typically suitable for low mobility. Both open-loop and closed-loop spatial multiplexing
transmit two separately encoded streams (i.e., two codewords) to improve the peak rate and
throughput performance of UEs under good channel conditions with multiplexing gain.
Open-loop/closed-loop spatial multiplexing can be enabled/disabled by means of O&M.
When this functionality is enabled, adaptive switch between spatial diversity and spatial
multiplexing is performed taking into account the UE specific link quality and rank
information. When this functionality is disabled (by setting the maximum rank for spatial
multiplexing to 1), a single codeword is always scheduled for all UEs.
Besides fixed MIMO modes, adaptive open-loop MIMO, adaptive closed-loop MIMO, and
adaptation between open-loop and closed-loop MIMO modes can be configured by means of
O&M.
Enhancement
 eRAN8.1
Downlink 2x2 MIMO in TM9 increases the average cell throughput and cell-edge
throughput in the downlink in scenarios where adaptive single frequency network(SFN)
is deployed and each cell is served by multiple RF modules.

Dependency
 eNodeB
Downlink 2x2 MIMO requires the eNodeB to provide 2 TX channels and 2 antennas.
 UE
Spatial multiplexing is supported for terminals with UE category of greater than one.
That is, for category-1 UEs, only a single codeword is scheduled. Relatively accurate
PMI report from UE is a prerequisite for the configuration of closed-loop MIMO modes.
2.2.1.2 LOFD-001002 UL 2x2 MU-MIMO
Availability
This feature is
Summary
Huawei eRAN1.0 supports UL 2x2 MU-MIMO between UE and eNodeB improving system
uplink performance.
Benefits
This feature can improve the system uplink performance, because it allows two users to
transmit data using the same time-frequency resources.
Description
The uplink virtual MIMO is one of the important features to deliver the superior performance
for LTE systems. It refers to a technique of multiplexing several users using the same time
and frequency resources on the uplink.
Uplink virtual MIMO is a way to improve the throughput of the LTE system. With N receive
antennas for an LTE eNodeB, no more than N virtual MIMO users can be demodulated. The
uplink virtual MIMO does not involve UEs and it is transparent to UEs.
With uplink virtual MIMO, the eNodeB requires the matching demodulation algorithm and
channel estimation algorithm in order to successfully demodulate the signals from different
virtual MIMO users that use the same frequency-time resources.
If two receive antennas are configured in eNodeB, the eNodeB measures the UE's uplink
channel SINR and channel orthogonality with another UE. If the SINR and orthogonality
meet requirements, 2x2 MU-MIMO is used. Otherwise, 2-Antenna Receive Diversity is used.
UL 2x2 MU-MIMO is only used for the physical uplink shared channel (PUSCH).
If two receive antennas are configured in the eNodeB, the eNodeB adaptively selects between
UL 2x2 MU-MIMO and UL 2-Antenna Receive Diversity.
Enhancement
None

Dependency
 eNodeB
UL 2x2 MU-MIMO requires the eNodeB to provide 2 RX channels and 2 antennas per
sector.
2.2.1.3 LOFD-001096 Advanced Receiver (PSIC)
Availability
This feature is
Summary
eNodeB can use parallel soft interference cancellation (PSIC), an advanced receiver
technology, to mitigate two types of interference: interference between MU-MIMO UEs and
interference among symbols of one UE.
MU-MIMO is the abbreviation of multi-user multiple-input multiple-output (MU-MIMO),
MU-MIMO needs UEs to be paired to support MIMO. MU-MIMO UEs are UEs which are
selected to be paired.
Benefits
By mitigating these two types of interference, PSIC significantly increases the uplink
demodulation performance of the eNodeB and improves system throughput.
Description
When the energy of these two types of interference is dramatically greater than that of the
noise floor, interference will cause poor uplink demodulation performance. Interference
between MU-MIMO UEs and interference between one UE's symbols are inevitable. Because
these interference problems are generated due to the inexact channel orthogonality between
MU-MIMO UEs and the frequency-selective fading characteristic within transmission
bandwidth, respectively.
By effectively mitigating these two types of interference, PSIC significantly increases the
uplink demodulation performance. PSIC also outperforms parallel hard interference
cancellation (PHIC) mechanism in terms of gain and robustness. PSIC brings positive gain
which increases with the increasing of modulation order, but PHIC mechanism introduces
negative gain while mitigating interference.
Enhancement
None
Dependency
 eNodeB
This feature is not applicable to LBBPc board.

 Other features
LOFD-001002 UL 2X2 MU-MIMO
2.2.2 4x2 Downlink MIMO

Overview
Applications
LOFD-001003 DL 4x2 MIMO uses 4 transmit channels and 16 codebooks while downlink
2x2 MIMO uses only 2 and 4 respectively. LOFD-001003 DL 4x2 MIMO increases
beamforming gains, improves PDSCH quality, and expands downlink capacity.
Value
 Improving Downlink Coverage
This feature package increases edge throughput at the same coverage distance. In other
words, it increases coverage distance at the same edge throughput.
 Expanding Downlink Capacity
This feature package expands downlink capacity. It increases the average downlink cell
throughput by 10% to 20%, increases the downlink edge throughput by 10% to 40%, but
decreases the peak throughput by approximately 2.3%, relative to downlink 2x2 MIMO.
 Capacity gains depend on multiple factors.
− The peak throughput can be reached when the SINR is high, UEs are not in line of
sight (LOS), and there are many multipath signals.
− A UE in a cell will obtain higher gains if it is further away from the cell center.
− A cell will obtain higher gains if more UEs in it are far away from the cell center.
2.2.2.1 LOFD-001003 DL 4x2 MIMO
Availability
This feature is
 Not available in micro eNodeBs
 Available in LampSite eNodeBs from eRAN12.1
Summary
Four antenna ports are configured in the downlink, and the transmission scheme per user is
dynamically selected between spatial diversity and spatial multiplexing to improve the
downlink throughput and coverage performance.

Benefits
This feature provides the gain of high peak rate and throughput performance using spatial
multiplexing (two codewords) and good cell edge performance using spatial diversity (single
codeword).
Description
Similar to the downlink 2x2 MIMO feature, four 4x2 MIMO schemes are supported in the
downlink: transmit diversity, large-delay cyclic delay diversity, closed-loop spatial
multiplexing, and closed-loop spatial multiplexing using a single transmission layer. The
former two schemes are robust to mobility while the latter two are typically used at low
mobility as UE is required to report its preferred precoding matrix index (PMI) timely.
4x2 MIMO differs from the 2x2 MIMO mainly in the following aspects:
 Additional reference signal overhead for antenna ports 2 and 3
 Transmit diversity applies the scheme of SFBC plus frequency switch transmit diversity
(FSTD) instead of SFBC
 The closed-loop precoding applies a separate codebook of 16-elements
Consequently, 4x2 MIMO has a slightly lower peak rate than 2x2 MIMO due to additional
reference signal overhead. Nevertheless, 4x2 MIMO can get more precoding gain, improving
the system throughput and especially the cell edge performance based on the assumption that
4x2 MIMO is well supported by the terminals.
Open-loop/closed-loop spatial multiplexing can be enabled/disabled by means of O&M.
When this functionality is enabled, adaptive switch between spatial diversity and spatial
multiplexing is performed on a UE basis taking into account the UE specific link quality and
rank information. When this functionality is disabled, a single codeword is always scheduled
for all UEs.
Besides fixed MIMO modes, adaptive open-loop MIMO, adaptive closed-loop MIMO, and
adaptation between open-loop and closed-loop MIMO modes can be configured by means of
O&M.
Enhancement
 eRAN8.1
Downlink 4x2 MIMO in TM9 is introduced. It is a trail function in eRAN8.1.
Dependency
 eNodeB
DL 4x2 MIMO requires the eNodeB to provide 4 TX channels and 4 antennas.
For LampSite, this feature is only applicable in Virtual 4T4R cells.
 UE
Spatial multiplexing is supported for terminals with UE category of greater than one.
That is, for category-1 UEs, only a single codeword is scheduled.
Relatively accurate PMI report from UE is a prerequisite for the configuration of
closed-loop MIMO modes.
 Other features
- LOFD-001001 DL 2x2 MIMO

- LOFD-001005 4-Antenna Receive Diversity
2.2.3 4-Antenna Receiver Diversity

Overview
Applications
4-Antenna Receive Diversity is used to improve uplink coverage and expand uplink capacity.
The following table describes the applications of the feature package.

n
Improving LOFD-001005 This feature uses two more antennas than uplink
uplink 4-Antenna 2-antenna receive diversity to increase receive diversity
coverage Receiver gains and array gains. It improves uplink interference
Diversity suppression capability, signal quality, and coverage.
Expanding LOFD-001005 This feature uses two more antennas than uplink
uplink 4-Antenna 2-antenna receive diversity to increase receive diversity
capacity Receiver gains and array gains. It improves uplink interference
Diversity suppression capability, signal quality, and system
throughput.
LOFD-001058 Based on spatial multiplexing, this feature enables two
UL 2x4 UEs to use the same time-frequency resource for data
MU-MIMO transmission and therefore increases spectral efficiency
and system throughput.
Value
 Improving uplink coverage
4-Antenna Receive Diversity improves the coverage of PUSCH, PUCCH, and PRACH
by approximately 3 dB, relative to 2-antenna receive diversity.
Coverage gains depend on multiple factors:
− There will be lower gains if MRC is used for uplink reception in a cell.
− There will be higher gains if inter-cell interference is stronger.
 Expanding uplink capacity
4-Antenna Receive Diversity expands uplink capacity. It increases the average uplink
cell throughput by 30% to 65% and the downlink edge throughput by 50% to 170%,
relative to downlink 2x2 MIMO.
Capacity gains depend on multiple factors:

− A UE in a cell will obtain higher gains if it is further away from the cell center.
− A cell will obtain higher gains if more UEs in it are far away from the cell center.
− The number of scheduled UEs will increase after uplink MU-MIMO is used on a
heavily loaded network. Uplink coverage may deteriorate and CEU throughput may
decrease if the network experiences strong interference.
2.2.3.1 LOFD-001005 UL 4-Antenna Receive Diversity
Availability
This feature is
Summary
Receive diversity is the common type of multiple-antenna technology to improve signal
reception and to combat signal fading and interference. It improves network capacity and data
rates. Besides UL 2-Antenna Receive Diversity, Huawei eNodeB also supports 4-Antenna
Receive Diversity.
Benefits
This feature can improve the uplink coverage and throughput.
Description
Receiving diversity is a technique to monitor multiple frequencies from the same signal
source or multiple radios and antennas monitoring the same frequency, in order to combat
signal fading and interference.
Receive diversity is a way to enhance the reception of uplink channels, including the PUSCH,
physical uplink control channel (PUCCH), physical random access channel (PRACH), and
sounding reference signal (SRS).
Huawei eNodeB supports both with RX diversity mode and without RX diversity mode. In
RX diversity mode, Huawei eNodeB can be configured with 4 antennas (4-way) in addition to
UL 2-antenna receive diversity.
Enhancement
None
Dependency
 eNodeB
The eNodeB must have at least 4 Rx antenna.
For Micro, this feature is only applicable to 3203E.

2.2.3.2 LOFD-001058 UL 2x4 MU-MIMO
Availability
This feature is
Summary
Huawei eNodeB supports UL 2x4 MU-MIMO between UE and eNodeB to improve system
uplink performance. Up to 2 UEs could be multiplexed to share the same time-frequency
resources.
Benefits
This feature can improve the overall cell uplink throughput, because it allows 2 users to
transmit data using the same time-frequency resources.
Description
As UL 2X2 MU-MIMO, if four receive antennas are configured in eNodeB, eNodeB can use
UL2X4 MU-MIMO to improve system uplink performance.
The eNodeB measures the UE's uplink channel SINR and channel orthogonality with another
UE. If the UE have good uplink channel SINR and good channel orthogonality with the other
UE, 2x4 MU-MIMO is used. Otherwise, 4-Antenna Receive Diversity is used.
UL 2x4 MU-MIMO is only used for the physical uplink shared channel (PUSCH).
If four receive antennas are configured in the eNodeB, the eNodeB adaptively selects between
UL 2x4 MU-MIMO and UL 4-Antenna Receive Diversity.
Enhancement
None
Dependency
 eNodeB
UL 2x4 MU-MIMO requires the eNodeB to provide 4 RX channels and 4 antennas per
sector.
For Micro, this feature is only applicable to 3203E.
 Other features
For macro, this feature depends on LOFD-001005 UL 4-Antenna Receive Diversity &
LOFD-001002 UL 2x2 MU-MIMO.
For micro, this feature only depends on LOFD-001005 UL 4-Antenna Receive
Diversity .

2.2.4 4x4 Downlink MIMO

Overview
Applications
LOFD-001060 DL 4x4 MIMO uses four transmission layers while downlink 4x2 MIMO uses
only two. LOFD-001060 DL 4x4 MIMO supports rank-3 and rank-4 transmissions for UEs of
categories 6 or higher (excluding categories 8 and 14). It increases the peak throughput and
expands downlink capacity.
Value
This feature package expands PDSCH capacity. It increases the peak throughput by
approximately 100%, average downlink throughput by 20% to 60%, and downlink edge
throughput by 30% to 70%, relative to downlink 2x2 MIMO.
Capacity gains depend on multiple factors.
 The peak throughput can be reached when the SINR is high, UEs are not in LOS, and
there are many multipath signals.
 A UE in a cell will obtain higher gains if it is further away from the cell center.
 A cell will obtain higher gains if more UEs in it are far away from the cell center.
2.2.4.1 LOFD-001060 DL 4x4 MIMO
Availability
Summary
This feature requires that both eNodeBs and UEs be configured with four antenna ports for
downlink MIMO. To increase downlink throughput and improve coverage performance, this
feature can adaptively switch between spatial diversity and spatial multiplexing for each UE.
Benefits
This feature increases the downlink peak rate and throughput and improves coverage
performance by multiple times, compared with 2x2 MIMO and 4x2 MIMO. Therefore, this
feature provides better user experience.

Description
This feature enables UEs with four receive antennas to achieve receive diversity gains,
improves downlink performance, and provides better user experience. In addition, this feature
schedules these UEs on a maximum of four layers, and therefore increases the peak rate and
throughput.
Open-loop spatial multiplexing can be enabled or disabled. UEs of category 5 can be
scheduled on more than two layers only when the maximum rank of spatial multiplexing is 4
and channel quality is acceptable.
Fixed configuration of transmission modes and adaptive configuration of open-loop
transmission modes can be specified manually. If adaptive configuration of open-loop
transmission modes is used, this feature adaptively switches between transmit diversity and
large-delay cyclic delay diversity (CDD) spatial multiplexing based on the UE's link quality
and rank information.
Enhancement
 eRAN8.1
This version introduced downlink 4x4 MIMO in TM9, which is a trial function in this
version.
 eRAN11.1
This version introduced downlink 4x4 MIMO at three or four layers for UEs of category
6 or higher.
Applicability
Yes No Yes
Dependency
 eNodeB
This feature requires eNodeBs to provide four transmit channels.
 eCoordinator
None
 UE
UEs must support downlink 4x4 MIMO.
 Core network
None
 Other NEs
None
 Other features
LOFD-001001 DL 2x2 MIMO


LOFD-001005 UL 4-Antenna Receive Diversity
 Others
None
2.2.5 CoMP
Overview
Inter-cell interference is a major factor that affects the performance of an LTE system, which
uses orthogonal frequency division multiple access (OFDMA). The main anti-interference
technologies are interference randomization, interference cancellation, interference
coordination, and interference utilization.
Coordinated multipoint transmission/reception (CoMP) features perform data transmission
based on comprehensive evaluation on the resources of multiple nodes to significantly
improve network coverage and spectral efficiency.
Applications
CoMP features improve uplink and downlink performance. They are mainly used in low and
high load scenarios. The following table describes the applications of these features.
Application Feature Description

Low load in LEOFD-11130 A number of cell-specific reference signal (CRS)
the downlink 6 Breathing transmissions are disabled under certain conditions to
Pilot reduce interference on neighboring cells and increase
the SINR of the entire network while not affecting the
basic measurement of UEs.
LAOFD-11120 The eNodeB obtains the CRS assistance information of
6 neighboring cells over the X2 interface, selects the
Network-Assist neighboring cells with the strongest interference on UEs
ed CRS IC in the local cell, and sends the CRS assistance
information of these neighboring cells to the UE in the
local cell. The UEs then perform CRS interference
cancellation (IC) based on the assistance information.
High load in LOFD-070208 This feature dynamically configures appropriate
the downlink Coordinated downlink transmit power for each cell in an area,
Scheduling coordinates inter-cell interference, and improves
based Power network performance.
Control
LOFD-060201 With the eCoordinator for centralized management and
Adaptive FDD eNodeBs for distributed control, adaptive
Inter-Cell inter-cell interference coordination (ICIC) automatically
Interference adjusts cell edge band modes and cell transmit power
Coordination based on automatically collected and processed
information about inter-cell interference and cell edge
load. Adaptive ICIC effectively controls inter-cell
interference.
Adaptive ICIC can adjust algorithms based on load


changes in intra-frequency networking scenarios to
reduce inter-cell interference and increase the
throughput of cell edge users (CEUs).
Low/High LOFD-001012 Interference rejection combining (IRC) is a receive
load in the UL antenna combining technology. It effectively combats
uplink Interference inter-cell interference.
Rejection
Combining
LOFD-001094 This feature protects PUCCH and PRACH against
Control inter-cell interference.
Channel IRC
LOFD-120202 This feature reconstructs the interference signals of
Intra-eNodeB neighboring cells and removes them from received
and signals to increase the SINRs and improve the quality of
Inter-eNodeB received signals.
Uplink
Interference
Cancellation
LOFD-001066 This feature implements joint reception and interference
Intra-eNodeB suppression in cells served by the same eNodeB.
UL CoMP
LOFD-070222 This feature works with LOFD-001066 Intra-eNodeB
Intra-eNodeB UL CoMP to implement intra-BBP and intra-BBU
UL CoMP inter-BBP UL CoMP.
Phase II
LOFD-070223 This feature works with LOFD-001066 Intra-eNodeB
UL CoMP UL CoMP and LOFD-070222 Intra-eNodeB UL CoMP
based on Phase II to implement inter-BBU UL CoMP in
Coordinated multi-BBU interconnection scenarios.
eNodeB
High load in LOFD-081206 This feature adjusts modulation and coding schemes
the uplink Uplink (MCSs), resource allocation polices, and transmit power
Coordinated for UEs based on inter-cell information exchange and
Scheduling coordination to increase uplink user-perceived
throughput.
Note that "Low/High load in the uplink" in the preceding table indicates that the features
apply to both low load and high load in the uplink.
Value
 Low load in the downlink
Breathing Pilot will reduce interference between intra-frequency cells, improve signal
quality, and increase user-perceived throughput if network load is low. The CEU
throughput will increase by up to 60% if full buffer services are performed, according to
drive test results.

 High load in the downlink

In Cloud BB mode, the typical scenario is that the average physical resource block (PRB)
usage in the deployment area exceeds 30%, the average inter-site distance (ISD) is less
than 500 m, and no obvious inter-system interference is present. In this scenario, the
average UE throughput increases by 5% to 20% and the CEU throughput increases by
5% to 40%.
In IP RAN mode, the typical scenario is that the average PRB usage in the deployment
area exceeds 30%, the average number of active UEs in hotspot cells is greater than 3,
the average ISD is less than 500 m, and no obvious inter-system interference is present.
In this scenario:
− If the average PRB usage is approximately 30%, then the CEU throughput in
hotspots will increase by up to 10% and the average UE throughput increases by up
to 5%.
− If the average PRB usage is approximately 50%, then the CEU throughput in
hotspots will increase by 5% to 20% and the average UE throughput will increase
by 5% to 10%.
Downlink benefits mainly depend on cell edge load and ISD:
− If the cell edge load is higher, the benefits will be higher.
− If the ISD is longer, the benefits will be lower.
 Low load in the uplink
In Cloud BB mode, the typical scenario is that the average PRB usage in the deployment
area is less than or equal to 30% and no obvious inter-system interference is present. In
this scenario, the average UE throughput increases by 2% to 10% and the CEU
throughput increases by 6% to 25%.
area is less than or equal to 30% and no obvious inter-system interference is present. In
this scenario, the average UE throughput increases by 1% to 7% and the CEU throughput
increases by 3% to 15%.
 High load in the uplink
In Cloud BB mode, the typical scenario is that the average PRB usage exceeds 30% in
the deployment area and no obvious inter-system interference is present. In this scenario,
the average UE throughput increases by 4% to 45% and the CEU throughput increases
by 10% to 100%.
area is greater than 30% and no obvious inter-system interference is present. In this
scenario, the average UE throughput increases by 2% to 40% and the CEU throughput
increases by 5% to 70%.
Uplink benefits mainly depend on the load and the number of receive antennas:
− If the load is higher, the benefits will be higher.
− If there are more receive antennas (for example, four antennas), the benefits will be
lower. If there are fewer receive antennas (for example, two antennas), the benefits
will be higher.
2.2.5.1 LOFD-060201 Adaptive Inter-Cell Interference Coordination
Availability
This feature is:


Summary
Adaptive inter-cell interference coordination (adaptive ICIC) is a combination of centralized
eCoordinator management and distributed FDD eNodeB control. This feature implements
effective inter-cell interference control. This involves automatic adjustments of cell edge band
modes and cell transmit power based on the inter-cell interference and edge load data
automatically collected and processed.
In intra-frequency networking, this feature can adaptively adjust algorithms based on load
changes, which reduces inter-cell interference and improves cell edge user (CEU) throughput.
The adaptive function is automatically disabled or enabled based on network load and
interference to determine whether inter-cell interference coordination is required.
Benefits
This feature reduces interference between cells with the same frequency and bandwidth and
increases CEU throughput.
This feature automatically implements ICIC, reduces operators' workload for ICIC
configuration, and lowers operating expense (OPEX).
Description
This feature provides the following functions:
 Adaptive ICIC
With the eCoordinator for centralized management and eNodeBs for distributed control,
adaptive ICIC automatically collects and processes data about inter-cell interference and
cell edge load and adjusts cell edge band modes and UE band scheduling policies based
on the data. Adaptive ICIC implements soft frequency reuse and effectively controls
inter-cell interference.
 Adaptive ICIC plus
Based on the architecture of adaptive ICIC, adaptive ICIC plus controls inter-cell
interference by adjusting transmit power among cells but not adopting soft frequency
reuse.
Both adaptive ICIC and adaptive ICIC plus apply to cells with the same frequency and
bandwidth. The differences between the two functions are as follows:
 Adaptive ICIC automatically configures and adjusts ICIC working modes and cell edge
band modes based on the load and interference data in an area.
 Adaptive ICIC plus automatically adjusts transmit power of each cell based on the load
and interference data in an area.
 Adaptive ICIC slightly decreases CEU throughput and average UE throughput in the cell
by no more than -15%, whereas adaptive ICIC plus does not decrease the throughput. It
is recommended that adaptive ICIC plus replace adaptive ICIC.
Applicability


Yes No No
Enhancement
 eRAN11.1
Huawei has introduced adaptive ICIC plus in eRAN11.1. This function automatically
adjusts transmit power of each cell and reduces inter-cell interference based on the
automatically collected and processed inter-cell interference and edge load data.
Dependency
 eNodeB
None
 eCoordinator
The ECO6910 must be deployed, and adaptive ICIC plus supports only the built-in
eCoordinator.
 UE
None
 Other NEs
None
 Other features
Adaptive ICIC depends on the following features:
− LBFD-001015 Enhanced Scheduling
− LBFD-00101502 Dynamic Scheduling
− LBFD-002026 Uplink Power Control
− LBFD-002016 Dynamic Downlink Power Allocation
Adaptive ICIC is mutually exclusive with the following features:
− LOFD-070205 Adaptive SFN/SDMA
− LOFD-070208 Coordinated Scheduling based Power Control
Adaptive ICIC plus depends on the following features:
− LBFD-00101501 CQI Adjustment
Adaptive ICIC plus is mutually exclusively with LOFD-070208 Coordinated Scheduling
based Power Control.
Either adaptive ICIC or adaptive ICIC plus can be enabled.
 Others
None

2.2.5.2 LOFD-070208 Coordinated Scheduling based Power Control
Availability
This feature is:
 Available in micro eNodeBs (BTS3911E and BTS3912E) as of eRAN11.1.
Summary
Based on coordinated scheduling, the Coordinated Scheduling based Power Control feature
dynamically configures downlink (DL) transmit power for each cell within an area for
inter-cell interference coordination.
Benefits
In an E-UTRAN, physical resource block (PRB) usage increases with the traffic volume. UEs
experience severe interference in densely populated urban areas where intra-frequency
eNodeBs are deployed with an inter-site distance of less than 500 m.
The Coordinated Scheduling based Power Control feature efficiently mitigates inter-cell
interference and offers the following benefits:
 Increases hotspot cell capacity if the network load is unbalanced.
 Increases the throughput of cell edge UEs across the network.
 Reduces handover failures and service drops caused by DL interference.
Description
The Coordinated Scheduling based Power Control feature coordinates cell-specific transmit
power configurations in individual cells in the time domain, reducing inter-cell interference
based on collaboration between scheduling and power control.
As illustrated in Figure 2-15, cell 1 and cell 2 are neighboring cells. To meet their respective
scheduling requirements, the cells coordinate the transmit power for resource elements (REs)
that carry data on the physical downlink shared channel (PDSCH) in the time domain. In the
figure, a blue rectangle represents an RE with full transmit power, a yellow rectangle
represents an RE with increased transmit power, and a gray rectangle represents an RE with
decreased transmit power.

Figure 2-15 Example of time-domain power coordination
This feature includes the following functions:

 CSPC on a centralized Cloud BB network (referred to as the CSPC function in this
section)
On a centralized Cloud BB network, only RRUs are deployed at sites and BBUs are deployed in a
centralized manner and interconnected through USUs. The RRUs and BBUs are connected using CPRI
optical cables.
The centralized control node collects UE scheduling information about each E-UTRAN
cell, calculates the optimal cell power configurations for each E-UTRAN cell, and
delivers the results to the eNodeBs involved. The eNodeBs then change their DL power
to the received power values. Each cell obtains the transmit power configurations for the
local cell and neighboring cells on the same time-frequency resources and updates the
modulation and coding schemes (MCSs) for cell edge UEs. If a UE experiences
interference from neighboring cells, the serving cell schedules the UE on the
time-frequency resources where the neighboring cells reduce transmit power. This type
of scheduling increases the spectral efficiency of the UE.
 CSPC on an IP RAN (referred to as the eCSPC function in this section)
eNodeBs calculate the power adjustment requirement for each neighboring cell,
exchange the requirements over eX2 interfaces, and update DL transmit power
configurations.
 Intra-eNodeB CSPC
This function applies to UEs that experience interference mostly from intra-eNodeB
intra-frequency neighboring cells. It now works only to mitigate interference from the
three strongest intra-eNodeB neighboring cells.

Enhancement
 eRAN8.1
CSPC works in any of the following situations:
− Between macro and micro cells
− Between BBUs that are interconnected through two levels of USUs
− Between single frequency network (SFN) cells
 eRAN11.1
Neighboring cells for SRS measurements can be automatically configured for each cell
based on event A3 reports, simplifying feature activation.
Coordinated Scheduling based Power Control works on IP RANs.
Applicability
Yes Yes Yes
Dependency
 eNodeB
For the CSPC function:
− A UMPT must be configured as the main control board for each BBU.
− The baseband processing units must be LBBPd or UBBP boards.
− A UBBPd6 or UBBPe6 board must be configured in a BBU under each USU and be
used as a centralized control node.
− If the cells in the CSPC coverage area are configured in BBU3900s, an LBBPd or
UBBP must be installed in slot 2 or 3 of each BBU. This constraint does not apply
to cells configured in BBU3910s.
For the eCSPC and intra-eNodeB CSPC functions, the baseband processing units must
be LBBPd, UBBPd, UBBPe, or BBPs of higher specifications.
 eCoordinator
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
− LBFD-00300503 Synchronization with GPS or LOFD-00301302 IEEE1588 V2
Clock Synchronization, for the CSPC function
This feature does not work with the following features:


− LOFD-001007 High Speed Mobility
− LOFD-001008 Ultra High Speed Mobility
− LOFD-001009 Extended Cell Access Radius
− LOFD-060201 Adaptive Inter-Cell Interference Coordination
− LAOFD-081233 Dynamic TDM eICIC
− LEOFD-111302 Flexible Bandwidth based on Overlap Carriers
 If a Double Deck cell group uses a non-standard bandwidth of 5.7, 7.3, 7.6, 8.6,
or 8.9 MHz, the CSPC and intra-eNodeB CSPC functions cannot be activated
in either of the cells in the group.
 If a Double Deck cell group uses a non-standard bandwidth of 4, 12.2, or 17.1
MHz, the CSPC and intra-eNodeB CSPC functions cannot be activated in the
cell with a standard bandwidth of 3 MHz in the group.
 If a Double Deck cell group uses a non-standard bandwidth of 27.6 or 28.5
MHz, the CSPC and intra-eNodeB CSPC functions cannot be activated in the
cell with a standard bandwidth of 10 MHz in the group.
 Others
The CSPC function requires time synchronization with accuracy of ±1.5 μs.
2.2.5.3 LOFD-081206 Uplink Coordinated Scheduling
Availability
This feature is available in macro eNodeBs, micro eNodeBs (BTS3911E and BTS3912E) and
LampSite eNodeBs as of eRAN12.1.
Summary
Uplink Coordinated Scheduling (UL CS) adjusts the resource allocation policy and transmit
power based on the information exchanged between LTE cells and their coordination,
improving the user-perceived uplink throughput.
Benefits
This feature helps increase the average uplink throughput and cell edge user (CEU)-perceived
throughput.
Description
This feature involves coordinated resource allocation (CRA) and coordinated power control
(CPC).
UL CRA adjusts the resource allocation for users in the local cell based on the interference
and load information exchanged between the serving cell and coordinated cells, reducing the
interference of high-interference UEs on neighboring cells in interference-limited scenarios
with increased uplink traffic.
UL CPC calculates the comprehensive scheduling performance of each cell in the cluster
according to the information exchanged between the serving cell and coordinated neighboring
cells to obtain the best performance information and determines the power adjustment
direction based on the user scheduling information and interference on coordinated

neighboring cells. This effectively decreases the interference level in medium- to heavy-load
networks with increased uplink traffic and improves the average user-perceived throughput.
Enhancement
 eRAN12.1
The functions of CRA and CPC are added and can be applicable to networks with relaxed
backhaul requirements. In addition, the functions can be used in micro eNodeBs and
LampSite eNodeBs.
Dependency
 eNodeB
BBP:
LBBPc does not support this feature.
Bandwidth:
CRA is not applicable if the bandwidth is less than 5 MHz.
 eCoordinator
None
 UE
UEs must support this feature.
CPC requires that one-way delay be shorter than 8 ms in networks with relaxed backhaul
requirements.
CRA requires that one-way delay be shorter than 50 ms in networks with relaxed
backhaul requirements.
 Core network
None
 OSS
None
 Other features
CRA does not work with any of the following features or functions:
− Uplink VoIP RB Reservation
− Frequency hopping
− LOFD-081223 Extended Cell Access Radius Beyond 100km
− LOFD-111205 CDMA and LTE Zero Bufferzone (LTE FDD)
− MRFD-090202 GSM and LTE FDD Dynamic Spectrum Sharing(LTE FDD)
− LOFD-001093 PUCCH Flexible Configuration
CPC does not with any of the following features:


− LBFD-070105 IoT-based PUSCH Power Control
 Others
None
2.2.5.4 LOFD-001066 Intra-eNodeB UL CoMP
Availability
 Available in BTS3911Es as of eRAN12.1.
Summary
UL CoMP is short for uplink coordinated multipoint reception.
This feature implements signal combining and interference mitigation for intra-BBP cells.
Benefits
This feature increases the uplink throughput of cell edge users (CEUs) and some cell center
users (CCUs) in intra-BBP cells.
Description
UL CoMP can be used in two scenarios:
 In joint reception scenarios, this feature uses the antennas of two neighboring cells to
receive PUSCH signals from a single UE. This UE is a type-1 UL CoMP UE, located at
the edge of its serving cell and close to the cooperating cell.
 In interference mitigation scenarios, if a UE in a neighboring cell uses the same RBs as a
type-1 UE in the local cell, UL CoMP treats the former UE as a type-2 UE. By using the
signals received from the type-1 UE, UL CoMP mitigates interference from the type-1
UE to the type-2 UE and improves the performance of interference rejection combining
(IRC).
The following figure illustrates joint reception.

Enhancement
 eRAN6.0
− One LBBPd2 or UBBPd4 supports a maximum of three cells. This feature can be
used in 4R cells (that is, cells each with four receive antennas).
− One LBBPd3, UBBPd5, or UBBPd6 supports a maximum of six cells configured
evenly on two carriers. This feature can be used in 2R cells.
 eRAN7.0
One LBBPd3, UBBPd5, or UBBPd6 supports a maximum of six cells configured on one
carrier. This feature can be used in 2R cells.
 eRAN8.1
− Supports 3-cell UL CoMP. The antennas of three cells jointly receive signals from a
single UE. In a 2R cell, a total of six antennas jointly receive PUSCH signals from a
single UE. This joint IRC (JIRC) achieves higher signal quality than joint reception
by a single cell's or two cells' antennas. The following figure compares 2-cell (left)
and 3-cell UL CoMP (right).
− This feature can be performed between 1R cells or between 1R and 2R cells.

− Supports UL CoMP in a HetNet composed of macro eNodeBs and low power nodes
(LPNs).
− Supports macro-micro intra-BBP UL CoMP.
The signals sent by a UE in a macro cell can be jointly received by the macro cell
and micro cells served by LPNs. The joint reception improves the performance of
this UE, as shown in the following figure. In macro-micro scenarios, the eNodeB
can select cooperating cells based on sounding reference signal (SRS)
measurements (that is, UL RSRP values).

− Supports micro-micro intra-BBP UL CoMP. When LPNs are adjacent to each other,
UL CoMP can be performed between the micro cells served by the LPNs. The
working principles are the same as those for intra-BBP macro-macro UL CoMP.
 eRAN11.1
This feature adaptively changes the periodic reporting interval of event A3 measurement
reports based on the number of UEs in connected mode. In addition, this feature stops
UL CoMP when the CPU usage exceeds a certain threshold, reducing Uu signaling and
decreasing CPU usage.
This feature can be performed between 1R/2R and 4R cells.
Applicability
Yes Yes (BTS3911E) Yes
Dependency
 eNodeB
The LBBPc does not support 1R+1R or 1R+2R UL CoMP. Only the UBBPd and UBBPe
support 1R/2R+4R UL CoMP.
The BTS3202E and BTS3203E do not support this feature.
 Other features
Prerequisite feature: LOFD-001012 UL Interference Rejection Combining
− High speed mobility
LOFD-001007 High Speed Mobility
LOFD-001008 Ultra High Speed Mobility
LOFD-081228 Handover Enhancement at Speed Mobility
LOFD-111209 High Speed Specified Policy Management
− SFN based on coordination between BBUs
LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU
LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on Coordinated BBU

If the CellUlschAlgo.UlHoppingType parameter is not set to Hopping_OFF,
frequency hopping is enabled.
− Multi-RRU cell
If the Cell.MultiRruCellFlag parameter is set to BOOLEAN_TRUE and the
Cell.MultiRruCellMode is set to DIGITAL_COMBINATION for a cell, this cell
is a multi-RRU cell.
2.2.5.5 LOFD-070222 Intra-eNodeB UL CoMP Phase II
Availability
Summary
This feature works with LOFD-001066 Intra-eNodeB UL CoMP to implement intra-BBP or
intra-eNodeB inter-BBP UL CoMP.
Benefits
This feature increases the uplink throughput of CEUs and some CCUs in intra-BBP or
intra-eNodeB inter-BBP cells, thereby improving user experience.
Description
This feature uses inter-BBP cell antennas to receive signals from a single UE. The serving and
cooperating cells are set up on different BBPs in the same eNodeB, and they exchange
information between the BBPs.
The following figure shows intra-eNodeB inter-BBP UL CoMP.
Enhancement
 eRAN8.1

− Supports 3-cell UL CoMP. The antennas of three cells jointly receive signals from a
single UE. In a 2R cell, a total of six antennas jointly receive PUSCH signals from a
single UE. This joint IRC (JIRC) achieves higher signal quality than joint reception
by a single cell's or two cells' antennas. The following figure compares 2-cell (left)
and 3-cell UL CoMP (right).
− Supports 1R+1R UL CoMP and 1R+2R UL CoMP.

− Supports UL CoMP in a HetNet composed of macro eNodeBs and low power nodes
(LPNs).
− Supports macro-micro inter-BBP UL CoMP.
The signals sent by a UE in a macro cell can be jointly received by the macro cell
and micro cells served by LPNs. The joint reception improves the performance of
this UE, as shown in the following figure. In macro-micro scenarios, the eNodeB
can select cooperating cells based on SRS measurements (that is, UL RSRP values).
− Supports micro-micro inter-BBP UL CoMP.

When LPNs are adjacent to each other, UL CoMP can be performed between the
micro cells served by the LPNs. The working principles are the same as those for
inter-BBP macro-macro UL CoMP.
 eRAN11.1
− Supports inter-BBP UL CoMP for type-2 UEs.
If the PUSCH PRBs of a UE in a local cell and a type-1 UE in an inter-BBP
neighboring cell overlap each other, this feature mitigates the interference from the
type-1 UE to the type-2 UE, improving the performance of the type-2 UE.
− Supports 1R+4R UL CoMP and 2R+4R UL CoMP.

Applicability
Yes No Yes
Dependency
 eNodeB
− BBU
If a BBU3900 is used, an intra-BBU connection set must contain cells established
on at least one LBBPd or UBBPd in slot 2 or 3.
− BBP
Only the UBBPd and UBBPe support inter-BBP type-2 UL CoMP.
Only the UBBPd and UBBPe support 1R/2R+4R UL CoMP.
− Cell
− Micro eNodeB
The BTS3202E, BTS3203E, BTS3911E, and BTS3912E do not support this feature.
 Other features
− Other features mutually exclusive with this feature are the same as those for
LOFD-001066 Intra-eNodeB UL CoMP.
2.2.5.6 LOFD-070223 UL CoMP Based on Coordinated eNodeB
Availability
Summary
This feature implements inter-eNodeB UL CoMP by working with LOFD-001066
Intra-eNodeB UL CoMP and LOFD-070222 Intra-eNodeB UL CoMP Phase II in
multi-eNodeB interconnection scenarios.
Benefits
This feature raises the proportion of CEUs and some CCUs for which UL CoMP is performed
in inter-eNodeB cells, increases uplink UE throughput, and improves user experience.

Description
This feature uses the antennas of inter-eNodeB cells to jointly receive signals from a single
UE. The serving and cooperating cells are set up on different eNodeBs, and they exchange
information between the eNodeBs.
This feature requires time synchronization between BBUs (for example, using a GPS clock).
This feature can be used in the following scenarios:
 Inter-eNodeB UL CoMP
Figure 2-16 Inter-eNodeB UL CoMP (using USU-based interconnection as an example)
 Macro-micro inter-eNodeB UL CoMP

The signals sent by a UE in a macro cell can be jointly received by the macro cell and
micro cells served by LPNs. The joint reception improves the performance of this UE, as
shown in the following figure. In macro-micro scenarios, the eNodeB can select
cooperating cells based on SRS measurements (that is, UL RSRP values).

 Supports micro-micro inter-eNodeB UL CoMP.

When LPNs are adjacent to each other, micro-micro UL CoMP can be performed. The
working principles are the same as those for inter-eNodeB UL CoMP.
Enhancement
 eRAN8.1
− Supports 3-cell UL CoMP.
− Supports two levels of USUs.
− In macro-micro scenarios, the eNodeB can select cooperating cells based on SRS
measurements (that is, UL RSRP values). The macro cell selects appropriate
cooperating cells based on the difference between the UL RSRP measured by the
serving cell and the UL RSRP values measured by LPN-served micro cells.
− Supports micro-micro inter-eNodeB UL CoMP. The principles are the same as those
for inter-eNodeB macro-macro UL CoMP.
− This feature can be performed between 1R cells or between 1R and 2R cells.
 eRAN11.1
− Supports inter-eNodeB UL CoMP for type-2 UEs.
If the PUSCH PRBs of a UE in a local cell and a type-1 UE in an inter-eNodeB
neighboring cell overlap each other, this feature mitigates the interference from the
type-1 UE to the type-2 UE, improving the performance of the type-2 UE.
− This feature can be performed between 1R/2R and 4R cells.
Applicability
Yes No No
Dependency
 eNodeB
− BBU
This feature is dependent on the Cloud BB architecture. It does not work on LBBPc
or LMPT.
If the cells with this feature enabled are configured in BBU3900s, an LBBPd or
When the USU3900 is used, only the cells that are established on BBPs with the
same slot number can form a connection set between BBU3900 and BBU3910. For
example, cells established on the BBP in slot 0 of BBU 0 and those established on
the BBP in slot 0 of BBU 1 can compose an inter-BBU connection set.
− BBP
Only the UBBPd and UBBPe support inter-eNodeB type-2 UL CoMP.
Only the UBBPd and UBBPe support 1R/2R+4R UL CoMP.
− Cell

Multi-eNodeB interconnection is required.
 Other features
− LOFD-070222 Intra-eNodeB UL CoMP Phase II
Mutually exclusive features are the same as those for LOFD-070222 Intra-eNodeB UL
CoMP Phase II.
2.2.5.7 LOFD-120202 Intra-eNodeB and Inter-eNodeB Uplink Interference

Cancellation
Availability
This feature is:
 Available in macro and LampSite eNodeBs as of eRAN12.1.
Summary
In densely populated urban areas, inter-site distance is small, site load is high, and
intra-frequency interference is severe. In IP RAN scenarios, the joint reception solution is
restricted due to high bandwidth consumption. In HetNet scenarios, UEs served by macro
base stations cause strong interference to UEs served by micro base stations, which cannot be
resolved by the joint reception solution.
UL interference cancellation (IC) reconstructs neighboring cell interference signals and
eliminates interference signals from the received signals, thereby improving the quality and
signal to interference plus noise ratio (SINR) of received signals.
UL IC can be applied in intra- or inter-eNodeB networking (BBU, BBU cascading, or cloud
BB) or IP RAN networking (including the HetNet scenarios). The maximum delay supported
in IP RAN scenarios is 4 ms (with low load).
Benefits
The throughput of cell edge UEs (CEUs) improves in heavily or medium loaded networks.
The average cell and CEU throughput improves in HetNet scenarios where networks are
heavily or medium loaded.
Description
UL IC resolves inter-cell interference by using scheduling and antenna transmit/receive
coordination between sites. UL IC helps improve uplink cell edge throughput and capacity,
thereby meeting the requirements on the increasing capacity of air interface.

UL IC reconstructs neighboring cell interference signals and eliminates interference signals

from the uplink received signals, thereby improving the quality and SINR of uplink received
signals.
Based on the signal objects on which the IC functions, UL IC is classified into Pilot IC and
Data IC. Pilot IC functions on DMRS pilot signals and Data IC functions on data signals.
 Pilot IC increases the signal-to-noise ratio (SNR) for preprocessing channel estimation,
which greatly increases the CoMP IC gain while improving channel estimation quality.
 Data IC eliminates known interference, reduces the interference power, and thereby
improving the demodulation performance.
UL IC obtains gains in the following scenarios:
 In IP RAN scenarios, the joint reception solution is restricted due to high bandwidth
consumption. The bandwidth consumption of UL IC is low. Therefore, UL IC obtains the
interference mitigation gains with inter-BBU neighboring cells.
 In HetNet scenarios, UEs served by macro base stations cause strong interference to UEs
served by micro base stations, which cannot be resolved by the joint reception solution.
UL IC suppresses strong interference from UEs served by macro base stations, thereby
obtaining the interference mitigation gains.
Enhancement
 eRAN12.1
− Intra-eNodeB UL IC is supported in eRAN12.1. By enhancing the reconstruction of
neighboring cell interference signals, intra-eNodeB UL IC can further obtain
interference mitigation gains based on the application of intra-eNodeB UL CoMP.
Dependency
 eNodeB
BBP:
This feature requires the UBBPe.
 eCoordinator
None
 UE
None
 This feature is based on the intra- or inter-eNodeB networking (BBU, BBU cascading, or
cloud BB) or IP RAN networking (including the HetNet scenarios).
 Core network
None
 OSS
None
 Other features
LBFD-00300503 Synchronization with GPS or LOFD-00301302 IEEE1588 V2 Clock
Synchronization
This feature does not work with the following features and functions:


Frequency hopping is enabled if CellUlschAlgo.UlHoppingType is not set to
Hopping_OFF.
− Multi-RRU cell
If the Cell.MultiRruCellFlag parameter is set to BOOLEAN_TRUE and the
Cell.MultiRruCellMode parameter is set to DIGITAL_COMBINATION for a cell,
this cell is a multi-RRU cell.
 Others
This feature supports inter-cell uplink IC based on coordinated BBU and requires
inter-BBU time synchronization with accuracy of 3 μs.
2.2.5.8 LOFD-001012 UL Interference Rejection Combining
Availability
This feature is
Summary
This feature allows eNodeB to effectively overcome the inter-cell interference. The method
can be used with receiving diversity and can be used for MIMO decoding in any scenario.
Benefits
This feature can improve the system performance in the presence of interference. Therefore,
enhanced network coverage and better service quality are provided for cell edge users
(CEUs).
Description
Interference Rejection Combining (IRC) is a receive-antenna combining technique to
effectively combat the inter-cell interference. IRC is often used together with receive diversity.
In theory, IRC can be used for Multiple Input Multiple Output (MIMO) decoding in any
scenario, and it is particularly effective for colored interference.
The main advantage of IRC lies in that it can outperform Maximum Ratio Combining (MRC)
in terms of demodulation of a signal in the presence of interference or jamming.
Enhancement
None
Dependency
 eNodeB

The eNodeB must be equipped with multiple receive antennas (equal to or more than
two).
 Other features
LBFD-00202001 UL 2-Antenna Receive Diversity or LOFD-001005 UL 4-Antenna
Receive Diversity.
2.2.5.9 LOFD-001094 Control Channel IRC
Availability
This feature is
Summary
Control channel interference rejection combining (IRC) protects physical uplink control
channel (PUCCH) and physical random access channel (PRACH) from inter-cell interference.
Benefits
Control channel IRC receiver suppresses interference for uplink control channels and
improves the control channel coverage. Downlink performance may indirectly be improved
due to more robust ACK/NAK reporting in uplink.
Description
Control channel IRC on PUCCH and PRACH combines signals on control channels received
by multiple antennas. This feature can suppress colored interference, while maximum ratio
combining (MRC) is not fit for such scenario.
eNodeB supports adaptive switching between IRC and MRC for PUCCHs and PRACHs.
When colored interference is detected, eNodeB selects IRC; In other cases, eNodeB selects
MRC.
Enhancement
None
Dependency
 eNodeB
The eNodeB must be equipped with two or more receive antennas.
PUCCH IRC isn't applicable to LBBPc board.
For Micro PRACH IRC is only applicable to3202E/3203E; PUCCH IRC is only
applicable to3203E.
 Other features
LBFD-00202001 UL 2-Antenna Receive Diversity or LOFD-001005 UL 4-Antenna
Receive Diversity

2.2.6 SFN
Overview
The single frequency network (SFN) feature package includes common SFN features,
adaptive SFN features, and the super combined cell feature.
Common SFN features allow multiple physical cells served by multiple RF modules working
on the same frequency to be combined into one logical cell. Joint transmission by multiple RF
modules is used in the downlink while independent or joint reception by one or multiple RF
modules is used in the uplink.
Adaptive SFN features perform joint scheduling for UEs in the overlapping areas between
physical cells and performs independent scheduling for UEs in the centers of the physical
cells, thereby increasing cell throughput.
The super combined cell feature allows multiple SFN cells with contiguous coverage to be
combined into one logical cell.
The SFN feature package can reduce interference and increase the signal to interference plus
noise ratio (SINR) in the overlapping areas between physical cells, therefore improving user
experience in the overlapping areas and reducing the number of handovers between physical
cells.
Applications
SFN features can be used in outdoor coverage, indoor coverage, indoor and outdoor joint
coverage, and high-speed railway coverage. The following table describes the applications of
these features.

Outdoor LOFD-003029 SFN These features convert mutually interfering
coverage signals of multiple cells into enhanced multipath
LOFD-070205 signals, and perform joint or independent
Adaptive SFN/SDMA scheduling based on UE attributes in both uplink
and downlink. These features increase the SINR
LOFD-081208
at cell edges, decrease the number of neighboring
Inter-eNodeB SFN
cells, reduce co-channel interference between
Based on Coordinated
neighboring cells, and therefore improve user
eNodeB
experience at cell edges.
LOFD-081209
Inter-eNodeB
Adaptive SFN/SDMA
eNodeB
Indoor LOFD-003029 SFN These features allow multiples cells to be
coverage combined into a large SFN cell, and perform joint
LOFD-070205 or independent scheduling based on UE attributes
Adaptive SFN/SDMA in both uplink and downlink. These features
decrease the number of handovers.
LOFD-081208
Inter-eNodeB SFN
eNodeB


LOFD-081209
Inter-eNodeB
Adaptive SFN/SDMA
eNodeB
Outdoor and LOFD-003029 SFN These features allow outdoor and indoor common
indoor joint RRUs to be combined to serve an SFN cell, and
coverage LOFD-070205 perform joint or independent scheduling based on
Adaptive SFN/SDMA UE attributes in both uplink and downlink. These
features reduce service drops due to handovers in
LOFD-081208
indoor-outdoor overlaps and mitigate
Inter-eNodeB SFN
outdoor-to-indoor interference.
eNodeB
LOFD-081209
Inter-eNodeB
Adaptive SFN/SDMA
eNodeB
High-speed LOFD-003029 SFN These features perform joint scheduling for
railway high-speed UEs. These features decrease the
coverage LOFD-081208 number of handovers and improve user
Inter-eNodeB SFN experience in the overlapping areas between
Based on Coordinated physical cells.
eNodeB
LOFD-081221 Super
Combined Cell
Value
 Impact on Capacity
− In outdoor dense scenarios where, for example, three common RRUs are combined
to serve an SFN cell
Common SFN will increase the average downlink user-perceived throughput by
about 30% to 80% and keep the cell throughput nearly unchanged if the physical
cells are lightly loaded before the combination (the total downlink PRB usage is
less than 45%).
Adaptive SFN will increase the average downlink cell throughput by up to 80%
compared with common SFN if the common SFN cell is heavily loaded. Adaptive
SFN will increase the average uplink cell throughput by up to 10% compared with
common SFN if the uplink PRB usage of the common SFN cell exceeds 50%.
− In indoor coverage scenarios where, for example, two pRRU groups (each with five
pRRUs) are combined to serve an SFN cell
Common SFN will increase the average downlink user-perceived throughput by
about 10% to 50% if the physical cells are lightly loaded before the combination
(the total downlink PRB usage is less than 60%).

Adaptive SFN will increase the average downlink cell throughput by up to 70%
compared with common SFN if the common SFN cell is heavily loaded.
− In scenarios where the function 4x4 MIMO in the overlapping areas of an SFN cell
is enabled
This function will increase the downlink user-perceived throughput by up to 20% in
the overlapping areas and up to 4% on average in the SFN cell if the following
conditions are met in the overlapping areas:
 The UEs support TM9/TM10 and 4R.
 More than 20% of the UEs meet 4x4 MIMO requirements.
 The average SINR exceeds 20 dB.
This function will increase the downlink user-perceived throughput by up to 3% in
the overlapping areas and keep it nearly unchanged or decrease it by less than 5%
on average in the SFN cell if the following conditions are met in the overlapping
areas:
 More than 90% of the UEs support TM9/TM10 and 4R.
 More than 20% of the UEs meet 4x4 MIMO requirements.
 The average SINR exceeds 20 dB.
− In linear scenarios, for example, on high-speed railways or in tunnels:
The super combined cell feature will increase the downlink UE throughput in the
boundary physical cells by more than 50% compared with common SFN.
 Impact on Performance
− SFN will increase the SINR of the entire network if SFN is deployed on a large
scale.
− SFN will increase the average cell-specific reference signal (CRS) SINR by 2-3 dB
if three common RRUs are combined to serve an SFN cell in an outdoor dense area
and the system is fully loaded.
− Common SFN and adaptive SFN will increase the average CRS SINR by about
10-20 dB and 5-15 dB respectively (compared with the non-SFN case) if pRRU
groups are combined to serve an SFN cell in an indoor coverage area and the
system is fully loaded. The increase rate depends on the deployment density of
pRRUs before the combination and the number of pRRUs serving an SFN cell after
the combination.
− SFN may decrease the SINR in the overlapping areas between physical cells on
high-speed railways due to frequency shift. This SINR is different from the SINR
actually used for demodulation. Comparing pre- and post-combination CQIs are
recommended for estimating the benefits of SFN.
− SFN will slightly decrease the SINR if the load of the physical cells after the
combination is higher than before.
2.2.6.1 LOFD-003029 SFN
Availability
This feature is:

 4x4 MIMO in TM9/TM10 in the overlapping areas of an SFN cell is available in macro
eNodeBs as of eRAN12.1.
Summary
This feature enables multiple remote radio units (RRUs) to be combined into a single
frequency network (SFN) cell. The SFN cell has only one physical cell identifier (PCI). RRUs
involved in this feature can be common RRUs or pico RRUs (pRRUs).
In the uplink, this feature supports uplink selective reception and joint reception. Uplink
selective reception selects the RRU with the best signal quality for reception. Uplink joint
reception selects the RRU with the best uplink signal quality and the RRU with the highest
signal strength for joint reception.
In the downlink, this feature implements joint scheduling of air interface resources on
different RRUs so that the same data is transmitted using the same time-frequency resources.
For 4R UEs that support TM9 or TM10, 4x4 MIMO can be implemented through channel
state information-reference signal (CSI-RS) in the overlapping areas of an SFN cell.
Benefits
This feature provides the following benefits:
 The SFN feature reduces interference and greatly improves the signal to interference plus
noise ratio (SINR) at the cell edge in a densely populated area.
 The SFN feature improves the blind/weak point coverage and indoor coverage.
 The SFN feature reduces handover times and service drop rate.
 When the SINR reaches the preset threshold in the overlapping areas of an SFN cell, 4R
UEs that support TM9 or TM10 can increase their downlink peak throughput through
4x4 MIMO, thereby increasing the user-perceived rate in the overlapping areas.
Description
In the uplink, the LTE baseband processing unit (LBBP) independently demodulates signals
from different RRUs. During random access, the LBBP receives PRACH and SRS from all
RRUs. Based on received information, the LBBP selects the RRU with the maximum
preamble power for random access. Then the RRU with the maximum preamble power is
selected for selective reception of PUSCH and PUCCH. The RRU with the best SRS SINR or
another RRU with the best SRS RSRP is selected for joint reception of PUSCH and PUCCH.
In the downlink, the LBBP copies the signals of a cell and transmits them to multiple RRUs.
Comparing with single-RRU cells, SFN cells do not have interference between RRUs but
obtain gains from joint transmission of RRUs.
A cell can be divided into multiple coverage areas. Each coverage area has an independent
RRU. Multiple RRUs serving the same cell have the same PCI.
This feature allows two to six RRUs or pRRU groups to be combined to serve one SFN cell
based on the BBP type. All RRUs/pRRUs serving an SFN cell must be connected to LBBP
boards within the same BBU.
When four ports are configured for the two RRUs with the highest RSRPs in an SFN cell to
transmit CSI-RS, 4R UEs can increase their downlink peak throughput through 4x4 MIMO in
the overlapping areas covered by the RRUs where the SINR reaches the threshold, thereby
increasing the user-perceived rate.

Enhancement
 eRAN8.1
4T4R RRUs can be combined to serve an SFN cell. RRUs with different TX/RX modes
(including 2T2R, 2T4R, and 4T4R) can also be combined to serve an SFN cell.
Two RRUs can be combined to serve a physical cell. A maximum of 12 RRUs can be
combined.
The uplink joint reception function of an SFN cell is enhanced as follows:
− Supports joint reception of signals from inter-BBP physical cells
− Supports joint reception of signals from up to three physical cells
− Supports joint reception of signals from physical cells working in 1R+1R or 1R+2R
mode
UL CoMP can be used in SFN cells.
Common RRUs/RFUs and pRRUs can be combined to serve an SFN cell. Physical cells
working in different TX/RX modes can also be combined to form an SFN cell. For
example, physical cells working in 1T1R, 2T2R, and 2T4R modes can be combined, and
those working in 2T2R, 2T4R, and 4T4R modes can also be combined.
 eRAN12.1
BTS3911E and BTS3912E now support SFN and adaptive SFN.
 eRAN12.1
TM9/TM10 UEs support 4x4 MIMO in the overlapping areas of an SFN cell.
Dependency
 eNodeB
This feature requires SRS resource allocation.
It is recommended that this feature be disabled when the system bandwidth is 1.4 or 3
MHz.
The LBBPc applies only to LampSite base stations instead of macro base stations, and
each LBBPc supports an intra-BBP SFN cell served by at most three combined RRUs.
A maximum of six inter-BBP RRUs can be combined. LBBPd1, LBBPd2, LBBPd3,
UBBPd3, UBBPd4, UBBPd5, and UBBPd6 are applicable to macro and LampSite
eNodeBs.
The TX/RX mode of an SFN cell can be configured only as 1T1R, 2T2R, 2T4R, or
4T4R. Different TX/RX modes can also be configured for an SFN cell.
This feature is not supported with LBBPc for Macro RRU combination.
 eCoordinator
None
 UE
To support 4x4 MIMO in TM9/TM10 in the overlapping areas of an SFN cell, UEs must
support TM9 or TM10 and have four receive channels.
None
 Core network
None
 OSS

None
 Other features
This feature is not compatible with the following features:
− LOFD-001031 Extended CP
− LOFD-001074 Intelligent Power-Off of Carriers in the Same Coverage of UMTS
Network
− LEOFD-111305 Virtual 4T4R
− LEOFD-120304 UL 8-Antenna Receive Diversity
− LEOFD-111302 Flexible Bandwidth based on Overlap Carriers
− LOFD-111205 CDMA and LTE Zero Bufferzone (LTE FDD)
− MRFD-111401 GSM and LTE Zero Bufferzone
− MRFD-101221 UL Refarming Zero Bufferzone
 Others
None
2.2.6.2 LOFD-070205 Adaptive SFN/SDMA
Availability
This feature is:
Summary
When multiple physical cells are combined into an SFN cell, the eNodeB classifies UEs by
their signal quality and adaptively selects joint or independent scheduling of time-frequency
resources for the UEs in the downlink. The space division multiple access (SDMA)
technology is used in independent-scheduling mode. In the uplink, the eNodeB selects
different UEs to pair. After being paired, the UEs use the same resource blocks (RBs) for
transmitting data, thereby improving uplink capacity.
Benefits
This feature increases resource utilization and system throughput without compromising
coverage quality.
Baseband processing unit (BBP) interworking enables inter-cell communications, which
allows for wider application of this feature.

Description
In the downlink, the eNodeB determines the attribute of a UE based on the received UL RSRP
values of different RRUs, and then initiates one of the following procedures:
 Joint scheduling of all RRUs' resources
 Joint scheduling of some RRUs' resources
 Independent scheduling of a single RRU's resources
In addition, the eNodeB determines the working RRU list. All PDSCH and PUSCH resources
of the RRUs in the list are jointly or independently scheduled.
In the uplink, the eNodeB selects two UEs without intersection based on the received UL
RSRPs of different RRUs to pair. After being paired, the UEs use the same RBs for
transmitting data.
Enhancement
 eRAN8.1
4T4R RRUs can be combined to serve an SFN cell. RRUs with different TX/RX modes
(including 2T2R, 2T4R, and 4T4R) can also be combined to serve an SFN cell.
Two RRUs can be combined to serve a physical cell. A maximum of 12 RRUs can be
combined.
Uplink joint reception is enhanced in an SFN cell. RRUs serving inter-BBP physical
cells are allowed to jointly receive data. A maximum of three physical cells can be
combined for joint reception. RRUs with different RX modes (including 1R+1R and
1R+2R) can be combined.
UL CoMP can be used in SFN cells.
Common RRUs/RFUs and pRRUs can be combined to serve an SFN cell. Physical cells
working in different TX/RX modes can also be combined to form an SFN cell. For
example, physical cells working in 1T1R, 2T2R, and 2T4R modes can be combined, and
those working in 2T2R, 2T4R, and 4T4R modes can also be combined.
 eRAN11.1
SFN cell configuration is simplified. After the cell grouping result of an SFN cell is
entered on the CME and one of the combined cells is specified as the primary cell, the
eNodeB automatically configures the SFN cell, sets the SFN downlink schedule switch
CellAlgoSwitch.SfnDlSchSwitch to ADAPTIVE in batches, and activates the SFN cell.
Counters related to E-RAB and RRC connection setup in an SFN cell can be collected
for each physical cell.
VoLTE UEs can always be joint-scheduling UEs when the Adaptive SFN/SDMA feature
is enabled.
 eRAN12.1

Uplink adaptive scheduling for SFN is optimized through UE pairing.

 eRAN12.1
Dependency
 eNodeB
This feature requires SRS resource allocation.
MHz.
The LBBPc is applicable only to LampSite eNodeBs and not macro eNodeBs, with a
maximum of three pRRUs combined within one LBBPc.
A maximum of six inter-BBP RRUs can be combined. LBBPd1, LBBPd2, LBBPd3,
UBBPd3, UBBPd4, UBBPd5, and UBBPd6 are applicable to macro and LampSite
eNodeBs.
The TX/RX mode of an SFN cell can be configured only as 1T1R, 2T2R, 2T4R, or
4T4R. Different TX/RX modes can also be configured for an SFN cell.
The TM9 switch can be turned on only when two physical cells are combined into an
SFN cell.
 eCoordinator
None
 UE
None
 Core network
None
 OSS
None
 Other features
This feature requires LOFD-003029 SFN.
− LOFD-060201 Adaptive Inter-Cell Interference Coordination
− MRFD-231806 GSM and LTE Dynamic Power Sharing (LTE)
 Others
None
2.2.6.3 LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU
Availability
This feature is:

 Implemented in Cloud BB networking scenarios.

Summary
This feature works together with SFN. It allows multiple physical cells served by remote radio
units (RRUs) connected to different BBUs to be combined into an SFN cell. All physical cells
in an SFN cell can use only one physical cell identifier (PCI). RRUs involved in this feature
can be common RRUs or pico RRUs (pRRUs).
In the uplink, the eNodeB with SFN enabled selects the RRU with the best signal quality to
receive signals.
Benefits
This feature works together with SFN. In addition to the benefits provided by SFN, this
feature provides the following benefits:
This feature enables physical cells with strong interference to be combined into an SFN cell,
further improving the cell edge coverage compared with SFN.
Description
This feature allows 2 to 6 physical cells to be combined into an SFN cell, depending on the
BBP type. All physical cells in an SFN cell can be deployed on different BBUs.
This feature supports in-advance scheduling, lowering the requirements for the delay and
bandwidth between BBUs. Therefore, there is enough bandwidth between BBUs for
cooperation with other features.
This feature supports the configuration of primary and secondary subracks. The primary
subrack houses the BBU configured with baseband processing units for SFN scheduling, and
the secondary subracks house other BBUs where the physical cells are configured. To enhance
reliability, the physical cells combined into the SFN cell can be configured as secondary cells
in the secondary subrack. In this way, when the communication between the primary subrack
and the secondary subrack is interrupted, the secondary cells start functioning to reduce
performance loss.

Enhancement
 eRAN12.1
Dependency
 eNodeB
This feature is dependent on the Cloud BB architecture. It does not work on LBBPc or
LMPT.
− The antenna modes of all the combined physical cells can be 1T1R, 2T2R, or 2T4R.
Physical cells with different antenna modes can be combined into an SFN cell.
− If the cells with this feature enabled are configured in BBU3900s, an LBBPd or
− All the combined physical cells can be deployed in different BBUs on a cloud BB
network.
 eCoordinator
None
 UE
None
 Core network
None
 OSS
None
 Other features
− LOFD-081219 Inter-eNodeB VoLTE CoMP
− LOFD-001039 RF Channel Intelligent Shutdown
− LOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage
− LOFD-001040 Low Power Consumption Mode
 Others
MHz.

2.2.6.4 LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on

Coordinated BBU
Availability
This feature is:
 Implemented in Cloud BB networking scenarios.
Summary
This feature works together with SFN. It allows multiple physical cells served by remote radio
units (RRUs) connected to different BBUs to be combined into an SFN cell. All physical cells
in an SFN cell can use only one physical cell identifier (PCI). RRUs involved in this feature
can be common RRUs or pico RRUs (pRRUs).
In the uplink, the eNodeB with SFN enabled selects the RRU with the best signal quality to
receive signals.
Benefits
This feature works together with SFN. In addition to the benefits provided by SFN, this
feature provides the following benefits:
This feature enables physical cells with strong interference to be combined into an SFN cell,
further improving the cell edge coverage compared with SFN.
Description
This feature allows 2 to 6 physical cells to be combined into an SFN cell, depending on the
BBP type. All physical cells in an SFN cell can be deployed on different BBUs.
This feature supports in-advance scheduling, lowering the requirements for the delay and
bandwidth between BBUs. Therefore, there is enough bandwidth between BBUs for
cooperation with other features.
This feature supports the configuration of primary and secondary subracks. The primary
subrack houses the BBU configured with baseband processing units for SFN scheduling, and
the secondary subracks house other BBUs where the physical cells are configured. To enhance
reliability, the physical cells combined into the SFN cell can be configured as secondary cells

in the secondary subrack. In this way, when the communication between the primary subrack
and the secondary subrack is interrupted, the secondary cells start functioning to reduce
performance loss.
Enhancement
 eRAN12.1
Dependency
 eNodeB
This feature is dependent on the Cloud BB architecture. It does not work on LBBPc or
LMPT.
− The antenna modes of all the combined physical cells can be 1T1R, 2T2R, or 2T4R.
Physical cells with different antenna modes can be combined into an SFN cell.
− All the combined physical cells can be deployed in different BBUs on a cloud BB
network.
 eCoordinator
None
 UE
None
 Core network
None
 OSS
None
 Other features
− LOFD-003029 SFN
− LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU
− LOFD-001040 Low Power Consumption Mode
− LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB)

− LOFD-060201 Adaptive ICIC

 Others
MHz.
If UL frequency hopping is enabled, UL CoMP cannot be used.
2.2.6.5 LOFD-081221 Super Combined Cell
Availability
This feature is:
Summary
This feature works with SFN and is applied to high-speed railway scenarios. It allows
multiple SFN cells with seamless coverage to be combined into a super combined cell. All
SFN cells in a super combined cell use the same physical cell identifier (PCI) but different
cell global identifications (CGIs). UEs moving in a super combined cell do not experience
handovers. In the overlapping area of SFN cells, the joint transmission technology is applied.
Benefits
This feature reduces the number of handovers for UEs in high-speed railway scenarios and
improves signal quality in the overlapping areas of SFN cells.
An SFN cell in a super combined cell has a flexible number of physical cells. It is assumed
that there are 36 physical cells. If Super Combined Cell is disabled, each SFN cell should
consist of six physical cells to reduce the number of handovers. However, if Super Combined
Cell is enabled, each SFN cell can consist of three physical cells. In this scenario, there are a
total of 12 SFN cells in the super combined cell. In addition, if Super Combined Cell is
enabled, the user throughput in the edge areas of SFN cells increases by 50%.
Description
This feature allows SFN cells in linear coverage along a high-speed railway to be combined
into a super combined cell. The SFN cells can be deployed in the same BBU or on a
centralized cloud BB network.
In a super combined cell, all SFN cells use the same PCI but different CGIs. With this feature
enabled, seamless handover and joint transmission are adopted between SFN cells with linear
coverage so that UEs in a super combined cell almost do not perceive the existence of
multiple SFN cells. This feature reduces the number of handovers, increases the signal quality
in the overlapping areas between SFN cells, and improves user experience in high-speed
railway scenarios.
Enhancement
None

Dependency
 eNodeB
This feature works in cloud BB mode. It does not work on LBBPc, LBBPd, or LMPT.
− A UMPT must be configured as the main control board for each BBU. This feature
is applicable only to UBBPd3, UBBPd4, UBBPd5, UBBPd6, and UBBPe.
− All the combined physical cells must be deployed in the same BBU or on a
centralized cloud BB network.
 Network requirements
Cells near the super combined cell must be common cells or SFN cells deployed by
Huawei.
It is recommended that one super combined cell should not cover the overlapping area of
two high-speed railways.
It is recommended that Super Combined Cell be disabled in the high-speed railway
scenario where SFN cells encounter overshoot coverage.
SFN cells in a super combined cell cannot share a BBP board with common cells or
other SFN cells.
A super combined cell contains a maximum of 100 SFN cells.
 eCoordinator
None
 UE
None
None
 Core network
EPC devices must be from Huawei.
 OSS
None
 Other features
When a super combined cell cooperates with adjacent cells, the feature LOFD-081207
Specified PCI Group Based Neighboring Cell Management must be activated for the
cells and the PCI of the super combined cell must be set in the special PCI range of the
cells. Otherwise, a UE in a common cell may fail to be handed over to the super
combined cell.
− LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz
− LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz

− LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU

− LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB)
− VoIP Semi-persistent Scheduling
2.2.7 High Speed Scenario

Overview
High-speed movement of UEs causes great Doppler effect, which distorts the orthogonality
between subcarriers. Features included in the High Speed Scenario feature are designed to
reduce the impacts of this effect.
The High Speed Scenario feature package reduces handovers, improves performance, and
improves user experience, ensuring LTE service quality in high-speed scenarios, such as
high-speed rail.
Applications
High Speed Scenario features are used in basic scenarios and multi-RRU cells, and for
performance improvement on dedicated/public networks. The following table describes the
features in this package and their applications.
Applicat Feature Description

ion
Basic LOFD-001007 When UEs are moving quickly, eNodeBs use automatic
scenarios High Speed frequency correction (AFC) to correct uplink Doppler shifts
Mobility for demodulation, improve the uplink eNodeB throughput,
increase the UE access success rate, and ensure stable
service provision.
LOFD-001008 When UEs are moving quickly, eNodeBs use AFC to
Ultra High correct uplink Doppler shifts for demodulation, improve the
Speed Mobility uplink eNodeB throughput, increase the UE access success
rate, and ensure stable service provision.
Multi-RR LOFD-001007 In multi-RRU cells, when UEs receive signals from two
U cells High Speed overlapping sectors, there are both positive and negative
Mobility frequency shifts between the different signals. Relative
frequency correction must be performed for the two
neighboring sectors to decrease the downlink frequency
shifts.
Performa LOFD-081228 This feature provides three functions:
nce Handover  Inter-frequency directional handover
improvem Enhancement at
ent on Speed Mobility With dual-carrier networking, the eNodeB delivers only
dedicated/ high-speed neighboring E-UTRAN frequencies to
public high-speed UEs, ensuring that these UEs stay on
networks high-speed railway dedicated networks.
 Low-speed UE outmigration
The eNodeB hands over low-speed UEs from
high-speed frequencies to low-speed frequencies.
 Inter-RAT directional handover


ion
If high-speed UEs need to be handed over from LTE
dedicated networks to UMTS networks, the eNodeB
hands over these UEs to dedicated UMTS networks.
LOFD-111209 This feature provides scenario-specific solutions to
High Speed high-speed coverage using frequencies of public networks.
Specified The eNodeB identifies high-speed UEs and low-speed UEs,
Policy and then applies differentiated QoS policies. This feature
Management provides directional handovers, and reduces the UE
transmit power and allocated resource blocks (RBs) in
neighboring cells, improving performance of high-speed
UEs.
Value
 Basic scenarios
High Speed Mobility and Ultra High Speed Mobility
− Benefits
High Speed Mobility and Ultra High Speed Mobility improves experience for
high-speed users. When the train speed ranges from 300 km/h to 450 km/h, these
features provide the following gains for high-speed UEs:
 Improves the uplink average data rate by 5% to 10%.
 Decreases the service drop rate by up to 20%.
 Improves the handover success rate by up to 5%.
− Requirements
 If the cell operates on a band lower than 1 GHz or the train speed is lower than
120 km/h, the cell is configured as a low-speed cell.
 If the cell operates on a band ranging from 1 GHz to 2.6 GHz and the train
speed reaches 350 km/h, the cell is configured as a high-speed cell.
 If the cell operates on a band ranging from 1 GHz to 2.6 GHz and the train
speed reaches 450 km/h, the cell is configured as an ultra-high-speed cell.
− Impact factors
The more severe the Doppler effect is for high-speed UEs, the more gains there are
from these features. The Doppler effect is made more severe by the following:
 Higher frequency band
 Faster moving UE
 Longer inter-site distance
 Shorter eNodeB-to-rail distance
 Multi-RRU cells
High Speed Mobility
− Benefits
This feature improves the SINR in overlapping coverage areas, increases downlink
cell throughput and UE data rate by 3% to 5% in the 1.8 GHz frequency band.
When this feature is used together with SFN, handovers reduce, inter-site

interference decreases, the SINR in the coverage area overlapped between sites
increases, and the downlink cell throughput increases by 3% to 10%.
− Requirements
1. A train is moving quickly.
2. An SFN cell is served by RRUs of a minimum of two sites.
3. Two antennas connecting to the RRUs are facing each other.
4. Every RRU covers a certain area along the train tracks.
5. The frequency offset is greater than the threshold.
− Impact factors
The stronger the anti-frequency-offset capability of UEs, the greater the gains. The
faster the train speed, the greater the gains. The higher the frequency band, the
greater the gains. The greater the inter-site distance or eNodeB-to-rail distance or
downtilt angle, the greater the gains.
 Performance improvement on dedicated/public networks
Handover Enhancement at Speed Mobility
− Benefits
 Inter-frequency directional handover: The eNodeB delivers only high-speed
neighboring E-UTRAN frequencies to high-speed UEs to ensure that these
UEs stay on high-speed railway dedicated networks. This function increases
the inter-frequency handover success rate of high-speed UEs by up to 2%.
 Low-speed UE outmigration: The eNodeB hands over low-speed UEs from
high-speed railway dedicated networks to public networks to increase the
perceived rates of high-speed UEs by up to 3%.
 Inter-RAT directional handover: The eNodeB hands over high-speed UEs to
high-speed railway dedicated UMTS networks. This function increases the
inter-RAT handover success rate of high-speed UEs by up to 10%.
− Requirements
 Inter-frequency directional handover: High-speed railway dedicated networks
use multi-frequency networking.
 Low-speed UE outmigration: High-speed railway dedicated networks use
multi-frequency networking. Low-speed UEs have accessed the high-speed
railway dedicated networks.
 Inter-RAT directional handover: High-speed railway dedicated UMTS
networks provide coverage for a certain area along the train tracks. High-speed
UEs tend to fall back to UMTS networks.
− Impact factors
If more low-speed UEs have accessed high-speed railway dedicated networks
before this feature is enabled, more resources are occupied by low-speed UEs. With
low-speed UE outmigration enabled, the increase in the data rates of high-speed
UEs is more significant, as well as the decrease in the data rates of low-speed UEs.
High Speed Specified Policy Management
− Benefits
 Preferential scheduling for high-speed UEs
 The average throughput of high-speed UEs increases by up to 20%.
 Adaptive SFN
The average throughput of high-speed UEs increases by up to 10%.

 Closed-loop MIMO
Closed-loop MIMO is not recommended for high-speed UEs. 4T requires
closed-loop MIMO, and 4T is not recommended in high-speed cells. When 2T
is used, closed-loop MIMO improves cell capacity by up to 5%, depending on
the gains provided by MIMO. Therefore, whether 2T is recommended in
high-speed cells varies.
 Semi-persistent scheduling and TTI bundling
The gains provided by High Speed Specified Policy Management vary
depending on those provided by VoLTE. For details, see description about
capacity enhancement and coverage improvement in VoLTE Feature
Parameter Description.
 Intra-frequency directional handover
The proportion of RRC connection reestablishments decreases by up to 30%.
The service drop rate decreases by up to 20%. The proportion of handover
failures decreases by up to 20%.
 Interference avoidance
Experience of high-speed UEs improves by sacrificing the performance of
neighboring cells (by a maximum of 5%) within a short time, which is
tolerable. When the physical resource block (PRB) usage in neighboring cells
is lower than 20%, the perceived rates of high-speed UEs increase by 5% to
15% by reducing the downlink transmit power. When the physical resource
block (PRB) usage in neighboring cells reaches 20%, the perceived rates of
high-speed UEs increase by 5% to 20% by reducing the number of available
PRBs.
− Requirements
Areas along train tracks are covered by public networks. Essentially, high-speed
cells and their neighboring cells use single-frequency networking and provide
continuous coverage.
− Impact factors
 Scheduling prioritization
The gains vary with the number of resources occupied by low-speed UEs and
the scheduling priority weight of low-speed UEs. More low-speed UEs occupy
more resources, leading to a greater cell resource usage. In this case, the
increase in data rates of high-speed UEs is more significant. A smaller
scheduling priority weight of low-speed UEs also leads to a more significant
increase in data rates of high-speed UEs.
 Adaptive SFN
The gains vary with the number of RRUs serving an adaptive SFN cell and the
number of low-speed UEs. If more RRUs serve an adaptive SFN cell or more
low-speed UEs exist, the spectrum utilization is more efficient, the decrease in
the cell load is more significant, and the increase in the data rates of
high-speed UEs is more significant.
 Closed-loop MIMO
The more accurate PMIs reported by UEs, the greater the cell capacity gains.
 Semi-persistent scheduling and TTI bundling
For details, see description about capacity enhancement and coverage
improvement in VoLTE Feature Parameter Description.
 Intra-frequency directional handover

The wider the coverage of low-speed cells along the train tracks, the more
significant the increase in the performance of high-speed UEs.
 Interference avoidance
The gains vary with the interference from neighboring low-speed cells. More
neighboring low-speed cells produce greater interference, and the gains
provided by decreasing the transmit power are greater. More neighboring
low-speed cells and greater loads in these cells produce greater interference,
and the gains provided by decreasing the available RBs are greater.
In general, High Speed Specified Policy Management improves the downlink
throughput by up to 20%, increases the inter-frequency handover success rate
by up to 2%, decreases the probability of RRC connection reestablishment by
up to 30%, decreases the service drop rate by up to 20%, decreases the
probability of handover failures by up to 20%, and increases the inter-RAT
handover success rate of high-speed UEs by up to 10%.
2.2.7.1 LOFD-001007 High Speed Mobility
Availability
This feature is:
Summary
This feature ensures the network performance in high-speed scenarios where the cell operates
in a band ranging from 1 GHz to 2.6 GHz and UEs in the cell move at speeds of up to 350
km/h or where the cell operates in a band not higher than 1 GHz and UEs in the cell move at
speeds of up to 450 km/h.
Benefits
High speed mobility is a Huawei SingleRAN LTE solution to provide high-speed coverage.
 Ensures network performance in the following high-speed scenarios:
− The cell operates in the 700 MHz or 800 MHz band and UEs in the cell move at
speeds of up to 450 km/h.
− The cell operates in a band ranging from 1 GHz to 2.6 GHz and UEs in the cell
move at speeds of up to 350 km/h.
 Provides seamless user experience in high-speed scenarios.
Description
This feature allows a Huawei LTE system to operate in high-speed scenarios and provide
good performance.
The higher speed the UE experiences, the severer fast fading the system suffers. Therefore,
network performance is a challenge in high-speed scenarios.

The Huawei LTE system supports preceding scenarios, covering most scenarios in urban
environment. The eNodeB measures UE speeds and generates channel evaluation solutions.
For example, open-loop adaptive MIMO is supported in high-speed scenarios to achieve
better performance of air interfaces.
Enhancement
 In eRAN7.0
Supporting UEs moving at speeds of up to 350 km/h in cells operating in bands ranging
from 1 GHz to 2.6 GHz
Supporting open-loop adaptive MIMO in high-speed scenarios
Dependency
 eNodeB
The LBBPc does not support this feature. This feature does not apply to the BTS3202E,
BTS3203E, BTS3911E, BTS3912E, or LampSite eNodeBs.
2.2.7.2 LOFD-001008 Ultra High Speed Mobility
Availability
This feature is:
Summary
This feature ensures the network performance in ultra-high-speed scenarios where the cell
operates in a band ranging from 1 GHz to 2.6 GHz and UEs in the cell move at speeds of up
to 450 km/h.
Benefits
High speed mobility is a Huawei SingleRAN LTE solution to provide high-speed coverage.
 Ensures network performance in ultra-high-speed scenarios where the cell operates in a
band ranging from 1 GHz to 2.6 GHz and UEs in the cell move at speeds of up to 450
km/h.
 Provides seamless user experience in ultra-high-speed scenarios.
Description
This feature allows a Huawei LTE system to operate in ultra-high-speed scenarios and provide
good performance. For example, a UE on a high-speed train may move at the speed of up to
450 km/h.
The higher speed the UE experiences, the severer fast fading the system suffers. The detection
algorithm for PRACH channel with greater frequency deviation is supported to ensure the
access performance of ultra-high-speed UEs.

Enhancement
 In eRAN2.0
Supporting UEs moving at speeds of up to 450 km/h
Dependency
 eNodeB
2.2.7.3 LOFD-081228 Handover Enhancement at Speed Mobility
Availability
This feature is:
Summary
In high-speed mobility scenarios (such as high-speed railways), this feature ensures sufficient
resources for high-speed UEs by the following handover enhancements:
 eNodeBs hand over low-speed UEs out from cells with high-speed mobility features
enabled.
 eNodeBs hand over high-speed UEs to cells with high-speed mobility features enabled,
preventing them from being handed over to normal cells.
Benefits
User experience improves in high-speed mobility scenarios.
Description
Generally, a dedicated network is deployed for high-speed mobility scenarios (such as
high-speed railways). However, the dedicated network may have overlapping coverage with
normal macro cells. To prevent normal UEs from occupying dedicated-network resources
reserved for high-speed UEs (for example on the train), eNodeBs with this feature enabled
hand over normal UEs to normal cells. In addition, eNodeBs hand over high-speed UEs to
cells enabled with the high-speed mobility feature in the dedicated network, preventing them
from being handed over to normal cells. This feature enables high-speed UEs to obtain
sufficient resources in the dedicated network, thereby improving user experience and
maximizing the value of the dedicated network.
This feature applies to high-speed and ultra-high-speed mobility scenarios.
Enhancement
None

Dependency
 eNodeB
 Other features
This feature requires the following feature:
LOFD-001007 High Speed Mobility or LOFD-001008 Ultra High Speed Mobility
2.2.7.4 LOFD-111209 High Speed Specified Policy Management
Availability
Summary
This feature consists of the following functions:
 Soft vector networking
When the cells on the high-speed railway dedicated network and public network use the
same frequency, low-speed UEs exist in the high-speed cell. As a result, high-speed and
low-speed UEs coexist in the same cell. The soft vector networking function enables the
eNodeB to distinguish between high-speed and low-speed UEs, provide different
parameter and feature policies for these UEs, and perform differentiated scheduling
based on quality of service (QoS). This function ensures performance of both high-speed
and low-speed UEs and improves user experience of high-speed UEs and overall cell
performance.
 Intra-frequency directional handover
This function enables the eNodeB to hand over high-speed UEs to high-speed cells to
reduce improper handovers.
 Interference avoidance
This function enables the eNodeB to provide differentiated policies for high-speed and
low-speed UEs based on QoS and improve the performance of high-speed cells at the
tolerable performance cost of low-speed cells when a high-speed train passes by.
Benefits
User experience improves in high-speed mobility scenarios.
Description
Based on the High Speed Mobility/Ultra High Speed Mobility and Handover Enhancement at
Speed Mobility features, this feature provides basic UE speed identification and the following
enhanced functions:
 High-speed intra-frequency directional handover: This function adjusts handover
parameters for high-speed UEs to reduce the probability of being incorrectly handed over
to public-network cells.
 High-speed/low-speed UE attribute function optimization: This optimization improves
the scheduling priorities of high-speed UEs and features for low-speed UEs, including
semi-persistent scheduling, TTI bundling, and closed-loop MIMO.

 High-speed/low-speed UE attribute parameter optimization: This optimization provides

differentiated configurations of handover and TA sending period parameters for
high-speed UEs.
 Interference avoidance: This function selects cells experiencing strong interference and
reduces the proportion of available PRBs or the transmit power in neighboring low-speed
cells to reduce the interference to high-speed UEs when the eNodeB identifies that a
high-speed train passes by.
This feature applies to high-speed and ultra-high-speed mobility scenarios.
Enhancement
 eRAN12.1
Interference avoidance is introduced.
Applicability
Yes No No
Dependency
 eNodeB
 eCoordinator
None
 UE
None
None
 Core network
None
 OSS
None
 Other features
The following table provides the prerequisite features of LOFD-111209 High Speed
Specified Policy Management.
Feature ID Feature Name Description
LOFD-001007 High Speed Mobility LOFD-111209 High Speed Specified Policy

Management supports differentiated speed
LOFD-001008 Ultra High Speed management based on UE speed identification.
Mobility This feature takes effect only in high-speed
mobility scenarios and requires either of the
features.

 The following table provides the impacted features of LOFD-111209 High Speed
Specified Policy Management.

LBFD-002025 Basic Scheduling If both this feature and LOFD-111209 High
Speed Specified Policy Management are
enabled, scheduling priorities are raised for
uplink and downlink non-GBR services of
high-speed UEs.
LOFD-001016 VoIP If both these features and LOFD-111209 High
Semi-persistent Speed Specified Policy Management are
Scheduling enabled, these features take effect for low-speed
UEs or when high-speed UEs slow down.
LOFD-001048 TTI Bundling
LBFD-002017 DRX
LOFD-001032 Intra-LTE Load If both this feature and LOFD-111209 High
Balancing Speed Specified Policy Management are
enabled, this feature does not apply to
high-speed UEs, and load-based inter-frequency
measurements and handovers are performed
only on low-speed UEs in high-speed cells.
LOFD-070205 Adaptive If both this feature and LOFD-111209 High
SFN/SDMA Speed Specified Policy Management are
enabled, joint transmission is used for
high-speed UEs and space division multiple
access (SDMA) is used only for low-speed UEs.
 Others
None
2.2.8 QoS
Overview
Features related to quality of service (QoS) provide customer satisfaction indicators for
services provided by an operator. The QoS feature package provides differentiated policies
based on QoS class identifiers (QCIs) and user types, ensuring the user experience for
different users and services. The following table lists QoS feature classifications based on
their bearer and user types.
Feature Differentia Differentiated Policy Feature

Packag tion Item
e
QoS QCI QCI-based scheduling LOFD-081218 Enhanced
policy Extended QCI

Feature Differentia Differentiated Policy Feature

Packag tion Item
e
ARP ARP-based admission LOFD-001029 Enhanced

policy Admission Control
ARP-based congestion LOFD-001029 Enhanced
control policy Admission Control
SPID SPID-specific cell LOFD-001054 Flexible User
reselection policy Steering
SPID-specific handover LOFD-001054 Flexible User
policy Steering
SPID-specific load LOFD-001054 Flexible User
management policy Steering
SPID-specific DRX policy LOFD-001054 Flexible User
Steering
SPID-specific LOFD-001059 UL Pre-allocation
pre-allocation policy Based on SPID
QCIs include GBR and non-GBR bearer information. They are used to differentiate service types, such
as voice services or data services.
Allocation and Retention Priority (ARP) helps differentiate different users performing the same service.
They are used for admission and preemption.
A Subscriber Profile ID (SPID) is used to differentiate users, such as roaming or local users, VoLTE or
CSFB only users, and users of different brands after being combined. On the CN side, they are called
RAT/Frequency Selection Priorities (RFSPs).
Applications
The QoS feature package is used in high-load scenarios to improve the user experience for
specific users on the network or specific high-value users, improve key quality indicators
(KQIs), and reduce user complaints. This solution may impact certain KPIs. Application
scenarios for QoS-related features depend on user and bearer policies specified by operators.
These policies are described in the following table.

n
High- and LOFD-001054 An SPID-specific load management policy can:
low-value Flexible User  Allocate different frequencies to high- and
users Steering low-value users. High-value users are allocated
more bandwidth, reducing complaints from
these high-value users.
 Enable the EPC to dynamically adjust SPIDs
based on UE traffic, transfer high-traffic UEs to
UMTS networks.


n
LOFD-001029 This feature allocates ARP values with high
Enhanced Admission priorities to high-ARPU UEs, ensuring high-ARPU
Control UEs can access networks.
Roaming LOFD-001054 An SPID-specific handover policy enables roaming
users Flexible User UEs to be handed back over to their home networks
Steering when they have returned to networks provided by
their home operators.
PTT LOFD-081218 The Enhanced Extended QCI and other basic
services Enhanced Extended features help provide service experience the same
QCI as that of VoLTE services.
Data card LOFD-001054 SPID-specific DRX and pre-allocation policies help
users Flexible User improve the data card user throughput without
Steering affecting other users.
LOFD-001059 UL
Pre-allocation Based
on SPID
VoLTE-cap LOFD-001054 The SPID-specific cell reselection and handover
able Flexible User policies prevent UEs only supporting CSFB from
UEs/Only Steering reselecting or handing over to 700 MHz cells.
CSFB-capab
le UEs
Value
The following table describes values and factors affecting gains of the QoS feature package.
Applic Feature Values and Factors Affecting Gains

ation
High- LOFD-001054 Value: Improves the user experience for high-value
and Flexible User users and decreases complaints from low-value users.
low-val Steering This value can be observed by testing high-value user
ue users experience.
LOFD-001029
Enhanced Factors affecting gains: network load, and high-value
Admission Control user proportion The higher the network load and the
fewer high-value users are on the network, the greater
the gains.
Roamin LOFD-001054 Value: Meets roaming agreements between operators.
g users Flexible User Factors affecting gains: UEs roaming to discontiguous
Steering coverage areas, and operator overlapping coverage
proportion The greater the proportion of the coverage
that is overlapping, the greater the gains.
PTT LOFD-081218 Value: Ensures PTT service experience. The E-RAB
services Enhanced Extended setup success rate of PTT services increases when the

Applic Feature Values and Factors Affecting Gains

ation
QCI admission algorithm is enabled.
Factors affecting gains: network load, and proportion
of GBR services with higher or the same priority The
higher the network load, the more GBR services there
will be with the same or a higher priority.
Data LOFD-001054 Value: Improves data card user throughput. This value
card Flexible User can be observed by testing the user experience of data
users Steering card users.
LOFD-001059 UL Factors affecting gains: network load The lower the
Pre-allocation Based network load, the greater the gains.
on SPID
VoLTE- LOFD-001054 Value: Prevents complaints from only CSFB-capable
capable Flexible User UEs at new and low frequency bands.
UEs/Onl Steering Factors affecting gains: none
y
CSFB-c
apable
UEs
2.2.8.1 LOFD-001054 Flexible User Steering

2.2.8.1.1 LOFD-00105401 Camp & Handover Based on SPID
Availability
This feature is:
Summary
This feature allows operators to control UE mobility, including camping on, redirection to, or
handovers to suitable cells. The priorities for the cell selection are predefined per subscriber
profile ID (SPID) and configured on eNodeBs.
Benefits
Operators can enable UEs to camp on, be redirected to, or be handed over to a suitable LTE,
UMTS, or GSM cell or a suitable LTE frequency based on service characteristics and load
status. For example, operators can enable data-centric UEs to camp on LTE cells and
voice-centric UEs to camp on GSM or UMTS cells. When UEs move to the boundaries
between roaming areas and non-roaming areas, they can return to their HPLMNs, meeting
requirements of different camping policies.

Description
An SPID is an index of user information, such as the mobility profile and service usage
profile. The information is UE-specific and applies to all its radio bearers.
This index is mapped by the eNodeB to locally defined configuration in order to apply
specific RRM policies, for example, for defining priorities related to idle-mode mobility or
controlling inter-RAT or inter-frequency redirection or handover in RRC_CONNECTED
mode.
In RRC_IDLE mode, a UE can camp on a cell of a suitable RAT or on a suitable frequency.
In RRC_CONNECTED mode, when an inter-frequency or inter-RAT handover or redirection
is triggered for load balancing or overload control, the eNodeB will select a suitable target
from the cells based on the priorities indexed by the UE's SPID. In addition, when the UE
finishes its services, the eNodeB can release the UE into a suitable cell based on the priorities.
For a UE without an SPID, if overload occurs, the UE can also be redirected to a suitable cell
based on common priorities and overload information.
This way, operators make the UE camp on a suitable cell based on its subscription
information. For example, operators can enable dongle UEs to camp on high-frequency LTE
cells for a high service rate and enable VoIP UEs to preferentially camp on low-frequency
LTE cells to ensure contiguous coverage. Based on SPIDs, operators can enable UEs to return
to their HPLMNs using policies such as CSFB, SRVCC, and PS handover.
Enhancement
 eRAN3.0
When an inter-frequency or inter-RAT handover is triggered for an RRC_CONNECTED
UE, the eNodeB can select a suitable target cell or (if the UE is roaming) select an
HPLMN cell based on the priorities indexed by the UE's SPID. HPLMN cells are more
suitable than cells in roaming areas for roaming RRC_CONNECTED UEs that enter
HPLMN LTE or UMTS coverage areas through handovers.
 eRAN8.1
The Enhanced Policy of SPID-specific Handover back to HPLMN is introduced, which
enables UEs with a specific SPID to return to their HPLMNs through the PS handover,
CSFB, or SRVCC procedure when they move to the boundaries between roaming areas
and non-roaming areas.
The Enhanced Policy of SPID-specific Handover back to HPLMN is controlled by the
SPID-specific PLMN selection algorithm switch.
− When the switch is on, the enhanced policy is used. After receiving the SPID
information sent by the MME, an eNodeB implements the policy as follows:
If all neighboring cells on a specific frequency are not allowed to serve as candidate
cells for handovers during roaming, the eNodeB checks whether the PLMN of these
neighboring cells is on the handover-allowed HPLMN list corresponding to the
UE's SPID. If it is, the eNodeB sends measurement configurations about that
frequency to the UE. If it is not, the eNodeB does not send measurement
configurations about that frequency to the UE.
If a neighboring cell on a specific frequency is allowed to serve as a candidate cell
for handovers during roaming, the eNodeB sends measurement configurations
about that frequency to the UE regardless of whether the HPLMN of the
neighboring cell is on the handover-allowed HPLMN list corresponding to the UE's
SPID.
− When the switch is off, the enhanced policy is not used.

 eRAN12.1
The SPID-specific Load Management Policy has been enhanced. Different thresholds for
inter-RAT load balancing can now be specified for different SPIDs. If the load of a cell
exceeds the inter-RAT load balancing threshold specific to an SPID, the eNodeB will
attempt to transfer the UEs with this SPID to inter-RAT cells.
Dependency
 Core network
The EPC must support the SPID configuration.
 Other features
The SPID-specific Load Management Policy in this feature requires LOFD-001032
Intra-LTE Load Balancing, LOFD-070215 Intra-LTE User Number Load Balancing,
LOFD-001044 Inter-RAT Load Sharing to UTRAN, or LOFD-001045 Inter-RAT Load
Sharing to GERAN.
The SPID-specific Handover back to HPLMN Policy in this feature requires
LBFD-00201802 Coverage Based Inter-frequency Handover or LOFD-001019 PS
Inter-RAT Mobility between E-UTRAN and UTRAN.
 Others
The GSM and UMTS networks must support this feature to avoid ping-pong handovers.
2.2.8.2 LOFD-001059 UL Pre-allocation Based on SPID
Availability
This feature is
Summary
Operator can configure a suitable SPID (Subscriber Profile ID for RAT/Frequency Priority) in
core network for each UE. When an UE accesses to the network, its SPID will be transmitted
to the eNodeB, by which the eNodeB can enable or disable the UL pre-allocation for the
corresponding UE.
Benefits
With this feature, Operator can assign different UL pre-allocation capability for different UE.
UL pre-allocation is used when the cell is in a light load situation to achieve the small latency
for a certain UE.
Description
The SPID is an index referring to user information (e.g. mobility profile, service usage
profile). The information is UE specific and applies to all its Radio Bearers.
This index is mapped by the eNodeB to locally defined configuration in order to apply
specific RRM strategies.

Operator can configure a suitable SPID in core network for each UE. When an UE accesses to
the network, its SPID will be transmitted to the eNodeB, by which the eNodeB can enable or
disable the UL pre-allocation for the corresponding UE.
UL pre-allocation functionality allocates PUSCH RBs to the UE while the cell is in light load
situation; even the UE's sending buffer is empty. It gives the UE the possibility to hit the
sending chance quickly. For instance, this functionality can accelerate the ACK of a DL RRC
signaling message.
With UL pre-allocation, the sending delay of UE will be shortened, but the power
consumption of UE will increase. Operators can adjust the related parameters to get
compromise on the latency and power consumption.
Enhancement
None
Dependency
 CN
This feature depends on SAE to support the SPID configuration.
2.2.8.3 LOFD-081218 Enhanced Extended QCI
Availability
This feature is:
Summary
Compared with common extended QoS class identifiers (QCIs), enhanced extended QCIs are
characterized by higher scheduling priorities. This enhances reliability of services with
extended QCIs.
Push to talk (PTT) services can preempt physical resource blocks (PRBs) of low-priority
services. However, operators do not expect PTT services to preempt PRBs without restrictions,
and the proportions of PRBs that can be used by PTT services must be controlled.
Benefits
The scheduling priorities mapped to extended QCIs now equal or exceed those of guaranteed
bit rate (GBR) services. The data rates of services with the extended QCIs are guaranteed
even if cells are severely congested.
When an LTE operator intends to use extended QCIs for services with a high reliability
requirement (for example, PTT services), the Enhanced Extended QCI feature enables
dedicated bearers for these services to be assigned higher scheduling priorities.
In most cases, networks are maintained by operators and provide LTE services for common
UEs. A few PRBs are reserved for government and enterprise PTT UEs. When PTT services
are in off-peak hours, the reserved PRBs can be allocated to common UEs. When the number

of enterprise PTT UEs within an area increases rapidly (for example in public safety
emergencies), operators dynamically raise the number of PRBs used by PTT services on the
live network to meet requirements.
Description
In earlier versions, extended QCIs apply only to non-GBR services and cannot meet operators'
high reliability requirements. The Enhanced Extended QCI feature now raises the QoS
policies of extended QCIs to support GBR services. The scheduling priorities mapped to the
extended QCIs can be configured to equal or exceed the priority mapped to QCI 1. QCI 1 is
used for voice over Long Term Evolution (VoLTE) services according to 3GPP specifications.
Dedicated bearers with extended QCIs use robust header compression (ROHC) to reduce IP
header overheads and increase transmission efficiency.
This feature must be used with the extended QCI configurations of the evolved packet core
(EPC). Parameters related to dedicated GBR bearers, such as uplink and downlink guaranteed
bandwidths for GBR services, must be configured for extended QCIs on the EPC. Otherwise,
eNodeBs cannot apply the QoS policies for GBR services to the extended QCIs.
Enhancement
 eRAN11.1
When PTT services use the Enhanced Extended QCI feature, operators can use the features
LOFD-001048 TTI Bundling and LOFD-001016 VoIP Semi-persistent Scheduling to increase
the uplink coverage and cell capacity of PTT services.
The ratios of uplink and downlink PRBs occupied by the PTT services are measured and
reported to the admission control algorithm. The admission control algorithm then determines
whether the number of PRBs occupied by the ongoing PTT services exceeds the number of
PRBs allocated to the PTT services by the operator. If the maximum number of allocated
PRBs is reached, the admission control algorithm implements admission control for new PTT
service requests to help control PRBs occupied by the PTT services.
In RAN sharing scenarios, PRBs occupied by PTT services can be restricted for different
operators. Operators can adjust the PRBs allocated to PTT services. When PTT services are in
off-peak hours, the PRBs reserved for PTT services can be used by other services. When PTT
services are in peak hours, usage of the PRBs based on the ratios of operator allocated PRBs
occurs due to the high priority of PTT services.
Dependency
 eNodeB
None
 UE
UEs must support dedicated bearer setup and ROHC (if required for PTT services).
None
 CN
The EPC must support extended QCIs.
 OSS
None
 Other features

To allow ROHC for services with extended QCIs, the feature LOFD-001017 RObust
Header Compression (ROHC) must be enabled.
To allow TTI bundling for services with extended QCIs, the feature LOFD-001048 TTI
Bundling must be enabled.
To allow semi-persistent scheduling for services with extended QCIs, the feature
LOFD-001016 VoIP Semi-persistent Scheduling must be enabled.
Resource reservation restricts the number of PRBs for GBR PTT services, not for
non-GBR services. This feature does not take effect on non-GBR PTT services.
When both VoLTE and PTT services exist, it is recommended that the
allocation/retention priority (ARP) allocated by the EPC for the PTT-dedicated extended
QCI be higher than that for QCI 1. This is to ensure that PTT services can be available in
the case of radio network congestion (where all radio resources are occupied by VoLTE
users).
 Others
None
2.2.8.4 LOFD-001029 Enhanced Admission Control

2.2.8.4.1 LOFD-00102901 Radio/transport resource pre-emption
Availability
This feature is
Summary
This feature enables service differentiation when the network is congested to provide better
services for high-priority users.
Benefits
This feature provides operators with a method to differentiate users according to their priority.
High priority users can obtain the system resources in case of resource limitation. In this way,
operators can provide better service to those high priority users.
Description
Pre-emption is the function related to admission control and is the method for differentiating
services. It enables operators to provide different services by setting different priorities, which
will affect the user call setup success rate during the call setup procedure. If there are not
enough resources and a new call is not admitted to access to the network, high priority user
will have more chances to access to the network than low priority users by pre-empting other
low priority users.
The priority information is obtained from the E-RAB Level QoS Parameters including ARP
(Allocation / Retention Priority), in the message of ERAB SETUP REQUEST. The eNodeB
will assign the user priority based on ARP.

Pre-emption will take action if admitting a call fails due to lack of resource, including S1
transmission resource and radio resource (for example, QoS satisfaction ratio based admission
check is failure). The service with the attribution of Pre-emption Capability and Pre-emption
Vulnerability indicates the service ability of pre-empt and pre-emption vulnerability. The
pre-emption capability indicates the pre-emption capability of the request on other E-RABs,
and pre-emption vulnerability indicates the vulnerability of the E-RAB to preemption of other
E-RABs.
In case of Signaling Radio Bearer (SRB), the pre-emption will not be triggered if resource
allocation for SRB fails. For the emergency call (e.g., E911) service, on account of their very
high priority, it always has the preemption capability. For the SRB, emergency call and IMS
signaling, they cannot be preempted.
Enhancement
 In eRAN6.0
This feature enables preemption when the number of UEs that have accessed cells
reaches the maximum number of UEs supported by an eNodeB. With this enhancement,
high-priority services and services that must be guaranteed to comply with laws can
preempt resources of common services and therefore get better access.
An eNodeB admits all initially accessing UEs, allowing setup of Radio Resource Control
(RRC) connections for the UEs. Then during E-UTRAN radio access bearer (E-RAB)
setup, the eNodeB triggers preemption for high-priority services and emergency calls,
which are selected based on allocation/retention priority (ARP) values. The eNodeB
selects services to be preempted in the following sequence: non-GBR services on
unsynchronized UEs, non-GBR services on synchronized UEs, and low-priority GBR
services.
Dependency
 CN
This feature needs the core network to bring the ARP IE to eNodeB during E-RAB
assignment procedure so that eNodeB can get the service priority with those E-RAB
parameters.
2.2.9 High Load Handling

Overview
The High Load Handling feature package provides the following functions:
 Access class (AC) control
AC control manages UE access to networks, as defined by 3GPP. An eNodeB broadcasts
AC control parameters using system information block type 2 (SIB2) to all UEs in a cell.
UEs then perform access control at RRC connection setup, based on the AC information
stored on SIMs, setup types, or service types. In accordance with section 5.3.3 "RRC
connection establishment" in 3GPP TS 36.331 V11.2.0, barring evaluation and barring
control are performed by UEs originating services, rather than UEs handed over from
other cells or UEs terminating services, after the UEs receive AC control parameters
from the eNodeB.
AC control methods include:
− Intelligent AC control

This method applies to mobile originated data (MO data) and mobile originated
signaling (MO signaling) services. The eNodeB determines whether to adjust and
deliver AC control parameters in a cell based on the cell congestion status.
− Dynamic service specific access control (SSAC)
This method applies to multimedia voice and video services. The eNodeB
determines whether to adjust and deliver AC control parameters in a cell based on
cell disaster and congestion status.
 Scheduling optimization
Scheduling optimization gives scheduling priority to UEs with smaller service packets
and better signal quality. This function increases user-perceived data rates.
 Automatic congestion handling
The eNodeB periodically checks cell congestion status and, based on congestion
conditions, adjusts parameter settings to relieve cell congestion, improving network
performance and user experience.
Applications
The following table lists the applications of the High Load Handling feature package and
describes the features involved. Among the functions provided by this package:
 AC control is used for unusual incidents where congestion occurs because a large
number of UEs unexpectedly access a network at the same time, especially where
multimedia video or voice services are in demand, for example, in the event of an
earthquake or tsunami.
 Scheduling optimization is used in common commercial networks with medium or high
load.
 Automatic congestion handling is used on common commercial networks where
congestion may occur.

Flow control LOFD-070207 If the RRC connection setup success rate
occurs in an Intelligent Access decreases because of flow control on the main
eNodeB Class Control control board or baseband processing units,
because a intelligent AC control prevents some UEs from
large number accessing the cell. This feature relieves cell
of UEs congestion, increasing the RRC connection setup
unexpectedly success rate.
access the
network at the LOFD-008002 This feature works at special events where a large
same time. Dynamic number of UEs initiate multimedia voice or video
Service-specific services, for example, at holiday celebration,
Access Control concerts, sporting events, earthquakes, or
tsunamis. It controls UE access for multimedia
voice or video services to prevent network
congestion and ensure that UEs originating data
services can promptly access the disaster bulletin
information on the network.
A common LOFD-110205 This feature gives scheduling priority to UEs
commercial Traffic Model Based with smaller service packets and better signal
network is Performance quality. It increases user-perceived data rates.
medium- or Optimization
heavily-loaded


.
A common LOFD-081205 This feature automatically adjusts parameter
commercial Automatic settings to improve network performance when
network is Congestion Handling the network is suddenly congested, for example,
congested. at large gatherings or sporting events. It restores
the settings when the congestion has been
relieved.
LOFD-110205 This feature gives scheduling priority to UEs
Traffic Model Based with smaller service packets and better signal
Performance quality. It increases user-perceived data rates.
Optimization
Value
The High Load Handling feature package offers the following value:
 AC control offers the following benefits, depending on the traffic model, cell congestion
condition, AC barring factor, and the proportion of UEs supporting AC barring on live
networks:
− Increased RRC connection setup rate
− Decreased number of RRC connection setup requests discarded and rejected by
flow control
− Decreased average CPU usage and maximum CPU usage
− Decreased number of "mo-Data" and "mo-Signalling"–oriented RRC connection
setup requests discarded and rejected by flow control
− Decreased number of multimedia voice or video–oriented RRC connection setup
requests discarded and rejected by flow control
− Increased access success rate for high-priority UEs and decreased number of RRC
connection setup requests from these UEs discarded and rejected by flow control
 Scheduling optimization shortens the service wait time for UEs. It increases
user-perceived data rates and improves user experience while maintaining cell capacity.
Especially, in heavy traffic scenarios (for example, PRB usage > 60%), the
user-perceived data rate increases by 5% to 20%.
 Automatic congestion handling offers the following benefits:
− This function automatically adjusts parameter settings based on the predefined rules
upon network congestion to improve network performance and user experience.
− This function simplifies service assurance and reduces manual OM costs in heavy
traffic scenarios.
Automatic congestion handling and scheduling optimization can both take effect when congestion
occurs. This further increases user-perceived data rates while offering the gains produced by automatic
congestion handling.

2.2.9.1 LOFD-001109 DL Non-GBR Packet Bundling
Availability
This feature is
Summary
Delay-based downlink (DL) packet bundling introduces delay control and bundles DL packets
before transmission.
Benefits
Delay-based DL packet bundling offers the following benefits:
 This feature reduces PDCCH overheads and increases the PDCCH capacity.
 Compared with non-delay-based functions, this feature better meets the delay
requirements of best effort (BE) services and increases the eNodeB throughput in hybrid
service scenarios when both guaranteed bit rate (GBR) and non-GBR services exist.
Description
Delay-based DL packet bundling primarily introduces delay control for BE services.
If the network load is light and the resources for control and traffic channels are sufficient,
delay-based DL packet bundling is not necessary. When the network load increase, PDCCH
packet delay will also increase and PDCCH transmission might be congested. By bundling the
PDCCH packets, eNodeB reduced the overhead on the PDCCH transmission. This feature
improves BE user experience , and increases the eNodeB throughput in hybrid service
scenarios at high load.
When the feature is used, average PDCCH packet delay of GBR services might increase when
it is mixed with non-GBR services. For non-GBR services, when Proportional Fair (PF)
scheduling is used small PDCCH packet delay might increase.
Enhancement
None
Dependency
None
2.2.9.2 LOFD-008002 Dynamic Service-Specific Access Control
Availability
This feature is:
 applicable to Macro from eRAN8.1.

 applicable to Micro from eRAN8.1.

 applicable to LampSite from eRAN8.1.
Summary
In case of sudden disasters, this feature performs dynamic access class (AC) control on
subscribers initiating multimedia telephony video or voice services. The control is based on
cell load.
Benefits
In case of sudden disasters, subscribers may frequently make multimedia voice or video calls
in effort to contact their relatives. This consumes an enormous amount of radio resources, and
therefore prevents other subscribers from using the disaster message board service through the
PS network to obtain the disaster-related information and evacuation advisories in real time.
In addition, other subscribers cannot contact their relatives through the use of short messages.
This feature offers a solution by applying the AC control function on subscribers initiating
multimedia telephony video or voice services when cells are congested in the event of sudden
disasters. Subscribers can then use the disaster message board service through the PS network
and contact their relatives through the use of short messages.
Description
This feature performs dynamic AC control on subscribers initiating multimedia telephony
video or voice services based on cell congestion status in the event of sudden disasters.
The triggering scenario is determined as follows:
 Disaster status
An eNodeB determines whether a disaster occurs according to the earthquake and
tsunami warning system (ETWS) primary notifications (PNs) or the commercial mobile
alert system (CMAS) messages received from the MME. The disaster-related messages
based on which an eNodeB determines disaster status are configurable.
 Cell congestion status
An eNodeB identifies cell congestion status based on the flow control level in the cell.
The specific policies of dynamic AC control are as follows:
 In the disaster response state, if the cell congestion status consistently meets the
triggering condition of AC control throughout a specific number of consecutive
measurement periods, the eNodeB performs AC control on subscribers initiating
multimedia telephony video or voice services.
 If the cell still stays in the disaster response state and has not yet met the stopping
conditions of AC control throughout a measurement period after AC control is triggered,
then the eNodeB gradually increases the proportion of subscribers under AC control
within all subscribers initiating multimedia telephony video or voice services from the
next measurement period.
 An eNodeB retains the current proportion of subscribers under AC control and continues
performing AC control in the next measurement period should the number of consecutive
periods throughout which either of the following conditions met is less than the specified
number:
− The cell has exited the disaster response state.
− The cell meets the conditions for stopping AC control.

 If the cell stays in the ending phase of the disaster response state or meets the conditions
for stopping AC control throughout a specified number of consecutive periods, then the
eNodeB stops AC control on subscribers initiating multimedia telephony video or voice
services.
Enhancement
None
Dependency
 eNodeB
None
 UE
UEs must comply with 3GPP R9-defined AC control on multimedia telephony video or
voice services.
None
 CN
None
 OSS
None
 Other features
This feature requires the LBFD-002009 Broadcast of system information feature.
 Others
None
2.2.9.3 LOFD-070207 Intelligent Access Class Control
Availability
This feature is
Summary
This feature enables access control in scenarios where a large number of users access the
network simultaneously, such as New Year party, concert, or gathering. Access control is
performed based on the cell congestion status to ensure smooth access of UEs and prevent a
sharp increase in signaling load.
This feature may affect user experience in network access. Therefore, it is recommended that
this feature be enabled only when a large number of users access the network simultaneously.
Benefits
This feature offers the following benefits:

 Controls UE access to prevent a sharp increase in signaling load.

 Relieves cell congestion and improves user experience of UEs that have accessed the
network.
Description
As defined in 3GPP specifications, access class control supported since eRAN2.1 enables an
eNodeB to send access control parameters in system information block type 2 (SIB2) to UEs
in a cell. Based on access control parameter settings, UEs then determine whether they can
access the cell.
Based on the access cause, SIB2 can contain access control parameters for different types of
services. The causes include MO Signaling, MO Data, Emergency, SSAC_MMTEL_Video,
SSAC_MMTEL_Voice, and CSFB.
For Emergency services, the access control parameter can specify whether to enable access
barring. For other services, access control parameters can specify the barring factor, barring
duration, and barring of access classes 11 to 15.
Intelligent access class control is an enhancement to access class control. With this
enhancement, an eNodeB can determine whether to start access class control based on the cell
congestion status. After access class control is started, the eNodeB can dynamically adjust
access control parameters until cell congestion is relieved.
Currently, only intelligent access class control for MO Signaling and MO Data are supported.
Intelligent access class control provides the following enhancement:
 Enables an eNodeB to start access class control based on the cell congestion status.
 Enables an eNodeB to dynamically adjust access control parameters after access class
control is enabled.
Enhancement
 eRAN8.1
Operators can configure the triggering and stopping conditions of intelligent AC control
based on the onsite requirements. For example, operators can configure a "quick enter
slow out" policy or a "slow enter quick out" policy for intelligent AC control. In the
"quick enter slow out" policy, when intelligent AC control is enabled, AC control is
allowed to be triggered soon after the triggering condition is met and is allowed to be
stopped some time after the stopping condition is met.
Dependency
 UE
UEs must support AC barring control defined in 3GPP Release 8.
 Other feature
This feature requires LBFD-002009 Broadcast of system information.
2.2.9.4 LOFD-081205 Automatic Congestion Handling
Availability

Summary
Based on scenario-specific adaptive parameter adjustment rules predefined in an eNodeB, the
eNodeB periodically determines whether to enable adaptive parameter adjustment. The
eNodeB checks the performance counters of various resources and periodically determines
whether to trigger adaptive parameter adjustment. If the preset conditions are fulfilled, the
eNodeB performs relevant parameter adjustment to enhance network performance.
Benefits
 Adjusts the parameter settings based on the predefined intelligent optimization functions
in the event of network congestion to improve network performance and user experience.
 Simplifies the service guarantee task and reduces manpower costs in heavy traffic
scenarios.
Description
The eNodeB monitors the usage of specified resources, such as the proportion of cell users,
usage of physical resource blocks (PRBs), usage of PDCCH control channel elements (CCEs),
equivalent proportion of eNodeB users, PUSCH IN, and PUCCH IN. Based on the monitoring
results and predefined trigger conditions, the eNodeB determines whether to trigger intelligent
optimization functions. The procedure consists of the following three steps:
1. Data collection
The eNodeB periodically collects data required for intelligent optimization functions.
2. Trigger condition judgment
The eNodeB judges the trigger conditions for each intelligent optimization rule of an
intelligent optimization function based on the collected data in a period. If a trigger
condition applies, the eNodeB implements the specified parameter adjustment. If none of
the trigger conditions apply, the current procedure ends and a new procedure starts in the
next period.
3. Parameter adjustments according to intelligent optimization functions
The eNodeB adjusts the parameters specified by the triggered intelligent optimization
functions.
The eNodeB periodically follows this procedure to monitor the network load status and
adaptively adjust parameters, maximizing network performance. This feature involves
overhead reduction, efficiency improvement, interference mitigation, and access control.

Figure 2-17 Procedure for Automatic Congestion Handling
Enhancement
 eRAN11.1
The following intelligent optimization functions have been added:
− Optimized T302
− Penalty for abnormal UE access
− Intelligent AC control
PUSCH and PUCCH anti-interference measures have been added to enhance the
network performance in heavy-traffic scenarios.
Applicability
Yes Yes Yes
Dependency
When the cell load meets the trigger condition of an intelligent optimization rule in the
intelligent optimization functions of "Intelligent Access Class Control", the eNodeB
automatically adjusts parameters based on the related intelligent optimization rule. The
intelligent optimization rule requires the feature LOFD-070207 Intelligent Access Class
Control to be active.
2.2.9.5 LOFD-110205 Traffic Model Based Performance Optimization
Availability
This feature is:

Summary
This feature optimizes the enhanced proportional fair (EPF), a scheduling policy, for
non-GBR services considering factors such as the buffered data to be transmitted and the
transmission rates over the Uu interface.
Benefits
This feature improves the average perceivable data rates for non-GBR services in uplink and
downlink during peak hours, improving user experience.
Description
This feature raises the scheduling priorities for "good users" with small traffic volumes and
favorable channel quality through review of the amounts of buffered data and transmission
rates over the Uu interface. In heavy traffic scenarios (for example, the RB usage is greater
than 60%), the traditional PF scheduling algorithm may cause "bad users" with large traffic
volumes and poor channel conditions to occupy a large number of scheduling opportunities.
"Good users", which can be quickly scheduled, must wait in the scheduling queue for long
periods. Consequently, the average perceivable uplink and downlink user rates decrease and
user experience deteriorates. This feature raises the scheduling priorities for "good users" and
reduces the scheduling opportunities for "bad users." Service performance of "good users" is
significantly improved at little expense of unnoticeable performance degradation of "bad
users." The average perceivable uplink and downlink data rates increase and user experience
improves in peak hours at the network level.
This feature works only in cells with a bandwidth of 5 MHz or higher.
Enhancement
None
Dependency
 eNodeB
None
 UE
None
None
 Core network
None
 OSS
None
 Other features
None
 Others
This feature works only in cells with a bandwidth of 5 MHz or higher.

2.2.10 Uplink High Order Modulation

Overview
The Uplink High Order Modulation feature package provides the uplink (UL) 64QAM
modulation scheme. This scheme enables UEs to transmit data at higher rates under favorable
UL radio conditions so as to receive a better experience with data services.
The 64QAM scheme modulates six information bits into one modulation symbol.
Applications
Applicati Feature Description
on
UL LOFD-001006 UL When UL radio conditions are favorable, this feature
high-order 64QAM enables UEs to transmit data at higher rates for better
modulation experience with UL data services.
Value
UL 64QAM provided by Uplink High Order Modulation increases the UL spectral efficiency
and throughput for UEs in the cell center. The amount of the increase varies from 0% to 39%,
depending on radio channel quality.
2.2.10.1 LOFD-001006 UL 64QAM
Availability
This feature is:
Summary
UL 64 quadrature amplitude modulation (64QAM) is a high-order modulation scheme for
uplink data transmission. It enables UEs to transmit data at a higher bit rate to eNodeBs when
radio channel quality is favorable. UL 64 QAM helps increase uplink data throughput and
data transmission rates.
Benefits
This feature enables higher bit rates for services, thereby increasing cell throughput and
Description
UL 64QAM is a supplement to quadrature phase shift keying (QPSK) and 16QAM. It can be
used to increase the bit rate for UEs when radio channel quality is favorable. 64QAM

modulates more bits in a symbol than QPSK and 16QAM. Specifically, six, four, and two bits
are modulated in a symbol in 64QAM, 16QAM, and QPSK, respectively. Therefore, 64QAM
obviously increases the uplink system capacity.
An eNodeB selects a modulation scheme based on radio channel quality. If the radio channel
quality is favorable, the eNodeB can select 64QAM. As a result, large transport blocks can be
used in the uplink to increase data rates.
Enhancement
None
Dependency
 eNodeB
The BTS3202E does not support this feature.
 UE
64QAM applies only when radio channel quality is favorable. The UE should support
64QAM modulation and the eNodeB should support 64QAM demodulation.
2.2.11 RAN & Terminal Cooperation

Overview
With RAN & Terminal Cooperation, UEs and the network cooperate with each other through
information exchange to improve UE performance and user experience.
RAN & Terminal Cooperation is used primarily in differentiated processing for UEs including
SRLTE-capable UEs, WBB UEs, WTTx UEs, and iPhones, or to achieve optimal
performance for functions such as power saving for common UEs. (SRLTE stands for single
radio LTE, WBB for wireless broadband, and WTTx for wireless to the x.)
Applications
The features in the RAN & Terminal Cooperation feature package are independent of each
other and there are no application scenarios of using them together. The following table
describes these features and their applications.
Feature Description
LOFD-001105 Dynamic UE inactivity timers are tuned in different scenarios
DRX through cooperation between smart terminals and the
network, reducing RRC connection-related signaling
LOFD-00110501 Dynamic messages and saving power for smart terminals.
DRX
LOFD-00110502
High-Mobility-Triggered
Idle Mode
LOFD-080212 SRLTE Scheduling and measurement control are implemented for
Optimization SRLTE-capable UEs during handovers through cooperation
between the UEs and the network, improving measurement
accuracy, user rates, and cell throughput.

Feature Description
LOFD-110223 WBB WBB UE identification and differentiated QoS provision
Specified Policy helps develop WBB services while ensuring MBB user
Management experience. As the number of WBB UEs increases and the
network capacity becomes restricted, capacity can be
expanded for specified-service cells to reduce network load
and improve WBB user experience.
LAOFD-111208 Smartphone DRX parameter and scheduling control is implemented for
App-Aware Coordinated iPhones in different service states through cooperation
Control between the iPhones and the network, improving the
iPhones power efficiency.
LOFD-121203 WTTx Uplink HCode data compression is implemented through
Uplink Data Compression cooperation between WTTx UEs and the network,
improving the uplink application-layer data transmission
rate. (HCode is a Huawei proprietary algorithm.)
LEOFD-121203 Idle Mode Paging cycles for smart terminals in idle mode are extended
eDRX for LTE through cooperation between the terminals and the
network, reducing power consumption and prolonging
standby time of the terminals.
Value
The features in the RAN & Terminal Cooperation feature package are independent of each
other and there are no noticeable combined gains of using them together. To learn the benefits
of a particular feature, see the related feature parameter description.
2.2.11.1 LOFD-001105 Dynamic DRX

2.2.11.1.1 LOFD-00110501 Dynamic DRX
Availability
This feature is
Summary
In a network with a large number of smartphones, by increasing the UE inactivity timer,
signaling for establishing and release of Radio Resource Control (RRC) connections is
reduced. If the UE inactivity timer is short, these connections may be established and released
constantly by smartphones for services that use a few small packets or heartbeat packets.
DRX feature reduces the power consumption for smartphones in RRC connection state, but
UE in uplink in-synchronization state and UE in uplink out-of-synchronization state have
different characters. This feature supports separate DRX setting for UE in uplink
out-of-synchronization state, and dynamically switches the DRX setting in both states.

Benefits
When UE inactivity timer is set much longer to reduce RRC-connection-related signaling to
prevent signaling storms, this feature reduced smartphone battery power even further
comparing to DRX feature.
Description
To save battery power, smartphones generally enter idle mode after service sessions end.
However, many smartphone applications use a few small packets or heartbeat packets and, for
most services, smartphones keep always online by periodically sending heartbeat packets to
the corresponding application servers. These heartbeats and other instant service messages
require the network to reestablish connections frequently and therefore consume a large
amount of signaling resources.
When such services are used, the network can enable smartphones to be always online in Uu
interface by setting a long UE inactivity timer. In this case, smartphones will consume more
uplink resources and energy. This is because the smartphones, which are in connected mode,
must monitor physical downlink control channels (PDCCHs) and consume uplink physical
resources for sounding reference signal (SRS) and physical uplink control channels
(PUCCH).
DRX could save smartphone battery power in such case, but the UE in uplink
in-synchronization state and UE in uplink out-of-synchronization state have different
characters regarding DRX. Dynamic DRX addresses the conflict between the amount of
signaling and the consumption of UE power and network resources in different scenarios.
This feature applies all of the following measures:
 Configures DRX parameters for the uplink out-of-synchronization state with a longer
DRX cycle to reduce UE power consumption.
 Dynamically switching DRX parameters when UE is in uplink in-synchronization and
uplink out-of-synchronization states.
Enhancement
None
Dependency
 Other features
This feature requires LBFD-002017 DRX feature.
2.2.11.1.2 LOFD-00110502 High-Mobility-Triggered Idle Mode
Availability
This feature is

Summary
This feature enables a high-mobility UE to switch from the always-online state to idle mode if
the signaling increase due to frequent UE handovers is greater than the signaling reduction
gained by staying in the always-online state.
Benefits
This feature reduces signaling and therefore can protect the network against signaling storms.
Description
This feature includes the following functions:
 Checking whether always-online UEs are in the high-mobility state
This feature applies to UEs that have entered the always-online state. Generally, UEs
stay in connected mode when they are running applications that require heartbeat
messages, such as those for IM, Facebook, or Twitter.
With this feature, eNodeB measures the speed of UE movement, packet sending state,
and cell camping time. With the measurement results eNodeB determines whether the
UEs meet the condition for entering idle mode to minimize the signaling messages for
frequent handover.
 Triggering the high-mobility check in the handover decision phase
After an eNodeB receives a measurement report from a UE and determines that the
conditions for triggering a handover are met, the eNodeB checks whether the UE is in
the high-mobility state. If the UE meets the conditions for switching to idle mode, the
eNodeB releases the RRC connection with the UE. Otherwise, the handover is executed.
 Supporting feature performance monitoring
The effect of this feature can be observed by checking the control-plane CPU usage and
the number of handovers before and after this feature is enabled.
Enhancement
None
Dependency
None
2.2.11.2 LOFD-080212 SRLTE Optimization
Availability
This feature is:

Summary
This feature enables the eNodeB to detect whether an SRLTE-capable UE leaves the LTE
network. By doing this, the eNodeB can stop scheduling the UE when the UE leaves the LTE
network and resume the scheduling of the UE when the UE returns to the LTE network.
Benefits
Upon detecting that an SRLTE-capable UE leaves the LTE network, the eNodeB stops
scheduling the UE and allocates the time-frequency resources to other UEs, improving cell
throughput. The eNodeB also terminates measurement for an SRLTE-capable UE when the
UE leaves the LTE network, improving the measurement accuracy and user rate.
Description
A single-radio UE in the RRC_CONNECTED state periodically leaves the LTE network to
monitor the paging channel (PCH) on a network of another radio access technology (RAT).
The UE also leaves the LTE network due to events such as sending or receiving short
messages. When an SRLTE-capable UE leaves the LTE network, the UE does not notify the
eNodeB and therefore, the eNodeB continues scheduling the UE and performing
measurement for the UE.
The following figure provides the process in which an SRLTE-capable UE periodically leaves
the LTE network to monitor the PCH on the CDMA2000 1X network. When the PCH
monitoring is complete, the UE returns to the LTE network. The minimum monitoring
duration is 80 ms. When additional mechanisms such as TCP penalty are deployed, the
duration can reach a maximum length of 120 ms. The monitoring duration varies with the
paging cycle on the CDMA2000 1X network, which is specified by a parameter on the
CDMA side and can be set to 1.28s or 2.56s.
Figure 2-18 SRLTE-capable UE monitoring a PCH channel on a CDMA2000 1X network
This feature enables the eNodeB to detect the status of an SRLTE-capable UE. If the UE is
monitoring the PCH on the CDMA2000 1X network, the eNodeB stops scheduling the UE
and allocates the time-frequency resources other UEs, improving cell throughput. The
eNodeB also terminates measurement for an SRLTE-capable UE if the UE is monitoring the
PCH, increasing the user rate.
Enhancement
 eRAN12.1
In addition to single-card dual-mode single-radio UEs supporting both LTE and CDMA,
dual-card dual-mode single-radio UEs supporting LTE and CDMA, LTE and GSM, LTE and
UMTS, or LTE provided by different operators also support this feature. The eNodeB

identifies whether a UE leaves the LTE network through private interaction messages. If the
eNodeB detects that the UE leaves the LTE network, the eNodeB stops scheduling the UE and
allocates the time-frequency resources to other UEs, improving cell throughput. The eNodeB
also terminates measurement for an SRLTE-capable UE when the UE leaves the LTE network,
increasing the user rate.
Currently, all dual-card dual-mode single-radio UEs use Qualcomm chips.
Dependency
 UE
The UE supports SRLTE.
2.2.11.3 LOFD-110223 WBB Specified Policy Management
Summary
With the wireless broadband (WBB) function, operators promote the WBB service volume
while retaining a quality mobile broadband (MBB) service experience.
The eNodeB identifies WBB UEs based on subscriber profile IDs (SPIDs) or QoS class
identifiers (QCIs). Then, the eNodeB applies differentiated QoS guarantee and resource
allocation policies to the identified WBB UEs.
Benefits
 Using idle LTE air interface resources in low-PRB-usage areas, such as suburban or rural
areas, operators develop WBB services, which improves the LTE spectral efficiency,
increases profits, and helps operators to preempt the broadband market.
 The WBB solution includes the following functions: scheduling priorities for WBB UEs,
SPID-specific DRX policy, SPID-specific intra- and inter-frequency handover processing,
and restriction of the maximum PRB usage of WBB and MBB UEs. These functions
enable operators to provide differentiated services to promote WBB services while
retaining a quality MBB user experience.
 Operators can expand capacity by adding specified-service cells that only WBB UEs and
emergency-call MBB UEs can camp on, which reduces the network load and prevents
network congestion caused by the increased number of WBB UEs.
Description
The WBB specified policy management feature consists of the following functions:
 WBB UE identification and specified QoS guarantee
The eNodeB identifies WBB UEs based on SPIDs or QCIs. Then, the eNodeB can use
the differentiated scheduling priorities and PRB usage upper limits of WBB and MBB
UEs to ensure the QoS of WBB services. In addition, the eNodeB can also apply
differentiated DRX and intra- and inter-frequency handover treatments on WBB UEs
identified based on SPIDs.
 Specified-service cell planning
Operators can expand the capacity by adding specified-service cells that only WBB UEs
and emergency-call MBB UEs can camp on. Non-emergency-call MBB UEs cannot
camp on the specified-service cells.

Enhancement
eRAN12.1
When both WBB and MBB services are provided, the eNodeB identifies WBB UEs based on
SPIDs or QCIs and allows different configurations of the PRB usage upper limits between the
two types of UEs. In this way, the following problems can be avoided:
 WBB UEs use too many PRBs so that MBB user experience is affected.
 MBB UEs use too many PRBs so that no PRBs are available for WBB UEs.
Dependency
 eNodeB
None
 UE
None
None
 Core network
Supports SPIDs.
 OSS
None
 Other features
The WBB subscriber identification and differentiated QoS guarantee function requires
the following features:
− LOFD-001054 Flexible User Steering: WBB subscribers are identified based on the
SPID.
− LBFD-001015 Enhanced Scheduling: adjusts QoS parameters related to the WBB
UE scheduling priority, which involves scheduling modules.
The WBB subscriber identification and differentiated QoS guarantee function is not
compatible with LOFD-070210 Multi Operators SPID Policy.
 Others
None
2.2.12 Inter-RAT Mobility

Overview
The Inter-RAT Mobility feature package provides mobility management solutions for data
services when multiple networks overlap. The solutions cover mobility from E-UTRAN to
GERAN, from E-UTRAN to UTRAN, and from E-UTRAN to CDMA2000.
Applications
Inter-RAT Mobility is used in coverage-, service-, and distance-based handovers and flexible
policy configurations. The following table lists the features and their applications.


icatio
n
Cover LOFD-001019 PS Inter-RAT This feature ensures data service continuity
age-b Mobility between E-UTRAN between E-UTRAN and UTRAN when the
ased and UTRAN UTRAN provides supplementary coverage for
hando the E-UTRAN, which does not provide full
ver coverage.
LOFD-001020 PS Inter-RAT This feature ensures data service continuity
Mobility between E-UTRAN between E-UTRAN and GERAN when the
and GERAN GERAN provides supplementary coverage for
the E-UTRAN, which does not provide full
coverage.
LOFD-001021 PS Inter-RAT This feature ensures data service continuity
Mobility between E-UTRAN between E-UTRAN and CDMA2000 network
and CDMA2000 when the CDMA2000 network provides
supplementary coverage for the E-UTRAN,
which does not provide full coverage.
LOFD-001111 PS Mobility This feature allows UEs on certain frequencies
from E-UTRAN to of E-UTRAN to be handed over to a
CDMA2000 HRPD Based on CDMA2000 HRPD network based on
Frequency-specific Factors frequency-specific factors to achieve
frequency-based service steering. This feature is
used before E-UTRANs are fully deployed
across an operator's coverage areas and
CDMA2000 networks are used to supplement
coverage and the operator runs multiple
frequency bands.
Servic LOFD-001043 Service based This feature hands over UTRAN-preferred
e-base inter-RAT handover to services from E-UTRAN to UTRAN based on
d UTRAN inter-RAT handover policies that operators
hando configure for services with different QCIs.
ver
LOFD-001046 Service based This feature hands over GERAN-preferred
inter-RAT handover to services from E-UTRAN to GERAN based on
GERAN inter-RAT handover policies that operators
configure for services with different QCIs.
Distan LOFD-001072 Distance based This feature hands over UEs from E-UTRAN to
ce-bas inter-RAT handover to UTRAN based on inter-site distances when the
ed UTRAN E-UTRAN and the UTRAN overlap and the
hando E-UTRAN experiences a severe overshoot
ver coverage issue.
LOFD-001073 Distance based This feature hands over UEs from E-UTRAN to
inter-RAT handover to GERAN based on inter-site distances when the
GERAN E-UTRAN and the GERAN overlap and the
E-UTRAN experiences a severe overshoot
coverage issue.
Flexib LOFD-001078 E-UTRAN to This feature hands over CS and PS services to
le UTRAN CS/PS Steering their respective preferred systems.


icatio
n
policy LOFD-070216 Separate This feature hands over UEs from E-UTRAN to
config Mobility Policies to UTRAN a UTRAN cell in a specific PLMN when the
uratio for Multi PLMN UTRAN cell belongs to multiple PLMNs.
n
LOFD-111204 Separate This feature hands over UEs from E-UTRAN to
Mobility Policies to GERAN a GERAN cell in a specific PLMN when the
for Multi PLMN GERAN cell belongs to multiple PLMNs.
Other LOFD-070203 RIM Based This feature allows E-UTRAN to provide cell
s LTE Target Cell Selection load information for UTRAN and assists
UTRAN in selecting appropriate target cells for
handovers from UTRAN to E-UTRAN.
Value
 Coverage-based handover
This feature package ensures data service continuity between E-UTRAN and GERAN,
UTRAN, or CDMA2000 network before E-UTRANs are fully deployed across an
operator's coverage areas and such networks are used to supplement coverage.
 Service-based handover
In multi-network co-coverage scenarios, this feature package allows services to be
preferentially established on a frequency based on inter-RAT handover policies that
operators configure for services with different QCIs to achieve service steering.
 Distance-based handover
This feature package hands over UEs on E-UTRAN experiencing severe overshoot
coverage to another network based on the inter-site distance when the coverage of the
E-UTRAN and the other network overlaps.
 Flexible Policy Configuration
In multi-network co-coverage scenarios, this feature package hands over UEs to a
PLMN- or frequency-specific inter-RAT cell based on service types and candidate cell
characteristics.
 Others
In multi-network co-coverage scenarios, this feature package assists other networks in
increasing their inter-RAT handover success rate.
2.2.12.1 LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and

UTRAN
Availability
This feature is

Summary
PS Inter-RAT Mobility between E-UTRAN and UTRAN provides the function of Inter-RAT
cell selection and reselection between E-UTRAN and UTRAN, and the function that the UEs
can be handed over to an Inter-RAT UTRAN cell for the reason of limited cell coverage. If the
PS handover is not supported by the current networks, the PS redirection between E-UTRAN
and UTRAN is used to realize the Inter-RAT mobility. Moreover, the blind handover is
provided if Inter-RAT measurements may be skipped (to save time and resources) or can be
unavailable.
PS handover between E-UTRAN and UTRAN also supports the function that the UEs can be
handed over to an Inter-RAT UTRAN cell when there is uplink coverage restriction on
E-UTRAN.
PS handover based on uplink power is supported. When UE's service QoS is limited in uplink,
eNodeB can trigger an Inter-RAT handover to UTRAN to guarantee the service QoS.
Benefits
The feature provides the following benefits:
 Enables the seamless mobility between E-UTRAN and UTRAN
 Guarantees smooth evolution from legacy wireless systems to LTE systems.
 Provides supplementary coverage for E-UTRAN in the early phase using the legacy
wireless systems to prevent call drop, thus, seamless user coverage
 Improves the network performance and end user experience
Description
1. PS Handover between E-UTRAN and UTRAN
Handover between E-UTRAN and UTRAN is a critical feature to allow seamless
co-existence and a smooth evolution from the legacy wireless communication systems to
LTE system. It is one type of inter-Radio Access Technology (RAT) handover. It exists in
the early E-UTRAN deployment when a UE moves to an area where E-UTRAN does not
have coverage while UTRAN has.
In Huawei eNodeB, handover is based on the coverage triggered by evaluating the cells'
DL reference signals that can be RSRP (Reference Signal Received Power), RSRQ
(Reference Signal Received Quality) of E-UTRAN, and Received Signal Code Power
(RSCP) or Ec/N0 of UTRAN .
When a UE moves out of the area of E-UTRAN, the eNodeB decides whether to
handover it from E-UTRAN to UTRAN according to its reported measurement. The UE
performs handover to the target UTRAN cell when it receives the handover command
from the source eNodeB.
The Inter-RAT measurement of the target cell is gap-assisted for the UE with only one
RF receiver. In the serving cell, the Inter-RAT measurement is triggered by an event A2
that means the DL reference signal quality of E-UTRAN become worse than the absolute
threshold, and stopped by an event A1 that means the DL reference signal quality of
E-UTRAN becomes better than absolute threshold.
The Inter-RAT handover is triggered by an event B1 that means the Common Pilot
Channel (CPICH), RSCP and/or Ec/N0 of UTRAN cells is better than absolute threshold.
After receiving the measurement report from the UE, the eNodeB decides whether to
hand over it to UTRAN.

Generally speaking, LTE system is limited in uplink. Sometimes, QoS can be guaranteed
in downlink, but in uplink it is not satisfied even UE has transmitted its full power. To
guarantee UE's service QoS in this scenario, Huawei eNodeB supports uplink
transmission power based Inter-RAT handover to UTRAN.
While eNodeB detected UE's QoS is limited, eNodeB will send measurement control
message to UE. When UE reports B1 event to eNodeB, eNodeB decides whether to
handover to UTRAN.
Huawei eNodeB also supports PS handover from UTRAN to E-UTRAN.
In some specific scenario, Inter-RAT measurements may be skipped (to save time and
resources) or can be unavailable. In such a scenario, Huawei eNodeB provides Blind
Handover to realize Inter-RAT handover from E-UTRAN to UTRAN in eRAN2.0. For
example, if an E-UTRAN cell is co-sited with a UTRAN site, and having the same
coverage range, operators can configure the UTRAN cell as the E-UTRAN cell's blind
handover target cell. When handover trigger conditions (load, service) are met, the
eNodeB can handover the UE to the blind handover target cell without Inter-RAT
measurement. Blind handover, compared to PS handover, features more reduced
handover time.
2. PS Redirection between E-UTRAN and UTRAN
If the legacy UTRAN or UEs cannot support PS handover, Huawei eNodeB provides PS
redirection functionality to realize Inter-RAT handover between UTRAN and E-UTRAN
in eRAN2.0. There is no upgrade requirement for legacy UTRAN and UEs to support PS
Redirection.
After a UE accesses a cell, the eNodeB delivers two sets of event A2 configurations. One
is used for triggering measurements, and the other is used for triggering urgent
redirection. The triggering of event A2 for urgent redirection indicates that the signal
quality in the serving cell has become too poor to provide services for the UE.
The procedure of PS redirection is the same as that of RRC connection release procedure
in which the carrier frequency information of the target redirection system will be
included in the RRCConnectionRelease message. After a RRC connection of a UE is
released by the source LTE system, the UE reselects the target system based on the
received carrier frequency information during the release procedure and re-establishes
the connection with the target system. In summary, the handover mechanism of PS
redirection consists of connection release, carrier-frequency re-selection, and connection
re-establishment.
3. Idle Mode Mobility
Note that the above description refers to a UE in active mode mobility. In idle mode
mobility, Cell Selection and Reselection are procedures used for searching a new RAT
serving cell. The UE will continually perform this procedure when it moves. Cell
selection and Reselection for Inter-RAT is usually performed in the following scenarios:
− Cell Selection: Procedure of cell selection is invoked when the UE initially turns on.
The cell of which technology is selected by the UE is based on the priority setting.
− E-UTRAN to UTRAN Cell Reselection: The UE has initially camped on the LTE
cell. When the UE moves out of E-UTRAN coverage, the UE needs to reselect
UTRAN if available.
− UTRAN to E-UTRAN Cell Reselection: The UE has camped initially on a UTRAN
cell. When the UE enters a cell of E-UTRAN coverage, and if E-UTRAN is
configured with higher priority, the UE will reselect E-UTRAN. The priority
information is broadcasted in cell system information.
When camping on a cell, the UE regularly searches for a better cell according to the cell
reselection criteria. If a better cell is found, that cell is selected.

Enhancement
 In eRAN2.0
PS Redirection and Blind Handover between E-UTRAN and UTRAN are supported.
 In eRAN2.1
The Handover based on UL power is supported. It guarantees service continuity in
uplink limited power or limited E-UTRAN coverage when a UE moves to the cell edge.
 In eRAN2.2,
 In eRAN6.0
Blind redirections from E-UTRAN to UTRAN can be performed as long as the UTRAN
frequency information is configured. This enhancement simplifies the neighboring cell
configurations at the early stage of network construction and reduces the operation and
maintenance (OM) cost. This enhancement applies only during the early stage of
network construction. After neighbor relationships (including blind handover priorities)
are configured, redirections should be performed normally, based on the complete
neighbor relationship configurations rather than the frequency information configured at
the early stage of network construction. This enhancement can be enabled by specifying
a redirection priority for each UTRAN frequency.
redirects the UE to a neighboring GERAN, UTRAN, or E-UTRAN cell. Note that the
UE is preferentially redirected to a neighboring E-UTRAN cell and is redirected to a
neighboring UTRAN or GERAN cell (according to the configured priorities for the
UTRAN and GERAN) only if there is no neighboring E-UTRAN cell.
Dependency
 CN
Core network should support this function.
 Others
UTRAN should support this function.
2.2.12.2 LOFD-001043 Service based inter-RAT handover to UTRAN
Availability
This feature is
 Applicable to Micro from eRAN3.0

Summary
This feature steers the VoIP service from LTE to UMTS during the service setup phase.
Benefits
This feature utilizes the legacy network resource and improves LTE system capacity while
guaranteeing the service QoS. The feature reduces the possibility of system overload and
decreases the service drop rate.
Description
The eNodeB sends inter-RAT measurement control message to the UE that sets up VoIP
services and instructs the UE to execute the measurement. When receiving event B1 from the
UE, the eNodeB decides whether to set up service in the UMTS based on the RAB QCI
handover strategy.
Enhancement
None
Dependency
 Other features
UTRAN to perform handovers or LOFD-001022 SRVCC to UTRAN.
2.2.12.3 LOFD-001072 Distance based Inter-RAT handover to UTRAN
Availability
This feature is
 Applicable to Macro from eRAN3.0
 Not applicable to Micro
 Not applicable to LampSite
Summary
Huawei LTE eNodeB supports distance-based inter-RAT handover to UTRAN.
Benefits
Better end user experience
Description
When moving away from the serving eNodeB with frequency (such as F1), the UE may still
experience a relatively strong signal from F1 so that the condition of A2 event cannot be
satisfied to trigger an inter-RAT handover to UTRAN, even though the neighboring UTRAN
signal is much better than F1. In this case, a distance-based handover to UTRAN is employed
to achieve best connection.

When distance-based handover algorithm is used, the eNodeB continuously measures the
distance to each UE based on the TA measurement. Once the distance exceeds an
operator-configured distance threshold, inter-RAT gap measurements for neighboring
UTRAN are triggered to find an optimal handover candidate cell to improve service
performance.
Enhancement
None
Dependency
 Other features
UTRAN.
2.2.12.4 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering
Availability
This feature is
 Applicable to Micro from eRAN6.0
Summary
Huawei eNodeB supports the prioritized inter-RAT frequency selection based on the
provisioned CS and/or PS service-type priority during handover from E-UTRAN to UTRAN.
This feature applies to coverage-based or CSFB-triggered E-UTRAN to UTRAN handover.
Benefits
This feature is an enhanced LTE mobility feature by providing a type of flexible prioritized
frequency selection method for E-UTRAN to UTRAN handover, with which, UEs with
different CS and/or PS services can be steered from E-UTRAN to the designated high-priority
frequencies of UTRAN according to the operator's network planning and load-balancing
preferences.
Description
In the event of coverage-based or CSFB-triggered E-UTRAN to UTRAN handovers, the
eNodeB initiates the inter-RAT blind handover process to the UEs incapable of inter-RAT
measurement. Huawei eNodeB can prioritize UTRAN frequencies based on UE's existing
CS-domain or PS-domain service type and each frequency's CS/PS priority configuration, and
then send the UE the highest priority frequency for either blind handover or blind redirection
if the UE does not support inter-RAT handover.
The eNodeB initiates the inter-RAT measurement process to the UEs capable of inter-RAT
measurement. Huawei eNodeB can prioritize UTRAN frequencies based on UE's existing
CS-domain or PS-domain service type and each frequency's CS/PS priority configuration, and
then send the UE the highest priority frequency for measurement.

Enhancement
None
Dependency
 Other features
LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN
LOFD-001033 CS Fallback to UTRAN
2.2.12.5 LOFD-070216 Separate Mobility Policies to UTRAN for Multi

PLMN
Availability
Summary
This feature applies to scenarios where neighboring UTRAN cells of an E-UTRAN cell or
devices in the CN supporting the neighboring UTRAN cells of different operators may not
support the PSHO, RIM, Ultra Flash CSFB, VoIP, or SRVCC in an LTE network.
This feature enables eNodeBs to determine PSHO, RIM, Ultra Flash CSFB, VoIP, or SRVCC
policies based on neighboring UTRAN cells during the interoperability between LTE and
UMTS.
Benefits
This feature reduces dependencies between the PSHO, RIM, Ultra Flash CSFB, VoIP, and
SRVCC functions in RAN sharing scenarios, and enables the configuration of these functions
for some operators or some neighboring UTRAN cells.
Description
eNodeBs determine handover policies based on neighboring UTRAN cells and devices in the
CN supporting a UTRAN cell. In mobility-based handovers from E-UTRAN to UTRAN,
eNodeBs determine handover policies depending on whether a neighboring UTRAN cell or
the CN of the neighboring UTRAN cell supports the PSHO, RIM, Ultra Flash CSFB, VoIP,
and SRVCC.
Enhancement
 eRAN11.1
The function of SRVCC from E-UTRAN to UTRAN for multiple PLMNs is added.
Applicable to
Y Y Y

Dependency
 Base Station
None
 eCO
None
 UE
None
 CN
None
 Other NEs
None
 Other Features
The PS HO function in this feature is dependent on LOFD-001019 PS Inter-RAT
Mobility between E-UTRAN and UTRAN.
The RIM function in this feature is dependent on LOFD-001052 Flash CS Fallback to
UTRAN.
The Ultra Flash CSFB function in this feature is dependent on LOFD-070202
Ultra-Flash CSFB to UTRAN.
The VoIP function in this feature is dependent on the E-UTRAN-to-UTRAN VoIP
function.
The SRVCC function in this feature is dependent on LOFD-001022 SRVCC to UTRAN.
None
 Others
None
2.2.12.6 LOFD-070203 RIM Based LTE Target Cell Selection
Availability
This feature is
Summary
This feature applies to areas jointly covered by UMTS and LTE.
During service- or load-based UMTS-to-LTE handovers or redirections, this feature sends
LTE cell load information to UTMS cells through the RAN information management (RIM)
procedure and the RNC preferentially selects LTE cells or frequencies with low loads as target
cells. By preferentially selecting low-load cells or frequencies, this feature increases the
UMTS-to-LTE handover or redirection success rate and prevents ping-pong inter-RAT
handovers or redirections.

Benefits
 Increases the UMTS-to-LTE handover or redirection success rate
 Prevents ping-pong inter-RAT handovers or redirections
Description
When this feature is not activated, the UTRAN cannot obtain LTE cell load information. In
this case, the RNC performs service- or load-based UMTS-to-LTE handovers or redirections
without considering LTE cell loads. This results in handover preparation failures, increased
signaling overheads, and ping-pong inter-RAT handovers or redirections.
When this feature is activated, the RNC sends LTE cell load queries to the eNodeB through
the RIM procedure. In turn, the eNodeB sends the required cell load information to the RNC
through the RIM procedure. When the loads of the related LTE cells change, the eNodeB
actively informs the RNC of the changes. In this case, the RNC can perform service- or
load-based UMTS-to-LTE handovers or redirections based on LTE cell loads.
Enhancement
None
Dependency
 eNodeB
None
 UE
None
None
 CN
NEs on the CN side must support the RIM procedure that complies with 3GPP Release
9.
 OSS
None
 Other Features
At least one of the following features has been activated on the UTRAN side:
− WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE
− WRFD-140218 Service-Based PS Handover from UMTS to LTE
− WRFD-150216 Load Based PS Redirection from UMTS to LTE
− WRFD-150217 Load Based PS Handover from UMTS to LTE
 Others
The UTRAN can obtain LTE cell load information through the RIM procedure.

2.2.12.7 LOFD-111204 Separate Mobility Policies to GERAN for Multi

PLMN
Availability
Summary
This feature applies to scenarios where neighboring GERAN cells of an E-UTRAN cell or
devices in the CN supporting the neighboring GERAN cells of different operators may not
support the RIM, Ultra Flash CSFB, or SRVCC in an LTE network.
This feature enables eNodeBs to determine RIM, Ultra Flash CSFB, or SRVCC policies based
on neighboring GERAN cells during the interoperability of CS services between LTE and
GSM.
Benefits
This feature reduces dependencies between the Flash CSFB, Ultra Flash CSFB, and SRVCC
functions in RAN sharing scenarios, and enables the configuration of these functions for some
operators or some neighboring GERAN cells.
Description
eNodeBs determine handover policies based on neighboring GERAN cells and devices in the
CN supporting a GERAN cell. In mobility-based handovers from E-UTRAN to GERAN,
eNodeBs determine handover policies depending on whether a neighboring GERAN cell or
the CN of the neighboring GERAN cell supports the RIM, Ultra Flash CSFB, and SRVCC.
Enhancement
None
Applicable to
Y Y Y
Dependency
 Base Station
None
 eCO
None
 UE
None
 CN

None
 Other NEs
None
 Other Features
The RIM function in this feature is dependent on LOFD-001053 Flash CS Fallback to
GERAN.
The Ultra Flash CSFB function in this feature is dependent on LOFD-081283
Ultra-Flash CSFB to GERAN.
The SRVCC function in this feature is dependent on LOFD-001023 SRVCC to GERAN.
None
 Others
None

GERAN
Availability
This feature is
Summary
PS Inter-RAT Mobility between E-UTRAN and GERAN provides the function of Inter-RAT
cell selection and reselection between E-UTRAN and GERAN, and the function that the UE
can handover to an Inter-RAT GERAN cell for the reasons of limited cell coverage. If the PS
handover is not supported by the current network, the PS redirection between E-UTRAN and
GERAN is provided to realize the Inter-RAT mobility. Moreover, the blind handover is
provided if Inter-RAT measurements may be skipped (to save time and resources) or can be
unavailable.
PS handover between E-UTRAN and GERAN supports also the function that the UEs can be
handed over to an Inter-RAT GERAN cell when there is uplink coverage restriction on
E-UTRAN.
PS handover based on uplink power is supported. When UE's service QoS is limited in uplink,
eNodeB can trigger an Inter-RAT handover to GERAN to guarantee the service QoS.
Benefits
The feature provides the following benefits:
 Enables the seamless mobility between E-UTRAN and GERAN
 Guarantees smooth evolution from legacy wireless systems to LTE systems

 Provides supplementary coverage for E-UTRAN in early phase using the legacy wireless
systems to prevent call drop, thus, seamless overage for the UE
 Improves the network performance and end user experience
Description
1. PS handover between E-UTRAN and GERAN
Handover between E-UTRAN and GERAN is a critical feature to allow a seamless
co-existence and a smooth evolution from the legacy wireless communication systems to
LTE systems. It is one type of the Inter-RAT handover. It exists in the early phase of
E-UTRAN when a UE moves into an area where E-UTRAN does not have coverage but
GERAN has.
In Huawei eNodeB, handover is based on the coverage by evaluating the cells' DL
reference signals which can be RSRP, RSRQ of E-UTRA, and carrier Received Signal
Strength Indicator (carrier RSSI) of GSM .
When a UE is moving out of E-UTRAN coverage, the eNodeB can decide whether to
handover it from E-UTRA to GERAN according to its reported measurement. The UE
performs handover to the target GERAN cell after receiving the handover command
from the eNodeB.
The Inter-RAT measurement of the target cell is gap-assisted for UE with one RF
receiver. In the serving cell, the Inter-RAT measurement is triggered by an event A2 that
means the quality of E-UTRAN DL reference signal becomes worse than the absolute
threshold, and stopped by an event A1 that means the quality of E-UTRAN DL reference
signal is better than absolute threshold.
The Inter-RAT handover is triggered by an event B1 that means the carrier RSSI of GSM
becomes better than absolute threshold. After receiving the measurement report from UE,
the eNodeB decides to hand over the UE to GERAN.
Generally speaking, LTE system is limited in uplink. Sometimes, QoS can be guaranteed
in downlink, but in uplink it is not satisfied even UE has transmitted its full power. To
guarantee UE's service QoS in this scenario, Huawei eNodeB supports uplink
transmission power based Inter-RAT handover to GERAN.
While eNodeB detected UE's QoS is limited, eNodeB will send measurement control
message to UE. When UE reports B1 event to eNodeB, eNodeB decides whether to
handover to GERAN.
Huawei eNodeB also supports the PS handover between GERAN and E-UTRAN. In
addition to PS handover, Huawei eNodeB also supports Cell Change Order (CCO) with
or without NACC (Network Assisted Cell Change).
In some specific scenario, Inter-RAT measurements may be omitted (to save time and
resources) or can be unavailable. In such a scenario, Huawei eNodeB provides Blind
Handover solution to realize Inter-RAT handover from E-UTRAN to GERAN. For
example, if an E-UTRAN cell is co-sited with a GERAN cell, and having the same
coverage range, operators can configure the GERAN cell as the E-UTRAN cell's blind
handover target cell. When handover trigger condition (load, service) is met, the eNodeB
can handover the UE to the blind handover target cell without Inter-RAT measurement.
Blind handover, compared to PS handover, features more reduced handover time.
2. PS redirection between GERAN and E-UTRAN
If the legacy GERAN networks or UEs cannot support PS handover, Huawei eNodeB
provides PS redirection functionality to realize Inter-RAT handover between GERAN
and E-UTRAN. There is no update requirement for legacy GERAN networks and UEs to
support PS Redirection.

After a UE accesses a cell, the eNodeB delivers two sets of event A2 configurations. One
is used for triggering measurements, and the other is used for triggering urgent
redirection. The triggering of event A2 for urgent redirection indicates that the signal
quality in the serving cell has become too poor to provide services for the UE.
The procedure of PS redirection is the same as that of RRC connection release procedure
in which the carrier frequency information of the target redirection system will be
included in the RRCConnectionRelease message. After a RRC connection of a UE is
released by the source system, the UE reselects to the target system based on the
received carrier frequency information during the release procedure and re-establishes
the connection with the target system. In summary, the handover mechanism of PS
redirection consists of connection release, carrier frequency re-selection, and connection
re-establishment.
3. Idle Mode Mobility
Note that the above description refers to a UE in active mode mobility. In idle mode
mobility, Cell Selection and Reselection are procedures used for searching a new serving
cell. The UE will continually perform this procedure when it moves. Cell selection and
reselection for Inter-RAT is usually performed in the following scenarios:
− Cell Selection: procedure of cell selection is invoked when the UE initially turns on.
the cell of which technology is selected by the UE is based on the priority setting.
− E-UTRAN to GERAN Cell Reselection: the UE has initially camped on the LTE
cell. When the UE moves out of E-UTRAN coverage, the UE needs to reselect
GERAN if available.
− GERAN to E-UTRAN Cell Reselection: the UE has camped initially on a GERAN
cell. When the UE enters a cell of E-UTRAN coverage, and if E-UTRAN is
configured with higher priority, the UE will reselect E-UTRAN. The priority
information is broadcasted in cell system information.
When camping on a cell, the UE regularly searches for a better cell according to the cell
reselection criteria. If a better cell is found, that cell is selected.
Enhancement
 In eRAN2.0
PS Redirection and Blind Handover between E-UTRAN and GERAN are supported.
 In eRAN2.1
The Handover based on UL power is supported. It guarantees service continuity in
uplink limited power or limited E-UTRAN coverage when a UE moves to the cell edge.
 In eRAN2.2
 In eRAN6.0
Blind redirections from E-UTRAN to GERAN can be performed as long as the GERAN
frequency information is configured. This enhancement simplifies the neighboring cell
configurations at the early stage of network construction and reduces the operation and
maintenance (OM) cost.This enhancement applies only during the early stage of network
construction. After neighbor relationships (including blind handover priorities) are
configured, redirections should be performed normally, based on the complete neighbor
relationship configurations rather than the frequency information configured at the early

stage of network construction. This enhancement can be enabled by specifying a

redirection priority for each GERAN frequency.
redirects the UE to a neighboring GERAN, UTRAN, or E-UTRAN cell. Note that the
UE is preferentially redirected to a neighboring E-UTRAN cell and is redirected to a
neighboring UTRAN or GERAN cell (according to the configured priorities for the
UTRAN and GERAN) only if there is no neighboring E-UTRAN cell.
Dependency
 CN
Core network should support this function.
 Others
GERAN should support this function.
2.2.12.9 LOFD-001046 Service based inter-RAT handover to GERAN
Availability
This feature is
Summary
It is to steer the VOIP service to GERAN and LTE system support PS service during the
service setup phase.
Benefits
It can utilize the legacy network resource and improve LTE system capacity at the same time
that it can guarantee the service QoS. It can reduce the possibility of system overload and
decrease the service dropping rate.
Description
LTE system sends inter-system measurement control message to UE which want to set up
VOIP service and notices it to execute the measurement. When UE reports B1 event to
eNodeB, eNodeB decides whether to setup service in the GERAN based on ERAB (EPS RAB)
QCI handover strategy
Enhancement
None

Dependency
 Other features
LOFD-001023 SRVCC to GERAN
2.2.12.10 LOFD-001073 Distance based Inter-RAT handover to GERAN
Availability
This feature is
 Not applicable to Micro
 Not applicable to LampSite
Benefits
Better end user experience
Description
When moving away from the serving eNodeB with frequency (such as F1), the UE may still
experience a relatively strong signal from F1 so that the condition of A2 event cannot be
satisfied to trigger an inter-RAT handover to GERAN, even though the neighboring GERAN
signal is much better than F1. In this case, a distance-based handover to GERAN is employed
to achieve best connection.
When distance-based handover algorithm is used, the eNodeB continuously measures the
distance to each UE based on the TA measurement. Once the distance exceeds an
operator-configured distance threshold, inter-RAT gap measurements for neighboring
GERAN are triggered to find an optimal handover candidate cell to improve service
performance.
Enhancement
None
Dependency
 Other features
GERAN.

CDMA2000
Availability
This feature is:

Summary
This feature provides the functions of inter-RAT cell reselection between E-UTRAN and
CDMA2000 HRPD and handovers from E-UTRAN to CDMA2000 HRPD. It includes the
following functions:
 Cell reselection between E-UTRAN and CDMA2000 HRPD
 Non-optimized handover from E-UTRAN to CDMA2000 HRPD
This function includes the following subfunctions:
− Blind redirection from E-UTRAN to CDMA2000 HRPD
− Inter-system measurement-based (including B1 or B2 measurement event)
redirection from E-UTRAN to CDMA2000 HRPD
 Optimized handover from E-UTRAN to CDMA2000 HRPD
Benefits
 Seamless integration of E-UTRAN and CDMA2000 HRPD
 Smooth evolution from CDMA2000 HRPD to E-UTRAN
 Supplementing E-UTRAN coverage with CDMA2000 HRPD in E-UTRAN early phase
to achieve seamless coverage. This improves network performance and user experience.
Description
This feature is applicable when UEs move from E-UTRAN coverage areas to CDMA2000
HRPD coverage areas in the early phase of E-UTRAN networks. With this feature defined in
3GPP TS 23.402, Huawei eNodeBs can allow UEs to perform E-UTRAN-to-CDMA2000
HRPD idle mode reselection, non-optimized handovers, and optimized handovers.
 Cell reselection between E-UTRAN and CDMA2000 HRPD
An eNodeB broadcasts information about neighboring CDMA2000 HRPD cells in an
SIB8. When a UE in the idle state moves out of an E-UTRAN coverage area, it selects a
CDMA2000 HRPD network based on the information about neighboring CDMA2000
HRPD cells in an SIB8. When a UE moves from a CDMA2000 HRPD coverage area to
an E-UTRAN coverage area, the eNodeB allows the UE to reselect an E-UTRAN
network from the CDMA2000 HRPD network.
 E-UTRAN-to-CDMA2000 HRPD non-optimized handover
UEs camping on an E-UTRAN network do not pre-register with a CDMA2000 HRPD
network. When a UE in the active state moves out of an E-UTRAN coverage area, the
eNodeB determines to redirect the UE from E-UTRAN to CDMA2000 HRPD through
blind redirection or measurement-based to redirection.
 E-UTRAN-to-CDMA2000 HRPD optimized handover
UEs camping on an E-UTRAN network pre-register with a CDMA2000 HRPD network.
When a UE in the active state moves out of an E-UTRAN coverage area, the eNodeB
requests cell resources from the target CDMA2000 HRPD network based on UE's
measurement results. The eNodeB sends a handover command to the UE upon receiving
a cell resource allocation response. The command contains the information about the
CDMA2000 HRPD cell resources. The UE hands over the UE to the target CDMA2000
HRPD cell upon receiving the handover command.

UEs with only one RF receiver perform inter-RAT cell measurement based on the GAP
measurement. In serving cells, UEs start inter-RAT measurement when event A2 occurs and
stop inter-RAT measurement when event A1 occurs. Event A2 indicates that the quality of
E-UTRAN downlink reference signals is lower than an absolute threshold, and event A1
indicates that the quality of E-UTRAN downlink reference signals is higher than an absolute
threshold.
Inter-RAT handover parameters can be set for respective services.
Enhancement
 eRAN8.1
This feature supports inter-system measurement-based redirection from E-UTRAN to
CDMA2000 HRPD.
Dependency
 eNodeB
None
 eCO
None
 UE
None
None
 CN
Core networks should support this feature.
 OSS
None
 Other Features
None
 Others
CDMA2000 HRPD should support this feature.
2.2.12.12 LOFD-001111 PS Mobility from E-UTRAN to CDMA2000 HRPD

Based on Frequency-specific Factors
Availability
This feature is

Summary
Using this feature, the eNodeB can redirect E-UTRAN UEs to an operator's CDMA2000 High
Rate Packet Data (HRPD) frequencies (in one or multiple band classes), based on the
specified factors for these frequencies during redirection.
Benefits
The factors specified for CDMA2000 HRPD frequencies are used to balance the loads on
these frequencies during redirection.
Description
An operator owning multiple CDMA2000 HRPD frequencies can set a redirection factor for
each CDMA2000 HRPD frequency. Based on these factors, the eNodeB determines the target
CDMA2000 HRPD band class for redirection.
The operator can specify the redirection factors for CDMA2000 HRPD frequencies, based on
their respective loads. For example, an operator has two CDMA2000 HRPD bands: 800 MHz
and 2.1 GHz. Generally, frequencies in the 800 MHz band are more heavily loaded than those
in the 2.1 GHz band. To balance the loads between the two bands, the operator sets the factors
for frequencies in the 800 MHz band to smaller values than those for frequencies in the 2.1
GHz band.
The following figure illustrates another example. In this situation, CDMA2000 HRPD
frequencies 1, 2, and 3 are assigned factors 0.7, 1, and 1, respectively. Then the number of
UEs that fall back to frequencies 1, 2, and 3 will meet the following condition:
Number of UEs on frequency 1:Number of UEs on frequency 2:Number of UEs on frequency
3 = 0.7:1:1
Figure 2-19 Redirection from E-UTRAN to CDMA2000 HRPD based on factors for frequencies

Enhancement
None
Dependency
 Other features
This feature requires LOFD-001021 PS Mobility from E-UTRAN to CDMA.
2.2.13 Multi-carrier Load Management

Overview
Features related to Multi-carrier Load Management redistribute the UEs on the network to
achieve the following goals:
 Reducing the differences between UE-perceived data rates in different carriers in the
network.
 Reducing the load of local cells to below a certain target.
Applications
Multi-carrier Load Management was introduced for LTE multi-band and multi-carrier
scenarios. Multi-carrier Load Management balances the UE-perceived data rates on different
carriers in an LTE network in the applications listed in the following table. The following
table lists the features in the package and their applications.

ion
UEs are LOFD-070215 This feature balances loads among carriers, based
static or Intra-LTE User on the number of UEs or differences in the
move at Number Load UE-perceived downlink data rate. This feature aims
low Balancing to equalize differences in UE distribution and in UE
speeds. experience.
LOFD-001032 This feature balances loads between carriers, based
Intra-LTE Load on their PRB usages. This feature aims to equalize
Balancing differences in PRB usage.
LOFD-081227 This feature is an enhanced version of
Intra-LTE Load LOFD-070215 Intra-LTE User Number Load
Balancing for Balancing and LOFD-001032 Intra-LTE Load
Non-cosited Cells Balancing in non-cosited scenarios.
LOFD-121201 This feature helps select the optimal air interface
Multi-band Optimal bearer for an UE in RRC_CONNECTED mode.
Carrier Selection
UEs User-number-based This feature transfers UEs in fixed proportions
move at load balancing in fixed among inter-frequency carriers.
high proportions
speeds.

In applications listed in the following table, Multi-carrier Load Management reduces the load
of a local cell to below a certain target.

n
UEs are LOFD-070215 This feature transfers UEs away from a local cell
static or Intra-LTE User based on the number of UEs there are when the
move at low Number Load system is overloaded.
speeds. Balancing
LOFD-001032 This feature transfers UEs away from a local cell
Intra-LTE Load based on the PRB usage when the system is
Balancing overloaded.
LOFD-081227 This feature is an enhanced version of
Intra-LTE Load LOFD-070215 Intra-LTE User Number Load
Balancing for Balancing and LOFD-001032 Intra-LTE Load
Non-cosited Cells Balancing in non-cosited scenarios.
E-UTRAN LOFD-001044 This feature transfers UEs to a UTRAN when
and UTRAN Inter-RAT Load the E-UTRAN is in the high-load state.
co-coverage Sharing to UTRAN
E-UTRAN LOFD-001045 This feature transfers UEs to a GERAN when
and GERAN Inter-RAT Load the E-UTRAN is in the high-load state.
co-coverage Sharing to GERAN
Value
Multi-carrier Load Management reduces the differences between UE-perceived data rate
differences in different carriers and improves average downlink UE throughput in the entire
network. The throughput increase can be 5% or more.
Impact factors:
 Load difference
The greater the load difference among different carriers, the more the average
UE-perceived data rate will increase.
 CA UE penetration rate
CA UEs can use the air interface resources of multiple carriers simultaneously. Gains
from this feature package become smaller as the penetration rate of CA UEs increases.
Multi-carrier Load Management balances the loads of local cells to reduce the load of
individual cell below a specified target. This decreases the possibility of overload-induced cell
congestion. If all the cells on the entire network are highly loaded, however, Multi-carrier
Load Management may not be able to achieve this goal.
2.2.13.1 LOFD-001032 Intra-LTE Load Balancing
Availability
This feature is:


Summary
This feature resolves load imbalances between a cell and its inter-frequency neighboring cells.
Benefits
This feature achieves better utilization of network resources, increasing system capacity,
whilst it reducing the probability of system overload and increasing access success rates.
Description
Intra-LTE Load Balancing is recommended in commercial LTE networks with multiple LTE
frequencies where one frequency has a higher load but other frequencies have a lower load.
A local cell is responsible for measuring its local cell load after this feature is enabled. If the
local cell load exceeds a preset threshold, the eNodeB serving the local cell will collect
neighboring cell load information. If a neighboring cell's load is lower than a threshold, the
eNodeB evaluates whether to hand over UEs to the neighboring cell.
The cell load is represented by the physical resource block (PRB) usage.
The mobility load balancing (MLB) procedure consists of the following activities: load
measurement and evaluation, load information exchange, load balancing decision, load
balancing execution and performance monitoring.
MLB without load information exchange is applicable to scenarios where no X2 interface is
available or the X2 interface does not support load information exchange.
Enhancement
 eRAN7.0
Frequency-priority-based MLB is supported.
MLB without load information exchange is applicable to scenarios where no X2
interface is available or the X2 interface does not support load information exchange.
 eRAN11.1
UEs that can be selected or not selected based on QCIs for MLB, are configurable on
eNodeBs.
Frequencies that can be selected as target frequencies based on QCIs are configurable on
eNodeBs.
Dependency
None
2.2.13.2 LOFD-070215 Intra-LTE User Number Load Balancing
Availability
This feature is:


Summary
This feature balances user number-based loads among cells and frequencies within an LTE
network.
Benefits
This feature better uses network resources and balances user number-based loads to reduce
the probability of burst traffic and to balance control-channel resource loads among cells.
Description
Intra-LTE User Number Load Balancing contains connected mode and idle mode. This feature
is recommended in commercial LTE networks with multiple LTE frequencies where one
frequency has a higher user number but other frequencies have lower user numbers.
For connected mode, a serving eNodeB measures the number of the serving cell. If the
number exceeds a preset threshold, the serving cell will send a request to the neighboring cells,
which shall authorize or reject handover determined by individual user number load.
For idle mode, UEs in a normal RRC release procedure can be released to different
frequencies on configured proportions, by using Dedicated Priority included in the RRC
Connection Release message. This function can precisely distribute UEs in idle mode to
different frequencies as operators wish.
MLB without load information exchange is applicable to scenarios where no X2 interface is
available or the X2 interface does not support load information exchange.
Intra-LTE User Number Load Balancing is used in scenarios where inter-frequency LTE cells
have considerable coverage overlap.
Enhancement
 eRAN11.1
Whether UEs can be selected or not for MLB based on QCIs and whether UEs are
preferentially selected are configurable on eNodeBs.
Frequencies that can be selected as target frequencies based on QCIs are configurable on
eNodeBs.
The eNodeB supports load evaluation based on spectrum efficiency, so that
high-spectrum-efficiency cells can serve more UEs.
The eNodeB supports SNR-based UE selection, decreasing the possibility of UE
performance deterioration after load transfer.
The eNodeB supports load transfer of CA UEs and target cell selection based on band
combination capability of CA UEs and the eNodeB.
The eNodeB supports enhanced cell-reselection priority control to prevent RRC-released
UEs from being transferred to high-load cells after load transfer.
 eRAN12.1

The uplink traffic volume-based user selection function is supported in eRAN12.1. This
function is recommended in the FDD and TDD co-coverage network. UEs with a large
traffic volume are not selected for the TDD frequency.
Dependency
None
2.2.13.3 LOFD-001044 Inter-RAT Load Sharing to UTRAN
Availability
This feature is:
Summary
In an LTE and UMTS co-coverage scenario, this feature can transfer load from an E-TURAN
cell to neighboring UTRAN cells when the load status of the E-UTRAN cell is high.
Benefits
This feature utilizes LTE and UMTS network resources. It reduces the probability of system
overload and increases the access success rate. This feature is based on UE capability and
target cell load.
Description
In a commercial LTE network, LTE cells have high load because of the characteristics of UE
services. In this situation, MLB is triggered to share traffic load to UMTS.
An LTE cell measures and evaluates its cell load. Then it decides whether to transfer some
UEs to neighboring UTRAN cells. The triggering variable of inter-RAT MLB can be the PRB
usage, number of UEs, or either of them. If the triggering variable is PRB usage, an eNodeB
triggers PRB-usage-based MLB to UTRAN when the PRB usage of a cell and the number of
RRC_CONNECTED UEs in the cell meet certain conditions. In this case, the eNodeB
transfers some RRC_CONNECTED UEs and idle UEs to neighboring UTRAN cells through
handover and redirection, respectively. A UE in the RRC connection release procedure is
regarded as an idle UE. If the triggering variable is the number of UEs, an eNodeB triggers
user-number-based MLB to UTRAN when the number of RRC_CONNECTED UEs in a cell
meets certain conditions. In this case, the eNodeB transfers some RRC_CONNECTED UEs
to neighboring UTRAN cells through handover. If the triggering variable is either the PRB
usage or the number of UEs, the eNodeB triggers the corresponding type of MLB to UTRAN
when the PRB usage or the number of UEs meets certain conditions.
The MLB to UTRAN procedure includes the following steps: load measurement and
evaluation, load balance triggering, load information exchange (optional), target
cell/frequency selection, UE selection, dedicated cell-reselection priority update (optional),
and load transfer.
This feature is used in the LTE and UMTS co-coverage scenarios.

Enhancement
 eRAN2.1
The Inter-RAT Load Sharing to UTRAN feature is enhanced with the following
administration function:
Operators can enable or disable the MLB to UTRAN.
 eRAN3.0
This feature supports the transfer of RRC_IDLE UEs. When the number of UEs in an
LTE cell and the PRB usage of an LTE cell are both higher than the thresholds, eNodeB
will select some UEs in normal RRC Release procedure to re-select and camp on UMTS,
by using dedicated cell-reselection priority contained the RRC Connection Release
message.
 eRAN7.0
Frequency-priority-based MLB is supported.
 eRAN8.1
User-number-based MLB to UTRAN is now supported. In a scenario where the number
of UEs in a cell is large but the PRB usage of a cell is small, user-number-based MLB
can be triggered when the number of RRC_CONNECTED UEs in the cell meets certain
conditions.
Dependency
 eNodeB
None
 UE
None
None
 Core network
None
 OSS
None
 Other features
This feature requires the LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and
UTRAN feature.
 Others
None
2.2.13.4 LOFD-001045 Inter-RAT Load Sharing to GERAN
Availability
This feature is

Summary
This feature applies when E-UTRAN and GERAN have the same coverage area and
E-UTRAN is highly loaded.
Benefits
This feature increases resource usage, provides QoS guarantee, reduces the probability of
system overload, and decreases service drop rates.
Description
When an E-UTRAN cell is highly loaded, this feature is triggered to transfer traffic load to
GERAN cells.
The E-UTRAN cell measures and evaluates cell loads. Then, it decides whether to hand over
some UEs to neighboring cells. If the E-UTRAN cell load is higher than a predefined
threshold, load balancing is triggered. The cell load is represented by the PRB usage
according to 3GPP TS 36.314.
This feature applies only to UEs in connected mode. The load balancing procedure includes
the following phases: load measurement and evaluation, triggering of load balancing,
selection of candidate UEs, and handover execution.
This feature requires that E-UTRAN and GERAN have the same coverage area.
Enhancement
 In eRAN2.1,
This feature can be enabled or disabled by users.
Dependency
 Other features
GERAN.
2.2.13.5 LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells
Availability
This feature is
Summary
This feature provides the following two functions:
 Event-A2-triggered frequency-priority-based inter-frequency handovers
 Event-A5-triggered load-based inter-frequency handovers

Benefits
This feature brings the following benefits to improve the inter-frequency mobility load
balancing (MLB) performance in non-cosited scenarios:
 Increases the peak throughput of UEs in lightly loaded cells
 Improves the spectral efficiency
Description
This feature provides the following two functions:
 Event-A2-triggered frequency-priority-based inter-frequency handovers
When a UE initially accesses a cell, a UE is handed over to the cell, or the RRC
connection of the UE is reestablished to the cell, the eNodeB delivers A2-related
measurement configuration to the UE. When the UE reports event A2 and
PRB-usage-based inter-frequency MLB or user-number-based inter-frequency MLB is
not triggered in the target cell of a frequency-priority-based handover, the eNodeB
performs a handover and transfers this UE to this cell.
In scenarios where inter-frequency neighboring cells that are configured with different
bandwidths are located in different sites, cells with smaller bandwidths can choose cells
with larger bandwidths as target cells for frequency-priority-based handovers. When the
cell load is light, UEs that are not located in the site center of small-bandwidth cells can
be handed over to large-bandwidth cells, improving the peak throughput of UEs.
 Event-A5-triggered load-based inter-frequency handovers
PRB-usage-based inter-frequency MLB and user-number-based inter-frequency MLB
supports frequency-specific measurement configurations for event A4 or A5 that triggers
load-based inter-frequency handovers. In scenarios where inter-frequency neighboring
cells are not located in the same site, the eNodeB initiates handovers based on event A5.
In this way, UEs that are not located in the site center are selected for MLB, improving
the Uu interface performance of UEs after MLB and the spectral efficiency.
Enhancement
None
Dependency
 Other features
LOFD-001032 Intra-LTE Load Balancing
LOFD-070215 Intra-LTE User Number Load Balancing
2.2.13.6 LOFD-121201 Multi-band Optimal Carrier Selection
Availability
This feature is:

Summary
This feature fast detects UEs with data transmission in a cell and selects better carriers for the
UEs.
Benefits
This feature increases network resource efficiency and user-perceived data rates.
Description
An eNodeB fast detects UEs with data transmission in a cell and instructs the UEs to perform
inter-frequency measurements. After receiving a report from a UE, the eNodeB evaluates the
signal quality, bandwidths, and load of the inter-frequency neighboring cells included in the
report. The eNodeB then selects one of these cells as the serving cell for the UE. This cell will
serve the UE better.
Enhancement
None
Dependency
 eNodeB
The eNodeB must be equipped with a UMPTb or UMPTe board.
2.2.14 Spectrum & Site Management

Overview
LTE specifications define six standard frequency bandwidths: 1.4 MHz, 3 MHz, 5 MHz, 10
MHz, 15 MHz, and 20 MHz. However, in some countries, operators may acquire
non-standard bandwidths. The evolution of GSM/UMTS networks to LTE networks means
that GSM and UMTS spectrum resources are gradually being released. Generally, some or all
even all of the GSM 900 MHz spectrum is allocated to LTE networks. In such a case,
non-standard LTE bandwidths may be used. In addition, network coverage and capacity
expansion have been driving demand for large CPRI bandwidths for transmitting I/Q data on
CPRI ports, and CPRI resources are limited.
The Spectrum & Site management feature package:
 Deploys LTE networks using non-standard LTE bandwidths, helping operators meet LTE
network deployment requirements and improve network spectral efficiency.
 Compresses the I/Q bit width and lowers the sampling rate to reduce the amount of CPRI
bandwidth required so that more carriers; or RRUs, RFUs, or pRRUs can be supported
on each CPRI port.
Applications
The Spectrum & Site management feature package is used in the following scenarios:
 LTE network deployment of non-standard LTE bandwidths
 Insufficient CPRI bandwidth

The following table describes features deployed in different scenarios.
Applicati Feature Description

on
GSM/CD LOFD-001051 This feature provides 12 different methods for
MA Compact deploying LTE networks using non-standard LTE
spectrum Bandwidth bandwidths when non-standard LTE bandwidth
refarming spectrum has been released from CDMA or GSM
for LTE network. The Compact Bandwidth feature does this by
network reducing guard bandwidths (using stringent filtering)
deploymen and effective bandwidths (using physical channel
t resource management).
LOFD-001093 This feature helps manage physical resources when
PUCCH Flexible non-standard LTE bandwidths are used. When the
Configuration PUCCH experiences severe interference due to
inter-RAT signal leakage, the access performance
deteriorates, and the downlink throughput decreases.
This feature allows flexible PUCCH configuration, used
to decrease interference and improve access
performance. In addition, the bandwidth originally
allocated to the PUCCH can be reallocated to transmit
uplink data, offsetting the decrease in PUSCH
throughput.
Zero LOFD-111205 During CDMA-to-LTE evolution, a bufferzone is
bufferzone CDMA and LTE planned for overlapping LTE and CDMA areas to
for CDMA Zero Bufferzone eliminate CDMA and LTE co-channel interference
and LTE (LTE FDD) (CCI). With this feature enabled, the bufferzone is not
network required. LTE cells can be configured in overlapping
deploymen areas of single-frequency networks, improving spectral
t efficiency.
Non-standa LEOFD-111302 During refarming or when non-standard LTE
rd LTE Flexible bandwidths are used, this feature establishes overlapped
bandwidth Bandwidth based deployment of pairs of independent LTE cells, using
on Overlap standard bandwidths. These cell pairs are then combined
Carriers into cell groups, so that the non-standard LTE
bandwidth can still be used.
Insufficient LOFD-001076 This feature compresses I/Q bit width and lowers the
CPRI CPRI sampling rate to reduce the amount of CPRI bandwidth
bandwidth Compression required so that more carriers; RRUs, RFUs, or pRRUs
can be supported on each CPRI port.
Value
 Network deployment on non-standard LTE bandwidths during GSM/CDMA refarming
During GSM/CDMA refarming, the following non-standard LTE bandwidths can be used
to deploy LTE networks:
− 1.2 MHz to 1.3 MHz


− 14.6 MHz to 14.9 MHz
− 18.3 MHz to 18.5 MHz
− 18.6 MHz to 18.9 MHz
− 19 MHz to 19.2 MHz
− 19.3 MHz to 19.9 MHz
During GSM refarming, the following non-standard LTE bandwidths are provided:
 Zero bufferzone for CDMA and LTE single-frequency network deployment
LTE networks can be deployed in the original bufferzone areas for CDMA and LTE
single-frequency networks. This way, no bufferzone is required, improving spectral
efficiency.
 Network deployment on non-standard LTE bandwidths
This feature package combines pairs of standard LTE cells to create cell groups, so that
non-standard LTE bandwidth can still be used for cell deployment. The recommended
combinations of overlapping cells that can be deployed for various non-standard
bandwidths are as follows:
Bandwidth Cell Combination

2.6 MHz 1.4 MHz + 1.4 MHz
4 MHz 3 MHz + 1.4 MHz
5.7 MHz 3 MHz + 3 MHz
10.8 MHz 10 MHz + 1.4 MHz
12.2 MHz 10 MHz + 3 MHz
12.5 MHz 10 MHz + 3 MHz
17.1 MHz 15 MHz + 3 MHz
17.4 MHz 15 MHz + 3 MHz
23.9 MHz 20 MHz + 5 MHz
27.6 MHz 20 MHz + 10 MHz
28.5 MHz 20 MHz + 10 MHz

 CPRI compression
CPRI compression is used when CPRI bandwidth is insufficient. For any given amount
of CPRI bandwidth, CPRI compression:
− Improves carrier or RRU/RFU/pRRU specifications.
− Reduces the number of CPRI Ethernet cables (only for LampSite eNodeBs) or
CPRI optical cables needed for site installation.
2.2.14.1 LOFD-001051 Compact Bandwidth
Availability
This feature is:
Summary
Huawei eNodeB supports the Compact Bandwidth feature. With this feature, operators can
perform strict filtering and compress RBs to maximize wireless bandwidth resources and
deploy LTE systems under non-standard bandwidths. Compared with LTE standard
bandwidths, non-standard bandwidths improve user experience.
Benefits
 Saves frequency resources by fully using non-standard bandwidths.
 Increases the service rate and total cell throughput and improves user experience by fully
using non-standard bandwidths, in comparison with standard bandwidths under the same
bandwidth condition.
 Supports compatibility with terminals of R8 or later because this feature is fully
transparent to UEs.
Description
The following table lists non-standard bandwidths supported by this feature.
Table 2-2 Non-standard bandwidths supported by this feature
Non-stan Non-standard Number of Standard Bandwidth

dard Bandwidth Range Available RBs Range (MHz)
Bandwidt (MHz)
h
Scenario
1 1.2-1.3 6 1.4
2 4.4-4.7 23 5
3 4.8-4.9 25 5

Non-stan Non-standard Number of Standard Bandwidth

dard Bandwidth Range Available RBs Range (MHz)
Bandwidt (MHz)
h
Scenario
4 8.8 46 10
5 8.9-9.1 46 10
6 9.2-9.5 48 10
7 9.6-9.9 50 10
8 14.6-14.9 75 15
9 18.3-18.5 94 20
10 18.6-18.9 96 20
11 19-19.2 98 20
12 19.3-19.9 100 20
Enhancement
eRAN12.1 supports 8.8 MHz.
Dependency
 eNodeB
This feature applies to eNodeB using 450 MHz or 1800 MHz bands. The detailed
requirements are as follows:
− eNodeB using the 1800 MHz band
The RRU3959 can be used in non-standard bandwidth scenarios 2, 3, 4, 6, and 10.
The RRU3953w and MRFUdw V6 can be used in non-standard bandwidth
scenarios 2 and 3.
The MRFUd V6 can be used in non-standard bandwidth scenario 2.
The MRFUd, RRU3928, RRU3929, and RRU3962d can be used in non-standard
bandwidth scenarios 3, 7, 8, 9, 10, 11, and 12.
The AAU3940 can be used in non-standard bandwidth scenarios 3, 6, 7, 8, 9, 10, 11,
and 12.
The MRFU V6 can be used in non-standard bandwidth scenario 4.
The RRU3939, AAU3920, RRU3953, and RRU3942 can be used in non-standard
bandwidth scenario 6.
The RRU3953 and RRU3971 can be used in non-standard bandwidth scenarios 7
and 12.
The RRU3938 can be used in non-standard bandwidth scenario 10.
− eNodeB using the 450 MHz band
RRU3668 can be used in non-standard bandwidth scenarios 1 and 2.

 eCoordinator
None
 UE
None
None
 Core network
None
 OSS
None
 Other features
This feature is not compatible with any of the following features.
LEOFD-111302 Flexible Bandwidth The Flexible Bandwidth based on

based on Overlap Overlap Carriers feature does not
Carriers support the addition of cells whose
actual bandwidth is within the
following ranges to Double Deck cell
groups: 4.4-4.7 MHz, 8.9-9.2 MHz,
9.3-9.5 MHz, 18.3-18.5 MHz, 18.6-18.9
MHz, and 19-19.2 MHz.
MRFD-111401 GSM and LTE Zero None
Bufferzone
MRFD-090202 GSM and LTE FDD None
Dynamic Spectrum
Sharing (LTE FDD)
LOFD-120203 UL 8-Antenna Receive None
Diversity
 Others
None
2.2.14.2 LOFD-001093 PUCCH Flexible Configuration
Availability
 Available in BTS3911E and BTS3912E as of eRAN11.1.
Summary
This feature enables the PUCCH to occupy RBs allocated to the PUSCH. Similarly, it enables
the PUSCH to occupy RBs allocated to the PUCCH.

Benefits
This feature protects the PUCCH at the edge of a band against interference, thereby
improving the PUCCH coverage and system capacity.
Description
In most cases, the PUCCH is configured at the edge of a band. When the edge band in a cell is
affected by continuous interference, this feature moves the PUCCH to the middle point of the
band, thereby improving the PUCCH coverage and system capacity. However, this feature
results in uplink frequency band fragments and reduces the uplink scheduling efficiency and
peak rate.
This feature is implemented on the eNodeB, and has no requirement on the UE.
Enhancement
None
Dependency
 eNodeB
This feature does not apply to the LBBPc board. This feature applies to the BTS3911E
and BTS3912E.
 Others
This feature does not work with uplink ICIC or frequency modulation.
2.2.14.3 LOFD-111205 CDMA and LTE Zero Bufferzone (LTE FDD)
Availability
This feature is introduced in SRAN11.1.
Summary
This feature limits the uplink PUSCH scheduling and downlink PDSCH scheduling for LTE
cell edge users (CEUs) during CDMA and LTE refarming. This reduces the mutual
interference generated during CDMA and LTE intra-frequency adjacent-site deployment,
making full use of the spectrums in the buffer zone and improving spectral efficiency.
Benefits
The feature benefits lie in that the shared spectrum in the original buffer zone can be used for
LTE deployment, thereby increasing spectral efficiency and LTE system capacity and
This feature lowers the CDMA/LTE buffer zone planning requirements, thereby simplifying
CDMA/LTE refarming and accelerating the network development to LTE.
Assume that there is 10 MHz frequency spectrum, the 5 MHz of which is dedicated to CDMA
and the other 5 MHz is shared by CDMA and LTE. Assume that there is 1 or 2 CDMA shared
carriers. If this solution is not used and LTE deployment is required in the buffer zone, only
the 1.4 or 3 MHz LTE network can be deployed.

If this solution is used, the 5 MHz LTE network can be deployed. Compared with the uplink
and downlink capacity benefits provided by the 1.4 MHz LTE network, those provided by the
5 MHz LTE network are greater than 200% and 110% respectively. Compared with the uplink
and downlink capacity benefits provided by the 3 MHz LTE network, those provided by the 5
MHz LTE network are greater than 45% and 25% respectively.
The preceding benefits assume that all the remaining RB resources can be scheduled. The actual benefits
may have a difference of about 20%.
Description
During the evolution from CDMA to LTE, CDMA and LTE intra-frequency adjacent-site
deployment frequently occurs. If LTE uplink scheduling and downlink scheduling are not
limited, strong mutual interference will be generated between CDMA and LTE. To prevent
intra-frequency interference between CDMA and LTE, the conventional solution is to
geographically deploy intra-frequency guard space on the spectrum shared by CDMA and
LTE, which is called the buffer zone. However, the planning of buffer zone will result in a
waste of frequency spectrum and reduced spectral efficiency.
To reduce intra-frequency interference between CDMA and LTE, the system first checks
whether the LTE UE is a CEU or a cell center user (CCU) based on the related measurement
information of the LTE UE:
 If the system determines that the LTE UE is a CEU, this UE can use the RBs only on the
LTE-dedicated spectrum during PUSCH or PDSCH scheduling.
 If the system determines that the LTE UE is a CCU, PUSCH or PDSCH scheduling of
this UE is not limited.
Figure 2-20 uses a 10 MHz spectrum as an example. The intermediate 5 MHz spectrum is
used to deploy LTE and the remaining spectrum is dedicated to CDMA. The spectrum that
overlaps the spectrum of the adjacent CDMA site is the CDMA/LTE shared spectrum, and the
spectrum that does not overlap the spectrum of the adjacent CDMA site is the LTE-dedicated
spectrum.

Figure 2-20 Working principles of CDMA and LTE Zero Bufferzone (example: 10 MHz
spectrum)
This feature is recommended if there is LTE-dedicated spectrum in the refarming frequency

band and the dedicated spectrum accounts for at least 50%.
Enhancement
None
Applicable to
Y N N
Dependency
 eNodeB
None
 eCoordinator
None
 UE
None
 Core network
None
 Other NEs

None
 Other features
None
LAOFD-081233 Dynamic TDM eICIC
LAOFD-081234 FeICIC
LBFD-002022 Static Inter-Cell Interference Coordination
LBFD-00202202 Uplink Static Inter-Cell Interference Coordination
LOFD-060201 Adaptive Inter-Cell Interference Coordination
LOFD-003029 SFN
LOFD-070205 Adaptive SFN/SDMA
 Others
None
2.2.14.4 LOFD-001076 CPRI Compression
Availability
This feature is:
Summary
This feature reduces the common public radio interface (CPRI) bandwidth required by each
cell.
Benefits
This feature:
 Allows each CPRI port to connect to more cascaded RRUs.
 Reduces the required number of fiber optic cables.
 Reduces investment on eNodeB installation and reconfiguration.
Description
CPRI Compression reduces the cell bandwidth required by each cell. This feature allows each
CPRI port to connect to more cascaded RRUs with the same line rate of the optical interface,
cell bandwidth, and number of antennas in the cell. Therefore, this feature reduces investment
on eNodeB installation and reconfiguration.
When CPRI Compression is enabled, about 50% CPRI bandwidth is saved.

Enhancement
 eRAN7.0
For the LampSite eNodeB, the CPRI port between an RHUB and a pRRU supports 3:1
or 4:1 compression. Therefore an Ethernet cable supports two UMTS 5 MHz carriers and
one 20 MHz or 10 MHz LTE carrier or two 20 MHz carriers.
Dependency
 eNodeB
The cell bandwidth must be 20 MHz, 15 MHz, 10 MHz, or 5 MHz.
The LBBPc does not support this feature.
Hardware Type Common CPRI Enhanced CPRI

Compression Compression
RRU/RFU MRFUd, MRFUc, MRFUe, MRFUc, MRFU V6,

MRFU V6, LRFUe, RRU3952, RRU3953,
RRU3952, RRU3962, RRU3959, RRU3262,
RRU3962d, RRU3953, RRU3269, RRU3281,
RRU3959, RRU3229, RRU3952m, RRU3962,
RRU3260, RRU3268, RRU3962d, RRU3965,
RRU3281, RRU3628, RRU3965d, RRU3261,
RRU3935, RRU3841, RRU3959w, AAU3920,
RRU3832, RRU3261, AAU3940, AAU3961,
RRU3838, RRU3928, RRU3630m, RRU3958,
RRU3929, RRU3932, RRU3971, RRU3230E,
RRU3936, RRU3938, RRU3930E, RRU3951,
RRU3939, RRU3942, RRU3953w, RRU3249,
RRU3961, RRU3630m, RRU3668
RRU3262, RRU3269,
RRU3959w, RRU3952m,
RRU3958, RRU3965,
RRU3965d, AAU3920,
AAU3940, AAU3961,
RRU3220E, RRU3230E,
RRU3930E, RHUB3908,
RRU3971, RHUB3908,
AAU3911, RRU3951,
AAU3910, RRU3953w,
RRU3249, RRU3668
RHUB RHUB3908 None
The following table provides the hardware requirements for CPRI Compression over
electrical ports between RHUBs and pRRUs on LampSite eNodeBs.
Hardware 2:1 Compression 3:1 Compression 4:1 Compression

Type Ratio Ratio Ratio
pRRU pRRU3901, pRRU3902, pRRU3901, pRRU3901,

pRRU3911, and pRRU3902, pRRU3902,
pRRU3907 pRRU3911, and pRRU3911, and

Hardware 2:1 Compression 3:1 Compression 4:1 Compression

Type Ratio Ratio Ratio
pRRU3907 pRRU3907
RHUB RHUB3908 RHUB3908 RHUB3908
2.2.15 Coverage Enhancement

Overview
This feature package is used to extend network coverage, mitigate interference caused by
multipath delay, and improve the PUSCH decoding accuracy for UEs in weak coverage areas.
Applications
The coverage enhancement feature package is used to extend network coverage, mitigate
interference caused by multipath delay, and improve service quality in weak uplink coverage
scenarios. The following table lists the features and their applications.

Network LOFD-001009 Extended This feature is used when the cell radius is
coverage Cell Access Radius in the range of (15 km, 100 km].
extension
LOFD-081223 Extended This feature is used when the cell radius is
Cell Access Radius in the range of (100 km, 160 km].
Beyond 100 km
Multipath LOFD-001031 Extended This feature mitigates inter-symbol
delay CP interference (ISI) and inter-carrier
resistance interference (ICI) caused by multipath
delay, thereby ensuring network coverage in
E-UTRAN cells.
Service quality LOFD-120201 Turbo This feature improves the PUSCH decoding
improvement Receiver accuracy of eNodeBs for UEs in weak
in uplink weak coverage areas, thereby improving uplink
coverage areas throughput.
Value
 Network coverage extension
The cell radius can be extended to up to 160 km. The random access success rate
increases in the coverage area.
 Multipath delay resistance
Extended CP enhances multipath delay spread resistance in large-cell-radius scenarios
and multipath interference resistance.
 Service quality improvement in uplink weak coverage areas

The uplink throughput for UEs in weak coverage areas increases by approximately 3% to
25%.
The average uplink throughput in weak coverage areas of a cell increases by
approximately 3% to 20%.
2.2.15.1 LOFD-001009 Extended Cell Access Radius
Availability
This feature is:
 Available in BTS3911E and BTS3912E as of eRAN11.1.
Summary
To improve wireless network coverage, 3GPP TS36.211 has defined four types of preamble
formats 0 to 3 for frame structure type 1. Format 0 corresponds to a small cell access radius.
Format 1, 2 or 3 corresponds to an extended cell access radius.
Benefits
This feature applies when the cell radius is large to extend the cell coverage.
Description
This feature provides an operator with an extended cell radius. According to 3GPP TS36.211,
there are four types of preamble formats 0 to 3 for PRACH that are defined to support
different cell access radii, as described in Table 2-3.
Table 2-3 Relationships between preamble formats and cell radii
Preamble Format TCP (TS) TSEQ (TS) Cell Radius (km)
0 3168 24576 About 15

1 21024 24576 About 70
2 6240 2 x 24576 About 30
3 21024 2 x 24576 About 100
Format 0 supports a cell radius of 15 km, and it applies when the cell radius is small, that is,
the cell radius is basic. Formats 1 to 3 applies when the cell radius is extended. Format 3
supports a cell radius of 100 km, and it is applicable when the cell radius is large, improving
coverage.
Enhancement
None

Dependency
 eNodeB
The UBBPda and UBBPdd do not support this feature. This feature does not apply to the
BTS3202E, BTS3203E, or LampSite eNodeBs. This feature applies to the BTS3911E
and BTS3912E.
2.2.15.2 LOFD-001031 Extended CP
Availability
This feature is
Summary
The Cyclic Prefix (CP) is the guard interval used in the OFDM to decrease the interference
caused by the multi-path delay. The 3GPP TS36.211 supports two types of CP length, namely
normal CP and extended CP.
Benefits
The normal CP and the extended CP are used in different cell scenarios. In case of small
multi-path delay scenario, normal CP can achieve better system performance. In case of large
multi-path delay scenario, extended CP can achieve better system performance.
Description
For both downlink and uplink, the extended CP is calculated as follows:
Extended cyclic prefix: TCP = 512*Ts
Where Ts = 1 / (2048*f), f = 15 kHz
For normal CP there are 7 symbols available in one slot. While for extended CP there are 6
symbols available in one slot. The extended CP increases overhead in exchange for larger
multi-path capability.
The CP length is set in the network planning phase according to the system application
scenario.
Enhancement
None
Dependency
 UE
UEs should support the extended CP length as the eNodeB.

2.2.15.3 LOFD-081223 Extended Cell Access Radius Beyond 100km
Availability
This feature is:
Summary
This feature supports an extended cell radius up to 200 km in open areas (for example, on the
sea) while keeping certain network performance.
Benefits
With this feature, the coverage area can be extended to more than 100 km in open areas (for
example, on the sea).
Description
This feature is implemented based on the technology of delaying uplink timing reception.
When the coverage distance exceeds 100 km, UEs cannot obtain sufficient TA adjustment
quantity without changing UE capability while complying with related specifications.
Therefore, the eNodeB delays the uplink timing reception to ensure that it can receive uplink
signals sent by UEs.
To provide coverage beyond 100 km, the eNodeB uses two RRUs to provide coverage in the
local area (0 to N km) and remote area (N km to 100 + N km) by adjusting the antenna height
and downtilt. Here, 0 < N ≤ 100 km. RRUs serving the local area provide a normal coverage,
and the uplink timing alignment timer does not need to be adjusted. RRUs serving the remote
area provide an extended coverage, and the uplink timing alignment timer needs to be
adjusted. If there is no coverage requirement in the local area, the RRU that serves the local
area does not need to be installed.
Enhancement
 eRAN12.1
The UBBPe supports the maximum cell radius of 200 km.
Dependency
 eNodeB
The eNodeB must be equipped with the BBP that supports this feature.
The following BBPs support the maximum cell radius of 160 km: UBBPd3, UBBPd4,
UBBPd5, and UBBPd6.
The UBBPe supports the maximum cell radius of 200 km.
The TX/RX mode of the cell must be 1T1R, 1T2R, 2T2R, 2T4R, or 4T4R.
The following models of RRUs do not support this feature: RRU3201, RRU3203,
RRU3220, RRU3222, RRU3808, RRU3908, LRFU, and MRFU.
 eCoordinator

None
 UE
None
None
 Core network
None
 OSS
None
 Other features
LOFD-070223 UL CoMP based on Coordinated BBU
LOFD-070222 Intra-eNodeB UL CoMP Phase II
LOFD-001066 Intra-eNodeB UL CoMP
LOFD-081219 Inter-eNodeB VoLTE CoMP
LOFD-001096 Advanced Receiver (PSIC)
LOFD-081206 Uplink Coordinated Scheduling
LOFD-001007 High Speed Mobility
LOFD-001008 Ultra High Speed Mobility
LOFD-070208 Coordinated Scheduling based Power Control
LOFD-003029 SFN
LOFD-070205 Adaptive SFN/SDMA
LOFD-081221 Super Combined Cell
LAOFD-001001 LTE-A Introduction
LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
LAOFD-070201 CA for Downlink 2CC From Multiple Carriers
LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
LAOFD-080202 Carrier Aggregation for Uplink 2CC
LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO
MRFD-101222 FDD+TDD Downlink Carrier Aggregation(LTE FDD)
MRFD-111222 FDD+TDD Uplink Carrier Aggregation (LTE FDD)
 Others
None

2.2.15.4 LOFD-120201 Turbo Receiver
Availability
This feature is:
Summary
In weak coverage scenarios such as LTE intra-frequency cell edges, this feature improves
uplink reception quality and detection performance for cell edge users (CEUs).
Benefits
This feature increases CEU throughput and improves CEU experience.
Description
This feature uses the turbo receiver principles to implement iterative channel estimation,
equalization, and Turbo decoding and to improve detection performance.
After the first decoding, the turbo receiver outputs soft information (log-likelihood ratio
[LLR]). Based on the soft information, the receiver reconstructs signals and provides them for
iterative channel estimation and equalization in the same order as in the first detection.
 Source of benefits
− Iterative channel estimation, which improves channel estimation quality
− Iterative equalization, which improves equalization quality
 Factors impacting the benefits:
− Uplink reception quality: If the original quality is worse, this feature will offer a
higher gain.
− Channel change frequency: If the original channel changes more frequently, this
feature will offer a higher gain.
− Multipath delay spread: If the original delay spread is longer, this feature will offer
a higher gain.
 Application scenarios:
− Wide coverage scenarios with a long inter-site distance, such as rural areas
− Wider coverage scenarios, such as grasslands, deserts, and oceans
− Indoor scenarios covered by outdoor sites
Enhancement
None
Dependency
 eNodeB
The UBBPe must be configured.

 Other features
None
2.3 Networking & Transmission & Security

2.3.1 Transmission Network Enhancement
Overview
IP transmission network enhancement features include the following categories:
 Quality of service (QoS) management
Related features:
− Enhanced Transmission QoS Management Different
− Transport Paths based on QoS Grade
If the intermediate network has bandwidth limitations or uses different transport paths
with different priorities, QoS enhancement-related features can be used to improve the
bandwidth usage and user experience.
 Reliability
Related features:
− Bidirectional Forwarding Detection
− Ethernet Link Aggregation OM Channel Backup
If a base station has multiple gateways or multiple access links, features designed to
enhance reliability can be used to provide redundant protections for gateways or access
links.
 Transmission maintenance
Related features:
− IP Active Performance Measurement
− Ethernet OAM
If the quality of intermediate transmission networks using microwave transmission, x
digital subscriber lines (xDSL), or of other networks prone to congestion, cannot be
ensured, features related to improving transmission maintenance can be used to monitor
link status.
 IPv6
Related features:
− S1 and X2 over IPv6
IPv4 is in wide use, but the limited number of available IP addresses has become a
concern for network expansion and upgrades. A new IP version, IPv6, has been
introduced to resolve this issue. Transmission over the X1 and S2 interfaces now support
the IPv6 protocol.
Applications
The following table describes the applications of these features.

Applica Feature Description

tion
QoS  LOFD-003011 Enhanced  Transport Overbooking uses enhanced
manage Transmission QoS transport admission control and QoS
ment Management mechanisms (traffic shaping and congestion
− LOFD-00301101 control) to allow as many UEs as possible to
Transport be admitted without impacting transmission
Overbooking quality.
 Transport Resource Overload Control helps
− LOFD-00301103
Transport Resource improve transmission reliability when the
Overload Control transport network is suddenly overloaded.
 Transport Differentiated Flow Control uses
− LOFD-00301102
Transport the following functions to provide
Differentiated Flow differentiated services for UEs while
Control ensuring fairness among them:
− Enhanced flow control, including
transport admission control
− Queue scheduling, including priority
queuing (PQ) and weighted round robin
(WRR)
− Back-pressure flow control
LOFD-003016 Different Different Transport Paths based on QoS Grade
Transport Paths based on allocates services using different transport paths
QoS Grade based on the QoS grade of the services in
question.
Reliabilit LOFD-003005 OM Channel If the active OM channel becomes faulty, a
y Backup backup OM channel takes over, improving
channel reliability.
LOFD-003007 Bidirectional Bidirectional Forwarding Detection is used to
Forwarding Detection detect IP route faults.
LOFD-003008 Ethernet Ethernet Link Aggregation is used to bind
Link Aggregation (IEEE multiple Ethernet links to form a logical link,
802.3ad) improving the link reliability or link bandwidth.
Transmis LOFD-070219 IP Active  IP performance can be measured on
sion Performance Measurement connections between wireless NEs and
maintena devices in compliance with Two-way Active
nce Measurement Protocol (TWAMP) standards
on wireless backhaul networks, for example,
between eNodeBs, between an eNodeB and
the CN, between a wireless NE and a
transmission device (for example, a router),
or between a wireless NE and a testing
instrument.
 The IP Active Performance Measurement
feature complies with the following IETF
IPPM standards and is implemented based
on the following standards:
− RFC5357 (TWAMP)


tion
− RFC2678
− RFC2680
− RFC2681
− RFC3393
 The Internet Engineering Task Force (IETF)
IP Performance Metrics (IPPM) working
group has defined configuration and
maintenance standards for IP-based
transmission networks. These standards
simplify performance testing and
maintenance of IP links between
transmission devices and test instruments.
 LOFD-003004 Ethernet  Ethernet OAM (IEEE 802.3ah)
OAM Used for fault isolation and troubleshooting
 LOFD-00300401 of point-to-point Ethernet services.
Ethernet OAM (IEEE  Ethernet OAM (IEEE 802.1ag)
802.3ah)
Used for fault isolation and troubleshooting
 LOFD-00300402 of end-to-end Ethernet services.
Ethernet OAM (IEEE
 Ethernet OAM (Y.1731)
802.1ag)
 LOFD-00300403 Used for end-to-end performance
Ethernet OAM (Y.1731) monitoring. This feature helps OAM
personnel track performance counters.
In compliance with the IEEE 802.1ag
protocol, this feature can provide fault
management functions (such as connectivity
checks).
IPv6 LOFD-003017 S1 and X2 S1 and X2 over IPv6 enables IP transmission
over IPv6 over the S1 and X2 interfaces.
Value
 QoS management
− LOFD-003011 Enhanced Transmission QoS Management
This feature includes three sub-features:
 LOFD-00301101 Transport Overbooking
Allows more UEs to be admitted while ensuring the service quality
 LOFD-00301102 Transport Differentiated Flow Control
This feature maintains fairness while providing differentiated services for the
UEs.
 Fairness
Each UE that has been admitted is allocated a set amount of bandwidth.
 Differentiation

UEs with high priorities are served preferentially.

 LOFD-00301103 Transport Resource Overload Control
 Protects the system when transport resources become unexpectedly
insufficient
− LOFD-003016 Different Transport Paths based on QoS Grade
 Reduces the OPEX for operators
 Improves the network reliability
 Reliability
− LOFD-003005 OM Channel Backup
 Improves the OM channel reliability
− LOFD-003007 Bidirectional Forwarding Detection
 Detects network faults
 Ensures the reliability and availability of Ethernet services and helps provide
economical and efficient Ethernet services
− LOFD-003008 Ethernet Link Aggregation (IEEE 802.3ad)
 Improves the reliability of Ethernet links between eNodeBs and transmission
devices
 Provides the load sharing function for Ethernet links, improving the link
bandwidth
 Transmission maintenance
− LOFD-070219 IP Active Performance Measurement
 Tests the QoS of transmission networks
This feature quickly locates and isolates transmission faults, reducing
maintenance costs.
 Provides long-term performance measurement
This feature monitors the transmission quality on bearer networks and reduces
maintenance costs for operators.
 Injects UDP packets into transmission networks
UDP injection consumes network bandwidth. For example, sending 80-byte
packets continuously sent at a rate of 10 packets per second during a
monitoring flow will consume 6.4 kbit/s of bandwidth.
− LOFD-003004 Ethernet OAM
 LOFD-00300401 Ethernet OAM (IEEE 802.3ah)
This feature manages the administration and maintenance of two directly
connected Ethernet devices.
 LOFD-00300402 Ethernet OAM (IEEE 802.1ag)
This feature:
 Detects network faults
 Ensures the availability and reliability of Ethernet services, and enables
service providers to provide cost-effective and efficient Ethernet services
 LOFD-00300403 Ethernet OAM (Y.1731)
This feature:
 Overcomes the difficulty in monitoring layer-2 network performance of
IP-based transmission networks and monitors the transmission quality

 Quickly locates layer-2 network connectivity or performance issues of

IP-based transmission networks, reducing the fault location time
 Monitors the layer-2 network performance and provides network
performance information to give warnings if network upgrade is required
 IPv6
− LOFD-003017 S1 and X2 over IPv6
 Provides additional IP addresses
IPv6 allows for more flexible address allocation and traffic routing, and lowers
the requirement on network address translation (NAT).
2.3.1.1 LOFD-003011 Enhanced Transmission QoS Management

2.3.1.1.1 LOFD-00301101 Transport Overbooking
Availability
This feature is
Summary
The transmission overbooking allows admission of more users with the guarantee of certain
quality with the enhanced admission control mechanism (TAC: Transport Admission Control)
and QoS mechanism (traffic shaping and congestion control).
Benefits
This feature allows admission of more users with the guarantee of certain traffic quality.
Description
The transmission overbooking mechanism allows admission of more users with the guarantee
of certain traffic quality.
The implementation of this function depends on the sub-functions TAC, traffic shaping, and
congestion control.
 TAC: It allows the bandwidth for user admission control to be larger than the bandwidth
of the physical port. That is, operators can set the admission threshold to allow admission
of more users.
 Traffic shaping: It guarantees that the total available traffic bandwidth is not larger than
the total configured bandwidth. The minimum transport bandwidth of each resource
group supported by eNodeB is 64kps for dual rate and 32kps for single rate The
bandwidth granularity is 1kbps.
 Congestion control: It detects congestion. If congestion occurs, two steps would be taken.
First, a signal is sent to the data source to indicate the congestion. Second, some
low-priority packets are discarded.

Enhancement
None
Dependency
None
2.3.1.1.2 LOFD-00301102 Transport Differentiated Flow Control
Availability
This feature is
Summary
Transmission Differentiated Flow Control enhances the admission control mechanism (TAC:
Transport Admission Control) ,Queue scheduling (Priority Queue-PQ scheduling and
Weighted Round Robin-WRR scheduling) and back-pressure flow control to provide users
with differentiated services while guaranteeing fairness.
Benefits
This feature provides users with differentiated services while guaranteeing fairness.
Description
Transmission Differentiated Flow Control provides users with differentiated services while
guaranteeing fairness.
 Fairness: Each admission user should be allocated some bandwidth to avoid hungry
phenomenon.
 Differentiation: High-priority users take precedence over low-priority ones.
The implementation of this function depends on the sub-functions TAC , Queue scheduling
and back-pressure flow control.
 TAC: If the GBR requirement exists, the transport bandwidth is computed on the basis of
the GBR; otherwise, it is computed on the basis of the default reserved bandwidth of, for
example, non-GBR services.
 Queue scheduling: services enter to PQ and WRR queues based on service priority.
Services that entered the PQ queues have the highest priority to be scheduled, Services
that entered the WRR queues are scheduled on the basis of the weight computed
according to the traffic bandwidth. Each service has a weight and then has a chance to be
scheduled.
 Back-pressure flow control: It detects congestion S1 overhead . If congestion occurs, two
steps would be taken. First, a signal is sent to the data source to indicate the congestion.
Second, some low-priority packets are discarded.

Enhancement
None
Dependency
None
2.3.1.1.3 LOFD-00301103 Transport Resource Overload Control
Availability
This feature is
Summary
Transmission Resource Overload Control is a way to rapidly enhance the transmission
stability when overloaded happen unexpectedly.
Benefit
This feature provides protection for the system when transmission resources are overloaded
unexpectedly
Description
Transmission Resource Overload Control provides protection for the system when
transmission resources are overloaded unexpectedly.
There are two scenarios of the unexpected overload:
 A great bandwidth change of transport bearer (the bandwidth available in the system)
occurs. For example, the transmission bandwidth decreases from 20 Mb/s to 10 Mb/s
because of network failure.
 A great bandwidth change of service traffic (the bandwidth used in the system) occurs.
For example, the traffic bandwidth increases from 5 Mb/s to 10 Mb/s rapidly.
When the above-mentioned scenarios happen, it is necessary to take some extreme actions
such as releasing low-priority users to guarantee high-priority users'QoS.
The strategy depends on QoS parameter Allocation and Retention Priority (ARP). ARP
defines whether user could be released during overload or not.
Enhancement
None
Dependency
None

2.3.1.2 LOFD-070219 IP Active Performance Measurement
Availability
This feature is
Summary
IP performance monitoring (IPPM) introduced by the Internet Engineering Task Force (IETF)
boosts IP transport network development and improves the test performance of IP links
between transmission devices and test devices.
This feature is developed based on IPPM specifications, including RFC5357 (TWAMP),
RFC2678, RFC2680, RFC2681, and RFC3393.
This feature supports IPPM between wireless network elements (NEs) and devices supporting
the Two-Way Active Measurement Protocol (TWAMP) in the wireless backhaul network. For
example, IPPM can be performed between:
 eNodeBs over the X2 interfaces
 eNodeBs and devices in the evolved packet core (EPC)
 Wireless NEs and transmission devices (such as routers)
 Wireless NEs and test devices
Benefits
This feature supports the quality of service (QoS) test on the transport network, facilitates
problem location and rectification, and therefore reduces maintenance costs.
This feature supports traffic measurement over a long duration, enables operators to monitor
the QoS of the transport network, and therefore reduces maintenance costs.
This feature uses UDP packet injection for testing, consuming network bandwidths. For
example, if a piece of monitoring stream is sent in consecutive packet transmission mode at a
speed of 10 packets per second and the length of each packet is 80 bytes, the network
bandwidth to be consumed is 6.4 kbit/s.
Description
This feature detects the transmission performance of the IP network between eNodeBs and the
EPC, or between transport devices and test devices based on the TWAMP. Meanwhile, this
feature monitors changes in QoS parameters related to the transport network, such as
round-trip delay, one-way packet loss rate, and one-way jitter.
A measurement model is defined based on the TWAMP. The measurement model provides
functions of the Controller and the Responder. The Controller consists of the Session-Sender
and Control-Client, and the Responder consists of the Session-Reflector and Server.
TWAMP control packets are transmitted between the Control-Client and Server for
measurement task negotiation (also known as initialization), start, and stop. TWAMP control
packets are transmitted based on TCP, and the Server uses port 862.

TWAMP test packets are transmitted between the Session-Sender and Session-Reflector based
on UDP.
The following figure shows the working mechanism of the measurement model.
The Controller sends TWAMP packets over a negotiated stream based on the measurement
task negotiation result. The stream consists of the Controller IP address, Responder IP address,
UDP port number, and Type-P information. Type-P information can be the protocol type, port
number, packet length, or differentiated services code point (DSCP). A TWAMP test packet
contains the sending sequence number and sending timestamp. Based on the TWAMP test
packets, link performance indicators (such as one-way delay, one-way jitter, one-way packet
loss rate, and round-trip delay) can be calculated.
The Responder sends responses to the packets sent by the Controller. The Responder records
the receiving timestamp, obtains the sending sequence number and timestamp, and generates
a response packet. The response packet contains the receiving timestamp, sending sequence
number, and sending timestamp of each packet sent by the Controller, as well as the sending
sequence number and sending timestamp of each packet sent by the Session-Reflector.
This feature works in unacknowledged mode, and supports the functions of the Controller and
Responder.
This feature calculates the packet loss rate within a measurement period using the following
formulas:
 Packet loss rate in the direction from the Sender to the Reflector = (Number of packets
sent by the Sender – Number of packets sent by the Reflector)/Number of packets sent
by the Sender
 Packet loss rate in the direction from the Reflector to the Sender = (Number of packets
sent by the Reflector – Number packets received by the Sender)/Number of packets sent
by the Reflector
This feature calculates the round-trip time (RTT) using the following formula:
RTT = (T2 – T1) + (T4 – T3) = (T4 – T1) – (T3 – T2)
where
 T1: time that the Sender sends the packet

 T2: time that the Reflector receives the packet

 T3: time that the Reflector sends the response packet
 T4: time that the Sender receives the response packet
This feature calculates the one-way jitter based on the delay between adjacent packets.
This feature supports fault location of the transport network in segments in daily operation
and maintenance by connecting the eNodeB and TWAMP supporting devices such as the
intermediate router. This feature supports traffic measurement over a long duration and
quality monitoring of the transport network.
Enhancement
None
Dependency
 eNodeB
None
 UE
None
None
 CN
None
 OSS
None
 Other Features
If the UDP loopback function is enabled on the base station side, UDP loopback cannot
work with TWAMP simultaneously to perform loopback tests on specified IP addresses
or all IP addresses.
 Others
Peer devices must support the TWAMP protocol.
Currently, this feature supports IPPM between wireless NEs and Huawei routers.
2.3.1.3 LOFD-003004 Ethernet OAM

2.3.1.3.1 LOFD-00300401 Ethernet OAM (IEEE 802.3ah)
Availability
This feature is

Summary
Ethernet OAM (803.3ah) provides the fault isolation and troubleshooting capabilities for
point-to-point Ethernet services.
Benefits
Ethernet OAM between two directly connected devices is available.
Description
Ethernet OAM is a protocol at the MAC layer in which the protocol is defined to facilitate the
operation, administration, and maintenance (OAM) of Ethernet. Ethernet OAM includes
802.3ah and 802.1ag.
 802.3ah supports point-to-point OAM between two directly connected devices.
 802.1ag provides the end-to-end OAM function.
The basic functions supported by 802.3ah are as follows:
 Discovery: OAM session setup procedure. The device sends OAM PDUs (Protocol Data
Unit) periodically to know whether the peer device supports 802.3ah function properly
or not.
 Remote failure indication: When detecting faults such as a link fault, dying gasp, critical
event, the device informs the peer device of the faults with OAM PDUs.
 Link monitoring: The device supports link bit error rate (such as error frame and error
signal) monitoring. When the error rate exceeds the threshold, it will report the event to
the peer device with OAM PDUs.
 Remote loopback: The device sends a loopback control PDU to ask the peer device to
loop back. With loopback, it is easy to locate the fault and test the link quality.
Enhancement
None
Dependency
The peer equipment must support IEEE802.3ah when IEEE802.3ah is used.
 CN
The core network equipments should support this function
2.3.1.3.2 LOFD-00300402 Ethernet OAM (IEEE 802.1ag)
Availability
This feature is

Summary
Ethernet OAM (803.1ag) provides the fault isolation and troubleshooting capabilities for
end-to-end Ethernet services.
Benefits
Ethernet OAM (IEEE802.1ag) can help the operator to detecting network fault.
 Ethernet OAM (IEEE802.1ag) achieves reliability and high availability of Ethernet
services, enables the service provider to provide economical and efficient advanced
Ethernet services.
Description
Ethernet OAM (IEEE802.1ag) can report the status of the network at the data link layer, thus
monitoring and managing the network more effectively.
It establishes end-to-end detection to perform maintenance of the Ethernet based on the
services as follows:
 Continuity Check: Detecting the connectivity of two Ethernet elements.
 Loop Back: The link status detecting, similar as IP ping.
 Link Trace: Locate the fault of link, similar as IP trace route.
Enhancement
None
Dependency
The peer equipment must support IEEE802.1ag when IEEE802.1ag is used
 CN
2.3.1.3.3 LOFD-00300403 Ethernet OAM (Y.1731)
Availability
This feature is
Summary
Ethernet OAM (ITU Y.1731) provides end-to-end performance monitoring functions which
allow operation, administration, and maintenance (OAM) staff to measure different
performance parameters. It also provides fault management functions (including continuity
check) which are compliant with the IEEE 802.1ag protocol.

Benefits
 On an IP transmission network, operators cannot monitor transmission quality or layer 2
network performance. Ethernet OAM (ITU Y.1731) can help operators do it.
 On an IP transmission network, operators have trouble locating faults and fault diagnosis
takes a long time. Ethernet OAM (ITU Y.1731) can quickly locate layer 2 connection and
performance faults.
 Operators can use Ethernet OAM (ITU Y.1731) to monitor layer 2 performance and
therefore acquire more information about the network performance. The information
helps the operators to decide whether to upgrade the network.
Description
The Ethernet OAM (ITU Y.1731) protocol defines fault management and performance
monitoring functions. Because the fault management function defined in the ITU Y.1731
protocol is compliant with the IEEE 802.1ag protocol, this feature includes only the
performance monitoring function part.
Ethernet OAM (ITU Y.1731) performance monitoring measures Ethernet performance
parameters including Frame Loss Ratio, Frame Delay and Frame Delay Variation.
This feature establishes an end-to-end detection session to monitor performance parameters of
the Ethernet based on the services:
 Ethernet frame loss measurement (ETH-LM) is used to collect counter values applicable
to ingress and egress service frames. The counters maintain a count of transmitted and
received data frames between a pair of maintenance association end points (MEPs).
 Ethernet delay measurement (ETH-DM) can be used for an on-demand OAM to measure
frame delay and frame delay variation. ETH-DM can be performed in two directions,
which is called two-way ETH-DM. Two-way ETH-DM is recommended, considering the
requirement of one-way ETH-DM for clock synchronization between two MEPs.
Enhancement
None
Dependency
The peer equipment must also comply with ITU Y.1731.
 CN
2.3.1.4 LOFD-003005 OM Channel Backup
Model
LT1S00OMCB00
Availability
This feature is


Summary
The OM channel backup solution provides reliability of OM channel with an alternative OM
channel if OM main channel happen to fail.
Benefits
This feature provides reliability of OM channels.
Description
The OM channel backup function provides reliability of OM channels.
In the OM channel backup solution, there are two OM channels: master and slave. The key is
that each channel has an OM IP address. Usually, only the master channel is active. When the
master channel fails, the slave channel is activated.
Enhancement
None
Dependency
The peer equipments should support this function.
2.3.1.5 LOFD-003007 Bidirectional Forwarding Detection
Availability
This feature is:
Summary
Bidirectional Forwarding Detection (BFD) is used to detect the fault of an IP route.
Benefits
 Helps operators detect network faults.
 Ensures the availability and reliability of Ethernet services, and enables service providers
to provide cost-effective and efficient Ethernet services.
Description
The BFD feature is a method of detecting the IP route connectivity by periodically
transmitting BFD packets between two nodes. When no BFD packet is received during the

detection period, an IP route is considered faulty and related recovery actions will be triggered
to prevent service interruption. BFD can quickly detect faults and therefore can be used for
telecommunication services carried on IP networks.
An eNodeB supports single-hop and multi-hop BFDs. Multi-hop BFD means that at least one
router exists on the IP path between the source node and destination node. Single-hop BFD
means that only one router exists.
The single-hop BFD is used for detecting the gateway availability.
The multi-hop BFD is used for detecting the connectivity between two NEs, such as two
eNodeBs, eNodeB and S-GW/MME, or eNodeB and transmission equipment. The following
figure shows the BFD application scenario.
Figure 2-21 BFD application scenario
Enhancement
 eRAN11.1
BFD security hardening is implemented in eRAN11.1.
A BFD session between an eNodeB and the peer node must contain authentication
information of the two ends. If the local keys are inconsistent between the two ends, the
BFD session will be terminated.
BFD authentication for an eNodeB involves only single-hop BFD.
The detection mechanism and post-detection processing (such as route association) after
a BFD authentication is performed are the same as those of a BFD session. Security
authentication ensures the consistency and integrity of a session and provides the
anti-replay function.
Dependency

The peer equipment supports BFD.
2.3.1.6 LOFD-003008 Ethernet Link Aggregation (IEEE 802.3ad)
Model
LT1S000ELA00
Availability
This feature is
Summary
The Ethernet Link Aggregation binds several Ethernet links to one logical link.
Benefits
 Ethernet link aggregation enhances the reliability of Ethernet link between eNodeB and
transport equipment.
 Ethernet provides loading balance on the link between the eNodeB and transport
equipment and increases the bandwidth of the link.
Description
Ethernet link aggregation is a protocol defined in IEEE802.3ad. IEEE802.3ad defines a link
aggregation control protocol (LACP). The links status of link group could be detected by
LACP.
The eNodeB supports static LACP. For static LACP, the parameters of the link group are
configured manually. The fault detecting uses the LACP.
The Ethernet link aggregation can be used in the following figure.
Figure 2-22 the Ethernet link aggregation

Enhancement
None
Dependency
 eNodeB
This feature is not applicable to UMPT board.
The transport network's ingress equipment from eNodeB must support this function.
It must support Ethernet.
2.3.1.7 LOFD-003016 Different Transport Paths based on QoS Grade
Availability
This feature is
Summary
Different transport paths based on QoS grade is a transport networking solution that consists
on different transport paths implementation for different QCI grades.
Benefits
 Different transport paths to reduce operator OPEX
 Different transport-paths implementation to improve the network reliability
Description
Different transport paths based on QoS grade consist of two paths between eNodeB and
S-GW. Operator can configure traffic to have two groups of different QCIs being allocated to
the two different paths, high QoS path and low QoS path. The high QoS path provides lower
bandwidth for less high QoS traffic, and the low QoS path provides higher bandwidth for
more low QoS traffic. Thereby, operator can reduce the network operation expenditures
OPEX.

Figure 2-23 Two paths configuration between eNodeB and S-GW
Different transport paths based on QoS grade can also improve the network reliability. When
failure happens to one path, the connection will be dropped out, and the new data traffic will
be handed off over the second path. The path failure detection is done by means of the
different OAM mechanisms supported by Huawei eNodeB such as BFD, Ethernet OAM, and
Ping, and so on.
Enhancement
None
Dependency
 CN
S-GW must support two paths configurations.
2.3.1.8 LOFD-003017 S1 and X2 over IPv6
Availability
This feature is
Summary
This feature supports IPv6 protocol on S1 and X2 interface.
Benefits
IPv6 has a vastly larger address space than IPv4. This expansion of address space provides
flexibility in allocating addresses and routing traffic and eliminates the primary need for
network address translation (NAT).
This feature makes eNodeB be able to support S1 and X2 protocols over IPv6 network so that
eNodeB could provides service on IPv6 network.

Description
This feature supports IPv6 protocol on S1 and X2 interface.
Figure 2-24 S1 and X2 protocol stack
The S1 interface connects the eNodeB to the EPC. The X2 interface is used to inter-connect
eNodeBs. Both of them are based on a full IP transport stack with no dependency on the
legacy SS7 network as used in GSM or UMTS networks. In addition to support S1 and X2
interface over IPv4 protocol stack, this feature supports S1 and X2 interface over IPv6
protocol stack.
Enhancement
None
Dependency
The peer equipments should support IPv6.
 CN
The core network should support this feature.
2.3.1.9 LOFD-003002 2G/3G and LTE Co-transmission
Availability
This feature is:

Summary
2G/3G and eNodeB co-transmission provides operators with the option of eNodeB
co-transmission with legacy networks such as GSM, UMTS, or CDMA for better resource
utilization and OPEX reduction.
Benefits
In a co-site scenario, this feature provides the following benefits:
 Better utilization of transmission resources
 Reduced OPEX
Description
The eNodeB supports co-transmission with 2G/3G base stations.
During eNodeB deployment, an eNodeB may share a site with a base station operating in a
different mode (GSM, UMTS, or CDMA). In such a case, co-transmission facilitates better
utilization of transmission resources and reduces the OPEX (for example, rental fees of the
transmission resources).
The following figure shows a 2G/3G and eNodeB co-transmission topology.
Figure 2-25 2G/3G and eNodeB co-transmission
Implementing co-transmission requires multiple ports, IP routes, DHCP relay, and Weighted
Round Robin (WRR) scheduling.
 Multiple ports
The eNodeB provides several Ethernet ports and E1/T1 ports.
 IP route
The data of the cascaded base stations is switched to an IP network by the eNodeB. IP
routes can be configured by users.
 DHCP relay
In general, cascaded base stations obtain IP addresses using DHCP. DHCP requires that
the DHCP client (the base station) and the DHCP server be located in the same broadcast
domain. In a co-transmission scenario, however, the cascaded base stations are not
located in the same broadcast domain as the DHCP server. In this case, the DHCP relay
must transfer DHCP messages across different broadcast domains.

 WRR scheduling
Data is scheduled on the basis of a weight computed based on the traffic bandwidth,
thereby ensuring fairness in data transmission between cascaded base stations and the
eNodeB. Each cascaded base station and eNodeB have a weight and then have a chance
to be scheduled.
Enhancement
None
Dependency
 Others
2G/3G base stations must support IP transmission.
2.3.2 Synchronization
Overview
Synchronization maintains a certain relationship between two or more signals in terms of
frequency or time. In a digital communications network, synchronization ensures that the
clock frequency or time difference among communication equipment across the entire
network is within a reasonable error range. In this way, synchronization prevents the
transmission performance deterioration caused by incorrect timing of receiving or
transmitting signals in the transmission system.
Clock synchronization is classified into frequency synchronization and time synchronization.
In principle, a lower-level device must synchronize with its upper-level device to achieve
clock synchronization.
As a lower-level device, eNodeBs support multiple synchronization sources, including GPS
clock, BeiDou clock, IEEE1588 V2 clock, IEEE1588v2 ATR, clock over IP, synchronous
Ethernet, 1PPS+TOD clock, BITS clock, and E1/T1 line clock.
After eNodeBs are synchronized with an external clock source, clock signals are distributed to
each module inside eNodeBs. The eNodeB clock can be in one of the following modes:
free-running, fast-tracking, locked, and holdover.
Applications
As a prerequisite for the provisioning of wireless services, the synchronization feature
package is recommended when frequency synchronization or time synchronization is required.
The following table describes the features in this package and their applications.

tion
Frequenc LOFD-00301301/ML eNodeBs can select the most appropriate clock
y OFD-00301301 synchronization mode based on the clock topology,
synchron Synchronization with and support the Synchronization with Ethernet (ITU-T
ization Ethernet (ITU-T G.8261) feature.
G.8261)
LOFD-00301302/ML IEEE1588 V2 implements synchronization


tion
OFD-00301302 measurement and achieves highly-accurate
IEEE1588 V2 Clock synchronizaiton between distributed nodes and
Synchronization independent devices. IEEE1588 V2 achieves
high-precision frequency synchronization and time
synchronization between a clock server and eNodeBs
on the radio access network (RAN).
IEEE1588 V2 clock works as an alternative to the
GPS clock.
LOFD-00301303/ML Clock over IP is a Huawei-proprietary protocol, and
OFD-00301303 can be used on networks where IEEE1588 V2 Clock
Clock over IP Synchronization is inapplicable.
(Huawei proprietary)
Time LOFD-00301302/ML IEEE1588 V2 implements synchronization
synchron OFD-00301302 measurement and achieves highly-accurate
ization IEEE1588 V2 Clock synchronizaiton between distributed nodes and
Synchronization independent devices. IEEE1588 V2 achieves
high-precision frequency synchronization and time
synchronization between a clock server and eNodeBs
on the RAN.
IEEE1588 V2 clock works as an alternative to the
GPS clock.
LOFD-080216 Uu Uu-based soft synchronization achieves phase
based Soft synchronization between base stations (eNodeBs and
Synchronization GBTSs) based on UE signal measurement results
provided by base stations over the Uu interface.
Afterwards, Uu-based soft synchronization uses the
GPS time configured for the reference base station and
Network Time Protocol (NTP) time configured for
other base stations to achieve time synchronization.
LOFD-121212 The eNodeB Supporting 1588v2 ATR feature
eNodeB Supporting introduces a low-cost solution based on the IEEE1588
1588v2 ATR V2 Clock Synchronization feature. With the eNodeB
Supporting 1588v2 ATR feature, clock packets are
transparently transmitted from the clock server to
eNodeBs. That is, intermediate transmission
equipment is not required to support the IEEE 1588v2
standard, and eNodeB time synchronization has less
dependency on the transmission network.
Easy LOFD-081220 Clock synchronization must be achieved between
deploym Inter-BBU Clock interconnected BBUs to support cell coordination.
ent of Sharing When BBUs are interconnected and one base station is
clock configured with the GPS clock, other base stations can
solutions share the GPS clock through the USU.

Value
 Frequency synchronization
Frequency synchronization enables eNodeBs to obtain clock signals from a clock source
or from the transmission network. Different ways of synchronization bring different
benefits.
− Synchronization with a clock source (GPS/BeiDou/1PPS/BITS): The internal
clocks of base stations are directly synchronized with a reference clock. This
synchronization mode meets the clock precision requirements of the radio
frequency and transmission network.
− Synchronization with a transmission network clock (E1T1/synchronous
Ethernet/IEEE1588 V2): The internal clocks of eNodeBs are synchronized with the
transmission network without using any auxiliary clock devices. This
synchronization mode meets the clock precision requirements of the radio
frequency and transmission network, and it also reduces costs.
 Time synchronization
Time synchronization enables eNodeBs to obtain clock signals from a clock source, the
transmission network, or the Uu interface. Different ways of synchronization bring
different benefits.
− Synchronization with a clock source (GPS/BeiDou/1PPS): The internal clocks of
eNodeBs are directly synchronized with a reference clock, in which case eNodeBs
are provided with highly-accurate and reliable clock signals. This synchronization
mode meets the clock precision requirements of the radio frequency and especially
FDD services.
− Synchronization with a transmission network clock (IEEE1588 V2):
Synchronization with the IEEE1588 V2 clock reduces operators' network
deployment costs and facilitates network management and maintenance.
− Uu-based soft synchronization: Many LTE features (TDM eICIC/inter-eNodeB
CA/eMBMS) pose high requirements for phase synchronization or time
synchronization. Uu-based software synchronization supports time synchronization
at lower costs compared with GPS clock or IEEE1588 V2 clock.
Uu-based soft synchronization can also meet the time synchronization requirements of
the evolved multimedia broadcast/multicast service (eMBMS).
 Synchronization reliability improvement
If an error occurs on the clock source in use, eNodeBs are not affected or the impact is
minimized.
2.3.2.1 LOFD-003013 Enhanced Synchronization

2.3.2.1.1 LOFD-00301301 Synchronization with Ethernet (ITU-T G.8261)
Availability
This feature is

Summary
Huawei eRAN2.0 can support Synchronize with Ethernet (ITU-T G.8261) Clock.
Benefits
The Synchronization with Ethernet technology is an economical and convenient solution for
all-IP networks.
Description
The Synchronization with Ethernet, which adopts Ethernet link code streams to retrieve
clocks, is a physical layer based clock synchronization method. A highly accurate clock is
used by the Ethernet physical layer (PHY) for data transmission. The receiver extracts and
retrieves the clock signals from data streams, and the high accuracy can be maintained. The
following figure shows the framework of the Synchronization with Ethernet.
Figure 2-26 Basic principle of the Synchronization with Ethernet
The eNodeB does not require extra synchronization equipment or hardware to implement
synchronization with Ethernet.
Enhancement
None
Dependency
The peer equipments should support this function
 CN

2.3.2.1.2 LOFD-00301302 IEEE1588 V2 Clock Synchronization
Availability
This feature is
Summary
IEEE1588 defines the PTP (Precision Time Protocol) protocol, which applies to the standard
Ethernet, with the precision to microseconds.
The IEEE1588 V2 clock synchronization targets precise synchronization of distributed and
independent clocks in measurement and control systems. In LTE applications, high-accuracy
frequency synchronization and time synchronization between clock server and eNodeB can be
achieved.
IEEE1588V2 clock synchronization is an alternative clock solution for the GPS clock
synchronization.
Benefits
Compared with the GPS clock solution, the IEEE1588V2 clock synchronization reduces the
network deployment cost for the operator and is easy for management and maintenance.
Description
 Basic principles
Figure 2-27 illustrates the basic principles of IEEE 1588.
Figure 2-27 Basic principles of IEEE 1588

The NE with the master clock sends synchronization timing packets to the NE with the
slave clock. The intermediate switching device connects to the NE with the master clock
as a slave clock to obtain the timing information on the transmission of the master clock.
Then, the intermediate switching device functions as a master clock and connects to
other devices functioning as slave clocks.
The Time Stamp Unit (TSU) provides the ability of precise time synchronization,
thereby reducing delay and jitter caused by the intermediate switching device and
accurately sending timing information. In this way, the work related to synchronization
processing is shifted to be processed at the layer between the physical layer and the
MAC layer.
 Synchronization principles
Figure 2-28 illustrates the synchronization principles of IEEE 1588.
Figure 2-28 Synchronization principles of IEEE 1588
The signaling procedure is described as follows:

Step 1 The clock server (for example, IPCLK1000) periodically sends a Sync message to the
eNodeB.
The Sync message carries the standard time information, such as year, month, date, hour,
minute, second, and nanosecond. The eNodeB records T2, the arrival time of the Sync
message at the eNodeB. The time for sending or receiving the message needs to be measured
and recorded at the underlying physical layer or the position close to the physical layer to
improve the clock accuracy.
In the IEEE1588 standard, the optional hardware assist techniques are designed to improve
the clock accuracy. If the Sync message is generated through the hardware assist techniques,
the message can also carry the timestamp T1, at which the message is sent. If the delay of the

Sync message sending from the clock server is uncertain, the clock server generates a
Follow_UP message, which carries the timestamp T1. The Follow_UP message is optional.
Step 2 The eNodeB sends a Delay_req message to the clock server at T3.
The eNodeB records T3. The clock server receives the Delay_req message at T4 and then
generates a Delay_resp message that carries the timestamp T4 to the eNodeB. The delay of
sending the Delay_resp message does not affect T4. Therefore, the Delay_resp message need
not be processed in real time.
Step 3 The eNodeB stores the complete information about T1, T2, T3, and T4.
Then, the delay of message propagation between the clock server and the eNodeB is
calculated as follows:
Delay = [(T4 – T1) – (T3 – T2)]/2
In principle, the absolute time of the eNodeB is equal to the standard time carried in the Sync
message plus the delay.
----End
Enhancement
 eRAN2.2
Security of IEEE 1588 V2 in frequency synchronization mode is enhanced by
transporting 1588-related messages with IPsec security channel.
 eRAN8.1
Supports the ITU-T G.8275.1 time synchronization protocol, which applies to the
interconnection between the eNodeB and the third-party network transmission devices
that comply with this protocol in IEEE1588 V2 layer 2 multicast networking mode.
Dependency
 eNodeB
None
 UE
None
None
 CN
The MME must support this feature.
 OSS
None
 Other Features
None
 Others
None

2.3.2.1.3 LOFD-00301303 Clock over IP (Huawei proprietary)
Availability
This feature is
Summary
Clock over IP is an alternative network clock synchronization solution if the network does not
support the IEEE1588 V2 Clock Synchronization. It is Huawei proprietary clock protocol.
Benefits
Huawei proprietary clock over IP protocol does not require extra requirement to be invested
into the IP network. This feature has the same requirements for the network as the service
transmission.
Description
The IEEE 1588V2 clock synchronization solution requires that all the devices on the clock
relay path support IEEE1588V2 protocol. If the network does not support IEEE1588V2
protocol, Huawei LTE eRAN2.0 can use Huawei proprietary protocol to support clock over
IP.
The following figure shows the framework of Huawei proprietary protocol. The clock servers
generate time stamps and send the time stamps to eNodeBs connecting to it, which act as
clock clients in this case. Because there is delay and jitter in packet networks, eNodeB uses an
adaptive method to get rid of the delay and retrieve the timing signals. The time stamps are set
in packets at the UDP layer and will be transmitted at the physical layer after the related
packet header is added, so there will be an extra expense in bandwidth.

Figure 2-29 Framework of Huawei proprietary protocol
Pay attention to the following information:

 There are clock servers and clock clients. The servers can be located in the network
independently, and the clients are integrated into the eNodeBs.
 An adaptive algorithm is involved in the system. The clock servers send time stamps,
and clock clients receive time stamps to retrieve the frequency.
 One clock server serves a maximum of 512 eNodeBs.
 Two or more clock servers can be used together to improve the reliability. This is
optional.
 The required transmission bandwidth for time stamps in unicast mode is from 5kbit/s to
100kbit/s for each clock client. In most cases, 25kbit/s is recommended.
 This proprietary protocol only supports frequency synchronization. Frequency accuracy
obtained in the eNodeB is 0.05ppm.
Enhancement
None
Dependency
None

2.3.2.2 LOFD-003023 IEEE 1588v2 over IPv6
Availability
This feature is
Summary
This feature enables eNodeB to provide frequency synchronization by transporting IEEE
1588v2 PTP messages through IPv6 unicast packet.
This feature is applicative in FDD system.
Benefits
When eNodeB accesses the IPv6 network, IEEE 1588 v2 clock synchronization could be used
in IPv6 transmission network, provide an alternative clock solution for the GPS clock
synchronization.
Description
IEEE 1588 v2 standard enables precise synchronization of clocks in measurement and control
systems implemented with technologies such as network communication, local computing and
distributed objects. It is applicable to systems communicating via packet networks.
The clocks in the communication system communicate with each other over a communication
network and the 1588 function generates a master slave relationship among the clocks in the
system. All clocks ultimately derive their time from a clock known as the grandmaster clock.
IEEE 1588 v2 over IPv6 enables the use of 1588 in networking environment deploying IPv6.
Time server as clock master sends the IEEE 1588v2 PTP message which encapsulated in IPv6
unicast packet. Then the eNodeB as clock client receives these message and uses the Adaptive
Clock algorithm to implement frequency synchronization.
The synchronization mechanism is the same as IEEE1588 v2 over IPv4, please refer to
LOFD-003013 Enhanced Synchronization.
Enhancement
None
Dependency
 Other features
This feature depends on LOFD-003013 Enhanced Synchronization.
 Others
This feature needs time server support 1588v2 over IPv6.

2.3.2.3 LOFD-080216 Uu based Soft Synchronization
Availability
This feature is:
Summary
This feature helps achieve phase synchronization between eNodeBs based on measurements
of UE signals transmitted over the Uu interface. In addition, this feature achieves time
synchronization between eNodeBs based on the Global Positioning System (GPS) equipped
on one eNodeB and Network Time Protocol (NTP) equipped on all eNodeBs in a
synchronization zone.
Benefits
Phase synchronization between eNodeBs is required by LTE features such as time division
multiplexing (TDM) enhanced inter-cell interference coordination (eICIC) and inter-site
carrier aggregation (CA). Time synchronization between eNodeBs is required by LTE features
such as evolved multimedia broadcast/multicast service (eMBMS). GPS, IEEE1588 V2 clock
synchronization, and Uu-based soft synchronization support phase synchronization and time
synchronization between eNodeBs. Uu-based soft synchronization achieves phase
synchronization and time synchronization between eNodeBs at lower costs than GPS and
IEEE1588V2 clock synchronization.
Uu-based soft synchronization supports time synchronization for eMBMS.
Description
In two neighboring eNodeBs that are included in one eNodeB pair, the random access
preamble sent by a UE at the eNodeB edge is detected by both eNodeBs. The phase difference
between the two eNodeBs is calculated based on the delay in transmitting the preamble from
the UE to both eNodeBs over the Uu interface.
The phase differences between each pair of eNodeBs in a synchronization zone can be used to
calculate phase adjustments for each eNodeB, thereby achieving phase synchronization
between eNodeBs in the synchronization zone. eNodeBs perform phase adjustments in their
off-peak hours to achieve phase synchronization.
eNodeBs in a synchronization zone use the same reference clock source to achieve frequency
synchronization based on a synchronous Ethernet and to perform phase tracing. In this way,
the phase differences between eNodeBs remain stable, ensuring phase synchronization within
the phase difference adjustment period.
In a synchronization zone, if a reference eNodeB is equipped with GPS or IEEE1588 V2,
other eNodeBs are equipped with NTP, and phase synchronization between eNodeBs is
achieved, other eNodeBs calibrate the NTP time based on mapping between the GPS time and
phases to obtain the GPS time and achieve time synchronization.

Enhancement
None
Dependency
 eNodeB
The baseband processing unit must be LBBPd or UBBP. The main control board must be
LMPT or UMPT.
 eCoordinator
ECO6910 is required.
 Others
Both the transport network and the eNodeB must support synchronous Ethernet.
2.3.2.4 LOFD-081220 Inter-BBU Clock Sharing
Availability
This feature is:
Summary
The Inter-BBU Clock Sharing feature enables multiple BBUs to share Global Positioning
System (GPS) clock references, including the Remote Global Positioning System (RGPS)
clock reference. With this feature, the BBU deployed for a macro eNodeB sends GPS
(including RGPS) clock information to the universal switching unit (USU), and then the USU
forwards the information to other BBUs (including LampSite BBUs) for clock
synchronization.
Benefits
This feature solves the problem that GPS (including RGPS) cannot be deployed for LampSite
BBUs and improves the reliability of the BBU clock.
Description
With this feature, the USU delivers the clock signals of the BBU that has locked the GPS
reference clock to other BBUs, including LampSite BBUs. Other BBUs can use the GPS
(including RGPS) clock reference signals sent by the USU for synchronization or use the GPS
(including RGPS) clock reference in the local subrack for synchronization. By default, BBUs
use the GPS (including RGPS) clock reference signals sent by the USU for synchronization. If
a BBU cannot receive GPS (including RGPS) clock reference signals from the USU because
of a fault and a GPS (including RGPS) clock signal is available in the local subrack, the BBU
will automatically use the local GPS (including RGPS) clock signal.
Two GPS reference clocks can be configured for two separate BBUs. The two GPS reference
clocks work in active/standby mode. If the active GPS (including RGPS) reference clock
becomes faulty, BBUs automatically synchronize their clocks with the standby GPS
(including RGPS) reference clock.

Enhancement
None
Dependency
 eNodeB
The LBBPc and LMPT do not support this feature. This feature does not apply to the
BTS3202E, BTS3203E, BTS3911E, or BTS3912E eNodeBs.
 Others
This feature must be used in Cloud BB scenarios.
2.3.2.5 LOFD-121212 eNodeB Supporting 1588v2 ATR
Availability
This feature is:
Summary
This feature supports the deployment of 1588v2 time synchronization on the eNodeB.
Synchronization packets are transparently transmitted from the clock server to the eNodeB.
The intermediate transport network devices are not required to support IEEE 1588v2
standards, which reduces the dependency of eNodeB time synchronization on the transport
network.
Benefits
This feature implements time synchronization with the IEEE 1588v2 clock on the live
network, making it possible to deploy LTE-A features.
In addition, only the clock server and eNodeB are required to support IEEE 1588v2 standards,
which reduces the network construction costs.
Description
1588v2 Adaptive Time Recovery (ATR) is a low-cost IEEE 1588v2 time synchronization
solution. 1588v2 ATR depends on the activation of the G.8275.2/IEEE1588V2 feature.
Otherwise, 1588v2 ATR cannot take effect.
1588v2 ATR does not require intermediate transport network devices to support IEEE 1588v2
standards. The eNodeB implements time synchronization by filtering out the packet delay
variation (PDV). Not every hop of the transport network device between the clock server and
the base station is required to support 1588v2. To meet the accuracy requirements of time
synchronization, the IPCLK server must be moved downwards and a large number of clock
servers must be deployed at the edge access layer. In addition, application scenarios must be
restricted to improve reliability.
The following figure shows a typical application scenario.

The time synchronization of 1588v2 ATR is sensitive to the PDV. The residual PDV is the
synchronization error. The synchronization error claimed by Huawei is 1.5 us. That is, the
minimum PDV from the clock source to the eNodeB does not exceed 1.5 us.
PDV is generally caused by congestion, which is related to the load, packet size, different
methods used by devices to process the load, and cumulative effect of the load processing on
multiple devices. Therefore, the PDV is related to the load, packet size, and type and number
of the intermediate devices.
PDV requires the following: With the measurement period of 100s, the proportion of the
end-to-end noise floor jitter (floor delay) per second being less than 1 us is greater than 10%.
The following are the recommendations for the transport network:
Only the access of switches, routers, and microwave is supported, and the access of MSTP
and DSL is not supported.
The number of switches, routes, microwaves, and combinations of these devices must be less
than or equal to 4, 2, 3, and 3, respectively.
The time during which the load of the transport network is constantly greater than 80% must
be less than or equal to 100s.
The time of a single transport network interruption must be less than or equal to 100s.
Generally, 10 to 30 sites share one set of "small-scale clock server+GPS".
Enhancement
 None
Dependency
 eNodeB
The UMPT or LMPT must be configured to support this feature.
 eCoordinator
None

 UE
None
 Core network
None
 Other features
This feature requires the LOFD-00301302 IEEE1588 V2 Clock Synchronization feature.
 Others
An IP clock server must be deployed in the network.
2.3.3 Security
Overview
To address the increasing severity of network security threats, Huawei has designed and
deployed SingleRAN networks to provide multi-plane and multi-layer security protection
against various threats and attacks. This design is in accordance with the security model
defined in ITU-T X.805.
The security feature package protects radio equipment and network communications against
security attacks from insecure transport networks.
Applications
The security feature package is applicable to defense from local attack, security access,
coverage improvement, reliability enhancement, and multi-operator PKI. The following table
describes these features and related applications.

cation
Defens LOFD-003014 Integrated The integrated firewall filters attack packets to
e from Firewall improve equipment security.
local MLOFD-003014 Integrated
attack Firewall
LOFD-00301401 Access The integrated firewall provides the ACL
Control List (ACL) function to filter L2, L3, and L4 packets.
MLOFD-00301401 Access
Control List (ACL)
LOFD-00301402 Access The integrated firewall provides the ACL auto
Control List (ACL) Auto generation function to automatically configure
Configuration ACL rules to simplify network maintenance.
MLOFD-00301402 Access
Control List (ACL) Auto
Configuration
Access LOFD-003015 Access IEEE 802.1x is an IEEE standard from the IEEE
securit Control based on 802.1x 802 group of networking protocols for port-based
y MLOFD-003015 Access network access control. Port-based network
Control based on 802.1x access control requires that the authentication
access equipment in the local area network


cation
(LAN) perform identity authentication and access
control on users or devices connected to its ports.
Only authenticated users or devices are allowed
to access the LAN through corresponding ports.
Access Control based on 802.1x prevents
unauthorized users or devices from accessing the
network, which ensures transport network
security.
Reliabi LOFD-070212 eNodeB These features improve the reliability of
lity Supporting PKI Redundancy PKI-based secure networks.
enhanc MLOFD-070212 eNodeB
ement Supporting PKI Redundancy
Multi- LOFD-081280 eNodeB The eNodeB Supporting Multi-operator PKI
operato Supporting Multi-operator feature enables each operator to deploy its own
r PKI PKI PKI server on the base station. With this feature,
LOFD-081280 eNodeB certificates from multiple operators can be loaded
Supporting Multi-operator to and managed on the base station, and
PKI certificate application, update, and revocation of
one operator are independent from those of
another operator. The IPsec tunnel of each
operator uses the certificates issued by its own
PKI server for authentication.
Value
 Defense from local attack
The integrated firewall filters attack packets to improve equipment security.
 Access security
Access Control based on 802.1x prevents unauthorized users or devices from accessing the
network, which ensures transport network security.
 Reliability enhancement
The eNodeB Supporting PKI Redundancy feature improves PKI networking reliability.
 Multi-operator PKI
When the eNodeB Supporting Multi-operator PKI feature is enabled, certificates from
multiple operators can be loaded to and managed on a base station, and certificate application,
update, and revocation of one operator are independent from those of another operator.
2.3.3.1 LOFD-070212 eNodeB Supporting PKI Redundancy
Availability
This feature is:


Summary
This feature supports deployment of one active PKI server and one standby PKI server on a
network. If a session between an eNodeB and the active PKI server fails, the eNodeB
automatically reinitiates a session with the standby PKI server.
Benefits
 Prevents certificate updates and CRL acquisitions from being affected by active server
failures.
 Prevents link failures caused by certificate-related problems.
 Improves the reliability of PKI-based secure networks.
Description
In PKI redundancy, you must deploy one active PKI server and one standby PKI server on a
network and ensure that they synchronize certificate management data between them. If a
session between an eNodeB and the active PKI server fails, the eNodeB automatically
reinitiates a session with the standby PKI server to continue to apply for and update a
certificate and obtain a CRL. The following figure illustrates how this feature works.
Figure 2-30 Example of eNodeB Supporting PKI Redundancy
Enhancement
None
Dependency
 eNodeB
The UMPT, LMPT, or UTRPc must be configured to support this feature.

 UE
None
None
 Core network
None
 OSS
None
 Other features
− Prerequisite features
This feature depends on the LOFD-003010 Public Key Infrastructure (PKI) feature.
− Mutually exclusive features
None
 Others
One active PKI server and one standby PKI server must be deployed on the network.
2.3.3.2 LOFD-081280 eNodeB Supporting Multi-operator PKI
Availability
This feature is
 Available in micro eNodeBs as of eRAN8.1
 Available in LampSite eNodeBs as of eRAN8.1
Summary
This feature applies to RAN Sharing scenarios so as to securely isolate the services of each
operator. After this feature is enabled, if each operator deploys its own PKI server, the
eNodeB can load and manage the device certificates issued by multiple PKI servers. The
eNodeB establishes an independent security tunnel for each operator based on their respective
device certificates, so as to achieve the secure isolation of each operator's services.
Benefits
In RAN Sharing scenarios, if each operator deploys its own PKI server, this feature provides
an independent security tunnel for each operator so as to achieve the secure isolation of each
operator's services.
Description
The eNodeB supports loading and managing device certificates and CRL files issued by
multiple PKI servers. The following actions are involved:
 Certificate application: Each operator uses a Huawei-issued device certificate to apply to
its own PKI server for a certificate, and the eNodeB establishes an independent IPsec
tunnel for each operator. As shown in Figure 2-31, operator A's PKI server issues
certificate A to the eNodeB, and operator B's PKI server issues certificate B to the

eNodeB. Then, the eNodeB establishes IPsec tunnels A and B for operators A and B,
respectively.
 Certificate update: Similarly, each operator's PKI server issues an updated certificate.
 Certificate revocation: Similarly, each operator's PKI server can revoke a certificate.
 CRL file management: Similarly, the eNodeB can obtain the CRL file on each server.
The eNodeB then independently manages each certificate file.
To securely isolate the services of operators, the eNodeB can use their respective device
certificates to establish a dedicated IPsec tunnel for each operator.
Figure 2-31 eNodeB Supporting Multi-operator PKI
Enhancement
None
Dependency
 eNodeB
The eNodeB must be configured with the UMPT, UMDU, LMPT, or UTRPc board to
support this feature.
 UE
None
Multiple CA servers must be deployed in the network.
 CN

None
 OSS
None
 Other Features
None.
 Others
None
2.3.3.3 LOFD-003014 Integrated Firewall

2.3.3.3.1 LOFD-00301401 Access Control List (ACL)
Availability
This feature is
Summary
Access Control List is comprised of a series rules, the eNodeB provides packet filtering based
on Access Control List.
Benefits
 The eNodeB provides packets filtering according to Access Control List to prevent some
attacks.
 The eNodeB identifies specific kinds of packets, which need to be encrypted and
authenticated by IPsec according to Access Control List.
Description
Access Control List (ACL) is comprised of a series rules. The operating in the system is
according to the rules of ACL.
ACL is supported by eNodeB. With ACL rules, the eNodeB provides packets filtering
according the packet attributes, such as, source IP addresses, destination IP addresses, source
port numbers and destination port numbers of the packets. The ACL rules can also be based
on the Type of service (TOS), DSCP and address wildcard.
When IPsec is applied to guarantee security of the data flows, operators can select data flows
that need to encrypted and authenticated by IPsec with Access Control List.
Enhancement
 In eRAN3.0
ACL can be utilized by L2 filter; working under L2, ACL rule will filter packages by
VLAN identify. The eNodeB can identify the VLAN ID of the packages, only packages
with own VLAN ID will be allowed.

eNodeB support that IPsec encrypted and authenticate selected data flows with ACL
under IPv6.
Dependency
None
2.3.3.3.2 LOFD-00301402 Access Control List (ACL) Auto Configuration
Availability
This feature is
Summary
This feature automatically creates access control list (ACL) rules for operation and
maintenance (O&M) data, service data, signaling data, data from the Certificate Authority
(CA), data from the security gateway (SeGW), and clock data. The automatic ACL rule
creation simplifies whitelist configuration for the packet filtering function.
Benefits
This feature reduces the complexity of configuring the packet filtering function.
Description
 Enables the eNodeB to obtain the IP addresses and port numbers of peer NEs from the
managed object (MO) information about O&M link, service link, signaling link, CA,
SeGW, and clock. Using the IP addresses and port numbers, this feature automatically
creates ACL rules. These automatically created ACL rules can ensure that the eNodeB
provides basic services. Auto-configured ACLRULE will use some range ID, currently
the range of ID is [0, 65535], ID of auto-configured ACLRULE is [50000, 60000]. So
before activating this feature, need reserve [50000, 60000] for auto-configured
ACLRULE. In addition, need check if ACLRULE number specification satisfies network
requirements or not.
 Updates related ACL rules when MO information changes.
When an O&M function is enabled at the peer end, not at the local end, the eNodeB cannot
obtain the IP address of a maintenance packet. To ensure information security, ACL rules for
maintenance data must be manually created.
Enhancement
None
Dependency
 eNodeB

None
 UE
None
None
 CN
None
 OSS
None
 Other Features
This feature requires LOFD-00301401 ACL.
 Others
None
2.3.3.4 LOFD-003015 Access Control based on 802.1x
Availability
This feature is:
Summary
eNodeBs can use device certificates to authenticate the transport network using IEEE 802.1x
(port-based network access control).
Benefits
This feature provides digital certificate authentication between an eNodeB and a LAN switch
to improve network security.
Description
IEEE 802.1x uses the physical access characteristics of IEEE 802 LAN infrastructure to
provide a means of authenticating and authorizing devices attached to a LAN port that has
point-to-point connection characteristics, and of preventing access to that port in cases where
the authentication and authorization process fails.
The authentication and authorization of IEEE 802.1x use the framework of Extensible
Authentication Protocol (EAP) and refer to the authentication architecture of the eNodeB,
LAN switch, and RADIUS server.

Figure 2-32 eRAN 802.1x application scenario
Before the authentication and authorization process completes, only Extensible Authentication
Protocol over LAN (EAPoL) packets can pass through the LAN switch. All other packets will
be dropped by the LAN switch.
Enhancement
None
Dependency
The peer device must support IEEE 802.1x.
 Core network
The core network equipment must support IEEE 802.1x.
 Other features
This feature depends on LBFD-003010 Public Key Infrastructure (PKI).
2.3.4 IPsec
Overview
To address the increasing severity of network security threats, Huawei has designed and
deployed SingleRAN networks to provide multi-plane and multi-layer security protection
against various threats and attacks. This design is in accordance with the security model
defined in ITU-T X.805.
The IPsec feature package protects radio equipment and network communications against
security attacks from insecure transport networks.
Applications
The IPsec feature package is applicable to transport network protection, coverage
improvement, reliability enhancement, and quality improvement. The following table
describes these features and related applications.

ation
Transpo LOFD-003009 IPsec The move to IP-based networks has improved
rt MLOFD-003009 IPsec network performance and reduced network
network deployment costs. However, various threats and


ation
protecti vulnerabilities specific to IP networks still exist.
on Before IPsec was introduced, base stations
transmitted IP-layer data in plaintext, but packets
transmitted on an insecure network can be tampered
with or otherwise accessed without proper
authorization. Huawei base stations use IPsec tunnels
to help protect against such malicious attacks,
ensuring the secure transmission of data.
IPsec provides transparent, end-to-end security
services for IP networks to protect against potential
cyber-attacks.
LOFD-003024 IPsec Huawei base stations use IPsec tunnels to protect data
for IPv6 transmitted over IPv6 networks.
MLOFD-003024 IPsec
for IPv6
Coverag LOFD-081281 eNodeB When the base station serves to initiate IPsec
e Supporting IPsec redirection, the IPsec redirection feature achieves
improve Redirection load balancing between SeGWs and simplifies SeGW
ment MLOFD-081281 network planning.
eNodeB Supporting
IPsec Redirection
LOFD-111203 eNodeB If no PKI system is deployed on an operator's
Supporting Digital network, the base station cannot use an
Certificate Whitelist operator-issued device certificate to access the
Management operator's network. The base station must then use
MLOFD-111203 the digital certificate whitelist management function
eNodeB Supporting to access the operator's network.
Digital Certificate
Whitelist Management
Reliabili LOFD-070211 IPsec The IPsec Redundancy Among Multiple SeGWs
ty Redundancy Among feature uses IKE DPD to detect the status of the IPsec
enhance Multiple SeGWs tunnels between the base station and all the SeGWs.
ment MLOFD-070211 IPsec If the active IPsec tunnel between the base station
Redundancy Among and the primary SeGW is faulty, the base station
Multiple SeGWs attempts to establish a standby IPsec tunnel with a
secondary SeGW. This creates IPsec redundancy
among multiple SeGWs.
LOFD-003019 IPsec The IPsec Tunnel Backup feature enables a base
Tunnel Backup station to establish primary and secondary IPsec
MLOFD-003019 IPsec tunnels with two SeGWs, respectively. If the primary
Tunnel Backup IPsec tunnel is faulty, services are switched over to
the secondary IPsec tunnel, which improves
reliability.
Quality LOFD-121213 Direct If an IPsec tunnel is established over the X2 interface
improve IPsec between two eNodeBs through an SeGW, the X2
ment interface cannot meet stringent transmission delay


ation
requirements. This requires that a direct IPsec tunnel
be established between the eNodeBs to meet the
transmission delay requirements.
Value
 Transport network protection
The following features help protect transport networks:
− IPsec provides transparent, end-to-end security services for IP networks to protect
against potential cyber-attacks.
− The IPsec for IPv6 feature secures IPv6 transport networks.
The following features help improve network security:
− The eNodeB Supporting IPsec Redirection feature fulfills the customer's security
requirements when multiple SeGWs are deployed on the network.
− The Digital Certificate Whitelist Management feature meets the customer's security
requirements when no PKI system is deployed on the network.
 Reliability enhancement
In IPsec networking, the IPsec Redundancy Among Multiple SeGWs and IPsec Tunnel
Backup features provide cold and hot backup for IPsec tunnels, improving service
reliability.
 Quality improvement
Compared with IPsec tunnels to the SeGW, X2 interfaces with direct IPsec tunnels
effectively reduce transmission path alternations of X2 interfaces, decrease the X2
interface latency, and reduce the bandwidth consumption of the transport network.
2.3.4.1 LOFD-003009 IPsec
Availability
This feature is:
Summary
IPsec authenticates and encrypts data transmitted between network elements at the IP layer.
Benefits
This feature provides security mechanisms, including confidentiality, integrity, and
authentication for data transmission between network elements at the IP layer.

Description
The following figure shows the IPsec topology.
Figure 2-33 IPsec
IPsec provides a framework of open standards dealing with data confidentiality, integrity, and
authentication between communicating peers. IPsec provides these security features at the IP
layer. It uses IKEv1 and IKEv2 to negotiate protocols and algorithms based on the local
policy, and to generate the encryption and authentication keys used by IPsec.
IPsec can be used to protect one or more connections between two eNodeBs, between an
eNodeB and an S-GW/MME, or between an SeGW and an eNodeB.
The key characteristics of IPsec are:
 Two encapsulation modes
− Transport mode
− Tunnel mode
 Two security protocols
− Authentication Header (AH)
− Encapsulation Security Payload (ESP)
 Multiple encryption methods
− NULL
− DES
− 3DES
− AES
 Multiple integrity protection methods
− HMAC_SHA-1
− AES-XCBC-MAC-96
− SHA256
− HMAC_MD5

Enhancement
 In eRAN2.0, IPsec requires the LOFD-003010 Public Key Infrastructure (PKI) feature
for authentication.
 In eRAN3.0, two new integrity protection algorithms are supported:
AES-XCBC-MAC-96 and SHA256.
Dependency
An SeGW supporting IPsec is required.
 Other features
If IPsec uses digital certificate authentication, IPsec depends on the LBFD-003010
Public Key Infrastructure (PKI) feature.
2.3.4.2 LOFD-003019 IPsec Tunnel Backup
Availability
This feature is:
Summary
This feature enables a pair of primary and secondary IPsec tunnels to be established between
one eNodeB to two SeGWs. This improves the reliability of eNodeB transport links protected
by IPsec.
Benefits
Without this feature, an eNodeB can establish an IPsec tunnel with only one SeGW. If this
tunnel is broken, data will not be protected by IPsec. This feature allows the use of a pair of
primary and secondary IPsec tunnels between the eNodeB and two SeGWs. If one IPsec
tunnel is faulty, data is transmitted over the other IPsec tunnel, improving reliability.
Description
The LTE network is divided into trusted and untrusted domains to ensure service security. A
SeGW is deployed between the trusted and untrusted domains. The network elements in the
CN stay in the trusted domain. An IPsec tunnel is used to protect the data transmitted between
the SeGW and the eNodeB in the untrusted domain.
When two SeGWs are deployed, the eNodeB can establish one primary IPsec tunnel and one
secondary IPsec tunnel to the SeGWs. In normal conditions, both IPsec tunnels are available
for data transmission. In the uplink, the eNodeB selects the primary IPsec tunnel based on the
priorities of IPsec tunnels. In the downlink, the eNodeB can receive data on both the primary
and secondary IPsec tunnels. The SeGWs can send data to the eNodeB on either IPsec tunnel.
The eNodeB uses BFD to check the connectivity between itself and the SeGWs. If the
primary IPsec tunnel is broken, the eNodeB will switch the uplink data to the secondary IPsec
tunnel, and the SeGWs should be able to switch downlink data to the secondary IPsec tunnel.

Enhancement
None
Dependency
 Core network
The SeGWs in the CN must support this feature.
 Other features
LOFD-003009 IPsec
2.3.4.3 LOFD-003024 IPsec for IPv6
Availability
This feature is
Summary
IPsec is used to provide security service at IP layer, in both IPv4 and IPv6 environment. The
security service secures S1\X2 signaling plane data, user plane data, OM plane data and
synchronization plane data transmission.
This feature provides IPsec for IPv6 protocol stack which can secure the data flow from or to
eNodeB.
Benefits
This feature provides the security service include confidentiality, integrity, and peer
authentication and anti-replay between participating peers at the IPv6 protocol stack, IPsec for
IPv6 can enhance the security when eNodeB data is transported on the un-trust IPv6 transport
network.
Description
Internet Protocol Security (IPsec) is a protocol suite for securing Internet Protocol (IP)
communications by authenticating and encrypting each IP packet of a data stream. IPsec also
includes protocols for establishing mutual authentication between endpoints at the beginning
of the session and negotiation of cryptographic keys to be used during the session.
The key characteristics of IPsec for IPv6 are same as the IPsec on IPv4:
 Two encapsulation modes: transport mode and channel mode
 Two security protocols: Authentication Header (AH) and Encapsulation Security Payload
(ESP)
 Main encryption methods: NULL, Data Encryption Standard , Triple Data Encryption
Standard, and Advanced Encryption Standard

Main integrity protection methods: HMAC_SHA-1 and HMAC_MD5, where HMAC stands
for Hash Message Authentication Code, SHA stands for Secure Hash Algorithm, and MD5
stands for Message Digest 5
IPsec for IPv6 is developed in conjunction with IPv6 and is therefore mandatory in all
standards -compliant implementations of IPv6 (but its implementation is an optional extension
to IPv4).
When the network equipment (host or security gateway) supports IPv6, IPsec for IPv6 can be
used to protect data flows between a pair of hosts (e.g. computer users or servers), between a
pair of security gateways (e.g. routers or firewalls), or between a security gateway and a host.
In LTE network, IPsec for IPv6 can be used to protect one or more data flows between two
eNodeBs, between eNodeB and SGW/MME, or between eNodeB and security gateway.
Enhancement
None
Dependency
 CN
This feature depends on the IPsec tunnel peer Network Equipment (eg. Security gateway,
MME, and SGW) supporting IPsec on IPv6.
 Other features
This feature depends on LOFD-003009 IPsec.
2.3.4.4 LOFD-070211 IPsec Redundancy Among Multiple SeGWs
Availability
This feature is:
Summary
This feature uses the dead peer detection (DPD) function to detect the status of IPsec tunnels
between an eNodeB and all SeGWs. If the IPsec tunnel between the eNodeB and the primary
SeGW is faulty, the eNodeB attempts to establish a standby IPsec tunnel with a secondary
SeGW. This implements IPsec redundancy among multiple SeGWs.
Benefits
 Quick service recovery
 Improved reliability of secure networks
 Reduced economic losses for operators

Description
 When an eNodeB detects that the IPsec tunnel between the eNodeB and the primary
SeGW is faulty, the eNodeB attempts to initiate an IKE negotiation with each secondary
SeGW sequentially, until the eNodeB establishes a temporary IPsec tunnel. Then, the
eNodeB switches its services to the temporary IPsec tunnel.
 If the IPsec tunnel between the eNodeB and the primary SeGW is restored, the eNodeB
switches the services back to the IPsec tunnel and removes the temporary IPsec tunnel.
This feature applies to intra- or inter-city secure networks.
Enhancement
 SRAN11.1
The IPsec Redundancy Among Multiple SeGWs feature enables the base station to
attempt to establish a standby IPsec tunnel with a secondary SeGW if the active IPsec
tunnel between the base station and the primary SeGW is faulty. In this situation,
multiple base stations may simultaneously initiate negotiations with a secondary SeGW,
causing traffic storms on the secondary SeGW. To stagger the time base stations initiate
IKE negotiations with a secondary SeGW, the IPSECSOWAITTIME and
IPSECSORANDTIME parameters have been added. The IPSECSBRANDTIME
parameter has been added to stagger the time base stations switch back to the primary
SeGW.
Dependency
 eNodeB
Only the Ethernet ports on the UMPT, LMPT, and UTRPc support this feature.
 UE
None
None
 Core network
None
 OSS
None
 Other features
− Prerequisite features
LOFD-003009 IPsec
− Mutually exclusive features
LOFD-003019 IPsec Tunnel Backup
 Others
− Multiple SeGWs must be deployed on a network, and all the routes from the
eNodeB to these SeGWs must be reachable.
− The SeGWs must support generation of internal dynamic routes based on IPsec
security associations (SAs).
− The E8000E and SeMG9811 must support the deployment of SeGWs.

2.3.4.5 LOFD-081281 eNodeB Supporting IPsec Redirection
Availability
This feature is
Summary
This feature supports deploying the IPsec redirection function on the network. When the
IKEv2 redirection function is enabled for the eNodeB and SeGW, the SeGW decides whether
to continue to provide services for the eNodeB or initiate a redirection to a new SeGW
according to the redirection policy. If the eNodeB receives a redirection packet from the
SeGW, the eNodeB initiates IKE negotiation with a new SeGW and establishes a new IPsec
tunnel.
Benefits
 Easier SeGW capacity expansion and lower network configuration complexity
 Higher SeGW reliability
Description
This feature allows redirecting an eNodeB from one security gateway to another if the load
decision conditions are met or if maintenance is required, so as to improve IPsec tunnel
reliability.
This feature enables an eNodeB to implement IKE negotiation with different SeGWs using
the same IKE configuration and to establish an IPsec tunnel, thereby simplifying SeGW
network configuration and reducing network configuration complexity. This feature has the
following characteristics:
 Compatible with the RFC 5685 protocol, the eNodeB can only serve as an initiator.
 Supports initiating a redirection during the IKEv2 Initial exchange phase and
IKE_AUTH exchange phase for IKEv2.
 During the redirection, the eNodeB supports indicating the target SeGW only through
IPV4.
 Supports setting the maximum number of redirections within five minutes so as to
eliminate the possibility that the eNodeB cannot provide services normally because it is
repeatedly redirected due to a configuration error or a malicious attack.
 IPsec redirection is not supported when an IPsec link is established using DHCP.
Enhancement
None
Dependency
 eNodeB

The eNodeB must be configured with the UMPT, UMDU, LMPT or UTRPc board to
support this feature.
 UE
None
The SeGW must support RFC 5685 IKEv2 Redirect and IPsec SA-based internal
dynamic route generation.
 CN
None
 OSS
None
 Other Features
− Prerequisite Feature:
LOFD-003009 IPsec
− Mutually Exclusive Feature:
LOFD-003019 IPsec Tunnel Backup
 Others
None
2.3.4.6 LOFD-111203 eNodeB Supporting Digital Certificate Whitelist

Management
Availability
Summary
This feature validates the accessed devices through the digital certificate whitelist
management function provided by the eNodeB and SeGW if the PKI system is not deployed
on the network and the Huawei-issued device certificate is used for network access. The
eNodeB and SeGW support deploying the digital certificate whitelist management function.
The system verifies whether the Common Name carried by the IKE message is in the whitelist
during IKE negotiation. If yes, IKE negotiation and IPsec tunnel setup are allowed. If not,
IKE negotiation is disallowed and IPsec tunnel setup fails. In this way, only the devices in the
digital certificate whitelist can access the network, thereby ensuring network security.
Benefits
This feature allows operators to use the digital certificate whitelist management function to
ensure access security without deploying the PKI system on the network.
Description
If the PKI system is deployed, the eNodeB applies for a certificate from the PKI system, and
the PKI system performs verification. Only verified eNodeBs can access the network. If the
PKI system is not deployed, both the eNodeB and SeGW use the digital certificate whitelist
management function to ensure that the accessed devices are in the whitelist.

The eNodeB supports the following functions:

 Digital certificate whitelist configuration: The eNodeB supports updating the digital
certificate whitelist in file mode with the following configuration modes: batch whitelist
configuration and single whitelist configuration.
 Access control: The system verifies whether the certificate name carried by the IKE
message is in the whitelist during IKE negotiation. If yes, IKE negotiation and IPsec
tunnel setup are allowed. The verification is controlled by a switch. If this switch is
turned on and the digital certificate whitelist is configured, the verification is performed.
If this switch is turned off or the digital certificate whitelist is not configured, the
verification is not performed.
The verification is not performed during IKE negotiation for PnP deployment.
Enhancement
None
Applicable to
Y Y Y
Dependency
 eNodeB
Only the UMPT, BBU3910A, LMPT, and UTRPc support this feature.
 UE
None
The peer end must be a Huawei SeGW that supports digital certificate whitelist
management.
 CN
None
 OSS
None
 Other features
LOFD-003009 IPsec
None
 Others
None

2.3.4.7 LOFD-121213 Direct IPsec
Availability
This feature is:
Summary
This feature enables a direct IPsec tunnel to be established between eNodeBs over the X2
interface, which secures data transmitted over the X2 interface and reduces X2 interface
delay.
Benefits
IP RAN-based inter-site coordinated services have high requirements on X2 interface delay.
In an IPsec network, the X2 interface delay is long if a security gateway (SeGW) is used. In
such a network, Direct IPsec can effectively reduce transmission path length and X2 interface
delay, thereby improving the provisioning ratio of IP RAN-based inter-site coordinated
services.
Description
The Direct IPsec feature depends on the IPsec and Self-configuration features, because an X2
self-setup procedure must be performed to establish a direct IPsec tunnel. Compared with the
IPsec tunnel between the eNodeB and the SeGW, the direct IPsec tunnel features a shorter
transmission path. Therefore, X2 interface delay is reduced, which improves the provisioning
ratio of IP RAN-based inter-site coordinated services in IPsec networks.
The following figure shows a direct IPsec network topology.
After Direct IPsec is enabled, an X2 interface may have multiple IPsec tunnels. X2 data flows
can be preferentially transmitted over the direct IPsec tunnel.
This feature supports configuration of a blacklist for direct IPsec tunnels. Once an eNodeB is
added to the blacklist, direct IPsec self-setup will not be triggered for the eNodeB.
Enhancement
None

Dependency
 eNodeB
The eNodeB must be equipped with a UMPT, UTRPc, or UMDU board.
 Other features
LBFD-002035 Self-configuration
LOFD-003009 IPsec
None
2.3.5 RAN Sharing

Overview
RAN sharing means the sharing of network infrastructure or network equipment among
multiple operators (or with third parties).
The RAN sharing features include:
 RAN Sharing with Common Carrier
 RAN Sharing with Dedicated Carrier
 Hybrid RAN Sharing
The sharing of network infrastructure and network resources helps decrease costs and
improve resource usage.
Applications
RAN sharing allows for the sharing of hardware or spectrum resources across single- and
multi-mode networks. The features in this package provide idle mode management, resource
management, and different types of load sharing. Each different scenario will require the use
of different features. The following table lists the features required in for each scenario.

cation
Netwo LOFD-001036 RAN Sharing This feature allows operators to share the same
rk with Common RAN. They can share carrier resources under the
sharing Carrier/MLOFD-121251 same eNodeB.
NB-IoT RAN Sharing with
Common Carrier
LOFD-001037 RAN Sharing This feature allows operators to share eNodeB
with Dedicated hardware resources but not spectrum resources.
Carrier/MLOFD-121252
NB-IoT RAN Sharing with
Dedicated Carrier
LOFD-070206 Hybrid RAN Huawei eNodeBs has supported RAN Sharing
Sharing with Common Carrier and RAN Sharing with
Dedicated Carrier since eRAN2.0. As LTE has
evolved and RAN sharing scenarios have become


cation
increasingly diverse, each of these two features
has developed their own constraints. In RAN
Sharing with Common Carrier, each cell can
support multiple operators, but the primary
PLMN ID of cells on the same eNodeB must be
the same. In RAN Sharing with Dedicated
Carrier, the PLMN IDs of cells on the same
eNodeB can differ, but each cell supports only
one operator.
Hybrid RAN Sharing eliminates such constraints
by allowing each cell to support multiple
operators and to have different primary PLMN
IDs.
LOFD-001086 RAN Sharing This feature allows up to six operators to share a
by More Operators RAN running on Huawei eNodeBs. Without this
feature enabled, the eNodeBs can support no
more than four.
Idle LOFD-001112 MOCN In RAN Sharing with Common Carrier or Hybrid
Mode Flexible Priority Based RAN Sharing, MOCN Flexible Priority Based
Manag Camping Camping allows for the configuration of cell
ement reselection priorities for different frequencies and
RATs on a per operator basis.
Resour LOFD-070213 Fair User In RAN sharing, the proportions of the licensed
ce Sharing number of RRC_CONNECTED UEs to the total
manag number of RRC_CONNECTED UEs that each
ement operator can use and share can be configured on
eNodeBs to achieve static resource allocation and
dynamic resource sharing.
Load LOFD-070204 Operator In RAN sharing, each operator can balance
Balanc Load Based Intra-LTE MLB network load according to its own load status.
ing
Flexibl LOFD-070210 Multi Previously in RAN sharing, operators that share
e User Operators SPID Policy an eNodeB must jointly plan the SPIDs to
Steerin prevent SPID range overlap among operators.
g With this feature, operators that share an eNodeB
can specify their own SPID ranges without the
need to negotiate with each other.
Value
 Network construction
RAN sharing among multiple operators can:
− Resolve the problem of limited spectrum resources.
− Make the acquisition of new sites and other resources easier.
− Reduce the capital expenditure (CAPEX) and operating expense (OPEX).

− Decrease the time required for network construction.

− Expand network coverage.
 Idle mode management
In RAN Sharing with Common Carrier or Hybrid RAN Sharing, operators can be
configured with different camping policies for RRC_IDLE UEs.
 Resource management
In RAN sharing, the licensed number of RRC_CONNECTED UEs can be flexibly
shared to improve resource usage.
 Load balancing
In RAN sharing, each operator can implement load sharing according to its own network
status, which optimizes network resource usage, increases system capacity, decreases the
possibility of system overload, and increases access success rate.
2.3.5.1 LOFD-001036 RAN Sharing with Common Carrier
Availability
This feature is:
Summary
The eNodeB supports multiple operators sharing the same Radio Access Network (RAN),
where the operators use common carriers in the same eNodeB.
Benefits
Operators can share RAN resources to reduce capital expenditure (CAPEX) and operating
expense (OPEX).
Description
The multi-operator core network (MOCN) solution enables operators to share RAN resources,
including spectrum and baseband resources. Different operators share the same cell, and each
eNodeB connects to the core networks of all operators. The system information broadcast in
each shared cell contains the PLMN ID of each operator (up to 4) and a single tracking area
code (TAC), which is valid within all the PLMNs sharing the radio access network resources.
The architecture is depicted as follows.

Figure 2-34 RAN sharing with common carrier
An LTE UE supporting MOCN can read up to four PLMN IDs and select one of the PLMNs
as its serving PLMN during its first attach procedure after it is powered on. The UE informs
the eNodeB of the selected PLMN ID. The eNodeB then selects an appropriate MME
according to the PLMN ID indicated by the UE.
The MOCN solution allows operators to share an OSS, which is linked to different NMSs
through different interfaces.
The shared eNodeB and non-shared eNodeB can be connected to each other. In the shared
area, a UE can be handed over from one shared eNodeB to another one. If UE moves to a
non-shared area, the eNodeB will select an appropriate neighboring cell for the handover. For
example, the same operator's network may be preferentially considered. The interworking
between different RATs may be required during the handover.
The MOCN solution has the following characteristics:
 Multiple PLMN IDs are broadcast in a shared cell. The core networks are separated.
 The logo and name of the corresponding operator are displayed.
 The shared OSS connects to different NMSs through northbound interfaces.
 A maximum of four operators are supported.
Enhancement
 eRAN2.1
The enhancements are as follows:
The dynamic radio resource management function is introduced.
Benefits
This function guarantees the fairness and flexibility in the MOCN solution. All radio
resources can be shard dynamically and fairly among operators.
Description
This function meets the general principles of fair resource sharing described as follows:
a. Balance between maximum system throughput and fair sharing of resources among
MOCN operators.
b. Any unused resources shall be used by other operators.

c. Fair sharing of resources applies both in the uplink and downlink.

Operators sharing a network may have different service models and different price
models. The QoS parameters can be totally different. In high load situations where this
function is disabled, the operator with higher QoS requirements will occupy more radio
resources because the dynamic scheduling algorithm will balance system throughput and
user fairness based on QCIs.
The dynamic radio resource management function guarantees fairness among operators.
The priority of each operator is calculated based on the RB usage and predefined RB
ratio. The scheduling is first performed among operators according to the operators'
priority. Then, it is performed within each operator.
Preemption algorithm in admission control is also enhanced in this function. Service of
operator A can preempt resources of operator B only when RB usage of operator A is less
than its predefined RB ratio and RB usage of operator B is greater than its predefined
ratio.
 eRAN3.0
Four counters are introduced to measure the RB usage for each operator.
a. Downlink RB usage belonging to its own quota
b. Uplink RB usage belonging to its own quota
c. Downlink RB usage belonging to other operator's quota
d. Uplink RB usage belonging to other operator's quota
 eRAN6.0
An S1 interface can connect to MMEs of multiple PLMNs. An eNodeB can connect to
either multiple MMEs included exclusively in PLMNs or an MME shared by multiple
PLMNs over the S1 interface.
 eRAN11.1
− RBs can be shared on a per operator group basis. This function is an enhancement
of operator-specific RB sharing. Some operators may have a partnership with each
other. When three or more operators share cells, the partners can form a resource
group that can be represented by a member operator, and RBs are preferentially
shared by the resource group. If there are still unused RBs, they can be shared by
other operators. This function ensures that resources are equally allocated to
operators in the same resource group.
− The interval for cells to broadcast PLMN IDs in a round robin manner can be
configured on a per operator basis. In RAN sharing with common carriers, a
fairness guarantee for roaming needs to be provided because roaming service brings
considerable profits to operators. According to section 4.4 in 3GPP TS 23.122
V8.5.0, a roaming UE randomly selects a PLMN ID if there is not a prominent
PLMN (for example, in terms of signal quality). It is more likely that some UEs
preferentially select the PLMN ID at the top of the PLMN list when they roam to a
cell shared by operators. In versions earlier than eRAN11.1, PLMN IDs are
broadcast in a round robin manner at the same interval. With this function in
eRAN11.1, the interval can be specified on a per operator basis.
Dependency
 Other features
This feature requires the LBFD-001018 S1-flex feature.
If a shared eNodeB is connected to multiple non-shared MMEs, RAN Sharing with
Common Carrier requires the LBFD-001018 S1-flex feature. If a shared eNodeB is

connected to a shared MME, RAN Sharing with Common Carrier does not require any
feature.
2.3.5.2 LOFD-001037 RAN Sharing with Dedicated Carrier
Availability
This feature is:
Summary
This feature allows operators to share the same RAN but not spectrum resources.
Benefits
Operators can share RAN resources to reduce CAPEX and OPEX.
Description
Huawei eNodeBs supports RAN sharing, which is a part of network sharing. In RAN Sharing
with Dedicated Carrier, operators share only hardware resources but not spectrum resources.
The shared eNodeB can connect to a shared MME or MMEs exclusively owned by operators.
Operators owning exclusive spectrum resources share the RAN in a specific area. The TACs
of the cells of different operators in this area differ from each other. The architecture is
depicted as follows.
Figure 2-35 RAN sharing with dedicated carrier
When a UE accesses a cell, the eNodeB routes this UE to the core network of its operator
according to the cell on which the UE previously camps. Different cells correspond to
different operators. If the S1-flex feature is enabled, the eNodeB selects an MME for the UE

based on the globally unique MME identifier (GUMMEI), which is a component in the
globally unique temporary identity (GUTI) allocated to this UE.
This feature enables the shared OSS of the primary operator to connect to NMSs of different
operators through different interfaces. Cell-level fault and performance management data is
reported on a per operator basis.
A shared eNodeB can connect to a non-shared eNodeB. UEs can be handed over from a
shared eNodeB to a non-shared eNodeB without constraints. If an operator has an exclusively
owned network in the non-sharing area, UEs can be handed over only to this network, even if
it is not an LTE network.
This feature has the following characteristics:
 The PLMN ID of each operator is broadcast on its respective carrier.
 The logo and name of the corresponding operator are displayed.
 Cell-level fault and performance management data is reported on a per operator basis.
The shared OSS connects to NMSs of different operators through different interfaces.
 License configurations are managed on a per operator basis.
 This feature is activated or deactivated on a per operator basis.
Enhancement
 eRAN6.0
An S1 interface can connect to MMEs of multiple PLMNs. An eNodeB can connect to
either multiple MMEs included exclusively in PLMNs or an MME shared by multiple
PLMNs over the S1 interface.
Dependency
 Other features
This feature requires the LBFD-001018 S1-flex feature.
If a shared eNodeB is connected to multiple non-shared MMEs, RAN Sharing with
Dedicated Carrier requires the LBFD-001018 S1-flex feature. If a shared eNodeB is
connected to a shared MME, RAN Sharing with Dedicated Carrier does not require any
feature.
2.3.5.3 LOFD-001086 RAN Sharing by More Operators
Availability
This feature is
Summary
This feature allows up to six operators to share an eNodeB in RAN sharing mode.

Benefits
This feature greatly reduces the capital expenditure (CAPEX) and operating expense (OPEX)
of the operators.
Description
An eNodeB can work in two RAN sharing modes: RAN sharing with common carriers or
RAN sharing with dedicated carriers. In either of the modes, up to six operators can share an
eNodeB that is connected to all the evolved packet core (EPC) networks of these operators.
Such an eNodeB can be managed by a shared element management system (EMS), and the
EMS can be connected to the network management systems (NMSs) of the operators through
different northbound interfaces.
In RAN sharing with dedicated carriers mode, the operators can share only the hardware of an
eNodeB. In RAN sharing with common carriers mode, the operators can share both the
hardware and cells of an eNodeB. A maximum of six operators can share the cells of an
eNodeB. In shared cells, system information block type 1 (SIB1) contains a maximum of six
PLMN IDs in the PLMN ID list.
Enhancement
None
Dependency
 Other features
LOFD-001036 RAN Sharing with Common Carrier or LOFD-001037 RAN Sharing with
Dedicated Carrier
2.3.5.4 LOFD-001112 MOCN Flexible Priority Based Camping
Availability
This feature is
Summary
In RAN sharing with common carriers, absolute cell-reselection priorities of frequencies are
broadcast in system information without distinguishing between operators. With this feature,
operator-specific cell-reselection priorities can be specified for intra- or inter-RAT
neighboring frequencies.
Benefits
This feature helps operators implement their own camping policies for UEs in idle mode.

Description
The cell-reselection priority of an intra-RAT or inter-RAT neighboring frequency can be set
for different operators, which are identified by its own PLMN IDs. If an operator-specific
cell-reselection priority is set, the priority is used as a dedicated priority of the frequency.
If dedicated priorities are set, the eNodeB delivers the corresponding priority to the UE in the
information element (IE) IdleModeMobilityControlInfo in the RRC Connection Release
message.
Enhancement
None
Dependency
 Other features
This feature requires the LOFD-001036 RAN Sharing with Common Carrier feature.
2.3.5.5 LOFD-070206 Hybrid RAN Sharing
Availability
This feature is
Summary
Huawei eRAN2.0 and later versions support both RAN sharing with common carriers and
RAN sharing with dedicated carriers, but the flourishing of LTE networks calls for more
diversity in RAN sharing. Additionally, RAN sharing with common carriers and RAN sharing
with dedicated carriers have their own restrictions. For example, RAN sharing with common
carriers requires that the cells under a shared eNodeB must have the same primary PLMN ID,
and RAN sharing with dedicated carriers disallows multiple operators to share a cell. The
Hybrid RAN Sharing feature eliminates such restrictions by allowing multiple operators to
share a cell and allowing shared cells to have different primary PLMN IDs.
Benefits
Hybrid RAN Sharing curtails the capital expenditure (CAPEX) and operating expense (OPEX)
of operators by allowing flexible RAN sharing and accelerates the pace of network
deployment.
Description
Hybrid RAN Sharing allows operators to share RAN resources when all the following
conditions are met:
 Each eNodeB operates on two or more frequencies.
 At least one frequency is shared by operators.

 Two or more cells have different primary PLMN IDs.

The following are two typical application scenarios of Hybrid RAN Sharing:
 A shared eNodeB operates on both common and dedicated frequencies. For example,
operators A and B share frequency 1 (A being the primary operator), and operator B uses
a dedicated frequency (frequency 2), as shown in figure below.
Figure 2-36 Shared eNodeB operating on both common and dedicated frequencies
 Operators share different operating frequencies of an eNodeB. For example, operators A

and B share frequency 1 (A being the primary operator), and operators C and D share
frequency 2 (C being the primary operator), as shown in figure below .
Figure 2-37 Operators sharing different frequencies
In Hybrid RAN Sharing scenarios, the eNodeB can be shared by up to four operators and
configured primary and secondary operator information for each cell. The procedure of user's
PLMN ID selection is as below:
1. eNodeB broadcast the primary and secondary PLMN ID in system information.

2. UE get the PLMN ID list in SIB1 of shared cell and select one proper PLMN as its
serving PLMN
3. eNodeB establish the connection to particular MME for a UE according to the PLMN ID
that UE selected.
In Hybrid RAN Sharing scenarios, related features, resources and OSS management follow
the policies below:
 The feature configuration of a shared cell must keep same between different operators,
which is same as MOCN cell.
 The allocation of cell-specific resources for a shared cell, such PRB resource, are same
as MOCN cell. The eNodeB-specific resources, such as RRC connected user number, are
shared by multiple operators.
 OSS is shared by multiple operators and connected to NMSs of different operators by
different Itf-N interface. The information such as configuration management, fault
management and performance management can be reported individually to different
NMS.
Hybrid RAN Sharing is compatible with RAN sharing with common carriers and RAN
sharing with dedicated carriers. Purchasing the license for Hybrid RAN Sharing eliminates the
need to purchase licenses for RAN sharing with common carriers and RAN sharing with
dedicated carriers.
Enhancement
None
Dependency
 Other features
If a shared eNodeB is connected to multiple non-shared MMEs, LOFD-070206 Hybrid
RAN Sharing is dependent on LOFD-001018 S1-flex. If a shared eNodeB is connected
to a shared MME, LOFD-070206 Hybrid RAN Sharing is not dependent on any feature.
2.3.5.6 LOFD-070204 Operator Load Based Intra-LTE MLB
Availability
This feature is:
Summary
In radio access network (RAN) sharing scenarios, all operators can perform load balancing
based on the load status of respective cells.
Benefits
In RAN sharing scenarios, this feature enables load balancing among cells of an operator
based on the actual cell loads of the operator. This feature provides the following benefits:

 Makes full use of network resources.

 Increases the system capacity.
 Reduces the probability of system overload.
 Increases the access success rate.
Description
In RAN sharing scenarios, this feature is recommended for load balancing among cells of an
operator.
The cell load of an operator can be represented by the following values:
 Physical resource block (PRB) usage of the operator
 Number of synchronized UEs served by the operator in a cell
This feature allows each operator to independently monitor its cell load. If the cell load of an
operator exceeds the specified threshold for load balancing, the eNodeB transfers UEs served
by this operator in the cell to an inter-frequency cell with light load.
Operator-load-based intra-LTE MLB is triggered for an operator when either PRB usage of
the operator or the number of synchronized UEs served by the operator in the cell exceeds the
corresponding specified threshold for load balancing.
Enhancement
 eRAN11.1
Added inter-operator resource sharing. With this function activated, operator-level MLB
can be triggered for an operator. This situation is applicable if both the serving cell's load
and the operator's load meet the related MLB triggering conditions. If the serving cell's
load does not meet the triggering conditions, this feature allows resource sharing among
operators in the serving cell, achieving better utilization of cell resources and decreasing
the number of unnecessary handovers.
Dependency
 Other features
This feature depends on the following features:
a. LOFD-001036 RAN Sharing with Common Carrier or LOFD-070206 Hybrid RAN
Sharing
b. LOFD-070215 Intra-LTE User Number Load Balancing or LOFD-001032
Intra-LTE Load Balancing
 Others
X2 interfaces are preconfigured and support the exchange of load information.
2.3.5.7 LOFD-070213 Fair User Sharing
Availability
This feature is

Summary
In RAN sharing scenarios, users can set the proportion of UEs in RRC_CONNECTED mode
and the resource sharing proportion for each operator.
Benefits
The resources for UEs in RRC_CONNECTED mode can be statically allocated to operators
or dynamically shared among operators.
Description
The idle resources in terms of the permissible number of RRC_CONNECTED UEs can be
shared by one operator to other operators.
When the idle resources of an operator are shared, this operator's newly admitted UEs can
preempt the shared resources to ensure that the operator can use the originally allocated
amount of resources.
Enhancement
None
Dependency
 Other features
LOFD-001036 RAN Sharing with Common Carrier, LOFD-001037 RAN Sharing with
Dedicated Carrier or LOFD-070206 Hybrid RAN Sharing.
2.3.5.8 LOFD-070210 Multi Operators SPID Policy
Availability
This feature is
Summary
eNodeBs support operator-specific subscriber profile ID for RAT/frequency priority (SPID)
policies so that UEs camp on different networks based on their cell reselection priorities.
Benefits
In RAN sharing scenarios, this feature enables operators to customize policies for radio
resource management (RRM), such as camping of UEs in idle mode. Operators can configure
the same SPID range.

Description
An operator registers an SPID (a policy index ranging from 1 to 256) for UEs in a home
subscriber server (HSS) database. Based on the SPID, an eNodeB performs service processing
dedicated to the UEs.
SPID policies can be customized for different operators on an eNodeB. Based on the serving
PLMNs and SPIDs of UEs, operators share eNodeBs, query the local configurations of the
eNodeBs, and enable the eNodeBs to deliver the customized cell reselection policies to UEs.
This feature supports the cell reselection policies that are customized only based on SPIDs.
Different operators can register the same SPID for a UE and can also customize different cell
reselection policies on shared eNodeBs.
Enhancement
None
Dependency
 CN
CN need support SPID.
 Other features
LBFD-00201803 Cell Selection and Re-selection.
LOFD-001054 Flexible User Steering
2.3.6 Small Cell

2.3.6.1 LOFD-001057 Load Balancing based on Transport QoS
Availability
This feature is:
 Not available in macro eNodeBs.
Summary
Usually, the transport capability of a micro eNodeB is weaker than that of a macro eNodeB. It
is possible that the S1 transport capability of the micro eNodeB is insufficient when the
backhaul traffic is heavy. When the S1 load is high, the micro eNodeB triggers mobility load
balancing (MLB) and transfers UEs to other micro and macro cells to decrease the S1 load.
Benefits
This feature reduces the S1 load to prevent congestion.
Description
In some situations of commercial networks, the S1 load of some eNodeBs may be excessively
high and others' low because of UE service differences. In this case, MLB can be triggered.

The micro eNodeB monitors the S1 load and load of neighboring cells at the same time. The
micro eNodeB evaluates the load status and determines whether to transfer UEs to
neighboring cells. When the S1 load of the micro eNodeB is high and the S1 load of a
neighboring eNodeB is low, the micro eNodeB transfers UEs to the neighboring cells. The S1
load is represented by the transport bandwidth usage.
This feature supports only UE transfer to inter-frequency neighboring cells. This feature
applies when multiple LTE carriers have the same coverage area.
Enhancement
None
Dependency
 eNodeB
X2 interfaces must be configured between eNodeBs.
This feature applies only to:
− BTS3202E
− BTS3203E
− BTS3911E
− BTS3912E
 Other features
This feature requires LOFD-001032 Intra-LTE Load Balancing.
2.3.6.2 LOFD-003022 PPPoE
Availability
This feature is
Summary
The Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol for encapsulating
Point-to-Point(PPP) frames inside Ethernet frames. It is used mainly with DSL services where
a host connects to the DSL Modem over Ethernet.
Benefits
By supporting PPPoE, eNodeB could use public IP network for backhaul. The CAPEX could
be saved.
Description
Ethernet networks are frame-based and have no concept of a connection like PPP/HDLC or
circuit like ATM and also lack basic security features to protect against IP and MAC conflicts
and rogue DHCP servers. By using PPPoE, users can virtually dial from one machine to

another over an Ethernet network, establish a point to point connection between them and
then securely transport data packets over the connection.
PPPoE is easily integrated with the current dial-up AAA systems and fits perfectly into the
current ATM backbones. Also pre-paid traffic bucket business models can be created with
PPPoE more easily than with DHCP or multiplexing multiple users with different speed tiers
or QoS through 1 DSL modem or by creating a different login for each static IP purchased by
customers.
Enhancement
None
Dependency
 Other features
This feature depends on LOFD-003009 IPSec.
2.3.6.3 LOFD-003031 Horizon Beam-Width Adjustment
Availability
This feature is
Summary
This feature enables horizontal beamwidth adjustment via active antenna system that supports
horizontal beamforming.
Benefits
Horizontal beamwidth adjustment optimizes network coverage and improves network
performance. In addition, this feature allows operators to remotely adjust the horizontal
beamwidth, improving maintenance efficiency and reducing the operating expense (OPEX).
Description
When multiple arrays of antenna elements are placed horizontally and driven by several TRXs,
the eNodeB supports horizontal beamforming. For a site with this configuration, operators can
use this feature to adjust the horizontal beamwidth by changing the weight values for different
antenna arrays on the horizontal plane.
A narrow beam provides high antenna gains and is suitable for in-depth network coverage,
while a wide beam improves network coverage and service offloading.
The following figure illustrates horizontal beamwidth adjustment. The green ellipse indicates
the beam direction of a wide beam, and the red ellipse indicates the beam direction of a
narrow beam.

Figure 2-38 horizontal beamwidth adjustment
Enhancement
None
Dependency
 eNodeB
This feature is only applicable to BTS3203E with internal antenna.
2.4 O&M
2.4.1 SON
Overview
The self-organizing network (SON) feature package provides measures related to automatic
network management. SON features automatically optimize the network and improve network
performance, improving operation and maintenance (OM) efficiency and reducing the
manpower required by operators.
The SON feature package includes features related to self-configuration and self-optimization.
Self-configuration features automatically configure and manage neighbor relationships,
physical cell identifiers (PCIs), X2 interfaces, and public land mobile network (PLMN) lists.
Self-optimization features adaptively adjust and optimize network parameters based on the
site conditions, thereby improving network performance.
Applications
SON allows the network to configure and optimize itself, automatically. The following table
lists the features in the package and their applications.


ation
Self-co LOFD-002001 This feature instructs UEs to perform ECGI reading to
nfigurat Automatic automatically add, remove, and maintain neighbor
ion Neighbour Relation relationships, significantly decreasing the work required
(ANR) for network optimization.
LOFD-002002 This feature adds and removes neighbor relationships of
Inter-RAT ANR E-UTRAN cells with UTRAN, GERAN, and
CDMA2000 cells; and manages attributes of neighboring
cells.
LOFD-002007 PCI This feature automatically detects PCI conflicts between
Collision Detection two cells when they have the same PCI and are operating
and on the same frequency. It reports PCI conflict alarms for
Self-Optimization the conflicting cells, and reassigns appropriate PCIs. This
prevents the service drop rate from increasing and
prevents PCI conflicts from impacting the handover
success rate.
LOFD-081225 This feature classifies neighbor relationships as either
Neighbor Cell formal or extended, based on the handover statistics. It
Classification manages neighbor relationships based on this
Management classification, improving the OM.
LOFD-081207 When there are too many eNodeBs and too few PCIs,
Specified PCI PCI confusions easily occur, and the handover success
Group-based rate is affected. This feature can be used to resolve this
Neighboring Cell issue when there is a large number of micro eNodeBs are
Management deployed around a single macro eNodeB. Operators can
reserve a specified PCI group for cells served by the
micro eNodeBs and these cells share PCIs within that the
group.
LOFD-110219 Auto This feature is used together with carrier aggregation
Neighbor Group (CA), mobility load balancing (MLB), or dynamic
Configuration enhanced inter-cell interference coordination (eICIC). It
automatically sets the overlap indicators between
neighboring cells based on the measurement event
statistics of the network. This reduces the OM costs
involving in planning and overlap indicator
configuration.
Self-op LOFD-002005 This feature reduces the number of the abnormal
timizati Mobility Robust handovers. It automatically detects abnormal handovers
on Optimization that may have occurred when mobility parameters are set
(MRO) inappropriately in live networks, and optimizes related
parameters accordingly. Abnormal handovers include
premature handovers, delayed handovers, handovers to
wrong cells, and ping-pong handovers.
LOFD-002015 Random access channel (RACH) optimization can
RACH Optimization increase the access efficiency. It can be used when the
random access success rate is low, or to increase the
access efficiency in general. RACH optimization


ation
includes the following measures:
 RACH resource adjustment
 PRACH frequency-domain position adjustment
 PRACH power control parameter adjustment
 PRACH false alarm detection
 PRACH root sequence conflict detection
 Optimization of random access beyond cell radius
Value
 Self-configuration
SON helps configure the network automatically. The eNodeB automatically configures
radio and transport parameters and automatically checks and manages neighbor
relationships. Self-configuration reduces the repetition involved in manual configuration
of many parameters during network deployment, making network construction easier
and less expensive. Self-configuration also improves OM efficiency and reduces
operating expenses (OPEX).
SON self-configuration includes neighbor relationship management, blacklist
management, and auto neighbor group configuration.
− Neighbor relationship management
Features in the SON feature package detect and add missing neighboring cells,
manage and optimize neighbor relationships, detect and remove inappropriate
neighbor relationships, and optimize PCI planning, reducing the cost of OM.
− Blacklist management
The SON feature detects overshooting neighboring cells and place them on a
blacklist automatically, preventing service drops due to handovers to these cells,
and preventing neighboring cells from being repeatedly added and then removed.
− Auto neighbor group configuration
The SON feature package simplifies feature activation for CA, MLB, and eICIC,
improving OM efficiency.
 Self-optimization
SON uses MRO and RACH optimization, adaptively adjusting parameters and
optimizing network performance based on the operating status of network equipment.
− MRO
This feature can reduce the number of intra-frequency ping-pong handovers by up
to 20%.
− RACH optimization
 RACH optimization increases the non-contention-based random access
success rate by 5% to 10%.
 When detection of contention-based random access beyond cell radius is
enabled, PDSCH, PUSCH, and PDCCH overheads increase and the random
access success rate may drop by 16% to 30%.

2.4.1.1 LOFD-002001 Automatic Neighbour Relation (ANR)
Availability
This feature is:
Summary
The automatic neighbor relation (ANR) feature takes advantage of the eNodeB algorithm to
plan and configure neighbor relationships automatically and to rectify incorrect neighbor
relationship configurations. This feature greatly reduces the OPEX for operators by avoiding
human intervention and saving labor work.
Benefits
 Missing or incorrect neighbor relationships can be detected or rectified. Therefore, no
handover failure is caused by missing or incorrect neighbor relationships.
 Physical cell identifier (PCI) conflict detection can be triggered.
Description
ANR can automatically add and update neighbor relationships in Neighboring Relation Tables
(NRTs). However, the manual configuration of NRT's attributes including No handover
indicator and No remove indicator takes priority over the ANR algorithm. To prevent
automatic removal, set the No remove indicator parameter to
FORBID_RMV_ENUM(Forbid ANR Remove) or set the Control Mode parameter to
MANUAL_MODE(Manual Mode)
The following explains the ANR procedure.

Figure 2-39 ANR procedure
The source eNodeB informs the UE which E-UTRA frequency needs to be measured (1).
1. The UE detects that cell B meets the measurement requirements, and it reports the PCI of
cell B to the source eNodeB (2). This report does not include its E-UTRAN Cell Global
Identifier (ECGI). The source eNodeB checks whether the NRT includes the PCI of cell
B.
− If the NRT includes this PCI, the procedure ends.
− If the NRT does not include this PCI, the procedure continues.
2. The eNodeB instructs the UE to use the newly detected PCI to read the ECGI of the
related neighboring cell (3). The eNodeB may need to schedule appropriate idle periods
to allow the UE to read the ECGI of the neighboring cell, as the UE needs to decode the
new cell's BCH to obtain ECGI.
3. When the UE has read the new cell's ECGI, it reports the obtained ECGI to the source
eNodeB (4&5).
4. The source eNodeB decides to add this neighbor relationship and uses the PCI and ECGI
to perform the following operations:
− Searches a transport layer address to the target eNodeB (OM search or MME search
mechanism that is standardized by 3GPP.)
− Updates its NRT
There are two major mechanisms for the eNodeB or cell to detect a new neighboring cell.
 The neighboring cell's PCI is reported to the eNodeB in the measurement report, and
then the eNodeB instructs the UE to read the ECGI of the new neighboring cell.
 The handover request message that the source eNodeB sends to the target eNodeB
contains the UE history information. The UE history information contains the source

cell's ECGI. After receiving the handover request message, the target eNodeB obtains the
PCI, TAC, and frequency of the new neighboring cell from U2000.
After the eNodeB adds the new neighboring cell to an NRT, the PCI conflict detection
procedure can be activated. For details on PCI conflict detection, see LOFD-002007 PCI
Collision Detection & Self-Optimization.
If needed, the eNodeB sets up an X2 interface by using the Automatic Transport Setup
function in the feature LOFD-002004 Self-configuration. When there is no neighbor
relationship between two eNodeBs throughout a specific period, the X2 interface will be
automatically removed.
eNodeBs support periodic ANR (that is, fast ANR). An eNodeB selects and configures UEs to
periodically report the strongest intra-RAT cells. If a UE reports an unknown PCI, the
eNodeB instructs the UE to perform ANR measurements to obtain the corresponding ECGI.
Periodical ANR improves handover performance.
eNodeBs also support intra-RAT event-triggered ANR. Intra-RAT ANR can be triggered by
coverage-based handovers or load-based inter-frequency handovers. If a UE includes an
unknown PCI in a measurement report sent to an eNodeB, the eNodeB instructs the UE to
measure and report the ECGI of the unknown cell.
eNodeBs support ANR with shared cells. If a neighboring cell is shared by operators, ANR
maintains its PLMN list, in addition to the NCL and NRT. This function involves the
procedure of obtaining neighboring cell information from the U2000 and requires the
cooperation of the U2000.
Enhancement
 eRAN2.1
This feature is enhanced with the following administration functions:
The ANR logs now record the key event during the SON process and this information
can be used for query and statistics. Operators can also analyze the log information to
learn the feature running process and key events.
 eRAN6.0
This feature is enhanced with the following functions:
− When the serving cell of a UE and an acquired shared cell are managed by the same
OSS, the serving cell can obtain the serving PLMN list of the acquired cell with the
assistance of the OSS if the UE cannot report the serving PLMN list or the acquired
cell does not broadcast the list.
− ANR can be triggered by inter-frequency load balancing to add an inter-frequency
neighbor.
− When there is no neighbor relationship between two eNodeBs throughout a specific
period, the X2 interface will be automatically removed.
 eRAN6.1
− If an X2 interface is faulty throughout a specified period, the local eNodeB
automatically removes the X2 interface.
− If the number of handovers from a peer eNodeB to a local eNodeB and the number
of handovers from the local eNodeB to the peer eNodeB are both less than the
specified thresholds throughout a specified period, the local eNodeB automatically
removes the X2 interface between the eNodeBs.

− If a local eNodeB receives from a peer eNodeB a request message to remove the X2
interface between the eNodeBs, the local eNodeB removes the X2 interface.
 eRAN7.0
− Optimized automatic neighbor relationship removal: If the number of neighbor
relationships in an NRT has reached its maximum and a new neighbor relationship
needs to be added to the NRT, the eNodeB removes a neighbor relationship with a
neighboring cell that is not measured or to which no handover has been triggered
throughout a specific period. After that, the eNodeB adds the new neighbor
relationship to the NRT.
− Automatic setting of the No HO attribute for neighboring cells: ANR can
automatically set the No HO attribute to FORBID_HO_ENUM for the
neighboring cells whose handover success rates are low. This prevents the impact of
low handover success rates of neighboring cells on the handover success rate of the
entire network.
− More intra-RAT neighbor relationships: A maximum of 256 inter- and
intra-frequency neighbor relationships are supported.
 eRAN8.1
In RAN sharing scenarios, this feature now supports the following functions:
− Cross-U2000 neighboring cell information query: With this function, an eNodeB
can obtain the ECGIs and PLMN lists of cells for adding neighbor relationships to
NRTs.
− Frequency-specific setting of RAN sharing indicators: This controls the way in
which an eNodeB obtains the neighboring cell information from the U2000.
Dependency
 UE
UEs must support this feature.
 OSS
This feature requires the OSS feature WOFD-180600 Automatic Neighbor Relation
Optimization - LTE.
2.4.1.2 LOFD-002002 Inter-RAT ANR
Availability
This feature is
 Applicable to Micro form eRAN3.0.
Summary
The Inter-RAT ANR functionality takes advantage of the eNodeB algorithm to plan, configure
neighboring relations, and revise the incorrect neighboring relations between E-UTRAN and
GERAN/UTRAN/CDMA2000.

Benefits
In LTE system, the Inter-RAT neighboring relations can be automatically added without
human intervention, thus reducing the OPEX of the operator.
Description
Inter-RAT ANR can add neighboring relations in the LTE eNodeB automatically through UE
Inter-RAT measurement.
The Inter-RAT ANR consists of the following functions:
 Measures the existence of the CDMA2000 cell, UTRAN cell, and GERAN cell
 Establishes E-UTRAN -> other RAT neighboring relations inside the LTE eNodeB
 Establishes E-UTRAN -> other RAT mobility constraints (for example, operator
mobility limitation policy)
The Inter-RAT ANR process is described as follow:
Figure 2-40 Inter-RAT ANR function
The eNodeB serving cell A has an ANR function. During a normal call procedure, the eNodeB
instructs each UE to perform measurements and detect cells on other RATs. The eNodeB may
use different policies for instructing the UE to perform measurements and then to report them
to the eNodeB.

 The eNodeB instructs the UE to search neighboring cells in the target RATs. The
eNodeB may need to schedule appropriate gaps periods to allow the UE to scan all cells
in the target RATs/frequencies.
 The UE reports the Phy-CID (Physical Cell ID) of the detected cells in the target RATs
and their respective signal quality. The carrier frequency and Primary Scrambling Code
(PSC) define the Phy-CID in case of UTRAN cell, and the Band Indicator + BSIC +
BCCH ARFCN in case of GERAN cell.
 When the eNodeB receives UE's report containing Phy-CIDs of cells that are not already
in Inter-RAT neighbor lists of that cell, the following sequence may be used:
− The eNodeB instructs the UE to use the newly discovered Phy-CID as parameter
and read the Global-CID of the detected neighboring cell in the target RAT. The
eNodeB may need to schedule appropriate idle periods to allow the UE to read the
Global-CID from the broadcast channel of the detected neighboring cell.
− When the UE has read the new cell's Global-CID, it reports the detected
Global-CID to the serving cell eNodeB.
− The eNodeB updates its Inter-RAT neighbor lists.
The eNodeB also supports inter-RAT periodic ANR. During inter-RAT periodic ANR
procedures, the eNodeB selects UEs to participate in periodic ANR and sets the reporting
purpose to "reportStrongestCellsForSON" for the UEs. Then, the UEs will send measurement
results periodically. If a UE reports an unknown layer-1 cell identity (such as a PCI, PSC, or
BSIC), the eNodeB instructs the UE to measure and report the CGI of the corresponding cell.
Inter-RAT periodic ANR improves handover performance.
The eNodeB supports inter-RAT event-triggered ANR. It is implemented as follows:
 Event-triggered ANR with GERAN: If a UE includes an unknown base transceiver
station identity code (BSIC) of a GERAN cell in a handover measurement report sent to
an eNodeB, the eNodeB instructs the UE to measure and report the cell global
identification (CGI) of the GERAN cell.
 Event-triggered ANR with UTRAN or CDMA2000: If the conditions for triggering a
handover event are met for a UE, the eNodeB sets the reporting purpose to
"reportStrongestCellsForSON" for the UE, instructing the UE to report the cell with the
strongest signal strength. Then, if the UE reports an unknown UTRAN or CDMA2000
cell, the eNodeB instructs the UE to measure and report the CGI of the cell.
Enhancement
 In eRAN2.1
The Inter-RAT ANR feature is enhanced with the following administration functions:
a. Setting: user can enable or disable the feature or sub-function such as periodic
Inter-RAT HO function in Inter-RAT HO
b. Log: records the key event during the SON process and this information can be
used for query and statistical. Operator can also analyze the log information to
master the feature running process and key event.
 In eRAN6.0
When the serving cell of a UE and an acquired shared cell are managed by the same OSS,
the serving cell can obtain the serving PLMN list of the acquired cell under the
assistance of the OSS if the UE cannot report the serving PLMN list or the acquired cell
does not broadcast the list.

Inter-RAT ANR can be triggered by L2U/G load balancing to add an L2U/G neighbor
(Micro is only support L2U load balancing).
 In eRAN7.0
Optimized automatic neighbor relation removal: If the NRT configuration has reached
the maximum specifications and a new neighbor relationship needs to be added to the
NRT, the eNodeB removes a relationship with a neighboring cell that is not measured or
to which no handover has been triggered within a measurement period, and then adds the
new neighbor relationship to the NRT.
Automatic setting of blind handover priorities for inter-RAT neighboring cells: An
eNodeB can automatically identify co-coverage neighboring UTRAN or GERAN cells
based on handover-related measurement results and configure or update blind handover
priorities.
Dependency
 eNodeB
None
 eCO
None
 UE
The UE must support this feature
None
 CN
None
 OSS
This feature depends on OSS feature WOFD-181400 Inter-RAT Automatic Neighbor
Relation Optimization -LTE.
 Other Features
None
 Others
None
2.4.1.3 LOFD-002007 PCI Collision Detection & Self-Optimization
Availability
This feature is
Summary
This feature detects Physical Cell Identity (PCI) conflict automatically, and the cell has an
incorrect PCI will be assigned with a proper PCI from EMS.

Benefits
This feature decreases operating cost in PCI conflict detection & PCI conflict solving
operation.
Description
PCI is an essential configuration parameter to E-UTRAN cells. It corresponds to a unique
combination of one orthogonal sequence (PSS) and one pseudo-random sequence (SSS). PCI
affects DL synchronization, demodulation, reselection, and handover.
In LTE, there are 504 PCIs can be used, PCI reuse is allowed among different cells. But two
cells that share same PCI cannot be geographically close and do not cause mutual
interference.
Each LTE cell should be assigned a proper PCI for transmitting data between cells. PCI
assignment must meet the following conditions:
 Collision-free: The PCI is unique in a certain geographical area.
 Confusion-free: A cell must not have neighboring cells with identical PCI.
PCI collision and PCI confusion are both PCI conflict, which will deteriorate network
performance.
Manual operation, ANR, and X2 interaction may cause changes in configuration parameters,
thereby causing PCI conflict.
Whenever a new neighbor relationship is added to eNodeB, PCI/DL EARFCN of any local
cell is changed, or PCI/DL EARFCN of any neighboring cell is changed, PCI conflict
detection procedure will be triggered to check possible PCI conflict.
PCI conflict is solved by PCI Self-optimization implemented in EMS. In order to allocate the
optimal PCI for conflicting cell, engineering information (longitude, latitude, azimuth) and
neighboring cell information are taken into account. As for eNodeB, if engineering
information (longitude, latitude, and azimuth) is unavailable, the algorithms can also allocate
an optimal PCI for conflicting cells by merely considering its neighboring cells' PCI
information.
PCI self-optimization consists of two procedures, PCI optimization analysis and PCI
optimization result implementation. PCI optimization analysis is used to calculate a proper
PCI for conflicting cells and PCI optimization result implementation is used to modify the
PCI of the conflicting cells according to the PCI optimization result.
There are 2 modes to start PCI optimization analysis:
 Immediate & automatic analysis: The EMS will calculate new PCIs for conflicting cells
as soon as possible.
 Periodic & automatic analysis: The EMS will calculate new PCIs for conflicting cells at
a cycle time basis.
Only when newly assigned PCI is delivered to conflicting cell, the PCI conflict is solved. The
newly assigned PCI can be configured in three manners:
 Immediate & automatic delivery: The EMS delivers the new PCI to the eNodeB as soon
as it is generated by PCI optimization analysis.
 Scheduled & automatic delivery: The EMS delivers the new PCI at a regular basis.

 Manually confirmed delivery: The EMS will generate a notice for confirmation before
delivering the PCI to the eNodeB. Operator can change the suggested PCI, and decide
whether to deliver the newly assigned PCI.
Key events can be queried in SON log, which are recorded when:
 PCI conflict appears or disappears
 PCI optimization analysis starts or stops
 PCI optimization advice is delivered
Enhancement
 eRAN2.1
PCI collision detection is enhanced with self-optimization implemented in EMS to solve
the detected collisions. In order to allocate the optimal candidate PCI for the whole
network, and to minimize the interference among neighboring cells, the site engineering
information (longitude, latitude, azimuth), GCI, and neighboring cell list are taken into
the PCI assignment. For Micro eNodeB, if the above information cannot be provided, the
algorithms also can allocate the optimal candidate PCI for the micro cell base on its
neighboring cells' PCI information. The neighboring cells' information of the micro
eNodeB can be discovered by the sniffer or ANR. The new assigned PCI can be
configured in three manners:
a. Immediate & Automatic delivery: The EMS will deliver the new PCIs to the
eNodeB as soon as it is generated.
b. Regular & Automatic delivery: The EMS will deliver the new PCI at a cycle time
basis.
c. Manually confirmed delivery: The EMS will generate a notice for confirmation
before delivery to the eNodeB.
The PCI Collision Detection & Self-Optimization feature is enhanced with the following
maintenance functions:
a. Policy setting: Operator can set up some policy of the feature, such as the
optimization analysis mode. Break point: operator can set up break points to
increase the control capability on the feature. The algorithm can be stopped at the
break points and operator confirmation is needed for the process continuity.
b. Log: records the key event during the SON process and this information can be
used for query and statistics. Operator can also analyze the log information to learn
about the feature running process and key event.
 eRAN7.0
PCI self-optimization is enhanced with the following maintenance functions:
a. Site engineering information import function. If the engineering information is not
completely or correctly configured in eNodeB, users can import this information
through U2000 so that U2000 can get enough engineering information for PCI
optimization.
b. Available PCI range import function. In network border area, the U2000 cannot
obtain the PCI information of cells in the other side of the border, after PCI
optimization, the U2000 cannot guarantee that new PCI will not introduce new PCI
conflict. In eRAN7.0, operator can negotiate available PCI range between different
vendors or different operators and import the range into the U2000 to perform PCI
optimization. By doing this, new PCI conflict in border area can be avoided.
c. Select conflicted cell base on user-defined priority and PCI modification time.

Another two facts will be considered in eRAN7.0 to select conflicted cell for
implementing PCI modification, user-defined priority and PCI modification time.
Users can define the priority of each cell with any of the following 3 values: "High",
"Low", "Not allowed to modify", U2000 will select a cell with a high priority to
perform PCI optimization. If the cell is defined as "Not allowed to modify", the
U2000 cannot implement any PCI optimization to this cell.
Users can configure the threshold for PCI modification time, if cell PCI
modification time is less than this threshold, it will be considered as new cell, which
will have a higher priority than old cell to implement PCI optimization.
 eRAN8.1
The PCI collision detection is enhanced in the following aspect:
ECGI measurements can now be triggered by low handover success rates. The
measurements help detect the unknown neighboring cells whose PCIs conflict with the
PCIs of other neighboring cells. PCI conflict detection is triggered during ANR
procedures for adding the detected cells.
Dependency
 eNodeB
None
 eCO
None
 UE
None
None
 CN
None
 OSS
This feature depends on OSS feature WOFD-170200 Automatic PCI Optimization -LTE.
 Other Features
None
 Others
None
2.4.1.4 LOFD-081225 Neighboring Cell Classification Management
Availability
Summary
This feature classifies neighbor relationships based on the statistics of neighbor relationships
and applies different management policies to different classes of neighbor relationships. This
feature helps increase neighbor relationship management efficiency and improve operator's
OM experience.

Benefits
This feature automatically classifies neighbor relationships, improving neighbor relationship
OM efficiency.
Description
An eNodeB classifies intra-RAT neighbor relationships based on the number of handover
attempts and the number of successful handovers between two neighboring cells within a
measurement period. An intra-RAT neighbor relationship can be classified into a "Formal" or
"Extended" one and handled in a differentiated way.
 In a handover to a neighboring cell with this attribute set to "Formal", the UE is handed
over directly based on the neighbor relationship configuration. In a handover to a
neighboring cell with this attribute set to "Extended", the UE is handed over based on the
neighboring cell configuration or ECGI reading.
 If two intra-frequency neighboring cells share one PCI, then: 1. If the attribute values of
the two cells are both "Formal" or "Formal" and "Extended", the local cell needs to
perform PCI confusion detection on these neighboring cells. 2. If the attribute values of
the two cells are "Extended", the local cell does not perform PCI confusion detection on
these neighboring cells.
The eNodeB classifies neighboring UTRAN or GERAN cells based on number of times the
neighboring cell is measured within a measurement period. A UTRAN or GERAN
neighboring cell can be classified into a "Formal" or "Extended" one and handled in a
differentiated way.

In the preceding figure, special neighboring indicators refer to Overlap Indicator, Blind handover
Priority, and SCell Blind Configuration Flag.
The eNodeB can periodically report neighboring E-UTRAN and UTRAN cells to the U2000.
The U2000 checks over-distance neighboring cells based on engineering parameters and
configuration information. The eNodeB sets such E-UTRAN and UTRAN neighboring cells
to the blacklists and does not allow handovers to these cells.

Enhancement
 In eRAN11.1
An eNodeB can classify UTRAN and GERAN neighbor relationships based on the
number of times the neighbor relationship is measured.
The eNodeB automatically checks over-distance E-UTRAN and UTRAN neighbor
relationships and adds them the blacklists.
Applicability
Yes Yes Yes
Dependency
 eNodeB
None
 eCoordinator
None
 UE
UEs must support CGI reading and reporting for neighboring cells.
 CN
None
 Other NEs
This feature requires support from the U2000.
 Other features
This feature depends on LOFD-002001 Automatic Neighbour Relation (ANR) or
LOFD-002007 PCI Collision Detection and Self-Optimization.
 Others
None

2.4.1.5 LOFD-110219 Auto Neighbor Group Configuration
Availability
Summary
This feature can automatically configure overlap indicators used for inter-frequency mobility
load balancing (MLB) and SCell blind configuration flags used for carrier aggregation (CA),
and plan associations between macro and micro cells required for TDM eICIC activation.
This feature can automatically detect the network topology change and adjust the overlap
indicators, SCell blind configuration flags, and association between macro and micro flags.
Benefits
After this feature is deployed, the eNodeB automatically configures overlap indicators, SCell
blind configuration flags, and associations between macro and micro cells, reducing the OM
cost.
Description
 Automatic configuration of overlap indicators
The overlap indicator is one of key parameters used by inter-frequency MLB and CA. It
helps to determine a target candidate neighboring cell for MLB and select a candidate
component carrier (CC) for CA.
Overlap indicators can be added or deleted only manually before this feature is deployed.
Before the addition of an overlap indicator, a pair of cells with overlapping coverage
must be manually identified and the overlap indicator must be added to the neighbor
relationship between the cells. Before the deletion of an overlap indicator, a pair of cells
must be manually identified and the overlap indicator must be deleted from the neighbor
relationship between the cells. All these manual operations are time-consuming but must
be accurately performed.
If this feature is enabled, based on the statistical results and configurable thresholds of
measurement events on the network, the eNodeB can automatically identify the
inter-frequency neighboring cells for which overlap indicators need to be added or
deleted. In addition, the eNodeB can automatically (or in a controlled manner) add or
delete overlap indicators, reducing the manpower significantly. For example, when the
statistical result indicates that the overlap proportion of a neighboring cell is greater than
the threshold for adding an overlap indicator, the eNodeB identifies the neighboring cell
as a cell to which an overlap indicator can be added.
 Automatic configuration of SCell blind configuration flag
The SCell blind configuration flag is one of key CA parameters. Blind configuration can
be performed for SCells configured with such flags without prior measurements.
Before this feature is deployed, SCell blind configuration flags can be added, modified,
or deleted only manually. Before the addition of an SCell blind configuration flag, a pair
of cells with overlapping coverage must be manually identified and the flag must be
added to the neighbor relationship between the cells. Before the modification or deletion
of an SCell blind configuration flag, a pair of cells with overlapping coverage must be
manually identified and the overlap indicator must be modified or deleted from the
neighbor relationship between the cells. All these manual operations are time-consuming
but must be accurately performed.

If this feature is enabled, based on the statistical results and configurable thresholds of
measurement events on the network, the eNodeB can automatically identify the
inter-frequency neighboring cells for which SCell blind configuration flags need to be
added, modified, or deleted. In addition, the eNodeB can automatically (or in a
controlled manner) add, modify, or delete such flags, reducing the manpower
significantly. For example, when the statistical result indicates that the overlap
proportion of a neighboring cell is greater than the threshold for adding an SCell blind
configuration flag, the eNodeB identifies the neighboring cell as a cell to which an SCell
blind configuration flag can be added.
 Automatic configuration of the association between macro and micro cells
After this function is enabled, the micro cell collects the number of times that a macro
cell has the strongest signal strength in the intra-frequency neighboring cell A3
measurement report. After the measurement period ends, the macro cell with the
strongest signal strength for the most times is regarded as the target homing cell of the
micro cell. Then, the eICIC homing relationship is updated through an X2 message.
Updating the association between a macro cell and a micro cell may change the cell
range expansion (CRE). If the CRE changes, a large number of UEs will re-establish
RRC connections and the handover between a macro cell and a micro cell will be
triggered. Therefore, it is recommended that the association change start time be set to a
time when the traffic is light.
Enhancement
In eRAN11.1, automatic configuration of overlap indicators is enhanced by adding the
following subfunctions:
 Automatic configuration of an overlap indicator for a micro cell
If a micro cell detects that its coverage range is within that of a macro cell, the micro cell
can actively notify the macro cell to configure an overlap indicator.
 Automatic configuration of overlap indicators for a micro cell group
If the coverage ranges of multiple micro cells are within the coverage range of a macro
cell, the macro cell can regard all the inter-frequency micro cells using the same
EARFCN as one micro cell group. To add overlap indicators to a micro cell group, the
macro cell adds an overlap indicator to each micro cell in the group. To delete overlap
indicators from a micro cell group, the macro cell deletes an overlap indicator from each
micro cell in the group.
Applicability
Yes Yes Yes
Dependency
 eNodeB
None
 eCoordinator
None
 UE

None
 CN
None
 Other NEs
eNodeBs communicate with each other over the X2 interface.
 Other features
None
 Others
The corresponding neighboring cells must use Huawei devices.
2.4.1.6 LOFD-002005 Mobility Robust Optimization (MRO)
Availability
This feature is
 Applicable to Micro form eRAN3.0.
Summary
MRO aims to reduce intra-RAT/inter-RAT ping-pong handovers, premature handovers,
delayed handovers, intra-RAT handovers to wrong cells, and unnecessary inter-RAT
handovers. It is implemented by optimizing the typical mobility control parameters.
Benefits
 Reducing intra-RAT/inter-RAT ping-pong handovers, premature handovers, delayed
handovers, intra-RAT handovers to wrong cells, and unnecessary inter-RAT handovers
 Saving labor cost for typical and common mobility optimization scenarios
Description
This feature reduces intra-RAT/inter-RAT ping-pong handovers, premature handovers,
delayed handovers, intra-RAT handovers to wrong cells, and unnecessary inter-RAT
handovers in different scenarios:
 Ping-pong handovers, handovers to wrong cells, premature handovers, and delayed
handovers of intra-LTE scenarios
The major MRO parameter adjustment are the CIO (Cell Individual Offset) of event A3
for intra-frequency MRO, CIO of event A3/A4 and measurement threshold of event A2
for inter-frequency MRO.
Both premature and delayed handovers are captured at the source eNodeB. Only
outgoing handover failures are captured. There is no need to capture incoming
handovers.
CIO offset is adjusted automatically by steps according to the number of abnormal
handovers in a certain period. CIO offset explicitly declares the handover threshold

between measurement results of signaling quality from both source and target cells.
Hence, changing the CIO offset will shift ahead or delay the happening of handovers.
The reduction of ping-pong handovers exploits the UE History Information that is passed
from the source eNodeB to the target eNodeB during the handover preparation. When
the UE History Information is received, the target eNodeB identifies ping-pong if the
second newest cell's GCI is equal to that of the target cell and the time spent in the
source cell is less than a ping-pong time threshold. Ping-pong is corrected by decreasing
the Cell Individual Offset, thereby delaying handovers.
In the intra-frequency scenario, there is a UE specific ping-pong handover reduction
algorithm. If the UE is identified under ping-pong handover, specific CIO parameter is
applied for the UE to stop the ping-pong handover.
 Ping-pong handovers, premature handovers, delayed handovers, and unnecessary
handovers of inter-RAT scenarios
Event A2 and B1 measurements thresholds are adjusted for inter-RAT scenarios.
Enhancement
 In eRAN2.1
The MRO feature is enhanced with the following administration functions:
− Feature On/Off Switch: operator can enable or disable the feature
− Log: records the key event during the MRO process and this information can be
used for query and statistic. Operator can also analyze the log to check the feature
running status and key events.
 In eRAN6.0
UE-level MRO against ping-pong handovers is introduced. The eNodeB identifies
ping-pong UEs and sends corresponding UE-level MRO parameters to these UEs. This
type of MRO reduces the number of ping-pong handovers, reduces Uu resource usage,
and improves quality of experience (QoE) of UEs.
The UE-level MRO algorithm is independent of the cell-level MRO algorithm. They are
controlled by different switches.
 In eRAN8.1
The maintenance and testing method for inter-RAT MRO is enhanced. The counters
related to premature and delayed handovers from E-UTRAN to GERAN have been
added. The counters related to premature, delayed, unnecessary, ping-pong handovers
from E-UTRAN to UTRAN have been added.
Inter-RAT MRO optimizes premature handovers, delayed handovers, and unnecessary
handovers.
Dependency
 eNodeB
For intra-RAT MRO scenarios, X2 interface is needed.
For inter-RAT MRO against unnecessary handovers, the UTRAN and GERAN must
support unnecessary handover detection (including the RIM procedure) defined by 3GPP
Release 10.
 eCO
None
 UE
None

None
 CN
None
 OSS
None
 Other Features
None
 Others
None
2.4.1.7 LOFD-002015 RACH Optimization
Availability
This feature is:
Summary
The feature supports the following functions:
 Dynamic adjustment of preamble groups
 Dynamic assignment of PRACH resources
 Optimized back-off time
 PRACH false alarm detection
 Root sequence conflict detection
Benefits
The feature improves the performance of random access.
 Dynamic adjustment of preamble groups is used to adjust the ratios of contention-based
preambles and dedicated preambles. When the load of contention-based random access is
high while the load of non-contention-based random access is low, this feature reduces
the preamble collision probability and delay of contention-based random access. When
the load of contention-based random access is low while the load of
non-contention-based random access is high, this feature reduces the delay of
non-contention-based random access.
 PRACH resource adjustment is used to adjust RACH resource configuration based on
the RACH load in a cell. When the RACH load is high, more RACH resources will be
allocated to reduce the preamble collision probability.
 PRACH false alarm detection reduces the probability of reporting false alarms.
 Root sequence conflict detection is used to detect root sequence conflicts between cells.
Based on the detection result, root sequences are replanned to eliminate root sequence
conflicts and reduce the probability of preamble collision and false alarms reporting.

 Intelligent PRACH detection is used to enable handovers for UEs located beyond the cell
radius.
Description
There are 64 PRACH preambles, which are divided into contention-based preambles and
dedicated preambles. These two types of preambles are used for contention-based random
access and non-contention-based random access, respectively. The eNodeB can detect
whether preambles in a preamble group are sufficient, and then adjusts the number of
preambles in the group dynamically as required.
The PRACH configuration index indicates the number and positions of subframes that can be
used to send random access preambles. The eNodeB measures the number of preambles and
adjusts the PRACH configuration index as required. If the number of preambles exceeds the
threshold, the eNodeB will increase the PRACH configuration index to occupy more
subframes, and vice versa.
When PRACH resource conflicts occur, the eNodeB sends different back-off time indicators
to UEs. UEs then select random back-off time based on the back-off time indicators to retry
access, so that the chance of conflicts is reduced.
The eNodeB detects false alarms based on the peak value of cross correlation sequence of
initially transmitted random preambles and the distance indicated by the timing advance (TA).
A preamble will be identified as a false alarm in either of the following conditions:
 The peak value of cross correlation sequence of initially transmitted random preambles is
less than the threshold.
 The distance indicated by the TA is greater than the threshold.
The eNodeB does not send a random access response (RAR) to preambles identified as false
alarms.
When the serving cell works properly, the eNodeB will report a root sequence conflict alarm
if it detects that the serving cell and neighboring cell or the serving cell and an intra-eNodeB
cell work on the same uplink frequency and use the same root sequence. Then, the root
sequence will be replanned to prevent conflicts.
Enhancement
 eRAN8.1
− Root sequence conflict detection has been added.
− The eNodeB supports the detection of root sequence conflicts between
intra-eNodeB cells and between inter-eNodeB cells with X2 links.
 eRAN12.1
Detection of contention-based random access of UEs beyond the cell radius has been
added and random access of UEs performing handovers beyond the cell radius has been
optimized. These solutions are applied when UEs are located beyond the cell radius but
within twice the cell radius.
Detection of contention-based random access of UEs beyond the cell radius:
The eNodeB can identify UEs that are located beyond the cell radius and allow their
contention-based random access to cells.
Optimized random access of UEs performing handovers beyond the cell radius
If a UE is handed over to the target cell from a location beyond the cell radius, the
eNodeB optimizes the access procedure for this UE to ensure its successful access.

Dependency
None
2.4.1.8 LOFD-081207 Specified PCI Group-based Neighboring Cell

Management
Availability
This feature is:
Summary
When a large number of micro base stations are deployed under a macro base station,
dedicated PCI ranges are specified for micro and macro base stations to distinguish common
sites from densely deployed sites. The eNodeB adopts different management policies on
neighboring cells depending on different PCI ranges. This feature implements handovers
between macro and micro base stations based on CGI reading, thereby reducing manual
operations, saving operators' costs, and ensuring normal handovers between macro and micro
base stations.
Benefits
 This feature simplifies PCI planning in scenarios where a large number of micro base
stations are deployed.
 This feature implements handovers between macro and micro base stations based on CGI
reading, thereby preventing handover failures caused by PCI multiplexing of micro base
stations.
Description
When a large number of micro base stations are deployed under a macro base station,
dedicated PCI ranges are specified for micro and macro base stations to distinguish common
sites from densely deployed sites. Macro base stations use the PCIs for common sites, and
micro base stations use PCIs for densely deployed sites. After UEs report the neighboring cell
measurements, the PCIs contained in the measurement reports are used to identify the type of
neighboring cells.
When the source cell served by a common site detects that its neighboring cells are served by
densely deployed sites, a CGI reading procedure is triggered, irrespective of whether its
neighboring cells have been configured. Based on CGI reading results, the eNodeB adds or
updates neighboring cell configurations and determines whether the handover is complete. In
this scenario, you can configure cells served by intra-frequency densely deployed sites with
the same PCI as neighboring cells for the common site in the neighboring cell list. In this case,
PCI confusion check is not required.
This feature does not apply to the scenario where both the source cell and its detected
neighboring cells are served by the common site or the source cell is served by a densely
deployed site.

Enhancement
None
Dependency
 UE
This feature requires support from the UE.
 Other features
This feature requires LOFD-002001 Automatic Neighbour Relation (ANR) and
LOFD-002007 PCI Collision Detection & Self-Optimization.
2.4.2 Power Saving

Overview
The power saving features dynamically adjust the running status of eNodeBs to improve
energy efficiency and reduce power consumption without affecting user experience.
Applications
The power saving feature package is used for two purposes: energy conservation and power
consumption management. The following table lists the features that can be activated in each
scenario.
Ap Feature Description
plic
atio
n
eNo LOFD-001025 The eNodeB dynamically adjusts the offset voltage of the PAs
deB Adaptive Power according to the cell load. This increases the PA efficiency and
Ene Consumption reduces the power consumption of the RF modules.
rgy
Con LOFD-001039 When the cell load is low in a specified period, the eNodeB
serv RF Channel shuts down some transmit channels of a cell to save power.
atio Intelligent Meanwhile, the eNodeB increases the reference signal transmit
n Shutdown power of the remaining channels to ensure proper coverage.
LOFD-001042 If the local and target carriers are both lightly loaded in
Intelligent inter-frequency co-coverage networking, the eNodeB transfers
Power-Off of UEs to the target carrier that can bear the added load and shuts
Carriers in the down the local carrier to save power.
Same Coverage
LOFD-001056 The eNodeB configured with Huawei AC/DC PSUs monitors
PSU Intelligent the cell load in real time and accordingly has the redundant
Sleep Mode PSUs enter the sleep mode. This improves conversion efficiency
of the remaining PSUs and reduces power consumption.
LOFD-001070 This feature enables the eNodeB to turn off PAs during periods
Symbol Power for symbols that do not contain any data to transmit.
Saving
LOFD-001074 If the coverage of a lightly loaded E-UTRAN cell with a small

Ap Feature Description
plic
atio
n
Intelligent number of UEs overlaps the coverage of a UTRAN cell, the
Power-Off of eNodeB transfers UEs to the UMTS carrier and shuts down the
Carriers in the LTE carrier to reduce power consumption.
Same Coverage
of UMTS
Network
Pow LOFD-001040 When the eNodeB reports alarms such as power insufficiency or
er Low Power power failure, or is manually operated, the cell enters the low
Con Consumption power consumption mode. In this mode, the eNodeB reduces
sum Mode the power consumption of the RF modules to prolong the
ptio service duration.
n
Ma LOFD-001071 Battery management functions are provided to extend the
nag Intelligent battery lifespan. These functions include the automatic switch
eme Battery between the charge and discharge modes, battery
nt Management overtemperature protection, and power backup duration
estimation in case of mains outage.
Value
 eNodeB Energy Conservation
The power saving features can reduce the eNodeB power consumption. In the
recommended application scenarios, the features can reduce the eNodeB power
consumption by 15% to 20%. Factors that affect the power-saving gains are as follows:
− Cell load: The higher the cell load, the lower the probability that the power-saving
features are triggered, and less gains are obtained.
− Parameter configuration: Some features in the package require configuration of
parameters such as the validity period and PRB usage threshold. The more strict the
conditions, the lower probability that the corresponding feature is triggered, and the
less the power-saving gains.
RF module type: The proportion of power consumed by the PAs in the entire RF module
varies with the type of the RF module. The higher the proportion, the greater the gains of
the power-saving features.
 Power Consumption Management
In recommended scenarios, the low power consumption mode increases the power
backup duration by 50% or so, and intelligent battery management can prolong the
battery life by about 50%.
2.4.2.1 LOFD-001025 Adaptive Power Consumption
Availability
This feature is


Summary
Huawei LTE supports the green eNodeB solution with power saving management. This
solution has two sub-features: Adaptive Power Adjustment and RF module regular time sleep
mode.
Benefits
This feature improves the efficiency of the PA and saves power consumption of the eNodeB.
Description
Huawei LTE supports the green eNodeB solution with power saving management. This
solution has two sub-features: Adaptive Power Adjustment and RF module regular time sleep
mode.
 Adaptive Power Adjustment
Huawei Adaptive Power Adjustment solution, based on the traffic load, supports dynamic
adjustment of the PA working state, and thereby improves PA efficiency and saves eNodeB
power consumption.
The typical scenarios are described as follows:
1. Based on the change of cell load in the day and at night, the PA working state is changed
dynamically.
2. Based on the change of cell load in the working days and non-working days of the business
districts, the PA working state is changed dynamically.
3. At the early stage of network deployment, there are usually less users in the cell, and
when there's no any user in the cell, the PA working state is changed dynamically.
 RF module regular time sleep mode
In some scenarios, such as high-speed railway, which will stop operating at late night, the RF
module of eNodeB can be put into sleep mode automatically at preset time based on the
operator's configuration.
Enhancement
None
Dependency
 OSS
This feature depends on OSS feature WOFD-200200 Base Station Power-Saving
Management -LTE.
 Others
"Adaptive Power Adjustment" is not supported in 1.4, 3 and 5 MHz system bandwidth.

2.4.2.2 LOFD-001039 RF Channel Intelligent Shutdown
Availability
This feature is:
Summary
This feature shuts down some transmit channels of a cell to conserve energy within a
specified period if there are few UEs or even no UE in the cell. After some transmit channels
are shutdown, the eNodeB increases the transmit power of reference signals to ensure
coverage.
Benefits
Among the transmit channels of an RF module, those with no load or low load are shut down
to reduce the eNodeB power consumption.
Description
An eNodeB is usually configured with two or four antennas. The cell traffic volume changes
over time. In some periods, for example from the midnight to the early morning
(time-segment is configurable), the service load is low and reaches the feature activation
threshold and there is no UE with the QCI of 1, the eNodeB will shut down one of the two
transmit channels or two of the four transmit channels to reduce the power consumption of RF
modules.
When service load increases to the exit threshold, a UE with the QCI of 1 accesses the cell, or
the period ends, the eNodeB automatically switches on the transmit channels that have been
previously shut down, and the cell recovers to the normal state.
Enhancement
 eRAN8.1
The RF channel intelligent shutdown algorithm for macro eNodeBs is enhanced as
follows:
− The feature activation threshold is optimized so that the feature also takes effect
when the cell has a low service load.
− The UE service type can be identified. The RF Channel Intelligent Shutdown
feature does not take effect if there are UEs whose QCI is 1.
Dependency
 eNodeB
The cell is configured with either two or four transmit antennas.
 eCO
None
 UE

None
None
 Core network
None
 OSS
Management -LTE.
 Other features
LOFD-001001 DL 2x2 MIMO or LOFD-001003 DL 4x2 MIMO
 Others
The cell bandwidth is greater than or equal to 10 MHz.
The feature enhancement of eRAN8.1 requires that the cell bandwidth is greater than or
equal to 20 MHz.
2.4.2.3 LOFD-001040 Low Power Consumption Mode
Availability
This feature is:
 Available in third-party power supply scenarios as of eRAN8.1.
 Available in macro eNodeBs in distributed power supply scenarios as of eRAN12.1.
Summary
When detecting power supply disconnection or receiving a specific command, the eNodeB
will enter the low power consumption mode, sometimes forcibly. This mode extends the
service time of an eNodeB that is powered by batteries.
Benefits
Compared with the eNodeB in normal mode, an eNodeB in low power consumption mode
consumes less power and has a longer in-service time if powered by batteries. In addition, if
the power supply cannot be quickly restored, the probability of an eNodeB going out of
service is also lower.
Description
Low power consumption mode has three stages. If the eNodeB stays in a stage for a time
equal to the operator-defined duration threshold and the power supply fails to restore within
this time, the eNodeB enters the next stage. This process continues until the cell becomes out
of service.
An eNodeB enters low power consumption mode if either of the following conditions is met:
 The power outage alarm is reported.

If power insufficiency or power failure lasts for a time equal to the operator-defined
duration, this alarm is reported and the eNodeB enters low power consumption mode.
 The element management system (EMS) delivers a command.
The operator delivers a command using the EMS, instructing the eNodeB to enter or exit
from low power consumption mode.
Enhancement
 eRAN12.1
Macro eNodeBs now work in distributed power supply scenarios.
Dependency
 eNodeB
This feature is applicable to macro eNodeBs that are configured with PMUs and
batteries.
 OSS
This feature requires OSS feature WOFD-200200 Base Station Power-Saving
Management -LTE.
2.4.2.4 LOFD-001042 Intelligent Power-Off of Carriers in the Same

Coverage
Availability
This feature is:
Summary
When there is light traffic in an area that is covered by multiple carriers, some of the carriers
can be blocked, and all services can be automatically taken over by the carriers that remain in
service. When the traffic increases to a certain degree, the carriers that are blocked can be
automatically unblocked again to provide services.
Benefits
When there is light traffic in an area that is covered by multiple carriers, some of the carriers
can be blocked, and all services can be automatically taken over by the carriers that remain in
service. This helps reduce the power consumption of the eNodeB without any impact on the
service quality.
Description
When multiple carriers provide coverage for the same area, the traffic of the area varies by
time. In some certain periods, for example from the midnight to the early morning (the
periods can be preset by the operator), the traffic is light. When the eNodeB detects the light
traffic, it triggers UEs to perform migration to some of the carriers and then blocks the
carriers without any load. In this way, the power consumption is reduced. When the traffic

increases or the preset periods end, the eNodeB can automatically switch on the carriers that
are unblocked to recover the functionality of the carriers. In this way, the system capacity is
increased without any impact on the service quality.
Enhancement
From eRAN12.1 onwards:
 The triggering algorithm of this feature is optimized by utilizing the neighboring cell
overlap indicator for the macro and LampSite eNodeBs.
 Carriers that serve FDD and TDD co-coverage cells can be blocked in FDD and TDD
co-MPT scenarios.
Dependency
 OSS
This feature depends on the OSS feature WOFD-200200 Base Station Power-Saving
Management - LTE.
 Others
This feature and the LOFD-001074 Intelligent Power-Off of Carrier in the Same
Coverage of UMTS Network feature cannot take effect simultaneously in the same cell.
2.4.2.5 LOFD-001056 PSU Intelligent Sleep Mode
Availability
This feature is
Summary
This feature introduces the function of PSU (Power Supply Unit) intelligent Sleep Mode.
With this feature, certain PSUs can be powered on or off according to the power consumption
of the eNodeB, thus reducing the power consumption.
Benefits
When the traffic is light, the eNodeB can power off certain PSUs to reduce the power
consumption. In the following scenario, 3 PSUs in 1 eNodeB and low traffic, turning on this
feature could help to save 4% to %5 power consumption.
Description
If an eNodeB with AC input is configured with HUAWEI PSUs (converting AC into DC) and
HUAWEI PMU, the function of PSU intelligent Sleep Mode can be used. The number of
configured PSUs depends on the maximum power consumption of the eNodeB. The purpose
is to ensure that the eNodeB operates properly even at the maximum load. In most cases, the
eNodeB does not operate at full load, and thus the PSUs do not operate at full power.
Generally, the PSU conversion efficiency is proportional to its output power. In other words,

the decrease in the conversion efficiency increases the overall power consumption of the
eNodeB.
When the eNodeB is powered by multiple PSUs, the PSU intelligent shutdown function
enables shutting down one or several PSUs according to the actual load and the power supply
need. In this way, the remaining PSUs work in full load mode, thus ensuring their best level of
efficiency.
Enhancement
None
Dependency
 eNodeB
The eNodeB with AC input must be configured with HUAWEI PSUs (converting AC
into DC) and HUAWEI PMU.
2.4.2.6 LOFD-001070 Symbol Power Saving
Availability
This feature is:
Summary
The eNodeB can shut down power amplifiers (PAs) when symbols are empty, that is, within
symbol periods when there is no data to send. Multicast Broadcast multicast service Single
Frequency Network (MBSFN) subframes can be used to further reduce the number of
reference signals (RSs) so that more empty symbols are available for PAs to shut down.
Benefits
When the traffic is light, the eNodeB can shut down a PA when symbols are empty to save the
static power consumption of the PA. The power consumption of the eNodeB is reduced.
Description
PAs consume the most power in eNodeBs. The PAs require static power consumption even
when there is no signal output. If PAs support fast power-on and power-off, symbol power
saving can be used.
eNodeBs can shut down their PAs when symbols are empty. This function reduces the static
power consumption of the PAs. The power-on and power-off of PAs must be under control to
maintain data integrity.
For example, when there is no active UE in a cell, PAs can be powered off in the RS-free
OFDM symbol periods within certain subframes where only RSs are transmitted.
In addition, if the cell is not configured to provide MBMS services, the eNodeB can configure
some of the empty subframes as MBSFN subframes for further power saving. In an MBSFN

subframe, only the first RS needs to be transmitted over the air interface. The other symbols
in the subframe can be set to be empty so that the PA can be powered off.
Figure 2-41 Symbol power saving (normal CP)
Figure 2-42 Symbol power saving with MBSFN subframe (extended CP)
Enhancement
None
Dependency
 eNodeB
The following RF modules must be configured to support Symbol Power Saving:
− Single-mode RF modules
RRU3221 (2600 MHz), RRU3240 (2600 MHz), RRU3249 (700 MHz), RRU3260
(2600 MHz), RRU3261 (2300 MHz, 2600 MHz), RRU3262 (700 MHz, 2600 MHz),
RRU3268 (700 MHz, 2600 MHz), RRU3269 (700 MHz), RRU3632 (2100 MHz),
RRU3638 (2100 MHz), RRU3642 (850 MHz), RRU3668 (450 MHz), LRFUe,
RRU3281
− Multimode RF modules
RRU3832 (AWS, 2100 MHz), RRU3952m (2100 MHz), RRU3838 (2100 MHz),
RRU3928 (900 MHz, 1800 MHz), RRU3929 (900 MHz, 1800 MHz), RRU3936
(900 MHz), RRU3938 (900 MHz, 1800 MHz), RRU3939 (1800 MHz), RRU3952
(850 MHz), RRU3952m (1800 MHz), RRU3953, RRU3958, RRU3959,
RRU3959w (1800 MHz), RRU3962 (1800 MHz, 2100 MHz), RRU3962d (1800
MHz, 2100 MHz), RRU3965d (800 MHz, 900 MHz), RRU3965 (800 MHz, 900
MHz), RRU3971, RRU3841 (AWS), MRFUc (2100 MHz), MRFUd, MRFUdw

(1800 MHz), AAU3920 (1800 MHz, 2100 MHz), AAU3940, AAU3961, AAU3911,
RRU3951, AAU3910, RRU3953w
 Others
To implement enhanced symbol power saving mode, all UEs must be capable of
identifying and handling MBSFN subframes.
2.4.2.7 LOFD-001071 Intelligent Battery Management
Availability
This feature is
Summary
With this feature,
 The battery management mode automatically changes depending on the selected grid
type, which prolongs the battery lifespan.
 The battery self-protection function is triggered under high temperature, which avoids
the overuse of batteries and the consequent damages to the batteries.
 The runtime of batteries is displayed after the mains supply is cut off. According to the
runtime, users can take measures in advance to avoid service interruption due to power
supply cutoff.
Benefits
 Prolonged battery lifespan
 Reduced operation costs
 Improved system stability
Description
 Automatic change of the battery management mode:
The PMU board records the number of times power supply is cut off and the duration of each
cutoff. Then, the PMU board determines which grid type is chosen and correspondingly
activates a specific power management mode. In grid types 1 and 2, batteries can enter the
hibernation state in which batters do not charge or discharge, which helps prolong battery
lifespan.
Table 2-4 Battery management modes

Power Grid Type Charge Current Hibernatio Hibernatio Estimated
Supply and Limitation n Voltage n Duration Battery
Cutoff Discharge Valve (V) (Days) Lifespan
Duration Mode Improvem
Within 15 ent Rate
Days
(Hours)

≤5 1 Mode A 0.10 C 52 13 100%

5-30 2 Mode B 0.15 C 52 6 50%
30-120 3 Mode C 0.15 C N/A N/A 0%
≥120 4 Mode C 0.15 N/A N/A 0%
The function of the automatic change of the battery management mode is under license
control. In addition, this function is disabled by default and you can enable it by running an
MML command.
 Self-protection under high temperature:
When batteries maintain a temperature exceeding the threshold for entering the floating
charge state for 5 minutes, they enter the state and no alarms are generated.
When batteries maintain a temperature exceeding the threshold for the self-protection function
for 5 minutes, they are automatically powered off or the voltage of batteries is automatically
adjusted.
 Display of the battery runtime:
After the mains supply is cut off, the base station works out the runtime of batteries based on
the remaining power capacity, discharge current, and other data. This runtime can be queried
by running an MML command.
To calculate the runtime of batteries, use the following formula:
Runtime of batteries = (Remaining power capacity x Total power capacity x Discharge
efficiency)/(Mean discharge current x Aging coefficient)
Enhancement
None
Dependency
 eNodeB
The APM30H (Ver. C), BTS3900AL, TP48600A, and batteries must be configured.
2.4.2.8 LOFD-001074 Intelligent Power-Off of Carriers in the Same

Coverage of UMTS Network
Availability
This feature is

Summary
When there is light traffic in an area that is covered by UMTS Networks in setting time period,
LTE carrier can be blocked, and all users (including DRX user) can be automatically
handover to the inter-RAT carriers. When the setting time period is expired, the LTE carrier
that is blocked can be unblocked again automatically to provide services.
Benefits
When there is light traffic in an area that is covered by UMTS Networks in setting time period,
LTE carrier can be blocked, and all users (including DRX user) can be automatically
handover to the inter-RAT carriers. This can help reduce the power consumption of the
eNodeB, thus save OPEX of operator.
Description
When multiple-RAT carriers provide coverage for the same area, the traffic of the area varies
by time. In some certain periods, for example from the midnight to the early morning (the
periods can be preset by the operator), the traffic is light. When the eNodeB detects the light
traffic, it triggers UEs to perform migration to some of the UMTS carriers and then blocks the
LTE carrier. In this way, the power consumption is reduced. When the preset periods end, the
eNodeB can automatically switch on the carriers that are unblocked to recover the
functionality of the carrier. In this way, the system capacity is increased.
Enhancement
None
Dependency
 OSS
Management -LTE.
 Other features
This feature depends on LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and
UTRAN.
 Others
This feature should not work to a cell simultaneously with feature LOFD-001042
Intelligent Power-Off of Carriers in the Same Coverage.

LTE FDD eRAN12.1 Feature Description 3 Acronyms and Abbreviations
3 Acronyms and Abbreviations
Table 3-1
3GPP Third Generation Partnership Project
A
ABS Almost-blank subframe
ACK acknowledgment
ACL Access Control List
AES Advanced Encryption Standard
AFC Automatic Frequency Control
AH Authentication Header
AMBR Aggregate Maximum Bit Rate
AMC Adaptive Modulation and Coding
AMR Adaptive Multi-Rate
ANR Automatic Neighboring Relation

ARP Allocation/Retention Priority
ARQ Automatic Repeat Request
B
BCH Broadcast Channel
BCCH Broadcast Control Channel

BITS Building Integrated Timing Supply System
BLER Block Error Rate

C
CA Carrier aggregation
C/I Carrier-to-Interference Power Ratio
CCCH Common Control Channel
CDMA Code Division Multiple Access
CEU Cell Edge Users
CGI Cell Group Indicator
CME Configuration Management Express
CP Cyclic Prefix
CPICH Common Pilot Channel
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
CRS Cell-specific reference signal

CSI-RS Channel state information reference signal
D
DCCH Dedicated Control Channel
DES Data Encryption Standard
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Services
DL-SCH Downlink Shared Channel
DRB Data Radio Bearer
DRX Discontinuous Reception
DSCP DiffServ Code Point
DTCH Dedicated Traffic Channel
E
ECM EPS Control Management
eCSFB Enhanced CS Fallback
EDF Early Deadline First
EF Expedited Forwarding
eHRPD Evolved high rate packet data

eICIC Enhanced Inter-cell Interference

Coordination
eMBMS evolved Multimedia Broadcast Multimedia
System
EMM EPS Mobility Management
EMS Element Management System
eNodeB evolved NodeB
EPC Evolved Packet Core
EPS Evolved Packet System
ESP Encapsulation Security Payload
ETWS Earthquake and Tsunami Warning System
E-UTRA Evolved –Universal Terrestrial Radio

Access
F
FCPSS Fault, Configuration, Performance, Security
and Software Managements
FDD Frequency Division Duplex
FEC Forward Error Correction
FTP File Transfer Protocol
G
GBR Guaranteed Bit Rate
GERAN GSM/EDGE Radio Access Network
GPS Global Positioning System
H
HARQ Hybrid Automatic Repeat Request
HII High Interference Indicator
HMAC Hash Message Authentication Code

HMAC_MD5 HMAC Message Digest 5
HMAC_SHA HMAC Secure Hash Algorithm
HO Handover
HRPD High Rate Packet Data

I
ICIC Inter-cell Interference Coordination
IKEV Internet Key Exchange Version
IMS IP Multimedia Service
IP PM IP Performance Monitoring
IPsec IP Security
IRC Interference Rejection Combining
K
KPI Key Performance Indicator
L
LMT Local Maintenance Terminal
M
MAC Medium Admission Control
MIB Master Information Block
MCH Multicast Channel
MCCH Multicast Control Channel
MCS Modulation and Coding Scheme
MIMO Multiple Input Multiple Output
min_GBR Minimum Guaranteed Bit Rate
MME Mobility Management Entity
MML Man-Machine Language
MOS Mean Opinion Score

MRC Maximum-Ratio Combining
MTCH Multicast Traffic Channel
MU-MIMO Multiple User-MIMO
N
NACC Network Assisted Cell Changed

NACK Non acknowledgment

NAS Non-Access Stratum
NRT Neighboring Relation Table
O
OCXO Oven Controlled Crystal Oscillator
OFDM Orthogonal Frequency Division
Multiplexing
OFDMA Orthogonal Frequency Division
Multiplexing Access
OI Overload Indicator
OMC Operation and Maintenance Center

OOK On-Off-Keying
P
PBCH Physical Broadcast Channel
PCCH Paging Control Channel
PCFICH Physical Control Format Indicator Channel
PCH Paging Channel
PCI Physical Cell Identity
PDB Packet Delay Budget
PDCCH Physical Downlink Control Channel
PDCP Packet Data Convergence Protocol
PDH Plesiochronous Digital Hierarchy
PDSCH Physical Downlink Shared Channel

PF Proportional Fair
PHB Per-Hop Behavior
PHICH Physical Hybrid ARQ Indicator Channel
PM Performance Measurement
PLMN Public Land Mobile Network
PMCH Physical Multicast Channel

PRACH Physical Random Access Channel
PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel
Q
QAM Quadrature Amplitude Modulation
QCI QoS Class Identifier
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
R
RA Random Access
RACH Random Access Channel
RAM Random Access Memory
RAT Radio Access Technology

RB Resource Block
RCU Radio Control Unit
RET Remote Electrical Tilt
RF Radio Frequency
RLC Radio Link Control
RRC Radio Resource Control
RRM Radio Resource Management
RRU Remote Radio Unit
RS Reference Signal
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
RSSI Received Signal Strength Indicator
RTT Round Trip Time

RV Redundancy Version
Rx Receive
S
S1 interface between EPC and E-UTRAN
SBT Smart Bias Tee

SC-FDMA Single Carrier-Frequency Division Multiple

Access
SCTP Stream Control Transmission Protocol
SDH Synchronous Digital Hierarchy
SFBC Space Frequency Block Coding
SFP Small Form – factor Pluggable
SGW Serving Gateway
SIB System Information Block
SID Silence Indicator

SINR Signal to Interference plus Noise Ratio
SRB Signaling Radio Bearer
SRS Sounding Reference Signal
SSL Security Socket Layer
STBC Space Time Block Coding
STMA Smart TMA
T
TAC Transport Admission Control
TCP Transmission Control Protocol
TDD Time Division Duplex
TMA Tower Mounted Amplifier
TMF Traced Message Files
ToS Type of Service
TTI Transmission Time Interval
Tx Transmission
U
UE User Equipment
UL-SCH Uplink Shared Channel

USB Universal Serial Bus
U2000 Huawei OMC

V
VLAN Virtual Local Area Network
VoIP Voice over IP
W
WRR Weighted Round Robin
X
X2 interface among eNodeBs


ERAN12.1 Feature Description

Uploaded by

Document Information

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

ERAN12.1 Feature Description

Uploaded by

Copyright:

Available Formats

LTE eRAN12.

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2017-03-22) Huawei Proprietary and Confidential i

1 LTE Basic Features ........................................................................................................................ 1

Issue 01 (2017-03-22) Huawei Proprietary and Confidential ii

1.2.18 LBFD-002016 Dynamic Downlink Power Allocation ........................................................................................... 30

Issue 01 (2017-03-22) Huawei Proprietary and Confidential iii

1.2.46 LBFD-001027 Active Queue Management (AQM) .............................................................................................. 71

Issue 01 (2017-03-22) Huawei Proprietary and Confidential iv

1.4.8 LBFD-004008 Performance Management ............................................................................................................. 107

2 LTE Optional Features ............................................................................................................. 125

Issue 01 (2017-03-22) Huawei Proprietary and Confidential v

2.1.3.11 LOFD-001035 CS Fallback to CDMA2000 1xRTT ......................................................................................... 163

Issue 01 (2017-03-22) Huawei Proprietary and Confidential vi

2.2.6.2 LOFD-070205 Adaptive SFN/SDMA ................................................................................................................ 229

Issue 01 (2017-03-22) Huawei Proprietary and Confidential vii

Issue 01 (2017-03-22) Huawei Proprietary and Confidential viii

2.3.2.4 LOFD-081220 Inter-BBU Clock Sharing ........................................................................................................... 349

Issue 01 (2017-03-22) Huawei Proprietary and Confidential ix

2.4.2.2 LOFD-001039 RF Channel Intelligent Shutdown .............................................................................................. 414

3 Acronyms and Abbreviations ................................................................................................. 423

Issue 01 (2017-03-22) Huawei Proprietary and Confidential x

1 LTE Basic Features

1.1 Standards Compliance

1.1 Standards Compliance

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 1

1.1.2 LBFD-001007 3GPP R9 Specifications

1.1.3 LBFD-001008 3GPP R10 Specifications

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 2

1.1.4 LBFD-001009 3GPP R11 Specifications

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 3

1.1.5 LBFD-110101 3GPP R12 Specifications

1.1.6 LBFD-121101 3GPP R13 Specifications

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 4

1.1.7 LBFD-001002 FDD mode

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 5

1.1.8 LBFD-001003 Scalable Bandwidth

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 6

1.1.9 LBFD-001004 CP length

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 7

1.1.10 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM,

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 8

1.1.11 LBFD-001006 AMC

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 9

1.1.12 LBFD-001030 Support of UE Category 2/3/4

UE Category Max. No. of Max. No. of Total No. of Max. No. of

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 10

UE Category Max. No. of Bits of a Support for UL 64QAM

UE Category Total L2 Buffer Size (kBytes)

1.2 RAN Architecture & Features

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 11

 applicable to LampSite from eRAN6.0

1.2.2 LBFD-002002 Transport Channel Management

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 12

1.2.3 LBFD-002003 Physical Channel Management

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 13

appropriate physical time-frequency resources. Based on the mapping, a transport channel at

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 14

1.2.4 LBFD-002004 Integrity Protection

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 15

1.2.5 LBFD-002005 DL Asynchronous HARQ

Issue 01 (2017-03-22) Huawei Proprietary and Confidential 16