Appendix8 LTETDDeRAN6.0FeatureDescriptionDraftB

LTE TDD eRAN6.
0
V100R006C00
Feature Description
Issue Draft B
Date 2013-1-7
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Copyright © Huawei Technologies Co., Ltd.
LTE TDD eRAN6.0
Feature Description About This Document
About This Document
Change History
Issue Date Description
Draft B 2013-01-07 1. Add TDLOFD-001016 VoIP Semi-persistent Scheduling Dependencies:

This feature cannot coexist with following features:
a) TDLOFD-001007 High Speed Mobility
b) TDLOFD-001008 Ultra High Speed Mobility
2. Add TDLOFD-001049 Single Streaming Beamforming Dependencies:
3. Add TDLOFD-001049 Single Streaming Beamforming Dependencies:
4. Add TDLOFD-001077 MU-Beamforming Dependencies:
5. Add TDLOFD-001007 High Speed Mobility Dependencies:
a) TDLOFD-001016 VoIP Semi-persistent Scheduling
b) TDLOFD-001049 Single Streaming Beamforming
c) TDLOFD-001061 Dual Streaming Beamforming
d) TDLOFD-001077 MU-Beamforming
6. Add TDLOFD-001008 Ultra High Speed Mobility Dependencies:
Issue 01 (2012-11-15) Huawei Proprietary and Confidential ii

LTE TDD eRAN6.0
2013-01-05 1. Enhance TDLOFD-001007 High Speed Mobility to support 4T4R mode

2. Enhance TDLOFD-001008 Ultra High Speed Mobility to support 4T4R mode
3. Remove TDLOFD-001016 VoIP Semi-persistent Scheduling Dependencies:
TDLOFD-001008 Ultra High Speed Mobility
4. Remove TDLOFD-001058 UL 2x4 MU-MIMO Dependencies:
b) TDLOFD-001048 TTI Bundling
5. Remove TDLOFD-001007 High Speed Mobility Dependencies:
b) TDLOFD-001076 CPRI Compression
c) TDLOFD-001049 Single Streaming Beamforming
d) TDLOFD-001061 Dual Streaming Beamforming
e) TDLOFD-001077 MU-Beamforming
6. Remove TDLOFD-001008 Ultra High Speed Mobility Dependencies:
7. Add TDLOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT Dependencies:
a) TDLOFD-001088 CS Fallback Steering to UTRAN
b) TDLOFD-001089 CS Fallback Steering to GERAN
8. Add TDLOFD-001039 RF Channel Intelligent Shutdown Dependencies:
a) TDLOFD-001075 SFN
b) TDLOFD-002008 Adaptive SFN/SDMA
c) TDLOFD-001098 Inter-BBP SFN
d) TDLOFD-001080 Inter-BBU SFN
e) TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
f) TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
9. Add TDLOFD-001031 Extended CP Dependencies:
a) TDLOFD-001076 CPRI Compression
2012-12-24 1. Enhance TDLOFD-001033 CS Fallback to UTRAN to support Blind handover

2. Enhance TDLOFD-001034 CS Fallback to GERAN to support Blind handover
3. Add TDLOFD-001034 CS Fallback to GERAN Dependencies:
a) TDLOFD-001035 CS Fallback to CDMA2000 1xRTT
b) TDLOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT
Issue 01 (2012-11-15) Huawei Proprietary and Confidential iii

LTE TDD eRAN6.0
4. Modify TDLOFD-001035 CS Fallback to CDMA2000 1xRTT Dependencies:

a) TDLOFD-001033 CS Fallback to UTRAN
b) TDLOFD-001034 CS Fallback to GERAN
c) TDLOFD-001052 Flash CS Fallback to UTRAN
d) TDLOFD-001053 Flash CS Fallback to GERAN
e) TDLOFD-001068 CS Fallback with LAI to UTRAN
f) TDLOFD-001069 CS Fallback with LAI to GERAN
g) TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering
h) TDLOFD-001088 CS Fallback Steering to UTRAN
i) TDLOFD-001089 CS Fallback Steering to GERAN
5. Add TDLOFD-001052 Flash CS Fallback to UTRAN Dependencies:
6. Add TDLOFD-001053 Flash CS Fallback to GERAN Dependencies:
7. Remove TDLOFD-001066 Intra-eNodeB UL CoMP Dependencies:
a) TDLOFD-001008 Ultra High Speed Mobility
8. Add TDLOFD-001016 VoIP Semi-persistent Scheduling Dependencies:
a) TDLOFD-001058 UL 2x4 MU-MIMO
9. Add TDLOFD-001048 TTI Bundling Dependencies:
a) TDLOFD-001058 UL 2x4 MU-MIMO
Draft A 2012-12-10 This issue is a draft.
Issue 01 (2012-11-15) Huawei Proprietary and Confidential iv

LTE TDD eRAN6.0
Feature Description Contents
Contents
About This Document .................................................................................................................... ii

1 Basic Features ................................................................................................................................. 1
1.1 TDLBFD-001001 3GPP R8 Specifications ...................................................................................................... 1
1.2 TDLBFD-001008 3GPP R9 Specifications ...................................................................................................... 2
1.3 TDLBFD-001009 3GPP R10 Specifications .................................................................................................... 2
1.4 TDLBFD-001002 TDD mode .......................................................................................................................... 3
1.5 TDLBFD-001003 Scalable Bandwidth ............................................................................................................ 3
1.6 TDLBFD-001004 CP length ............................................................................................................................ 5
1.6.1 TDLBFD-00100401 Normal CP ............................................................................................................. 5
1.7 TDLBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM ................................................ 6
1.8 TDLBFD-001006 AMC ................................................................................................................................... 7
1.9 TDLBFD-001007 Basic uplink-downlink subframe configuration.................................................................. 8
1.9.1 TDLBFD-00100701 uplink-downlink subframe configuration type1&2 ............................................... 8
1.9.2 TDLBFD-00100702 uplink-downlink special subframe configuration type 7 ....................................... 9
1.10 TDLBFD-002001 Logical Channel Management ........................................................................................ 10
1.11 TDLBFD-002002 Transport Channel Management ..................................................................................... 11
1.12 TDLBFD-002003 Physical Channel Management ....................................................................................... 11
1.13 TDLBFD-002004 Integrity Protection ......................................................................................................... 12
1.14 TDLBFD-002005 DL Asynchronous HARQ ............................................................................................... 13
1.15 TDLBFD-002006 UL Synchronous HARQ ................................................................................................. 14
1.16 TDLBFD-002007 RRC Connection Management ....................................................................................... 15
1.17 TDLBFD-002008 Radio Bearer Management ............................................................................................. 16
1.18 TDLBFD-002009 Broadcast of System Information ................................................................................... 17
1.19 TDLBFD-002010 Random Access Procedure ............................................................................................. 18
1.20 TDLBFD-002011 Paging ............................................................................................................................. 19
1.21 TDLBFD-002012 Cell Access Radius up to 15km ...................................................................................... 20
1.22 TDLBFD-002023 Admission Control .......................................................................................................... 21
1.23 TDLBFD-002024 Congestion Control ......................................................................................................... 22
1.24 TDLBFD-002025 Basic Scheduling ............................................................................................................ 23
1.25 TDLBFD-002026 Uplink Power Control ..................................................................................................... 23
1.26 TDLBFD-002016 Dynamic Downlink Power Allocation ............................................................................ 25
1.27 TDLBFD-002017 DRX ................................................................................................................................ 26
Issue 01 (2012-11-15) Huawei Proprietary and Confidential v

LTE TDD eRAN6.0
1.28 TDLBFD-002018 Mobility Management .................................................................................................... 27

1.28.1 TDLBFD-00201801 Coverage Based Intra-frequency Handover....................................................... 27
1.28.2 TDLBFD-00201802 Coverage Based Inter-frequency Handover ....................................................... 28
1.28.3 TDLBFD-00201803 Cell Selection and Reselection .......................................................................... 29
1.28.4 TDLBFD-00201804 Distance Based Inter-frequency Handover ........................................................ 30
1.28.5 TDLBFD-00201806 Multi-Band Compatibility Enhancement ........................................................... 31
1.29 TDLBFD-002022 Static Inter-Cell Interference Coordination..................................................................... 32
1.29.1 TDLBFD-00202201 Downlink Static Inter-Cell Interference Coordination ...................................... 32
1.29.2 TDLBFD-00202202 Uplink Static Inter-Cell Interference Coordination ........................................... 33
1.30 TDLBFD-002020 Antenna Configuration.................................................................................................... 34
1.30.1 TDLBFD-00202001 UL 2-Antenna Receive Diversity ...................................................................... 34
1.31 TDLBFD-002021 Reliability ....................................................................................................................... 35
1.31.1 TDLBFD-00202102 Cell Rebuild between Baseband Processing Units ............................................ 35
1.31.2 TDLBFD-00202103 SCTP Multi-homing .......................................................................................... 36
1.31.3 TDLBFD-00202104 Intra-baseband Card Resource Pool(user level/cell level) ................................. 37
1.32 TDLBFD-002027 Support of UE Category 1 .............................................................................................. 38
1.33 TDLBFD-002028 Emergency Call .............................................................................................................. 39
1.34 TDLBFD-002029 Earthquake and Tsunami Warning System (ETWS) ....................................................... 41
1.35 TDLBFD-002031 Support of aperiodic CQI reports.................................................................................... 42
1.36 TDLBFD-002033 SCTP Congestion Control .............................................................................................. 43
1.37 TDLBFD-002035 Multi Carrier ................................................................................................................... 44
1.38 TDLBFD-003001 Transmission Networking ............................................................................................... 45
1.38.1 TDLBFD-00300101 Star Topology .................................................................................................... 45
1.38.2 TDLBFD-00300102 Chain Topology ................................................................................................. 46
1.38.3 TDLBFD-00300103 Tree Topology .................................................................................................... 46
1.39 TDLBFD-003006 IPv4/IPv6 Dual Stack ..................................................................................................... 47
1.40 TDLBFD-003002 Basic QoS Management ................................................................................................. 48
1.40.1 TDLBFD-00300201 DiffServ QoS Support ....................................................................................... 48
1.41 TDLBFD-003003 VLAN Support (IEEE 802.1p/q) .................................................................................... 50
1.42 TDLBFD-003004 Compression and Multiplexing over E1/T1 .................................................................... 51
1.42.1 TDLBFD-00300401 IP Header Compression ..................................................................................... 51
1.42.2 TDLBFD-00300402 PPP MUX .......................................................................................................... 51
1.42.3 TDLBFD-00300403 ML-PPP/MC-PPP .............................................................................................. 52
1.43 TDLBFD-003005 Synchronization .............................................................................................................. 53
1.43.1 TDLBFD-00300501 Clock Source Switching Manually or Automatically ........................................ 53
1.43.2 TDLBFD-00300502 Free-running Mode ............................................................................................ 54
1.43.3 TDLBFD-00300503 Synchronization with GPS ................................................................................ 55
1.43.4 TDLBFD-00300505 Synchronization with 1PPS+TOD ..................................................................... 55
1.44 TDLBFD-004001 Local Maintenance on the LMT ..................................................................................... 56
1.45 TDLBFD-004002 Centralized M2000 Management.................................................................................... 57
1.46 TDLBFD-004003 Security Socket Layer ..................................................................................................... 58
1.47 TDLBFD-004004 Software Version Upgrade Management ........................................................................ 58
Issue 01 (2012-11-15) Huawei Proprietary and Confidential vi

LTE TDD eRAN6.0
1.48 TDLBFD-004005 Hot Patch Management................................................................................................... 60

1.49 TDLBFD-004006 Fault Management .......................................................................................................... 60
1.50 TDLBFD-004007 Configuration Management ............................................................................................ 62
1.51 TDLBFD-004008 Performance Management .............................................................................................. 63
1.52 TDLBFD-004009 Real-time Monitoring of System Running Information .................................................. 64
1.53 TDLBFD-004010 Security Management ..................................................................................................... 65
1.54 TDLBFD-004011 Optimized eNodeB Commissioning Solution ................................................................. 65
1.55 TDLBFD-004012 Environment Monitoring ................................................................................................ 66
1.56 TDLBFD-004013 Inventory Management ................................................................................................... 67
1.57 TDLBFD-004014 License Management ...................................................................................................... 68
1.58 TDLBFD-004015 License Control for Urgency .......................................................................................... 69
2 Optional Features ........................................................................................................................ 70

2.1 TDLOFD-001016 VoIP Semi-persistent Scheduling...................................................................................... 70
2.2 TDLOFD-001017 RObust Header Compression (ROHC) ............................................................................. 71
2.3 TDLOFD-001048 TTI Bundling .................................................................................................................... 72
2.4 TDLOFD-001022 SRVCC to UTRAN .......................................................................................................... 73
2.5 TDLOFD-001023 SRVCC to GERAN .......................................................................................................... 75
2.6 TDLOFD-001033 CS Fallback to UTRAN.................................................................................................... 76
2.7 TDLOFD-001034 CS Fallback to GERAN.................................................................................................... 78
2.8 TDLOFD-001035 CS Fallback to CDMA2000 1xRTT ................................................................................. 80
2.9 TDLOFD-001052 Flash CS Fallback to UTRAN .......................................................................................... 82
2.10 TDLOFD-001053 Flash CS Fallback to GERAN ........................................................................................ 83
2.11 TDLOFD-001068 CS Fallback with LAI to UTRAN .................................................................................. 84
2.12 TDLOFD-001069 CS Fallback with LAI to GERAN .................................................................................. 85
2.13 TDLOFD-001088 CS Fallback Steering to UTRAN ................................................................................... 86
2.14 TDLOFD-001089 CS Fallback Steering to GERAN ................................................................................... 87
2.15 TDLOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT............................................................... 88
2.16 TDLOFD-001047 LoCation Services(LCS) ................................................................................................ 91
2.17 TDLOFD-001001 DL 2x2 MIMO ............................................................................................................... 92
2.18 TDLOFD-001030 Support of UE Category 2/3/4 ........................................................................................ 93
2.19 TDLOFD-001005 UL 4-Antenna Receive Diversity ................................................................................... 94
2.20 TDLOFD-001058 UL 2x4 MU-MIMO ........................................................................................................ 95
2.21 TDLOFD-001006 UL 64QAM .................................................................................................................... 96
2.22 TDLOFD-001012 UL Interference Rejection Combining ........................................................................... 97
2.23 TDLOFD-001094 Control Channel IRC ...................................................................................................... 97
2.24 TDLOFD-001049 Single Streaming Beamforming ..................................................................................... 98
2.25 TDLOFD-001061 Dual Streaming Beamforming ........................................................................................ 99
2.26 TDLOFD-001075 SFN............................................................................................................................... 100
2.27 TDLOFD-002008 Adaptive SFN/SDMA ................................................................................................... 102
2.28 TDLOFD-001098 Inter-BBP SFN ............................................................................................................. 103
2.29 TDLOFD-001080 Inter-BBU SFN ............................................................................................................. 104
Issue 01 (2012-11-15) Huawei Proprietary and Confidential vii

LTE TDD eRAN6.0
2.30 TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA.................................................................................. 105

2.31 TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA ................................................................................. 106
2.32 TDLOFD-001077 Multi-User Beamforming ............................................................................................. 107
2.33 TDLOFD-001066 Intra-eNodeB UL CoMP .............................................................................................. 108
2.34 TDLOFD-001132 Intra-BBU Baseband Sharing (2T) ............................................................................... 109
2.35 TDLOFD-001062 UL 8-Antenna Receive Diversity ................................................................................. 111
2.36 TDLOFD-001028 TCP Proxy Enhancer (TPE).......................................................................................... 112
2.37 TDLOFD-001054 Flexible User Steering .................................................................................................. 113
2.37.1 TDLOFD-00105401 Camp & Handover Based on SPID ................................................................. 113
2.38 TDLOFD-001059 UL Pre-allocation Based on SPID ................................................................................ 114
2.39 TDLOFD-001133 Multi Operators SPID Policy ........................................................................................ 115
2.40 TDLOFD-001105 Dynamic DRX .............................................................................................................. 116
2.41 TDLOFD-001106 High-Mobility-Triggered Idle Mode............................................................................. 117
2.42 TDLOFD-001015 Enhanced Scheduling ................................................................................................... 118
2.42.1 TDLOFD-00101501 CQI Adjustment .............................................................................................. 118
2.42.2 TDLOFD-00101502 Dynamic Scheduling ....................................................................................... 119
2.43 TDLOFD-001109 DL Non-GBR Packet Bundling .................................................................................... 120
2.44 TDLOFD-001027 Active Queue Management (AQM) ............................................................................. 120
2.45 TDLOFD-001029 Enhanced Admission Control ....................................................................................... 121
2.45.1 TDLOFD-00102901 Radio/transport Resource Pre-emption............................................................ 121
2.46 TDLOFD-001007 High Speed Mobility .................................................................................................... 123
2.47 TDLOFD-001008 Ultra High Speed Mobility ........................................................................................... 124
2.48 TDLOFD-001031 Extended CP ................................................................................................................. 125
2.49 TDLOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN ........................................... 126
2.50 TDLOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN ........................................... 128
2.51 TDLOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000 ..................................... 131
2.52 TDLOFD-001050 Mobility between LTE TDD and LTE FDD ................................................................. 132
2.53 TDLOFD-001032 Intra-LTE Load Balancing ............................................................................................ 133
2.54 TDLOFD-001044 Inter-RAT Load Sharing to UTRAN ............................................................................ 134
2.55 TDLOFD-001045 Inter-RAT Load Sharing to GERAN ............................................................................ 135
2.56 TDLOFD-001043 Service based Inter-RAT handover to UTRAN ............................................................ 136
2.57 TDLOFD-001046 Service based Inter-RAT handover to GERAN ............................................................ 136
2.58 TDLOFD-001072 Distance based Inter-RAT handover to UTRAN .......................................................... 137
2.59 TDLOFD-001073 Distance based Inter-RAT handover to GERAN .......................................................... 138
2.60 TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering ........................................................................ 139
2.61 TDLOFD-001026 Optional uplink-downlink subframe configuration ...................................................... 140
2.61.1 TDLOFD-00102601 uplink-downlink subframe configuration type 0 ............................................. 140
2.61.2 TDLOFD-00102602 uplink-downlink special subframe configuration type 4 ................................. 141
2.61.3 TDLOFD-00102603 uplink-downlink special subframe configuration type 5 ................................. 142
2.62 TDLOFD-001076 CPRI Compression ....................................................................................................... 143
2.63 TDLOFD-002001 Automatic Neighbour Relation (ANR) ......................................................................... 143
2.64 TDLOFD-002002 Inter-RAT ANR ............................................................................................................ 146
Issue 01 (2012-11-15) Huawei Proprietary and Confidential viii

LTE TDD eRAN6.0
2.65 TDLOFD-002004 Self-configuration ......................................................................................................... 148

2.66 TDLOFD-002007 PCI Collision Detection & Self-Optimization .............................................................. 151
2.67 TDLOFD-001024 Remote Electrical Tilt Control...................................................................................... 152
2.68 TDLOFD-002005 Mobility Robust Optimization (MRO) ......................................................................... 153
2.69 TDLOFD-002015 RACH Optimization ..................................................................................................... 154
2.70 TDLOFD-002011 Antenna Fault Detection ............................................................................................... 155
2.71 TDLOFD-002012 Cell Outage Detection and Compensation .................................................................... 156
2.72 TDLOFD-003002 2G/3G and LTE Co-transmission ................................................................................. 157
2.73 TDLOFD-003004 Ethernet OAM .............................................................................................................. 158
2.73.1 TDLOFD-00300401 Ethernet OAM_(IEEE 802.3ah) ...................................................................... 158
2.73.2 TDLOFD-00300403 Ethernet OAM (Y.1731) .................................................................................. 159
2.74 TDLOFD-003007 Bidirectional Forwarding Detection ............................................................................. 160
2.75 TDLOFD-003011 Enhanced Transmission QoS Management .................................................................. 161
2.75.1 TDLOFD-00301101 Transport Overbooking .................................................................................... 161
2.75.2 TDLOFD-00301102 Transport Differentiated Flow Control ............................................................ 162
2.75.3 TDLOFD-00301103 Transport Resource Overload Control ............................................................. 163
2.76 TDLOFD-003012 IP Performance Monitoring .......................................................................................... 164
2.76.1 TDLOFD-00301201 IP Performance Monitoring ............................................................................. 164
2.76.2 TDLOFD-00301202 Transport Dynamic Flow Control .................................................................... 165
2.77 TDLOFD-003016 Different Transport Paths based on QoS Grade ............................................................ 166
2.78 TDLOFD-003013 Enhanced Synchronization ........................................................................................... 167
2.78.1 TDLOFD-00301302 IEEE1588 V2 Clock Synchronization ............................................................. 167
2.79 TDLOFD-001134 Virtual Routing & Forwarding ...................................................................................... 169
2.80 TDLOFD-001018 S1-flex .......................................................................................................................... 170
2.81 TDLOFD-001036 RAN Sharing with Common Carrier ............................................................................ 171
2.82 TDLOFD-001037 RAN Sharing with Dedicated Carrier ........................................................................... 173
2.83 TDLOFD-001086 RAN Sharing by More Operators ................................................................................. 175
2.84 TDLOFD-003017 S1 and X2 over IPv6 .................................................................................................... 176
2.85 TDLOFD-003024 IPsec for IPv6 ............................................................................................................... 177
2.86 TDLOFD-003005 OM Channel Backup .................................................................................................... 178
2.87 TDLOFD-003006 IP Route Backup ........................................................................................................... 179
2.88 TDLOFD-003008 Ethernet Link Aggregation (IEEE 802.3ad) ................................................................. 179
2.89 TDLOFD-003019 IPsec Tunnel Backup .................................................................................................... 180
2.90 TDLOFD-001010 Security Mechanism ..................................................................................................... 181
2.90.1 TDLOFD-00101001 Encryption: AES .............................................................................................. 181
2.90.2 TDLOFD-00101002 Encryption: SNOW 3G ................................................................................... 182
2.91 TDLOFD-00101003 Encryption: ZUC ...................................................................................................... 183
2.92 TDLOFD-003009 IPsec ............................................................................................................................. 184
2.93 TDLOFD-003010 Public Key Infrastructure (PKI) ................................................................................... 185
2.94 TDLOFD-003015 Access Control based on 802.1x ................................................................................... 186
2.95 TDLOFD-003014 Integrated Firewall........................................................................................................ 187
2.95.1 TDLOFD-00301401 Access Control List (ACL) .............................................................................. 187
Issue 01 (2012-11-15) Huawei Proprietary and Confidential ix

LTE TDD eRAN6.0
2.96 TDLOFD-001039 RF Channel Intelligent Shutdown ................................................................................ 188

2.97 TDLOFD-001040 Low Power Consumption Mode ................................................................................... 189
2.98 TDLOFD-001041 Power Consumption Monitoring .................................................................................. 190
2.99 TDLOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage.............................................. 191
2.100 TDLOFD-001056 PSU Intelligent Sleep Mode ....................................................................................... 192
2.101 TDLOFD-001070 Symbol Power Saving ................................................................................................ 193
2.102 TDLOFD-001071 Intelligent Battery Management ................................................................................. 194
3 Acronyms and Abbreviations ................................................................................................. 196
Issue 01 (2012-11-15) Huawei Proprietary and Confidential x

LTE TDD eRAN6.0
Feature Description 1 Basic Features
1 Basic Features
1.1 TDLBFD-001001 3GPP R8 Specifications

Availability
This feature was introduced in LTE TDD eRAN2.0.
Summary
Huawei LTE TDD eRAN2.0 is based on 3GPP Release 8 specifications (2009-03).
Benefits
In complying with the 3GPP Release 8 specifications (2009-03), Huawei LTE TDD eRAN2.0
can provide users with richer and more high-performance services to improve the operator's
competitiveness.
Description
Huawei LTE TDD eRAN2.0 is compliant with 3GPP Release 8 specifications (2009-03).
Huawei is an active participant in the specification development in 3GPP and makes great
contributions. This high-level involvement enables Huawei to actively contribute to and closely
follow the 3GPP development during Huawei product development. LTE TDD eRAN2.0 is
based on 3GPP Release 8 in March 2009, which is the latest version of the LTE standard.
Enhancement
None
Dependencies
None
Issue 01 (2012-11-15) Huawei Proprietary and Confidential 1

LTE TDD eRAN6.0

Availability
Summary
Huawei LTE TDD eNodeB is based on 3GPP Release 9 specifications (2010-09).
Benefits
None
Description
Huawei LTE TDD eNodeB is compliant with 3GPP Release 9 specifications (2010-09).
Huawei is an active participant and great contributor to 3GPP specification development. This
high-level involvement enables Huawei to actively contribute, and closely follow 3GPP
standard development during Huawei product development. LTE TDD eNodeB is based on
3GPP Release 9 September 2010.
Enhancement
None
Dependency
None

Availability
Summary
Benefits
None
Description
Huawei is an active participant and great contributor to 3GPP specification development. This
high-level involvement enables Huawei to actively contribute, and closely follow 3GPP

LTE TDD eRAN6.0
standard development during Huawei product development. LTE eNodeB supports 3GPP
Release 10 specifications 2011.03 version.
Enhancement
None
Dependencies
None
1.4 TDLBFD-001002 TDD mode

Availability
Summary
Huawei LTE TDD supports the Time Division Duplex (TDD) mode.
Benefits
The 3GPP specifications support for Frequency Division Duplex (FDD) and Time Division
Duplex (TDD) mode. In the uplink and downlink, FDD mode use different frequency bands,
whereas TDD mode using the same frequency band.
Description
The 3GPP specifications support the TDD mode. In TDD mode, sole frequency bands are used
for both the uplink and the downlink.
Enhancement
None
Dependencies
The related network elements (NEs) should support TDD mode.
1.5 TDLBFD-001003 Scalable Bandwidth

Availability
Summary
Huawei LTE TDD eRAN1.0 supports the scalable channel bandwidths of 10 MHz and 20 MHz

LTE TDD eRAN6.0
Benefits
⚫ Larger bandwidth produces higher throughput and better user experience.
⚫ Flexible bandwidth configuration helps operators use frequency bands.
Description
Huawei LTE TDD eRAN1.0 supports the scalable channel bandwidths of 10 MHz and 20 MHz
The bandwidth can be configured by the software.
Huawei LTE TDD eRAN3.0 supports the scalable channel bandwidths of 5 MHz which has
some limitations.
Enhancement
None
Dependencies
Only RRU3232/RRU3252 can support 5M bandwidth.
LBBPc board can only support 5M at 2T2R networking.
LBBPd2 can support 5M at 2T2R/4T4R networking.
UE should support the same bandwidth.
If the bandwidth of eNodeB is 5 MHz, the following features cannot work:
⚫ TDLOFD-001049 Single Streaming Beamforming
⚫ TDLOFD-001061 Dual Streaming Beamforming
⚫ TDLOFD-001077 MU-Beamforming
⚫ TDLOFD-001008 Ultra High Speed Mobility
⚫ TDLOFD-001075 SFN
⚫ TDLOFD-002008 Adaptive SFN/SDMA
⚫ TDLOFD-001098 Inter-BBP SFN
⚫ TDLOFD-001080 Inter-BBU SFN
⚫ TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
⚫ TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
⚫ TDLOFD-001005 UL 4-Antenna Receive Diversity (with LBBPc board)
⚫ TDLOFD-001062 UL 8-Antenna Receive Diversity (with LBBPd board)
⚫ TDLOFD-001031 Extended CP
⚫ TDLOFD-001036 RAN Sharing with Common Carrier
⚫ TDLOFD-001037 RAN Sharing with Dedicated Carrier
⚫ TDLOFD-001066 Intra-eNodeB UL CoMP
⚫ TDLOFD-001039 RF Channel Intelligent Shutdown

LTE TDD eRAN6.0
1.6 TDLBFD-001004 CP length

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

LTE TDD eRAN6.0
1.7 TDLBFD-001005 Modulation: DL/UL QPSK, DL/UL

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

LTE TDD eRAN6.0
Dependencies
UE should support the same modulation scheme.
1.8 TDLBFD-001006 AMC

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

LTE TDD eRAN6.0
1.9 TDLBFD-001007 Basic uplink-downlink subframe

configuration
1.9.1 TDLBFD-00100701 uplink-downlink subframe configuration
type1&2
Availability
Summary
The eNodeB supports different uplink-downlink subframe configurations.
Benefits
This feature enables the customer to flexibly configure uplink-downlink subframe ratio
according to different service requirements.
Description
The eNodeB supports different uplink-downlink subframe configurations specified in 3GPP TS
36.211, including:
Type 1: The ratio of uplink subframe to downlink subframe is 2:2. In case of this configuration,
the uplink and downlink traffic are symmetrical.
the throughput of downlink traffic is larger than uplink traffic.
The following figure shows the subframe configurations.
Uplink-downlink Downlink-to-Uplink Subframe number
configuration Switch-point periodicity 0 1 2 3 4 5 6 7 8 9
1 5 ms D S U U D D S U U D
2 5 ms D S U D D D S U D D
In the preceding figure, D denotes the subframe is reserved for downlink transmissions, "U"
denotes the subframe is reserved for uplink transmissions, and "S" denotes a special subframe
with the three fields DwPTS, GP and UpPTS.
Enhancement
None
Dependencies
Subframe configuration type 1 cannot coexist with following features:

