LTE FDD eRAN8.1 Optional Feature Description PDF

eRAN
eRAN8.1
Optional Feature Description
Issue 01
Date 2015-01-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. 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
Huawei Proprietary and Confidential

Issue 01 (2015-01-15) i
Copyright Huawei Technologies Co., Ltd.
eRAN
Optional Feature Description Contents
Contents
1 Voice & Other Services ................................................................................................................ 1

1.1 VoLTE Capacity & Coverage........................................................................................................................................ 1
1.1.1 LOFD-001016 VoIP Semi-persistent Scheduling ...................................................................................................... 1
1.1.2 LOFD-001017 RObust Header Compression (ROHC) ............................................................................................. 3
1.1.3 LOFD-001048 TTI Bundling ..................................................................................................................................... 4
1.1.4 LOFD-081229 Voice Characteristic Awareness Scheduling ...................................................................................... 5
1.2 SRVCC to UTRAN ....................................................................................................................................................... 7
1.2.1 LOFD-001022 SRVCC to UTRAN ........................................................................................................................... 7
1.2.2 LOFD-001087 SRVCC Flexible Steering to UTRAN ............................................................................................... 8
1.3 SRVCC to GERAN ....................................................................................................................................................... 9
1.3.1 LOFD-001023 SRVCC to GERAN ........................................................................................................................... 9
1.4 CSFB to UTRAN ........................................................................................................................................................ 11
1.4.1 LOFD-001033 CS Fallback to UTRAN .................................................................................................................. 11
1.4.2 LOFD-070202 Ultra-Flash CSFB to UTRAN ......................................................................................................... 13
1.4.3 LOFD-001052 Flash CS Fallback to UTRAN ......................................................................................................... 15
1.4.4 LOFD-001068 CS Fallback with LAI to UTRAN ................................................................................................... 16
1.4.5 LOFD-001088 CS Fallback Steering to UTRAN .................................................................................................... 17
1.5 CSFB to GERAN ........................................................................................................................................................ 18
1.5.1 LOFD-001034 CS Fallback to GERAN .................................................................................................................. 18
1.5.2 LOFD-001053 Flash CS Fallback to GERAN ......................................................................................................... 19
1.5.3 LOFD-081283 Ultra-Flash CSFB to GERAN ......................................................................................................... 20
1.5.4 LOFD-001069 CS Fallback with LAI to GERAN ................................................................................................... 22
1.5.5 LOFD-001089 CS Fallback Steering to GERAN .................................................................................................... 23
1.6 CSFB to 1xRTT .......................................................................................................................................................... 24
1.6.1 LOFD-001035 CS Fallback to CDMA2000 1xRTT ................................................................................................ 24
1.6.2 LOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT ............................................................................... 25
1.6.3 LOFD-001091 CS Fallback to CDMA2000 1xRTT Based on Frequency-specific Factors .................................... 27
1.6.4 LOFD-080212 SRLTE Optimization ....................................................................................................................... 29
1.7 LCS & Broadcasting ................................................................................................................................................... 30
1.7.1 LOFD-001047 LoCation Services (LCS) ................................................................................................................ 30
1.7.2 LOFD-001092 CMAS Support ................................................................................................................................ 31
1.7.3 LOFD-008002 Dynamic Service-specific Access Control ...................................................................................... 32
1.8 eMBMS ...................................................................................................................................................................... 34
Issue 01 (2015-01-15) Huawei Proprietary and Confidential ii

eRAN
1.8.1 LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture ............................................................. 34

1.8.1.1 LOFD-07022001 Multi-cell transmission in MBSFN area................................................................................... 36
1.8.1.2 LOFD-07022002 Mixed transmission of unicast and broadcast ........................................................................... 37
1.8.1.3 LOFD-07022003 Data synchronization ................................................................................................................ 38
1.8.1.4 LOFD-07022004 Session admission control ........................................................................................................ 39
1.8.2 LOFD-080215 eMBMS Service Continuity ............................................................................................................ 40
2 Radio & Performance ................................................................................................................. 42

2.1 LTE 2 Antenna 150M/50Mbps ................................................................................................................................... 42
2.1.1 LOFD-001001 DL 2x2 MIMO ................................................................................................................................ 42
2.1.2 LOFD-001030 Support of UE Category 2/3/4 ......................................................................................................... 44
2.2 LTE 2 Antenna 150M/100Mbps ................................................................................................................................. 46
2.2.1 LOFD-001002 UL 2x2 MU-MIMO......................................................................................................................... 46
2.2.2 LOFD-001006 UL 64QAM ..................................................................................................................................... 47
2.3.1 LOFD-001003 DL 4x2 MIMO ................................................................................................................................ 48
2.3.2 LOFD-001005 UL 4-Antenna Receive Diversity .................................................................................................... 49
2.3.3 LOFD-001058 UL 2x4 MU-MIMO......................................................................................................................... 50
2.4.1 LOFD-001060 DL 4X4 MIMO ............................................................................................................................... 51
2.5 Interference Handling ................................................................................................................................................. 52
2.5.1 LOFD-001012 UL Interference Rejection Combining ............................................................................................ 52
2.5.2 LOFD-001014 Dynamic Inter-Cell Interference Coordination ................................................................................ 53
2.5.2.1 LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination ........................................................ 53
2.5.2.2 LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination ............................................................. 54
2.5.3 LOFD-060201 Adaptive Inter-Cell Interference Coordination ................................................................................ 55
2.5.4 LOFD-001067 800M Self-interference Cancellation .............................................................................................. 56
2.5.5 LOFD-001093 PUCCH Flexible Configuration ...................................................................................................... 57
2.5.6 LOFD-001094 Control Channel IRC ....................................................................................................................... 58
2.5.7 LOFD-001096 Advanced Receiver (PSIC) .............................................................................................................. 59
2.5.8 LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB) ............................................................ 60
2.5.9 LOFD-081206 Intra-eNodeB Coordinated Uplink AMC ........................................................................................ 62
2.6 UL CoMP.................................................................................................................................................................... 63
2.6.1 LOFD-001066 Intra-eNodeB UL CoMP ................................................................................................................. 63
2.6.2 LOFD-070222 Intra-eNodeB UL CoMP Phase II ................................................................................................... 66
2.6.3 LOFD-070223 UL CoMP based on Coordinated BBU ........................................................................................... 68
2.6.4 LOFD-081219 UL CoMP Based on Relaxed Backhaul ........................................................................................... 71
2.7 QoS ............................................................................................................................................................................. 75
2.7.1 LOFD-001015 Enhanced Scheduling ...................................................................................................................... 75
2.7.1.1 LOFD-00101501 CQI Adjustment ....................................................................................................................... 75
2.7.1.2 LOFD-00101502 Dynamic Scheduling ................................................................................................................ 76
2.7.2 LOFD-001026 TCP Proxy Enhancer (TPE) ............................................................................................................ 77
Issue 01 (2015-01-15) Huawei Proprietary and Confidential iii

eRAN
2.7.3 LOFD-001027 Active Queue Management (AQM) ................................................................................................ 79

2.7.4 LOFD-001029 Enhanced Admission Control .......................................................................................................... 80
2.7.4.1 LOFD-00102901 Radio/transport resource pre-emption ...................................................................................... 80
2.7.5 LOFD-001054 Flexible User Steering ..................................................................................................................... 81
2.7.5.1 LOFD-00105401 Camp & Handover Based on SPID .......................................................................................... 81
2.7.6 LOFD-001059 UL Pre-allocation Based on SPID ................................................................................................... 83
2.7.7 LOFD-001109 DL Non-GBR Packet Bundling ....................................................................................................... 84
2.7.8 LOFD-081202 Busy-Hour Download Rate Control ................................................................................................ 85
2.7.9 LOFD-081203 Video Service Rate Adaption .......................................................................................................... 86
2.7.10 LOFD-081218 Enhanced Extended QCI ............................................................................................................... 87
2.8 Signaling Storm & Terminal Battery Life Saving ....................................................................................................... 88
2.8.1 LOFD-001105 Dynamic DRX ................................................................................................................................. 88
2.8.1.1 LOFD-00110501 Dynamic DRX .......................................................................................................................... 88
2.8.1.2 LOFD-00110502 High-Mobility-Triggered Idle Mode ........................................................................................ 90
2.8.2 LOFD-070207 Intelligent Access Class Control...................................................................................................... 91
2.9 Inter-RAT Mobility to UTRAN .................................................................................................................................. 92
2.9.1 LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN .............................................................. 92
2.9.2 LOFD-001043 Service based inter-RAT handover to UTRAN ............................................................................... 95
2.9.3 LOFD-001072 Distance based Inter-RAT handover to UTRAN ............................................................................. 96
2.9.4 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering ........................................................................................... 97
2.9.5 LOFD-070216 Separate Mobility Policies to UTRAN for Multi PLMN ................................................................ 98
2.9.6 LOFD-070203 RIM Based LTE Target Cell Selection ............................................................................................ 98
2.10 Inter-RAT Mobility to GERAN .............................................................................................................................. 100
2.10.1 LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN .......................................................... 100
2.10.2 LOFD-001046 Service based inter-RAT handover to GERAN ........................................................................... 103
2.10.3 LOFD-001073 Distance based Inter-RAT handover to GERAN ......................................................................... 104
2.11 Inter-RAT Mobility to CDMA2000 ........................................................................................................................ 105
2.11.1 LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000 .................................................... 105
2.11.2 LOFD-001111 PS Mobility from E-UTRAN to CDMA2000 HRPD Based on Frequency-specific Factors....... 107
2.12 Refarming ............................................................................................................................................................... 108
2.12.1 LOFD-001051 Compact Bandwidth .................................................................................................................... 108
2.13 High Speed Mobility............................................................................................................................................... 110
2.13.1 LOFD-001007 High Speed Mobility ................................................................................................................... 110
2.13.2 LOFD-001008 Ultra High Speed Mobility .......................................................................................................... 111
2.13.3 LOFD-081228 Handover Enhancement at Speed Mobility ................................................................................. 112
2.14 Coverage Enhancement .......................................................................................................................................... 113
2.14.1 LOFD-001009 Extended Cell Access Radius ...................................................................................................... 113
2.14.2 LOFD-001031 Extended CP ................................................................................................................................ 114
2.14.3 LOFD-081223 Extended Cell Access Radius Beyond 100km............................................................................. 115
3 Networking & Transmission & Security .............................................................................. 118

3.1 Transmission & Synchronization .............................................................................................................................. 118
Issue 01 (2015-01-15) Huawei Proprietary and Confidential iv

eRAN
3.1.1 LOFD-003002 2G/3G and LTE Co-transmission .................................................................................................. 118

3.1.2 LOFD-003011 Enhanced Transmission QoS Management ................................................................................... 120
3.1.2.1 LOFD-00301101 Transport Overbooking ........................................................................................................... 120
3.1.2.2 LOFD-00301102 Transport Differentiated Flow Control ................................................................................... 121
3.1.2.3 LOFD-00301103 Transport Resource Overload Control .................................................................................... 122
3.1.3 LOFD-003012 IP Performance Monitoring ........................................................................................................... 123
3.1.3.1 LOFD-00301201 IP Performance Monitoring .................................................................................................... 123
3.1.3.2 LOFD-00301202 Transport Dynamic Flow Control........................................................................................... 124
3.1.4 LOFD-070219 IP Active Performance Measurement ............................................................................................ 124
3.1.5 LOFD-003013 Enhanced Synchronization ............................................................................................................ 127
3.1.5.1 LOFD-00301301 Synchronization with Ethernet (ITU-T G.8261) ..................................................................... 127
3.1.5.2 LOFD-00301302 IEEE1588 V2 Clock Synchronization .................................................................................... 128
3.1.5.3 LOFD-00301303 Clock over IP (Huawei proprietary) ....................................................................................... 131
3.1.6 LOFD-003016 Different Transport Paths based on QoS Grade............................................................................. 133
3.1.7 LOFD-080216 Uu based Soft Synchronization ..................................................................................................... 134
3.1.8 LOFD-081220 Inter-BBU Clock Sharing .............................................................................................................. 135
3.2 IPv6........................................................................................................................................................................... 136
3.2.1 LOFD-003017 S1 and X2 over IPv6 ..................................................................................................................... 136
3.2.2 LOFD-003023 IEEE 1588v2 over IPv6................................................................................................................. 138
3.2.3 LOFD-003024 IPsec for IPv6 ................................................................................................................................ 139
3.3 Security ..................................................................................................................................................................... 140
3.3.1 LOFD-001010 Security Mechanism ...................................................................................................................... 140
3.3.1.1 LOFD-00101001 Encryption: AES..................................................................................................................... 140
3.3.1.2 LOFD-00101002 Encryption: SNOW 3G .......................................................................................................... 141
3.3.1.3 LOFD-00101003 Encryption: ZUC .................................................................................................................... 142
3.3.2 LOFD-003009 IPsec .............................................................................................................................................. 143
3.3.3 LOFD-003010 Public Key Infrastructure (PKI) .................................................................................................... 144
3.3.4 LOFD-003014 Integrated Firewall ........................................................................................................................ 146
3.3.4.1 LOFD-00301401 Access Control List (ACL) ..................................................................................................... 146
3.3.4.2 LOFD-00301402 Access Control List (ACL) Auto Configuration ..................................................................... 147
3.3.5 LOFD-003015 Access Control based on 802.1x ................................................................................................... 148
3.3.6 LOFD-070211 IPSec Redundancy Among Multiple SeGWs ................................................................................ 149
3.3.7 LOFD-070212 eNodeB Supporting PKI Redundancy ........................................................................................... 150
3.4 Reliability ................................................................................................................................................................. 152
3.4.1 LOFD-001018 S1-flex ........................................................................................................................................... 152
3.4.2 LOFD-003004 Ethernet OAM ............................................................................................................................... 154
3.4.2.1 LOFD-00300401 Ethernet OAM (IEEE 802.3ah) .............................................................................................. 154
3.4.2.2 LOFD-00300402 Ethernet OAM (IEEE 802.1ag) .............................................................................................. 155
3.4.2.3 LOFD-00300403 Ethernet OAM (Y.1731) ......................................................................................................... 156
3.4.3 LOFD-003005 OM Channel Backup ..................................................................................................................... 157
3.4.4 LOFD-003006 IP Route Backup............................................................................................................................ 158
3.4.5 LOFD-003007 Bidirectional Forwarding Detection .............................................................................................. 158
Issue 01 (2015-01-15) Huawei Proprietary and Confidential v

eRAN
3.4.6 LOFD-003008 Ethernet Link Aggregation (IEEE 802.3ad) .................................................................................. 160

3.4.7 LOFD-003019 IPsec Tunnel Backup ..................................................................................................................... 161
3.4.8 LOFD-081280 eNodeB Supporting Multi-operator PKI ....................................................................................... 162
3.4.9 LOFD-081281 eNodeB Supporting IPsec Redirection .......................................................................................... 164
3.5 RAN Sharing ............................................................................................................................................................ 166
3.5.1 LOFD-001036 RAN Sharing with Common Carrier ............................................................................................. 166
3.5.2 LOFD-001037 RAN Sharing with Dedicated Carrier ........................................................................................... 168
3.5.3 LOFD-001086 RAN Sharing by More Operators .................................................................................................. 170
3.5.4 LOFD-001112 MOCN Flexible Priority Based Camping...................................................................................... 171
3.5.5 LOFD-070206 Hybrid RAN Sharing ..................................................................................................................... 171
3.5.6 LOFD-070204 Operator Load Based Intra-LTE MLB .......................................................................................... 174
3.5.7 LOFD-070213 Fair User Sharing .......................................................................................................................... 175
3.5.8 LOFD-070210 Multi Operators SPID Policy ........................................................................................................ 176
3.6 Advance Micro.......................................................................................................................................................... 177
3.6.1 LOFD-002016 Micro eNodeB Self-planning ........................................................................................................ 177
3.6.2 LOFD-001057 Load Balancing based on Transport QoS ...................................................................................... 178
3.6.3 LOFD-003022 PPPoE............................................................................................................................................ 179
3.6.4 LOFD-003031 Horizon Beam-Width Adjustment ................................................................................................. 180
3.7 Site Architecture ....................................................................................................................................................... 181
3.7.1 LOFD-001076 CPRI Compression ........................................................................................................................ 181
3.7.2 LOFD-003032 Intra-BBU Baseband Sharing (2T) ................................................................................................ 182
3.7.3 LOFD-003029 SFN ............................................................................................................................................... 183
3.7.4 LOFD-070205 Adaptive SFN/SDMA ................................................................................................................... 185
3.7.5 LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU ........................................................................... 187
3.7.6 LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on Coordinated BBU ............................................... 189
3.7.7 LOFD-081221 Super Combined Cell .................................................................................................................... 191
4 O&M ............................................................................................................................................ 194

4.1 SON Self-Configuration ........................................................................................................................................... 194
4.1.1 LOFD-002001 Automatic Neighbour Relation (ANR) .......................................................................................... 194
4.1.2 LOFD-002002 Inter-RAT ANR ............................................................................................................................. 197
4.1.3 LOFD-002004 Self-configuration ......................................................................................................................... 201
4.1.4 LOFD-002007 PCI Collision Detection & Self-Optimization ............................................................................... 204
4.1.5 LOFD-081225 Neighbor Cell Classification Management ................................................................................... 207
4.2 SON Self-Optimization............................................................................................................................................. 208
4.2.1 LOFD-001032 Intra-LTE Load Balancing............................................................................................................. 208
4.2.2 LOFD-070215 Intra-LTE User Number Load Balancing ...................................................................................... 209
4.2.3 LOFD-081227 Intra-LTE Load Balancing for Non-cosited Cells ......................................................................... 210
4.2.4 LOFD-001044 Inter-RAT Load Sharing to UTRAN ............................................................................................. 212
4.2.5 LOFD-001045 Inter-RAT Load Sharing to GERAN ............................................................................................. 213
4.2.6 LOFD-002005 Mobility Robust Optimization (MRO) .......................................................................................... 214
4.2.7 LOFD-002015 RACH Optimization ...................................................................................................................... 216
Issue 01 (2015-01-15) Huawei Proprietary and Confidential vi

eRAN
4.2.8 LOFD-081207 Specified PCI Group-based Neighboring Cell Management ......................................................... 218
4.2.9 LOFD-081205 Automatic Congestion Handling ................................................................................................... 219
4.3 SON Self-Healing ..................................................................................................................................................... 221
4.3.1 LOFD-002010 Sleeping Cell Detection ................................................................................................................. 221
4.3.2 LOFD-002011 Antenna Fault Detection ................................................................................................................ 222
4.3.3 LOFD-002012 Cell Outage Detection and Compensation .................................................................................... 223
4.4 Power Saving ............................................................................................................................................................ 224
4.4.1 LOFD-001025 Adaptive Power Consumption ....................................................................................................... 224
4.4.2 LOFD-001039 RF Channel Intelligent Shutdown ................................................................................................. 225
4.4.3 LOFD-001040 Low Power Consumption Mode.................................................................................................... 227
4.4.4 LOFD-001041 Power Consumption Monitoring ................................................................................................... 228
4.4.5 LOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage .............................................................. 229
4.4.6 LOFD-001056 PSU Intelligent Sleep Mode .......................................................................................................... 230
4.4.7 LOFD-001070 Symbol Power Saving ................................................................................................................... 231
4.4.8 LOFD-001071 Intelligent Battery Management .................................................................................................... 232
4.4.9 LOFD-001074 Intelligent Power-Off of Carriers in the Same Coverage of UMTS Network ............................... 234
4.4.10 LOFD-001075 RRU PA Efficiency Improvement ............................................................................................... 235
4.5 Antenna Management ............................................................................................................................................... 236
4.5.1 LOFD-001024 Remote Electrical Tilt Control ...................................................................................................... 236
5 Acronyms and Abbreviations ................................................................................................. 238
Issue 01 (2015-01-15) Huawei Proprietary and Confidential vii

eRAN
Optional Feature Description 1 Voice & Other Services
1 Voice & Other Services
1.1 VoLTE Capacity & Coverage

1.2 SRVCC to UTRAN
1.3 SRVCC to GERAN
1.4 CSFB to UTRAN
1.5 CSFB to GERAN
1.6 CSFB to 1xRTT
1.7 LCS & Broadcasting
1.8 eMBMS
1.1 VoLTE Capacity & Coverage

1.1.1 LOFD-001016 VoIP Semi-persistent Scheduling
Availability
This feature is
applicable to Macro from eRAN2.0
applicable to Micro from eRAN3.0
applicable to Lampsite from eRAN6.0
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.
Issue 01 (2015-01-15) Huawei Proprietary and Confidential 1

eRAN
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.

eRAN
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 0x00000x0004 based on both IPv4 and IPv6 (Micro
eNodeB Table 2-2 shows the profile identifiers
and their associated header compression protocols.
Table 1-1 ROHC profile identifier and header compression protocol
Profile Identifier Usage:

eRAN
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.
1.1.3 LOFD-001048 TTI Bundling

Availability
This feature is
applicable to Micro form eRAN3.0
not applicable to Lampsite
Summary
TTI bundling transmission is introduced to improve LTE uplink coverage. The UEs in cell
edge with poor uplink SINR can retransmit the same data block in continuous subframe by
means of TTI bundling.
Benefits
TTI bundling could help to improve uplink coverage and in-house reception for voice.
Description
TTI bundling transmission is introduced to improve LTE uplink coverage. The UEs in cell
edge with poor uplink SINR can retransmit the same data block in continuous subframe by
means of TTI bundling.. The activation and deactivation of TTI bundling transmission is
controlled by RRC signaling message.
If TTI bundling is configured by the RRC layer, TTI_BUNDLE_SIZE provides the number of
TTIs of a TTI bundle. Within a TTI bundle, HARQ retransmissions are non-adaptive and shall

eRAN
be performed without waiting for feedbacks (e.g. NACK or ACK ) related to previous
transmissions according to TTI_BUNDLE_SIZE. A 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 fixed to 4.
Enhancement
In eRAN8.1
When performing mixed services, UEs enter the TTI bundling state if VoIP services
(QCI of 1) are included.
Dependency
eNodeB
None
eCO
None
UE
The UE should support TTI Bundling.
Transport network
None
CN
None
OSS
None
Other features
This feature is not supported in 1.4MHz system bandwidth.
This feature is applicable for VoIP service only.
Others
None
1.1.4 LOFD-081229 Voice Characteristic Awareness Scheduling

Availability
This feature is
Applicable to Macro from eRAN8.1.
Applicable to Micro from eRAN8.1.
Applicable to Lampsite from 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 uplink volume to be scheduled to improve uplink voice performance in heavy
traffic scenarios.

eRAN
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; a longer waiting time
indicates a higher priority. This way, the eNodeB makes a balance among scheduling queues
and improves voice quality, especially the voice quality of UEs at the cell edge where channel
conditions are poor.
Uplink VoLTE volume estimation for dynamic scheduling
The eNodeB estimates uplink VoLTE volume for dynamic scheduling based on the
VoLTE 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 volume of
voice packets 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
None
Dependency
eNodeB
None
eCo
None
UE
None
Transport network
None
CN
None
OSS
None

eRAN
Other features
This feature applies only to VoLTE services. This feature requires the following features:
LBFD-002025 Basic Scheduling
LOFD-00101502 Dynamic Scheduling
Others
None
1.2 SRVCC to UTRAN

1.2.1 LOFD-001022 SRVCC to UTRAN
Availability
This feature is
Summary
Single Radio Voice Call Continuity (SRVCC) is voice call continuity between IMS over PS
access and CS access for calls that are anchored in the IMS when the UE is capable of
transmitting/receiving on only one of those access networks at a given time.
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 is used to maintain voice call
continuity for the UE.
For facilitating session transfer (SRVCC) of the voice component to the CS domain, the IMS
multimedia telephony sessions need to be anchored 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. The MME is responsible for processing the Forward

eRAN
Relocation Response from the MSC Server during the SRVCC and PS-PS handover
procedures.
The following figure shows the SRVCC from E-UTRAN to UTRAN
Figure 1-1 SRVCC from E-UTRAN to UTRAN
Enhancement
None
Dependency
CN
IMS multimedia telephony.
1.2.2 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.

eRAN
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
1.3 SRVCC to GERAN

1.3.1 LOFD-001023 SRVCC to GERAN
Availability
This feature is

eRAN
Summary
SRVCC is voice call continuity between IMS over PS access and CS access for calls that are
anchored in the IMS when the UE is capable of transmitting/receiving on only one of those
access networks at a given time.
Benefits
When a UE moves from E-UTRAN to GERAN, SRVCC maintains voice call continuity for
the UE.
Description
When a UE moves from E-UTRAN to GERAN, SRVCC is used to maintain voice call
continuity for the UE.
For facilitating session transfer (SRVCC) of the voice component to the CS domain, the IMS
multimedia telephony sessions need to be anchored in the IMS.
For SRVCC from E-UTRAN to GERAN, 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 GERAN.
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. The MME is responsible for processing the Forward
Relocation Response from the MSC Server during the SRVCC and PS-PS handover
procedures.
The following figure shows the SRVCC from E-UTRAN to GERAN

eRAN
Figure 1-2 SRVCC from E-UTRAN to GERAN
Enhancement
None
Dependency
CN
IMS multimedia telephony
1.4 CSFB to UTRAN

1.4.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.

eRAN
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 1-3 CS fallback in EPS architecture
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.
Dependency
UE
UE needs to support CSFB.
Other features
This feature depends on LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and
UTRAN.
Others

eRAN
Target load based CS fallback to UTRAN requires core network and RNC support
RIM-based load information transfer to eUTRAN.
1.4.2 LOFD-070202 Ultra-Flash CSFB to UTRAN

Availability
This feature is
applicable to LampSite from eRAN7.0
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 1-4 illustrates how this feature works.

eRAN
Figure 1-4 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
This feature requires the following features:
LOFD-001033 CS Fallback to UTRAN
WRFD-160271 Ultra-Flash CSFB
Others
None

eRAN
1.4.3 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

eRAN
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.
1.4.4 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.

eRAN
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.
1.4.5 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.

eRAN
Enhancement
None
Dependency
Other features
LOFD-001033 CS Fallback to UTRAN and LOFD-001078 E-UTRAN to UTRAN
CS/PS Steering.
1.5 CSFB to GERAN

1.5.1 LOFD-001034 CS Fallback to GERAN
Availability
This feature is
Summary
When UE is in the E-UTRAN and GERAN coverage overlapped area and E-UTRAN cannot
provide CS-domain services for the UE, we can use CS fallback to GERAN to provide
CS-domain service for the UE.
Benefits
We can use CS fallback to GERAN 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
connected to E-UTRAN may use GERAN to establish one or more CS-domain services. This
function is only available in case E-UTRAN coverage is overlapped by GERAN coverage.
The CS fallback in EPS function is realized by using the SGs interface mechanism between
the MSC Server and the MME.

eRAN
The MGW is not shown in the figure since the CS fallback in EPS does not have any impacts
to the U-plane handling<0}.
Enhancement
None
Dependency
UE
Other features
LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN.
1.5.2 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.

eRAN
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.
1.5.3 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.

eRAN
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 1-6 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

eRAN
Dependency
eNodeB
None
UE
UEs must support SRVCC from E-UTRAN to GERAN.
Transport network
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
1.5.4 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

eRAN
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.
1.5.5 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:

eRAN
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.
1.6 CSFB to 1xRTT

1.6.1 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
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.
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.

eRAN
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
1.6.2 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.

eRAN
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 1-8 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.

eRAN
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.
1.6.3 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.

eRAN
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 1-9 CSFB based on factors for CDMA2000 1xRTT frequencies
Enhancement
None
Dependency
Other features

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

Fallback to CDMA2000 1xRTT.
1.6.4 LOFD-080212 SRLTE Optimization

Availability
This feature is
Applicable to Macro from eRAN8.1
Applicable to Micro from eRAN8.1
Applicable to Lampsite from eRAN8.1
Summary
This feature enables the eNodeB to detect the period when an SRLTE-capable UE
periodically leaves or returns to RRC_CONNECTED state. The detection result serves as an
input to scheduling. SRLTE is short for Single Radio LTE.
Benefits
Upon detecting that an SRLTE-capable UE has left RRC_CONNECTED state, the eNodeB
switches to schedule other UEs, increasing cell throughput.
Description
An SRLTE-capable UE periodically leaves RRC_CONNECTED state to monitor a paging
channel on a CDMA2000 1X network. The UE does not notify the eNodeB of the monitoring,
and the eNodeB continues scheduling the UE, decreasing cell throughput.
The following figure shows the procedure in which an SRLTE-capable UE periodically leaves
the RRC_CONNECTED state to monitor a paging channel on a CDMA2000 1X network.
Figure 1-10 SRLTE-capable UE monitoring a paging channel on a CDMA2000 1X network
The paging cycle in the CDMA2000 1X network is specified by a parameter on the network.
The cycle can be set to 1.28s or 2.56s, for example. The monitoring duration is associated
with the paging cycle. The minimum duration is 80 ms. If other mechanisms such as TCP
penalty are used, the duration can reach 120 ms.
This feature enables the eNodeB to check the status of an SRLTE-capable UE. Upon detecting
that the UE has left RRC_CONNECTED state to monitor the paging channel on the
CDMA2000 1X network, the eNodeB switches to schedule other UEs, increasing the cell
throughput.

eRAN
Enhancement
None
Dependency
UE
UEs must support SRLTE.
1.7 LCS & Broadcasting

1.7.1 LOFD-001047 LoCation Services (LCS)
Availability
This feature is
Summary
LCS (LoCation Services) provides a method to identify UE's geographical location through
radio signal measurement.
Benefits
The feature LCS (LoCation Services) can be used to identify UE's geographical location
information such as longitude, latitude, velocity and so on. The geographical location
information can be used to offer a range of location based value added services. For instance,
it can be used by navigation applications, or for location requirements in emergency
call/lawful interception situations. For example, for E911 service, the alarm center can locate
the emergency call originator then conduct the appropriate rescue.
Description
The feature LCS provides a method to identify UE's geographical location by radio signal
measurement. A network element, E-SMLC (Enhanced Serving Mobile Location Centre), is
needed to support this feature.
The different positioning methods supported are:
Cell ID based Basic accuracy (depending on radio network density)
OTDOA (Observed Time Difference Of Arrival) Medium accuracy
A-GPS High accuracy
LCS feature is implemented mainly in E-SMLC and UE while the eNodeB acts as a
transparent entity for messages and information measurement forwarding. A typical LCS
procedure is:

eRAN
MME receives LCS request for a target UE location, or MME starts LCS service by
itself.
MME sends LCS request to E-SMLC.
E-SMLC sends auxiliary data to UE, check related measurement information from
UE/eNodeB. E-SMLC calculates out location information of target UE and forward it to
MME.
If MME does not host the LCS, MME will forward the location information to the network
element which hosts the LCS.
Enhancement
None
Dependency
UE
UE should support LCS for A-GPS and OTDOA.
CN
MME should support LPPa protocol.
E-SMLC is required.
Others
OTDOA requires Time synchronization for E-UTRAN.
E-CID requires intelligent antenna.
OTDOA and AGPS is not applicable to multi-mode scenario.
1.7.2 LOFD-001092 CMAS Support

Availability
This feature is
Summary
This feature enable eNodeB to support the commercial mobile alert system (CMAS). With
this feature, eNodeB will receive warning broadcast requests from MMEs, and then deliver
warning notifications to UEs in RRC_CONNECTED and RRC_IDLE mode by system
information (SI) broadcast.
Benefits
If disasters or other emergencies occur, 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.

eRAN
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 to help
protect 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 Write-Replace Warning procedure and Kill procedure defined in
3GPP S1 Application Protocol (S1AP) specification. 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.
CN
MMEs in the evolved packet core (EPC) must support CMAS.
1.7.3 LOFD-008002 Dynamic Service-specific Access Control

Availability
This feature is:
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.

eRAN
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.

eRAN
Transport network
None
CN
None
OSS
None
Other features
This feature requires the LBFD-002009 Broadcast of system information feature.
Others
None
1.8 eMBMS
1.8.1 LOFD-070220 eMBMS Phase 1 based on Centralized MCE
Architecture
Availability
This feature is
Summary
Huawei eMBMS phase 1 supports transmission of multimedia broadcast multicast service
(MBMS) based on the centralized multi-cell/multicast coordination entity (MCE) architecture,
which is defined in 3GPP Release 9.
Benefits
When operators provide unicast services and there is a large demand for services (for example,
live video of a football match) in an LTE network, eMBMS offers the following benefits:
A stable and bandwidth-guaranteed broadcast offers a satisfactory service experience.
There is no limit on the number of UEs that receive MBMS services, because MBMS
services are broadcast using semi-static radio resource configurations and the number of
UEs served is irrelevant to the amount of resources allocated.
Either RRC_IDLE or RRC_CONNECTED UEs can receive MBMS services. There is no limit on the
number of UEs that receive MBMS services. However, the maximum number of RRC_CONNECTED
UEs in an eMBMS-capable cell is subject to the cell capacity expressed in a number of UEs.
The broadcast allows resources to be shared in order to deliver the services in demand. It
reduces the requirement for unicast bearer resources and lowers the risk of network
congestion. In addition, it improves user experience with existing unicast services in a
heavily loaded or even congested network.

eRAN
eMBMS reduces investment in equipment for capacity expansion and allows operators to
develop new value-added services (for example, high-definition video) in order to
increase revenue.
Description
Compared with the LTE-SAE architecture that supports unicast services, an eMBMS-capable
LTE network incorporates three new network elements (NEs):
Broadcast multicast service center (BM-SC): supports service announcement, security
management, session management, transmission proxy, and data synchronization.
eMBMS gateway (MBMS GW): forwards MBMS user data to the eNodeB using IP multicast
over the M1 interface and performs MBMS session control (session start/stop) towards the
E-UTRAN through the MME. The MBMS GW can be deployed together with the P-GW.
MCE: performs admission control on MBMS sessions, and allocates multimedia broadcast
multicast service single frequency network (MBSFN) time-frequency resources used by all
eNodeBs in the MBSFN area for multi-cell MBMS transmissions.
In Huawei eMBMS phase 1, the MCE's functions are provided by the eCoordinator rather
than the eNodeB. The following figure shows the networking for eMBMS phase 1 based on
the centralized MCE architecture.
In eRAN7.0, frequency bands and bandwidths supported by Huawei eMBMS phase 1 are as
follows:
Frequency band: 800 MHz, 1800 MHz, and 2.6 GHz for LTE FDD
Bandwidth: 5 MHz, 10 MHz, 15 MHz, or 20 MHz for FDD cells;
Enhancement
eRAN8.1
Since eRAN8.1, Huawei eMBMS supports MBSFN area overlaps, that is, a single cell
can belong to a maximum of three MBSFN areas. The support of MBSFN area overlaps
enables more flexible deployment of MBMS services, especially when some services
must be transmitted across a wide area and some others 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
Allocation of MBSFN subframes in a centralized manner 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.

eRAN
LBBPc and LMPT do support this feature.

An eNodeB can now broadcast an MBMS session in different MBSFN areas at the same
time. The application scenarios are as follows:
RRUs are installed remotely. In addition, a single MBSFN area cannot include all the
cells served by the remote RRUs or include these cells and the cells served by local
RF units.
The eNodeB operates in multiple frequency bands, and eMBMS is required in more
than one of the bands.
Since eRAN8.1, Huawei eMBMS supports cell-specific PMCH transmit power
configuration. If the transmit power of a cell does not reach the licensed power and the
transmit power of the sector equipment serving the cell does not reach the maximum, the
cell-specific PMCH transmit power can be increased by modifying the offset parameter.
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.
Dependency
eCO
eCO6910 should be deployed.
CN
The feature requires the support from EPC NEs, including the BM-SC, MBMS GW, and
MBMS-capable MME.
UE
This feature requires the support from UEs. UEs must comply with 3GPP Release 9 or
later.
Transport network
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: 1.5s.
1.8.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.

eRAN
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.
1.8.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.

eRAN
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.
1.8.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.

eRAN
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.
1.8.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.

eRAN
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
1.8.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.

eRAN
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.

eRAN
Optional Feature Description 2 Radio & Performance
2 Radio & Performance
2.1 LTE 2 Antenna 150M/50Mbps

2.5 Interference Handling
2.6 UL CoMP
2.7 QoS
2.8 Signaling Storm & Terminal Battery Life Saving
2.9 Inter-RAT Mobility to UTRAN
2.10 Inter-RAT Mobility to GERAN
2.11 Inter-RAT Mobility to CDMA2000
2.12 Refarming
2.13 High Speed Mobility
2.14 Coverage Enhancement

2.1.1 LOFD-001001 DL 2x2 MIMO
Availability
This feature is

eRAN
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 to 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.

eRAN
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.1.2 LOFD-001030 Support of UE Category 2/3/4

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. So there are five categories defined in the
protocol. This feature can enable BS to support UE category 2/3/4.
Benefits
This feature can enable BS to support UE category 2/3/4.
Description
E-UTRAN needs to respect the signaled UE radio access capability parameters when
configuring the UE and when scheduling the UE. So there are five categories defined in the
protocol. This feature can enable base station to support UE category 2/3/4.
Table 2-1 Downlink physical layer parameter values set by the field UE-Category
UE Category Maximum Maximum Total number Maximum

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

Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2

eRAN
UE Category Maximum Maximum Total number Maximum

number of number of of soft number of
DL-SCH bits of a channel bits supported
transport DL-SCH layers for
blocks bits transport spatial
received block multiplexing
within a TTI received in DL
within a TTI
Category 5 299552 149776 3667200 4
Table 2-2 Uplink physical layer parameter values set by the field UE-Category
UE Category Maximum number of Support for 64QAM in

bits of an UL-SCH UL
transport block
transmitted within a TTI
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No
Category 5 75376 Yes
Table 2-3 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
The UE should be category 2/3/4.

eRAN

2.2.1 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 UE have good uplink
channel SINR and good channel orthogonality with the other UE, 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

eRAN
UL 2x2 MU-MIMO requires the eNodeB to provide 2 RX channels and 2 antennas per
sector.
2.2.2 LOFD-001006 UL 64QAM

Availability
This feature is
Summary
UL 64QAM enhances the uplink modulation scheme and allows UE in good radio
environments to transmit data to the eNodeB at a higher data rate. The feature increases
uplink data throughput and provides fast data transmission.
Benefits
This feature provides a higher service bit rate to increase cell throughput and improve user
experience.
Description
The uplink 64QAM is a complementary modulation scheme to Quadrature Phase Shift
Keying (QPSK) and 16QAM. The uplink 64QAM is intended to increase the bit rate for UEs
in excellent channel condition. Compared with two information bits carried at each symbol
using QPSK and four information bits using 16QAM, six information bits can be modulated
with each symbol using 64QAM. Therefore, 64QAM can significantly improve the system
capacity in uplink.
Depending upon the quality of radio environment, the eNodeB can select QAM modulation
schemes of different orders. If a UE in a good radio environment, the eNodeB could select the
highest order QAM modulation (64QAM mode) and large transport blocks for uplink
transmission to achieve a higher data rate.
Enhancement
None
Dependency
eNodeB
For Micro, this feature is only applicable to 3203E.
UE
This modulation scheme can be used only for UEs in excellent channel condition. The
UE should support 64QAM modulation.

eRAN

2.3.1 LOFD-001003 DL 4x2 MIMO
Availability
This feature is
not applicable to Micro
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 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.

eRAN
Enhancement
eRAN8.1
Downlink 4x2 MIMO in TM9 enables some inventory UEs to work in a 4-port CRS
network, where the eNodeB uses four antenna ports for cell-specific reference signals
(CRSs). It is a trail function in eRAN8.1.
Dependency
eNodeB
DL 4x2 MIMO requires the eNodeB to provide 4 TX channels and 4 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.
Other features
LOFD-001001 DL 2x2 MIMO
2.3.2 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).

eRAN
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.
2.3.3 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

eRAN
Dependency
eNodeB
UL 2x4 MU-MIMO requires the eNodeB to provide 4 RX channels and 4 antennas per
sector.
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.4.1 LOFD-001060 DL 4X4 MIMO
Availability
This feature is
not applicable to Micro.
not applicable to Lampsite.
Summary
This feature requires both eNodeBs and UEs to be configured with four antenna ports for the
downlink. To increase downlink throughput and improve coverage performance, this feature
adaptively selects spatial diversity or spatial multiplexing for each UE.
Benefits
For UEs of category 5, 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 of category 5 to use four antenna ports for reception, and therefore
brings receive diversity gains for these UEs, 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 MIMO modes or adaptive open-loop transmission mode can be configured. In adaptive
open-loop transmission mode, this feature adaptively selects transmit diversity or large-delay
cyclic delay diversity (CDD) based on UEs' channel conditions and rank information.

eRAN
Enhancement
eRAN8.1
Downlink 4x4 MIMO in TM9 is introduced. This function enables some Release 8 or 9
UEs to work in a 4-port CRS network, where the eNodeB uses four antenna ports for
cell-specific reference signals (CRSs). It is a trail function in eRAN8.1.
Dependency
eNodeB
This feature requires eNodeBs to provide four transmit channels.
UE
This feature requires UEs to support DL 4x4 MIMO.
Other Features
This feature requires LOFD-001003 DL 4x2 MIMO.
2.5 Interference Handling

2.5.1 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.

eRAN
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.5.2 LOFD-001014 Dynamic Inter-Cell Interference Coordination

2.5.2.1 LOFD-00101401 Downlink Dynamic Inter-Cell Interference
Coordination
Availability
This feature is
Summary
The DL dynamic ICIC feature dynamically adjusts the system frequency band for CEU
according to DL ICIC message.
Benefits
The DL ICIC feature can reduce the DL inter-cell interference and improve the CEU's
throughput. It is particularly effective when the loading in neighboring cells is unbalanced.
Description
Huawei DL ICIC solution uses employ power control and CEU scheduling to adjust the
resource allocation for the CEUs in frequency domain to reduce the DL inter-cell interference.
By keeping the non-overlapping downlink frequency bands for CEUs in neighboring cells, the
DL inter-cell interference can be controlled under certain level. Therefore, the CEU's
Signal-to-Noise Ratio (SINR) and throughput can be improved.
Downlink Dynamic Inter-Cell Interference Coordination is an enhancement compared to the
Downlink Static Inter-Cell Interference Coordination feature. It will dynamically adjust the
frequency bandwidth according to the cell load.
The eNodeB adjusts the edge band of the serving cell and informs the scheduler about it. The
adjustment is based on the following information:
Band division schemes determined during network planning
DL ICIC messages from neighboring cell

eRAN
Target neighboring cells for ICIC: These cells are selected based on neighboring cell
information and inter-cell interference. The neighboring cell list is managed based on the
DL ICIC messages from neighboring cells and the RSRP measurement reports from
UEs.
Load determination results
The eNodeB checks the cell load.
The scenario that benefits the most from DL ICIC is when the loading among the neighboring
cells is unbalanced. The lightly-loaded cell can schedule the CEUs at the CEU frequency band
with less bandwidth to allow the heavily-loaded cell to expand its CEU frequency band.
Enhancement
None
Dependency
Transport network
This feature requires X2 interface.
Other features
LBFD-002025 Basic Scheduling or LOFD-001015 Enhanced Scheduling.
2.5.2.2 LOFD-00101402 Uplink Dynamic Inter-Cell Interference

Coordination
Availability
This feature is
Summary
The uplink dynamic ICIC feature dynamically adjusts the system frequency band for the CEU
according to the cell load.
Benefits
UL ICIC can reduce inter-cell interference and improve the throughput of edge users, as well
as the cell coverage.
Description
The UL ICIC is a technique to combat the inter-cell interference for a LTE system by
coordinating transmitting power control and resource allocation in frequency domain among
neighboring cells. It can improve the throughput of CEUs and reduce impact of interference
on system performance. Different from static ICIC, the frequency bands of cells can be
adjusted dynamically for cell edge users based on the cell load information exchanged via X2
Interface when UL dynamic ICIC is enabled. For the neighboring cells, the coordination is