LTE TDD eRAN6.0

Subframe configuration type 2 cannot coexist with following feature:
⚫ TDLOFD-001048 TTI Bundling
1.9.2 TDLBFD-00100702 uplink-downlink special subframe

configuration type 7
Availability
Summary
The eNodeB supports different special subframe configurations (lengths of
DwPTS/GP/UpPTS).
Benefits
This feature enables the customer to flexibly configure special subframe configurations
according to application scenario, such as different cell access radius.
Description
The eNodeB supports different special subframe configurations (lengths of DwPTS/GP/UpPTS)
specified in 3GPP TS 36.211. The length of GP can determine the cell access radius.
Type 7: The ratio of lengths of DwPTS to GP to UpPTS is 10:2:2. In case of this configuration,
the maximum cell access radius is up to 15 km.
The detailed special subframe configurations are listed in the following table.
Special subframe Normal cyclic prefix

configuration
DwPTS GP UpPTS
7 21952  Ts 4384  Ts 4384  Ts
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
1.10 TDLBFD-002001 Logical Channel Management

Availability
Summary
The logical channels are provided between the Media Access Control (MAC) layer and the
Radio Link Control (RLC) layer. Each logical channel type is defined according to the type of
the transmitted data. They are generally classified into two types: control channels and traffic
channels.
In Huawei LTE TDD eNodeB, all logical channels are supported except those related to the
evolved Multimedia Broadcast Multicast Service (eMBMS) functionality.
Benefits
Each logical channel is used to send a type of data.
Description
The logical channels are provided between the MAC layer and the RLC layer. They are
responsible for what is transported. They are generally classified into two types:
⚫ Control channels: for transmitting the control plane information
⚫ Traffic channels: for transmitting the user plane information
Control channels include:
⚫ Broadcast Control Channel (BCCH)
⚫ Paging Control Channel (PCCH)
⚫ Common Control Channel (CCCH)
⚫ Multicast Control Channel (MCCH)
⚫ Dedicated Control Channel (DCCH)
Traffic channels include:
⚫ Dedicated Traffic Channel (DTCH)
⚫ Multicast Traffic Channel (MTCH)
In Huawei LTE TDD eNodeB, all logical channels are supported except those related to the
eMBMS functionality, such as MCCH and MTCH.
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
1.11 TDLBFD-002002 Transport Channel Management

Availability
Summary
Transport channels that are provided between the MAC layer and the physical layer, are defined
according to the type of transmitted data and the method of data transmission over the radio
interface. They are used to offer the information about transmission services for the MAC and
higher layers. In Huawei LTE TDD eNodeB, all transport channels except those related to the
eMBMS functionality are supported.
Benefits
Each transport channel is used to send a type of data.
Description
The transport channels are provided between the MAC layer and the physical layer.
Downlink transport channels are classified into the following types:
⚫ Broadcast Channel (BCH)
⚫ Downlink Shared Channel (DL-SCH)
⚫ Paging Channel (PCH)
⚫ Multicast Channel (MCH)
Uplink transport channels are classified into the following types:
⚫ Uplink Shared Channel (UL-SCH)
⚫ Random Access Channel (RACH)
In Huawei LTE TDD eNodeB, all transport channels are supported except those related to the
eMBMS functionality, such as MCH.
Enhancement
None
Dependencies
None
1.12 TDLBFD-002003 Physical Channel Management

Availability

LTE TDD eRAN6.0
Summary
The physical layer is responsible for coding, physical-layer hybrid-ARQ processing,
modulation, multi-antenna processing, and mapping from the signal to the appropriate physical
time-frequency resources. Based on the mapping, a transport channel at the higher layer can
serve one or several physical channels at the physical layer.
In Huawei LTE TDD eNodeB, all physical channels are supported except those related to the
eMBMS functionality, such as PMCH.
Benefits
Each physical channel provides a set of resource blocks for information transmission.
Description
Each physical channel corresponds to a set of resource elements carrying the information from
higher layers.
Downlink physical channels are classified into the following types:
⚫ Physical Broadcast Channel (PBCH)
⚫ Physical Control Format Indicator Channel (PCFICH)
⚫ Physical Downlink Control Channel (PDCCH)
⚫ Physical Hybrid ARQ Indicator Channel (PHICH)
⚫ Physical Downlink Shared Channel (PDSCH)
⚫ Physical Multicast Channel (PMCH)
Uplink physical channels are classified into the following types:
⚫ Physical Uplink Control Channel (PUCCH)
⚫ Physical Uplink Shared Channel (PUSCH)
⚫ Physical Random Access Channel (PRACH)
In Huawei LTE TDD eNodeB, all physical channels are supported except those related to the
eMBMS functionality, such as PMCH.
Enhancement
None
Dependencies
None
1.13 TDLBFD-002004 Integrity Protection

Availability

LTE TDD eRAN6.0
Summary
The feature offers the integrity protection for signaling data. It enables the receiving entity
(either UE or eNodeB) to check whether the signaling data has been illegally modified. It
encrypts or decrypts the signaling data by using a certain integrity algorithm through an RRC
message.
Benefits
The integrity protection procedure prevents the signaling data from illegal modification.
Description
LTE offers the integrity protection for RRC signaling messages at the PDCP layer. The sender
calculates a message authentication code MAC-I based on the RRC message and some
parameters (such as the key, bearer ID, direction, and count) by using an integrity algorithm,
and then send the code to the receiver together with the message. The receiver recalculates the
X-MAC code and compares it with the MAC code in the message. If the two codes are
inconsistent, the receiver knows that the message has been modified illegally.
The eNodeB decides which integrity algorithm to use and informs each UE of the algorithm
through an RRC message.
Huawei LTE TDD eRAN2.0 supports the integrity algorithm both the EIA1 (SNOW3G) and
EIA2 (AES).
In addition to the AES, Huawei eRAN2.0 also supports encryption algorithm SNOW3G.
Enhancement
None
Dependencies
UE should support the same integrity algorithm as the eNodeB.
1.14 TDLBFD-002005 DL Asynchronous HARQ

Availability
Summary
The Hybrid Automatic Repeat and Request (HARQ) provide robustness against transmission
errors. It is also a mechanism for capacity enhancement. As HARQ retransmissions are fast,
many services allow one or multiple times of retransmissions, thereby forming an implicit
(closed loop) rate-control mechanism. An asynchronous transmission protocol is the basis for
downlink HARQ operation. Hence, downlink retransmissions may occur at any time after the
initial transmission, and an explicit HARQ process number is used to indicate the HARQ
process.

LTE TDD eRAN6.0
Benefits
DL HARQ functionality is a fast retransmission protocol to ensure successful data transmission
from the eNodeB to a UE at the physical layer and MAC layer. A UE can request for
retransmissions of data that was incorrectly decoded through an NACK message and
soft-combine the retransmitted data with the previously received data to improve the decoding
performance.
This feature helps improve user throughput and reduce transmission latency in the downlink.
Description
The HARQ is a link enhancement technique combining Forward Error Correction (FEC) and
ARQ technologies. Compared with the ARQ, the HARQ can provide faster and more efficient
retransmissions with lower transmission latency. In the downlink, if the data received by the UE
is decoded correctly by the FEC and passes the Cyclic Redundancy Check (CRC), the UE will
send an ACK message to inform the eNodeB that the data was received correctly. Otherwise,
the UE will send a NACK message to the eNodeB to request for data retransmission.
Downlink HARQ is an asynchronous adaptive transmission process, which means that the
scheduler of the HARQ transmission is not predetermined to the UE. In addition, the DL
HARQ information, such as the location of the allocated resource blocks and MCSs, may be
different from that of the previous transmissions.
In LTE specifications, the DL HARQ scheme is based on an Incremental Redundancy (IR)
algorithm. After the retransmitted data is received, the HARQ process in the UE will
soft-combine the retransmitted data with the previously buffered content and then forward the
combined data to the FEC for decoding. The soft-combined data will help increase the
probability of successful FEC decoding, thereby increasing the data reception success rate.
In LTE specifications, multiple downlink HARQ processes are adopted to fully utilize system
resources. It greatly improves the system throughput and reduces the latency, but it requires
more buffer space and signaling overhead.
Enhancement
None
Dependencies
None
1.15 TDLBFD-002006 UL Synchronous HARQ

Availability
Summary
Compared with the downlink HARQ, uplink retransmission is based on a synchronization
protocol. It occurs at a predefined time after the initial transmission and the number of
retransmissions can be implicitly derived.

LTE TDD eRAN6.0
Benefits
The UL HARQ functionality is a fast retransmission protocol to ensure successful data
transmission from the UE to the eNodeB at the physical layer and MAC layer. An eNodeB can
request for retransmissions of data that is incorrectly decoded and soft-combine the
retransmitted data with the previously received data to improve the decoding performance.
This feature helps improve user throughput and reduce transmission latency in the uplink.
Description
The HARQ is a link enhancement technique combining FEC and ARQ technologies. Compared
with the ARQ, the HARQ can provide faster and more efficient retransmissions with lower
transmission latency. In the uplink, if the data received by the eNodeB is decoded correctly by
the FEC and passes the CRC check, the eNodeB will send an ACK message over the PHICH to
inform the UE that the data was received correctly. Otherwise, the eNodeB will send an NACK
message to the UE to request for data retransmission.
In LTE TDD eRAN1.0, uplink HARQ is a synchronization non-adaptive transmission process;
which means that HARQ transmission blocks are predetermined for transmission and
retransmission. In addition, the UL HARQ information, such as the location of the allocated
resource blocks and MCSs, is predetermined by the eNodeB.
In LTE TDD eRAN2.0, Huawei supports a synchronous adaptive UL HARQ transmission.
During retransmission, the allocated resource block and coding and modulation scheme may be
changed according to the channel quality. However, the retransmission transport block size
remains the same as the first transmission.
In LTE specifications, uplink HARQ scheme is based on an IR algorithm. After the
retransmitted data is received, the HARQ process in the eNodeB will soft-combine the
retransmitted data with the previously buffered content and then forward the combined data to
the FEC for decoding. The soft-combined data will help increase the probability of successful
FEC decoding, thereby increasing the data reception success rate.
In LTE specifications, multiple uplink HARQ processes are adopted to fully utilize system
resources. It greatly improves the system throughput and reduces the latency, but it requires
more buffer space and signaling overhead.
In LTE TDD eRAN2.0, Huawei supports a synchronous adaptive UL HARQ transmission.
While in eRAN1.0, Uplink HARQ is a synchronization non-adaptive transmission process.
Enhancement
None
Dependencies
None
1.16 TDLBFD-002007 RRC Connection Management

Availability

LTE TDD eRAN6.0
Summary
RRC connection is the layer 3 connection between the UE and eNodeB. The RRC connection
management aims to manage the layer 3 connection, including establishment, maintenance, and
release of the connection.
Benefits
The RRC connection management is essential from the UE to E-UTRAN, and serves all service
procedures and NAS procedures.
Description
RRC connection management involves RRC connection establishment, RRC connection
reconfiguration, RRC connection re-establishment, and RRC connection release.
⚫ RRC connection establishment: This procedure is performed to establish an RRC
connection. RRC connection establishment involves Signaling Radio Bearer 1 (SRB1)
establishment. The procedure is also used to transmit the initial NAS dedicated
information or messages from the UE to the E-UTRAN.
⚫ RRC connection reconfiguration: This procedure is performed to modify an RRC
connection, for example, to establish, modify, or release radio bearers, to perform
handovers, and to configure or modify measurements. As a part of the procedure, NAS
dedicated information may be transmitted from the E-UTRAN to the UE.
⚫ RRC connection re-establishment: This procedure is performed to re-establish an RRC
connection after a handover failure or radio link failure. RRC connection re-establishment
involves the restoration of SRB1 operation and the re-activation of security. A UE in
RRC_CONNECTED mode, for which security has been activated, may initiate the
procedure to continue the RRC connection. The connection re-establishment will succeed
only if the cell has a valid UE context.
⚫ RRC connection release: This procedure is performed to release an RRC connection. RRC
connection release involves the release of the established radio bearers and the release of
all radio resources.
Enhancement
In LTE TDD eRAN6.0, eNodeB supports the dual mode UE which supports FDD and TDD but
has different capability values for FDD and TDD. The dual mode UE includes capability IEs
applicable for both FDD and TDD, as well as extended capability IEs including TDD and FDD
specific capability values in the message of UE Capability Information. eNodeB supports
decoding the extended capability IEs and recording the UE’s total capabilities correctly.
Dependencies
None
1.17 TDLBFD-002008 Radio Bearer Management

Availability

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

Availability
Summary
System information (SI) includes:
⚫ Basic information for a UE to access the E-UTRAN, such as basic radio and channel
parameters
⚫ Information about cell selection and reselection parameters used by the UE in RRC_IDLE
mode
⚫ Information about neighboring cells
⚫ Important messages that should be sent to each UE, such as earthquake warning
information
The SI broadcast over the BCCH can be read without setting an RRC connection, and it can be
read by the UE in RRC_IDLE mode and RRC_CONNECTED mode. SI may also be provided
to the UE by means of dedicated signaling, for example, in the case of handover.
Benefits
This feature is the basis for the UE to access the E-UTRAN.

LTE TDD eRAN6.0
Description
SI is classified into the master information block (MIB) and a number of system information
blocks (SIBs):
⚫ MIB defines the information about the most essential physical layers of the cell required
for receiving further system information.
⚫ SIB1contains the information for checking whether a UE is allowed to access a cell and
for defining the scheduling of other system information blocks.
⚫ SIB2 contains the information about common and shared channels.
⚫ SIB3 contains cell reselection information, mainly related to the serving cell.
⚫ SIB4 contains the information about the serving frequency and intra-frequency
neighboring cells related to cell reselection (including common cell reselection parameters
for a frequency and cell-specific reselection parameters).
⚫ SIB5 contains the information about other E-UTRA frequencies and inter-frequency
⚫ SIB6 contains the information about UTRA frequencies and UTRA neighboring cells
related to cell reselection (including common cell reselection parameters for a frequency
and cell-specific reselection parameters).
⚫ SIB7 contains the information about GERAN frequencies related to cell reselection
(including cell reselection parameters for each frequency).
⚫ SIB8 contains the information about CDMA2000 frequencies and CDMA2000
⚫ SIB9 contains a home eNodeB identifier (HNBID).
⚫ SIB10 contains an ETWS primary notification.
⚫ SIB11 contains an ETWS secondary notification.
The paging message is used to inform the UEs in RRC_IDLE and the UEs in
RRC_CONNECTED of the change of the system information.
Huawei LTE TDD eNodeB supports MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB10,
and SIB11.
Enhancement
None
Dependencies
None
1.19 TDLBFD-002010 Random Access Procedure

Availability

LTE TDD eRAN6.0
Summary
Random access is the essential function of LTE system, which allows a UE to achieve the
uplink synchronization and to request for a connection setup. It is performed for the following
five events:
⚫ Initial access from RRC_IDLE
⚫ RRC Connection Re-establishment procedure
⚫ Handover
⚫ DL data arrival during RRC_CONNECTED requiring random access procedure
⚫ UL data arrival during RRC_CONNECTED requiring random access procedure
Benefits
This feature is the basis for the UE to access the E-UTRAN.
Description
The random access procedure enables the UE to establish uplink timing synchronization and to
request for setup of a connection to an eNodeB.
The procedure can be either contention-based (applicable to all the preceding five events) or
non-contention-based (applicable to only handover and DL data arrival). Normal DL/UL
transmission may occur after the random access procedure.
Huawei eNodeB supports the two types of random access procedures. In addition, Huawei
TDD eNodeB supports random access preamble format 0 and format 4.
Enhancement
None
Dependencies
None
1.20 TDLBFD-002011 Paging

Availability
Summary
The purpose of paging is to transmit paging information to a UE in RRC_IDLE mode, and/or to
inform UEs in RRC_IDLE and UEs in RRC_CONNECTED mode of a system information
change.
Benefits
This feature is used to page a UE or inform UEs of system information change.

LTE TDD eRAN6.0
Description
E-UTRAN initiates the paging procedure by transmitting the paging message, which can be
sent by the MME or eNodeB.
When an eNodeB receives a paging message from an MME over the S1 interface, the eNodeB
shall perform paging of the UE in cells which belong to tracking areas indicated in the "List of
TAIs" Information Element (IE) in the paging message.
When the system information changes, the eNodeB must inform all UEs in the cell by paging.
The eNodeB should guarantee that every UE can receive the paging message, that is, the
eNodeB should send the paging message on each possible paging occasion throughout a DRX
cycle. Support for UE discontinuous reception must be broadcast to the entire cell coverage
area and mapped to physical resources.
Enhancement
None
Dependencies
None
1.21 TDLBFD-002012 Cell Access Radius up to 15km

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

Preamble Format TCP TSEQ Cell Access Radius
0 103.1us 800us About 15 km

1 684.4us 800us About 70 km

LTE TDD eRAN6.0
Preamble Format TCP TSEQ Cell Access Radius
2 203.1us 1600us About 30 km

3 684.4us 1600us About 100 km
4 14.58us 133.33us About 1.4 km
Huawei TDD eNodeB supports random access preamble format 0 and format 4.
Enhancement
None
Dependencies
None
1.22 TDLBFD-002023 Admission Control

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

LTE TDD eRAN6.0
Enhancement
None
Dependencies
None
1.23 TDLBFD-002024 Congestion Control

Availability
Summary
The congestion control feature is used to adjust the system loading when the system is in
congestion or the QoS cannot be met.
The main goal of congestion control feature is to guarantee the QoS for the admitted services
while achieving the maximum radio resource utilization.
Benefits
The congestion control feature provides the following benefits:
⚫ Prevent system from being unstable due to overload;
⚫ Guarantee QoS satisfaction rate of services in the system by effectively reduce the system
loading.
Description
This feature is critical to maintain the system stability and deliver acceptable Quality of Service
(QoS) when the system is in congestion.
In LTE TDD eNodeB, congestion control is provided in which two methods are introduced:
The first method is to release low-priority services to alleviate the overloaded system, where the
priority is determined based on the QoS Class Identifier (QCI) assigned to the service.
The second method is GBR downsizing. The basic idea behind the GBR downsizing is to
slightly reduce the guaranteed data rate for all Guaranteed Bit Rate (GBR) services but still
above the minimum bit rate. By sacrificing the quality of GBR services slightly but still
maintaining acceptable quality, it might improve the overall QoS satisfaction ratio.
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
1.24 TDLBFD-002025 Basic Scheduling

Availability
Summary
The basic scheduling feature provides two common scheduling algorithms (MAX C/I and PF).
The operator can select either algorithm.
Benefits
This feature provides the flexibility for the operator to select the scheduling algorithm,
considering the system capacity and fairness among the users.
Description
Scheduling algorithm enables the system to decide the resource allocation for each UE during
each TTI. This feature provides different scheduling algorithms, considering the tradeoff
between system capacity and fairness among the users.
There are two scheduling algorithms provided and the operator can decide which algorithm to
take.
⚫ MAX C/I
⚫ PF (Proportional Fair)
With MAX C/I, users are scheduled based on their radio channel quality. The radio channel
quality is the only factor to be considered in this algorithm, and therefore the fairness among
users cannot be guaranteed.
With PF, users are scheduled according to the value of R/r, where R is the maximum data rate
corresponding to the channel quality, and r is the average data rate of the user. The PF scheduler,
based on the radio channel quality of an individual user, provides the user with an average
throughput proportional to its average channel quality. This algorithm is typically used by a
wireless system to achieve a moderate cell capacity while to ensure fairness among users.
Enhancement
None
Dependencies
None
1.25 TDLBFD-002026 Uplink Power Control

Availability

LTE TDD eRAN6.0
Summary
Uplink power control in LTE system is essential to the control of the eNodeB over the uplink
transmit power of UEs. It also controls the interference to the neighboring cells, to improve the
system throughput. Uplink control power applies to Physical Uplink Shared Channel (PUSCH),
Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), and Physical
Random Access Channel (PRACH).
Benefits
The uplink power control can reduce the interference between neighboring cells by carefully
controlling the transmit power of UEs by the eNodeB and therefore increase the overall
throughput in an LTE system. The uplink power control can also ensure the quality, such as the
block error rate (BLER), of service applications. In addition, uplink power control can reduce
the power consumption of UE.
Description
Uplink power control is one of the most important features for an LTE system. By controlling
the UE transmission power carefully, the interference to the neighboring cells can be reduced
and therefore the overall system throughput is improved. The uplink power control includes the
mechanisms of PUSCH power control, PUCCH power control, SRS power control, and
PRACH power control.
The PUSCH power control includes power adjustment for both Dynamic Scheduling and
Semi-persistent scheduling.
For Dynamic Scheduling:
⚫ Based on the difference between the estimated transmission power spectrum density (PSD)
and PSDTarget, the transmit power of the PUSCH is periodically adjusted according to the
channel environment change. If the estimated PSD is greater than PSDTarget, the eNodeB
sends a TPC command, ordering a decrease of the transmit power. If the estimated PSD is
smaller than PSDTarget, the eNodeB sends a TPC command, ordering an increase of the
transmit power.
⚫ Based on the OI information from the neighboring cell, estimated channel condition, the
PSDTarget is periodically adjusted to adapt to the change of channel environment and
neighboring cell interference.
For Semi-persistent Scheduling:
⚫ In Semi-persistent Scheduling, based on the difference between the measured IBLER and
IBLERTarget, the transmit power of the PUSCH is periodically adjusted according to the
channel environment change. If the measured IBLER is greater than IBLERTarget, the
eNodeB sends a TPC command to the UE, ordering an increase of the transmit power. If
the measured IBLER is smaller than IBLERTarget, the eNodeB sends a TPC command to
the UE, ordering a decrease of the transmit power.
⚫ The PUSCH TPCs of multiple VoIP users are sent to the UEs through DCI Format 3/3A.
By doing so, signaling overheads over PDCCH are reduced.
For PUCCH power control:
⚫ Based on the difference between the measured SINR and SINRTarget, the transmit power
of the PUCCH is periodically adjusted according to the channel environment change. If
the measured SINR is greater than SINRTarget, the eNodeB sends a TPC command,
ordering a decrease of the transmit power. If the measured SINR is smaller than

LTE TDD eRAN6.0
SINRTarget, the eNodeB sends a TPC command, ordering an increase of the transmit
power.
The uplink SRS power control also employs the same power control mechanism as the PUSCH
power control with identical parameter settings. Note that the initial power is calculated in the
same way as PUSCH, except that a power offset configured by RRC is added.
For the PRACH power control, the UE will calculate the transmit power for the initial Random
Access (RA) preamble by estimating the downlink path loss and based on the aforementioned
"expected received power from UE at eNodeB" obtained by monitoring the broadcast channel.
If the RA preamble attempt fails (for example, no RA preamble response for the eNodeB), the
UE can increase the transmit power for the next RA preamble attempt according to the settings
configured by the RRC layer.
Enhancement
None
Dependencies
None
1.26 TDLBFD-002016 Dynamic Downlink Power

Allocation
Availability
Summary
Dynamic Downlink Power Allocation allows an eNodeB to dynamically set the transmit power
at downlink channels to reduce power consumption while maintaining the quality of radio links.
It provides flexible power allocation for downlink channels based on the user's channel quality
and maintains acceptable quality of the downlink connections.
Benefits
This feature allows flexible power allocation for downlink channels based on the user's channel
quality and maintains acceptable quality of the downlink connections. Therefore, it can
improve the edge user throughput and transmission power usage.
Description
The LTE downlink power allocation consists of several parts corresponding to different types of
downlink channels, such as Physical Downlink Shared Channel (PDSCH), Physical Downlink
Control Channel (PDCCH), Physical HARQ Indicator Channel (PHICH), Physical Broadcast
Channel (PBCH), and Physical Control Format Indicator Channel (PCFICH).
⚫ A Fixed power setting is performed for the cell-specific reference signal, synchronization
signal, PBCH, PCFICH, and channels carrying common information of the cell such as

LTE TDD eRAN6.0
PDCCH and PDSCH; since the transmit power of those signals and channels are needed to
ensure the downlink coverage of the cell.
⚫ SINRRS estimation is based on the CQI report. Based on the difference between the
estimated SINRRS and SINRTarget, the transmit power of the PHICH is periodically
adjusted according to the path loss and shading. If SINRRS is smaller than SINRTarget, the
transmit power is increased. Otherwise, the transmit power is decreased.
⚫ In dynamic scheduling, the power of the PDSCH is determined by PA, and the power is
adjusted by updating PA. When the eNodeB receives a reported CQI from the UE, it
compares it with that reported in the previous time. If existing a great difference between
the two CQI values, the power adjustment is performed, and a process of re-calculating the
PA for the UE is started.
In semi-static scheduling, based on the difference between the measured IBLER of VoIP
packets and IBLERTarget, the transmit power of the PDSCH is periodically adjusted to meet
IBLERTarget requirements. If the measured IBLER is smaller than IBLERTarget, the transmit
power is decreased. Otherwise, the transmit power is increased.
In LTE TDD eRAN1.0, PDSCH and PDCCH support dynamically power control.
In LTE TDD eRAN2.0, PDSCH and PDCCH dynamically power control have been optimized.
Enhancement
None
Dependencies
None
1.27 TDLBFD-002017 DRX

Availability
Summary
In RRC_CONNECTED status, UE working on DRX (Discontinuous Reception) mode
switches the receiver on and off alternately according to the configuration of eNodeB to
continue or suspend the receiving of data and signals from network.
Benefits
This feature is mainly used to reduce the power consumption of UEs.
Description
To support the feature, UE should be configured by RRC with DRX functionality that allows it
to discontinuously monitor PDCCH on specific subframes.
There are two states in DRX mode, which are active state and sleep state namely DRX state.
During the active time, UE monitor PDCCH for the possible downlink transmission from
network.

LTE TDD eRAN6.0
Switching between two of the DRX states is not only related with several timers, which are On
Duration timer, DRX Inactivity timer and DRX Retransmission timer but also related with
other some special situation such as that HARQ buffer is not empty, and UE is in RA response
process.
Enhancement
None
Dependencies
UE should support this feature.
1.28 TDLBFD-002018 Mobility Management

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

LTE TDD eRAN6.0
E-UTRAN configures the handover-related measurement through the RRC Connection

Reconfiguration message. The UE could measure either Reference Signal Received Power
(RSRP) or Reference Signal Received Quality (RSRQ) for intra-frequency handover.
Upon receiving a measurement report from the UE, the eNodeB makes a handover decision
according to certain triggering criteria. If a handover is required, the handover execution
procedure will be invoked and the UE will be handed over from the source eNodeB to the target
eNodeB. Huawei LTE TDD eRAN1.0 follows the intra-frequency handover procedures
specified in 3GPP TS 36.300.
The following scenarios are considered in the intra-frequency handover:
⚫ Handover between two cells configured in the same eNodeB. No external neighbor is
needed.
⚫ Handover between two cells configured in different eNodeBs with an X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUEST message over
the X2 interface.
⚫ Handover between two cells configured in different eNodeBs with no X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUIRED message
over the S1 interface.
Enhancement
None
Dependencies
None
1.28.2 TDLBFD-00201802 Coverage Based Inter-frequency

Handover
Availability
Summary
Inter-Frequency Handover enables a UE in connected mode to be served continuously when it
moves across different cells that are operating at different frequencies.
Benefits
The coverage-based inter-frequency handover feature provides supplementary coverage in
inter-frequency LTE systems to prevent call drop, enable seamless coverage, and therefore
improve the network performance and end-user experience.
Description
This feature is one of the fundamental functions of an LTE system. The purpose of
inter-frequency handover is to ensure that a UE in RRC-CONNECTED mode is served
continuously when it moves across different cells operating at different frequencies.

LTE TDD eRAN6.0
The inter-frequency handover procedure can be divided into four phases: measurement
triggering, handover measurement, handover decision, and handover execution.
In inter-frequency handover, neighboring cell measurements are inter-frequency measurements.
The measurement is gap assisted for UEs with one RF receiver. The measurement is triggered
by an event A2 and stopped by an event A1, based on the monitoring on the value of RSRP or
RSRQ.
In inter-frequency handover, the UE sends measurement reports to the eNodeB when the RSRP
or RSRQ meets the criteria set in the measurement configuration.
Upon receiving a measurement report from the UE, the eNodeB makes a handover decision. If
the measurement meets the handover criteria, the eNodeB will perform the corresponding
inter-frequency handover as specified in TS 36.300.
The following inter-frequency handover scenarios are applicable:
⚫ Handover between two cells configured in the same eNodeB. In this case, the UE performs
the handover between two cells configured in the same eNodeB and no external interface
is required.
⚫ Handover between two cells configured in different eNodeBs with an X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUEST message over
the X2 interface.
⚫ Handover between two cells configured in different eNodeBs with no X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUIRED message
over the S1 interface.
Enhancement
In LTE TDD eRAN6.0, eNodeBs support inter-frequency blind redirection based on frequency
priorities. When a UE accesses a cell, the UE reports two A2 events based on the neighboring
cell signal quality. One A2 event is used to trigger the measurement for an inter-frequency blind
handover, and the other is used to trigger an inter-frequency blind handover when the serving
cell cannot provide services for the UE due to the poor signal quality. During the initial phase of
network construction, eNodeBs perform blind redirection instead of inter-frequency blind
handover if the neighbor relationships are not configured.
Dependencies
None
1.28.3 TDLBFD-00201803 Cell Selection and Reselection