eRAN
achieved at the frequency domain, where the CEUs in neighboring cells use non-overlapping
CEU frequency bands.
The uplink dynamic inter-cell coordination is achieved by exchanging High Interference
Indication (HII) message through X2 interface (for dynamic Inter-eNodeB UL ICIC) or
internally (for dynamic Intra-eNodeB UL ICIC). HII is primarily used for frequency resource
allocation to avoid interference. It is also used for dynamically adjustment of the frequency
band used for CEUs.
Enhancement
In eRAN2.0
UL ICIC algorithm changes the division of basic cell edge frequency based on eNodeB
to the division of basic cell edge frequency base on cell. It also changes the coordination
ways that it is coordinate between two cells in the old version to coordinate among all
the necessary neighbor cells.
Dependency
Transport network
This feature requires X2 interface.
Other features
2.5.3 LOFD-060201 Adaptive Inter-Cell Interference Coordination

Availability
This feature is
Summary
The Adaptive Inter-Cell Interference Coordination (Adaptive ICIC) feature is a combination
of centralized eCoordinator management and distributed FDD eNodeB control. This feature
automatically adjusts the assignment mode in the band division scheme based on the inter-cell
interference data and edge load data that are automatically collected and processed. This
feature implements soft frequency reuse and effective inter-cell interference control.
In intra-frequency networking, this feature can adaptively adjust algorithms based on load
changes, which reduces inter-cell interference and improves cell edge user throughput.
The adaptive function is automatically disabled or enabled based on the network load and
interference to determine whether to perform inter-cell interference coordination.
Benefits
This feature reduces inter-cell interference and improves cell edge user throughput in
intra-frequency networking.

eRAN
Automatic inter-cell interference coordination simplifies ICIC configuration for telecom

operators to reduce operation and maintenance (O&M) costs.
Description
Users can create ICIC optimization tasks on the eCoordinator to perform FDD LTE adaptive
ICIC optimization.
This feature provides the following functions:
Management of ICIC optimization tasks
Users can add, delete, modify, or view ICIC optimization tasks. When adding an
optimization task, users need to select an optimization range for cells and set
optimization parameters and strategies. Then, users can modify parameters, strategies,
and the optimization range for the optimization task.
Users can start an ICIC optimization task based on the preset optimization range,
parameters, and strategies. After users stop an ICIC optimization task, the ICIC
optimization for the cells within the optimization range is also stopped.
A cell can have only one optimization task. The optimization ranges for different
optimization tasks cannot overlap.
The eCoordinator can automatically perform slow self-optimization and can determine
the band division scheme based on the periodically collected load data.
After Adaptive ICIC is enabled, the band division scheme is automatically configured.
Users are not allowed to manually configure the mode.
Management of ICIC optimization suggestions
Once an optimization task has been performed, the eCoordinator provides optimization
suggestions consisting of a band division scheme that complies with the optimization
range.
Enhancement
None
Dependency
eCO
eCO6910should be deployed.
Other features
Others
Cannot work together with LBFD-002022 Static ICIC or LOFD-001014 Dynamic ICIC.
2.5.4 LOFD-001067 800M Self-interference Cancellation

Availability
This feature is

eRAN
Summary
This feature enables eNodeB to eliminate 800M (band 20) self-interference of UE by flexible
schedule for the 800M cells.
Benefits
By eliminating the UE self-interference, this feature improves UE DL throughput in the 800M
cells, if using more than 10MHz bandwidth.
Description
For LTE 800M (band 20) cells, the duplex gap is only 11MHz. When UE transmits and
receives data at the same time, DL may be interfered by UL if UE's duplex filter isolation and
parameters (transmitted power and RB position etc.) are not good enough. Then, DL
REFSENS (reference sensitivity power level) will be decreased due to UL self-interference.
In order to eliminate 800M self-interference from UE itself, number of RBs (Radio Block)
used for uplink transmission is reduced when the interference cannot be avoided by
scheduling.
Enhancement
None
Dependency
eNodeB
This feature is only applicable to 800MHz (Band 20) cell.
2.5.5 LOFD-001093 PUCCH Flexible Configuration

Availability
This feature is
Summary
With this feature, the physical uplink control channel (PUCCH) can occupy resource blocks
(RBs) that were originally available to the physical uplink shared channel (PUSCH). Likewise,
the PUSCH can occupy RBs that were originally available to the PUCCH.
Benefits
This feature protects the PUCCH from interference in the edge band and therefore improves
PUCCH coverage and increases system capacity.

eRAN
Description
Normally PUCCH is configured at the edge band. When there is constant interference on the
edge band of a cell, the PUCCH Flexible Configuration feature can be used to move the
PUCCH closer to the center of the frequency band of the cell. This improves PUCCH
coverage and system capacity. However, the flexible configuration of the PUCCH causes
uplink bandwidth fragments, which decreases uplink scheduling efficiency and uplink peak
rate.
This feature is implemented on eNodeB and needs no additional requirement to UE.
Enhancement
None
Dependency
eNodeB
This feature is not applicable to LBBPc board.
Others
This feature cannot be used together with uplink inter-cell interference coordination
(ICIC) or uplink frequency hopping.
2.5.6 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.

eRAN
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.5.7 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

eRAN
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.5.8 LOFD-070208 Coordinated Scheduling based Power Control

(Cloud BB)
Availability
This feature is
not applicable to LampSite
Summary
Based on coordinated scheduling, Coordinated Scheduling based Power Control (CSPC)
dynamically configures downlink transmit power for each subframe in 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.
CSPC efficiently coordinates inter-cell interference and offers the following benefits:
Increases hotspot cell capacity in a load-unbalanced network.
Increases the throughput of cell edge UEs across the network.
Reduces handover failures and service drops caused by DL interference.
Description
CSPC coordinates TTI-specific transmit power configurations in individual cells. It reduces
inter-cell interference based on collaboration of scheduling with power control.
During CSPC, the centralized controller periodically collects UE scheduling information
about each E-UTRAN cell, calculates the optimal cell power configurations for the entire
network, and delivers the results to the E-UTRAN NodeBs (eNodeBs). The eNodeBs then
change their DL power to the received power configurations. Each cell obtains the transmit

eRAN
power configurations for the local cell and its neighboring cells on the same time-frequency
resources and promptly updates the modulation and coding schemes (MCSs) for cell edge
UEs. In addition, 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 spectral efficiency of the UE.
The figure shows an example of time-domain power coordination. In this example, 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) within each TTI. In the figure, a blue rectangle denotes an
RE with full transmit power, a yellow rectangle denotes an RE with increased transmit power,
and a gray rectangle denotes an RE with decreased transmit power.
Enhancement
eRAN8.1
CSPC in HetNet scenarios is now supported in the centralized Cloud BB architecture. In
this architecture, remote radio units (RRUs) are installed at sites, and BBUs are located
together and interconnected through a USU. The RRUs are connected to the BBUs
through optical CPRI interfaces.
Dependency
eNodeB
This feature is dependent on the Cloud BB architecture. This feature requires a UBBPd6
to be deployed in a BBU under each USU.
A UMPT must be configured as the main control board for each BBU.
A UBBPd6 board must be installed in one of the BBUs interconnected through two
levels of USUs. The board must be used only to carry the centralized controller. The
baseband processing units in each BBU must be LBBPd or UBBPd boards.

eRAN
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.
Other features
This feature must be used with the following eRAN features:
LOFD-001015 Enhanced Scheduling
LBFD-00300503 Synchronization with GPS or LOFD-00301302 IEEE1588 V2
Clock Synchronization
This feature does not work with the following eRAN features:
LBFD-002025 Basic Scheduling
LBFD-002016 Dynamic Downlink Power Allocation
LBFD-00202201 Downlink Static Inter-Cell Interference Coordination
LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination
LOFD-060201 Adaptive Inter-Cell Interference Coordination
LOFD-001007 High Speed Mobility
LOFD-001008 Ultra High Speed Mobility
LOFD-001009 Extended Cell Access Radius
LOFD-070205 Adaptive SFN/SDMA
Others
This feature requires time synchronization with an accuracy of 1.5 s.
2.5.9 LOFD-081206 Intra-eNodeB Coordinated Uplink AMC

Availability
This feature is
Summary
This feature is an enhancement to the AMC feature.
This feature uses coordinated interference prediction to better trace interference changes,
helping accurately predict the SINR to select an appropriate MCS. This feature increases
system throughput.
Benefits
This feature improves user experience when the heavily-loaded cells are experiencing
severe interference.
This feature increases throughput of heavily-loaded cells and UEs at the cell edge.
Description
This feature predicts interference at time of data transmission, thereby accurately predicting
the SINR to select an appropriate MCS. This is achieved by:

eRAN
Using resource allocation information exchanged by multiple cells in a coordinated

AMC set
Considering the interference and channel measurements of UEs in neighboring cells
This feature is applicable to intra-eNodeB multi-sector scenarios and allows each coordinated
AMC set to support up to three intra-frequency cells.
Enhancement
None
Dependency
eNodeB
This feature is applicable only to 2R cells.
This feature is applicable only to the UBBP board.
Other features
This feature depends on the following features:
LBFD-001006 AMC
LBFD-002025 Basic Scheduling or LOFD-001015 Enhanced Scheduling
This feature and the following features are mutually exclusive:
LOFD-003029 SFN
LOFD-001005 UL 4-Antenna Receive Diversity
2.6 UL CoMP
2.6.1 LOFD-001066 Intra-eNodeB UL CoMP
Availability
This feature is
Summary
UL CoMP is the abbreviation of Uplink Coordinated Multi-Point.
This feature provides joint receiving and interference attenuating function for neighboring
cells within the same eNodeB.
Unless otherwise stated, "site" mentioned in this section refers to a physical site.

eRAN
Benefits
This feature provides better UL throughput for cell edge users between 2 cells of one eNodeB.
This feature increases the uplink (UL) throughput of intra-site cell edge users (CEUs) and
some cell center users (CCUs).
Description
CoMP is applicable to following two scenarios:
In first scenario, which is called joint receiving scenario, this feature uses two adjacent cells,
to receive a single UE's uplink physical channels. The UE is called as CoMP UE which is in
the range of cell edge area of the serving cell and near to the CoMP co-operating cell at the
same time.
In second scenario, which is called interference attenuating scenario, a CoMP UE in the
serving cell will provide the signals to its CoMP co-operating cell, which can be used by the
co-operating cell in order to attenuate the interference on the UEs using the same PRBs in the
co-operating cell, to enhance the IRC performance.
This feature provides intra-site UL CoMP (joint reception), as illustrated in the following
figure.
The application scenarios are as follows:

Scenario 1: To achieve signal combining gains, this feature enables two neighboring cells to
receive a single UE's PUSCH. The UE is called a type-1 CoMP UE for simplicity and is on
the edge of the serving cell and near the coordinating cell.
Scenario 2: To achieve interference mitigation gains, this feature selects a UE that occupies
the same PRBs as a type-1 CoMP UE. The selected UE is called a type-2 CoMP UE for
simplicity. This feature uses signals received from the type-1 CoMP UE to mitigate the
interference with the type-2 CoMP UE and to enhance the IRC performance.
Enhancement
In eRAN6.0
On an LBBPd2,UBBPd4 board, a maximum of three cells can be established, and the
intra-eNodeB UL CoMP feature can be applied between cells that each have four receive
antennas.

eRAN
On an LBBPd3, UBBPd5, UBBPd6 board, a maximum of six cells (S1/1/1/1/1/1) can be

established, and the intra-eNodeB UL CoMP feature can be applied between cells that
each have two receive antennas.
In eRAN7.0
On an LBBPd3, UBBPd5, UBBPd6, a maximum of six cells on one frequency
(S1/1/1/1/1/1) can be established, and this feature can be applied between 2R cells.
eRAN8.1
eRAN8.1 and later versions support 3-cell UL CoMP.
Three-cell CoMP means that a UE is simultaneously served by receive antennas in
three cells. In 2R cells, a total of six antennas jointly receive uplink PUSCH signals
of the cell. Using Joint Interference Rejection Combining (JIRC), 3-cell UL CoMP
provides a higher performance than single-cell UL CoMP and 2-cell UL CoMP.
As shown in the following figure, the left part illustrates the 2-cell UL CoMP and the
right part illustrates the 3-cell UL CoMP.
This feature is applicable to 1R+1R cells or 1R+2R cells.

This feature applies to a HetNet that contains macro cells served by macro eNodeBs
and micro cells served by low power nodes (LPNs).
This feature supports intra-BBP UL CoMP in macro-micro scenarios.
Signals from a UE in macro cell are received by both macro and LPN(Low Power
Node). The two types of cells collaborate to improve this UE's performance, as
shown in the following figure. In macro-micro scenarios, this feature selects
coordinating cells based on sounding reference signal (SRS) and UL reference signal
received power (RSRP).

eRAN
This feature supports intra-BBP UL CoMP in micro-micro scenarios, the principle is

the same as that in macro-macro scenarios.
Dependency
eNodeB
None
UE
None
eCO
None
Transport Network
None
CN
None
OSS
None
Other features
This feature depends on LOFD-001012 UL Interference Rejection Combining.
Others
None
2.6.2 LOFD-070222 Intra-eNodeB UL CoMP Phase II

Availability
This feature is
Summary
If this feature and LOFD-001066 Intra-eNodeB UL CoMP are enabled together, they can
provide intra- or inter-site UL CoMP within a baseband unit (BBU).
Unless otherwise stated, "site" mentioned in this section refers to a physical site.
Benefits
This feature increases the UL throughput of intra- or inter-site CEUs and some CCUs and
therefore improves user experience.
Description
LOFD-070222 Intra-eNodeB UL CoMP Phase II uses antennas of "cells under different
baseband processing units (BBPs)" to jointly receive a single UE's signals. The serving cell

eRAN
and coordinating cell belong to the same BBU, and therefore information exchange is
required between the BBPs in the BBU.
This feature is applicable to the following scenarios:
Inter-BBU inter-BBP inter-site UL CoMP
See the following figure.
Inter-BBU inter-BBP intra-site UL CoMP

To implement inter-BBU inter-board intra-site UL CoMP, the RRUs serving different cells
within a physical site must be connected to BBPs in a BBU. This networking is seldom
deployed on live networks and its implementation is not elaborated in this section.
Enhancement
eRAN8.1
eRAN8.1 and later versions support 3-cell UL CoMP.
Three-cell CoMP means that a UE is simultaneously served by receive antennas in
three cells. In 2R cells, a total of six antennas jointly receive uplink PUSCH signals
of the cell. Using Joint Interference Rejection Combining (JIRC), 3-cell UL CoMP
provides a higher performance than single-cell UL CoMP and 2-cell UL CoMP.
This feature applies to cells with only one receiver antenna. In addition, this feature
supports a CoMP set that contains cells with one receive antenna and cells with two
receive antennas.
This feature applies to a HetNet that contains macro cells served by macro eNodeBs
and micro cells served by low power nodes (LPNs).
This feature supports inter-BBP UL CoMP in macro-micro scenarios.
Signals from a UE in macro cell are received by both macro and LPN(Low Power
Node). The two types of cells collaborate to improve this UE's performance, as
shown in the following figure. In macro-micro scenarios, this feature selects
coordinating cells based on sounding reference signal (SRS) and UL reference signal
received power (RSRP).

eRAN

This feature supports inter-BBP UL CoMP in micro-micro scenarios, the principle is
Dependency
eNodeB
BBU
If a connection set belongs to a BBU3900, one LBBPd or UBBPd must be installed
in slot 2 or 3.
BBP
The LBBPc, LBBPd1, and Blade BBU do not support this feature.
Cell configuration
The receive modes of cells can be 1R, 2R, 4R, or a combination of 1R and 2R.
eCO
None
UE
None
Transport network
None
CN
None
OSS
None
Other features
LOFD-001012 UL Interference Rejection Combining
LOFD-001066 Intra-eNodeB UL CoMP
Others
None
2.6.3 LOFD-070223 UL CoMP based on Coordinated BBU

Availability
This feature is

eRAN

Summary
In multi-BBU interconnection scenarios, this feature can work with LOFD-001066
Intra-eNodeB UL CoMP and LOFD-070222 Intra-eNodeB UL CoMP Phase II to provide
inter-BBU intra-site UL CoMP or inter-BBU inter-site UL CoMP. BBU stands for baseband
unit, and UL CoMP stands for Uplink Coordinated Multiple Points Reception.
Benefits
This feature increases the percentage of UL CoMP UEs, increases the UL throughput of intra-
or inter-site cell edge users (CEUs) and some cell center users (CCUs), and improves user
experience.
Description
This feature uses the antennas of multiple cells that belong to different BBUs to receive
signals from a UE. As the serving cell and coordinating cell belong to different BBUs, this
feature employs universal switching units (USUs) to enable information exchange between
BBUs.
This feature is applicable to the following scenarios:
Inter-BBU UL CoMP
Figure 2-1 illustrates the implementation of inter-BBU UL CoMP.

eRAN
Figure 2-1 Inter-BBU UL CoMP
Inter-BBU UL CoMP in macro-micro scenarios.

Signals from a UE in macro cell are received by both macro and LPN(Low Power Node).
The two types of cells collaborate to improve this UE's performance, as shown in the
following figure. In macro-micro scenarios, this feature selects coordinating cells based
on sounding reference signal (SRS) and UL reference signal received power (RSRP).
Inter-BBU UL CoMP in micro-micro scenarios.
Enhancement
eRAN8.1
Supports 3-cell UL CoMP
Supports two levels of USUs

eRAN
If both macro and micro cells collaborate to perform inter-BBU UL CoMP, this
feature selects coordinating cells based on sounding reference signal (SRS) and UL
reference signal received power (RSRP).
This feature supports inter-BBU UL CoMP in micro-micro scenarios, the principle is
Dependency
eNodeB
BBU
This feature is dependent on the Cloud BB architecture. Don't support LBBPc and
LMPT.
If the cells 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.
Only 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
form a connection set.
BBP
Cell configuration
The receive modes of cells can be 1R, 2R, 4R, or a combination of 1R and 2R.
eCO
None
UE
None
Transport network
Multi-BBU interconnection
CN
None
OSS
None
Other features
LOFD-070222 Intra-eNodeB UL CoMP Phase II
Others
None
2.6.4 LOFD-081219 UL CoMP Based on Relaxed Backhaul

Availability
This feature is

eRAN

Summary
LOFD-001066 Intra-eNodeB UL CoMP and LOFD-070222 Intra-eNodeB UL CoMP Phase II
together can provide only inter-site UL CoMP in centralized cloud BB scenarios.
This feature together with LOFD-001066 Intra-eNodeB UL CoMP and LOFD-070222
Intra-eNodeB UL CoMP Phase II can provide inter-site UL CoMP in relaxed backhaul
scenarios.
In relaxed backhaul scenarios, BBUs are located in different places without dedicated transmission links
between them, and inter-site coordination data are exchanged through the radio access network.
Benefits
This feature enables inter-site CoMP to be implemented in relaxed backhaul scenarios; in
earlier versions, inter-site CoMP can be implemented only in cloud BB scenarios. Without
reconstruction of an existing transport network, this feature increases the uplink throughput of
UEs at the cell edges between BBUs and improves the experience of cell edge users (CEUs).
Description
When transmission conditions are not satisfied because of transmission delay and
transmission bandwidth, this feature uses the antennas of cells under different BBUs to jointly
receive signals from a UE. The serving cell and coordinating cell are under different BBUs,
and there is a loose requirement on inter-BBU transmission. This is why this feature is called
UL CoMP Based on Relaxed Backhaul.
The following figure shows an example of UL CoMP based on relaxed backhaul.
Figure 2-2 UL CoMP based on relaxed backhaul.

eRAN
The following figure illustrates the differences between relaxed backhaul, centralized cloud
BB, and distributed cloud BB.
Figure 2-3 Differences between relaxed backhaul, centralized cloud BB, and distributed cloud
BB.
Cloud BB: Two or more BBUs are connected to a universal switching unit (USU) through
interconnection signal cables to implement inter-BBU communication.
Centralized cloud BB: BBUs and USUs are located in the same place. The distance between a BBU
and a USU is generally shorter than 100 m.
Distributed cloud BB: BBUs and USUs are located in different places. The distance between a BBU
and a USU and the distance between a level-1 USU and a level-2 USU are generally shorter than 10
km.
This feature applies to the following scenarios:

Inter-BBU macro-macro UL CoMP:

eRAN
Figure 2-4 Macro-macro UL CoMP
Enhancement
None
Dependency
eNodeB
BBP
Cell configuration
The receive modes of cells can only be 2R.
eCO
None
UE
None
Transport network
Relaxed backhaul
CN
None
OSS
None
Other features

eRAN

LOFD-001048 TTI Bundling
Others
None
2.7 QoS
2.7.1 LOFD-001015 Enhanced Scheduling
2.7.1.1 LOFD-00101501 CQI Adjustment
Availability
This feature is
Summary
This function reinforces the traditional AMC feature by introducing downlink Channel
Quality Indicator (CQI) adjustment.
Benefits
This feature brings the following benefits:
Effectively compensates for the inaccurate CQI measurement and makes the MCS
selection more accurate by using a closed-loop mechanism.
Improves the system capacity by selecting more accurate MCS.
Allows an adaptive CQI measurement for different scenarios and therefore improves the
system capacity.
Description
The CQI adjustment scheme enhances the conventional AMC scheme by introducing
downlink CQI adjustment. It could provide additional performance gains.
Under the conventional AMC scheme, the eNodeB chooses a Modulation and Coding Scheme
(MCS) for a UE based on the reported CQI. As a result, MCS will mainly change according to
the reported CQI. Since the UE measurement error and channel fading could make the
reported CQI somewhat inaccurate, the MCS selection based on the inaccurate CQI could
cause the DL transmission fails to reach the Block Error Rate (BLER) target. The
conventional AMC scheme does not have a closed-loop feedback mechanism to guarantee
that the actual BLER reaches the BLER target.