Availability
Summary
Cell selection/reselection is a mechanism for UE in idle mode to select a cell to select/reselect a
cell to camp on and to receive the most appropriate service support upon session activation in
the LTE system.

LTE TDD eRAN6.0
Benefits
This feature provides a mechanism for UE in idle mode to select/reselect a cell to camp by
supplementary coverage in the LTE system.
This feature facilitates the automatic selection of the network for UE in idle mode and avoids
the complexity of manual operations.
The UE is always bound to a relatively good cell to obtain better service quality.
Description
When UE selects a PLMN or transition from RRC-CONNECTED to RRC-IDLE, cell selection
is required. The Non-Access Stratum (NAS) can determine the RAT(s) in which the cell
selection should be performed, for instance, by indicating the RAT(s) associated with the
selected PLMN and by maintaining a list of forbidden registration areas and a list of equivalent
PLMN. The UE shall select a suitable cell based on idle mode measurements and cell selection
criteria.
UE in RRC_IDLE can perform cell reselection if UE find a cell with a better radio environment.
When camping on a cell, the UE regularly searches for a better cell according to the cell
reselection criteria. If a better cell is found, that cell is reselected.
Absolute priorities of different E-UTRAN frequencies can be provided for the UE in the system
information and optionally in the RRC message releasing the RRC connection.
Enhancement
None
Dependencies
None
1.28.4 TDLBFD-00201804 Distance Based Inter-frequency

Handover
Availability
Summary
Huawei LTE eNodeB supports distance based inter-frequency handover.
Benefits
User experience is improved.
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 cannot be
satisfied to trigger an inter-frequency handover, even though the neighboring inter-frequency

LTE TDD eRAN6.0
eNodeB signal is much better than F1. To make the user always keep the best connection, a
distance based inter-frequency handover is employed.
When distance based HO algorithm is used, eNodeB should continuously measure the distance
to each UE based on the TA measurement, once the distance exceeds an operator configured
distance threshold, inter-frequency gap measurements of neighboring eNodeB will be triggered
to find an optimal handover candidate to improve user performance.
Enhancement
None
Dependencies
UE should support for inter-frequency Gap measurements
1.28.5 TDLBFD-00201806 Multi-Band Compatibility Enhancement

Availability
This feature is introduced in LTE TDD eRAN6.0.
Summary
If a cell works at a frequency that belongs to multiple bands, it can be configured as a
multi-band cell.
Benefits
⚫ The frequency resource efficiency improves and UEs supporting multiple bands can
access a network configured with these bands. For example, if a cell is configured with
both bands 38 and 41, UEs supporting the two bands can access the cell.
⚫ UE management and maintenance workload is reduced. For example, a UE supporting
both bands 38 and 41 can access the networks configured with these bands, and therefore
fewer UE models need to be maintained.
Description
According to 3GPP TS 36.331 released before October, 2012, the information about the band
supported by a cell is sent to a UE by using an SIB, and each cell supports only one band. If the
band indicated in the SIB differs from the band supported by the UE, the UE cannot access the
cell.
3GPP TS 36.331, released in October, 2012, defines the extended fields for SIBs:
⚫ SIB1: contains the multi-band indicator of the serving cell.
⚫ SIB2: contains additionalSpectrumEmission of different bands.
⚫ SIB5: contains the multi-band indicator of a neighboring cell.
⚫ SIB6: contains the multi-band indicator of a UMTS cell.
In LTE TDD eRAN6.0, a cell can work at multiple bands and the preceding types of SIBs are
sent to UEs.

LTE TDD eRAN6.0
If a UE supports one of the bands at which a cell works, the UE can access the cell.
If a UE supports one of the bands configured for a neighboring cell, the UE can be handed over
to this cell. More candidate cells are therefore available for a UE handover.
If a UTRAN cell is configured with different bands, SIB6 is used to send the band information
to UEs. If a UE supports one of the bands, more candidate cells are available for inter-RAT cell
reselection.
Enhancement
None
Dependencies
This feature depends on TDLBFD-002009 Broadcast of System Information.
UEs can work at different bands and parse the extended fields in SIBs.
1.29 TDLBFD-002022 Static Inter-Cell Interference

Coordination
1.29.1 TDLBFD-00202201 Downlink Static Inter-Cell Interference
Coordination
Availability
Summary
The downlink static inter-cell interference coordination function is used to reduce the downlink
inter-cell interference. The basic principle is that the cell edge users of different neighboring
cells are allocated with non-overlapping frequency bands by static configuration to mitigate
frequency interference.
Benefits
The downlink ICIC feature reduces the downlink inter-cell interference, therefore improves cell
edge user's throughput.
Description
In an LTE system, a cell can use the entire system frequency band and therefore it is inevitable
to cause inter-cell interference for a multi-cell deployment, particularly at the cell edge area. It
is important to develop an efficient solution to mitigate the inter-cell interference in the
multi-cell environment to achieve the performance target. A common solution is to coordinate
the transmission frequency bands among neighboring cells to reduce the inter-cell interference.
In Huawei downlink static ICIC solution, for each cell, a fixed portion of the system frequency
band is allocated to the cell edge users (CEUs). Between neighboring cells, the allocation of the

LTE TDD eRAN6.0
static CEU frequency band is carefully planned to avoid overlapping. The transmit power for
cell center users is limited below a certain threshold, but no such limit for cell edges users. By
doing so, the interference among the cell edge users in neighboring cells can be reduced, which
is the major source of the inter-cell interference. A simple example of the static ICIC solution is
the so-call the 1/3 partition. Among three neighboring cells, each cell will use different 1/3 of
the frequency band for the CEUs.
ICIC consider cell center load and cell edge load in version LTE TDD eRAN2.0. Every cell can
dynamically adjust the numbers of cell center users (CCUs) and CEUs according to the cell
load. It can balance scheduling of the GBR service and non-GBR service.
We can adopt downlink static ICIC when UEs suffer from serious downlink inter-cell
interference and cell coverage performance is bad. However, this may reduce cell capacity.
There are some limitations for using downlink static ICIC:
1. The total UE number of each cell needs to be more than 3.
2. Resource requirement of CEU should not be more than the edge’s PDSCH RB resources.
3. CEU frequency band for each neighboring cells has been carefully setting without
overlapping or conflicted
4. Load between cells and load between cell center and edge are nearly balanced.
5. The bandwidth should be larger than 3 MHz.
In LTE TDD eRAN2.0, static ICIC is optimized to consider cell center load and cell edge load.
Every cell can dynamically adjust the numbers of CCU and CEU according to the cell load,
especially when the cell edge user's GBR is not satisfied, CCUs are not congested and the GBR
service is satisfied. It can balance scheduling of the GBR service and non-GBR service.
Enhancement
None
Dependencies
None
1.29.2 TDLBFD-00202202 Uplink Static Inter-Cell Interference

Coordination
Availability
This feature is available from Huawei LTE TDD eRAN1.0.
Summary
The uplink static inter-cell interference coordination function is used to reduce the uplink
inter-cell interference. The basic principle is that the cell edge users of different neighboring
cells are allocated with non-overlapping frequency bands by static configuration so as to
mitigate frequency interference between cell edge users in neighboring cells.

LTE TDD eRAN6.0
Benefits
Uplink ICIC reduces inter-cell interference; therefore improve cell edge users and overall
throughput as well as the cell coverage.
Description
The uplink Inter-cell interference coordination (ICIC) is a technique to combat the inter-cell
interference for an LTE system by coordinating transmit power control and resource allocation
in frequency domains between neighboring cells. It can improve the throughput of cell edge
users and reduce impact of interference on system performance.
In Huawei uplink static ICIC solution, for each cell, a fixed portion of the system frequency
band is allocated to the cell edge users (CEUs). Between the neighboring cells, the allocation of
the static CEU frequency band of neighbor cells is carefully planned to avoid overlapping. By
doing so, the interference among the cell edge users in neighboring cells can be reduced, which
is the major source of the inter-cell interference. Additionally, the overload indication message
from X2 interface is also used for power control purpose to avoid the interference due to
overloaded frequency band.
We can adopt uplink static ICIC when cell edge users interfere with the neighboring cells
obviously. However, this may reduce cell capacity。
There are some limitations for using uplink static ICIC:
1. Resource requirement of CEU should not be more than the physic cell edge resources.
2. The bandwidth should be larger than 3 MHz.
Enhancement
None
Dependencies
None
1.30 TDLBFD-002020 Antenna Configuration

1.30.1 TDLBFD-00202001 UL 2-Antenna Receive Diversity
Availability
Summary
Receive diversity is a common type of multiple-antenna technology to improve signal reception
and to combat signal fading and interference. It improves network capacity and data rates.
Huawei eNodeB supports both RX diversity mode and no RX diversity mode.

LTE TDD eRAN6.0
Benefits
This feature can improve the receiver sensitivity and uplink coverage.
Description
Receive diversity is a technique to monitor signals at multiple frequencies from the same signal
source, or to monitor time division signals at the same frequency from the same signal source,
to combat signal fading and interference.
Receive diversity is one way to enhance the reception over uplink channels, including PUSCH,
PUCCH, PRACH, and SRS.
Huawei eNodeB supports both RX diversity mode and no RX diversity mode. In RX diversity
mode, the eNodeB can be configured with 2 antennas (2-way) through the Antenna Magnitude
parameter.
In RX diversity mode, the eNodeB does not require additional devices and works with the
Maximum-Ratio Combining (MRC) or Interference Rejection Combining (IRC) algorithms.
Compared with 1-way reception without RX diversity, 2-way RX diversity requires twice the
number of RX channels. The number of RX channels depends on the settings of the antenna
connectors. The antennas to be used can be space-interlace antennas or cross polarization
antennas.
Enhancement
None
Dependencies
This feature needs eNodeB to provide enough RF channels and demodulation resources that
can match the number of diversity antennas.
1.31 TDLBFD-002021 Reliability

1.31.1 TDLBFD-00202102 Cell Rebuild between Baseband
Processing Units
Availability
Summary
In Huawei eNodeB, multiple LTE Baseband Processing (LBBP) boards can be configured to
serve multiple cells. When an LBBP fails, the cell/cells served by the failed LBBP can be rebuilt
on another operating LBBP with spare resources or on a backup LBBP if available.
Benefits
This feature ensures the cell coverage by cell re-establishment and improves the system
reliability in case of an LBBP failure.

LTE TDD eRAN6.0
Description
Generally an eNodeB is equipped with multiple LBBP boards that serve multiple cells. The
following figure shows the example of the 3 x 10 MHz, 2T2R configuration with CPRI
interface backup.
Figure 1-1 3 x 10 MHz, 2T2R
When an LBBP board fails due to, for example, a hardware fault or communication interface
failure, the eNodeB is able to detect and locate the failure and tries to choose a target LBBP
board on which the cell/cells are to be rebuilt. The target LBBP should have a CPRI connection
with the RRU serving the cell/cells involved, as shown in the preceding figures. The selection
of a target LBBP board mainly depends on the spare resources at the potential target LBBP
board. In case of inadequate spare resources at the target LBBP, the bandwidth of the rebuilt
cell/cells, or even that of the existing cells, can be decreased.
Enhancement
None
Dependencies
This feature depends on the RRU with 2 TX channel.
eNodeB should be equipped with at least two LBBP boards.
1.31.2 TDLBFD-00202103 SCTP Multi-homing

Availability

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

level/cell level)
Availability
Summary
In this feature, the processing resources in a baseband processing board of Huawei eNodeB are
aggregated into a baseband resource pool in which they are shared for the load processing.

LTE TDD eRAN6.0
Benefits
This feature ensures the stability and robustness of eNodeB, in which the processing resources
are aggregated into a pool to share all load and therefore to prevent individual resource from
outage due to overload. The feature also improves the average cell capacity of eNodeB.
Description
The baseband processing board of Huawei eNodeB consists of several processing resources. A
baseband processing board is capable of supporting multiple cells depending on the bandwidths.
In this feature, the processing resources are aggregated into a resource pool to be shared for user
data processing by multiple cells. A new user will be assigned to a resource which has the least
load. In an occasional situation, if a resource should be overloaded or in outage, the eNodeB can
reduce the load of the individual resource or move its existing users to other resources.
Enhancement
None
Dependencies
None
1.32 TDLBFD-002027 Support of UE Category 1

Availability
Summary
E-UTRAN needs to respect the signaled UE radio access capability parameters when
configuring the UE and when scheduling the UE. There are five categories defined in the
protocol. This feature can enable base station to support UE category 1.
Benefits
This feature can enable base station to support UE category 1.
Description
protocol. This feature can enable base station to support UE category 1.
Downlink physical layer parameter values set by the field ue-Category:

LTE TDD eRAN6.0
UE Maximum number of Maximum number Total number Maximum number of

Category DL-SCH transport of bits of a of soft supported layers for
block bits received DL-SCH transport channel bits spatial multiplexing
within a TTI block 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
Uplink physical layer parameter values set by the field ue-Category:
UE Category Maximum number of bits of an UL-SCH Support for 64QAM in UL

transport block transmitted within a TTI
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No
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
Enhancement
None
Dependencies
UE should support the same category as eNodeB.
1.33 TDLBFD-002028 Emergency Call

Availability

LTE TDD eRAN6.0
Summary
The emergency call service is an operator-assisted service that connects a caller in a
life-threatening or time-critical situation to an emergency service organization.
Benefits
This feature provides all users, even those without SIM, a prioritized connection to an
emergency service organization.
Description
The emergency Call service is an operator-assisted service that connects a caller in a
life-threatening or time-critical situation to an emergency service organization such as police,
hospital and fire station.
New features in E-UTRAN to support emergency call are as follows:
⚫ Support of identifying emergency call users
⚫ Support of special processing such as access class barring and priority handling for the
network access and mobility management
⚫ Support of location service for emergency call users. This function depends on the feature
TDLOFD-001047 LoCation Services (LCS).
Admission of an emergency call is prioritized over other ongoing sessions in the eNodeB to
enable call completion. Regardless of network features/services activated in the network (for
example, unconditional call-forwarding and incoming call barring), the Public Safety
Answering Point (PSAP, used in the United States) or Emergency Center (EC, used in Europe)
is able to get emergency caller's location by means of LCS and call back the caller once an
emergency call has been placed. The emergency call, served on LTE with multi-mode terminal,
falls back to UMTS or GSM depending upon LTE VoIP support.
Four types of users are permitted to initiate an emergency call:
⚫ Common user: normal subscriber
⚫ Common restricted user: normal subscriber, whose calls are restricted for some reasons
(for example, out of coverage of own PLMN)
⚫ Restricted user with SIM card: User, whose SIM card fails to authenticate, uses IMEI
(International Mobile Equipment Identity) to initiate an emergency call.
⚫ Restricted user without SIM card: User, without SIM card, uses IMEI to initiate an
emergency call
This feature supports 911 Emergency Calls (North America) / 112 Emergency Calls (Europe) in
its SAE/LTE network as defined by 3GPP specification.
Enhancement
None
Dependencies
UE should support IMS-based voice service on LTE or voice service on 2G/3G.
The function of location service for emergency call users is dependent on the optional feature
TDLOFD-001047 LoCation Services (LCS).

LTE TDD eRAN6.0
The emergency call should be supported in the core network.

If IMS is not deployed, the support of the optional feature CS Fallback to GERAN/UTRAN
will be needed.
1.34 TDLBFD-002029 Earthquake and Tsunami Warning

System (ETWS)
Availability
This feature is available from eRAN2.2.
Summary
When an event, such as an earthquake, occurs, Warning Notification Providers produce
Warning Notification to PLMN operator; PLMN operators distribute Warning Notifications to
users by utilizing Earthquake and Tsunami Warning System (ETWS).
Benefits
⚫ Quick Warning Notification delivery after the occurrence of Earthquake or Tsunami.
⚫ Accurate Warning Notification delivery.
Description
When the occurrence of a disaster, such as an Earthquake, is detected, the warning notification
provider, such as the local government, is responsible for notifying the public as soon as
possible.
Figure 1-3 Overview of Earthquake and Tsunami Warning System
1. Warning Notification Provider may publish Primary Notification to PLMN. The content of
the Primary Notification only includes the most urgent information related to the disaster.
The Notification Area where the Warning Notification needs to be distributed is also
specified by Warning Notification Provider. When the Primary Notification is delivered by
PLMN to users in the Notification Area, the UE that detects the delivery of the Primary
Notification alerts the user, such as by sound and vibration.
2. Warning Notification Provider may publish a Secondary Notification to PLMN. The
content of the Secondary Notification may include additional information, such as
instructions on what to do / where to get help as long as the emergency lasts. The
Notification Area is also specified by Warning Notification Provider. While the Secondary
Notification is delivered by PLMN to users in the Notification Area, The UE which detects
the delivery of the Secondary Notification alerts the users, such as by specified buzzer and
vibration.

LTE TDD eRAN6.0
While Warning Notification Provider specifies that the Notification should be delivered
periodically, Warning Notification Provider may request the PLMN to stop to disseminate the
notification.
Enhancement
None
Dependencies
Both UE and MME should support ETWS
1.35 TDLBFD-002031 Support of aperiodic CQI reports

Availability
Summary
Aperiodic CQI is reported on PUSCH and the UE can be configured to report periodic CQI and
aperiodic CQI together or individually.
Benefits
Aperiodic CQI can offer more detailed channel quality information which may make the
scheduler more efficient.
Description
Aperiodic CQI is triggered by the UL scheduler when needed and the CQI Request field in the
UL grant is used to indicate the aperiodic CQI report. There are 5 types of the aperiodic
reporting modes, and the given mode is configured by the RRC.
Wideband-configured
Mode 1-2: A wideband CQI per codeword and multiple PMI for each subband are reported.
UE selected (sub band CQI)
Mode 2-0: A wideband CQI and a subband CQI for M preferred subbands are reported.
Mode 2-2: A wideband CQI and a subband CQI for M preferred subbands per codeword are
reported. A wideband PMI and a subband PMI for M preferred subbands are also reported.
Higher layer-configured
Mode 3-0: A wideband CQI and multiple subbands CQI for each subband are reported.
Mode 3-1: A wideband CQI and multiple subbands CQI for each subband per codeword are
reported. A wideband PMI is also reported.
Huawei eNodeB supports all of the aperiodic report modes, and supports periodic CQI and
aperiodic CQI configured at the same time.

LTE TDD eRAN6.0
Enhancement
None
Dependencies
None
1.36 TDLBFD-002033 SCTP Congestion Control

Availability
Summary
When the network is heavily loaded, Stream Control Transmission Protocol (SCTP) congestion
control can be used to prevent SCTP association exceptions caused by SCTP signaling
congestion. SCTP congestion control is triggered when SCTP resources, including the central
processing unit (CPU) and buffer resources, are insufficient.
Benefits
This feature enhances signaling message processing robustness when the network is heavily
loaded.
Description
In a Long Term Evolution (LTE) system, control plane messages are used to ensure that the
E-UTRAN runs properly and that service connections are set up and released properly. To
ensure the reliability of control plane messages, S1 signaling messages between an E-UTRAN
NodeB (eNodeB) and a mobility management entity (MME) and X2 signaling messages
between eNodeBs are transmitted in compliance with SCTP. E-UTRAN is short for evolved
universal terrestrial radio access network.
Signaling traffic has increased sharply with the extended use of smartphones and increasingly
rich applications such as instant messaging (IM). Consequently, when the service traffic and
signaling traffic are heavy, SCTP resources become a bottleneck. In such situations, SCTP
congestion control helps to maintain signaling transmission robustness and reduce impact on
service key performance indicators (KPIs).
The SCTP congestion control procedure includes SCTP congestion detection, backpressure,
and signaling congestion control at the application layer. The eNodeB determines whether
SCTP signaling is congested based on the SCTP resource usage. If SCTP signaling is congested,
the eNodeB notifies the application layer of the congestion by backpressure. Then, the
application layer processes SCTP signaling in a differentiated manner to reduce the signaling
traffic and to maintain stable service KPIs.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
None
1.37 TDLBFD-002035 Multi Carrier

Availability
Summary
When frequency resources are sufficient, this feature is used to increase system capacity.
Benefits
This feature greatly increases the system capacity in the uplink and downlink. In optimal
conditions, this feature can increase the system capacity to N times the original. N indicates the
number of carriers.
Description
Capacity requirements vary in different network deployment phases:
⚫ In the initial phase, operators focus on network coverage, and single-carrier networking
can meet the capacity requirements. Therefore, the entire network operates in
single-carrier mode.
⚫ When the number of users and the amount of service traffic increase, a larger capacity is
required. Operators must then optimize the network, and increase the number of sites or
use multi-carrier networking to expand the network capacity in certain areas requiring
large capacity.
When frequency resources are sufficient, this feature increases system capacity and reduces
network deployment costs without increasing the number of sites.
In LTE TDD eRAN6.0, a maximum of two carriers can be used for multi-carrier networking.
Enhancement
None
Dependencies
The eNodeB must be configured with hardware licenses.

LTE TDD eRAN6.0
1.38 TDLBFD-003001 Transmission Networking

1.38.1 TDLBFD-00300101 Star Topology
Availability
Summary
Star topology is easy to implement and manage with high reliability. It provides simple
topology between eNodeB interfaces.
Benefits
⚫ The simplest topology
⚫ Simple management and high reliability
Description
Figure 1-4 Star topology
The eNodeB supports star topology. eNodeBs connect to the core network by layer2 or layer3
data network. The interface between the eNodeB and core network element is the S1 interface.
There are also connections between eNodeBs by the X2 interface, which enable information
exchange between the eNodeBs.
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
1.38.2 TDLBFD-00300102 Chain Topology

Availability
Summary
eNodeBs can be connected in chain topology applied to the strip-shape areas of sparse
population.
Benefits
Chain networking can reduce costs of transmission equipment, engineering, construction, and
transmission link lease.
Description
eNodeBs can be connected in chain topology. This network topology is applicable to the
strip-shape areas of sparse population, such as expressways and railways. In these areas, the
chain topology can meet the requirement with much less transmission equipment. However,
chain networking reduces reliability because signals are transferred across many intermediate
systems.
The following figure shows the chain topology.
Figure 1-5 Chain topology
Enhancement
None
Dependencies
None
1.38.3 TDLBFD-00300103 Tree Topology

Availability
Summary
eNodeBs can be connected in tree topology applied to microwave transmission networks.

LTE TDD eRAN6.0
Benefits
Tree networking is suitable for microwave transmission networks. Tree topology requires fewer
transmission links than star networking.
Description
The eNodeB can be connected in tree topology. In most scenarios, the MW (Microwave)
network is typically in tree topology. It is suitable for the MW network.
The use of transport lines is less than that for star networking. However, tree connections reduce
reliability because signals are transferred across many intermediate systems. A fault occurring
in the upper-level eNodeB may affect the operation of the lower-level eNodeBs. The
networking topology is applicable to a large, sparsely populated area. Capacity expansion may
result in reconstruction of the network.
The following figure shows the tree topology.
Figure 1-6 Tree topology
Enhancement
None
Dependencies
The feature is based on E1/T1 and Ethernet interfaces.
1.39 TDLBFD-003006 IPv4/IPv6 Dual Stack

Availability

LTE TDD eRAN6.0
Summary
A fundamental IPv4-to-IPv6 transition technology involves the presence of two Internet
Protocol software implementations in an operating system, one for IPv4 and another for IPv6.
This feature provides support for IPv6 protocol stack. It also enables IPv4 and IPv6 protocol
stack work at the same time. Application level protocols (such as S1 and X2) over IPv6 are not
supported by this feature.
Benefits
The key to a successful IPv6 transition is compatibility with the large installed base of IPv4
hosts and routers. Maintaining compatibility with IPv4 while deploying IPv6 will streamline
the task of transitioning the Internet to IPv6.
Description
The most straightforward way for IPv6 nodes to remain compatible with IPv4-only nodes is by
providing a complete IPv4 implementation. IPv6 nodes that provide complete IPv4 and IPv6
implementations are called "IPv6/IPv4 dual-stack nodes". IPv6/IPv4 dual-stack nodes can to
send and receive both IPv4 and IPv6 packets. They can directly interoperate with IPv4 nodes
using IPv4 packets, and also directly interoperate with IPv6 nodes using IPv6 packets.
Huawei eNodeB could be operated in one of the three modes:
⚫ With IPv4 stack enabled and IPv6 stack disabled.
⚫ With IPv6 stack enabled and IPv4 stack disabled.
⚫ With both stacks enabled.
Huawei eNodeB provides a configuration switch to disable either IPv4 or IPv6 stack.
Enhancement
None
Dependencies
None
1.40 TDLBFD-003002 Basic QoS Management

1.40.1 TDLBFD-00300201 DiffServ QoS Support
Availability
Summary
Huawei supports Differ (Differentiated Services) to provide QoS guarantee by classifying and
managing different traffic in the network.

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

Data Type QCI Resource Type DSCP
User plane 1 GBR 0x2E

2 0x1A
3 0x1A
4 0x22
5 Non-GBR 0x2E
6 0x12
7 0x12
8 0x0A
9 0
Control plane SCTP 0x2E
OM MML 0x2E
FTP 0

LTE TDD eRAN6.0
Enhancement
None
Dependencies
None
1.41 TDLBFD-003003 VLAN Support (IEEE 802.1p/q)

Availability
Summary
This feature enables Virtual Local Area Network (VLAN) functionality to provide traffic
differentiation, manage data priority and security scheduling at the MAC layer.
Benefits
⚫ Traffic isolation at the MAC layer
⚫ Priority at the MAC layer
⚫ Security at the MAC layer
Description
The eNodeB supports the Virtual Local Area Network (VLAN) functionality, complying with
the IEEE 802.1p/q protocol. It provides traffic isolation, such as marking different VLANs for
OAM data and traffic data, and priority and security at the MAC layer.
The following two VLAN Marking ways are applicable:
⚫ Marking VLAN tag according to DSCP
⚫ Marking VLAN tag according to the next-hop IP address
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
1.42 TDLBFD-003004 Compression and Multiplexing over

E1/T1
1.42.1 TDLBFD-00300401 IP Header Compression
Availability
Summary
IP header compression provides a method to compress IP header information to increase the
efficiency of E1/T1 interfaces.
Benefits
IP header compression can save S1/X2 IP transport resource to provide higher transport
efficiency of S1/X2 IP transmission.
Description
This feature focuses on the compression technology in UDP/IP layer.
When UDP/IP/MLPPP/E1/T1 is used for transport, the UDP/IP encapsulation is too large for
packets of small payloads and results in low transport efficiency.
IP header compression is adopted to enhance the transport efficiency. The 28 bytes of UDP/IP
header can be compressed into 4-7 bytes.
Enhancement
None
Dependencies
This feature needs Optional UTRP (Universal Transmission Processing unit) card
IP over E1/T1 is used for transport.
The peer equipment should support the IP header compression functionality.
1.42.2 TDLBFD-00300402 PPP MUX

Availability
Summary
Point-to-point multiplexing (PPP MUX) provides a method to multiplex the IP header to
increase the efficiency of E1/T1 interfaces.

LTE TDD eRAN6.0
Benefits
PPP MUX can save S1/X2 IP transport resource to provide high transport efficiency for S1/X2
IP transmission.
Description
This feature focuses on the multiplex technology in PPP/ML-PPP layer.
When UDP/IP/ML-PPP/E1 is used for transport, the UDP/IP/ML-PPP encapsulation is too
large for packets of small payloads and results in low transport efficiency.
PPP MUX technology is adopted to enhance the transport efficiency. With PPP MUX
mechanism, several IP packets can be multiplexed into one PPP frame to reduce the transport
consumption of PPP.
Enhancement
None
Dependencies
IP over E1/T1 is used for transport
PPP or ML-PPP is used for transport
The peer equipment should support PPP MUX function.
1.42.3 TDLBFD-00300403 ML-PPP/MC-PPP

Availability
Summary
ML/MC-PPP (Multilink and Multi-Class Point-to-Point Protocol) is the extend protocols of
PPP. ML-PPP is a protocol for binding several PPP links to one logic PPP link. The priority is
provided for PPP link traffic via MC-PPP protocol.
Benefits
⚫ Increase the bandwidth of the PPP link.
⚫ Load balancing in multi-PPP links
⚫ Enhance the reliability of the PPP link
⚫ Provide priorities for traffic on PPP link.
⚫ Transport efficiency is enhanced when PPP header compression is used.
Description
PPP is a point-to-point transport protocol. The PPP header compression can be provided to
enhance the transport efficiency.

LTE TDD eRAN6.0
ML-PPP is an extend protocol of PPP. When ML-PPP is used, several PPP links are bound to
one logic PPP link group. The ML-PPP increases the bandwidth of the PPP link and enhances
the reliability of the PPP link between the eNodeB and the directly connected equipment. If one
link of PPP link group is broken, the ML-PPP will not be broken. Only thing happen is the
bandwidth decreases correspondingly.
MC-PPP is an extend protocol of PPP. When MC-PPP is used, the traffic on the PPP links can
be marked with different priorities according to DSCP which is mapped to QCI in eNodeB.
The following figure shows the ML/MC-PPP.
Figure 1-7 ML/MC-PPP
Enhancement
None
Dependencies
The peer transport equipment shall support ML-PPP/MC-PPP when ML-PPP/MC-PPP is used
to transport.
E1/T1 interfaces are used.
1.43 TDLBFD-003005 Synchronization

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