eRAN
The CQI adjustment scheme introduces a closed-loop mechanism to compensate for the CQI
measurement errors. When an eNodeB selects the MCS for the DL transmission, besides the
CQI and transmits power, the eNodeB also considers the difference between the target BLER
and the actually measured BLER. Note that the actually measured BLER is calculated on the
basis of the closed-loop ACK/NACK that the eNodeB received from the DL transmission. In
addition, the closed-loop solution used by the CQI adjustment scheme allows the eNodeB to
instruct a UE to change the BLER target for CQI reporting, which could maximize the system
throughput.
A common target BLER is optimized for all common scenarios, but in some sceanrios cell
throughput can be increased by increase initial target BLER, especially for cell edge users or
users only transmit small packets. A switch allows operator to adjust the initial target BLER
for cells of such scenarios.
Enhancement
In eRAN6.0
This feature is enhanced to allow adjust initial target BLER of a cell.
Dependency
None
2.7.1.2 LOFD-00101502 Dynamic Scheduling
Availability
This feature is
Summary
The dynamic scheduling feature provides the function that guarantees the user QoS and
achieves efficient resource utilization. The fairness between different UEs is also considered
in the function. The dynamic scheduling algorithm mainly focuses on the GBR and non-GBR
services.
Benefits
The scheduling feature is the core function to provide QoS in a LTE system. Huawei
scheduling solution could provide the following benefits:
Guarantees the QoS for GBR, and non-GBR services.
Achieves an optimal tradeoff among throughput, fairness, and QoS.
Description
The scheduling function facilitates to the achievement of efficient resource utilization on a
shared channel. In a LTE system, the scheduler allocates resources to the UEs every 1 ms or
every one TTI. The scheduling algorithm needs to meet the QoS requirements for different

eRAN
services and to achieve a good tradeoff between priority differentiation among different
services and the fairness among users.
The QoS specification is based on the nine QoS QCI defined in LTE standards. The nine
different QCI classes can be divided into GBR and Non-GBR service. The scheduling
solution is required to guarantee the bit rate requirement for GBR services, and enforce the
AMBR for Non-GBR services. Minimum GBR is set for Non-GBR services to avoid
starvation.
The uplink scheduler controls the service rates by using the token bucket algorithm for GBR
and Non-GBR services. Proportional Fair (PF) algorithm is the basic strategy to ensure
scheduling priorities (based on QCI) among different services. Higher priority is assigned to
IMS signaling and GBR services. Semi-persistent scheduling is employed for VoIP service
to ensure the voice quality. When the congestion indicator from load control algorithm is
received, the scheduler might reduce the guaranteed data rate for GBR service. The scheduler
might also consider the input from UL ICIC to reduce interference.
The uplink scheduler will divide the Logical Channel Groups (LCG) according to Operator
configuration. VOIP service is assigned with signaling in the same LCG and non-GBR
services belong to two LCG. Such configuration can guarantee the high priority non-GBR
services are scheduled in uplink. Prioritized bit rate (PBR) is not same as Minimum GBR and
PBR is configurable by operator.
The DL scheduler employs an enhanced scheduling strategy. During a given time window,
the scheduler is required to guarantee GBR and AMBR for all services. For GBR services, the
user channel quality and the service packet delay are taken into account when calculating the
priority. For Non-GBR services, in addition to the user channel quality, the scheduled service
throughput is also considered when calculating the priority. Note that semi-persistent
scheduling is used for VoIP service again and the bandwidth allocated for VoIP traffic is not
scheduled by the scheduler. The enhanced DL scheduler can achieve an optimal tradeoff
among throughput, fairness, and QoS guarantee. The same as the UL scheduler, the DL
scheduler also considers the input from DL ICIC to reduce the inter-cell interference.
As GBR services have higher priority than non-GBR services, when system is in congestion,
non-GBR service might be starving as it cannot be scheduled. The DL scheduler will reserve a
certain portion of resource for non-GBR services to prevent the issue.
Enhancement
In eRAN6.0
this feature is enhanced for DL non-GBR services to prevent non-GBR services from
starving at system congestion.
Dependency
None
2.7.2 LOFD-001026 TCP Proxy Enhancer (TPE)

Availability
This feature is

eRAN
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.

eRAN
The MTU Control function is introduced .
Dependency
None
2.7.3 LOFD-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 feature improves the end user service in different ways. With
AQM, where the buffer fill level is balanced to the UE data rate, the delay is significantly
reduced.
Description
In an interactive connection, the packet data to be transferred is typically characterized by
large variations, so the buffer is introduced to even out the variations. However, if the buffer
is filled up or an overflow situation takes place, it will result in loss of data packets.
Currently, TCP as the main transport layer protocol is used on Internet. Packet loss is regarded
as link congestion by TCP, and TCP will correspondingly reduce the data transmission rate.
TCP protocol is also sensitive to round trip delay 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 losses, it
may take a considerable time for the data rate to increase again, leading to poor radio link
utilization and causing long delays for the end user.
In addition, in case a user is performing parallel activities, e.g. FTP downloading and web
browsing, if the file downloading as a dominant stream would fill the buffers and thereby
cause a long delay for web browsing, before anything would happen when clicking on a link.
The functionality of AQM is provided as an optimized buffer handling method, in order to
interact with the TCP protocol in a favorable manner and reduce the buffering delay.
Operators can switch on/off the Active Queue Management function.
Enhancement
None

eRAN
Dependency
None
2.7.4 LOFD-001029 Enhanced Admission Control

2.7.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.

eRAN
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.7.5 LOFD-001054 Flexible User Steering

2.7.5.1 LOFD-00105401 Camp & Handover Based on SPID
Availability
This feature is
Summary
This feature is used in the scenarios under which the operator wants to control the mobility of
an UE to make it camp on, redirect or handover to a suitable cell. The priorities for the cell
selection is predefined and configured to eNodeB through SPID (Subscriber Profile ID for
RAT/Frequency Priority).
Benefits
Operators can make its subscribers to camp in, redirect or handover to a suitable RAT (a cell
of LTE/UMTS/GSM) or frequency (a cell of LTE) based on the service characteristics. For
example, for a data centric subscriber, a LTE cell will be the more suitable selection than an
UMTS cell or a GSM cell; for a voice centric subscriber, a GSM cell or an UMTS cell will be
the more suitable selection than a LTE cell; UEs can return to their home public land mobile
networks (HPLMNs) when they move to the boundaries between roaming areas and
non-roaming areas. This way, operators can customize different camping policies for UEs.

eRAN
Description
The SPID is an index referring to user information (for example, 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 strategies (for example, to define RRC_IDLE mode priorities and control
Inter-RAT/inter frequency redirection/ handover in RRC_CONNECTED mode).
In RRC_IDLE mode, UE can camp in a cell with its suitable RAT or frequency.
In RRC_CONNECTED mode, when load balance or overload control triggers an
inter-frequency or Inter-RAT handover or redirection, eNodeB will choose a suitable target
from the cells according to the priorities indexed by its SPID. In addition, when UE finish its
service, eNodeB can release it into a suitable cell according to its SPID priority. For UE
without SPID, when overload happens, the UE could also be redirect to a suitable cell
according to common priority and overload information.
This way, operator can configure and push subscribers into the suitable cell according its
subscription. For example: a dongle user usually stays in a LTE high frequency band for a
high service rate; a VoIP user is prior to stay in a LTE low frequency band to guarantee the
continuous coverage; UEs with a specific SPID can return to their HPLMNs from another
operator's network by using the PS handover, circuit switched fallback (CSFB), or single
radio voice call continuity (SRVCC) procedure.
Enhancement
eRAN3.0
When UE triggers an inter-frequency or inter-RAT handover, eNodeB can not only
choose a suitable target from the cells but also choose a HPLMN cell for national
roaming subscribers according to the priorities indexed by its SPID. For national
roaming subscribers, HPLMN cell will be more suitable to be selected than roaming cell
when entering HPLMN LTE or 3G coverage area through connected mode handover.
eRAN8.1
The "enhanced policy of SPID-specific handover back to the HPLMN" is introduced,
which enables UEs with a specific SPID to return to their HPLMNs by using 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 the HPLMN" is controlled by
the SPID-based Select PLMN Algo Switch parameter.
When this parameter is set to ON(On), the enhanced policy is enabled. After the
MME sends the SPID of a UE to the eNodeB:
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 HPLMN list corresponding to the UE's SPID (the list is
configured by the SpidHPlmnList MO). If it is, the eNodeB sends measurement
information about that frequency to the UE. If it is not, the eNodeB does not send
measurement information 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 information about that
frequency to the UE, regardless of whether the PLMN of the neighboring cell is on
the HPLMN list corresponding to the UE's SPID.
When this parameter is set to OFF(Off), the enhanced policy is disabled.

eRAN
Dependency
CN
It depends on SAE to support the SPID configuration.
Other features
The SPID-specific load-based handover policy in this feature requires LOFD-001032
Intra-LTE Load Balancing or LOFD-001044 Inter-RAT Load Sharing to UTRAN or
LOFD-001045 Inter-RAT Load Sharing to GERAN.
The SPID-specific handover back to the HPLMN policies in this feature require
LBFD-00201802 Coverage Based Inter-frequency or LOFD-001019 PS Inter-RAT
Mobility between E-UTRAN and UTRAN.
Others
GSM/UMTS network should support this functionality to avoid ping-pong handovers.
2.7.6 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.

eRAN
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.7.7 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.

eRAN
Enhancement
None
Dependency
None
2.7.8 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
Transport Network
None

eRAN
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.7.9 LOFD-081203 Video Service Rate Adaption

Availability
This feature is
Summary
This feature is applicable to initial video acceleration and service rate guarantee.
Benefits
Reduced video waiting time, which improves user experience in opening a video
Guaranteed video playing rate, which avoids video play suspension
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, service
guaranteed bit rate (SGBR), and segment acceleration policy. When the data rates of video
services are lower than the configured SGBR during video playback, the eNodeB raises the
scheduling priority of video services. If the data rates satisfy the SGBR requirements, the
eNodeB does not adjust the scheduling priority.
If the segment acceleration policy is configured, a higher priority and a higher SGBR rate are
adopted to guarantee video services during the initial phase for video services to increase the
initial video download rate. The initial phase for video services is configurable.
Enhancement
None
Dependency
eNodeB

eRAN
None
eCO
None
UE
None
Transport Network
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.7.10 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 the
extended QCIs.
Benefits
The scheduling priorities mapped to extended QCIs now equal or exceed those of guaranteed
bit rate (GBR) services. As a result, the data rates of services with the extended QCIs are
guaranteed even when cells are severely congested.
To use extended QCIs for services with high reliability requirements (for example, push to
talk [PTT] services), the Enhanced Extended QCI feature enables dedicated bearers for these
services to be assigned higher guaranteed scheduling priorities.
Description
Previously, extended QCIs indicated QoS policies for non-GBR services. They did not meet
high reliability requirements of operators. The Enhanced Extended QCI feature now raises the
QoS policies of extended QCIs to the level for GBR services. The scheduling priorities

eRAN
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 IP [VoIP] services according to 3GPP specifications.)
With this feature activated, dedicated bearers with the extended QCIs can use robust header
compression (ROHC) to reduce IP header overheads and increase their transmission
efficiency.
The Enhanced Extended QCI feature can be used only in collaboration with extended QCI
configurations in the EPC. Parameters related to dedicated GBR bearers, such as uplink and
downlink guaranteed bandwidths for GBR services, must be configured for extended QCIs in
the EPC. Otherwise, eNodeBs do not apply the QoS policies for GBR services to the extended
QCIs.
Enhancement
None
Dependency
eNodeB
None
eCO
None
UE
UEs must support dedicated bearer setup. To allow ROHC for PTT services, UEs must
support ROHC.
Transport Network
None
CN
The EPC must support extended QCIs and be able to identify service types so that
dedicated bearers can be set up for PTT services.
OSS
None
Other Features
To allow ROHC for services with extended QCIs, the feature LOFD-001017 RObust
Header Compression (ROHC) must be enabled.
Others
None
2.8 Signaling Storm & Terminal Battery Life Saving

2.8.1 LOFD-001105 Dynamic DRX
2.8.1.1 LOFD-00110501 Dynamic DRX
Availability
This feature is

eRAN

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

eRAN
Dependency
Other features
This feature requires LBFD-002017 DRX feature.
2.8.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

eRAN
Dependency
None
2.8.2 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:

eRAN
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.9 Inter-RAT Mobility to UTRAN

2.9.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.

eRAN
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.

eRAN
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,
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.
In eRAN6.0

eRAN
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.
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. 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.9.2 LOFD-001043 Service based inter-RAT handover to UTRAN

Availability
This feature is
Summary
It is to steer the VOIP service to UMTS 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

eRAN
eNodeB, eNodeB decides whether to setup service in the UMTS based on RAB QCI handover
strategy.
Enhancement
None
Dependency
Other features
LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN or
LOFD-001022 SRVCC to UTRAN.
2.9.3 LOFD-001072 Distance based Inter-RAT handover to

UTRAN
Availability
This feature is
Summary
Huawei LTE eNodeB supports distance based handover from E-UTRAN to UTRAN in
Mobility features.
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-RAT handover to UTRAN, even though the neighboring UTRAN
signal is much better than F1. In order to make the user always keep the best connection, a
distance based handover to UTRAN 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-RAT gap measurements of neighboring UTRAN will be
triggered to find an optimal handover candidate to improve user performance
Enhancement
None
Dependency
Other features

eRAN
This feature depends on LOFD-001019 PS Inter-RAT Mobility between E-UTRAN

and UTRAN.
2.9.4 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering

Availability
This feature is
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 and CS Fallback triggered E-UTRAN to UTRAN
Handover.
Benefits
This feature is an enhanced LTE mobility feature by providing a kind 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
When Coverage-based or CS Fallback triggers E-UTRAN to UTRAN handover, the eNodeB
initiates the inter-RAT blind handover process to the UE which is 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 doesn't support inter-RAT handover.
When Coverage-based triggers E-UTRAN to UTRAN handover, the eNodeB initiates the
inter-RAT measurement process to the UE which is 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-001033 CS Fallback to UTRAN

eRAN
2.9.5 LOFD-070216 Separate Mobility Policies to UTRAN for

Multi PLMN
Availability
This feature is
Summary
This feature enables the eNodeB to determine whether a neighboring UTRAN cell supports
the PS handover (PSHO) and RAN information management (RIM) in an LTE network. In
mobility-based handovers, eNodeBs determine handover policies depending on whether a
neighboring UTRAN cell or the evolved packet core (EPC) of the neighboring UTRAN cell
supports the PSHO and RIM.
Benefits
This feature reduces dependencies between features in RAN sharing scenarios, and enables
the configuration of the PSHO or Flash CS fallback (CSFB) for some operators or some
neighboring UTRAN cells.
Description
This feature applies to the scenario where neighboring UTRAN cells of an E-UTRAN cell or
devices in the SGSN supporting UTRAN cells of different operators may not support the
PSHO or RIM in an LTE network. eNodeBs determine handover policies based on
neighboring UTRAN cells and devices in the SGSN supporting a UTRAN cell.
Enhancement
None
Dependencies
Other features
LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN
LOFD-001052 Flash CS Fallback to UTRAN
2.9.6 LOFD-070203 RIM Based LTE Target Cell Selection

Availability
This feature is

eRAN
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
This feature provides the following 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
Transport Network
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

eRAN
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.10 Inter-RAT Mobility to GERAN

and 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

eRAN
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

eRAN
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
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.
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.
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. Note that the

eRAN
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.10.2 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

eRAN
2.10.3 LOFD-001073 Distance based Inter-RAT handover to

GERAN
Availability
This feature is
Summary
Huawei LTE eNodeB supports distance based handover from E-UTRAN to GERAN in
Mobility features.
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-RAT handover to GERAN, even though the neighboring GERAN
signal is much better than F1. In order to make the user always keep the best connection, a
distance based handover to GERAN 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-RAT gap measurements of neighboring GERAN will be
triggered to find an optimal handover candidate to improve user performance
Enhancement
None
Dependency
Other features
GERAN.

eRAN
2.11 Inter-RAT Mobility to CDMA2000

and CDMA2000
Availability
This feature is
Applicable to Macro from eRAN1.0
Applicable to Micro from eRAN3.0
Applicable to LampSite from eRAN6.0
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.

eRAN
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. Upon receiving a cell resource allocation response, the eNodeB
sends a handover command to the UE. The command contains the information about the
CDMA2000 HRPD cell resources. Upon receiving the handover command, the UE
hands over to the target CDMA2000 HRPD cell.
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
Transport Network
None
CN
Core networks should support this feature.
OSS
None
Other Features
None
Others
CDMA2000 HRPD should support this feature.

eRAN
2.11.2 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

eRAN
Figure 2-5 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.12 Refarming
2.12.1 LOFD-001051 Compact Bandwidth
Availability
This feature is
Summary
Huawei LTE supports the compact bandwidths by strict filter and RB punching. Compact
bandwidths for 5 MHz, 10 MHz, 15 MHz and 20 MHz are supported.

eRAN
Benefits
Compact bandwidth configuration helps operators make full use of certain non-standard
frequency bands and reduce the waste of frequency fragment.
Compact bandwidth need not to accord with standard bandwidth, producing higher
throughput and better user experience.
Compact bandwidth is completely transparent to UE and has no impact to R8/R9 UE.
Description
Huawei LTE supports the compact bandwidths listed in the following table:
Table 2-4 Compact bandwidths
Scenario Non-Standard Available RB Standard

No. Bandwidth(MHz) Number Bandwidth(MHz)
1 4.8-4.9 25 5
2 9.6-9.9 50 10
3 14.6-14.9 75 15
4 18.3-18.5 94 20
5 18.6-18.9 96 20
6 19-19.2 96 20
7 19.3-19.9 100 20
8 4.5-4.7 23 5
Enhancement
eRAN8.1
This feature supports scenario 8 for non-standard bandwidths listed in the preceding
table.
Dependency
eNodeB
This feature applies only to LTE networks working on the 450 MHz or 1800 MHz
frequency band.
For LTE networks working on the 1800 MHz frequency band:
When MRFUd, RRU3928, RRU3929, RRU3938, or RRU3939 is configured,
scenarios 1 to 7 for non-standard bandwidths listed in the preceding table are
supported.
For LTE networks working on the 450 MHz frequency band:
When RRU3668 is configured, scenarios 1 to 8 for non-standard bandwidths are all
supported.
eCO

eRAN
None
UE
None
Transport Network
None
CN
None
OSS
None
Other features
The feature LOFD-001014 Dynamic Inter-Cell Interference Coordination cannot be used
together with this feature when one of the following non-standard bandwidths is used on
the LTE network:
18.3 MHz to 18.5 MHz
8.9 MHz to 18.6 MHz
19 MHz to 19.2 MHz
4.5 MHz to 4.7 MHz
Others
None
2.13 High Speed Mobility

2.13.1 LOFD-001007 High Speed Mobility
Availability
This feature is
Summary
Huawei eNodeB supports the mobility up to 350 km/h at 1GHz~2.6GHz or 450km/h at less
than 1GHz with good performance.
Benefits
High speed access is one of the key differentiators for Huawei SingleRAN LTE solution to
provide high speed coverage. This feature brings the following benefits:
Allows Huawei LTE system to support high-speed UEs at different speed and frequency
combinations with good performance:
450km/h at 700MHz & 800MHz
350km/h at 1GHz~2.6GHz

eRAN
Provides a seamless user experience in a high-speed scenario.
Description
This feature allows a Huawei LTE system to operate in a high-speed scenario and deliver
good performance.
The higher the velocity that the UE experiences, the severer the effect of fast fading that the
system suffers. Therefore, it is more difficult to achieve the same performance in high-speed
scenario as in the normal speed.
Huawei supports the UE velocity at different frequencies as mentioned above, which has
almost covered all mobility scenarios in urban environment. The eNodeB should measure the
UE mobility speed and refine the channel estimation scheme accordingly. For example, the
adaptive open loop MIMO in high speed scenario is supported to achieve the better radio
performance.
Enhancement
In eRAN7.0
Up to 350km/h velocity at 1GHz to 2.6GHz frequency is supported.
The adaptive open loop MIMO in high speed scenario is supported
.Dependency
None
2.13.2 LOFD-001008 Ultra High Speed Mobility

Availability
This feature is
Summary
Huawei eNodeB can support the mobility up to 450 km/h at 1GHz to 2.6GHz frequency
with good performance.
Benefits
High speed access is one of the key differentiators for Huawei SingleRAN LTE solution to
provide high speed coverage. This feature brings the following benefits:
Allows Huawei LTE system to be deployed in any high speed scenario and supports UEs
at a speed of up to 450km/h at higher frequency.
Provides a seamless user experience in a high speed scenario.

eRAN
Description
In addition to the availability of speed in High Speed Mobility feature, this feature allows
Huawei LTE system to support UEs with almost any mobility profile at up to 450 km/h in
scenario with LoS path (e.g., Rician) and deliver good performance. For example, a UE on a
high-speed train could reach up to 450 km/h.
The higher the velocity that the UE experiences, the severer the effect of Doppler shift and
fast fading that the system suffers.The PRACH channel detecting algorithm in higher
frequency shift is supported to guarantee the access performance.
Enhancement
In eRAN2.0
450km/h is supported.
Dependency
None
2.13.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 users by the following handover enhancements:
eNodeBs hand over low-speed users out from cells enabled with high-speed mobility
features.
eNodeBs hand over high-speed users to cells enabled with high-speed mobility features,
preventing them from being handed over to common cells.
Benefits
User experience is improved in high-speed mobility scenarios.
Description
Generally, a dedicated network is deployed for high-speed mobility scenarios (such as
high-speed railways).
To prevent common users from occupying resources in this network, when this network
covers urban areas where common macro eNodeBs are deployed, the eNodeBs enabled with
this feature hand over common users to common cells served by the common macro eNodeBs.
In addition, the eNodeBs hand over high-speed users to cells enabled with the high-speed
mobility feature in the dedicated network, preventing them from being handed over to