LTE TDD eRAN6.0
Description
The eNodeB can work in multiple clock synchronization modes. The system clock source can
be chosen in a convenient and flexible manner. When one clock source fails, the system clock
can be manually or automatically switched to another available one.
The eNodeB clock sources that can be selected are as follows:
⚫ Synchronization with GPS
⚫ Synchronization with the IEEE1588V2
⚫ Synchronization with 1PPS+TOD
In addition to the previous clock sources, the eNodeB can work with the local oscillator.
Enhancement
None
Dependencies
None
1.43.2 TDLBFD-00300502 Free-running Mode

Availability
Summary
The free-running mode is an alternative mode to the clock sources if all clocks fail.
Benefits
When all clock sources are lost, this feature can keep the eNodeB in normal service for up to 8
hours.
Description
When all clock sources are lost, the eNodeB internal clock can work in the free-running mode
to keep the eNodeB running.
The enhanced stratum 3 Oven Controlled Crystal Oscillator (OCXO) with a high accuracy
works as the master clock of the eNodeB. The OCXO can keep the eNodeB in normal service
for up to 8 hours.
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
1.43.3 TDLBFD-00300503 Synchronization with GPS

Availability
Summary
The eNodeB can work in multiple clock synchronization modes to suit different clock
topologies. Global Positioning System (GPS) can be one of the synchronization sources.
Benefits
This feature provides GPS as one of the synchronization sources. The eNodeB internal clock
can be synchronized with the transport network and no auxiliary clock equipment is needed, in
order to reduce the cost. The synchronized clock is of the required accuracy to meet both radio
frequency and transmission network requirements.
Description
In compliance with 3GPP, the eNodeB clock must have a higher clock precision. The frequency
stability of the 10-MHz master clock of the eNodeB should be lower than ±0.05 ppm and phase
stability of the 10-MHz master clock of the eNodeB should be lower than ±1.5 µs.
It is required if a GPS clock should be used as the clock source.
The clock signals are processed and synchronized as follows:
The GPS antenna and feeder system receives GPS signals at 1575.42 MHz, and transmits the
signals to the GPS card. The system can simultaneously trace up to eight (normally three or four)
satellites. The GPS card processes the signals and transmits them to the main clock module.
eRAN 3.0 implements single satellite synchronization. To reach GPS synchronization, eNodeB
needs to receive the signals from at least four satellites. However, in some specific scenarios,
only the signals of one to three satellites can be received and this is not enough for GPS
synchronization. eRAN 3.0 enhances this feature. In eRAN3.0, if antenna location information
(latitude/ longitude/ altitude) is manually configured accurate in eNodeB, eNodeB is able to
implement GPS synchronization. The location information is very important. Inaccurate
location information will impact the synchronizing precision.
Enhancement
None
Dependencies
This feature needs GPS antenna and feeder system
1.43.4 TDLBFD-00300505 Synchronization with 1PPS+TOD

Availability

LTE TDD eRAN6.0
Summary
The eNodeB can work in multiple clock synchronization modes to suit different clock
topologies. 1PPS+TOD can be one of the synchronization sources.
Benefits
This feature provides 1PPS+TOD as one of the synchronization sources. The eNodeB internal
clock can be synchronized with the transport network and no auxiliary clock equipment is
needed, in order to reduce the cost. The synchronized clock is of the required accuracy to meet
both radio frequency and transmission network requirements.
Description
In compliance with 3GPP, the eNodeB clock must have a higher clock precision. The frequency
stability of the 10-MHz master clock of the eNodeB should be lower than ±0.05 ppm, and phase
stability of the 10-MHz master clock of the eNodeB should be lower than ±1.5µs.
This feature provides 1PPS+TOD as one of the synchronization sources.
Enhancement
None
Dependencies
This feature needs Optional USCU (Universal satellite Card and Clock Unit) card
1.44 TDLBFD-004001 Local Maintenance on the LMT

Availability
Summary
This feature is used in local maintenance of eNodeB.
Benefits
Local maintenance of eNodeB is available when centralized M2000 management is not
available, when the transmission between M2000 and eNodeB is not available or when faults
occur and field operation is required.
Description
The Local Maintenance Terminal (LMT) provides the following functions and tools:
⚫ Execution of MML commands
⚫ Querying of eNodeB alarms

LTE TDD eRAN6.0
⚫ Local eNodeB commissioning functions (applicable, for example, when the transmission
between the Huawei iManager M2000 and eNodeB is not available), such as download
and activation of software
⚫ Local eNodeB expert fault diagnosis functions
⚫ Real-time performance monitoring functions, such as sector performance monitoring,
RRU performance monitoring, and spectrum detection
Enhancement
The LMT functions can be achieved through a web browser.
Dependencies
A web browser is needs to achieve the function.
1.45 TDLBFD-004002 Centralized M2000 Management

Availability
Summary
The Huawei iManager M2000 provides FCPSS management functions for operators at the
management center.
Benefits
All LTE network elements can be managed at the management center, which effectively
reduces OPEX.
Description
The Huawei iManager M2000 provides all necessary fault management, configuration
management, performance management, security management and software management
(FCPSS defined by 3GPP) management functions to help operators to manage their network
elements on a sub-network.
FCPSS involves the following contents:
⚫ Centralized fault management
⚫ Centralized configuration management
⚫ Centralized performance management
⚫ Centralized security management
⚫ Centralized software management
Enhancement
None

LTE TDD eRAN6.0
Dependencies
This feature needs Huawei iManager M2000.
1.46 TDLBFD-004003 Security Socket Layer

Availability
Summary
Secure Sockets Layer (SSL) is a layer between the TCP layer and the O&M application layer.
SSL provides the secured data transfer function between the eNodeB and the Huawei iManager
M2000.
Benefits
All remote operation and maintenance tasks are performed through encrypted protocols.
Description
SSL is a layer between the TCP layer and the O&M application layer. SSL provides the secured
data transfer function between the eNodeB and the Huawei iManager M2000. All O&M
application data transferred through SSL is encrypted. FTP over SSL is also supported.
From eRAN3.0, this feature supports TLSv1.2. Transport Layer Security (TLS) and its
predecessor-Secure Sockets Layer (SSL), are cryptographic protocols that provide
communications security between eNodeBs and Huawei iManager M2000 above Transport
Layer. And TLSv1.2, which maps to SSLv3.3, is the latest version of TLS series.
Enhancement
None
Dependencies
Related certifications are required.
1.47 TDLBFD-004004 Software Version Upgrade

Management
Availability

LTE TDD eRAN6.0
Summary
This feature provides efficient and correct installation and upgrade of the software and version
management functions.
Benefits
The eNodeB software management enables efficient and correct software installation, upgrade,
and version management.
Description
The eNodeB software management covers the following functions:
⚫ Efficient and correct installation and upgrade of the software
− Automatic compatibility check on the software and hardware versions to verify a
successful software installation and upgrade.
− Automatic data conversion for the software upgrade, which requires no manual
configuration updates.
− Software download by configuration can reduce 30% of the software package size and
shorten the download time. For adding a board, the system supports automatic
download of software files for the board from the Huawei iManager M2000 if the files
are not downloaded to eNodeB previously.
− If the network recovers in 1 hours after breakdown, the system supports resumption of
the software download with no need to download the software from scratch.
− A maximum of 600 eNodeBs can be selected to download and activate the software in
batches automatically.
− Hot patch can be upgraded together with software in Huawei iManager M2000
software management wizard.
⚫ Version management, for example, the hardware and software version query
The process for upgrading software at a network element involves the following two activities:
⚫ Downloading the software package from the Huawei iManager M2000 to the eNodeB.
This may take some time because of the limited bandwidth of the OM link but does not
have impacts on services.
⚫ Running the software activation command on the Huawei iManager M2000 client. The
system will automatically load the software to the target boards and activate the software.
To activate the software, the target boards will be reset and the service on the boards will
be interrupted.
The above-mentioned two activities can be done separately, for example, downloading software
package to eNodeBs at daytime and activating the software at midnight. The separate software
upgrade procedure helps to reduce the risk of software upgrade failures and service interruption
of the sub-network.
Enhancement
None
Dependencies
This feature needs Huawei iManager M2000.

LTE TDD eRAN6.0
1.48 TDLBFD-004005 Hot Patch Management

Availability
Summary
This feature provides hot patch management functions, such as installation, uninstall and
rollback.
Benefits
The eNodeB supports the hot patches so that the software bugs can be fixed without
interrupting the ongoing services.
Description
A hot patch is a patch that is used to fix bugs and does not interrupt the ongoing services.
Huawei LTE TDD hot patch management involves the following functions:
⚫ Hot patch installation.
There are two ways to install a released hot patch package on the eNodeB:
− Running only a single installation command: In this way, the patch is downloaded,
loaded, activated and confirmed automatically.
− Running separate commands at different steps of the patch installation: In this way,
users have full control over the installation procedure: download, load, activate and
confirm.
⚫ Rollback of the last installed hot patch
⚫ Uninstall of the hot patch
Enhancement
None
Dependencies
Hot patch management can be implemented on the Huawei iManager M2000 or the eNodeB
LMT.
1.49 TDLBFD-004006 Fault Management

Availability
Summary
This feature provides automatic fault supervision and handling of eNodeB.

LTE TDD eRAN6.0
Benefits
This feature enables the automatic fault supervision of the equipment in the network elements.
With real-time alarm lists and alarm logs, operators can have a comprehensive view of the
actual status of the network at any time.
Description
Fault management involves fault detection, fault handling, fault correlation, and fault reporting.
With these features, operators can be informed as soon as the fault occurs in the network and
take proper actions to minimize or prevent service interruption.
⚫ Fault detection
Fault detection includes physical layer and link layer environment monitoring and KPI
alarm monitoring and other fault detection. A small portion of faults may have a negative
impact on the traffic if self-testing, such as RAM self-testing and transport link loopback
testing, is performed. Among those faults, some are detected automatically in the board
startup phase, and some can be manually triggered by executing fault testing commands.
Fault detection methods are carefully designed to avoid false alarms and intermittent
alarms.
⚫ Fault handling
The eNodeB will perform fault isolation and fault automatic recovery to minimize the
impacts on service.
⚫ Fault correlation
Fault management supports a run-time fault correlation handling mechanism and makes it
possible to notify operators of the most important alarms (the root cause and impacts on
the traffic) instead of all the related ones when a fault occurs. The number of alarms can be
greatly reduced in this way, which makes it easier to locate and solve the network
problems. This mechanism is predefined and embedded in the network elements, and
operators can customize more alarm correlation handling rules on the Huawei iManager
M2000.
⚫ Fault reporting
Faults are reported to users in the form of alarms. Because of the alarm correlation
function, the information of the correlation between alarms is contained in alarms. If any
correlative alarms occur, operators can get the root alarm by simply right-clicking the
service-affecting faults.
The operators can browse real-time alarm information, query historical alarm information, and
store alarm information. The online help provides detailed troubleshooting methods for each
type of alarm.
Huawei LTE TDD eRAN2.0 supports KPI alarm detection.
In Huawei LTE TDD eRAN2.2, when RRU power supply is AC, RRU could detect AC power
down and provide warning signal to the eNodeB.
Enhancement
None
Dependencies
Fault management can be implemented on the Huawei iManager M2000 or the eNodeB LMT.

LTE TDD eRAN6.0
1.50 TDLBFD-004007 Configuration Management

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

LTE TDD eRAN6.0
1.51 TDLBFD-004008 Performance Management

Availability
Summary
This feature provides various performance measurement (PM) counters to monitor the
performance of the eNodeB. The real-time KPI monitoring is an enhanced feature to help user
locate performance problems quickly.
Benefits
The performance management function provides an efficient way to monitor the network
performance so that network troubleshooting and optimization can be implemented, and the
real-time KPI monitoring is a more efficient feature.
Description
Performance measurement gives the detailed information of the network. Such information
facilitates troubleshooting and network optimization.
⚫ PM administration
The performance measurement administration provides operators with a means to manage
the available measurements.
For the new commissioning network elements (eNodeB), the predefined performance
measurements will start after initial startup phase. The performance measurements can be
suspended and resumed manually.
The network elements (eNodeB) provide machine-machine interfaces, allowing the
Huawei iManager M2000 to collect the necessary statistics and to set the related
parameters including statistical counters and the measurement period.
The statistics are obtained by the Huawei iManager M2000 in binary format in every
measurement period. The result files are also stored in the network element (eNodeB) for
up to 3x24 hours as backups that are useful when data transfer fails, which makes it
possible for the Huawei iManager M2000 to recollect the lost data later.
⚫ PM counters
The PM counters include key counters and other counters. The key counters are used to
generate the key performance indicators (KPIs) of the network, which are defined on the
Huawei iManager M2000, and these counters are predefined and initialized as soon as the
eNodeB starts. The KPIs, related original counters and formulas can be added, modified
and deleted on the Huawei iManager M2000. Other counters reflecting the other aspects of
network performance can be started when needed.
⚫ Real-time KPI monitoring
This feature provides the monitoring of KPIs and graphical representation of network
performance. Therefore, it is convenient for troubleshooting, drive tests and network
optimization. The smallest sample frequency is 10 seconds.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
Performance management is implemented on the Huawei iManager M2000.
1.52 TDLBFD-004009 Real-time Monitoring of System

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

LTE TDD eRAN6.0
1.53 TDLBFD-004010 Security Management

Availability
Summary
This feature provides the user authorization, system data backup and restore, security log
auditing and security-related alarms functions.
Benefits
This feature provides the user authorization and management mechanism to enhance network
security.
Description
Security management covers the following functions to enhance system security:
⚫ User management: This mechanism allows setting of user accounts and permissions, so
that the related authorized groups and operators can be managed.
⚫ System data backup and restoration
⚫ Collection of operation logs and auditing of security logs
⚫ Triggering of alarms when, for example, network attacks are detected or the number of
unauthorized sessions exceeds the preset threshold
⚫ Security alarms.
Enhancement
None
Dependencies
Security management is implemented on the Huawei iManager M2000.
1.54 TDLBFD-004011 Optimized eNodeB Commissioning

Solution
Availability
Summary
The optimized eNodeB commissioning solution supports USB commissioning and automatic
obtaining of software and configuration data from the Huawei iManager M2000. (1) The
security of the USB port is ensured by encryption. (2) When the USB port functions as a
commissioning Ethernet port, ensure that an OM port has been opened and the user has

LTE TDD eRAN6.0
obtained required authorities for accessing the base station through the OM port before
accessing the base station through the USB port.
Benefits
This feature simplifies the eNodeB commissioning procedure.
Description
This feature simplifies the on-site commissioning procedure from the following aspects:
⚫ If eNodeB data is ready on the Huawei iManager M2000 and transmission of this eNodeB
is ready, Huawei on-site manual commissioning task is very simple:
− Installing the hardware and powering on the eNodeB
− Waiting for the eNodeB startup
− If the eNodeB has a GPS, field engineer need do nothing because eNodeB will report
the location to iManager M2000 and iManager M2000 will automatically select the
correct configuration data for it.
− Or, if field engineer has a laptop, the engineer can use laptop to input very simple
information (eNodeBID). iManager M2000 can use this information to automatically
select correct configuration data.
− Or, field engineer can call the administration center and report the Electronic Serial
Number (ESN) of the eNodeB
⚫ In the procedure, the newly installed equipment will automatically set up the connection
with the Huawei iManager M2000 by using DHCP, download software and data from the
Huawei iManager M2000, and install the software.
⚫ USB commissioning is supported. The associated software and data of the eNodeB can be
copied to a USB disk at the administration center. A local commissioning engineer only
needs to obtain the USB disk, install the hardware, and connect the USB disk to the USB
port on the eNodeB. After that, the eNodeB can automatically install the software and load
data, start up, and set up the connection to the Huawei iManager M2000. No more local
configuration is required.
⚫ This feature simplifies eNodeB commissioning.
Enhancement
None
Dependencies
The optimized eNodeB commissioning solution depends on the Huawei iManager M2000.
USB commissioning requires USB disks.
1.55 TDLBFD-004012 Environment Monitoring

Availability

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

Availability
Summary
The Huawei iManager M2000 retrieves inventory information automatically from the eNodeB
after commissioning and synchronizing the information on the eNodeB every day.
Benefits
With this function, operators can obtain the timely and accurate inventory data of the existing
network for decision making.
Description
Inventory management helps operators to manage the asset information of the network. With
this function, the assets can be queried and managed on the Huawei iManager M2000.
The objects which are managed by this function include physical objects (such as racks, frames,
slots, boards, ports, and fans) and logical objects (such as software and patches).
When requested from the Huawei iManager M2000, an asset information file in .xml format is
generated and is sent to the Huawei iManager M2000. The Huawei iManager M2000 stores the
uploaded information in the network inventory database.

LTE TDD eRAN6.0
after commissioning and synchronizing the information on the eNodeB every day.
after commissioning.
Enhancement
None
Dependencies
The inventory information can be viewed only on the Huawei iManager M2000.
1.57 TDLBFD-004014 License Management

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

LTE TDD eRAN6.0
Enhancement
None
Dependencies
None
1.58 TDLBFD-004015 License Control for Urgency

Availability
Summary
With this feature, the license limitation is withdrawn in emergencies, so the operator can handle
the sudden increase of network capacity.
Benefits
This feature helps operator to face the situations where there is an unusual increase of traffic
(sport events, New Year…) by enabling a temporary increase of RAN resource, avoiding
permanent over-dimensioning and therefore adapting the capacity costs to the real usage.
Description
The license limitation is withdrawn through manual execution of the MML commands on the
LMT or M2000. Therefore, the equipment can be used effectively to optimum capacity.
For each R version, the operation personnel have three chances to withdraw the license
limitation through the MML commands. The operation takes effect immediately after the
commands are executed. The validity period is seven days. When the three chances are used up,
a new chance can be obtained only through the software upgrade.
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
Feature Description 2 Optional Features
2 Optional Features
2.1 TDLOFD-001016 VoIP Semi-persistent Scheduling

Availability
Summary
Semi-persistent Scheduling is a technique for efficiently assigning resources for spurts of traffic
in a wireless communication system. A semi-persistent resource assignment is valid as long as
more data is sent within a predetermined time period from last sent data, and expires if no data
is sent within the predetermined time period. For VoIP, a semi-persistent resource assignment
may be granted for a voice frame in anticipation of a spurt of voice activity.
Benefits
The semi-persistent scheduling is critical for VoIP services and provides the following benefits:
⚫ Guarantees the QoS for VoIP services.
⚫ Reduces the control signaling overhead for VoIP transmission.
⚫ Maximizes the resource utilization by dynamically activating/deactivating resource
allocation according to the transition between silent period and talk spurt.
Description
This feature is critical to delivery of 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 mms; during the silent period, Silence Indicator (SID) packets arrive at an
interval of 160 Ms.
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

LTE TDD eRAN6.0
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.
Enhancement
None
Dependencies
UE should support semi-persistent.
⚫ TDLOFD-001048 TTI Bundling
⚫ TDLOFD-001007 High Speed Mobility
2.2 TDLOFD-001017 RObust Header Compression

(ROHC)
Availability
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 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 radio link (a portion of the end-to-end path), some of the information

LTE TDD eRAN6.0
become redundant and can be reduced over the link, since they can be transparently recovered
at the receiving side.
ROHC protocol provides an efficient, flexible, and future-proof header compression concept
based on compression/decompression of IP/UDP/RTP/ESP packets header. It is designed to
operate efficiently and robustly over various link technologies with different characteristics,
especially for wireless transmission.
In LTE system, the ROHC function is located in Packet Data Convergence Protocol (PDCP)
entities associated with user plane packets. For the UL, the packets are compressed by the UE
and decompressed by the eNodeB; for the DL, the packets are compressed by the eNodeB and
decompressed by the UE.
The relative gain for specific flows or applications depends on the size of the payload used in
each packet. Header compression is expected to significantly improve the bandwidth utilization
for VoIP service with small payload size.
Huawei LTE eNodeB supports profiles 0x0000–0x0004 based on both IPv4 and IPv6. Table 2-1
shows the profile identifiers and their associated header compression protocols.
Table 2-1 ROHC profile identifier and header compression protocol

Profile Identifier Usage
0x0000 No compression
0x0001 RTP/UDP/IP
0x0002 UDP/IP
0x0003 ESP/IP
0x0004 IP
Enhancement
None
Dependencies
UE should support ROHC.
2.3 TDLOFD-001048 TTI Bundling

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

LTE TDD eRAN6.0
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
be performed without waiting for feedback (for example, 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.
According to 3GPP specifications, for LTE TDD only uplink-downlink configuration ratio 0, 1,
6 can support this feature in terms of the number of Uplink subframe.
Enhancement
None
Dependencies
UE should support TTI Bundling.
⚫ TDLBFD-00100701 uplink-downlink subframe configuration type1&2 (Not support
type2)
⚫ TDLOFD-001016 VoIP Semi-persistent Scheduling
⚫ TDLOFD-001058 UL 2x4 MU-MIMO
2.4 TDLOFD-001022 SRVCC to UTRAN

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

LTE TDD eRAN6.0
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
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 2-1 SRVCC from E-UTRAN to UTRAN
Target
UE E-UTRAN MME MSC Server 3GPP IMS
UTRAN/GERAN
Measurement
Reports
Handover to UTRAN/GERAN
required
Initiates SRVCC for voice component
CS handover preparation
Handles PS-PS HO for
non-voice if needed IMS Service Continuity Procedure
To eUTRAN
PS HO response to MME
Coordinates SRVCC
(CS resources)
Handover CMD and PS HO response
Handover
execution
Enhancement
None
Dependencies
This feature depends on the following feature:
⚫ TDLOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN

LTE TDD eRAN6.0
UE should support SRVCC.

This feature needs IMS multimedia telephony.
2.5 TDLOFD-001023 SRVCC to GERAN

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

LTE TDD eRAN6.0
Figure 2-2 SRVCC from E-UTRAN to GERAN
Target
UE E-UTRAN MME MSC Server 3GPP IMS
UTRAN/GERAN
Measurement
Reports
Handover to UTRAN/GERAN
required
Initiates SRVCC for voice component
CS handover preparation
Handles PS-PS HO for
non-voice if needed IMS Service Continuity Procedure
To eUTRAN
PS HO response to MME
Coordinates SRVCC
(CS resources)
Handover CMD and PS HO response
Handover
execution
Enhancement
None
Dependencies
⚫ TDLOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN
UE should support SRVCC.
This feature needs IMS multimedia telephony.
2.6 TDLOFD-001033 CS Fallback to UTRAN

Availability
This feature is available in LTE TDD eRAN2.0.
Summary
When UE is in the E-UTRAN and UTRAN coverage overlapped area and E-UTRAN cannot
provide CS-domain services for the UE, we can use CS Fallback to UTRAN to provide
CS-domain service for the UE.
Benefits
We can use CS Fallback to UTRAN to provide CS-domain service for the UE which is camped
in the E-UTRAN that cannot provide any CS-domain service for the UE.

LTE TDD eRAN6.0
Description
The CS Fallback in EPS enables the provisioning of voice and other CS-domain services (for
example, SMS/LCS) by reuse of CS infrastructure when the UE is served by E-UTRAN. A CS
Fallback enabled terminal, connected to E-UTRAN may use UTRAN to establish one or more
CS-domain services. This function is only available in case E-UTRAN coverage is overlapped
by UTRAN coverage.
CS Fallback and IMS-based services shall be able to co-exist in the same operator's network.
The CS Fallback in EPS function is realized by using the SGs interface mechanism between the
MSC Server and the MME.
Figure 2-3 CS Fallback in EPS architecture
Iu-CS
UTRAN
MSC
Uu Server
GERAN
A
Um SGs
UE E-UTRAN MME
LTE-Uu S1-MME
The MGW is not shown in the figure since the CS Fallback in EPS does not have any impacts
on the U-plane handling.
Enhancement
In LTE TDD eRAN6.0, the following functions in this feature are enhanced:
⚫ Blind handover
When a UMTS base station and an eNodeB at the same site use different antenna systems,
the CS fallback success rate for CEUs is low and user experience is affected in the
following scenarios:
− The E-UTRAN cell edge is covered by the UTRAN cell.
− The E-UTRAN cell coverage is larger than the UTRAN cell coverage if the E-UTRAN
frequency band is lower than the UTRAN frequency band.
eRAN6.0 introduces adaptive blind handovers. An eNodeB uses the A1 event to identify
CCUs and CEUs, and applies blind handovers and measurement-based handovers to
CCUs and CEUs, respectively. This reduces the CS fallback delay and the inter-RAT
measurement time for CCUs, and increases the CS fallback success rate for CEUs.
⚫ Fallback based on UMTS cell load
eNodeBs perform circuit switched (CS) Fallback to universal terrestrial radio access
network (UTRAN) cells based on Universal Mobile Telecommunications System (UMTS)
cell load information, which is shared with LTE cells by using the RAN Information
Management (RIM) procedure. RAN is short for radio access network.
Cell load information shared between a radio network controller (RNC) and an eNodeB is
used in target cell selection for CS fallback. This increases the success rate of CS Fallback
to UTRAN, prevents unnecessary delay and signaling overhead, and improves user
experience.

LTE TDD eRAN6.0
Dependencies
UE should support CSFB.
This feature depends on the following features:
⚫ TDLOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN.
Target cell load–based CS Fallback to UTRAN requires the core network and RNC to support
RIM-based load information transfer to E-UTRAN.
⚫ TDLOFD-001035 CS Fallback to CDMA2000 1xRTT
⚫ TDLOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT
2.7 TDLOFD-001034 CS Fallback to GERAN

Availability
This feature is available in LTE TDD eRAN2.1.
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
The CS Fallback in EPS enables the provisioning of voice and other CS-domain services (for
example, SMS/LCS) by reuse of CS infrastructure when the UE is served by E-UTRAN. A CS
Fallback enabled terminal, 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.
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.

LTE TDD eRAN6.0
Figure 2-4 CS Fallback in EPS architecture
Iu-CS
UTRAN
MSC
Uu Server
GERAN
A
Um SGs
UE E-UTRAN MME
LTE-Uu S1-MME
The MGW is not shown in the figure since the CS Fallback in EPS does not have any impacts
on the U-plane handling.
Enhancement
⚫ Blind handover
When a GSM base station and an eNodeB at the same site use different antenna systems,
− The E-UTRAN cell edge is covered by the GERAN cell.
− The E-UTRAN cell coverage is larger than the GERAN cell coverage if the E-UTRAN
frequency band is lower than the GERAN frequency band.
Dependencies
The enhancement of CS Fallback to GERAN requires support from Huawei GERAN network
elements (NEs) and eCoordinator.
UEs must support CS fallback.

LTE TDD eRAN6.0
2.8 TDLOFD-001035 CS Fallback to CDMA2000 1xRTT

Availability
Summary
When a UE is located in the area overlapped by the E-UTRAN and the CDMA2000 1x radio
transmission technology (CDMA2000 1xRTT) network and the E-UTRAN cannot provide CS
services for the UE, CS Fallback to CDMA2000 1xRTT helps to provide CS services for the UE.
CDMA is short for Code Division Multiple Access.
eNodeBs support the following functions related to CS fallback:
⚫ Redirection-based CS Fallback (Release 8)
⚫ e1xCSFB (Release 9)
⚫ Transmission and reception of short messages for UEs in the LTE network without
Fallback to CDMA2000 1xRTT
Benefits
CS Fallback to CDMA2000 1xRTT helps to provide CS services for UEs when the E-UTRAN
cannot provide CS services.
Description
CS Fallback in the evolved packet system (EPS) enables CS services to be provided by reusing
CS infrastructures when the UE is served by the E-UTRAN. A CS-fallback-capable UE,
connected to the E-UTRAN, can use CDMA2000 1xRTT to establish one or more CS services.
CS Fallback and IMS-based services are available in the same operator's network. IMS is short
for IP multimedia subsystem.
CS Fallback in the EPS is implemented by using the S102 interface between the 1xCS IWS and
the MME. 1xCS IWS is short for Circuit Switched Fallback Interworking Solution Function for
3GPP2 1xCS.
The S102 interface provides a tunnel between the MME and the 1xCS IWS to transfer 3GPP2
1xCS signaling messages.

LTE TDD eRAN6.0
Figure 2-5 CS Fallback to CDMA2000 1xRTT

1xCS
CSFB 1xRTT CS A1 1xRTT
UE Access MSC
A1
1xCS IWS
S102
MME
S1-MME S11
1xCS Serving/PDN SGi

E-UTRAN
CSFB GW
UE S1-U
Tunnelled 1xRTT messages
NOTE
The media gateway (MGW) is not shown in the figure because CS Fallback in the EPS has no impact on
user-plane processing.
Enhancement
None
Dependencies
The MME must support CS Fallback and e1xCSFB.
The 1xCS IWS must support CS Fallback and enhanced CS fallback. The 1xCS IWS may be
integrated into another NE, such as a CBSC newly deployed in the CDMA2000 1xRTT
network.
UEs must support CS Fallback and e1xCSFB.
⚫ TDLOFD-001033 CS Fallback to UTRAN
⚫ TDLOFD-001034 CS Fallback to GERAN
⚫ TDLOFD-001052 Flash CS Fallback to UTRAN
⚫ TDLOFD-001053 Flash CS Fallback to GERAN
⚫ TDLOFD-001068 CS Fallback with LAI to UTRAN
⚫ TDLOFD-001069 CS Fallback with LAI to GERAN
⚫ TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering
⚫ TDLOFD-001088 CS Fallback Steering to UTRAN
⚫ TDLOFD-001089 CS Fallback Steering to GERAN

LTE TDD eRAN6.0
2.9 TDLOFD-001052 Flash CS Fallback to UTRAN

Availability
Summary
When the RAN Information Management (RIM) procedure is supported by UEs, and the core
networks and RANs in both LTE and UMTS systems, flash CS fallback to UTRAN provides a
decreased delay on CS service access.
Flash CS fallback to UTRAN complies with 3GPP R9 specifications.
When the conditions described above are not satisfied (that is, the networks and UEs do not
support 3GPP R9 specifications), flash CS fallback feature to UTRAN can also be
accomplished by using blind CS fallback.
Benefits
This feature decreases CS service access delay to improve user experience. The delay in flash
CS fallback to UTRAN is about 1 second shorter than CS fallback defined in 3GPP R8
specifications, and close to the delay in UMTS calls.
Description
The RIM procedure is accomplished with the MME and the GSM/UMTS core network, which
transparently forwards the request to the target GSM/UMTS cell. Then, the target cell
encapsulates the system information and sends it back to the LTE cell.
The eNodeB can obtain the system information of the GSM/UMTS neighboring cells with the
RIM procedure based on 3GPP R9 specifications. The system information can be sent to the UE
during flash CS fallback so that the steps of requesting and updating the system information can
be omitted or partially omitted. As a result, the delay is reduced in CS Fallback.
A UE can benefit from blind CS fallback regardless of whether the UE complies with 3GPP R9
specifications. When a neighboring cells supporting blind handover has been configured for an
LTE cell, blind handover definitely decreases the delay in measurement and SI access.
Enhancement
⚫ Blind handover
When a UMTS base station and an eNodeB at the same site use different antenna systems,
− The E-UTRAN cell edge is covered by the UTRAN cell.
− The E-UTRAN cell coverage is larger than the UTRAN cell coverage if the E-UTRAN
frequency band is lower than the UTRAN frequency band.

LTE TDD eRAN6.0
⚫ Redirection
According to 3GPP specifications, a UE selects a cell regardless of whether the cell sends
an SIB to the UE. If the cell selected by the UE sends an SIB to the UE, the UE skips the
step for obtaining the system information from the cell. Therefore, the flash CS fallback
success rate increases with the number of cells that send SIBs to UEs.
In LTE TDD eRAN6.0, a parameter is added to these cells. Operators can set this parameter to
specify the number of cells for redirection based on the performance of the live network.
Dependencies
The core network and UEs must comply with 3GPP R9 specifications.
2.10 TDLOFD-001053 Flash CS Fallback to GERAN

Availability
Summary
When the RIM procedure is supported by UEs, and the core networks and RANs in both LTE
and GSM systems, flash CS fallback to GERAN provides a decreased delay on CS service
access.
Flash CS fallback to GERAN complies with 3GPP R9 specifications.
When the conditions described above are not satisfied (that is, the networks and UEs do not
support 3GPP R9 specifications), flash CS fallback feature to GERAN can also be
accomplished by using blind CS fallback.
Benefits
This feature decreases CS service access delay to improve user experience. The delay in flash
CS fallback to GERAN is about 2 second shorter than CS fallback defined in 3GPP R8
specifications, and close to the delay in GSM calls.
Description
The RIM procedure is accomplished with the MME and the GSM/UMTS core network, which
transparently forwards the request to the target GSM/UMTS cell. Then, the target cell
encapsulates the system information and sends it back to the LTE cell.
The eNodeB can obtain the system information of the GSM/UMTS neighboring cells with the
RIM procedure based on 3GPP R9 specifications. The system information can be sent to the UE

LTE TDD eRAN6.0
during flash CS fallback so that the steps of requesting and updating the system information can
be omitted or partially omitted. As a result, the delay is reduced in CS Fallback.
A UE can benefit from blind CS fallback regardless of whether the UE complies with 3GPP R9
specifications. When a neighboring cells supporting blind handover has been configured for an
LTE cell, blind handover definitely decreases the delay in measurement and SI access.
Enhancement
⚫ Blind handover
When a GSM base station and an eNodeB at the same site use different antenna systems,
− The E-UTRAN cell edge is covered by the GERAN cell.
− The E-UTRAN cell coverage is larger than the GERAN cell coverage if the E-UTRAN
frequency band is lower than the GERAN frequency band.
⚫ Redirection
According to 3GPP specifications, a UE selects a cell regardless of whether the cell sends
an SIB to the UE. If the cell selected by the UE sends an SIB to the UE, the UE skips the
step for obtaining the system information from the cell. Therefore, the flash CS fallback
success rate increases with the number of cells that send SIBs to UEs.
In LTE TDD eRAN6.0, a parameter is added to these cells. Operators can set this parameter to
specify the number of cells for redirection based on the performance of the live network.
Dependencies
This feature depends on the 3GPP R9 compliant core network and 3GPP R9 compliant UE.
2.11 TDLOFD-001068 CS Fallback with LAI to UTRAN

Availability

LTE TDD eRAN6.0
Summary
By new defined LAI IE, eNodeB can solve the difference of target RAT selecting between the
eNodeB and MME and 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 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
does not know the capability of UE; MME also maintains the mapping relationship 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, 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 network in which CSFB depends on a 3G network, 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
Dependencies
UE supports R8 or R9 CSFB.
MME needs to support the LAI IE.
2.12 TDLOFD-001069 CS Fallback with LAI to GERAN

Availability
This feature was introduced in LTE TDD eRAN3.0

LTE TDD eRAN6.0
Summary
By new defined LAI IE, eNodeB can solve the difference of target RAT selecting between the
eNodeB and MME and 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 network in which CSFB depends on a 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
does not know the capability of UE; MME also maintains the mapping relationship between the
TA and LA, the LA belongs to the attached 2G MSC;
MME sends the LA to eNodeB through 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
Dependencies
UE supports R8 or R9 CSFB.
MME needs to support the LAI IE.
2.13 TDLOFD-001088 CS Fallback Steering to UTRAN

Availability

LTE TDD eRAN6.0
Summary
Huawei eNodeBs support CS Fallback steering to UTRAN based on the UE status, target radio
access technology (RAT) priorities, target UTRAN frequency priorities, and CS Fallback
mechanism priorities.
Benefits
With this feature, operators who have deployed both an E-UTRAN and a UTRAN can achieve
CS Fallback of UEs to a specified RAT or inter-RAT frequency based on the network plan and
load balancing requirements.
Description
CS Fallback steering to UTRAN can be performed based on the following configurations:
⚫ UE status, including idle (supporting CS only) and active (supporting CS and PS)
⚫ Priorities of RATs, including GERAN and UTRAN
⚫ Priorities of UTRAN frequencies, including R99 and High Speed Packet Access (HSPA)
⚫ Priorities of CS Fallback mechanisms, including PS handover, PS redirection, and flash
CS fallback
The preceding configurations can be modified.
PS is short for packet switched.
Enhancement
None
Dependencies
⚫ TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering.
If TDLOFD-001068 CS Fallback with LAI to UTRAN is activated, CS Fallback steering to
UTRAN considers the location area identity (LAI) during target RAT selection.
2.14 TDLOFD-001089 CS Fallback Steering to GERAN

Availability

LTE TDD eRAN6.0
Summary
Huawei eNodeBs support CS Fallback steering to GERAN based on the UE status, target RAT
priorities, and CS Fallback mechanism priorities.
Benefits
With this feature, operators who have deployed both an E-UTRAN and a GERAN can achieve
CS Fallback of UEs to a specified RAT or inter-RAT frequency based on the network plan and
load balancing requirements.
Description
CS Fallback steering to GERAN can be performed based on the following configurations:
⚫ UE status, including idle (supporting CS only) and active (supporting CS and PS)
⚫ Priorities of RATs, including GERAN and UTRAN
⚫ Priorities of CS Fallback mechanisms, including PS handover, PS redirection, cell change
order/network assisted cell change (CCO/NACC), and flash CS fallback
The preceding configurations can be modified.
Enhancement
None
Dependencies
If operators require prioritization of GERAN and UTRAN frequencies for CS Fallback steering,
they must also deploy TDLOFD-001088 CS Fallback Steering to UTRAN.
If TDLOFD-001069 CS Fallback with LAI to GERAN is activated, CS Fallback steering to
GERAN considers the LAI during target RAT selection.
2.15 TDLOFD-001090 Enhanced CS Fallback to CDMA2000

1xRTT
Availability

LTE TDD eRAN6.0
Summary
If an operator has deployed a CDMA2000 1xRTT network and an E-UTRAN, UEs in the
overlapping area preferentially camp in the E-UTRAN. However, the operator often requires
that the CDMA2000 1xRTT network and E-UTRAN provide CS and PS services for UEs,
respectively. To meet such requirements, enhanced CS Fallback has been designed to ensure
that UEs are handed over to the CDMA2000 1xRTT network when initiating CS services in the
overlapping area.
Benefits
With enhanced CS fallback, UEs can be quickly handed over from the E-UTRAN to the
CDMA2000 1xRTT network to initiate or receive CS services. This quick handover improves
user experience. For example, when a UE is handed over to the CDMA2000 1xRTT network to
receive a CS service, the enhanced CS Fallback procedure takes only 2 to 3 seconds, which is
faster than the normal CS Fallback procedure.
Description
Enhanced CS Fallback in the 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 feature is only available when
CDMA2000 1xRTT coverage overlaps with E-UTRAN coverage.
Enhanced CS Fallback and IMS-based services are available in the same operator's network.
Enhanced CS Fallback in the EPS is implemented using the S102 interface between the 1xCS
IWS and the MME. The S102 interface provides a tunnel between the MME and the 1xCS IWS
to transfer 3GPP2 1xCS signaling messages.
Figure 2-6 Enhanced CS Fallback to CDMA2000 1xRTT

LTE TDD eRAN6.0
NOTE
⚫ S-GW is short for serving gateway, P-GW is short for PDN gateway, and PDN is short for packet data
network.
⚫ The MGW is not shown in the figure because enhanced CS Fallback in the EPS has no impact on
user-plane processing.
During an enhanced CS Fallback procedure, the eNodeB hands over the UE to the target
CDMA2000 1xRTT network to perform CS services. If the UE is performing PS services in the
E-UTRAN, the eNodeB redirects the ongoing PS services to the evolved high rate packet data
(eHRPD) network.
Enhancement
None
Dependencies
This feature depends on TDLOFD-001035 CS Fallback to CDMA2000 1xRTT and
TDLOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000.
If TDLOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000 is not
enabled, enhanced CS fallback with concurrent non-optimized PS handover cannot work and
other functions in TDLOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT are not
affected.
The CDMA2000 1xRTT network must support CS Fallback and enhanced CS fallback. NEs on
the network include the 1xCS IWS, CBSC, and CBTS.
The MME must support CS Fallback and enhanced CS fallback.
UEs must support CS Fallback and enhanced CS fallback.
If CS Fallback to CDMA2000 1xRTT is enabled, eNodeBs do not support CS Fallback to
GERAN or CS Fallback to UTRAN. If CS Fallback to GERAN or UTRAN is enabled,
eNodeBs do not support CS Fallback to CDMA2000 1xRTT.
⚫ TDLOFD-001052 Flash CS Fallback to UTRAN
⚫ TDLOFD-001053 Flash CS Fallback to GERAN
⚫ TDLOFD-001068 CS Fallback with LAI to UTRAN
⚫ TDLOFD-001069 CS Fallback with LAI to GERAN
⚫ TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering
⚫ TDLOFD-001088 CS Fallback Steering to UTRAN
⚫ TDLOFD-001089 CS Fallback Steering to GERAN

LTE TDD eRAN6.0
2.16 TDLOFD-001047 LoCation Services(LCS)

Availability
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, and velocity. 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 software, or for location requirements in emergency call/lawful interception
situations. For example, For E911 service, 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 Center) is
needed to support this feature. It is an independent network element in LTE core network or
integrated in the MME.
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:
1. MME receives LCS requirement for a target UE location, or MME starts LCS service by
itself.
2. MME sends LCS requirement to E-SMLC.
3. E-SMLC sends auxiliary data to UE and checks related measurement information from
UE/eNodeB. E-SMLC calculates location information of target UE and forwards the
information to MME.
4. If MME does not host the LCS, MME will forward the location information to the network
element which hosts the LCS.
Enhancement
None
Dependencies
UE should support LCS for A-GPS and OTDOA.
OTDOA requires Time synchronization for E-UTRAN.

LTE TDD eRAN6.0
MME should support LPPa protocol.

E-SMLC is required.
2.17 TDLOFD-001001 DL 2x2 MIMO

Availability
Summary
Huawei LTE TDD eRAN1.0 supports DL 2x2 MIMO, 2-antenna transmit diversity and
adaptive MIMO schemes between the UE and the eNodeB, improving system downlink
performance.
Benefits
This feature can significantly improve downlink system throughput and coverage performance
and also provide good user experience by offering higher data rates.
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. Downlink 2x2 MIMO is
supported in Huawei LTE TDD eRAN1.0. Both space diversity and spatial multiplexing are
supported as defined in LTE specifications, so Huawei eNodeB supports two DL 2x2 MIMO
modes:
⚫ transmit diversity
⚫ open-loop spatial multiplexing
If two transmit antennas are configured in the eNodeB, the eNodeB adaptively selects one of
the two modes based on UE rate and channel quality on the downlink.
Transmit diversity is a solution to combat signal fading and interference. By providing several
signal branches that present independent varying signal levels, space diversity increases the
robustness of the radio link because the probability that all signal copies are simultaneously in
deep fading is low.
Spatial multiplexing is a technique to transmit independent and separately encoded data signals,
known as streams, from each of the transmit antennas. Therefore, the space dimension is reused,
or multiplexed. If the transmitter is equipped with Ntx antennas and the receiver has Nrx
antennas, the maximum spatial multiplexing order is Ns = min (Ntx, Nrx). If the spatial channels
are independent of each other, which means that Ns different data streams are transmitted over
several independent (spatial) channels, it leads to an Ns increase of the spectrum efficiency or
capacity.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
The eNodeB must be configured with two transmit channels and two antennas per sector, and
the UE must be configured with a minimum of two antennas for receiving.
2.18 TDLOFD-001030 Support of UE Category 2/3/4

Availability
Summary
protocol. This feature can enable base station to support UE category 2/3/4.
Benefits
This feature can enable base station to support UE category 2/3/4.
Description
protocol. This feature can enable BS to support UE category 2/3/4.
Downlink physical layer parameter values set by the field ue-Category:
UE Maximum number of Maximum number of Total Maximum number

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

Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Uplink physical layer parameter values set by the field ue-Category:
UE Category Maximum number of bits of an UL-SCH Support for 64QAM in UL

transport block transmitted within a TTI
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No

LTE TDD eRAN6.0
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
Enhancement
None
Dependencies
UE should support the same category as eNodeB.
2.19 TDLOFD-001005 UL 4-Antenna Receive Diversity

Availability
Summary
Besides UL 2-Antenna Receive Diversity, Huawei eNodeB also supports 4 RX diversity.
Benefits
This feature can improve the uplink coverage and throughput.
Description
Receive diversity is a technique to monitor multiple frequencies from the same signal source or
multiple radios and antennas monitoring the same frequency, to combat signal fading and
interference.
Receive diversity is a way to enhance the reception of uplink channels, including the PUSCH,
physical uplink control channel (PUCCH), physical random access channel (PRACH), and
sounding reference signal (SRS).
Huawei eNodeB supports both with RX diversity mode and without RX diversity mode. In RX
diversity mode, Huawei eNodeB in LTE TDD eRAN2.1 can be configured with 4 antennas
(4-way) through the antenna magnitude parameter in addition to UL 2-antenna receive
diversity.

LTE TDD eRAN6.0
Enhancement
None
Dependencies
This feature cannot support LampSite.
This feature cannot work when the channel bandwidth of eNodeB(with LBBPc board) is 5
MHz.
2.20 TDLOFD-001058 UL 2x4 MU-MIMO

Availability
Summary
Huawei LTE TDD eRAN2.2 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
If four receive antennas are configured in eNodeB, eNodeB can use UL 2x4 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 CQI 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
In LTE TDD eRAN6.0, UL 2x4 MU-MIMO can support subframe assignment 0.
Dependencies
This feature needs eNodeB to provide 4 RX channels and 4 antennas per sector.

LTE TDD eRAN6.0

⚫ TDLOFD-001015 Enhanced Scheduling
⚫ TDLOFD-001005 UL 4-Antenna Receive Diversity
⚫ TDLOFD-001094 Control Channel IRC
This feature cannot coexist with following features on LBBPc:
2.21 TDLOFD-001006 UL 64QAM

Availability
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 is located very close to the eNodeB or 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

LTE TDD eRAN6.0
Dependencies
This feature can be used only for UEs in excellent channel condition.
2.22 TDLOFD-001012 UL Interference Rejection

Combining
Availability
Summary
Besides DL and UL inter-cell interference coordination (ICIC), Huawei LTE TDD eRAN1.0
provides interference rejection combining to effectively overcome the inter-cell interference.
The method can be used with receive diversity and can be used for MIMO decoding in any
scenario.
Benefits
This feature can improve the system performance in the presence of interference. Therefore,
enhanced network coverage and better service quality are provided for cell edge users (CEUs).
Description
Interference Rejection Combining (IRC) is a receive-antenna combining technique to
effectively combat the inter-cell interference. IRC is often used together with receive diversity.
In theory, IRC can be used for Multiple Input Multiple Output (MIMO) decoding in any
scenario, and it is particularly effective for colored interference.
The main advantage of IRC lies in that it can outperform Maximum Ratio Combining (MRC) in
terms of demodulation of a signal in the presence of interference or jamming.
Enhancement
None
Dependencies
eNodeB should be equipped with multiple receive antennas (equal to or more than two).
2.23 TDLOFD-001094 Control Channel IRC

Availability

LTE TDD eRAN6.0
Summary
Control channel interference rejection combining (IRC) prevents the PUCCH and physical
random access channel (PRACH) from being affected by inter-cell interference.
Benefits
Control channel IRC enhances interference resistance for uplink control channels and improves
control channel coverage.
Description
IRC combines signals on the PUCCH and PRACH received by multiple antennas. Compared
with maximum ratio combining (MRC), IRC performs better on colored interference
mitigation.
eNodeBs support adaptive switching between IRC and MRC for PUCCHs and PRACHs. When
there is colored interference, eNodeBs select IRC. In other cases, eNodeBs select MRC.
Enhancement
None
Dependencies
This feature depends on either of the following features:
⚫ TDLBFD-00202001 UL 2-Antenna Receive Diversity
eNodeBs must be equipped with two or more receive antennas, the LBBPd board.
2.24 TDLOFD-001049 Single Streaming Beamforming

Availability
Summary
This feature provides functions.
Downlink 4x2, 8x2 Beamforming which can significantly improve downlink system
throughput and coverage performance and also provide good user experience by offering higher
data rates.
Benefits
This feature can significantly improve downlink/uplink system throughput (especially for cell
edge user) and coverage performance.

LTE TDD eRAN6.0
Description
The classical technique of using an antenna array for transmitting energy in the direction of the
intended receiver falls into the category of improving SINR. Beamforming achieves increased
SINR by phase adjustments of the signals transmitted on the different antennas with the aim of
making the signals add-up constructively on the receive side. Huawei LTE TDD eRAN2.1
provides support on DL 8x2 and DL 4x2 Beamforming.
This feature can significantly improve downlink/uplink system throughput (especially for cell
edge user) and coverage performance.
Enhancement
None
Dependencies
The eNodeB must be configured with a minimum of four antennas for transmission.
UE should support TM7(R8) Single Streaming Beamforming.
This feature cannot work when the channel bandwidth of eNodeB is 5 MHz.
This feature cannot coexist with following feature:
2.25 TDLOFD-001061 Dual Streaming Beamforming

Availability
Summary
In LTE TDD eRAN2.2, the eNodeB supports dual-stream Beamforming for 3GPP Release
9–compliant UEs. In dual-stream Beamforming mode, two data streams are transmitted on the
same OFDM time-frequency resource. The eNodeB adaptively selects single- or dual-stream
Beamforming based on UE capabilities and channel conditions to increase downlink
throughput.
Benefits
This feature can significantly increase downlink throughput and improve user experience.
Description
Huawei eNodeB also supports dual-stream Beamforming.

LTE TDD eRAN6.0
3GPP Release 9 defines transmission mode (TM8), a new Beamforming transmission mode, to
support dual-stream Beamforming. In dual-stream Beamforming mode, two different and
independently coded data streams are separately transmitted from two logical antenna ports.
Either of the two data streams is generated by four or eight antennas in Beamforming
transmission mode. The two data streams both form directional beams towards the target UE,
which increases the signal to interference plus noise ratio (SINR). Dual-stream Beamforming
incorporates both spatial multiplexing and Beamforming during downlink transmission. This
helps provide partial multiplexing gains, diversity gains, and array gains.
Enhancement
None
Dependencies
UE must be configured with a minimum of two antennas for receiving and support TM8(R9)
Dual Streaming Beamforming.
This feature cannot work when the channel bandwidth of eNodeB is 5 MHz
This feature cannot coexist with TDLOFD-001031 Extended CP.
2.26 TDLOFD-001075 SFN

Availability
Summary
This feature combines multiple common cells to one single frequency network (SFN) cell.
SFN implements the joint scheduling of air interface resources in multiple cells by transmitting
the same data with the same time-frequency resource of different cells.
SFN transforms co-channel interference into useful signals in the downlink, cancels inter-cell
co-channel interference in the uplink, and greatly improves the signal to interference plus noise
ratio (SINR) at the cell edge.

LTE TDD eRAN6.0
Benefits
The SFN feature reduces interference at the cell edge in a densely populated area.
Description
An SFN cell is a combination of multiple common cells, which use the same cell ID and apply
joint time-frequency resource scheduling. The SFN can convert inter-cell interference into the
time-frequency resources scheduled inside the SFN cell, and increase the proportion of UEs
with a high SINR in the entire RAN.
In the downlink, joint scheduling is used, and all RRUs transmit the same signals except the
physical downlink shared channels (PDSCHs) of Beamforming users and UE-specific
reference signals. In the uplink, joint scheduling is used at the physical and Media Access
Control (MAC) layers. According to the measurement reports of a UE at the physical layer, the
MAC layer selects the serving remote radio unit (RRU) with the best channel quality for the UE.
The physical layer processes all signals of the UE and reports only the serving RRU physical
uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) of the UE to the
MAC layer.
In eRAN3.0, a maximum of three cells could be combined into an SFN cell.
Enhancement
In eRAN3.1, eNodeBs supported MU Beamforming and UL CoMP in SFN mode, and allowed
a maximum of seven cells to be combined into an SFN cell.
In LTE TDD eRAN6.0, eNodeBs can work in 2T2R mode only in the LampSite solution.
Dependencies
The eNodeB must be configured with a minimum of two antennas for transmission and
receiving.
⚫ TDLBFD-002022 Static Inter-Cell Interference Coordination
⚫ SEFD-033100 Adaptive Inter-Cell Interference Coordination – LTE
⚫ TDLAOFD-001001 Carrier Aggregation Introduction Package (Two Component
Carriers)
⚫ TDLAOFD-003001 DL CoMP Introduction Package
The LBBPc cannot support this feature to coexist with TDLOFD-001058 UL 2x4 MU-MIMO.

LTE TDD eRAN6.0
2.27 TDLOFD-002008 Adaptive SFN/SDMA

Availability
Summary
When multiple common cells are combined into an SFN cell, the eNodeB classifies the users
according to their signal quality, and implements adaptive joint scheduling and independent
scheduling of time-frequency resources in multiple cells. 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 improves system throughput while
ensuring coverage quality.
Description
An SFN cell includes multiple common cells. 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
In LTE TDD eRAN6.0, eNodeBs support 2T2R mode only in the LampSite solution.
Dependencies
⚫ TDLBFD-002022 Static Inter-Cell Interference Coordination
Carriers)

LTE TDD eRAN6.0

The LBBPc cannot support this feature to coexist with TDLOFD-001058 UL 2x4 MU-MIMO.
2.28 TDLOFD-001098 Inter-BBP SFN

Availability
Summary
The RRUs serving an SFN cell can be connected to different LBBPs in the same baseband unit
(BBU), and can implement joint scheduling of time-frequency resources in multiple cells.
Benefits
This feature expands the application range of SFN.
Description
An inter-BBP connection enables communication between different cells and allows the SFN
feature to be more widely used.
Enhancement
Dependencies
⚫ TDLBFD-00100701 uplink-downlink subframe configuration type1&2 (not support
type1)
Carriers)
LBBPc board cannot support this feature to coexist with TDLOFD-001058 UL 2x4
MU-MIMO.

LTE TDD eRAN6.0
If the SFN cells are LampSite cells, the following feature is needed:
⚫ TDLOFD-001132 Intra-BBU Baseband Sharing (2T)
⚫ TDLOFD-001076 CPRI Compression
2.29 TDLOFD-001080 Inter-BBU SFN

Availability
Summary
RRUs composing an SFN cell could be physically connected to different BBUs, and implement
the joint scheduling of multiple calls time frequency resource.
Benefits
This feature expands the application range of SFN. When the RRUs composing an SFN cell are
changed according to the network planning, it is not required to adjust the physical RRU
connection.
Description
By BBU interconnection with USU (Universal Switch Unit), to achieve the communication
between different cells, the SFN can be used at a larger range.
Enhancement
None
Dependencies
type1)
Carriers)

LTE TDD eRAN6.0

MU-MIMO.
BBUs implement interconnection by USU3900.
2.30 TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA

Availability
Summary
The RRUs serving an SFN cell can be connected to different LBBPs in the same BBU, and can
implement joint scheduling and independent scheduling of time-frequency resources in
multiple cells.
Benefits
This feature expands the application range of Adaptive SFN/SDMA.
Description
An inter-BBP connection enables communication between different cells and allows the
Adaptive SFN/SDMA feature to be more widely used.
Enhancement
Dependencies
type1)

LTE TDD eRAN6.0

Carriers)
MU-MIMO.
If the SFN cells are LampSite cells, the following feature is needed:
⚫ TDLOFD-001132 Intra-BBU Baseband Sharing (2T)
⚫ TDLOFD-001076 CPRI Compression
2.31 TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA

Availability
Summary
RRUs composing an SFN cell could be physically connected to different BBUs, and implement
the joint scheduling/respective of multiple calls time frequency resource.
Benefits
This feature expands the application range of Adaptive SFN/SDMA. When the RRUs
composing an SFN cell are changed according to the network planning, it is not required to
adjust the physical RRU connection.
Description
By BBU interconnection with USU (Universal Switch Unit), to achieve the communication
between different cells, the Adaptive SFN/SDMA can be used at a larger range.
Enhancement
None
Dependencies

LTE TDD eRAN6.0

type1)
Carriers)
MU-MIMO.
BBUs implement interconnection by USU3900.
2.32 TDLOFD-001077 Multi-User Beamforming

Availability
Summary
In LTE TDD eRAN3.0, the eNodeB supports transmission mode (TM) 8 for 3GPP Release 9. In
TM8, logical antenna port7 and port8 are defined and these 2 ports are scrambled by two
orthogonal DRS (dedicated reference sequence) sequences. When it simultaneously allocated
to two different users, one uses port7, another uses port8, two data streams from two users are
transmitted on the same OFDM time-frequency resource. The eNodeB decides which users to
pair based on pairing conditions to increase downlink throughput.
Benefits
This feature can significantly increase downlink throughput and improve user experience.
Description
3GPP Release 9 defines transmission mode (TM) 8 to support dual-stream Beamforming. In
TM8 mode, two different and independently coded data streams are separately scrambled by
two orthogonal DRS sequences and transmitted from two logical antenna ports.
Once two users in TM8 mode with single-stream Beamforming, each user will use one logical
antenna port. If these 2 users meet pairing conditions, eNodeB will generate two orthogonal
beams separately toward the pairing users and the beams are formed by means of zero-force
(ZF). Multi-user Beamforming incorporates spatial multiplexing and increases spectrum
efficiency during downlink transmission.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
UE should support TM8 (adaptive single/dual-stream Beamforming)
The LBBPc cannot support this feature.
2.33 TDLOFD-001066 Intra-eNodeB UL CoMP

Availability
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.
Benefits
This feature provides better UL throughput for cell edge users between 2 cells of one eNodeB.
Description
Two scenarios will encounter CoMP utilization.
In first scenario, which is called joint receiving scenario, this feature uses two adjacent cells
(each with 2 RX channels), 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 to attenuate the interference on the UEs using the same PRBs in the
co-operating cell.