eRAN
common cells. This ensures that high-speed users can obtain sufficient resources in the
dedicated network. As a result, the experience of high-speed users is improved and the value
of the dedicated network is maximized.
In this feature, high-speed mobility scenarios refer to high-speed and ultra-high-speed mobility
scenarios.
Enhancement
None
Dependency
None
2.14 Coverage Enhancement

2.14.1 LOFD-001009 Extended Cell Access Radius
Availability
This feature is
Summary
To improve wireless network coverage, 3GPP TS36.211 has defined four types of preamble
formats (0 - 3) for frame structure type 1. For format 0, it corresponds to small cell access
radius, for format 1, 2 and 3, they correspond to extended cell access radius.
Benefits
This feature is used in large cell scenario to extend the cell access radius.
Description
This feature provides operator with support of extended cell radius. According to the 3GPP
TS36.211, there are four types of preamble format (0-3) for PRACH are defined to support
different cell access radius, shown in Figure below.

eRAN
Figure 2-6 Preamble formats and cell access radius
For format 0, the supported cell access radius is about 15 km, it is used in small cell scenario,
and considered as basic cell radius. The extended cell radius consists of format 1, 2 and 3. For
format 3, the supported cell access radius is about 100 km, which is used in the large cell
scenario to enhance the system coverage.
Enhancement
None
Dependency
None
2.14.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.

eRAN
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.14.3 LOFD-081223 Extended Cell Access Radius Beyond 100km

Availability
This feature is
Not applicable to Micro.
Not applicable to Lampsite.
Summary
This feature supports the extended cell radius up to 160 km in open areas (for example, on the
sea) while keep certain network performance.
Benefits
With this feature, the coverage area can be extended to more than 100 km in open areas (that
is, on the sea).
Description
In scenarios where a UE is located 100 km away from the cell center and the UE does not
support a large timing adjustment, this technology allows the eNodeB delays the time for
receiving uplink signals from the UE, so that the eNodeB can correctly receive the uplink
signals from the UE. This feature does not require any modification of the UE and complies
with the current protocols.
To provide a coverage beyond 100 km, the eNodeB uses two RRUs to provide coverage in the
local area (0 to N km) and remote area (N to 100+N km) by adjusting the antenna height and
downtilt. Here, 0 N 60 km. The cell provides a normal coverage, and the uplink timing

eRAN
alignment timer does not need to be adjusted. The remote cell provides 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 covers the local area does not need to be installed.
Enhancement
None
Dependency
eNodeB
The baseband processing unit must be:
UBBPd3
UBBPd4
UBBPd5
UBBPd6
The TX and RX mode of the cell must be:
1T1R
1T2R
2T2R
2T4R
The RRU can not be:
RRU3201
RRU3203
RRU3220
RRU3222
RRU3808
RRU3908
LRFU
MRFU
eCoordinator
None
UE
None
Transport network
None
CN
None
OSS
None
Other features
This feature cannot work with the following features:
LOFD-070223 UL CoMP based on Coordinated BBU

eRAN

LOFD-081219 UL CoMP Based on Relaxed Backhaul
LOFD-001096 Advanced Receiver (PSIC)
LOFD-081206 Intra-eNodeB Coordinated Uplink AMC
LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB)
LOFD-003029 SFN
LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU
LOFD-081209 Inter-eNodeB adaptive SFN/SDMA Based on Coordinated BBU
LOFD-081221 Super Combined Cell
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 Carrier Aggregation for 2CC based on Coordinated BBU
LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
Others
None

eRAN
Optional Feature Description 3 Networking & Transmission & Security
3 Networking & Transmission & Security
3.1 Transmission & Synchronization

3.2 IPv6
3.3 Security
3.4 Reliability
3.5 RAN Sharing
3.6 Advance Micro
3.7 Site Architecture
3.1 Transmission & Synchronization

3.1.1 LOFD-003002 2G/3G and LTE Co-transmission
Availability
This feature is
Summary
2G/3G and LTE co-transmission provides the operators the possibility of LTE co-transmission
with legacy networks such as GSM, UMTS, or CDMA for better resources utilization and
OPEX reduction.
Benefits
In a co-site scenario:
Better utilization of transmission resources is achieved.
OPEX (rental fees of the transmission resources) is reduced.

eRAN
Description
The eNodeB supports co-transmission with other 2G/3G base stations.
During eNodeB site deployment, it is possible that an eNodeB shares a site with a base station
of different technologies such as GSM, UMTS, or CDMA. In this case, co-transmission
facilitates better utilization of transmission resources and reduces the OPEX (rental fees of the
transmission resources).
The following figure shows the 2G/3G and LTE co-transmission
Figure 3-1 2G/3G and LTE co-transmission
The implementation of the co-transmission function depends on four sub functions: multiple
ports, IP route, DHCP relay, and Weighted Round Robin (WRR) scheduling. They are
described as follows:
Multiple ports: eNodeB supports several Ethernet and E1/T1 interfaces.
IP route: The data of the cascaded base station is switched to IP network by the IP route
function in the eNodeB. IP routes can be configured by users.
DHCP relay: In general, a cascaded base station obtains the IP address by the DHCP
function. With the DHCP function, the DHCP client, that is the base station, and the
DHCP server are required to be located in the same broadcast domain. In the
co-transmission scenario, however, the cascaded base station is not located in the same
broadcast domain as the DHCP server. DHCP relay provides a means to transfer DHCP
messages between different broadcast domains.
WRR scheduling: It ensures fairness between the cascaded base station and the eNodeB
for the data transport. Data are scheduled on the basis of the weight computed
according to the traffic bandwidth. Each base station and eNodeB has a weight and then
has a chance to be scheduled.
Enhancement
None
Dependency
Others
2G/3G should support IP transmission.

eRAN
3.1.2 LOFD-003011 Enhanced Transmission QoS Management

3.1.2.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

eRAN
3.1.2.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

eRAN
3.1.2.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

eRAN
3.1.3 LOFD-003012 IP Performance Monitoring

3.1.3.1 LOFD-00301201 IP Performance Monitoring
Availability
This feature is
Summary
The IP Performance Monitoring enhances the performance management function by
providing an end to end network monitoring mechanism and KPIs(key performance indicator)
are acquired, such as information about traffic volume, packet loss rate, delay and jitter.
Benefits
End-to-end network performance monitoring is available.
System maintainability and testability are enhanced.
System performance is improved.
Description
IP Performance Monitoring (PM) is Huawei specific function. It can provide an end-to-end
network performance monitoring mechanism with period detecting packets. eNodeB
periodically sends detecting packets to peer device such as SGW, and the peer device returns
the response packets. eNodeB acquires the KPIs, such as traffic volume, packet loss rate,
delay, and jitter from these response packets.
With these KPIs, users can know the network quality and take actions, such as network
optimization and network expansion.
The IP PM feature facilitates fault identification too. If the LTE device including eNodeB,
SGW have the feature, it is easy to identify whether the fault is located in the transmission
network device or the LTE device. Furthermore, if every node on a network has the feature, it
is easy to locate the fault quickly.
Enhancement
None
Dependency
CN
The core network equipments should be from Huawei, and Huawei EPC will support this
feature since PS9.2.

eRAN
3.1.3.2 LOFD-00301202 Transport Dynamic Flow Control
Availability
This feature is
Summary
According to the network quality detected by IP PM (IP Performance Monitoring) mechanism,
Transmission Dynamic Flow Control can dynamically adjust flow control parameters.
Benefits
This feature dynamically adjusts flow control parameters according to the network quality,
which changes dynamically.
Description
In some scenarios, the quality of network changes frequently. In order to adopt these scenarios,
it is better to dynamically adjust QoS parameters, such as bandwidth. Transmission Dynamic
Flow Control provides a method to complete it according to the network quality detected by
IP PM(IP Performance Monitoring). With good network quality, it automatically increases
the bandwidth step by step, otherwise decreases the parameter.
IP PM provides the end-to-end network performance monitoring function to acquire
information of network quality such as traffic volume, packet loss rate, delay, and jitter.
Enhancement
None
Dependency
Other features
This feature is based on the LOFD-00301201 IP PM feature
3.1.4 LOFD-070219 IP Active Performance Measurement

Availability
This feature is

eRAN
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.

eRAN
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

eRAN
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
Transport Network
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.
3.1.5 LOFD-003013 Enhanced Synchronization

3.1.5.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.

eRAN
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
retriev Figure
2-17 shows the framework of the Synchronization with Ethernet.
Figure 3-2 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
Transport network
The peer equipments should support this function
CN
The core network equipments should support this function
3.1.5.2 LOFD-00301302 IEEE1588 V2 Clock Synchronization
Availability
This feature is

eRAN

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 3-3 illustrates the basic principles of IEEE 1588.
Figure 3-3 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.

eRAN
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 3-4 illustrates the synchronization principles of IEEE 1588.
Figure 3-4 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

eRAN
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
Transport Network
None
CN
The MME must support this feature.
OSS
None
Other Features
None
Others
None
3.1.5.3 LOFD-00301303 Clock over IP (Huawei proprietary)
Availability
This feature is

eRAN
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 3-5 Framework of Huawei proprietary protocol
Pay attention to the following information:

eRAN
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
3.1.6 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.

eRAN
Figure 3-6 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.
3.1.7 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

eRAN
synchronization between eNodeBs. Uu-based soft synchronization achieves phase

synchronization and time synchronization between eNodeBs at lower costs than GPS and
IEEE1588V2 clock synchronization.
The Uu based Soft Synchronization feature provides the time synchronization function for
eMBMS services.
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 any eNodeB is equipped with GPS or IEEE1588 V2, all
eNodeBs are equipped with NTP, and phase synchronization between eNodeBs is achieved,
these 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.
eCO
ECO6910 is required.
Others
Both the transport network and the eNodeB must support synchronous Ethernet.
3.1.8 LOFD-081220 Inter-BBU Clock Sharing

Availability
This feature is

eRAN
Summary
This feature implements inter-subrack sharing of the GPS reference clock (including the
RGPS reference clock). By using a universal switching unit (USU), this feature allows a
macro eNodeB to distribute the GPS reference clock (including the RGPS reference clock)
locked by one of its baseband unit (BBU) among other BBUs, including LampSite BBUs.
Benefits
This feature eliminates the need for deploying the GPS reference clock (including the RGPS
reference clock) on LampSite BBUs and improves BBU clock reliability of macro eNodeBs.
Description
With this feature, the USU distributes the clock of the BBU that has locked the GPS reference
clock (including the RGPS reference clock) among other BBUs, including LampSite BBUs.
By default, other BBUs synchronize their clock with GPS reference clocks (including the
RGPS reference clock) distributed by the USU. If the GPS reference clock (including the
RGPS reference clock) distributed by the USU is faulty and the BBUs have been configured
with the GPS reference clock (including the RGPS reference clock), the BBUs automatically
synchronize their clock with the configured GPS reference clock (including the RGPS
reference clock)
Two GPS reference clocks (including the RGPS reference clock) can be configured for two
separate BBUs. The two GPS reference clocks (including the RGPS reference clock) work in
active/standby mode. If the active GPS reference clock (including the RGPS reference clock)
clock becomes faulty, BBUs automatically synchronize their clock with the standby GPS
reference clock (including the RGPS reference clock).
Enhancement
None
Dependency
Others
This feature must be used in CloudBB scenarios.
3.2 IPv6
3.2.1 LOFD-003017 S1 and X2 over IPv6
Availability
This feature is

eRAN
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 3-7 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
Transport network
The peer equipments should support IPv6.
CN
The core network should support this feature.

eRAN
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
Transport network
Other features
This feature depends on LOFD-003013 Enhanced Synchronization.
Others
This feature needs time server support 1588v2 over IPv6.

eRAN
3.2.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.

eRAN
Enhancement
None
Dependency
Transport network
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.
3.3 Security
3.3.1 LOFD-001010 Security Mechanism
3.3.1.1 LOFD-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 procedure provides confidentiality protection for signaling data and user data in order to
keep them from illegal interception and modifying.
Description
LTE handles the ciphering protection for the RRC signaling and user data. The encryption
function includes both ciphering and deciphering and it is performed at PDCP layer. The
ciphering is activated by the initial security activation procedure after receiving the UE
context from the EPC. Upon connection establishment , the ciphering algorithm and key to be
used are generated by the RRC, which is common for all radio bearers, for example, the
configuration is used for the radio bearers carrying signaling data as well as for those carrying
user data.

eRAN
The ciphering algorithms can only be changed with handover. The ciphering keys change with
handover or RRC connection re-establishment. An intra-cell handover procedure may be used
to change the keys in RRC_CONNECTED mode.
From eRAN1.0, encryption algorithm AES is supported.
Enhancement
None
Dependency
UE
The UE should support the same encryption algorithm as the eNodeB.
3.3.1.2 LOFD-00101002 Encryption: SNOW 3G
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 procedure provides confidentiality protection for signaling data and user data in order to
keep them from illegal interception and modifying.
Description
LTE handles the ciphering protection for the RRC signaling and user data. The encryption
function includes both ciphering and deciphering and it is performed at PDCP layer. The
ciphering is activated by the initial security activation procedure after receiving the UE
context from the EPC. Upon connection establishment , the ciphering algorithm and key to be
used are generated by the RRC, which is common for all radio bearers, for example, the
configuration is used for the radio bearers carrying signaling data as well as for those carrying
user data.
The ciphering algorithms can only be changed with handover. The ciphering keys change with
handover or RRC connection re-establishment. An intra-cell handover procedure may be used
to change the keys in RRC_CONNECTED mode.
Huawei eRAN2.0 supports SNOW3G with 128 bits keys.
Enhancement
None

eRAN
Dependency
UE
The UE should support the same encryption algorithm as the eNodeB.
3.3.1.3 LOFD-00101003 Encryption: ZUC
Availability
This feature is
Summary
Encryption provides confidentiality protection for signaling and user data between the
eNodeB and the UE.
Benefits
The procedure provides confidentiality protection for signaling and user data to protect them
from illegal interception and modification.
Description
LTE handles ciphering protection for Radio Resource Control (RRC) signaling and user data.
The encryption function includes both ciphering and deciphering and is performed at the
Packet Data Convergence Protocol (PDCP) layer. Encryption is activated by the initial
security activation procedure after the UE context is received from the EPC. Upon connection
establishment , the encryption algorithm and the key to be used are generated by RRC and are
common for all radio bearers. For example, a configuration is used for radio bearers carrying
signaling as well as for those carrying user data.
The encryption algorithms can be changed only with handover. The cipher keys change with
handover or RRC connection reestablishment. An intra-cell handover procedure may be used
to change the keys for a UE in RRC_CONNECTED mode.
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
key-stream of 32-bit words (where each 32-bit word is called a key-word). This key-stream
can be used for ciphering/deciphering.
Huawei eRAN6.0 supports ZUC.
Enhancement
None
Dependency
eNodeB
This feature is not applicable to LBBPc card.

eRAN
UE
The UE must support the same encryption algorithm as the eNodeB.
3.3.2 LOFD-003009 IPsec

Availability
This feature is
Summary
IPsec is used to protect, authenticate, and encrypt data flow for necessary security between
two network entities at the IP layer.
Benefits
This feature provides the security mechanism, confidentiality, integrity, and authentication
between participating peers at the IP layer.
Description
The following figure shows the IPsec
Figure 3-8 IPsec
IP Security (IPsec) provides a framework of open standards dealing with data confidentiality,
integrity, and authentication between participating hosts. IPsec provides these security
services at the IP layer. It uses IKEV1 & IKEV2 (Internet Key Exchange) to handle
negotiation of 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 data flows between two eNodeBs, between eNodeB
and SGW/MME, or between security gateway and eNodeB.

eRAN
The key characteristics of IPsec are as follows:

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,AES-XCBC-MAC-96, SHA256 and
HMAC_MD5, where HMAC stands for Hash Message Authentication Code, SHA stands
for Secure Hash Algorithm, and MD5 stands for Message Digest 5
Enhancement
In eRAN2.0, PKI (Public Key infrastructure) could be used to provide authentication for
IPsec. This needs the support of feature LOFD-003010 Public Key Infrastructure (PKI).
In eRAN3.0,two new integrity protection methods AES-XCBC-MAC-96 and SHA256
could be use.
Dependency
Transport network
Security gateway is needed, and it should support IPsec.
Other features
If IPsec uses digital certificate authentication, this feature requires the LOFD-003010
Public Key Infrastructure(PKI) feature.
3.3.3 LOFD-003010 Public Key Infrastructure (PKI)

Availability
This feature is
Summary
eNodeB supports PKI (Public Key infrastructure). It is a framework to support certificate
authentication which is applied to IPsec Tunnel between eNodeB and security gateway, and
SSL channel between eNodeB and OMC.
Benefits
This feature provides digital certificate authentication between two network devices,
improving security in network domain.
Description
eNodeB supports PKI (Public Key infrastructure), which is a framework to manage digital
certificate. Digital certificate is used to provide authentication between two network elements,

eRAN
such as IPsec Tunnel between eNodeB and security gateway, or SSL channel between
eNodeB and OMC.
The digital certification management includes certificate create, store, distribute, revoke, CRL
(Certificate Revocation List) distribution and so on.
In general, a PKI system includes CA(Certificate Authority), CR(Certificate
Repository) ,CRL Server and users which need authentication. eNodeB and security
gateway are users of PKI system. eNodeB interacts with CA, CR and CRL Server with
assistance of U2000.
eNodeB supports pre-reserved certificate in factory and the certificate format is complied with
X.509 V3. After base station is running, it supports certificate replacing.
The following figure shows the scenario of eRAN certificate application.
Figure 3-9 eRAN certificate application scenario
Enhancement
In eRAN2.0
eNodeB can update digital certificates automatically. And eNodeB can update digital
certificates automatically through U2000 proxy.
In eRAN2.1
This feature is enhanced to support automatic certificate distribution using CMPv2. With
the introduction of CMPv2 between CA and eNodeB, the procedure of certificate
enrollment and update can be automated. In case of huge amount of base station
deployed over carrier's network, base station certificate issuing and updating will get
more efficiency when CMPv2 is introduced to establish direct tunnel from eNodeB to
CA.
The Certificate Management Protocol (CMP) is an Internet protocol used for X.509
digital certificate creation and management in a Public Key Infrastructure (PKI).
An eNodeB can utilize CMP to obtain certificates from the CA. This can be done
through an CMP "initial registration/certification", a "key pair update" or a "certificate
update" message sequence. Using a CMP "cross-certification request" message a CA can
get a certificate signed by another CA.

eRAN
Means of transportation for conveying CMP messages:Encapsulated in a HTTP/HTTPs

message.
Dependency
Transport network
The peer equipments should support this function
CN
The core network equipments should support this function.
3.3.4 LOFD-003014 Integrated Firewall

3.3.4.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.

eRAN
eNodeB support that IPsec encrypted and authenticate selected data flows with ACL
under IPv6.
Dependency
None
3.3.4.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

eRAN
None
UE
None
Transport Network
None
CN
None
OSS
None
Other Features
This feature requires LOFD-00301401 ACL.
Others
None
3.3.5 LOFD-003015 Access Control based on 802.1x

Availability
This feature is
Summary
eNodeB support authentication to the transport network using 802.1x (Port-Based Network
Access Control). Authentication is based on the device certificate.
Benefits
This feature provides digital certificate authentication between eNodeB and LAN-Switch,
improving security in network domain.
Description
802.1x (Port-Based Network Access Control) uses the physical access characteristics of IEEE
802 LAN infrastructures 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 the authentication and authorization process fails.
The authentication and authorization of 802.1x uses framework of EAP (Extensible
Authentication Protocol), and refer to eNodeB, LAN-Switch, and AAA-Server
(RADIUS-Server).

eRAN
Figure 3-10 eRAN 802.1x application scenario
Before the authentication and authorization process succeeds, only EAPoL (Extensible
Authentication Protocol over LAN) packet can across the LAN-Switch, and all the other
packets will be dropped by LAN-Switch.
Enhancement
None
Dependency
Transport network
The peer device needs to support the 802.1x functionality.
CN
The core network equipments needs to support the 802.1x functionality
Other features
This feature depends on LOFD-003010 Public Key Infrastructure (PKI).
3.3.6 LOFD-070211 IPSec Redundancy Among Multiple SeGWs

Availability
This feature is
Summary
This feature uses the dead peer detection (DPD) function to monitor the status of the IPSec
tunnels between the eNodeB and all the SeGWs. If the IPSec tunnel between the eNodeB and
the primary SeGW is faulty, the eNodeB attempts to establish a standby IPSec tunnel with the
secondary SeGW. This implements IPSec redundancy among multiple SeGWs.
Benefits
Quick service recovery

eRAN
Improved reliability of secure networks

Reduced economic losses for operators
Description
1. When an eNodeB detects that the IPSec tunnel between it and the active SeGW is faulty,
the eNodeB attempts to initiate an IKE negotiation with each standby SeGW,
sequentially, until the eNodeB establishes a temporary IPSec tunnel. Then, the eNodeB
switches its services to the temporary tunnel.
2. If the IPSec tunnel between the eNodeB and the active SeGW is restored, the eNodeB
switches the services back to the IPSec tunnel and removes the temporary tunnel.
This feature applies to intra- or inter-city secure networks.
Enhancement
None
Dependency
eNodeB
Only the Ethernet ports on the UMPT, LMPT, and UTRPc support this feature.
UE
None
Transport Network
None
CN
None
OSS
None
Other Features
This feature depends on the LOFD-003009 IPsec feature.
This feature cannot be used together with the LOFD-003019 IPsec Tunnel Backup
feature.
Others
Multiple SeGWs are deployed on a network, and routes from the eNodeB to these
SeGWs are all reachable.
This feature requires SeGWs to support generation of internal dynamic routes based
on IPSec security associations (SAs).
E8000E and SeMG9811 support the deployment of SeGW.
3.3.7 LOFD-070212 eNodeB Supporting PKI Redundancy

Availability
This feature is

eRAN

Summary
This feature supports deployment of one active and one standby PKI servers 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
Preventing certificate applications and updates as well as CRL acquisitions from being
affected by active server failures
Preventing link failures caused by certificate-related problems
Improving the reliability of PKI-based secure networks
Description
In PKI redundancy, you must deploy one active and one standby PKI servers 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 3-11 illustrates how this feature works.
Figure 3-11 eNodeB PKI redundancy example
Enhancement
None
Dependency
eNodeB