LTE TDD eRAN6.0
Enhancement
In LTE TDD eRAN6.0, eNodeBs can work in 4T4R mode.
Dependencies
This feature is only applicable to macro eNodeBs.
The total number of activated cells in one LBBP must be equal to or less than 3.
This feature can coexist but cannot work simultaneously with TDLOFD-001058 UL 2x4
MU-MIMO.
When the UlHoppingType parameter in the CellUlschAlgo MO is set to Hopping_OFF, UL
CoMP is disabled.
This feature cannot apply to the scenario where the RRU is installed far from the BBU.
2.34 TDLOFD-001132 Intra-BBU Baseband Sharing (2T)

Availability
This feature is available from LTE TDD eRAN6.0.
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
In the LampSite solution, this feature converges the data of multiple cells on one LBBP, which
transmits the data by using one optical fiber. This decreases the number of required optical
cables and therefore reduces the deployment cost.

LTE TDD eRAN6.0
Description
In a BBU, the LBBPs are connected by using the backplane to share baseband resources, as
shown in the following figure.
2 3
0 1 4 5
In the preceding figure, all baseband resources in a BBU are converged on the LBBPs in slots 2
and 3.
In LTE TDD eRAN6.0, each LBBPc or LBBPd can process the service data of three 20 MHz
cells served by 2T2R RRUs. The following table lists the baseband resource convergence
principles.
Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5
Slot 0 N/A Y Y Y N N
Slot 1 Y N/A Y Y N N
Slot 2 Y Y N/A Y Y Y
Slot 3 Y Y Y N/A Y Y
Slot 4 N N Y Y N/A Y
Slot 5 N N Y Y Y N/A
NOTE
In the preceding table, Y indicates that the resources of the LBBPc or LBBPd boards in two slots can be
converged, and N indicates that the resources of the LBBPc or LBBPd boards in two slots cannot be
converged.
Enhancement
None
Dependencies
This feature is available only for the LampSite solution.
The resources of the LBBP in slot 0 or 1 cannot be converged with the resources of the LBBP in
slot 4 or 5.

LTE TDD eRAN6.0
When an LBBPc is used for baseband resource convergence, the LBBPc cannot be connected to
the optical fiber.
2.35 TDLOFD-001062 UL 8-Antenna Receive Diversity

Availability
Summary
Besides UL 2-Antenna and UL 4-Antenna Receive Diversity, Huawei eNodeB also supports 8
RX diversity.
Benefits
This feature can improve the uplink coverage and throughput.
Description
Receive diversity is a technique to monitor multiple frequencies from the same signal source or
multiple radios and antennas monitoring the same frequency, in order to combat signal fading
and interference.
Receive diversity is a way to enhance the reception of uplink channels, including the PUSCH,
physical uplink control channel (PUCCH), physical random access channel (PRACH), and
sounding reference signal (SRS).
Huawei eNodeB supports both with RX diversity mode and without RX diversity mode. In RX
diversity mode, Huawei eNodeB in LTE TDD eRAN2.1 can be configured with 8 antennas
(8-way) through the antenna magnitude parameter in addition to UL 2-antenna and 4-antenna
receive diversity.
Enhancement
None
Dependencies
This feature cannot work when the channel bandwidth of eNodeB is 5 MHz.

LTE TDD eRAN6.0
2.36 TDLOFD-001028 TCP Proxy Enhancer (TPE)

Availability
Summary
A series of enhanced TCP functions adaptive to the link characteristics on the RAN side 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, thereby improving user
experience and system efficiency.
Benefits
This feature mitigates the impact of some factors such as packet loss in the RAN side to affect
negatively the performance of TCP data transmission, accelerates the slow startup and fast
retransmission of the server during the data transmission, 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 exhibit some
characteristics quite different from the wired network. To mitigate this effect, a number of
enhancements have been implemented in the eNodeB.
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, DupACK
duplication, and local retransmission. This feature accelerates the slow startup and congestion
avoidance of the server. 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 recover the congestion window; when the
sender in congestion avoidance mode, ACK splitting can accelerate the expansion of the
congestion window.
⚫ DupACK duplication
In TCP, a lost TCP packet is retransmitted after three DupACK are received. With this
feature, after the TPE receives the ACK message from the UE, the TPE immediately
duplicates three DupACK messages and sends them to the server if it detects that the
packets dropped before eNodeB. This shortens the time for packet retransmission.
⚫ Local retransmission
When packet loss occurs on the UE, the TPE retransmits the packet to the receiving end,
reducing the time for retransmission.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
None
2.37 TDLOFD-001054 Flexible User Steering

2.37.1 TDLOFD-00105401 Camp & Handover Based on SPID
Availability
Summary
This feature is used in the scenarios under which the operator wants to control the mobility of an
UE to make it camp in, redirect or handover to a suitable cell. The priorities for the cell
selection are 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, an 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 an LTE cell.
Description
The SPID is an index referring to user information (such as 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 to apply specific RRM
strategies (such as defining RRC_IDLE mode priorities and controlling 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.
Therefore, operator can configure and push subscribers into the suitable cell according its
subscription. For example: a dongle user usually stays in an LTE high frequency band for a high
service rate; a VoIP user is prior to stay in an LTE low frequency band to guarantee the
continuous coverage.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
UE cell reselection policy depends on the following features:
⚫ TDLBFD-00201803 Cell Selection and Re-selection
Load based UE handover policy depends on the following features:
⚫ TDLOFD-001032 Intra-LTE Load Balancing
⚫ TDLOFD-001044 Inter-RAT Load Sharing to UTRAN
⚫ TDLOFD-001045 Inter-RAT Load Sharing to GERAN
UE HPLMN switch policy depends on either of the following features:
⚫ TDLBFD-00201802 Coverage Based Inter-frequency
This feature depends on SAE to support the SPID configuration.
GSM/UMTS network should support this function to avoid Ping-Pong handover.
2.38 TDLOFD-001059 UL Pre-allocation Based on SPID

Availability
Summary
Operator can configure a suitable SPID (Subscriber Profile ID for RAT/Frequency Priority) in
core network for each UE. When a UE accesses 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 (such as 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 to apply specific RRM
strategies.
Operator can configure a suitable SPID in core network for each UE. When a UE accesses 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.

LTE TDD eRAN6.0
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
Dependencies
This feature depends on SAE to support the SPID configuration.
2.39 TDLOFD-001133 Multi Operators SPID Policy

Availability
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 0 to 255) for UEs in a home
subscriber server (HSS) database. Based on the SPID, an eNodeB then 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 based only 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
Dependencies

LTE TDD eRAN6.0
⚫ TDLBFD-00201803 Cell Selection and Re-selection

⚫ TDLOFD-001054 Flexible User Steering
2.40 TDLOFD-001105 Dynamic DRX

Availability
Summary
In a network with a large number of smartphones, dynamic discontinuous reception (DRX)
reduces signaling for radio resource control (RRC) connections. RRC connections may be
established and released constantly by smartphones for services that use a few small packets or
heartbeat packets. This feature enables smartphones to keep always online with low power
consumption.
Benefits
In addition to conserving smartphone battery power, dynamic DRX can greatly reduce RRC
connection-related signaling to prevent signaling storms.
Description
To save battery power, smartphones 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 heartbeat packets and other instant service messages require the
network to re-establish connections frequently and therefore consume a large amount of
signaling resources.
When such services are used, the network can enable smartphones to remain online. To remain
in the always-online state, the smartphones in RRC_CONNECTED mode must monitor
physical downlink control channels (PDCCHs) and consume uplink physical resources for
sounding reference signals (SRSs) and PUCCHs. As a result, they consume more uplink
resources and energy.
eRAN6.0 introduces the dynamic DRX feature to reduce the amount of signaling and the
consumption of battery power and network resources for smartphones. This feature performs
the following:
⚫ Enables smartphones to remain online to reduce signaling
⚫ Enables smartphones to stay in the uplink out-of-synchronization state to reduce PUCCH
resource consumption
⚫ Configures DRX parameters for the uplink out-of-synchronization state with a longer
DRX cycle to reduce UE power consumption
Enhancement
None

LTE TDD eRAN6.0
Dependencies
⚫ TDLBFD-002017 DRX
2.41 TDLOFD-001106 High-Mobility-Triggered Idle Mode

Availability
Summary
This feature enables a fast-moving UE to switch from the always-online state to idle mode if the
amount of signaling that increases due to frequent UE handovers is greater than the amount of
signaling that decreases when the UE stays in the always-online state.
Benefits
This feature reduces signaling to protect the network against signaling storms.
Description
This feature includes the following functions:
⚫ Checks 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 using applications that require heartbeat messages, such
as IM, Facebook, or Twitter.
With this feature, an eNodeB checks the UE speed, packet transmission status, and
duration when the UE camps on a cell. Based on the check results, the eNodeB determines
whether the UE meets the conditions for entering idle mode to minimize signaling impact.
⚫ Supports feature performance monitoring.
To monitor the performance of this feature, check the control-plane CPU usage and the
number of handovers before and after this feature is enabled.
Enhancement
None
Dependencies
⚫ TDLOFD-001105 Dynamic DRX.

LTE TDD eRAN6.0
2.42 TDLOFD-001015 Enhanced Scheduling

2.42.1 TDLOFD-00101501 CQI Adjustment
Availability
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 inaccurate to some extent, the MCS selection based on the inaccurate CQI will cause a
failure of the DL transmission 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.
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.
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
2.42.2 TDLOFD-00101502 Dynamic Scheduling

Availability
Summary
The dynamic scheduling feature provides the function that 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
Huawei dynamic scheduling solution could provide the following benefits:
⚫ Achieves efficient resource utilization.
⚫ Achieves an optimal tradeoff among throughput, fairness, and the QoS.
Description
The scheduling function facilitates to the achievement of efficient resource utilization on a
shared channel. In an LTE system, the scheduler allocates resources to the UEs every 1 ms or
every one TTI. The scheduling algorithm needs to achieve a good tradeoff between priority
differentiation among different services and the fairness among users.
The UL scheduler uses token bucket algorithm to achieve rate control function 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. 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 DL scheduler employs an enhanced scheduling strategy. 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. 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.
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
2.43 TDLOFD-001109 DL Non-GBR Packet Bundling

Availability
Summary
This feature introduces delay control and bundles downlink packets before transmission.
Benefits
This feature offers the following benefits:
⚫ Reduces PDCCH overhead and increases PDCCH capacity.
⚫ Meets the delay requirements of best effort (BE) services and increases the eNodeB
throughput when users are using both guaranteed bit rate (GBR) and non-GBR services.
Description
This feature primarily introduces delay control for BE services.
When the network load is light and the resources for control and traffic channels are sufficient,
the eNodeB does not perform delay-based downlink packet bundling. If the packet delay
increases with the network load, the eNodeB bundles downlink packets to reduce the overhead
on the PDCCH, improve BE service quality, and increase the eNodeB throughput when users
are performing both GBR and non-GBR services.
Enhancement
None
Dependencies
None
2.44 TDLOFD-001027 Active Queue Management (AQM)

Availability
Summary
This feature provides the approach to buffer optimization to interact with the TCP protocol in a
favorable manner and shorten the buffering delay.

LTE TDD eRAN6.0
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, such as 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 a link.
The functionality of AQM is provided as an optimized buffer handling method, to interact with
the TCP protocol in a favorable manner and reduce the buffering delay.
Operators can switch on/off the Active Queue Management function.
Enhancement
None
Dependencies
None
2.45 TDLOFD-001029 Enhanced Admission Control

2.45.1 TDLOFD-00102901 Radio/transport Resource Pre-emption
Availability
Summary
This feature enables service differentiation when the network is congested to provide better
services for high-priority users.

LTE TDD eRAN6.0
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 the network, high priority user will
have more chances to access 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, admission based on QoS satisfaction
rates fails). The attributes of Pre-emption Capability and Pre-emption Vulnerability indicate the
capability of pre-empting resources of other services and vulnerability to pre-emption by other
services. 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 is not triggered if resource allocation
for SRB fails. For the emergency call (for example, E911) service, on account of their very high
priority, it always has the preemption capability. For the SRB, emergency call and IMS
signaling, they cannot be preempted.
Enhancement
In LTE TDD eRAN6.0, this feature allows resource 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 according to local
laws and regulations can preempt the resources of common services to increase the admission
rate of these two types of services.
An eNodeB allows RRC connections to be set up for all the UEs that initially access the
network. During E-UTRAN radio access bearer (E-RAB) setup, the eNodeB enables
high-priority services and emergency calls to preempt the resources of common services. The
eNodeB selects the high-priority services and emergency calls based on allocation/retention
priority (ARP) values, and selects the common services, whose resources are to be preempted,
in the following sequence: non-GBR services on unsynchronized UEs, non-GBR services on
synchronized UEs, and low-priority GBR services.
Dependencies
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.

LTE TDD eRAN6.0
2.46 TDLOFD-001007 High Speed Mobility

Availability
Summary
Huawei LTE TDD eRAN1.0 supports the mobility up to 120 km/h with good performance.
Benefits
High speed access is one of the key differentiators for Huawei SingleRAN LTE solutions to
provide high speed coverage. This feature brings the following benefits:
⚫ Allows Huawei LTE system to support high-speed UEs at up to 120 km/h with good
performance.
⚫ 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 LTE TDD eRAN1.0 supports the UE velocity up to 120 km/h, which almost covers all
mobility scenarios in an urban environment. The eNodeB should measure the UE mobility
speed and refine the channel estimation scheme accordingly. In addition, the MIMO scheme
and resource allocation mechanism is adaptively adjusted by the radio resource management
(RRM) function to meet the high-speed performance requirement. For example, it is suitable to
use frequency diversity mode rather than frequency-selective scheduling, or transmit diversity
rather than spatial multiplexing for a UE at a high speed.
Enhancement
Dependencies
eNodeBs must work in 4T4R or 2T2R mode.

LTE TDD eRAN6.0
2.47 TDLOFD-001008 Ultra High Speed Mobility

Availability
Summary
Huawei eNodeB can support the mobility up to 450 km/h with good performance.
Benefits
High speed access is one of the key differentiators for Huawei SingleRAN LTE solutions 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 350 km/h and 450 km/h.
⚫ Provides a seamless user experience in a high speed scenario.
Description
In addition to the availability of speed at 120 km/h, this feature allows Huawei LTE system to
support UEs with almost any mobility profile at up to 350 km/h in any scenario and deliver
good performance. For example, a UE on a high-speed train could reach up to 350 km/h.
The higher the velocity that the UE experiences, the severer the effect of Doppler shift and fast
fading that the system suffers. In Huawei RRM solution, the MIMO scheme and resource
allocation mechanism is adaptively adjusted to meet the ultra high speed performance
requirement.
Enhancement
Dependencies
eNodeBs must work in 4T4R or 2T2R mode.

LTE TDD eRAN6.0
2.48 TDLOFD-001031 Extended CP

Availability
Summary
The Cyclic Prefix (CP) is the guard interval used in the OFDM to decrease the interference
caused by the multi-path delay. The 3GPP TS36.211 supports two types of CP length, namely
normal CP and extended CP.
Benefits
The normal CP and the extended CP are used in different cell scenarios. In case of small
multi-path delay scenario, normal CP can achieve better system performance. In case of large
multi-path delay scenario, extended CP can achieve better system performance.
Description
For both downlink and uplink, the extended CP is calculated as follows:
Extended cyclic prefix: TCP = 512 x Ts
Where Ts = 1/(2048 x 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
Dependencies
UE should support the extended CP length as the eNodeB.
This feature is only applicable to macro eNodeBs.
This feature is only supported by the following RF module: RRU3232/RRU3235/RRU3252

LTE TDD eRAN6.0

2.49 TDLOFD-001019 PS Inter-RAT Mobility between

E-UTRAN and UTRAN
Availability
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 network, the PS redirection between E-UTRAN
and UTRAN is provided to realize the inter-RAT mobility. Moreover, the blind handover is
provided if inter-RAT measurements may be omitted (to save time and resources) or can be
unavailable.
PS handover between E-UTRAN and UTRAN also supports the function that the UEs can be
handed over to an inter-RAT UTRAN cell when there is uplink coverage restriction on
E-UTRAN.
PS handover based on uplink power is supported. When UE's service QoS is limited in uplink,
eNodeB can trigger an inter-RAT handover to UTRAN to guarantee the service QoS.
Benefits
The feature provides the following benefits:
⚫ Enables the seamless co-existence between E-UTRAN and UTRAN.
⚫ Guarantees smooth evolution from legacy wireless systems to the LTE system.
⚫ Provides supplementary coverage for E-UTRAN in the early phase using the legacy
wireless systems to prevent call drop and therefore to provide seamless user coverage.
⚫ Improves the network performance and end-user experience.
Description
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 the 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.

LTE TDD eRAN6.0
In Huawei LTE TDD eRAN1.0, handover is based on the coverage 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 hand over 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 becomes 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.
Huawei eNodeB also supports PS handover from UTRAN to E-UTRAN.
In some specific scenario, inter-RAT measurements may be omitted (to save time and resources)
or can be unavailable. In such a scenario, Huawei provides blind handover to implement
inter-RAT handover from E-UTRAN to UTRAN in LTE TDD 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 hand over the UE to the
blind handover target cell without inter-RAT measurement. Blind handover, compared with PS
handover, features more reduced handover time.
If the legacy UTRAN network or UEs cannot support PS handover, Huawei provides PS
redirection functionality to realize inter-RAT handover between UTRAN and E-UTRAN in
LTE TDD eRAN2.0. There is no update requirement for legacy UTRAN and UEs to support PS
Redirection.
The procedure of PS redirection is the same as that of RRCConnectionRelease in which the
carrier frequency information of the target redirection system will be included in the
RRCConnectionRelease message. After an RRC connection of a UE is released by the source
LTE system, the UE performs cell reselection to the target system based on the received carrier
frequency information during the release procedure and re-establishes the connection with the
target system. In summary, the handover mechanism of PS redirection consists of connection
release, carrier-frequency reselection, and connection re-establishment.
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: The procedure of cell selection is invoked when the UE is initially powered
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 either 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 broadcast
in cell system information.

LTE TDD eRAN6.0
reselection criteria. If a better cell is found, that cell is selected.
Generally speaking, LTE system is limited in uplink. Sometimes, QoS can be guaranteed in
downlink, but in uplink it is not satisfied even if UE has transmitted its full power. To guarantee
UE's service QoS in this scenario, Huawei 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 perform a handover
to UTRAN.
Enhancement
In LTE TDD eRAN6.0, the urgent redirection function has been provided by this feature. After
a UE accesses a cell, the eNodeB delivers two sets of event A2 configurations. One is used for
triggering measurements, and the other is used for triggering urgent redirection. If urgent
redirection is triggered by event A2, the signal quality in the serving cell is poor and the serving
cell cannot provide services for the UE. In this case, the eNodeB blindly redirects the UE to a
neighboring UTRAN cell.
Dependencies
The functionality of PS handover from UMTS to LTE depends on whether the UMTS and the
core network support this kind of handover.

E-UTRAN and GERAN
Availability
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 be handed over to an inter-RAT GERAN cell for the reason 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 omitted (to save time and resources) or can be
unavailable.
PS handover between E-UTRAN and GERAN also supports 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.

LTE TDD eRAN6.0
Benefits
⚫ Enables the seamless co-existence between E-UTRAN and GERAN.
⚫ Guarantees smooth evolution from legacy wireless systems to the LTE system.
⚫ Provides supplementary coverage for E-UTRAN in early phase using the legacy wireless
systems to prevent call drop and therefore to provide seamless overage for the UE.
⚫ Improves the network performance and end-user experience.
Description
Handover between E-UTRAN and GERAN is a critical feature to allow seamless co-existence
and a smooth evolution from the legacy wireless communication systems to the LTE system. It
is one type of the inter-RAT handover. It exists in the early phase of E-UTRAN when a UE
moves to an area where E-UTRAN does not have coverage but GERAN has.
In Huawei LTE TDD eRAN1.0, 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 moves out of E-UTRAN area, the eNodeB can decide whether to hand over 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 the 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.
Huawei eNodeB also supports the PS handover between GERAN and E-UTRAN. In addition to
PS handover, Huawei LTE TDD eRAN1.0 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 provides blind handover to implement
inter-RAT handover from E-UTRAN to GERAN in LTE TDD eRAN2.0. 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 conditions (load, service) are met, the eNodeB can hand over the UE to the
blind handover target cell without inter-RAT measurement. Blind handover, compared with PS
handover, features more reduced handover time.
If the legacy GERAN networks or UEs cannot support PS handover, Huawei provides PS
redirection functionality to realize inter-RAT handover between GERAN and E-UTRAN in
LTE TDD eRAN2.0. There is no update requirement for legacy GERAN networks and UEs to
support PS Redirection.
The procedure of PS redirection is the same as that of RRCConnectionRelease in which the
carrier frequency information of the target redirection system will be included in the

LTE TDD eRAN6.0
RRCConnectionRelease message. After an RRC connection of a UE is released by the source

system, the UE performs cell reselection to the target system based on the received carrier
frequency information during the release procedure and re-establishes the connection with the
target system. In summary, the handover mechanism of PS redirection consists of connection
release, carrier frequency reselection, and connection re-establishment.
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: The procedure of cell selection is invoked when the UE is initially powered
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 either 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 broadcast
in cell system information.
reselection criteria. If a better cell is found, that cell is selected.
Generally speaking, LTE system is limited in uplink. Sometimes, QoS can be guaranteed in
downlink, but in uplink it is not satisfied even if UE has transmitted its full power. To guarantee
UE's service QoS in this scenario, Huawei 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 perform a handover
to GERAN.
Enhancement
neighboring GERAN cell.
Dependencies
The GERAN and core network must support NACC and PS handovers between the GERAN
and E-UTRAN.

LTE TDD eRAN6.0

E-UTRAN and CDMA2000
Availability
Summary
When this feature is enabled, the eNodeB can perform inter-RAT cell selection and reselection
between the E-UTRAN and CDMA2000 network and hands over the users using high rate
packet data (HRPD) services between the E-UTRAN and CDMA2000 network.
Benefits
⚫ Enables co-existence of the E-UTRAN and CDMA2000 network.
⚫ Supports smooth evolution from the CDMA2000 network to the E-UTRAN.
⚫ Provides supplementary coverage for the E-UTRAN in the initial phase of LTE network
deployment to prevent call drops and implement seamless coverage.
⚫ Improves network performance and user experience.
Description
The PS handover between the E-UTRAN and CDMA2000 network (that is, the HRPD network)
is a type of inter-RAT handover. In the initial phase of LTE network deployment; this type of
handover is performed when a UE moves from an E-UTRAN coverage area to a CDMA2000
coverage area.
For a handover from the E-UTRAN to HRPD network, Huawei eNodeB supports both
non-optimized and optimized handover mechanisms defined in 3GPP TS 23.402.
⚫ During a non-optimized handover, a UE does not pre-register in the HRPD system. When
moving out of the E-UTRAN coverage area, the UE determines whether to perform a
handover from the E-UTRAN to the HRPD network based on the measurement results,
and then initiates the handover to the target HRPD cell.
⚫ During an optimized handover, a UE pre-registers in the HRPD system. When moving out
of the E-UTRAN coverage area, the eNodeB determines whether to perform a handover
from the E-UTRAN to the HRPD network based on the measurement report from the UE.
Upon receiving the handover command sent by the eNodeB, the UE initiates a handover to
the target HRPD cell.
The UE uses an RF channel to perform the gap-assisted measurement of the target inter-RAT
cell. The measurement is triggered by event A2 and stopped by event A1.
⚫ When the measurement is triggered, the quality of E-UTRAN downlink reference signals
is less than a specific absolute threshold.
⚫ When the measurement is stopped, the quality of E-UTRAN downlink reference signals is
better than the absolute threshold.
The inter-RAT handover parameters can be configured for different services.

LTE TDD eRAN6.0
Huawei eNodeB also supports PS handovers from the CDMA2000 network to the E-UTRAN.
However, from an E2E solution point of view, this type of handover depends on the LTE system
capabilities and whether the CDMA2000 system and core network can support this type of
handover.
Enhancement
None
Dependencies
PS handovers from the CDMA2000 network to the E-UTRAN depend on whether the
CDMA2000 system and core network can support this type of handover.
2.52 TDLOFD-001050 Mobility between LTE TDD and

LTE FDD
Availability
Summary
This feature provides the function of cell selection and reselection between TDD E-UTRAN
and FDD E-UTRAN and the function that the UEs can be handed over from TDD to FDD
E-UTRAN cell or from FDD to TDD E-UTRAN cell for cell coverage.
Benefits
⚫ Enable the seamless co-existence between TDD and FDD E-UTRAN.
⚫ Therefore, it could improve the network performance and end-user experience.
Description
Handover functionality is important in any cellular telecommunications network. It is
performed to ensure no interruption to services. Handover plays a significant role in LTE
system performance since its main purpose is to decrease the communication delay, enlarge the
coverage and then enhance the system performance. Handover between TDD and FDD
E-UTRAN enables the seamless co-existence between these two networks and improves the
network performance and end-user experience.
The handover procedure can be divided into four phases: measurement triggering, handover
measurement, handover decision, and handover execution. Upon receiving a measurement
report from the UE, the eNodeB makes a handover decision. If the measurement meets the
handover criteria, the eNodeB will perform the corresponding handover.
Cell selection/reselection is a mechanism for UE in idle mode to select/reselect a cell to camp
on and to receive the most appropriate service support upon session activation in the LTE

LTE TDD eRAN6.0
system. This feature provides a mechanism for UE in idle mode to select/reselect a cell to camp
by supplementary coverage in LTE systems regardless of whether it is based on TDD
E-UTRAN or FDD E-UTRAN.
Enhancement
neighboring LTE FDD cell.
Dependencies
The UE should support this feature.
The core network should support this feature.
2.53 TDLOFD-001032 Intra-LTE Load Balancing

Availability
Summary
It can resolve the unbalance between the service cell and the intra-frequency or inter-frequency
neighbor cells.
Benefits
It can utilize the network resource fully and improve the system capacity by balancing the load
between the neighbor cells. In addition, it reduces the rate of system overload and improves the
access success rate.
Description
In some situation of commercial LTE network, some serving cells have high load but other
neighbor cells' load is low because of the differentiation of UE services. Under this condition, it
can trigger load balancing algorithm.
The serving cell measures the cell load and receives the neighboring cell's load at the same time.
The serving cell evaluates the load and decides whether to perform a handover to neighboring
cell. If the serving cell load is very high which is beyond the threshold, at the same time, the
neighboring cell's load is low, some UEs begin to be handed over to neighboring cell in advance.
The cell load is defined according to TS 36.314, which is utilization rate of PRB.
For intra-frequency load balancing, there are two types of load balancing: active load balancing
and idle load balancing. The idle load balancing is to update QoS and notice UE by system
broadcast information.

LTE TDD eRAN6.0
The active load balancing procedure includes the following steps: load measurement and
evaluation, load information exchanges, load balance decision, modification of CIO parameter
and monitoring of performance.
For inter-frequency load balancing, there is only one type of load balancing: active load
balancing. The active load balancing procedure includes the following steps: load measurement
and evaluation, load information exchanges and load balance decision.
Intra-LTE load balancing is used in the scenario of coverage overlapped between multiple
intra-frequency LTE cells or multiple inter-frequency LTE cells.
Enhancement
In LTE TDD eRAN6.0, eNodeBs dynamically balance load between sectors based on the load
difference between these sectors. The load difference can be configured.
Dependencies
The X2 interface must support intra-LTE intra-frequency load balancing.
2.54 TDLOFD-001044 Inter-RAT Load Sharing to UTRAN

Availability
Summary
This feature is used in the LTE and UMTS which coverage the same area and the two system's
load is unbalance.
Benefits
It can improve the system resource utilization rate at the same time that it can guarantee the
service QoS. It can reduce the possibility of system overload and decrease the service drop rate.
Description
In some situations of commercial LTE network, LTE cells have high load but the load of UMTS
cells is low because of the differentiation of UE services. Under this condition, the eNodeB uses
the load balancing algorithm.
The LTE cell measures the cell load and evaluates the load. Then it decides whether to perform
a handover to neighboring cell. If the LTE cell load is higher than a specific threshold, some UE
begins to be handed over to a UMTS cell. The cell load is defined as the utilization rate of PRBs.
For details, see 3GPP TS 36.314.
There is only one type of inter-LTE load balance: active load balance. The active load balance
procedure includes the following steps: load measurement and evaluation, load balance
triggering, UE-dedicate priority update, UE selection for handover, and handover execution.

LTE TDD eRAN6.0
Enhancement
In LTE TDD eRAN6.0, an eNodeB obtains the load of the neighboring UTRAN cell by the
RIM procedure before performing a handover. The eNodeB hands over UEs to this UTRAN
cell only when the cell load is lower than a specific threshold.
Dependencies
UE should support LTE TDD and UMTS.
2.55 TDLOFD-001045 Inter-RAT Load Sharing to GERAN

Availability
Summary
This feature is used in the LTE and GSM which coverage the same area and the two system's
load is unbalance.
Benefits
It can improve the system resource utilization rate at the same time that it can guarantee the
service QoS. It can reduce the possibility of system overload and decrease the service drop rate.
Description
In some situation of commercial LTE network, LTE cells have high load but GERAN system's
load is low because of the differentiation of UE services. Under this condition, it can trigger
load balancing algorithm. The LTE cell measures the cell load and evaluates the load. Then it
decides whether to perform a handover to neighboring cell. If the LTE cell load is very high
which is beyond the threshold, some UE begins to be handed over to GERAN system. The cell
load is defined according to TS 36.314, which is utilization rate of PRB.
There is only one type of inter-LTE load balance: active load balance. The active load balance
procedure includes the following steps: load measurement and evaluation, load balance trigger,
UE dedicate priority update, choosing handover UE and handover execution.
This feature is used in the scenario of repetition coverage area by LTE and GERAN.
Enhancement
None
Dependencies
UE should support LTE TDD and GSM.

LTE TDD eRAN6.0

⚫ TDLOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN.
2.56 TDLOFD-001043 Service based Inter-RAT handover to

UTRAN
Availability
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 drop rate.
Description
LTE system sends inter-system measurement control message to UE which want to set up VoIP
service and instructs it to execute the measurement. When UE reports B1 event to eNodeB,
eNodeB decides whether to set up service in the UMTS based on RAB QCI handover strategy.
Enhancement
None
Dependencies
UE should support LTE TDD and UMTS.
It is also related with RAB QCI, which decides whether to execute handover.
2.57 TDLOFD-001046 Service based Inter-RAT handover to

GERAN
Availability

LTE TDD eRAN6.0
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 drop rate.
Description
LTE system sends inter-system measurement control message to UE which want to set up VoIP
service and instructs it to execute the measurement. When UE reports B1 event to eNodeB,
eNodeB decides whether to set up service in the GERAN based on ERAB (EPS RAB) QCI
handover strategy.
Enhancement
None
Dependencies
UE should support LTE TDD and GSM.
It is also related with RAB QCI, which decides whether to execute handover.
2.58 TDLOFD-001072 Distance based Inter-RAT handover

to UTRAN
Availability
Summary
Huawei LTE eNodeB supports distance based handover from E-UTRAN to UTRAN in
Mobility features.
Benefits
Better End user Experience (Always Best Connected)

LTE TDD eRAN6.0
Description
satisfied to trigger an Inter-RAT handover to UTRAN, even though the neighboring UTRAN
signal is much better than F1. To make the user always keep the best connection, a distance
based handover to UTRAN is employed.
distance threshold, inter-RAT gap measurements of neighboring UTRAN will be triggered to
find an optimal handover candidate to improve user performance
Enhancement
None
Dependencies
UE should support for Inter-RAT Gap measurements of UTRAN.
2.59 TDLOFD-001073 Distance based Inter-RAT handover

to GERAN
Availability
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
satisfied to trigger an Inter-RAT handover to GERAN, even though the neighboring GERAN
signal is much better than F1. To make the user always keep the best connection, a distance
based handover to GERAN is employed.

LTE TDD eRAN6.0
distance threshold, inter-RAT gap measurements of neighboring GERAN will be triggered to

find an optimal handover candidate to improve user performance
Enhancement
None
Dependencies
UE should support for Inter-RAT Gap measurements of GERAN
2.60 TDLOFD-001078 E-UTRAN to UTRAN CS/PS

Steering
Availability
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 does not 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.

LTE TDD eRAN6.0
Enhancement
None
Dependencies
2.61 TDLOFD-001026 Optional uplink-downlink subframe

configuration
2.61.1 TDLOFD-00102601 uplink-downlink subframe
Availability
Summary
The eNodeB supports different uplink-downlink subframe configurations.
Benefits
This feature enables the customer to flexibly configure uplink-downlink subframe ratio
according to different service requirements.
Description
The eNodeB supports different uplink-downlink subframe configurations specified in 3GPP TS
36.211.
the throughput of uplink traffic is larger than downlink traffic, such as video surveillance.
The following figure shows the subframe configurations.
In the preceding figure, D denotes the subframe is reserved for downlink transmissions, "U"
denotes the subframe is reserved for uplink transmissions, and "S" denotes a special subframe
with the three fields DwPTS, GP and UpPTS.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
None
2.61.2 TDLOFD-00102602 uplink-downlink special subframe

Availability
Summary
DwPTS/GP/UpPTS).
Benefits
Description
Type 4: The ratio of lengths of DwPTS to GP to UpPTS is 12:1:1 when eNodeB adopts normal
cyclic prefix. The ratio of lengths of DwPTS to GP to UpPTS is 3:7:1 when eNodeB adopts
extended cyclic prefix.

configuration
DwPTS GP UpPTS
4 26336  Ts 2192  Ts 2192  Ts
Special subframe Extended cyclic prefix

configuration
DwPTS GP UpPTS
4 7680  Ts 17920  Ts 2560  Ts
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
2.61.3 TDLOFD-00102603 uplink-downlink special subframe

Availability
Summary
DwPTS/GP/UpPTS).
Benefits
Description
Type 5: The ratio of lengths of DwPTS to GP to UpPTS is 3:9:2 when eNodeB adopts normal
cyclic prefix. The ratio of lengths of DwPTS to GP to UpPTS is 8:2:2 when eNodeB adopts
extended cyclic prefix.

configuration
DwPTS GP UpPTS
5 6592  Ts 19744  Ts 4384  Ts
Special subframe Extended cyclic prefix

configuration
DwPTS GP UpPTS
5 20480  Ts 5120  Ts 5120  Ts
Enhancement
None
Dependencies
None

LTE TDD eRAN6.0
2.62 TDLOFD-001076 CPRI Compression

Availability
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.
⚫ 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 on the LBBPd and LBBPc decreases to about 50%
and 60% of the original CPRI data, respectively. The extent of reduction is determined by the
processing capabilities of the two boards.
Enhancement
None
Dependencies
RRU should support this feature.
2.63 TDLOFD-002001 Automatic Neighbour Relation

(ANR)
Availability

LTE TDD eRAN6.0
Summary
The ANR feature takes advantage of the eNodeB algorithm to plan and configure automatically
the neighbor relationships, and to solve the problems of incorrect neighbor relationship
configuration. This feature greatly reduces the OPEX for the operator by avoiding human
intervention and saving labor work.
Benefit
⚫ Missing or incorrect neighbor relationships can be found or optimized. Therefore, no
handover failure is caused by missing or incorrect neighbor relationship configuration.
⚫ The Physical Cell Identity (PCI) collision detection can be triggered
Description
ANR can automatically add and update neighbor relationships in the Neighboring Relation
Table (NRT). However, the manual configuration of NRT's attributes including NO HO and NO
REMOVAL has higher priority than ANR algorithm. For example, if operator sets up NO
REMOVAL, ANR will not remove this record from NRT.
The ANR process is described as follows:
Figure 2-7 ANR
Cell A Cell B
Phy-CID=3 Phy-CID=5
Global-CID =17 Global-CID =19
1) report(Phy-CID=5,
strong signal)
3) Report
Global-CID=19 2b) Read BCH()
2) Report Global-CID
Request (Target Phy-
CID=5)
The ANR process is described as follows:

1. The eNodeB instructs the UE for which the LTE frequency needs to be measured.
The UE sends a measurement report regarding cell B. This report contains cell B's PCI, but
not includes its GCI (Global Cell Identity). When the eNodeB receives a UE measurement
report containing the PCI that is not included in the NRT for that cell, the following
sequence may be used.
2. The eNodeB instructs the UE to use the newly discovered PCI as parameter to read the
GCI of the related neighboring cell. The eNodeB may need to schedule appropriate gaps to
allow the UE to read the GCI of the neighboring cell, as the UE needs to decode the new
cell's broadcast GCI.