eRAN
The UMPT, LMPT, or UTRPc must be configured to support this feature.

UE
None
Transport Network
None
CN
None
OSS
None
Other Features
This feature depends on the LOFD-003010 Public Key Infrastructure (PKI) feature.
Others
One active and one standby PKI servers must be deployed on a network.
3.4 Reliability
3.4.1 LOFD-001018 S1-flex
Availability
This feature is
Summary
This feature is part of the MME Pool solution which needs the support from both the eNodeB
and the MME. It allows an eNodeB to be connected to multiple MMEs simultaneously.
Huawei eNodeB supports a maximum of 32 S1 interfaces. There is one MME on each S1
interface which can be also connected to several MMEs.
Benefits
This feature increases the flexibility of S1 interface and provides the following benefits:
Increases the overall usage of capacity of MME pool.
Improves the load sharing across MMEs in pool.
Avoids unnecessary signaling in the core network when the UE moves in the MME Pool
Area because the served MME of the UE will not change.
Description
A connection topol Figure 2-1:

eRAN
Figure 3-12 connection topology between MME Pool and eNodeBs
If an eNodeB connects to a MME Pool, it indicates that the eNodeB must be able to determine
which MME in the pool should receive the signaling sent from a UE:
If the UE gives the MME information in the RRC signal message, the eNodeB will select the
MME according with this information.
If the UE does not give the MME information or the registered MME is not connected to the
eNodeB, the eNodeB will select a MME as follow:
Topology-based MME Pool selection
The MME pool is selected based the network topology to reduces the possibility of switching
MME during mobility.
Load-based MME selection
The MME is selected based on its capacity and load. The capacity of the MME can be
informed to the eNodeB during the S1 setup by the MME. When an MME is overloaded, the
eNodeB will limit assigning new UEs to the MME according to the overload action
information MME sent to it when overload started.
Enhancement
In eRAN6.0
The priority-based MME selection method is added. When MMEs or the S1 interfaces to
MMEs are assigned different priorities, the MME with the highest priority is
preferentially selected. If multiple MMEs have the highest priority, the MME with the
lowest load among them is preferentially selected. An MME with a low priority is
selected only when all high-priority MMEs are faulty or overloaded.

eRAN
The cell-based MME information configuration is added. In the case of TDD and FDD
system sharing the same eNodeB but with separated MME group, UE will only access
the MMEs which have been configured to the cell.
Dependency
CN
MME must support MME Pool function simultaneously.
3.4.2 LOFD-003004 Ethernet OAM

3.4.2.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.

eRAN
Enhancement
None
Dependency
Transport network
The peer equipment must support IEEE802.3ah when IEEE802.3ah is used.
CN
3.4.2.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
Transport network

eRAN
The peer equipment must support IEEE802.1ag when IEEE802.1ag is used

CN
3.4.2.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.

eRAN
Enhancement
None
Dependency
Transport network
The peer equipment must also comply with ITU Y.1731.
CN
3.4.3 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
Transport network
The peer equipments should support this function.

eRAN
3.4.4 LOFD-003006 IP Route Backup

Model
LT1S00IPRB00
Availability
This feature is
Summary
IP backup solution provides reliability of IP route with an alternative IP route if the IP main
route happens to fail.
Benefits
This feature provides reliability at the IP layer.
Description
The IP route backup function provides reliability at the IP layer.
Users can configure two routes with the same destination IP address but different next-hop
addresses and priorities. Usually, the route of the higher priority is active. When this route
fails and the outage, for example, through network ping, the route of the lower priority will be
activated.
Enhancement
None
Dependency
Transport network
The peer device must also support the IP route backup function.
3.4.5 LOFD-003007 Bidirectional Forwarding Detection

Model
LT1S000BFD00
Availability
This feature is

eRAN

Summary
BFD is a kind of bidirectional-detecting mechanism, which can be used to detect the fault of
the IP route.
Benefits
BFD help the operator to detecting network fault.
BFD achieve reliability and high availability of Ethernet services, enables the service
provider to provide economical and efficient advanced Ethernet services.
Description
The BFD feature is a method for IP connectivity failure detection by periodically transmitting
BFD packets between two nodes. When no BFD packets are received during the detection
interval, failure is declared and related recover action will be triggered, such as IP route, to
avoid traffic drop. BFD can detecting the failure rapidly, so it could use for telecom service
above IP network.
The one-hop and multi-hop BFD is supported by eNodeB. Multi-hop means there is at least
one router on the IP path between the source node and destination node. Otherwise it is
one-hop.
The one-hop BFD is used for the gateway availability detection when router is used.
The multi-hop BFD is used for detecting the connectivity of two network elements, such as
eNodeB to eNodeB, eNodeB to SGW/MME and eNodeB to transport equipment. The
following figure shows the one-hop and multi-hop BFD application scenarios:
Figure 3-13 the one-hop and multi-hop BFD application scenarios
Enhancement
None

eRAN
Dependency
Transport network
The peer equipment must support BFD when BFD is used to detect the fault of the IP
route.
3.4.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.

eRAN
Figure 3-14 the Ethernet link aggregation
Enhancement
None
Dependency
eNodeB
This feature is not applicable to UMPT board.
Transport network
The transport network's ingress equipment from eNodeB must support this function.
It must support Ethernet.
3.4.7 LOFD-003019 IPsec Tunnel Backup

Model
LT1S00IPTB00
Availability
This feature is
Summary
This feature provides prime and backup IPsec tunnels from one eNodeB to 2 security
gateways (Se-GW). It improves the reliability of eNodeB transportation paths protected by
IPsec tunnels.
Benefits
Without this feature, eNodeB could only establish one IPsec tunnel with Se-GW. If this tunnel
is broken, the data transportation protected by IPsec will stop. The introduction of prime and
backup IPsec tunnels by this feature could help the IPsec protected data transportation

eRAN
continues when one of the tunnels is broken so that the reliability of IPsec transportation is
improved.
Description
During the deployment of LTE network, in order to guarantee the security of the service, the
network is divided into trusted and non-trusted parts. The Se-GW is deployed between the
trusted and non-trusted networks. The EPC network elements stay in the trusted network and
IPsec tunnel is used to protect the data transportation between Se-GW and eNodeB in the
non-trusted network.
When 2 Se-GWs are used, eNodeB could establish 2 IPsec tunnels (one prime, one backup) to
the Se-GWs. In normal condition, both tunnels are ready to be use. The eNodeB chooses the
prime tunnel based on the priority of IPsec tunnels for the uplink transportation. For the
downlink transportation, eNodeB should support receive data in prime and backup tunnels at
the same time because both tunnels are up and running, the data could be sent from Se-GW to
eNodeB in either tunnel.
The eNodeB uses BFD to check the connectivity between itself and Se-GW, if the prime
tunnel is broken, the eNodeB will hand over the uplink data transportation to the backup
tunnel. In the downlink direction, the Se-GW needs to support IPsec tunnel hand over to
backup tunnel together with eNodeB.
Enhancement
None
Dependency
CN
Security gateway in core network needs to support this function.
Other features
LOFD-003009 IPsec and LOFD-003007 Bidirectional Forwarding Detection
3.4.8 LOFD-081280 eNodeB Supporting Multi-operator PKI

Availability
This feature is
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.

eRAN
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 3-15, 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 3-15 eNodeB supporting Multi-operator PKI

eRAN
Enhancement
None
Dependency
eNodeB
The eNodeB must be configured with the UMPT, UMDU, LMPT or UTRPc board to
support this feature.
UE
None
Transport Network
Multiple CA servers must be deployed in the network.
CN
None
OSS
None
Other Features
None.
Others
None
3.4.9 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

eRAN
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
Transport Network
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

eRAN
3.5 RAN Sharing

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 the RAN resource to reduce CAPEX (Capital Expenditure) and OPEX
(Operating Expense).
Description
The MOCN (Multiple Operator Core Network) network sharing solution is to share the RAN
resources, including frequency and baseband resources for all the operators. Different
operators share the same cell and each eNodeB can connect with all operators' Core Networks.
The system information broadcasted 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.

eRAN
Figure 3-16 RAN Sharing with common carrier
All the LTE UEs supporting MOCN should be able to read up to 4 PLMN-ids and select one
of the PLMN-ids at initial attachment. UEs indicate the selected PLMN-id to the eNodeB.
The eNodeB shall select an appropriate MME for the PLMN-ids indicated by the UE.
The MOCN Network Sharing solution supports shared master OSS which is linked to
different NMS through different interfaces.
The shared eNodeB and non-shared eNodeB can be connected to each other. In the shared
area, a UE can hand over from one shared eNodeB to another one. If UE moves to a non
shared area, the eNodeB will select an appropriate neighbor cell for the handover based on
some principles, for example, the same operator's network may be considered firstly. The
Inter-working between different RATs may be used during the handover.
The MOCN Network Sharing has the following features.
Multi PLMN-ids are broadcasted on the common carrier and the Core Network is
separated.
Support independent logo and name display.
The shared OSS connects different NMS through North interference.
Support up to 4 operators.
Enhancement
In eRAN2.1
The function Dynamic Radio Resource Management is introduced.
This feature guarantees the fairness and flexibility of MOCN Network Sharing. All radio
resource could be shard dynamically and fairly between operators.
This feature meets the following general principle of fair sharing resources.
1. Balance between maximum system throughput and fair sharing resources between
MOCN operators.

eRAN
2. Any unused resources shall be used by other operators.

3. Fair sharing resources solution shall be used for both uplink and downlink directions.
Operators sharing a network may have different service model and different price model.
The QoS parameters could be totally different. Without this feature, in high load
situations, the operator with higher QoS services will occupy more radio resources
because the dynamic scheduling algorithm will consider QCI to balance system
throughput and user fairness.
With this feature, the operator fairness is considered. The priority of each operator is
calculated according to the occupying RB ratio and predefined ration of each operator.
The scheduling is done between the operators according to the operator priority first.
Then scheduling within each operator is done.
Preemption algorithm in admission control is also enhanced in this feature. Service of
operator A can preempt service of operator B only when RB occupancy of A is less than
A's predefined ration and RB occupancy of B is large than B's predefined ration.
In eRAN3.0,
Four counters for each operator are introduced to measure the RB usage by this operator.
1. Downlink RB usage belonging to its own quota
2. Uplink RB usage belonging to its own quota
3. Downlink RB usage belonging to other operator's quota
4. Uplink RB usage belonging to other operator's quota
In eRAN6.0
One S1 interface can belong to multiple PLMNs. Using an S1 interface, an eNodeB can
connect to either an MME included exclusively in a PLMN or an MME shared by
multiple PLMNs.
Dependency
Other features
This feature depends on LOFD-001018 S1-flex.
If a shared eNodeB is connected to multiple non-shared MMEs, LOFD-001036 RAN
Sharing with Common Carrier is dependent on LOFD-001018 S1-flex. If a shared
eNodeB is connected to a shared MME, LOFD-001036 RAN Sharing with Common
Carrier is not dependent on any feature.
3.5.2 LOFD-001037 RAN Sharing with Dedicated Carrier

Availability
This feature is
Summary
The eNodeB supports multiple operators to share the same Radio Access Network (RAN),
where the operators use dedicated carriers in the same eNodeB.

eRAN
Benefits
Operators can share the RAN resource to reduce Capital of Expenditure (CAPEX) and
Operational Expenditure (OPEX).
Description
Huawei eNodeB supports Radio Access Network sharing as a part of Network sharing
functions. The LTE RAN Sharing Solution with dedicated carrier enables multiple operators
to share all eNodeB hardware resources. Different core networks are connected to the same
eNodeB separately. Multiple operators can cover the same area with their own frequency in a
single physical RAN. Each operator will have its own Tracking Area Code referring to its cell.
The architecture is shown in the following figure.
Figure 3-17 RAN Sharing architecture
When a UE accesses a cell, the eNodeB identifies which core network it should be routed to
according to the cell it comes from. Different cells are corresponding to different operators. If
S1-flex is applied, the eNodeB may select an MME node for UE by GUMMEI which is part
of UE's GUTI.
The Network Sharing solution supports shared master OSS which is linked to different NMS
through different interfaces. Cell-level FM&PM data can be independent for all operators.
The shared eNodeB can be connected to non-shared eNodeB and there is no restriction for a
UE to hand over from a shared eNodeB to a non-shared one .When operators have dedicated
network in the non-shared area, the UE will be only handed over to the same operator's
network although the target network (same operator) might not be LTE.
The dedicated carrier Network Sharing has the following features:
Each operator broadcasts its own PLMN-id on its own carrier separately.
Support independent logo and name display.
Independent cell-level FM&PM. The shared OSS connects different NMS through Itf-N
interference.
Independent License Management.
Independent feature activation and deactivation

eRAN
Enhancement
In eRAN6.0
one S1 interface can belong to multiple PLMNs. Using an S1 interface, an eNodeB can
connect to either an MME included exclusively in a PLMN or an MME shared by
multiple PLMNs.
Dependency
Other features
This feature depends on LOFD-001018 S1-flex.
If a shared eNodeB is connected to multiple non-shared MMEs, LOFD-001037 RAN
Sharing with Dedicated Carrier is dependent on LOFD-001018 S1-flex. If a shared
eNodeB is connected to a shared MME, LOFD-001037 RAN Sharing with Dedicated
Carrier is not dependent on any feature.
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

eRAN
Dependency
Other features
LOFD-001036 RAN Sharing with Common Carrier or LOFD-001037 RAN Sharing with
Dedicated Carrier
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.
3.5.5 LOFD-070206 Hybrid RAN Sharing

Availability
This feature is

eRAN

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 3-18 Shared eNodeB operating on both common and dedicated frequencies

eRAN
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 3-19 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

eRAN
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.
3.5.6 LOFD-070204 Operator Load Based Intra-LTE MLB

Availability
This feature is
Summary
In radio access network (RAN) sharing scenarios, every operator can perform load balancing
based on the load status of its 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 brings the following benefits:
Makes full usage of network resources.
Increases the system capacity.
Reduces the possibility of system overload.
Improves the access success rate.
Description
In RAN sharing scenarios, this feature is recommended for balancing loads among cells of an
operator.
The cell load of an operator can be evaluated by the following values:
Physical resource block (PRB) usage of the operator
Number of synchronized UEs that served by the operator in a cell
With this feature, every operator can monitor its cell load independently. If the cell load of an
operator exceeds the specified threshold for load balancing, the eNodeB transfers some UEs
served by this operator in the cell to an inter-frequency cell of this operator with light load.
Operator-load-based intra-LTE MLB is trigger 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
None

eRAN
Dependency
Other features
This feature depends on the following features:
LOFD-001036 RAN Sharing with Common Carrier or LOFD-070206 Hybrid RAN
Sharing
LOFD-070215 Intra-LTE User Number Load Balancing or LOFD-001032 Intra-LTE
Load Balancing
Others
X2 interfaces have been configured and support load information exchange.
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.

eRAN
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

eRAN
3.6 Advance Micro

3.6.1 LOFD-002016 Micro eNodeB Self-planning
Availability
This feature is
not applicable to Macro
Summary
This feature provides self-planning for Micro eNodeB. With self-planning, wireless
parameters required by Micro eNodeBs in one area could be generated automatically based on
a small number of pre-configured basic wireless parameters for this area.
Benefits
This feature can reduce the cost of network planning.
This feature can reduce the difficulty of network planning for Micro eNodeB.
This feature can increase the flexibility of network re-planning for Micro eNodeB.
Description
Before installation:
Importing available TAC, frequency and the range of PCI, RACH Root Sequence.
Figure 3-20 Wireless parameter self-planning
Only the basic parameters for each area need to be planned and prepared in the EMS. Other
configuration parameters for the Micro eNodeB in the area are generated automatically after
installation.

eRAN
After installation:
The Micro eNodeB works as a scanner to scan GSM/UMTS/LTE(LTE information is only
supplied by BTS3203E) cells' information around it. Base on the information, the system can
discover the area where the Micro eNodeB is installed, and get the area basic parameters.
Base on the area's basic parameters and the neighbor cells' info, the system can generate the
other necessary parameters for Micro eNodeB through the self-planning algorithm.
Enhancement
In eRAN7.0
Add TAC. TAC got from area parameter in eRAN6.0, but can generate base on scan
RAC/LAC/TAC of neighbor GSM/UMTS/LTE cell.
Parameter templates simplify. eRAN6.0 need import area parameter including neighbor
cell, every area need one table. eRAN7.0 no area parameter, all Micro eNodeB only need
one table.
When planning PCI consider the rule of mod3/mod30.
Dependency
Others
The existent cells (G/U/L) list Info (cell id,mcc,mnc,..) in each area are offered to the
planning engineer, which is optional.
Basic parameters for each area are planned and prepared in the EMS.
This feature depends on the sniffer.
3.6.2 LOFD-001057 Load Balancing based on Transport QoS

Model
LT1S00LBTQ00
Availability
This feature is
Summary
The transport capability of the Micro eNodeB is weaker than Macro eNodeB, so the S1
transport capability maybe not enough if the backhaul traffic is too high. When the S1 traffic
is too high, the Micro eNodeB will start load balance algorithm, and some UEs will be
handover to the cells of other Micro eNodeB or Macro eNodeB to reduce the load of S1
transport.
Benefits
Reduce the load of S1 transport to prevent congestion.

eRAN
Description
In some situation of commercial LTE network, some eNodeBs' S1 transport have high load
but other eNodeBs' S1 transport load is low because of the differentia of UE service. Under
this condition, it can trigger load balancing algorithm.
The Micro eNodeB measures the S1 transport load and receives the neighboring eNodeBs'
load information at the same time. The Micro eNodeB evaluates the load and decides whether
to get some UEs to handover to other cells of neighboring eNodeBs. If the Micro eNodeB's
S1 transport load is very high which is beyond the threshold, at the same time, the
neighboring eNodeB's S1 transport load is low, some UEs get to handover to other eNodeB's
cell. The S1 transport load is the use rate of the bandwidth.
Only the inter-frequency load balancing is supported.
Transport load balancing is used in the scenario of overlap coverage area by the multi
inter-frequency LTE cells exist.
Enhancement
None
Dependency
eNodeB
An X2 interface is required to support this feature.
Other features
This feature depends on LOFD-001032 Intra-LTE Load Balancing.
3.6.3 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

eRAN
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.
3.6.4 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.

eRAN
Figure 3-21 horizontal beamwidth adjustment
Enhancement
None
Dependency
eNodeB
This feature is only applicable to BTS3203E with internal antenna.
3.7 Site Architecture

3.7.1 LOFD-001076 CPRI Compression
Availability
This feature is
Summary
This feature reduces the common public radio interface (CPRI) bandwidth required by a cell.
Benefits
Increases the number of RRUs that can be cascaded on a CPRI port.
Decreases the number of optical fibers.

eRAN
Reduces eNodeB installation and reconstruction costs.
Description
This feature decreases CPRI bandwidth resources required by a cell. With this feature, more
RRUs can be cascaded on a CPRI port without changing the CPRI line rate, cell bandwidth,
or number of antennas for the cell. This reduces eNodeB installation and reconstruction costs.
When this feature is enabled, the CPRI data volume decreases to about 50% of the original
CPRI data.
Enhancement
eRAN7.0:
Lampsite supports 3:1 or 4:1 compression rate in the CPRI between RHUB and pRRU,
which makes U2C+L20/10MHz or L 2*20MHz in one ethernet cable available.
Dependency
eNodeB
The cell bandwidth must be 20 MHz, 15 MHz, 10 MHz, or 5 MHz.
This feature is not applicable to LBBPc.
The model of the RF modules is MRFUe, pRRU3901, RRU3229, RRU3260, RRU3268,
RRU3628, RRU3630, RRU3632, RRU3935, RRU3638, RRU3639, RRU3841,
RRU3642, RRU3832, RRU3838, RRU3929, RRU3932, RRU3939, RRU3942,
RRU3961, or RHub3908.
3.7.2 LOFD-003032 Intra-BBU Baseband Sharing (2T)

Availability
This feature is
Summary
This feature implements baseband resource convergence in a BBU. With this feature, only one
LBBP is connected to an optical fiber and both the LBBPs process baseband data.
Benefits
Decreases the number of optical fibers
Reduces eNodeB installation and reconstruction costs.

eRAN
Description
In LampSite solution, CPRI data of multiple cells need be transmitted on one optical fiber,
and limited cell number is supported in one baseband board. This feature combines the
baseband data of multiple cells on one LBBP to be transmitted on one optical fiber. This
feature decreases the number of required optical fibers and therefore reduces the deployment
cost.
Enhancement
None
Dependency
None
3.7.3 LOFD-003029 SFN

Availability
This feature is
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.
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 call drop rate compared with the independent
RRU/pRRU deployment.
Description
This feature provides independent demodulation of signals from multiple RRUs in one cell.

eRAN
In the uplink, the eNodeB performs independent demodulation of the multiple RRU
receiver signals within a BBU. The eNodeB receives PRACH and SRS from all RRUs
first. 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 eNodeB copies the signal of a cell and outputs it to multiple RRUs.
Comparing to single RRU cell, the multiple RRUs combined cell has no interference
between RRUs, but obtained gain from transmitting from multiple RRUs.
A cell can be divided into multiple coverage area, each coverage area has independent RRU,
and multiple RRUs belong to the same cell and have the same PCI.
This feature supports two to six RRUs/pRRU groups to be combined to support one SFN cell
based on LBBP board type. All RRUs/pRRU used for one SFN cell's combination shall be
connected to LBBP board(s) within same BBU.
Enhancement
eRAN8.1
4T4R RRUs can be combined to serve an SFN cell. A mixed configuration of 2T2R,
2T4R, and 4T4R RRUs can be supported.
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:
Allows RRUs serving inter-BBP physical cells to jointly receive data;
Allows RRUs serving up to three physical cells to jointly receive data;
Allows RRUs serving the physical cells (working in 1R+1R or 1R+2R mode) to
jointly receive data.
SFN cells support the UL CoMP feature.
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.
Dependency
eNodeB
This feature requires SRS resource allocation.
When the system bandwidth is 1.4 MHz or 3 MHz, this feature is not recommended.
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.
The LBBPd1, LBBPd2, LBBPd3, UBBPd3, UBBPd4, UBBPd5, and UBBPd6 boards
apply to both macro base stations and LampSite base stations, and each of these boards
supports an inter-BBP SFN cell served by at most six combined RRUs.
The TX/RX mode for an SFN cell can be configured as 1T1R, 2T2R, 2T4R, or 4T4R. A
mixed configuration of these modes can be supported.
This feature is not supported with LBBPc for Macro RRU combination.
eCO
None
UE