LTE TDD eRAN6.0
3. When the UE has read the new cell's GCI, it reports the detected GCI to the serving cell
eNodeB.
The eNodeB decides to add this neighbor relationship and uses the PCI and GCI to perform the
following operations:
⚫ Searches a transport layer address to the new eNodeB (OM search or MME search
mechanisms that have been already standardized by the 3GPP.
⚫ Updates its NRT
There are two major mechanisms for the eNodeB/cell to find new neighboring cell.
⚫ The neighboring cell's PCI is reported to the eNodeB in the UE measurement report, and
then, the eNodeB instructs the UE to read the GCI of the new neighboring cell.
⚫ The neighboring cell's GCI is sent to the eNodeB in the UE history information of
HANDOVER REQUEST, and then the eNodeB requests the PCI of the new neighboring
cell.
After the eNodeB adds the new neighboring cell, the PCI collision detection procedure can be
activated. For details on PCI collision detection, refer to TDLOFD-002007 PCI Collision
Detection & Self-Optimization.
If needed, an X2 link establishment can also be activated through the Automatic Transport
Setup function in feature TDLOFD-002004 Self-configuration.
The periodic ANR is supported. Its measurements refer to select and configure UEs to report for
strongest cells (intra-LTE) on a periodical time basis. In case a UE reports an unknown physical
cell identity (PCI), the eNodeB shall trigger ANR measurements to find out the corresponding
GCI. Periodical ANR increases handover performance.
In LTE TDD eRAN2.1, ANR feature is enhanced with the following administration functions:
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 master the feature running
process and key event.
Enhancement
In LTE TDD eRAN6.0, eNodeBs support the following functions:
⚫ Operator-specific X2 interface self-setup
In an area served by multiple operators, an eNodeB selects neighboring eNodeBs based on
the policies of the operators who have deployed these neighboring eNodeBs, and then sets
up X2 interfaces with them. This prevents the setup of unnecessary X2 interfaces.
⚫ Detection of missing neighboring cells
When the serving and neighboring cells are managed by the same element management system
(EMS), the configuration and status information of the neighboring cells are saved on the EMS.
If an eNodeB detects a missing neighboring cell, the eNodeB obtains the serving PLMN list of
the neighboring cell from the EMS and configures the neighboring cell.
Dependencies
⚫ OSS feature WOFD-180600 Automatic Neighbor Relation Optimization -LTE
⚫ TDLBFD-002017 DRX.

LTE TDD eRAN6.0
ANR based PCI Self-Optimization depends on TDLOFD-002001 Automatic Neighbour

Relation (ANR).
UE should support DRX.
When the serving and neighboring cells are managed by different EMSs, the round-robin
broadcast of PLMN IDs in TDLOFD-001036 RAN Sharing with Common Carrier is disabled.
Otherwise, ANR is ineffective.
When ANR triggers neighboring cell information modification, TDLOFD-002007 PCI
Collision Detection & Self-Optimization is performed.
2.64 TDLOFD-002002 Inter-RAT ANR

Availability
Summary
The Inter-RAT ANR functionality takes advantage of the eNodeB algorithm to plan, configure
neighbor relationships, and solve the problem of incorrect neighbor relationships between
E-UTRAN and GERAAN/UTRAN.
Benefit
In LTE system, the Inter-RAT neighbor relationships can be automatically added without
human intervention, reducing the OPEX of the operator.
Description
Inter-RAT ANR can add neighbor relationships in the LTE eNodeB automatically through UE
Inter-RAT measurement.
The coverage of particular radio technologies (RAT) will be broadcasted in E-UTRAN. Then,
the UE can measure and report the existence of these RATs to the LTE eNodeB instructing it to
build up Inter-RAT neighbor relationships for further Inter-RAT mobility.
The Inter-RAT ANR consists of the following functions:
⚫ Measures the existence of the UTRAN cell, and GERAN cell
⚫ Establishes E-UTRAN -> other RAT neighbor relationships 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:

LTE TDD eRAN6.0
Figure 2-8 Inter-RAT ANR function
It is assumed that this function is executed on the M2000 (Huawei OM platform) client, which
can manage:
⚫ Inter-RAT/frequency Search list: List of RATs/frequencies that shall be searched.
⚫ Inter-RAT/frequency ANR Blacklist: List of cells that shall not be included in the eNodeB
Inter-RAT/frequency neighbor lists.
It is also assumed that the OM system is informed about changes in the eNodeB
Inter-RAT/frequency neighbor lists.
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/frequencies. The
eNodeB may use different policies for instructing the UE to perform measurements and then to
report them to the eNodeB.
2. The eNodeB instructs the UE to search neighboring cells in the target RATs/frequencies.
The eNodeB may need to schedule appropriate gaps to allow the UE to scan all cells in the
target RATs/frequencies.
2. The UE reports the PCI of the detected cells in the target RATs/frequencies and their
respective signal quality. The carrier frequency and Primary Scrambling Code (PSC)
define the PCI in case of UTRAN cell, and the Band Indicator + BSIC + BCCH ARFCN in
case of GERAN cell.
When the eNodeB receives UE's reports containing Phy-CIDs of cells that are not already
in Inter-RAT/frequency neighbor lists of that cell, the following sequence may be used.
3. 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/frequency.
The eNodeB may need to schedule appropriate gaps to allow the UE to read the
Global-CID from the broadcast channel of the detected neighboring cell.
4. When the UE has read the new cell's Global-CID, it reports the detected Global-CID to the
serving cell eNodeB.

LTE TDD eRAN6.0
The eNodeB updates its inter-RAT/frequency neighbor lists.

Periodic inter-RAT ANR is supported. Its measurements refer to select and configure UEs to
report for strongest cells (LTE) or report for strongest cells for SON (inter-RAT) on a periodical
time base. In case a UE reports an unknown layer 1 cell identity (PCI, PSC, and BSIC) the
eNodeB shall trigger Inter-RAT ANR measurements to find out the corresponding GCI.
Periodic Inter-RAT ANR increases performance in handover procedure.
Enhancement
In LTE TDD eRAN6.0, eNodeBs support the detection of missing neighboring cells. When the
serving and neighboring cells are managed by the same EMS, the configuration and status
information of the neighboring cells are saved on the EMS. If an eNodeB detects a missing
neighboring cell, the eNodeB obtains the serving PLMN list of the neighboring cell from the
EMS and configures the neighboring cell.
Dependencies
⚫ OSS feature WOFD-181400 Inter-RAT Automatic Neighbour Relation Optimization -LTE
⚫ TDLBFD-002017 DRX.
UE should support DRX.
2.65 TDLOFD-002004 Self-configuration

Availability
Summary
The eNodeB can automatically establish an OM link, obtain the configuration data file and
software from the EMS, and then activate the configuration data file and software automatically.
The configuration data file contains radio parameters and transport parameters. Finally, the
eNodeB performs a self-test and reports the test result to the EMS.
The eNodeB can be triggered automatically by the M2000 or LMT to launch a comprehensive
self-test after the software and configuration data file are downloaded. After the test is complete,
the M2000 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,

LTE TDD eRAN6.0
through the DHCP server. 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.
After the software and configuration data file are downloaded, the M2000 or LMT
automatically launches a comprehensive self-test procedure on the eNodeB. After the test is
complete, the M2000 or LMT obtains a test report, indicating the eNodeB status.
The test report contains the following contents:
⚫ eNodeB basic information, such as type, name, MNC, MCC, and electrical serial number
⚫ Software version information
⚫ Board status information, such as information about the baseband and RF units
⚫ Transport status information (physical layer and link layer)
⚫ Clock status
⚫ Cell status
⚫ Environment temperature and humidity
In LTE TDD eRAN2.0, the eNodeB can establish an IPsec link with the security gateway
automatically during the self-configuration procedure.
In LTE TDD eRAN2.0, 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.
In LTE TDD eRAN2.0, 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.
Figure 2-9 General network topology

LTE TDD eRAN6.0
The eNodeB has parameters pre-configured in factory or other places before the installation,
such as the MAC address, local OM IP, unique ID, and security key. All these parameters do not
need to set or modified manually.
The automatic transport setup procedure is as follows:
⚫ 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.
⚫ The eNodeB is able to obtain VLAN ID of peer devices (switch, router) by VLAN
scanning. Therefore, the peer devices could receive the data from eNodeB correctly.
⚫ 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 (such as name, IP address, and protocol type).
⚫ 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.
⚫ The eNodeB establishes an IPsec tunnel with the SeGW, obtains the Internal IP address,
and then establishes the OM channel with the NEM.
⚫ 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.
⚫ The eNodeB starts the S1 interface self-configuration procedure and establishes the S1
link.
This feature also includes the X2 interface self-setup function of the ANR 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 core network, the eNodeB
establishes the X2 link with this new neighboring site automatically.
In LTE TDD eRAN2.1, eNodeB is able to obtain VLAN ID of peer devices (switch, router) by
VLAN scanning. Therefore, the peer devices could receive the data from eNodeB correctly.
In LTE TDD eRAN2.1, 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.
In LTE TDD eRAN2.1, 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.
In eRAN3.0, eNodeB supports X2 interface auto setup function of the ANR feature under IPv6.
In eRAN3.0, eNodeB supports to obtain the S-GW IP address for MME when one service is set
up. After eNodeB obtains the S-GW IP address from the signaling between MME and eNodeB,
eNodeB auto-configured S1-U interface.
Enhancement
None
Dependencies
The X2 interface automatic setup function in this feature depends on the optional ANR feature.

LTE TDD eRAN6.0
2.66 TDLOFD-002007 PCI Collision Detection &

Self-Optimization
Availability
Summary
This feature detects Physical Cell Identity (PCI) collision through ANR functionality.
Benefits
This feature detects the Physical Cell Identity (PCI) collision automatically.
Description
The physical cell identity (PCI) is an essential configuration parameter of an E-UTRAN cell. It
corresponds to a unique combination of one orthogonal sequence and one pseudo-random
sequence. In LTE, there are only 504 physical cell IDs that can be repeated for a large scale of
eNodeB deployment, but the key is that the two cells that share a physical cell ID cannot be
geographically close or they will interfere each other.
When a new eNodeB is brought into the field, a PCI, used to transmit data over the cell, needs to
be selected for each of its supported cells, avoiding collision with respective neighboring cells
that results in interference and service deterioration. The 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.
Whenever the new neighbor relationship is added by the eNodeB, the PCI collision detection
procedure is triggered to check the possible PCI collision within the neighboring cells.
In LTE TDD eRAN2.1, PCI Collision Detection is enhanced with Self-optimization
implemented in EMS to solve the detected collisions. To allocate the optimal candidate PCI for
the whole network, and to minimize the interference among neighboring cells, the sites
engineering information (longitude, latitude, Azimuth), GCI, and neighbor list are taken into
the PCI assignment. For Micro eNodeB, if 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 Micro's neighboring cells' information can be
discovered by the sniffer or ANR. The new assigned PCI can be configured in 3 manners:
⚫ Immediate and Automatic delivery: The EMS will deliver the new PCIs to the eNodeB as
soon as it is generated.
⚫ Regular and Automatic delivery: The EMS will deliver the new PCI at a cycle time basis.
⚫ Manually confirmed delivery: the EMS will generate a notice for confirmation before
delivery to the eNodeB
PCI Collision Detection and Self-optimization feature is enhanced with the following
administration functions:
⚫ Setting: can be divided into:

LTE TDD eRAN6.0
− Policy setting: operator can set up some policy of the feature (like 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.
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 master the feature running
process and key event.
Enhancement
None
Dependencies
⚫ OSS feature WOFD-170200 Automatic PCI Optimization -LTE
2.67 TDLOFD-001024 Remote Electrical Tilt Control

Availability
Summary
Remote Electrical Tilt Control improves the efficiency and minimizes the OM cost for
adjusting the downtilt 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 downtilt 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 downtilt is controlled
electrically and remotely.
After an antenna is installed, the downtilt of the antenna needs to be adjusted to optimize the
network. In this situation, the phases of signals that reach the elements of the array antenna can

LTE TDD eRAN6.0
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 downtilt of the RET antenna can be adjusted when the system is powered on, and the
downtilt can be monitored in real time. Therefore, the remote precise adjustment of the downtilt
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
Dependencies
This feature cannot be available when splitting RRU3232/RRU3252 into 2 2T2R RRUs.
2.68 TDLOFD-002005 Mobility Robust Optimization

(MRO)
Availability
Summary
MRO aims to avoid Ping-Pong handover, handover too early, and handover too late. It mainly
optimizes the typical mobility control parameters.
Benefits
This feature can save labor cost for typical and common mobility optimization scenarios.
Description
This feature addresses too-early and too-late handover failures, together with Ping-Pong events.
The major MRO parameters for adjustment are the CIO (Cell Individual Offset) for
intra-frequency MRO.
CIO will be adjusted online for the offset, which explicitly declares the HO threshold between
measurement results of signaling quality from both of the source and target cells. Hence,
changing the CIO will significantly speed up or delay handover. The major MRO parameter
adjustment is the CIO.
Both too early and too late handovers are captured at the source eNodeB by exploiting the fact
that the source eNodeB is informed of too late handovers that have been prepared by the UE
context release mechanism. Only outgoing handover failures are captured. There is no need to
capture incoming handovers.

LTE TDD eRAN6.0
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.
Huawei LTE TDD supports intra-frequency Mobility Robust Optimization.
the following administration functions are also supported:
⚫ Switch: user can enable or disable the feature
⚫ 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 master the feature
running process and key event.
Enhancement
None
Dependencies
None
2.69 TDLOFD-002015 RACH Optimization

Availability
Summary
The feature supports the following functions:
⚫ Dynamic adjustment of preamble groups
⚫ Dynamic assignment of PRACH resources
⚫ Optimize the back-off time
Benefits
The feature increases the random access success ratio.
Description
The number of PRACH preamble is 64, the preamble is divided into two parts which is for
competitive random access and non-competitive random access separately. 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 subframe which used to
send random access preamble. The eNodeB measures the number of preambles during the
period, and the eNodeB will adjust the PRACH configuration index to fulfill the demand. If the

LTE TDD eRAN6.0
number of preambles is greater than threshold, the PRACH configuration index will be adjusted
to indicate more subframe.
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.
Enhancement
None
Dependencies
None
2.70 TDLOFD-002011 Antenna Fault Detection

Availability
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, thereby improving the
efficiency and accuracy of fault diagnosis.
By using this feature, RF engineers do not need to be use equipment to measure eNodeB on site
every time, thereby 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 receiving signal
⚫ Unbalance of receiving signal between the main and the diversity
⚫ Voltages Standing Wave Ratio (VSWR) abnormal

LTE TDD eRAN6.0
Enhancement
None
Dependencies
None
2.71 TDLOFD-002012 Cell Outage Detection and

Compensation
Availability
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.
⚫ 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

LTE TDD eRAN6.0
After cell outage detected, the system will recover the cell.
After outage recovery, the system will reverse the compensation.
Enhancement
To accelerate the cell outage detection process, LTE TDD eRAN6.0 introduces the assisted cell
outage detection method. This method is independent of KPI measurement and detects cell
outage by checking internal eNodeB counters at an interval of 5 minutes. When the counter
values exceed the specified thresholds, the eNodeB reports the check results to the M2000. The
M2000 then determines that cell outage has occurred.
Dependencies
⚫ OSS feature WOFD-171000 Cell Outage Detection and Recovery -LTE
If operators have 2G/3G network, RRM compensation can be improved by using these two
optional features: TDLOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN,
TDLOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN.
2.72 TDLOFD-003002 2G/3G and LTE Co-transmission

Availability
Summary
2G/3G and LTE co-transmission provides the operators the possibility of LTE co-transmission
with legacy networks such as GSM, UMTS, or TD-SCDMA 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.
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 TD-SCDMA. 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

LTE TDD eRAN6.0
Figure 2-10 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 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 must 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 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
Dependencies
The base stations of other standards should support IP protocol.
2.73 TDLOFD-003004 Ethernet OAM

2.73.1 TDLOFD-00300401 Ethernet OAM_(IEEE 802.3ah)
Availability
Summary
Ethernet OAM (IEEE 803.3ah) provides the fault isolation and troubleshooting capabilities for
point-to-point Ethernet services.

LTE TDD eRAN6.0
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 IEEE
802.3ah.
⚫ 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 IEEE 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 IEEE 802.3ah function
properly or not.
⚫ Remote failure indication: When detecting faults such as a link fault, dying gasp, critical
event, the device informs the peer device of the faults with OAM PDUs.
⚫ Link monitoring: The device supports link bit error rate (such as error frame and error
signal) monitoring. When the error rate exceeds the threshold, it will report the event to the
peer device with OAM PDUs.
⚫ Remote loopback: The device sends a loopback control PDU to ask the peer device to loop
back. With loopback, it is easy to locate the fault and test the link quality.
Enhancement
None
Dependencies
The peer equipment should support IEEE802.3ah when IEEE802.3ah is used.
Ethernet interface is used.
2.73.2 TDLOFD-00300403 Ethernet OAM (Y.1731)

Availability
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) helps operators solve this problem.

LTE TDD eRAN6.0
⚫ 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 and therefore help operators solve this problem.
⚫ 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 describes only the
performance monitoring function.
Ethernet OAM (ITU Y.1731) performance monitoring measures Ethernet performance
parameters including Frame Loss Ratio, Frame Delay and Frame Delay Variation.
This feature establishes an end-to-end detection session to monitor performance parameters of
the Ethernet based on the services:
⚫ Ethernet frame loss measurement (ETH-LM) is used to collect counter values applicable
to ingress and egress service frames. The counters maintain a count of transmitted and
received data frames between a pair of maintenance association end points (MEPs).
⚫ Ethernet delay measurement (ETH-DM) can be used for an on-demand OAM to measure
frame delay and frame delay variation. ETH-DM can be performed in two directions,
which is called two-way ETH-DM. Two-way ETH-DM is recommended, considering the
requirement of one-way ETH-DM for clock synchronization between two MEPs.
Enhancement
None
Dependencies
The peer equipment must also comply with ITU Y.1731.
The core network equipment must also comply with ITU Y.1731.
2.74 TDLOFD-003007 Bidirectional Forwarding Detection

Availability
Summary
BFD is a kind of bidirectional-detecting mechanism, which can be used to detect the fault of the
IP route.
Benefits
⚫ BFD helps the operator to detect network fault.

LTE TDD eRAN6.0
⚫ BFD achieves 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 detect the failure rapidly, so it could be used for telecom service on
IP networks.
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 2-11 One-hop and multi-hop BFD application scenarios
Enhancement
None
Dependencies
The peer equipment should support BFD when BFD is used to detect the fault of the IP route.
Ethernet interface is used.
2.75 TDLOFD-003011 Enhanced Transmission QoS

Management
2.75.1 TDLOFD-00301101 Transport Overbooking
Availability

LTE TDD eRAN6.0
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 64 kbit/s for dual rate and 32 kbit/s for single rate. The bandwidth
granularity is 1 kbit/s.
⚫ 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
Dependencies
This feature needs support of core network, because the TAC of the S1 interface is managed by
SAE.
2.75.2 TDLOFD-00301102 Transport Differentiated Flow Control

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

LTE TDD eRAN6.0
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
Dependencies
None
2.75.3 TDLOFD-00301103 Transport Resource Overload Control

Availability
Summary
Transmission Resource Overload Control is a way to rapidly enhance the transmission stability
when overloaded happen unexpectedly.
Benefits
This feature provides protection for the system when transmission resources are overloaded
unexpectedly.

LTE TDD eRAN6.0
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
Dependencies
None
2.76 TDLOFD-003012 IP Performance Monitoring

2.76.1 TDLOFD-00301201 IP Performance Monitoring
Availability
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 a 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

LTE TDD eRAN6.0
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
Dependencies
Core network equipment should support this feature.
2.76.2 TDLOFD-00301202 Transport Dynamic Flow Control

Availability
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. 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 IPPM (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
Dependencies
This feature depends on the TDLOFD-00301201 IP PM feature.

LTE TDD eRAN6.0
2.77 TDLOFD-003016 Different Transport Paths based on

QoS Grade
Availability
Summary
Different transport paths based on QoS grade are a transport networking solution that consists
of different transport paths implementation for different QCI grades.
Benefits
⚫ Different transport paths to improve the network quality of service
⚫ Different transport-paths implementation to improve the network reliability
Description
Different transport paths based on QoS grade consist of two logical or physical paths setup
between the eNodeB and the MME/S-GW. Operator can configure the transmission network to
have two groups of different QCIs being allocated to two different paths, high priority path and
low priority path. Thereby, the high QoS traffic classes could be sent over the high priority path
and the low QoS traffic classes, over the low priority path to improve the network quality of
service.
Figure 2-12 Two paths configured between eNodeB and SGW
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. After the failed path recovery, the related traffic flow can be
again transmitted over the original path. The path failure detection is handling able by means of
the different OAM mechanisms supported by Huawei eNodeB such as BFD, Ethernet OAM,
Ping, ARP and SON.
Enhancement
None
Dependencies
S-GW should support two paths configurations.

LTE TDD eRAN6.0
2.78 TDLOFD-003013 Enhanced Synchronization

2.78.1 TDLOFD-00301302 IEEE1588 V2 Clock Synchronization
Availability
Summary
IEEE1588 defines PTP (Precision Time 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 servers and eNodeBs 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
⚫ The basic principle of the IEEE-1588.
The following figure shows the basic principle defined by the IEEE1588 protocol.
Figure 2-13 Basic principle defined by the IEEE1588 protocol
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

LTE TDD eRAN6.0
intermediate switching device functions as a master clock and connect to other devices
functioning as slave clocks.
The Time Stamp Unit (TSU) provides the ability of precise time synchronization, thereby
reducing delay and jitter caused by the intermediate switching device and accurately sending
timing information. In this way, the work related to synchronization processing is shifted to be
processed at the layer between the physical layer and the MAC layer.
⚫ Synchronization principle
The following figure shows the synchronization principle of the IEEE1588 protocol.
Figure 2-14 Synchronization principle of the IEEE1588 protocol
The signaling procedure is described as follows:

1. The clock server (for example, the 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 time stamp T1, at which the message is sent. If
the delay of sending the Sync message from the clock server is uncertain, the clock server
generates a Follow_UP message, which carries the time stamp T1. The Follow_UP
message is optional.
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 time stamp T4 to the eNodeB. The delay

LTE TDD eRAN6.0
of sending the Delay_resp message does not affect T4. Therefore, the Delay_resp message
does not need to be processed in real time.
3. The eNodeB saves the complete information of 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.
In LTE TDD eRAN2.2, security of IEEE 1588 V2 in frequency synchronization mode is
enhanced by transporting 1588-related messages with IPsec security channel.
Enhancement
None
Dependencies
For time synchronization, all the devices on the clock relay path should support the
IEEE1588V2 protocol. For the frequency synchronization, there is no requirement for the
devices on the clock replay path.
This feature depends on TDLOFD-003009 IPsec if the IEEE 1588 V2 related messages need to
be transported on IPsec security channel.
2.79 TDLOFD-001134 Virtual Routing & Forwarding

Availability
Summary
This feature allows eNodeBs to connect to the networks of different operators, which may be
configured with the same internal IP addresses.
Benefits
This feature greatly reduces the capital expenditure (CAPEX) and operating expense (OPEX)
of the operators.
Description
In a wholesale scenario, an eNodeB connects to each retailer network, for which the retailer
operator has deployed the NEs and independently planned internal IP addresses.
When the networks of different operators are configured with the same internal IP address, this
feature allows an eNodeB to connect to the network. With this feature, the eNodeB prevents the
destination IP address of each route from conflicting with others and independently forwards
packets in each routing area. In this way, this feature prevents IP address conflicts between
networks without changing the internal IP addresses.

LTE TDD eRAN6.0
Enhancement
None
Dependencies
The evolved packet core (EPC) and transport network must support virtual local area networks
(VLANs).
This feature cannot support the UTRPc.
2.80 TDLOFD-001018 S1-flex

Availability
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.
In LTE TDD eRAN2.0, Huawei eNodeB supports a maximum of 16 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.
⚫ Prevents 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 topology between MME Pool and eNodeBs is shown in the following figure.

LTE TDD eRAN6.0
Figure 2-15 Connection topology between MME Pool and eNodeBs
POOL1 POOL2
MME 1 MME 2 MME 3 MME 4 MME 5
eNB 1 eNB 2 eNB 3 eNB 4 eNB 5 eNB 6
POOL Area 1 POOL Area 2
If an eNodeB connects to an 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 an MME as follows:
⚫ Topology-based MME Pool selection
The MME 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
None
Dependencies
MME should support MME Pool function simultaneously.
2.81 TDLOFD-001036 RAN Sharing with Common Carrier

Availability

LTE TDD eRAN6.0
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 Capital Expenditure (CAPEX) and
Operational Expenditure (OPEX).
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 to all operators' Core Networks. The system
information broadcast in each shared cell contains the PLMN-id of each operator (up to 4) and a
single tracking area code (TAC), which is valid within all the PLMNs sharing the radio access
network resources.
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 preferentially considered. The Inter-working
between different RATs may be used during the handover.
The MOCN Network Sharing has the following features.
⚫ Multiple PLMN-ids are broadcast on the common carrier and the Core Network is
separated.
⚫ Support independent logo and name display.
⚫ The shared OSS connects different NMS through Itf-N interference.
⚫ Support up to 4 operators.
The following enhancement is introduced.
Dynamic Radio Resource Management
Benefit:
This feature guarantees the fairness and flexibility of MOCN Network Sharing. All radio
resource could be shard dynamically and fairly between operators.
Description:
This feature meets the following general principle of fair sharing resources:
⚫ Balance between maximum system throughput and fair sharing resources between MOCN
operators.
⚫ Any unused resources shall be used by other operators.
⚫ Fair sharing resources solution shall be used for both uplink and downlink directions.

LTE TDD eRAN6.0
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 ratio 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
ratio and RB occupancy of B is large than B's predefined ratio.
eRAN3.0 supports multiple operators sharing MME and S1 link.
Enhancement
None
Dependencies
If MOCN is used, this feature depends on TDLOFD-001018 S1-flex.
If GWCN is used, this feature can work properly without TDLOFD-001018 S1-flex.
2.82 TDLOFD-001037 RAN Sharing with Dedicated Carrier

Availability
Summary
The eNodeB supports multiple operators to share the same Radio Access Network (RAN),
where the operators use dedicated carriers in the same eNodeB.
Benefits
Operators can share the RAN resource to reduce Capital 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. A tracking area should include multiple completed shared cells. The
architecture is shown in the following figure.

LTE TDD eRAN6.0
When a UE accesses a cell, the eNodeB identifies which core network it should be routed to
according to the cell it comes from its originating cell. 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 and 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 using its own carrier and within its own Core
Network separately.
⚫ Support independent logo and name display.
⚫ Independent cell-level FM and PM. The shared OSS connects different NMS through
Itf-N interference.
⚫ Independent License Management.
⚫ Independent feature activation and deactivation.
Enhancement
None
Dependencies
If MOCN is used, this feature depends on TDLOFD-001018 S1-flex.
If GWCN is used, this feature can work properly without TDLOFD-001018 S1-flex.

LTE TDD eRAN6.0
2.83 TDLOFD-001086 RAN Sharing by More Operators

Availability
Summary
Up to six operators can share an eNodeB in RAN sharing mode.
Benefits
More operators can share an eNodeB, greatly reducing operators' CAPEX and OPEX.
Description
eNodeBs support two RAN sharing modes: RAN sharing with common carriers and RAN
sharing with dedicated carriers. In either mode, up to six operators can share an eNodeB and
manage the eNodeB on the element management system (EMS). The EMS is connected to the
network management systems (NMSs) of the operators through northbound interfaces.
In RAN sharing with dedicated carriers mode, operators can share only eNodeB hardware. In
RAN sharing with common carriers mode, operators can share both eNodeB hardware and the
cells served by the eNodeB. In RAN sharing with common carriers mode, the following
functions are available:
⚫ A shared eNodeB broadcasts system information block type 1 (SIB1) in each shared cell.
Each SIB1 contains a PLMN ID list and a common tracking area code (TAC). A PLMN ID
list can contain a maximum of six PLMN IDs.
During RRC connection setup, a UE obtains the PLMN ID list, selects a PLMN, and then
notifies the eNodeB of the selected PLMN ID over the Uu interface. Based on the received
PLMN ID, the eNodeB selects an EPC for the UE.
⚫ The logo and name of an operator can be displayed on UEs.
⚫ A shared eNodeB can dynamically allocate radio resources to the operators to ensure
flexible and fair resource scheduling.
The dynamic allocation is based on the following mechanisms:
− Admission control based on the satisfaction of each type of service provided by the
operators
− Operator-specific load control
− Fair resource scheduling between the operators
− Resource allocation ratio configured for each operator
To improve resource usage, the resources that are allocated to but not used by an operator
can be shared by other operators.
⚫ UEs can use the resources allocated by shared and non-shared eNodeBs.
A shared eNodeB can be connected to other shared eNodeBs and non-shared eNodeBs.
When a UE is moving between shared eNodeBs or between a shared eNodeB and a
non-shared eNodeB, the operator serving the UE remains unchanged.

LTE TDD eRAN6.0
Enhancement
None
Dependencies
⚫ TDLOFD-001036 RAN Sharing with Common Carrier
⚫ TDLOFD-001037 RAN Sharing with Dedicated Carrier
2.84 TDLOFD-003017 S1 and X2 over IPv6

Availability
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 provide services on IPv6 network.
Description
This feature supports IPv6 protocol on S1 and X2 interface.
Radio
Network S1 and X2
Layer
Transport
Transpo IPV6
rtNetwor
kLayer Data link layer
Physical layer
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.

LTE TDD eRAN6.0
Enhancement
None
Dependencies
The peer devices (transport network and core network) should support this feature.
2.85 TDLOFD-003024 IPsec for IPv6

Availability
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 (DES), Triple Data
Encryption Standard (3DES), and Advanced Encryption Standard (AES)
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).

LTE TDD eRAN6.0
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 (such as computer users or servers), between
a pair of security gateways (such as 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 security gateway and eNodeB.
Enhancement
None
Dependencies
The peer equipment should support IPv6.
⚫ TDLOFD-003009 IPsec
This feature rely on the IPsec tunnel peer Network Equipment （eg. Security gateway,
MME\SGW）supporting IPsec on IPv6.
2.86 TDLOFD-003005 OM Channel Backup

Availability
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
Dependencies
The peer devices (transport network and core network) should support this feature.

LTE TDD eRAN6.0
2.87 TDLOFD-003006 IP Route Backup

Availability
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
Dependencies
The peer device should support the IP route backup function.
2.88 TDLOFD-003008 Ethernet Link Aggregation (IEEE

802.3ad)
Availability
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.

LTE TDD eRAN6.0
Description
Ethernet link aggregation is a protocol defined in IEEE 802.3ad. IEEE 802.3ad defines a link
aggregation control protocol (LACP). The links status of link group could be detected by
LACP.
The eNodeB supports static LACP. For static LACP, the parameters of the link group are
configured manually. The fault detecting uses the LACP.
The Ethernet link aggregation can be used in the following figure.
Figure 2-16 Ethernet link aggregation
Enhancement
None
Dependencies
The Ethernet link aggregation should be supported by the directly connected transport
equipment.
Ethernet interfaces are used.
2.89 TDLOFD-003019 IPsec Tunnel Backup

Availability
Summary
This feature provides primary and backup IPsec tunnels from one eNodeB to two security
gateways (SeGWs). It improves the reliability of eNodeB transport paths protected by IPsec
tunnels.
Benefits
Without this feature, eNodeB could only establish one IPsec tunnel with SeGW. If this tunnel is
broken, the data transport protected by IPsec will stop. The introduction of primary and backup
IPsec tunnels by this feature could help the IPsec protected data transport continues when one
of the tunnels is broken so that the reliability of IPsec transport is improved.

LTE TDD eRAN6.0
Description
During the deployment of LTE network, to guarantee the security of the service, the network is
divided into trusted and non-trusted parts. The SeGW 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 transport between SeGW and eNodeB in the non-trusted network.
When two SeGWs are used, eNodeB could establish two IPsec tunnels (one primary, one
backup) to the SeGWs. In normal condition, both tunnels are ready to be use. The eNodeB
chooses the primary tunnel based on the priority of IPsec tunnels for the uplink transport. For
the downlink transport, eNodeB should support receive data in primary and backup tunnels at
the same time because both tunnels are up and running, the data could be sent from SeGW to
eNodeB in either tunnel.
The eNodeB uses BFD to check the connectivity between itself and SeGW. If the primary
tunnel is broken, the eNodeB will hand over the uplink data transport to the backup tunnel. In
the downlink direction, the SeGW needs to support IPsec tunnel switching to a backup tunnel
together with eNodeB.
Enhancement
None
Dependencies
⚫ TDLOFD-003009 IPsec
⚫ TDLOFD-003007 Bidirectional Forwarding Detection
S-GW in core network should support this function.
2.90 TDLOFD-001010 Security Mechanism

2.90.1 TDLOFD-00101001 Encryption: AES
Availability
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 modification.

LTE TDD eRAN6.0
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.
From LTE TDD eRAN1.0, encryption algorithm AES is supported.
Enhancement
None
Dependencies
UE should support the same encryption algorithm as the eNodeB.
2.90.2 TDLOFD-00101002 Encryption: SNOW 3G

Availability
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 modification.
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 LTE TDD eRAN1.1 supports SNOW3G with 128 bits keys.

LTE TDD eRAN6.0
Enhancement
None
Dependencies
UE should support the same encryption algorithm as the eNodeB.
2.91 TDLOFD-00101003 Encryption: ZUC

Availability
Summary
Encryption provides confidentiality protection for signaling and user data between eNodeBs
and UEs.
Benefits
This feature prevents illegal interception and modification of signaling and user data.
Description
The eNodeB provides encryption for RRC signaling and user data. The encryption function
consists of ciphering and deciphering and is performed at the Packet Data Convergence
Protocol (PDCP) layer. After receiving the UE context from the EPC, the eNodeB initiates the
initial security activation procedure. During RRC connection setup, an encryption algorithm is
selected and an encryption key is generated based on the RRC protocol. All radio bearers use
the encryption algorithm and key.
The encryption algorithm can be changed by a handover. The encryption key can be changed by
a handover or RRC connection setup. The encryption keys for a UE in RRC_CONNECTED
mode may be changed by a handover procedure.
The ZUC algorithm is a word-oriented stream ciphering algorithm. It uses a 128-bit initial key
and a 128-bit initial vector (IV) as input, and then provides a key stream of 32-bit words, where
each 32-bit word is called a keyword. This key stream can be used for ciphering and
deciphering.
eRAN6.0 supports the ZUC algorithm.
Enhancement
None
Dependencies
UE and core network must support the same encryption algorithm.

LTE TDD eRAN6.0
2.92 TDLOFD-003009 IPsec

Availability
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 IPsec.
Figure 2-17 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 and 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.
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 (DES), Triple Data
Encryption Standard (3DES), and Advanced Encryption Standard (AES)

LTE TDD eRAN6.0
⚫ 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
Enhancement
None
Dependencies
This feature needs security gateway.
2.93 TDLOFD-003010 Public Key Infrastructure (PKI)

Availability
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.
For example, it is applied to the IPsec tunnel between the eNodeB and SeGW, and the SSL
channel between the 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 M2000.
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.

LTE TDD eRAN6.0
Figure 2-18 eRAN certificate application scenario
In LTE TDD eRAN2.0, eNodeB can update digital certificates automatically. And eNodeB can
update digital certificates automatically through M2000 proxy.
In LTE TDD 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 EE can utilize CMP to obtain certificates from the CA. This can be done through a 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.
CMP messages are encapsulated in HTTP/HTTPs messages for transmission.
Enhancement
None
Dependencies
The peer device should support the PKI functionality.
2.94 TDLOFD-003015 Access Control based on 802.1x

Availability
Summary
eNodeB support authentication to the transport network using 802.1x (Port-Based Network
Access Control). Authentication is based on the device certificate.

LTE TDD eRAN6.0
Benefits
This feature provides digital certificate authentication between eNodeB and LAN-Switch,
improving security in network domain.
Description
IEEE 802.1x (Port-Based Network Access Control) uses the physical access characteristics of
IEEE 802 LAN infrastructures to provide a method of authenticating and authorizing devices
attached to a LAN port that has point-to-point connection characteristics and of preventing
access to that port if 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).
Figure 2-19 eRAN 802.1x application scenario
Before the authentication and authorization process succeeds, only EAPoL (Extensible
Authentication Protocol over LAN) pocket can cross the LAN-Switch, and all the other pocket
will be dropped by LAN-Switch.
Enhancement
None
Dependencies
The peer device should support the 802.1x functionality.
⚫ TDLOFD-003010 Public Key Infrastructure (PKI)
2.95 TDLOFD-003014 Integrated Firewall

2.95.1 TDLOFD-00301401 Access Control List (ACL)
Availability

LTE TDD eRAN6.0
Summary
Access Control List (ACL) is comprised of a series of 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
The operating in the system is based on 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.
With Access Control List, operators can select data flows that need to be encrypted and
authenticated by IPsec, when IPsec is applied to guarantee security of the data flows.
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.
In eRAN3.0, eNodeB support that IPsec encrypted and authenticate selected data flows with
ACL under IPv6.
Enhancement
None
Dependencies
None
2.96 TDLOFD-001039 RF Channel Intelligent Shutdown

Availability
Summary
In MIMO mode, the carrier for a cell is transferred through different transmission channels.
When no traffic is on the cell, the carrier can be switched off on part of transmission channels.
In this way, the power consumption of the eNodeB in empty load mode is decreased. When
there is traffic, the carrier can be switched on automatically to have the cell run normally again.

LTE TDD eRAN6.0
Benefits
Without load, the eNodeB can switch off carrier on some transmit channels to reduce the power
consumption of the eNodeB.
Description
An eNodeB in the LTE system is usually configured with two or four antennas. The traffic in
the cell varies by time. In some certain periods, for example, from the midnight to the early
morning (operators can customize the periods), there is no traffic. When the idle status is
detected by the eNodeB, it switched off the carrier on one transmission channel (if there are two
transmission channels) or on two transmission channels (if there are four transmission channels)
to decrease the power consumption. When a UE accesses the cell or the periods end, the
eNodeB can automatically switch on the carrier that is switched off. Then, the cell recovers to
the normal state and continues with services.
Enhancement
None
Dependencies
⚫ TDLOFD-001001 DL 2x2 MIMO
⚫ OSS feature WOFD-200200 Base Station Power-Saving Management -LTE
2.97 TDLOFD-001040 Low Power Consumption Mode

Availability
Summary
In some cases like power outage, an eNodeB can be forced to run in low power consumption
mode. The low power consumption mode can help expand the in-service time of an eNodeB
powered by battery.

LTE TDD eRAN6.0
Benefits
In some cases like power outage, an eNodeB can be forced to run in low power consumption
mode. When an eNodeB is derated, its power consumption is reduced and its in-service time
powered by battery is expanded. Therefore, the possibility of eNodeB going out of service is
reduced when power supply cannot come back to service in time.
Description
The low consumption running mode is implemented in four levels. If the power supply still
cannot recover to the normal state when the power consumption of a level reaches the time
threshold preset by the operator, the eNodeB enters into the low consumption running mode of
the next level till the cell exits from services.
The low power consumption mode of the eNodeB is triggered by one of the following
conditions:
⚫ Alarms of the power system
If the power insufficiency or power failure lasts for the period preset by the operator, an
alarm is generated to trigger the low power consumption mode of the eNodeB.
⚫ Forcible command delivered by the EMS
The operator can deliver a command through the EMS to force the eNodeB to enter or exit
from the low power consumption mode.
Enhancement
None
Dependencies
2.98 TDLOFD-001041 Power Consumption Monitoring

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

LTE TDD eRAN6.0
Description
The eNodeB periodically monitors the power of each monitoring point and reports the power
consumption within a period. The EMS receives and collects all data about power consumption.
Through the EMS, the operator can observe the change in the power consumption and analyze
the power consumption according to a statistics report generated by the EMS.
Enhancement
None
Dependencies
2.99 TDLOFD-001042 Intelligent Power-Off of Carriers in

the Same Coverage
Availability
Summary
When there is little 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 little 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.

LTE TDD eRAN6.0
Enhancement
In eRAN3.1, RRU can adjust the voltage of power amplifier according to the remaining carriers
after the carriers shut off. For example, 2 carriers configured, when carrier one is shut down,
RRU will reduce the voltage of the power amplifier according to the remaining carrier 1, to
reduce more the power consumption.
Dependencies
⚫ TDLBFD-00201802 Coverage Based Inter-frequency Handover
2.100 TDLOFD-001056 PSU Intelligent Sleep Mode

Availability
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, thereby 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 therefore 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, ensuring their best level of efficiency.
Enhancement
None

LTE TDD eRAN6.0
Dependencies
The eNodeB with AC input should be configured with HUAWEI PSUs (converting AC into DC)
and HUAWEI PMU.
2.101 TDLOFD-001070 Symbol Power Saving

Availability
Summary
This feature introduces the function of symbol power saving. The eNodeB can shut down the
PAs in the time of empty symbols. MBSFN sub-frame could be used to reduce the reference
signal further so that more empty symbols are available for PA to shut down.
Benefits
When the traffic is light, the eNodeB can shut down the PAs in the time of empty symbols 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 no signal output, the PA needs static power
consumption. If PA supports the feature of fast power on and off, the system could utilize the
function of symbol power saving.
The eNodeB can shut down the PAs in the time of empty symbols to save the static power
consumption of the PA. To guarantee the integrity of data, the system needs to control the time
of PA's switch on and off.
For example, when there are no active users in the cell and only RSs need to be transmitted in
some subframes, the PA can be powered off in the OFDM symbols where there is no RS.
If the cell is not configured with the MBMS service, the eNodeB needs to add some of the
empty subframes to MBSFN subframes for further deep power saving. When one subframe is
configured as MBSFN subframe, only the first RS need to be transmitted in the air interface.
The result symbols in the subframe could be set null so that the PA could be turned off for those
symbols to reduce power consumption.
Figure 2-20 Symbol power saving

LTE TDD eRAN6.0
Enhancement
None
Dependencies
This feature is only applicable to macro eNodeBs
MBSFN subframe configuration need that UE can identify and apply the serving/neighbor
cell's MBSFN subframe configuration related.
This feature is only supported by the following RF module: RRU3232/RRU3235.
2.102 TDLOFD-001071 Intelligent Battery Management

Availability
Summary
With this feature, the battery management mode automatically changes depending on the
selected grid type, which prolongs the battery lifespan.
The battery self-protection function is triggered under high temperature, which avoids the
overuse of batteries and the consequent damages to the batteries.
The runtime of batteries is displayed after the mains supply is cut off. According to the runtime,
users can take measures in advance to avoid service interruption due to power supply cutoff.
Benefits
⚫ Prolonged battery lifespan
⚫ Less energy consumption
⚫ 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,

LTE TDD eRAN6.0
batteries can enter the hibernation state in which batters do not charge or discharge, which
helps prolong battery lifespan.
Power Grid Charge and Current Hibernation Hibernation Estimated
Supply Type Discharge Limitatio Voltage (V) Duration Battery Lifespan
Cutoff Mode n Valve (Days) Improvement
Duration Rate
Within 15
Days (Hours)
≤5 1 Mode A 0.10 C 52 13 100%

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

LTE TDD eRAN6.0
Feature Description 3 Acronyms and Abbreviations
3 Acronyms and Abbreviations
1xCS IWS Circuit Switched Fallback Interworking Solution Function for 3GPP2 1xCS
3GPP Third Generation Partnership Project
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 Neighbor Relation
ARP Allocation/Retention Priority
ARQ Automatic Repeat Request
BBU Baseband unit

BCH Broadcast Channel
BCCH Broadcast Control Channel
BE Best effort
BLER Block Error Rate
CAPEX Capital expenditure

C/I Carrier-to-Interference Power Ratio

LTE TDD eRAN6.0
CCCH Common Control Channel

CCO Cell change order
CCU cell center user
CDMA2000 Code Division Multiple Access (3G standard)
CDMA2000 1xRTT CDMA2000 1x radio transmission technology
CEU Cell Edge Users
CGI Cell Group Indicator
CME Configuration Management Express
CP Cyclic Prefix
CPICH Common Pilot Channel
CPRI common public radio interface
CPU central processing unit
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
CPU central processing unit
CS circuit switched
DCCH Dedicated Control Channel

DES Data Encryption Standard
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Services
DL-SCH Downlink Shared Channel
DRB Data Radio Bearer
DRX Discontinuous Reception
DSCP DiffServ Code Point
DTCH Dedicated Traffic Channel
ECM EPS Control Management

EDF Early Deadline First
EDGE Enhanced Data rates for GSM Evolution
EF Expedited Forwarding
eHRPD evolved high rate packet data
EMM EPS Mobility Management

LTE TDD eRAN6.0
EMS element management system

eNodeB E-UTRAN NodeB
EPC Evolved Packet Core
EPS Evolved Packet System
ESP Encapsulation Security Payload
ETWS Earthquake and Tsunami Warning System
E-RAB E-UTRAN radio access bearer
E-UTRAN evolved universal terrestrial radio access network
FCPSS Fault, Configuration, Performance, Security and Software Managements

FDD Frequency Division Duplex
TDD Time Division Duplex
FEC Forward Error Correction
FTP File Transfer Protocol
GBR Guaranteed Bit Rate

GERAN GSM/EDGE Radio Access Network
GPS Global Positioning System
GSM Global System for Mobile Communications
GUL GSM+UMTS+LTE
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
HSPA High Speed Packet Access
HSS home subscriber server
ICIC Inter-cell Interference Coordination

IKEV Internet Key Exchange Version

LTE TDD eRAN6.0
IMS IP Multimedia Service

IP PM IP Performance Monitoring
IPsec IP Security
IRC Interference Rejection Combining
IV initial vector
KPI Key Performance Indicator
LAI location area identity

LMT Local Maintenance Terminal
LTE Long Term Evolution
M2000 Huawei OMC

MAC Medium Admission Control
MIB Master Information Block
MCH Multicast Channel
MCCH Multicast Control Channel
MCS Modulation and Coding Scheme
MGW media gateway
MIMO Multiple Input Multiple Output
MinBR Minimum 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 Negative acknowledgment
NAS Non-Access Stratum
NE network element
NMS network management system

LTE TDD eRAN6.0
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
OPEX operating expense
PBCH Physical Broadcast Channel

PCCH Paging Control Channel
PCFICH Physical Control Format Indicator Channel
PCH Paging Channel
PCI Physical Cell Identity
PDB Packet Delay Budget
PDCCH Physical Downlink Control Channel
PDCP Packet Data Convergence Protocol
PDH Plesiochronous Digital Hierarchy
PDN packet data network
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
PS packet switched
PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Shared Channel
P-GW PDN gateway

LTE TDD eRAN6.0
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
RAN radio access network
RAT Radio Access Technology
RB Resource Block
RCU Radio Control Unit
RET Remote Electrical Tilt
RF Radio Frequency
RIM RAN Information Management
RLC Radio Link Control
RNC radio network controller
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

LTE TDD eRAN6.0
SDMA space division multiple access

SFBC Space Frequency Block Coding
SFN single frequency network
SFP Small Form – factor Pluggable
SGW Serving Gateway
SIB System Information Block
SID Silence Indicator
SINR Signal to Interference plus Noise Ratio
SPID subscriber profile ID
SRB Signaling Radio Bearer
SRS Sounding Reference Signal
SSL Secure Sockets Layer
STBC Space Time Block Coding
STMA Smart TMA
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
UMTS Universal Mobile Telecommunications System
USB Universal Serial Bus
UTRAN universal terrestrial radio access network
VLAN Virtual Local Area Network

VoIP Voice over IP

LTE TDD eRAN6.0
WRR Weighted Round Robin
X2 interface among eNodeBs


Appendix8 LTETDDeRAN6.0FeatureDescriptionDraftB

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Appendix8 LTETDDeRAN6.0FeatureDescriptionDraftB

Uploaded by

Copyright:

Available Formats

LTE TDD eRAN6.

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2012-11-15) Huawei Proprietary and Confidential i

About This Document

Draft B 2013-01-07 1. Add TDLOFD-001016 VoIP Semi-persistent Scheduling Dependencies:

Issue 01 (2012-11-15) Huawei Proprietary and Confidential ii

2013-01-05 1. Enhance TDLOFD-001007 High Speed Mobility to support 4T4R mode

2012-12-24 1. Enhance TDLOFD-001033 CS Fallback to UTRAN to support Blind handover

Issue 01 (2012-11-15) Huawei Proprietary and Confidential iii

4. Modify TDLOFD-001035 CS Fallback to CDMA2000 1xRTT Dependencies:

Draft A 2012-12-10 This issue is a draft.

Issue 01 (2012-11-15) Huawei Proprietary and Confidential iv

About This Document .................................................................................................................... ii

Issue 01 (2012-11-15) Huawei Proprietary and Confidential v

1.28 TDLBFD-002018 Mobility Management .................................................................................................... 27

Issue 01 (2012-11-15) Huawei Proprietary and Confidential vi

1.48 TDLBFD-004005 Hot Patch Management................................................................................................... 60

2 Optional Features ........................................................................................................................ 70

Issue 01 (2012-11-15) Huawei Proprietary and Confidential vii

2.30 TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA.................................................................................. 105

Issue 01 (2012-11-15) Huawei Proprietary and Confidential viii

2.65 TDLOFD-002004 Self-configuration ......................................................................................................... 148

Issue 01 (2012-11-15) Huawei Proprietary and Confidential ix

2.96 TDLOFD-001039 RF Channel Intelligent Shutdown ................................................................................ 188

3 Acronyms and Abbreviations ................................................................................................. 196

Issue 01 (2012-11-15) Huawei Proprietary and Confidential x

1.1 TDLBFD-001001 3GPP R8 Specifications

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 1

1.2 TDLBFD-001008 3GPP R9 Specifications

1.3 TDLBFD-001009 3GPP R10 Specifications

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 2

1.4 TDLBFD-001002 TDD mode

1.5 TDLBFD-001003 Scalable Bandwidth

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 3

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 4

1.6 TDLBFD-001004 CP length

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 5

1.7 TDLBFD-001005 Modulation: DL/UL QPSK, DL/UL

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 6

1.8 TDLBFD-001006 AMC

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 7

1.9 TDLBFD-001007 Basic uplink-downlink subframe

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 8

⚫ TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA

1.9.2 TDLBFD-00100702 uplink-downlink special subframe

Special subframe Normal cyclic prefix

7 21952  Ts 4384  Ts 4384  Ts

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 9

1.10 TDLBFD-002001 Logical Channel Management

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 10

1.11 TDLBFD-002002 Transport Channel Management

1.12 TDLBFD-002003 Physical Channel Management

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

1.13 TDLBFD-002004 Integrity Protection

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 12

1.14 TDLBFD-002005 DL Asynchronous HARQ

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 13

1.15 TDLBFD-002006 UL Synchronous HARQ

Issue 01 (2012-11-15) Huawei Proprietary and Confidential 14

1.16 TDLBFD-002007 RRC Connection Management

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

1.17 TDLBFD-002008 Radio Bearer Management