eRAN
None
Transport network
None
CN
None
OSS
None
Other features
This feature is not compatible with the following features:
LOFD-001031 Extended CP
LOFD-001039 RF Channel Intelligent Shutdown
Others
None
3.7.4 LOFD-070205 Adaptive SFN/SDMA

Availability
This feature is
applicable to macro eNodeBs from eRAN7.0
not applicable to micro eNodeBs
applicable to LampSite eNodeBs from eRAN7.0
Summary
When multiple common cells are combined into an SFN cell, the eNodeB classifies UEs
according to their signal quality, and implements adaptive joint scheduling and independent
scheduling of time-frequency resources in multiple cells. The space division multiple access
(SDMA) technology is introduced to implement independent scheduling of time-frequency
resources in multiple cells.
Benefits
Adaptive SFN/SDMA increases resource usage and system throughput while ensuring
coverage quality.
An inter baseband board connection enables communication between different cells and
allows the adaptive SFN/SDMA feature to be more widely used.
The uplink joint reception function of an SFN cell is enhanced as follows:
Allows RRUs serving inter-BBP physical cells to jointly receive data;
Allows RRUs serving up to three physical cells to jointly receive data;
Allows RRUs serving the physical cells (working in 1R+1R or 1R+2R mode) to jointly
receive data.
SFN cells support the UL CoMP feature.

eRAN
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.
Description
Based on the uplink reference signal received power (RSRP), the eNodeB determines UE
attributes and then performs one of the following functions:
Joint scheduling of resources in all cells
Joint scheduling of resources in some cells
Independent scheduling of resources in a single cell
In addition, the eNodeB collects the working RRU list. The PDSCHs and PUSCHs of the
RRUs in this list will be scheduled jointly or independently.
Enhancement
eRAN8.1
4T4R RRUs can be combined to serve an SFN cell. A mixed configuration of 2T2R,
2T4R, and 4T4R RRUs can be supported.
Two RRUs can be combined to serve a physical cell. A maximum of 12 RRUs can be
combined.
Dependency
eNodeB
This feature requires SRS resource allocation.
This feature is not recommended when the system bandwidth is 1.4 MHz or 3MHz.
If an SFN cell is set up on the LBBPc, this feature applies only to LampSite eNodeBs
instead of macro eNodeBs, and each LBBPc supports an intra-BBP SFN cell served by at
most three RRUs.
If an SFN cell is set up on the LBBPd1, LBBPd2, LBBPd3, UBBPd3, UBBPd4,
UBBPd5, and UBBPd6 boards, this feature applies to both macro and LampSite
eNodeBs. These BBPs support either intra- or inter-BBP SFN cells. Such a cell can be
served by at most six RRUs.
The TX/RX mode for an SFN cell can only be configured as 1T1R, 2T2R, 2T4R, or
4T4R. The mixed configuration of these modes is supported.
The TM9 switch can be turned on only when two physical cells are combined into an
SFN cell.
eCO
None
UE
None
Transport network
None
CN
None
OSS

eRAN
None
Other features
This feature requires LOFD-003029 SFN.
This feature is not compatible with the following features:
LOFD-001067 800M Self-interference Cancellation
LBFD-002022 Static Inter-Cell Interference Coordination
LOFD-001014 Dynamic Inter-Cell Interference Coordination
MRFD-231806 GSM and LTE Dynamic Power Sharing(LTE)
Others
None
3.7.5 LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU

Availability
This feature is
applicable to Macro and LampSite from eRAN8.1
implemented in Cloud BB networking scenarios
Summary
This feature is used with the single frequency network (SFN) feature. With this feature,
multiple remote radio units (RRUs) can be combined to serve an 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 chooses the RRU with the best signal quality for 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.
Benefits
This feature is used with the SFN feature. In addition to the benefits from the SFN feature,
this feature provides the following benefits:
This feature has no restrictions on physical cells to be combined into an SFN cell. That is,
physical cells with the strongest interference can be combined into an SFN cell, which further
improves edge coverage.

eRAN
Description
Depending on different types of baseband processing units, this feature enables 2 to 6 physical
cells to be combined into an SFN cell. These physical cells can be configured 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
None
Dependency
eNodeB
LMPT.
The TX and RX mode of antennas in all physical cells to be combined can be 1T1R,
2T2R, 2T4R, or 4T4R. Physical cells with different antenna modes can be combined
into an SFN cell.
All the physical cells to be combined can reside in multiple BBUs in a Cloud BB.
eCO
None
UE
None
Transport network
None
CN
None
OSS
None
Other features
This feature requires LOFD-003029 SFN.
This feature is not compatible with any of the following features:

eRAN
LOFD-081219 UL CoMP Based on Relaxed Backhaul

Others
When uplink frequency hopping is enabled, uplink joint reception cannot be used.
3.7.6 LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on

Coordinated BBU
Availability
This feature is
applicable to Macro and LampSite from eRAN8.1
implemented in Cloud BB networking scenarios
Summary
This feature is used with the adaptive SFN/SDMA feature. With this feature, multiple RRUs
can be combined to serve an SFN cell.
When multiple common cells are combined into an SFN cell, the eNodeB classifies UEs into
different categories according to the signal quality and adaptively performs joint scheduling
or independent scheduling of time-frequency resources for multiple cells. The space division
multiple access (SDMA) technology is used to implement independent scheduling of
time-frequency resources for multiple cells.
Benefits
This feature is used with the adaptive SFN/SDMA feature. In addition to the benefits from the
adaptive SFN/SDMA feature, this feature provides the following benefits:
This feature has no restrictions on physical cells to be combined into an SFN cell. Common
cells with the strongest interference can be combined into an SFN cell. This feature further
improves edge coverage.
Description
Depending on different types of baseband processing units, this feature enables 2 to 6 physical
cells to be combined into an SFN cell. These physical cells can be configured 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

eRAN
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
None
Dependency
eNodeB
LMPT.
The TX and RX mode of antennas in all physical cells to be combined can be 1T1R,
2T2R, 2T4R, or 4T4R. Physical cells with different antenna modes can be combined
into an SFN cell.
All the physical cells to be combined can reside in multiple BBUs in a Cloud BB.
eCO
None
UE
None
Transport network
None
CN
None
OSS
None
Other features
The prerequisite features are as follows:
LOFD-003029 SFN
LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU
This feature is not compatible with any of the following features:
LOFD-001067 800M Self-interference Cancellation
LBFD-002022 Static Inter-Cell Interference Coordination

eRAN
LOFD-001014 Dynamic Inter-Cell Interference Coordination

Others
When uplink frequency hopping is enabled, uplink joint reception cannot be used.
3.7.7 LOFD-081221 Super Combined Cell

Availability
This feature is
Summary
This feature together with LOFD-003029 SFN allows multiple single-frequency-network
(SFN) cells that provide continuous coverage to be combined into one cell, called super
combined cell, to support high-speed mobility.
This feature uses a seamless transfer technique to reduce the number of handovers between
SFN cells. In addition, this feature uses a joint transmission technique to improve signal
quality in the overlapping areas between SFN cells.
The SFN cells in a super combined cell must be configured with the same physical cell
identifier (PCI) but different cell global identifications (CGIs).
Benefits
Reduces the number of handovers of UEs moving at high speed and improves signal
quality in the overlapping areas between SFN cells.
Enables flexible configuration of physical cells in an SFN cell.
Assume that there are 36 physical cells. Before this feature is used, each SFN cell needs
to contain 6 physical cells to minimize the number of handovers and there are a total of 6
SFN cells. After this feature is used, each SFN cell can contain only 3 cells and there are
a total of 12 SFN cells.
Increases UE throughput by more than 50% in the traditional handover areas between
SFN cells.
Description
This feature allows multiple SFN cells that provide continuous strip coverage to be combined
into a super combined cell to support high-speed mobility. These SFN cells (each having three
to six physical cells) must be served by the same baseband unit (BBU) or different BBUs
connected in a centralized Cloud BB architecture. In addition, these SFN cells must be
configured with the same PCI but different CGIs.

eRAN
This feature uses a seamless transfer technique and a joint transmission technique between
SFN cells. These techniques reduce the number of handovers and improve signal quality in
the overlapping areas between SFN cells, thereby improving the experience of users moving
at high speed.
Enhancement
None
Dependency
eNodeB
LMPT.
A UMPT must be configured as the main control board for each BBU. The baseband
processing unit (BBP) model must be UBBPd3, UBBPd4, UBBPd5, UBBPd6, or
UBBPd9.
All combined physical cells must be served by the same BBU or different BBUs
connected in a centralized Cloud BB architecture.
The requirements on cells are as follows:
Neighboring cells expected to work with a super combined cell must be common
cells or SFN cells served by Huawei base stations.
It is not recommended that a super combined cell cover crossing high-speed railways.
It is not recommended that this feature be enabled for SFN cells that provide
overshoot coverage.
The SFN cells in a super combined cell cannot be served by the same BBPs as
common cells or other SFN cells.
A super combined cell can contain up to 100 SFN cells.
eCo
None
UE
None
Transport network
This feature can be implemented within a BBU or between BBUs connected in a
centralized cloud BB architecture.
CN
CN equipment must be provided by Huawei.
OSS
None
Other features
The prerequisite features are as follows:
LOFD-003029 SFN
LOFD-081207 Specified PCI Group Based Neighboring Cell Management
When a super combined cell needs to work with neighboring cells, LOFD-081207
Specified PCI Group Based Neighboring Cell Management must be enabled in these

eRAN
neighboring cells. In addition, the PCI of the SFN cells must be included in the
specified PCI range; otherwise, UEs may fail to be handed over from
non-super-combined cells to this super combined cell.
The mutually exclusive features and functions are as follows:
LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz
LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture

eRAN
Optional Feature Description 4 O&M
4 O&M
4.1 SON Self-Configuration

4.2 SON Self-Optimization
4.3 SON Self-Healing
4.4 Power Saving
4.5 Antenna Management
4.1 SON Self-Configuration

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.

eRAN
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 4-1 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:

eRAN
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.

eRAN
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.
When X2 automatic removal is triggered at the request of the peer eNodeB, due to an X2
fault, or due to low X2 usage, if the local eNodeB is a Huawei eNodeB and the peer
eNodeB is a third-party eNodeB, Huawei eNodeB reports the X2 automatic removal
advice to the U2000. Operators determine whether to take the advice.
Dependency
UE
UEs must support this feature.
OSS
This feature requires the OSS feature WOFD-180600 Automatic Neighbor Relation
Optimization - LTE.
4.1.2 LOFD-002002 Inter-RAT ANR

Availability
This feature is

eRAN

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:

eRAN
Figure 4-2 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.

eRAN
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:
1. Setting: user can enable or disable the feature or sub-function such as periodic Inter-RAT
HO function in Inter-RAT HO
2. 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

eRAN
eCO
None
UE
The UE must support this feature
Transport Network
None
CN
None
OSS
This feature depends on OSS feature WOFD-181400 Inter-RAT Automatic Neighbor
Relation Optimization -LTE.
Other Features
None
Others
None
4.1.3 LOFD-002004 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 trigged automatically by the U2000 or LMT to launch a comprehensive
self-test after the software and configuration data file are downloaded. After the test is
complete, the U2000 or LMT can obtain a test report.
Benefits
Except hardware installation, no other manual operation needs to be performed by field
engineers for the eNodeB startup for the first time.
Description
When the eNodeB is powered on, it obtains the data needed to establish the OM link, such as
the IP address, subnet mask, IP address of the EMS, and IP address of the security gateway,
through the DHCP server. If transport network DHCP server cannot provide these information,
the info must be input into the eNodeBs before installation (in storehouse or other convenient
place) or through a USB stick (the USB stick is not special for site but public for many sites)
by field engineers.

eRAN
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 eNodeB, if PPPoE is used for transport authentication, then the PPPoE account
info must be pre-configured into the eNodeB before installation (in storehouse or other
convenient place) or through USB stick by field engineers.
After the software and configuration data file are downloaded, the U2000 or LMT can
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 contents:
eNodeB basic information, such as type, name
Software version information
Board status information, such as information about the baseband and RF units
Transport status information ( physical layer and link layer)
Cell status
Enhancement
In eRAN2.0,
The eNodeB can establish an IPsec link with the security gateway automatically during
the self-configuration procedure.
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 identify the eNodeB automatically
by comparing the received geographical information with the predefined geographical
information.
Automatic transport setup is supported. The eNodeB has three types of transport-related
interfaces: S1 interface, X2 interface, and OM channel interface. Accordingly, the
eNodeB provides three automatic transport setup processes: S1 setup, X2 setup, and OM
channel setup. The general network topology is shown in the following figure.
In eRAN2.1
A barcode of eNodeBID (In eRAN3.0,DID is used instead of eNodeBID)can be scanned
into eNodeB by a barcode reader connected to the USB port of the MPT. The scanned
eNodeBID can be send to EMS, so EMS will identify the eNodeB automatically.

eRAN
Figure 4-3 general network topology
In eRAN2.1
The eNodeB has parameters pre-configured in factory or other places before the
installation, such as the MAC address, local OM IP, and unique ID. All these parameters
need not be set or modified manually.
The automatic transport setup procedure is as follows:
1. When the eNodeB is powered on, it negotiates automatically the transport layer 1/2
(PHY/MAC) parameters, such as duplex mode, with the peer device. The peer device
can be a LAN switch, router, or another eNodeB.
2. The eNodeB is able to get VLAN ID of peer devices (switch, router) by VLAN scanning.
So the peer devices could receive the data from eNodeB correctly.
3. The eNodeB receives the OM channel parameters from the DHCP server, such as the
Internet IP address, Network Element Management (NEM) IP address, and SeGW IP
address and operator CA information (e.g. name, IP address, protocol type).
4. Based on the operator's CA information, eNodeB is able to retrieve operator certificate
from CA using CMPv2 protocol. The certificate is used for SSL and IPsec certification
later.
5. The eNodeB establishes an IPsec tunnel with the SeGW, obtains the Internal IP address,
and then establishes the OM channel with the NEM.
6. After the software and configuration file are downloaded and installed, the eNodeB
receives the necessary transport parameters of the S1 interface from the NEM, such as
the eNodeB traffic IP address and MME SCTP IP.
7. The eNodeB starts the S1 interface self-configuration procedure and establishes the S1
link.
This feature also includes the X2 interface auto setup function of the Automatic
Neighbor Relation feature. When the network is launched, the eNodeB can find out its
new neighboring site, which is not configured as neighboring site. After receiving
necessary transport data from the U2000 or core network, the eNodeB establishes the X2
link with this new neighboring site automatically.
eNodeB is able to get VLAN ID of peer devices (switch, router) by VLAN scanning. So
the peer devices could receive the data from eNodeB correctly.

eRAN
Based on the operator's CA (Certificate Authority) information, eNodeB is able to

retrieve operator certificate from CA using CMPv2 protocol. The certificate is used for
SSL and IPsec certification later.
Based on the configuration of DHCP server, eNodeB is able to request OM IP address
from either DHCP server or NMS.
In eRAN3.0
eNodeB supports automatic obtaining and configuring IPv6 transport information
through OAM. This function is only applicable to Macro eNodeB.
eNodeB supports X2 interface auto setup function of the Automatic Neighbor Relation
feature under IPv6. This function is applicable to Macro eNodeB.
eNodeB supports X2 interface auto setup with IPsec protection on X2 interface links.
eNodeB supports to obtain SGW's IP address for MME when one service is set up. After
eNodeB obtains SGW's IP address from the signaling between MME and eNodeB,
eNodeB auto-configured S1-U interface.
Dependency
Other features
The X2 interface automatic setup function in this feature depends on LOFD-002001
Automatic Neighbour Relation (ANR).
4.1.4 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.

eRAN
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

eRAN
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:
1. Immediate & Automatic delivery: The EMS will deliver the new PCIs to the eNodeB as
soon as it is generated.
2. Regular & Automatic delivery: The EMS will deliver the new PCI at a cycle time basis.
3. 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:
1. 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.
2. 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:
1. 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.
2. 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.
3. 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.

eRAN
Dependency
eNodeB
None
eCO
None
UE
None
Transport Network
None
CN
None
OSS
This feature depends on OSS feature WOFD-170200 Automatic PCI Optimization -LTE.
Other Features
None
Others
None
4.1.5 LOFD-081225 Neighbor Cell Classification Management

Availability
This feature is
Summary
This feature allows classification of intra-RAT neighbor relationships based on the statistics of
neighbor relationships and applies different management policies to different classes of
neighbor relationships. This feature helps increase the neighbor relationship management
efficiency and improve operator's OM experience.
Benefits
This feature generates the automatic classification results of neighbor relationships and
increases the OM efficiency of neighbor relationships.
Description
In the intra- and inter-frequency neighboring relation table (NRT), a new attribute
"NcellClassLabel" is added to classify the neighbor relationships into "Formal" and
"Extended" ones. The eNodeB collects the number of handover attempts from the local cell to
a neighboring cell within a measurement period and automatically sets this attribute for the
neighbor relationship. Based on this attribute, operators can prioritize neighboring cells and
the eNodeB adopts differentiated policies for neighboring cells.

eRAN
In a handover to a neighboring cell with this attribute set to "Formal", the UE is handed over
directly based on the NRT configuration. In a handover to a neighboring cell with this
attribute set to "Extended", the UE is handed over based on the ECGI reading results.
If two intra-frequency neighboring cells share one PCI, then:
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.
If the attribute values of the two cells are "Extended", the local cell does not perform PCI
confusion detection on these neighboring cells.
The function of setting the attribute "NcellClassLabel" based on the number of handover
attempts and the function of selecting the target cell based on the attribute "NcellClassLabel"
require the LOFD-002001 Automatic Neighbour Relation (ANR) feature.
The function of PCI confusion detection based on the attribute "NcellClassLabel" requires the
LOFD-002007 PCI Collision Detection & Self-Optimization feature.
Enhancement
None
Dependency
eNodeB
None
eCO
None
UE
This feature requires support from the UE.
Transport Network
None
CN
None
OSS
None
Other Features
None
Others
None
4.2 SON Self-Optimization

4.2.1 LOFD-001032 Intra-LTE Load Balancing
Availability
This feature is

eRAN

Summary
This feature resolves load imbalances between the serving cell and its inter-frequency
neighboring cells.
Benefits
This feature achieves better utilization of network resources and increases system capacity. In
addition, it reduces the probability of system overload and increases 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 lower load.
After this feature is enabled, a local cell measures its own cell load If the local cell load
exceeds a preset threshold, the eNodeB of the local cell will collect neighboring cell load
information. If a neighboring cell's load is lower than a threshold, the eNodeB to which the
local cell belongs will decide whether to hand over some UEs to the lower loaded neighboring
cell. The cell load is represented by the physical resource block (PRB) usage, as defined in
3GPP TS 36.314.
The load balancing procedure consists of the following activities: load measurement and
evaluation, load information exchange, load balancing decision, load balancing execution and
performance monitoring.
Intra-LTE Load Balancing is used in scenarios where inter-frequency LTE cells have highly
overlapping coverage.
Blind load balancing is supported for the scenarios where no X2 interface is available or the
X2 interface does not support load information exchange.
Enhancement
In eRAN7.0
Frequency priority based MLB is supported.
Blind load balancing is applicable to scenarios where no X2 interface is available or the
Dependency
None.
4.2.2 LOFD-070215 Intra-LTE User Number Load Balancing

Availability
This feature is

eRAN

Summary
This feature resolves user number load imbalances between cells and frequencies and makes
load sharing on control panel resource.
Benefits
This feature achieves better utilization of network resources and balance user number to
reduce the probability of burst traffic.
Description
Intra-LTE User Number Load Balancing contains connected mode and idle mode. It is
recommended in commercial LTE networks with multiple LTE frequencies where one
frequency has a higher user number but other frequencies have lower user number.
For connected mode, serving cell measures its own cell user number, if the number exceeds a
preset threshold, the serving cell will send handover request to the neighboring cells which
shall acknowledge or reject handover judged by their own user number load.
For idle mode, users in normal RRC release procedure can be released to different frequency
on configured proportion, by using Dedicated Priority within RRC Connection Release
message. This function can precisely distribute idle users to different frequency as operators
wish.
Blind load balancing is supported for the scenarios where no X2 interface is available or the
Intra-LTE User Number Load Balancing is used in scenarios where inter-frequency LTE cells
have highly overlapping coverage.
Enhancement
None
Dependency
None
4.2.3 LOFD-081227 Intra-LTE Load Balancing for Non-cosited

Cells
Availability
This feature is

eRAN
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

eRAN
4.2.4 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 achieves better utilization of network resources of LTE and UMTS network and it
is based on UE capability. In addition, it reduces the probability of system overload and
increases the access success rate.
Description
In a commercial LTE network, LTE cells have high load because of the differentia 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, UE dedicated 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 functions:
Operators can enable or disable the Inter-RAT Load Sharing to UTRAN function.
eRAN3.0

eRAN
Inter-RAT Load Sharing to UTRAN for UEs releasing to Idle Mode is introduced. 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 Priority contained 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
Transport network
None
CN
None
OSS
None
Other features
LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN
Others
None
4.2.5 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.

eRAN
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
This feature requires LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and
GERAN.
4.2.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

eRAN
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

eRAN
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
Transport Network
None
CN
None
OSS
None
Other Features
None
Others
None
4.2.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
Optimize the back-off time
PRACH false alarm detection
Root sequence conflict detection

eRAN
Benefits
The feature improves the performance of random access.
Dynamic adjustment of preamble groups adjusts the ratio between random 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 for root sequence conflict between
cells. Based on the detection result, root sequences are replanned to eliminate root
sequence conflict and reduce the probability of preamble collision and false alarms
reporting.
Description
There are 64 PRACH preambles, which are divided into random 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 which part is
enough while another part is not enough, and eNodeB can adjust the number of the preamble
group dynamically according to the demand.
The PRACH configuration index indicates the number and positions of sub-frames which are
used to send random access preamble. The eNodeB measures the number of preamble during
the period, and eNodeB will adjust the PRACH configuration index to fulfill the demand. If
the number of preambles is more than threshold, the PRACH configuration index will be
adjusted to indicate more sub-frames, and vice versa.
When conflict on PRACH resource detected, eNodeB could send different back-off time
indicator to UEs. UE could select a random back-off time based on the back-off time indicator
to try access again, so that the chance of conflict again is reduced.
The eNodeB detects for false alarms based on the peak value of cross correlation sequence of
initially transmitted random preambles and the distance corresponding to the time 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
smaller than the threshold.
The distance corresponding to 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 conflict.

eRAN
Enhancement
eRAN8.1
Root sequence conflict detection is added.
The eNodeB supports the detection of root sequence conflict between intra-eNodeB cells
and between inter-eNodeB cells with X2 links.
Dependency
None
4.2.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

eRAN
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.
4.2.9 LOFD-081205 Automatic Congestion Handling

Availability
This feature is:
Summary
Based on condition-based adaptive parameter adjustment rules predefined in an eNodeB, the
eNodeB periodically determines whether to enable adaptive parameter adjustment for a cell
based on the monitored results, including UE number, physical resource block (PRB) usage,
and control channel element (CCE) usage on the physical downlink control channel (PDCCH)
in the cell. If the monitored results meet the conditions for parameter adjustments, the
eNodeB automatically adjusts parameters to improve network performance.
Benefits
In heavy traffic scenarios, the eNodeB automatically adjusts parameters based on
predefined rules to improve network performance and user experience.
Adaptive parameter adjustment simplifies network maintenance and reduces manpower
costs in heavy traffic scenarios.
Description
The eNodeB monitors usage of specified resources, such as the number of admitted users,
physical resource blocks (PRBs), and PDCCH control channel elements (CCEs). Based on the

eRAN
monitoring results and predefined trigger conditions, the eNodeB decides 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 intelligent optimization functions
whose trigger conditions are met.
With periodic execution of the preceding three operations, this feature helps monitor the
network load in a timely manner and automatically performs parameter adjustments to
improve network performance.
Figure 4-4 Mechanism for handling automatic configuration
Enhancement
None
Dependency
None

eRAN
4.3 SON Self-Healing

4.3.1 LOFD-002010 Sleeping Cell Detection
Availability
This feature is
Summary
Sleeping cell refers to one cell may have some serious problems but no obvious abnormal
event or alarm had been triggered. UEs may camp in this cell but they cannot setup any
service connection or access into the network. This feature is provided to detect such issues
and to notify operator.
Benefits
This feature will shorten the time to detect some cell with serious fault problem but not
having triggered an alarm yet
Description
The sleeping cell detection is a function that an eNodeB can automatically detect faulty cell
which cannot provide normal service but eNodeB does not report alarm to EMS, so operator
does not know if cell is under sleeping status and cannot solve it in time.
eNodeB can detect sleeping cell itself and report alarm to EMS. EMS also can implement an
algorithm to detect sleeping cell and generate an alarm. These two ways can be combined
together to find sleeping cell more accurately than only by one way.
eNodeB uses the connected user measurement method to detect the sleeping cell. eNodeB will
count connected user every second. If the user number keeps zero for a given period of time
(this time value can be configured), eNodeB will generate an alarm to EMS. EMS will
correlate this alarm with some other alarms (for example, the alarm from antenna to which the
cell is associated, the alarm from the Tx/Rx channel, etc). This alarm is generated when the
eNodeB detects that the cell has no accessing of any user for a long time.
After detecting the dormant cell, the eNodeB will deactivate and activate the cell
automatically.
It is suggested that this feature will be used with EMS sleeping cell detection feature together
to get more accurate result.
Enhancement
None
Dependency
None

eRAN
4.3.2 LOFD-002011 Antenna Fault Detection

Availability
This feature is
Summary
The faults on the antenna system and radio frequency (RF) channels are caused by the
improper installation of projects when the projects are created, relocated, or optimized. The
faults can also be caused by natural or external changes.
This feature provides the function of detecting faults on eRAN antennas and enables users to
detect and locate antenna faults.
Benefits
This feature implements the detection of common antenna faults, thus improving the
efficiency and accuracy of fault diagnosis.
By using this feature, RF engineers need not use equipment to measure eNodeB on site every
time, thus reducing the project cost.
Description
The antenna system plays an important role in mobile communications. The performance of
the entire network is affected by the following problems:
Improper type or location of the antenna system
Improperly configured parameters of the antenna system
Faulty antenna system
The antenna fault detection system can detect the following faults and raise related alarms:
Weak received signal
Imbalance of received signal between the main and the diversity
Voltage Standing Wave Ratio (VSWR) abnormal
Enhancement
None
Dependency
None

eRAN
4.3.3 LOFD-002012 Cell Outage Detection and Compensation

Availability
This feature is
Summary
Cell Outage Detection and Compensation provides automatic detection of cell outage, and
automatic adjustment of mobility related RRM parameters to compensate outage cells. It
solves and shortens the duration of cell outage that is a critical situation in the network,
especially if there is only one frequency/RAT.
Benefits
This feature enables the operators to shorten the duration of the cell outage detection, and to
keep subscribers' service in outage cell with best effort.
Description
Cell outage is a critical situation, especially if there is only one frequency/RAT. It can cause
service failure or great KPI degradation. In other hand, if there are alternative
frequencies/RATs, it is preferred to move UEs from the outage cell to these alternative
frequencies/RATs by triggering handover process to another frequency or system instead of
compensating the coverage of surrounding cells.
This feature consists of three functions, which are cell outage detection, RRM compensation
and Cell outage recovery.
Cell outage detection:
It consists of real time monitoring of both pre-defined alarms and cell KPI. According to the
pre-defined alarms the system will detect whether the cell is out of service or not. The KPI
monitoring will help to detect abnormal outage cases that will not trigger alarms through the
cell KPI degradation including sleeping cell. Note that this KPI threshold is configurable by
operator.
In some cases, a cell outage can be detected in short time by checking counters related to
eNodeB internal modules. To accelerate the detection process, this feature also supportsthe
assisted cell outage detection method. This method is independent to KPI measurement and
detects cell outage by checking internal eNodeB counters at an interval of 5 minutes. When
the audit result is abnormal, eNodeB reports the result to the U2000, and U2000 determines
that cell outage has occurred.
RRM compensation:
This function will adjust the mobility related RRM parameters, so that the UEs can be moved
to the surrounding cells for services continuity. And the outage cell will be added into the
blacklist to prevent handover/reselection from neighbor cells. The priority for handover
triggering is defined by the mobility features to keep the service continuity.
Cell outage recovery:

eRAN
After cell outage detected, the system will recover the cell.
After outage recovery, the system will reverse the compensation.
Enhancement
In eRAN3.0
Cell outage is detected mainly based on alarms and abnormal key performance indicators
(KPIs). Checking KPIs takes about two measurement periods. Therefore, the time
required to detect a cell outage depends on the measurement periods.
In eRAN6.0
Introduce assisted cell outage detection by checking internal eNodeB counters and
reporting abnormal audit results. This enhancement helps to quickly and accurately
detect cell outages.
In eRAN7.0
KPI accumulation is introduced for low traffic cell outage detection. When the KPIs
number of one period is lower than the configured threshold, it will be accumulated to
the next period till accumulated KPIs is more than the threshold, and then the system will
calculate abnormal KPIs in accumulated periods to detect cell outage.
In CODC SON Log, it will register the key KPIs information of Cell outage detection
and Cell outage recovery for operator observation and analysis.
Customized KPI is introduced for cell outage detection. users can customize the
observed KPI and detection rules as abnormal judgment rule and recovery condition.
Frequency of abnormal KPI occurrence is also introduced for judgment condition.
RRU failure detection is introduced, if eNodeB found RRU has unavailable fault (eg: RF
channel failures, link failure), it will reported to U2000, and CODC GUI will present the
RRU failure information. Which can help detect the abnormal RRU in SFN scenario.
Dependency
OSS
This feature depends on OSS feature WOFD-171000 Cell Outage Detection and
Recovery -LTE.
Other features
LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN or
LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000
4.4 Power Saving

4.4.1 LOFD-001025 Adaptive Power Consumption
Availability
This feature is
Applicable to LampSite from eRAN8.1.

eRAN
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.
4.4.2 LOFD-001039 RF Channel Intelligent Shutdown

Availability
This feature is

eRAN

Not applicable to LampSite.
Summary
The RF Channel Intelligent Shutdown feature shuts down some transmit (TX) channels in a
cell when there is no traffic in the cell or traffic in the cell is light during a specified period.
This therefore reduces energy consumption. In addition, after some TX channels are shut
down, the eNodeB increases the transmit power of reference signals, thereby ensuring wide
network coverage.
Benefits
This feature reduces eNodeB energy consumption by shutting down some TX channels on
no-load or lightly-loaded radio frequency (RF) modules.
Description
An eNodeB is generally configured with two or four antennas. Traffic in a cell varies by time.
In certain periods, for example, from the midnight to the early morning (operators can
customize the periods), traffic is light, which reaches the feature activation threshold. If there
are no UEs whose QoS class identifier (QCI) is 1 during the periods, the eNodeB shuts down
one TX channel (if two TX channels are configured) or shuts down two TX channels (if four
TX channels are configured) to decrease the energy consumption of RF modules.
When traffic reaches the feature deactivation threshold; UEs whose QCI is 1 access a cell; or
when the preceding periods end, the eNodeB automatically switches on the TX channels that
were shut down. Then, the cell recovers and continues to provide services.
Enhancement
eRAN8.1
This feature incorporates the following enhancements for Macro:
Optimizes the feature activation threshold so that the feature can take effect when
traffic is light.
Supports identifying service type to prevent the feature from taking effect when there
are UEs whose QCI is 1.
Dependency
eNodeB
The target cell is configured with two or four antennas.
eCO
None
UE
None
Transport network
None
CN

eRAN
None
OSS
This feature requires OSS feature WOFD-200200 Base Station Power-Saving
Management -LTE.
Other features
This feature requires LOFD-001001 DL 2x2 MIMO or LOFD-001003 DL 4x2 MIMO.
Others
Cell bandwidth is 10 MHz or more.
To support feature enhancement in eRAN8.1, cell bandwidth must be 20 MHz or more.
4.4.3 LOFD-001040 Low Power Consumption Mode

Availability
This feature is
Summary
In some cases where an eNodeB detects a power outage or receives a command, the eNodeB
can opt to or be forced to enter low power consumption mode, which helps extend the
in-service time of an eNodeB 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.

eRAN
Enhancement
None
The eRAN6.0 enhancement to this feature supports power conversion modules manufactured
by other vendors. If an eNodeB is equipped with such a power conversion module, this
module sends a Boolean signal to the eNodeB when detecting an abnormal power supply
status, notifying the eNodeB that the condition for triggering the power outage alarm is met.
Then, the eNodeB enters low power consumption mode.
Corresponding to this enhancement, a parameter is added for the RAT-specific power backup
and energy saving policy. Based on the parameter settings, a multi-mode base station uses a
specific set of duration thresholds for each RAT. Here RAT stands for radio access technology.
Dependency
eNodeB
This feature is only applicable to Macro eNodeB configured with Battery
OSS
Management -LTE.
4.4.4 LOFD-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.

eRAN
Enhancement
None
Dependency
OSS
Management -LTE.
4.4.5 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
unblocked again automatically 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 taken over by the carriers that remain in service. This
can help 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
None
Dependency
OSS

eRAN

Management -LTE.
Others
This feature should not work to a cell simultaneously with feature LOFD-001074
Intelligent Power-Off of Carrier in the Same Coverage of UMTS Network.
4.4.6 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.

eRAN
4.4.7 LOFD-001070 Symbol Power Saving

Availability
This feature is
Summary
This feature introduces the function of symbol power saving. The eNodeB can shut down the
PAs (Power Amplifier) when a symbol is empty. MBSFN (Multicast Broadcast Single
Frequency Network) sub-frame could be used to reduce the reference signal further so that
more empty symbols are available for PA to shut down longer.
Benefits
When the traffic is light, the eNodeB can shut down the PAs when symbol is 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 eNodeB. Even when there is no signal output, the PA has
static power consumption. If PA could be power on and off quickly, the system could utilize
this function to implement symbol power saving.
The eNodeB can shut down the PAs when symbol is empty to save the static power
consumption of the PA. In order to guarantee the integrity of data, the system needs to control
the time of PA's switching on and off.
For example: when there is no active user in the cell, in some sub-frames only RS (Reference
Signal) signal is transmitted, PA can be powered off in the OFDM symbols when there is no
RS.
And if the cell is not using eMBMS service, the eNodeB can configure some of the empty
sub-frames into MBSFN sub-frames for further power saving. When one sub-frame is
configured as MBSFN sub-frame, only the first RS need to be transmitted in the air interface.
The rest symbols in the sub-frame could be set to empty so that the PA could be powered off.
Figure 4-5 Symbol power saving (Normal CP)

eRAN
Figure 4-6 Symbol power saving with MBSFN subframe (extended CP)
Enhancement
None
Dependency
eNodeB
This feature is only supported by the following LTE RF modules: LRFUe(800MHz),
RRU3221(2600MHz), RRU3240(2600MHz) and multi-mode RF modules:
mRFUd(1800MHz,900MHz),RRU3928(1800MHz,900MHz),RRU3929(1800MHz,900
MHz),RRU3841(AWS) working on LTE-only configuration.
Others
MBSFN sub-frame configuration need that UE can identify and apply the
serving/neighbor cell's MBSFN sub-frame configuration related.
4.4.8 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.

eRAN
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 4-1 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%
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)

eRAN
Enhancement
None
Dependency
eNodeB
The APM30H (Ver. C), BTS3900AL, TP48600A, and batteries must be configured.
4.4.9 LOFD-001074 Intelligent Power-Off of Carriers in the Same

Coverage of UMTS Network
Availability
This feature is
Not applicable to Micro.
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

eRAN

Management -LTE.
Other features
UTRAN.
Others
This feature should not work to a cell simultaneously with feature LOFD-001042
Intelligent Power-Off of Carriers in the Same Coverage.
4.4.10 LOFD-001075 RRU PA Efficiency Improvement

Availability
This feature is
Summary
This feature monitors the eNodeB transmitting power, and dynamically adjusts PA working
state when RRU transmitting power is low. Thereby it improves PA efficiency and saves
eNodeB power consumption.
This is similar to feature LOFD-001025 Adaptive Power Consumption, but it is specific to the
Blade RRU series which has utilized the new PA technologies. This feature provides more
power saving and can also be used at narrow frequency bandwidth (1.4MHz, 3MHz and
5MHz).
Benefits
This feature improves the efficiency of the PA and saves power consumption of the eNodeB.
Description
By decreasing equipment power consumption, operator's operating cost is decreased. The
lower power consumption also improves the reliability of equipment.
Blade RRU series utilized the latest PA technologies. When RRU transmitting power is low,
this feature will dynamically adjust the bias voltage of RRU, to improve the PA efficiency of
this kind of RRU.
PA Bias Voltage Dynamically Adjustment
In the commercial network, eNodeB traffic load is keep changing; PA transmitting power
is also changing with it. When PA transmitting power is high, PA efficiency is higher and
a higher PA bias voltage is needed. When PA transmitting power is low, if PA bias
voltage keeps high, the PA efficiency will be low.
This feature keeps monitoring the eNodeB traffic load. Based on the real time traffic load,
by decreasing the PA bias voltage PA efficiency is increased.

eRAN
This feature is specific to the Blade RRU series. Comparing to LOFD-001025 Adaptive
Power Consumption, this feature provides more power saving and can also be used at narrow
frequency bandwidth (1.4MHz, 3MHz and 5MHz).
This feature cannot be used with LOFD-001025 Adaptive Power Consumption at same time.
eNodeB will only enable this feature when the RRU type is Blade RRU series.
Enhancement
None
Dependency
eNodeB
This feature is only supported by following RF module: RRU3268(2600MHz).
4.5 Antenna Management

4.5.1 LOFD-001024 Remote Electrical Tilt Control
Availability
This feature is
Summary
Remote Electrical Tilt Control improves the efficiency and minimizes the OM cost for
adjusting the down tilt of the antenna. Huawei LTE RET solution complies with the AISG2.0
specification, and it is backward compatible with AISG1.1.
Benefits
The application of the RET prominently improves the efficiency and minimizes the OM cost
for adjusting the down tilt of the antenna. The application of the RET 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, therefore
strengthening the antenna signal and reducing neighboring cell interference.
Description
The Remote Electrical Tilt (RET) refers to an antenna system whose down tilt is controlled
electrically and remotely.

eRAN
After an antenna is installed, the down tilt 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 the electrical control. Then, the vertical pattern of the antenna can be
changed.
The phase shifter inside the antenna can be adjusted through the step motor outside the
antenna. The down tilt of the RET antenna can be adjusted when the system is powered on,
and the down tilt can be monitored in real time. Thus, the remote precise adjustment of the
down tilt of the antenna can be achieved.
Huawei LTE RET solution complies with the AISG2.0 specification, and it is compatible with
AISG1.1.
Enhancement
None
Dependency
None

eRAN
Optional Feature Description 5 Acronyms and Abbreviations
5 Acronyms and Abbreviations
Table 5-1 Acronyms and Abbreviations
3GPP Third Generation Partnership Project
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
BCH Broadcast Channel
BCCH Broadcast Control Channel
BITS Building Integrated Timing Supply System
BLER Block Error Rate
CA Carrier aggregation
C/I Carrier-to-Interference Power Ratio
CCCH Common Control Channel

eRAN
CDMA Code Division Multiple Access
CEU Cell Edge Users
CGI Cell Global Identification
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
DCCH Dedicated Control Channel
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
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

eRAN
ESP Encapsulation Security Payload
ETWS Earthquake and Tsunami Warning System
E-UTRA Evolved Universal Terrestrial Radio

Access
FCPSS Fault, Configuration, Performance, Security

and Software Managements
FDD Frequency Division Duplex
FEC Forward Error Correction
FTP File Transfer Protocol
GBR Guaranteed Bit Rate
GERAN GSM/EDGE Radio Access Network
GPS Global Positioning System
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
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
KPI Key Performance Indicator

eRAN
CME Configuration Management Express
LMT Local Maintenance Terminal
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
NACC Network Assisted Cell Changed
NACK Non acknowledgment
NAS Non-Access Stratum
NRT Neighboring Relation Table
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
PBCH Physical Broadcast Channel

eRAN
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
QAM Quadrature Amplitude Modulation
QCI QoS Class Identifier
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
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

eRAN
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
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

eRAN
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
UE User Equipment
UL-SCH Uplink Shared Channel
USB Universal Serial Bus
U2000 Huawei OMC
VLAN Virtual Local Area Network
VoIP Voice over IP
WRR Weighted Round Robin
X2 interface among eNodeBs


LTE FDD eRAN8.1 Optional Feature Description PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

LTE FDD eRAN8.1 Optional Feature Description PDF

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

1 Voice & Other Services ................................................................................................................ 1

Issue 01 (2015-01-15) Huawei Proprietary and Confidential ii

1.8.1 LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture ............................................................. 34

2 Radio & Performance ................................................................................................................. 42

Issue 01 (2015-01-15) Huawei Proprietary and Confidential iii

2.7.3 LOFD-001027 Active Queue Management (AQM) ................................................................................................ 79

3 Networking & Transmission & Security .............................................................................. 118

Issue 01 (2015-01-15) Huawei Proprietary and Confidential iv

3.1.1 LOFD-003002 2G/3G and LTE Co-transmission .................................................................................................. 118

Issue 01 (2015-01-15) Huawei Proprietary and Confidential v

3.4.6 LOFD-003008 Ethernet Link Aggregation (IEEE 802.3ad) .................................................................................. 160

4 O&M ............................................................................................................................................ 194

Issue 01 (2015-01-15) Huawei Proprietary and Confidential vi

5 Acronyms and Abbreviations ................................................................................................. 238

Issue 01 (2015-01-15) Huawei Proprietary and Confidential vii

1 Voice & Other Services

1.1 VoLTE Capacity & Coverage

1.1 VoLTE Capacity & Coverage

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 1

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 2

1.1.2 LOFD-001017 RObust Header Compression (ROHC)

Table 1-1 ROHC profile identifier and header compression protocol

Profile Identifier Usage:

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 3

Profile Identifier Usage:

1.1.3 LOFD-001048 TTI Bundling

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 4

1.1.4 LOFD-081229 Voice Characteristic Awareness Scheduling

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 5

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 6

1.2 SRVCC to UTRAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 7

Figure 1-1 SRVCC from E-UTRAN to UTRAN

1.2.2 LOFD-001087 SRVCC Flexible Steering to UTRAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 8

SRVCC to UTRAN for an LCS required VoIP services

1.3 SRVCC to GERAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 9

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 10

Figure 1-2 SRVCC from E-UTRAN to GERAN

1.4 CSFB to UTRAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 11

Figure 1-3 CS fallback in EPS architecture

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 12

1.4.2 LOFD-070202 Ultra-Flash CSFB to UTRAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 13

Figure 1-4 Working principle of CSFB based on SRVCC

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 14

1.4.3 LOFD-001052 Flash CS Fallback to UTRAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 15

1.4.4 LOFD-001068 CS Fallback with LAI to UTRAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 16

1.4.5 LOFD-001088 CS Fallback Steering to UTRAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 17

1.5 CSFB to GERAN

Issue 01 (2015-01-15) Huawei Proprietary and Confidential 18

Figure 1-5 CS fallback in EPS architecture

1.5.2 LOFD-001053 Flash CS Fallback to GERAN