eRAN7 0 LTE FDD Basic Feature Description 01 20140915 PDF

eRAN7.
0
V100R007C00
eRAN7.0 LTE FDD Basic Feature
Description
Issue 01
Date 2014-05-04
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Huawei Proprietary and Confidential

Issue 01 (2014-05-04) i
Copyright © Huawei Technologies Co., Ltd.
eRAN7.0
eRAN7.0 LTE FDD Basic Feature Description Contents
Contents
1 Basic Features ................................................................................................................................. 1

1.1 Standards Compliance .................................................................................................................................................. 1
1.1.1 LBFD-001001 3GPP R8 Specifications..................................................................................................................... 1
1.1.2 LBFD-001007 3GPP R9 Specifications..................................................................................................................... 2
1.1.3 LBFD-001008 3GPP R10 Specifications................................................................................................................... 2
1.1.4 LBFD-001002 FDD mode ......................................................................................................................................... 3
1.1.5 LBFD-001003 Scalable Bandwidth ........................................................................................................................... 4
1.1.6 LBFD-001004 CP length ........................................................................................................................................... 5
1.1.6.1 LBFD-00100401 Normal CP .................................................................................................................................. 5
1.1.7 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM .............................................................. 6
1.1.8 LBFD-001006 AMC .................................................................................................................................................. 7
1.2 RAN Architecture & Features ....................................................................................................................................... 8
1.2.1 LBFD-002001 Logical Channel Management ........................................................................................................... 8
1.2.2 LBFD-002002 Transport Channel Management ........................................................................................................ 9
1.2.3 LBFD-002003 Physical Channel Management ....................................................................................................... 10
1.2.4 LBFD-002004 Integrity Protection .......................................................................................................................... 11
1.2.5 LBFD-002005 DL Asynchronous HARQ ................................................................................................................ 12
1.2.6 LBFD-002006 UL Synchronous HARQ .................................................................................................................. 13
1.2.7 LBFD-002007 RRC Connection Management ........................................................................................................ 14
1.2.8 LBFD-002008 Radio Bearer Management .............................................................................................................. 15
1.2.9 LBFD-002009 Broadcast of system information ..................................................................................................... 16
1.2.10 LBFD-002010 Random Access Procedure ............................................................................................................ 17
1.2.11 LBFD-002011 Paging ............................................................................................................................................ 18
1.2.12 LBFD-002012 Cell Access Radius up to 15km ..................................................................................................... 19
1.2.13 LBFD-002023 Admission Control ......................................................................................................................... 20
1.2.14 LBFD-002024 Congestion Control ........................................................................................................................ 21
1.2.15 LBFD-002025 Basic Scheduling ........................................................................................................................... 22
1.2.16 LBFD-002026 Uplink Power Control.................................................................................................................... 23
1.2.17 LBFD-002016 Dynamic Downlink Power Allocation ........................................................................................... 25
1.2.18 LBFD-002017 DRX .............................................................................................................................................. 26
1.2.19 LBFD-002018 Mobility Management ................................................................................................................... 27
1.2.19.1 LBFD-00201801 Coverage Based Intra-frequency Handover ............................................................................ 27
1.2.19.2 LBFD-00201802 Coverage Based Inter-frequency Handover ............................................................................ 28
Issue 01 (2014-05-04) Huawei Proprietary and Confidential ii

eRAN7.0
1.2.19.3 LBFD-00201803 Cell Selection and Re-selection .............................................................................................. 30

1.2.19.4 LBFD-00201804 Distance Based Inter-frequency Handover ............................................................................. 31
1.2.19.5 LBFD-00201805 Service Based Inter-frequency Handover ............................................................................... 31
1.2.20 LBFD-002020 Antenna Configuration .................................................................................................................. 32
1.2.20.1 LBFD-00202001 UL 2-Antenna Receive Diversity ........................................................................................... 32
1.2.21 LBFD-002021 Reliability ...................................................................................................................................... 33
1.2.21.1 LBFD-00202101 Main Processing and Transport Unit Cold Backup ................................................................ 33
1.2.21.2 LBFD-00202102 Cell Re-build Between Baseband Processing Units ............................................................ 34
1.2.21.3 LBFD-00202103 SCTP Multi-homing ............................................................................................................... 36
1.2.21.4 LBFD-00202104 Intra-baseband Card Resource Pool (user level/cell level) ..................................................... 37
1.2.22 LBFD-002022 Static Inter-Cell Interference Coordination ................................................................................... 37
1.2.22.1 LBFD-00202201 Downlink Static Inter-Cell Interference Coordination............................................................ 37
1.2.22.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination ................................................................ 38
1.2.23 LBFD-002027 Support of UE Category 1 ............................................................................................................. 39
1.2.24 LBFD-002028 Emergency Call ............................................................................................................................. 41
1.2.25 LBFD-002029 Earthquake and Tsunami Warning System (ETWS) ...................................................................... 42
1.2.26 LBFD-002031 Support of aperiodic CQI reports .................................................................................................. 44
1.2.27 LBFD-002032 Extended-QCI ................................................................................................................................ 44
1.2.28 LBFD-002033 SCTP Congestion Control ............................................................................................................. 45
1.2.29 LBFD-002034 RRU Channel Cross Connection Under MIMO ............................................................................ 46
1.2.30 LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting ............................................................... 48
1.2.31 LBFD-060102 Enhanced UL Frequency Selective Scheduling ............................................................................. 49
1.2.32 LBFD-060103 Enhanced DL Frequency Selective Scheduling ............................................................................. 50
1.2.33 LBFD-070103 Multi-Band Compatibility Enhancement ....................................................................................... 51
1.2.34 LBFD-070101 Uplink Timing Based on PUCCH ................................................................................................. 52
1.2.35 LBFD-070102 MBR>GBR Configuration ............................................................................................................ 53
1.2.36 LBFD-070105 IoT-based PUSCH Power Control ................................................................................................. 54
1.2.37 LBFD-070106 PDSCH Efficiency Improvement .................................................................................................. 55
1.2.38 LBFD-070107 PDCCH Utilization Improvement ................................................................................................. 56
1.3 Transmission & Security ............................................................................................................................................. 57
1.3.1 LBFD-003001 Transmission Networking ................................................................................................................ 57
1.3.1.1 LBFD-00300101 Star Topology ........................................................................................................................... 57
1.3.1.2 LBFD-00300102 Chain Topology ........................................................................................................................ 58
1.3.1.3 LBFD-00300103 Tree Topology ........................................................................................................................... 59
1.3.2 LBFD-003002 Basic Qos Management ................................................................................................................... 60
1.3.2.1 LBFD-00300201 DiffServ QoS Support .............................................................................................................. 60
1.3.3 LBFD-003003 VLAN Support (IEEE 802.1p/q) ..................................................................................................... 62
1.3.4 LBFD-003004 Compression & Multiplexing over E1/T1 ....................................................................................... 63
1.3.4.1 LBFD-00300401 IP Header Compression ............................................................................................................ 63
1.3.4.2 LBFD-00300402 PPP MUX ................................................................................................................................. 63
1.3.4.3 LBFD-00300403 ML-PPP/MC-PPP ..................................................................................................................... 64
1.3.5 LBFD-003005 Synchronization ............................................................................................................................... 66
Issue 01 (2014-05-04) Huawei Proprietary and Confidential iii

eRAN7.0
1.3.5.1 LBFD-00300501 Clock Source Switching Manually or Automatically ............................................................... 66

1.3.5.2 LBFD-00300502 Free-running Mode ................................................................................................................... 67
1.3.5.3 LBFD-00300503 Synchronization with GPS ....................................................................................................... 67
1.3.5.4 LBFD-00300504 Synchronization with BITS ...................................................................................................... 68
1.3.5.5 LBFD-00300505 Synchronization with 1PPS ...................................................................................................... 69
1.3.5.6 LBFD-00300506 Synchronization with E1/T1 ..................................................................................................... 70
1.3.6 LBFD-003006 IPv4/IPv6 Dual Stack ...................................................................................................................... 71
1.4 Operation & Maintenance ........................................................................................................................................... 72
1.4.1 LBFD-004001 Local Maintenance of the LMT ....................................................................................................... 72
1.4.2 LBFD-004002 Centralized U2000 Management ..................................................................................................... 72
1.4.3 LBFD-004003 Security Socket Layer ..................................................................................................................... 73
1.4.4 LBFD-004004 Software Version Upgrade Management ......................................................................................... 74
1.4.5 LBFD-004005 Hot Patch Management ................................................................................................................... 75
1.4.6 LBFD-004006 Fault Management ........................................................................................................................... 76
1.4.7 LBFD-004007 Configuration Management ............................................................................................................. 78
1.4.8 LBFD-004008 Performance Management ............................................................................................................... 79
1.4.9 LBFD-004009 Real-time Monitoring of System Running Information .................................................................. 80
1.4.10 LBFD-004010 Security Management .................................................................................................................... 81
1.4.11 LBFD-004011 Optimized eNodeB Commissioning Solution ................................................................................ 82
1.4.12 LBFD-004012 Environment Monitoring ............................................................................................................... 83
1.4.13 LBFD-004013 Inventory Management .................................................................................................................. 83
1.4.14 LBFD-004014 License Management ..................................................................................................................... 84
1.4.15 LBFD-004015 License Control for Urgency ......................................................................................................... 85
1.4.16 LBFD-070104 Site Transmission Equipment Fault Detection .............................................................................. 86
2 Acronyms and Abbreviations ................................................................................................... 91
Issue 01 (2014-05-04) Huawei Proprietary and Confidential iv

eRAN7.0
eRAN7.0 LTE FDD Basic Feature Description Figures
Figures
Figure 1-1 3*10M 2T2R ..................................................................................................................................... 35

Figure 1-2 Stream Control Transmission Protocol .............................................................................................. 36
Figure 1-3 Overview of Earthquake and Tsunami Warning System ................................................................. 43
Figure 1-4 RRU channel cross connection under MIMO .................................................................................... 47

Figure 1-5 Comparing with no MIMO load Sharing ........................................................................................... 48
Figure 1-6 Star topology ...................................................................................................................................... 57
Figure 1-7 Chain topology .................................................................................................................................. 58
Figure 1-8 Tree topology ..................................................................................................................................... 60
Figure 1-9 ML-PPP/MC-PPP .............................................................................................................................. 65
Figure 1-10 License file management ................................................................................................................. 85
Issue 01 (2014-05-04) Huawei Proprietary and Confidential v

eRAN7.0
eRAN7.0 LTE FDD Basic Feature Description Tables
Tables
Table 1-1 Preamble formats and cell access radius.............................................................................................. 19
Table 1-2 Downlink physical layer parameter values set by the field UE-Category ........................................... 40
Table 1-3 Uplink physical layer parameter values set by the field UE-Category ................................................ 40
Table 1-4 Total layer 2 buffer sizes set by the field UE-Category ....................................................................... 40
Table 1-5 Relationship between QCI and DSCP ................................................................................................. 61

Table 2-1 Acronyms and Abbreviations ............................................................................................................... 91
Issue 01 (2014-05-04) Huawei Proprietary and Confidential vi

eRAN7.0
eRAN7.0 LTE FDD Basic Feature Description 1 Basic Features
1 Basic Features
About This Chapter

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

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

eRAN7.0
standard development during Huawei product development. LTE eNodeB supports 3GPP
Release 8 2009Q3.
Enhancement
None
Dependency
None

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

Availability
This feature is

eRAN7.0

Summary
Huawei LTE eNodeB is compliant with 3GPP Release 10 specifications.
Benefits
None
Description
Release 10 specifications 2011.03 version.
Enhancement
None
Dependency
None
1.1.4 LBFD-001002 FDD mode

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

eRAN7.0
Enhancement
None
Dependency
 Others
The related network elements (NEs) should support FDD mode.
1.1.5 LBFD-001003 Scalable Bandwidth

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

eRAN7.0
1.1.6 LBFD-001004 CP length

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

eRAN7.0
1.1.7 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL

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

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

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

eRAN7.0
Dependency
None
1.2 RAN Architecture & Features

1.2.1 LBFD-002001 Logical Channel Management
Availability
This feature is
Summary
The logical channels are provided between the Medium Access Control (MAC) layer and the
Radio Link Control (RLC) layer. Each logical channel type is defined according to the type of
the transmitted data. They are generally classified into two types: control channels and traffic
channels.
In Huawei LTE eNodeB, all logical channels are supported except those related to the evolved
Multimedia Broadcast Multicast Service (eMBMS) functionality.
Benefits
The logical channels are responsible for what type of information is transferred.
Description
The logical channels are provided between the MAC layer and the RLC layer. They are
responsible for "what is transported". They are generally classified into two types:
 Control channels: for transmitting the control plane information
 Traffic channels: for transmitting the user plane information
Control channels include:
 Broadcast Control Channel (BCCH)
 Paging Control Channel (PCCH)
 Common Control Channel (CCCH)
 Multicast Control Channel (MCCH)
 Dedicated Control Channel (DCCH)
Traffic channels include:
 Dedicated Traffic Channel (DTCH)
 Multicast Traffic Channel (MTCH)

eRAN7.0
In Huawei LTE eNodeB, all logical channels are supported except those related to the
eMBMS functionality, such as MCCH and MTCH.
Enhancement
None
Dependency
None
1.2.2 LBFD-002002 Transport Channel Management

Availability
This feature is
Summary
Transport channels that are provided between the MAC layer and the physical layer, are
defined according to the type of transmitted data and the method of data transmission over the
radio interface. They are used to offer the information about transmission services for the
MAC and higher layers. In Huawei LTE eNodeB, all transport channels except those related
to the eMBMS functionality are supported.
Benefits
The transport channels are responsible for what type of data is transmitted and how the data is
transmitted.
Description
The transport channels are provided between the MAC layer and the physical layer. They are
responsible for what type of data is transmitted and how the data is transmitted over the radio
interface.
Downlink transport channels are classified into the following types:
 Broadcast Channel (BCH)
 Downlink Shared Channel (DL-SCH)
 Paging Channel (PCH)
 Multicast Channel (MCH)
Uplink transport channels are classified into the following types:
 Uplink Shared Channel (UL-SCH)
 Random Access Channel (RACH)
In Huawei LTE eNodeB, all transport channels are supported except those related to the
eMBMS functionality, such as MCH.

eRAN7.0
Enhancement
None
Dependency
None
1.2.3 LBFD-002003 Physical Channel Management

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

eRAN7.0
In Huawei LTE eNodeB, all physical channels are supported except those related to the
eMBMS functionality, such as PMCH.
Enhancement
None
Dependency
None
1.2.4 LBFD-002004 Integrity Protection

Availability
This feature is
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
code and compares it with the code in the message. If the two codes are inconsistent, the
receiver knows that the message has been modified illegally.
The eNodeB decides which integrity algorithm to use and informs each UE of it through an
RRC message.
Enhancement
 In eRAN2.0
In addition to the AES, Huawei eRAN2.0 also supports integrity algorithm SNOW3G.
 In eRAN6.0
Macro also supports integrity algorithm ZUC.
 In eRAN7.0
Micro also supports integrity algorithm ZUC.

eRAN7.0
Dependency
 UE
The UE should support the same integrity algorithm as the eNodeB.
1.2.5 LBFD-002005 DL Asynchronous HARQ

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

eRAN7.0
In LTE specifications, multiple downlink HARQ processes are adopted to fully utilize system
resources. It greatly improves the system throughput and reduces the latency, but it requires
more buffer space and signaling overhead.
Enhancement
None
Dependency
None
1.2.6 LBFD-002006 UL Synchronous HARQ

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

eRAN7.0
according to the channel quality. But the retransmission transport block size remains the same
as the first transmission.
In LTE specifications, UL HARQ scheme is based on an IR algorithm. After the retransmitted
data is received, HARQ process in the eNodeB will soft-combine the retransmitted data with
the previously buffered content and forward the combined data to the FEC for decoding. The
soft-combined data will help increase the probability of successful FEC decoding, thus
increasing the data reception success rate.
In LTE specifications, multiple uplink HARQ processes are adopted to fully utilize system
resources. It greatly improves the system throughput and reduces the latency, but it requires
more buffer space and signaling overhead.
Enhancement
 In eRAN2.0
Huawei supports a synchronous adaptive UL HARQ transmission. While in eRAN1.0,
Uplink HARQ is a synchronization non-adaptive transmission process.
Dependency
None
1.2.7 LBFD-002007 RRC Connection Management

Availability
This feature is
Summary
RRC connection is the layer 3 connection between the UE and eNodeB. The RRC connection
management aims to manage the layer 3 connection, including establishment, maintenance,
and release of the connection.
Benefits
The RRC connection management is essential from the UE to E-UTRAN, and serves all
service procedures and NAS procedures.
Description
RRC connection management involves RRC connection establishment, RRC connection
reconfiguration, RRC connection re-establishment, and RRC connection release.
 RRC connection establishment: This procedure is performed to establish an RRC
connection. RRC connection establishment involves Signaling Radio Bearer 1 (SRB1)
establishment. The procedure is also used to transmit the initial NAS dedicated
information or messages from the UE to the E-UTRAN.

eRAN7.0
 RRC connection reconfiguration: This procedure is performed to modify an RRC

connection, for example, to establish, modify, or release radio bearers, to perform
handovers, and to configure or modify measurements. As a part of the procedure, NAS
dedicated information may be transmitted from the E-UTRAN to the UE.
 RRC connection re-establishment: This procedure is performed to re-establish an RRC
connection after a handover failure or radio link failure. RRC connection
re-establishment involves the restoration of SRB1 operation and the re-activation of
security. A UE in RRC_CONNECTED mode, for which security has been activated, may
initiate the procedure in order to continue the RRC connection. The connection
re-establishment will succeed only if the cell has a valid UE context.
 RRC connection release: This procedure is performed to release an RRC connection.
RRC connection release involves the release of the established radio bearers and the
release of all radio resources.
Enhancement
None
Dependency
None
1.2.8 LBFD-002008 Radio Bearer Management

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

eRAN7.0
Dependency
None
1.2.9 LBFD-002009 Broadcast of system information

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

eRAN7.0
 SystemInformationBlockType5 contains the information about other E-UTRA

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

Availability
This feature is
Summary
Random access is 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 and UE is out-of-sync with eNodeB in
uplink

eRAN7.0
 UL data arrival during RRC_CONNECTED and UE is out-of-sync with eNodeB in

uplink
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
eNodeB supports random access preamble formats 0–3 and PRACH configurations 0–63 (TS
36.211).
Enhancement
None
Dependency
None
1.2.11 LBFD-002011 Paging

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

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

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

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

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

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

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

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

eRAN7.0
Description
This feature is critical to maintain the system stability and deliver acceptable Quality of
Service (QoS) when the system is in congestion.
In eNodeB, congestion control is provided in which a method are introduced:
The method is to release low-priority services to alleviate the overloaded system, where the
priority is determined based on the ARP assigned to the service.
Enhancement
Size reduction on GBR service is not accepted by most operators and is not recommended
according to 3GPP. Function of size reduction on GBR service is removed when cell is in
congestion.
Dependency
None
1.2.15 LBFD-002025 Basic Scheduling

Availability
This feature is
Summary
The basic scheduling feature provides three common scheduling algorithms (MAX C/I and
RR and PF). The operator can select either algorithm.
Benefits
This feature provides the flexibility for the operator to select the scheduling algorithm,
considering the system capacity and fairness among the users.
Description
Scheduling algorithm enables the system to decide the resource allocation for each UE during
each TTI. This feature provides different scheduling algorithms, considering the tradeoff
between system capacity and fairness among the users.
There are three scheduling algorithms provided and the operator can decide which algorithm
to take.
 MAX C/I
 Round Robin
 PF (proportional fair)

eRAN7.0
With MAX C/I, users are scheduled based on their radio channel quality. The radio channel
quality is the only factor to be considered in this algorithm and therefore, the fairness among
users cannot be guaranteed.
With Round Robin, users are scheduled on turn and neglects of their radio quality. So all the
users have the same chance to get the resource and the fairness among uses is guaranteed. But
the system capacity is lowest among three scheduling algorithms.
With PF, users are scheduled according to the value of R/r, where R is the maximum data rate
corresponding to the channel quality, and r is the average data rate of the user. The PF
scheduler, based on the radio channel quality of an individual user, provides the user with an
average throughput proportional to its average channel quality. This algorithm is typically
used by a wireless system to achieve a moderate cell capacity while to ensure fairness among
users.
Enhancement
 In eRAN2.0
Round Robin is added in this feature.
Dependency
None
1.2.16 LBFD-002026 Uplink Power Control

Availability
This feature is
Summary
Uplink power control in LTE system is essential to the control of the eNodeB over the uplink
transmitting 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 transmitting 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

eRAN7.0
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 transmitting 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 transmitting
power. If the estimated PSD is smaller than PSDTarget, the eNodeB sends a TPC
command, ordering an increase of the transmitting power.
For Semi-persistent Scheduling:
 In Semi-persistent Scheduling, based on the difference between the measured IBLER
and IBLERTarget, the transmitting 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
transmitting power. If the measured IBLER is smaller than IBLERTarget, the eNodeB
sends a TPC command to the UE, ordering a decrease of the transmitting 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 transmitting
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 transmitting power. If the measured SINR is
smaller than SINRTarget, the eNodeB sends a TPC command, ordering an increase of the
transmitting 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 transmitting 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 (e.g. no RA preamble response for the
eNodeB), the UE can increase the transmitting power for the next RA preamble attempt
according to the settings configured by the RRC layer.
Enhancement
None
Dependency
None

eRAN7.0
1.2.17 LBFD-002016 Dynamic Downlink Power Allocation

Availability
This feature is
Summary
Dynamic Downlink Power Allocation allows an eNodeB to dynamically set the transmitting
power at downlink channels to reduce power consumption while maintaining the quality of
radio links. It provides flexible power allocation for downlink channels based on the user's
channel quality and maintains acceptable quality of the downlink connections.
Benefits
This feature allows flexible power allocation for downlink channels based on the user's
channel quality and maintains acceptable quality of the downlink connections. Therefore, it
can improve the edge user throughput and transmission power usage.
Description
The LTE downlink power allocation consists of several parts corresponding to different types
of downlink channels, such as Physical Downlink 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
PDCCH and PDSCH; since the transmitting power of those signals and channels are
needed to ensure the downlink coverage of the cell.
 SINRRS estimation is based on the CQI report. Based on the difference between the
estimated SINRRS and SINRTarget, the transmitting power of the PHICH is periodically
adjusted according to the path loss and shading. If SINRRS is smaller than SINRTarget,
the transmitting power is increased. Otherwise, the transmitting 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 there is 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 transmitting power of the PDSCH is periodically
adjusted to meet IBLERTarget requirements. If the measured IBLER is smaller than
IBLERTarget, the transmitting power is decreased. Otherwise, the transmitting power
is increased. The transmit power for the PDCCH is periodically adjusted according to
the DTX. If the DTX cannot meet system demand, transmit power is increased.
Enhancement
 In eRAN2.0

eRAN7.0
PDSCH and PDCCH dynamic power control is optimized.
Dependency
None
1.2.18 LBFD-002017 DRX

Availability
This feature is
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 sub-frames.
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.
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.
DRX may also be used for CGI measurement in ANR.
Enhancement
 In eRAN 3.0
Up to 320ms Long DRX cycle in sync is introduced, while up to 40ms Long DRX cycle
in sync was supported in version before.
Dependency
None

eRAN7.0
1.2.19 LBFD-002018 Mobility Management

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

eRAN7.0
 Handover between two cells configured in the same eNodeB. No external neighbor cell
is needed. This scenario is not applicable to Micro eNodeB because Micro eNodeB only
supports one cell.
 Handover between two cells configured in different eNodeBs with an X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUEST message
over the X2 interface.
 Handover between two cells configured in different eNodeBs with no X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUIRED message
over the S1 interface.
Enhancement
 In eRAN2.2
Each PLMN id of eNodeB will have its own PLMN list; each PLMN list can contain at
most 8 PLMN Identities; PLMN list is used as an access list for serving cell to judge
whether UE could handover to target cell in Inter-PLMN handover; Other cell, whose
PLMN ids are all different with serving cell PLMN id in which UE is located and at
same time are not in its PLMN list, will not be considered as target cell in handover
process for this UE.
Dependency
None
1.2.19.2 LBFD-00201802 Coverage Based Inter-frequency Handover
Availability
This feature is
Summary
Inter-Frequency Handover enables a UE in RRC-CONNECTED mode to be served
continuously when it moves across different cells that are operating at different frequencies.
Benefits
The coverage-based inter-frequency handover provides supplementary coverage in
inter-frequency LTE systems to prevent call drop, enable seamless coverage, and therefore
improve the network performance and end user experience.
Description
This feature is one of the fundamental functions for an LTE system. The purpose of
inter-frequency handover is to ensure that a UE in RRC-CONNECTED mode is served
continuously when it moves across different cells operating at different frequencies.
The inter-frequency handover procedure can be divided into four phases: measurement
triggering, handover measurement, handover decision, and handover execution.

eRAN7.0
In inter-frequency handover, neighboring cell measurements are inter-frequency

measurements. The measurement is gap assisted for UEs with one RF receiver. The
measurement is triggered by an event A2 and stopped by an event A1, based on the
monitoring on the value of RSRP or RSRQ.
In inter-frequency handover, the UE sends measurement reports to the eNodeB when the
RSRP or RSRQ meets the criteria set in the measurement configuration.
Upon receiving a measurement report from the UE, the eNodeB makes a handover decision.
If the measurement meets the handover criteria, the eNodeB will perform the corresponding
inter-frequency handover as specified in TS 36.300.
The following inter-frequency handover scenarios are applicable:
 Handover between two cells configured in the same eNodeB. In this case, the UE
performs the handover between two cells configured in the same eNodeB and no
external interface is required. This scenario is not applicable to Micro eNodeB because
Micro eNodeB only supports one cell.
 Handover between two cells configured in different eNodeBs with an X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUEST message
over the X2 interface.
 Handover between two cells configured in different eNodeBs with no X2 interface
available. In this case, the source eNodeB sends a HANDOVER REQUIRED message
over the S1 interface.
Enhancement
 eRAN2.2
Each PLMN id of eNodeB will have its own PLMN list; each PLMN list can contain at
most 8 PLMN Identities; PLMN list is used as an access list for serving cell to judge
whether UE could handover to target cell in Inter-PLMN handover; Other cell, whose
PLMN ids are all different with serving cell PLMN id in which UE is located and at
same time are not in its PLMN list, will not be considered as target cell in handover
process for this UE.
 eRAN3.0
The inter-frequency handover based on UL power is supported. It guarantees service
continuity in uplink limited power when a UE moves to the cell edge.
 eRAN6.0
The urgent redirection function has been provided by this feature. After a UE accesses a
cell, the eNodeB delivers two sets of event A2 configurations. One is used for triggering
measurements, and the other is used for triggering urgent redirection. The triggering of
event A2 for urgent redirection indicates that the signal quality in the serving cell has
become too poor to provide services for the UE. In this case, the eNodeB blindly
redirects the UE to a neighboring GERAN, UTRAN, or E-UTRAN cell.
Dependency
 UE
UE should support for inter-frequency Gap measurements

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

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

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

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

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

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

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

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

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

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

eRAN7.0
1.2.21.4 LBFD-00202104 Intra-baseband Card Resource Pool (user level/cell

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

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

eRAN7.0

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
so as 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 in order 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 static CEU frequency band is carefully planned to avoid overlapping. The
transmitting 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 within
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 frequency reuse 3. Among three
neighboring cells, each cell will use different 1/3 of the frequency band for the CEUs.
Enhancement
None
Dependency
None
1.2.22.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination
Availability
This feature is

eRAN7.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.
Benefits
Uplink ICIC reduces inter-cell interference; therefore improve cell edge users 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 transmitting power control and resource
allocation in frequency domain 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, the coordination is achieved at the frequency domain,
where the cell edge users are given non-overlapping frequency bands. That is, the frequency
band allocation for static UL ICIC is per cell basis.
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.
Enhancement
None
Dependency
None
1.2.23 LBFD-002027 Support of UE Category 1

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

eRAN7.0
Benefits
This feature can enable base station to support UE category 1.
Description
E-UTRAN needs to respect the signaled UE radio access capability parameters when
configuring the UE and when scheduling the UE. There are five categories defined in the
protocol. This feature can enable base station to support UE category 1.
Table 1-2 Downlink physical layer parameter values set by the field UE-Category
UE Category Maximum Maximum Total number of Maximum
number of number of bits soft channel number of
DL-SCH of a DL-SCH bits supported
transport blocks transport block layers for
bits received received within spatial
within a TTI a TTI multiplexing in
DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
Table 1-3 Uplink physical layer parameter values set by the field UE-Category
UE Category Maximum number of bits of Support for 64QAM in UL
an UL-SCH transport block
transmitted within a TTI
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No
Category 5 75376 Yes
Table 1-4 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

eRAN7.0
Category 3 1400
Category 4 1900
Category 5 3500
Enhancement
None
Dependency
 UE
UE should support the same category as eNodeB.
1.2.24 LBFD-002028 Emergency Call

Availability
This feature is
Summary
The emergency call service is an operator-assisted service that connects a caller in a
life-threatening or time-critical situation to an emergency service organization.
Benefits
This feature provides all users, even those without SIM, a prioritized connection to an
emergency service organization.
Description
The emergency Call service is an operator-assisted service that connects a caller in a
life-threatening or time-critical situation to an emergency service organization such as police,
hospital and fire station.
New features in E-UTRAN to support emergency call are as follows:
 Support of identifying emergency call users
 Support of special processing such as access class barring and priority handling for the
network access and mobility management
 Support of location service for emergency call users. This function depends on the
feature LOFD-001047 LoCation Services (LCS).
Admission of an emergency call is prioritized over other ongoing sessions in the eNodeB to
enable call completion. Regardless of network features/services activated in the network (for
example, unconditional call-forwarding, or incoming call barring), the Public Safety

eRAN7.0
Answering Point (PSAP, used in US)/ Emergency Centre (EC, used in Europe) is able to get
emergency caller's location by means of LCS and call back the caller once an emergency call
has been placed. The emergency call, served on LTE with multi-mode terminal, fallbacks to
UMTS or GSM depending upon LTE VoIP support.
Four types of users are permitted to initiate an emergency call:
 Common user: normal subscriber
 Common restricted user: normal subscriber, whose calls are restricted for some reasons
(for example, out of coverage of own PLMN)
 Restricted user with SIM card: User, whose SIM card fails to authenticate, uses IMEI
(International Mobile Equipment Identity) to initiate an emergency call.
 Restricted user without SIM card: User, without SIM card, uses IMEI to initiate an
emergency call
This feature supports 911 Emergency Calls (North America) / 112 Emergency Calls (Europe)
in its SAE/LTE network as defined by 3GPP specification.
Enhancement
None
Dependency
 UE
UE should support IMS based voice service on LTE or voice service on 2G/3G.
 CN
The emergency call should be supported in the core network.
 Other features
The location service for emergency call users function depends on the optional feature
LOFD-001047 LoCation Services (LCS).
 Others
If IMS is not deployed, the support of the optional feature CS Fallback to
GERAN/UTRAN/CDMA2000 will be needed.
1.2.25 LBFD-002029 Earthquake and Tsunami Warning System

(ETWS)
Availability
This feature is
Summary
When an event occurs e.g. an Earthquake, Warning Notification Providers produce Warning
Notification to PLMN operator, PLMN operators distribute Warning Notifications to users by
utilizing Earthquake and Tsunami Warning System(ETWS).

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

eRAN7.0
1.2.26 LBFD-002031 Support of aperiodic CQI reports

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

Availability
This feature is

eRAN7.0
Summary
Huawei supports extended QoS Class Identifier (extended QCI) (255 QCI including 9
standard QCI defined in 3GPP). Extended QCI can be used as operator defined QCI to
support customized non-GBR service. Extended QCI index can be defined by operator and
need SAE to support it.
Benefits
It can be configurable flexibly by operator and meet multi need of operator who wants to
operate the differentiated service.
Description
This feature supports extended QCI, which means that MME send one extended QCI index in
RAB assignment message. The eNodeB can configure these extended QCI and can be
assigned radio resource differently according to the different QCI number and different
scheduling weight factor.
The extended QCI can be configurable with Gold, Silver, and Bronze, which is the same as
the ARP.
Huawei currently supports extended non-GBR QCI, and the configurable scenario is that
eNodeB get the QCI index firstly, set the ARP and QoS parameter ( PDB, PLER, schedule
weight) related with QCI index.
Enhancement
None
Dependency
 Others
It relates with SAE.
1.2.28 LBFD-002033 SCTP Congestion Control

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

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

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

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

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

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

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

Availability
This feature is
Summary
This feature adaptively selects the frequency selective scheduling mode based on the number
of synchronized UEs and the number of to-be-scheduled UEs in a cell.
Benefits
This feature reduces the interference to UEs, improves the modulation and coding schemes
(MCSs), and therefore increases UE throughput.
Description
Frequency selective fading is inevitable due to the multipath effect in radio channels. Because
frequency selective fading changes relatively slowly for low-mobility UEs, frequency

eRAN7.0
selective fading is considered to be stable within the channel coherence time. The LTE system
adopts single carrier frequency division multiple access (SC-FDMA) in the uplink. In the
system, the system bandwidth is wide and the subband bandwidths for resource allocation can
be narrow. The channel fading effect varies with subbands. During scheduling, the eNodeB
allocates the subbands in good channel quality to UEs, which is called frequency selective
scheduling. Generally, the distributions of frequency selective fading for UEs are scattered,
that is, good-quality subbands are UE-specific. Therefore, all UEs can be scheduled on their
good-quality subbands, thereby increasing network throughput.
When this feature is disabled and the number of synchronized UEs in a cell is less than or
equal to 15, uplink frequency selective scheduling is used. When this feature is disabled and
the number of synchronized UEs in a cell is greater than 15, the eNodeB allocates resources in
order of RB sequence number. In this case, inter-cell interference cannot be avoided and the
UEs experience interference all the time.
When this feature is enabled, the eNodeB adaptively selects the frequency selective
scheduling mode based on the number of synchronized UEs and the number of
to-be-scheduled UEs in a cell. As a result, this feature reduces the interference to UEs and
therefore increases UE throughput.
Enhancement
 In eRAN7.0
eNodeBs select MCSs for slowly moving UEs based on the reported signal to
interference plus noise ratios (SINRs) in subbands during frequency selective scheduling.
Therefore, the frequency selective scheduling gains increase, raising the spectral
efficiency and throughput of the UEs.
Dependency
None
1.2.32 LBFD-060103 Enhanced DL Frequency Selective Scheduling

Availability
This feature is
Summary
Due to the multipath effect, radio signals reaching a receiver by multiple paths have different
phases, amplitudes, and delays. This results in frequency selective fading.
To achieve better system performance, the Enhanced DL Frequency Selective Scheduling
feature is introduced to LTE. This feature chooses sub-bands with higher quality for data
transmission.
Benefits
This feature increases downlink throughput.

eRAN7.0
Description
During downlink frequency selective scheduling, the eNodeB calculates each UE's scheduling
priority on each sub-band based on the sub-band CQIs reported by the UEs. Based on these
priorities, the eNodeB allocates different sub-bands to the most appropriate UEs.
When downlink frequency selective scheduling is enabled, each resource block group (RBG)
is allocated to the most appropriate UE and therefore more UEs are scheduled in each
transmission time interval (TTI). However, this may require more PDCCH resources, make
less resources available to the PDSCH, and decrease downlink throughput.
Compared with earlier versions, eRAN6.0 enhances the PDCCH symbol adaptation function.
It makes a balance between PDCCH symbols and PDSCH symbols and therefore achieves
frequency selective gains in more scenarios.
Enhancement
None
Dependency
None
1.2.33 LBFD-070103 Multi-Band Compatibility Enhancement

Availability
This feature is
Summary
If a cell works at a frequency that belongs to multiple bands, it can be configured as a
multi-band cell.
Benefits
In the case that there are existed different bands in same frequency, UEs support one band can
access a network configured with multiple bands, which can support roaming terminal better.
For example, if a cell is configured with both bands 2 and 25, UEs supporting band 2 or band
25 can access the cell.
Description
According to 3GPP TS 36.331 released before October, 2012, the information about the band
supported by a cell is sent to a UE by using an SIB, and each cell supports only one band. If
the band indicated in the SIB differs from the band supported by the UE, the UE cannot
access the cell.
3GPP TS 36.331, released in October 2012, defines the extended fields for SIBs:
SIB1: contains the multi-band indicator of the serving cell.

eRAN7.0
SIB2: contains additionalSpectrumEmission of different bands.

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

Availability
This feature is

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

Availability
This feature is
Summary
The eNodeB allows the maximum bit rate (MBR) to be greater than the guaranteed bit rate
(GBR).
Benefits
Setting of the MBR to be greater than the GBR allows applications to take advantage of
additional system capacity when it is available, thereby improving resource utilization and
user experience. For details, see 3GPP TS 23.860.

eRAN7.0
Description
The definition of MBR allows the increasing real-time services (such as voice and video
services), whose data rates are elastic, to make use of additional network resources that may
be available. The GBR can be set to the minimum data rate at which the real-time services can
be carried, and the MBR can be set to the maximum data rate at which the optimal user
experience is achieved. When the E-UTRAN is not congested and idle network resources are
available, the real-time services carried on the GBR bearers can reach rates between the GBR
and the MBR.
Enhancement
None.
Dependency
None.
1.2.36 LBFD-070105 IoT-based PUSCH Power Control

Availability
This feature is
Summary
When the network is lightly loaded, uplink interference can be mitigated using uplink
frequency selective scheduling or interference-randomization-based scheduling. However,
when the network is heavily loaded in special scenarios such as a concert or soccer match,
neither uplink frequency selective scheduling nor interference-randomization-based
scheduling can effectively mitigate uplink interference. As a result, performance of cell edge
UEs (CEUs) deteriorates.
IoT-based PUSCH Power Control is introduced to decrease inter-cell uplink interference and
improve performance of CEUs in these scenarios. (IoT is short for interference over thermal.)
Benefits
PUSCH power control based on the exchange of overload indications (OIs) between cells
decreases inter-cell uplink interference and increases uplink throughput of CEUs in special
scenarios.
Description
When a heavily-loaded cell detects strong uplink interference, the cell sends UL Interference
Overload Indication to neighboring cells (or sends the LOAD INFORMATION message
containing UL Interference Overload Indication to inter-eNodeB neighboring cells over X2
interfaces). After receiving UL Interference Overload Indication, the neighboring cells adjust
the PUSCH transmit power of UEs in and near the cell center to decrease uplink interference
on their adjacent cells.

eRAN7.0
In heavily-loaded networks, uplink interference on cells that send UL Interference Overload

Indication decreases, and uplink throughput of CEUs in these cells increases. In the cells that
receive UL Interference Overload Indication, UEs in and near the cell center decrease the
PUSCH transmit power, so uplink throughput of these UEs decreases.
In heavily-loaded networks with strong interference, to better provide LTE services for as
many UEs as possible in special scenarios, uplink coverage of neighboring cells can be
enhanced and user experience of CEUs can be improved at the cost of performance of UEs in
and near the center of a local cell.
Enhancement
None
Dependency
None
1.2.37 LBFD-070106 PDSCH Efficiency Improvement

Availability
This feature is
Summary
In LTE networks, surplus physical downlink shared channel (PDSCH) resources are available
in scenarios where the maximum number of transmitted bits in each transmission time interval
(TTI) is less than the maximum number of bits that the band can transmit or where the traffic
volume to be transmitted is too small.
In large traffic volume scenarios, insufficient physical downlink control channel (PDCCH)
resources result in a limited number of UEs to be scheduled in the downlink and a low
PDSCH resource usage.
This feature increases the PDSCH resource usage in the preceding scenarios, thereby
increasing downlink throughput and improving user experience.
Benefits
This feature enables better utilization of PDSCH resources and improves user experience.
Description
An eNodeB takes the following measures in scenarios where surplus resource blocks (RBs)
are available in LTE networks:
1. When the traffic volume to be scheduled remains unchanged, the eNodeB increases the
number of RBs to be scheduled and lowers the modulation and coding scheme (MCS) to
improve transmission reliability and user experience.

eRAN7.0
2. In large traffic volume scenarios, the eNodeB randomly selects a UE with large-size
packets during downlink scheduling and reserves PDCCH resources for the UE. The
eNodeB allocates PDSCH resources to the UE when scheduling the last UE. In this
manner, the PDSCH resource usage and downlink throughput increase.
Enhancement
None
Dependency
None
1.2.38 LBFD-070107 PDCCH Utilization Improvement

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

eRAN7.0
1.3 Transmission & Security

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

eRAN7.0
Enhancement
None
Dependency
None
1.3.1.2 LBFD-00300102 Chain Topology
Availability
This feature is
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-7 Chain topology
Enhancement
None

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

eRAN7.0
Figure 1-8 Tree topology
Enhancement
None
Dependency
 eNodeB
The UMPT card, which provides E1/T1 interfaces, is required.
1.3.2 LBFD-003002 Basic Qos Management

1.3.2.1 LBFD-00300201 DiffServ QoS Support
Availability
This feature is
Summary
Huawei supports DiffServ (Differentiated Services) to provide QoS guarantee by classifying
and managing different traffic in the network.
Benefits
This feature provides a kind of QoS guarantee mechanism. It is a standard mechanism used by
Mainstream vendors.

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

Data Type QCI Resource Type DSCP
User plane 1 GBR 0x2E
2 0x1A
3 0x22
4 0x1A
5 Non-GBR 0x2E
6 0x12
7 0x12
8 0x0A
9 0
Control plane SCTP 0x2E
0x30
OM MML 0x2E
0x30
FTP 0x0E
IP clock 0x2E
0x30

eRAN7.0
Enhancement
None
Dependency
None
1.3.3 LBFD-003003 VLAN Support (IEEE 802.1p/q)

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

eRAN7.0
1.3.4 LBFD-003004 Compression & Multiplexing over E1/T1

1.3.4.1 LBFD-00300401 IP Header Compression
Availability
This feature is
Summary
IP header compression provides a method to compress IP header information in order to
increase the efficiency of E1/T1 interfaces.
Benefits
IP header compression can save S1/X2 IP transport resource to provide higher transport
efficiency of S1/X2 IP transmission.
Description
This feature focuses on the compression technology in UDP/IP layer.
When UDP/IP/MLPPP/E1/T1 is used for transport, the UDP/IP encapsulation is too large for
packets of small payloads and results in low transport efficiency.
IP header compression is adopted to enhance the transport efficiency. The 28 bytes of UDP/IP
header can be compressed into 4-7 bytes.
Enhancement
None
Dependency
 eNodeB
 Transport network
IP over E1/T1 is used for transport
The peer equipment supported the IP header compression functionality.
 CN
The CN equipment supports the feature.
1.3.4.2 LBFD-00300402 PPP MUX
Availability
This feature is

eRAN7.0

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

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

eRAN7.0
The peer transport equipment shall support ML-PPP/MC-PPP when ML-PPP/MC-PPP is

used to transport.
E1/T1 interfaces are used.
 CN
1.3.5 LBFD-003005 Synchronization

1.3.5.1 LBFD-00300501 Clock Source Switching Manually or Automatically
Availability
This feature is
Summary
This feature enables manual or automatic switching between clock sources.
Benefits
If unexpected events occur in the current clock sources, the system will not be affected.
Description
The eNodeB can work in multiple clock synchronization modes. The system clock source can
be chosen in a convenient and flexible manner. When one clock source fails, the system clock
can be manually or automatically switched to another available one.
1. For phase synchronization, the clock source can be manually or automatically switched.
Following clock source supports manually switching:
− Synchronization with GPS
− Synchronization with the clock over IP (IEEE 1588V2)
− Synchronization with 1PPS + TOD
Following clock resource supports automatically switching:
− Between GPS and IEEE 1588V2
− Between GPS and 1PPS+TOD
2. For frequency synchronization, the clock source can be manually switched. Following
clock source supports manually switching:
− Synchronization with Ethernet(ITU-T G.8261)
− Synchronization with the clock over IP (IEEE 1588V2)
− Synchronization with the clock over IP (Huawei proprietary solution)
− Synchronization with GPS
− Synchronization with the BITS
− Synchronization with E1/T1 interface

eRAN7.0
− Synchronization with 1PPS

In addition to the previous clock sources, the eNodeB can work with the local oscillator.
Enhancement
None
Dependency
None
1.3.5.2 LBFD-00300502 Free-running Mode
Availability
This feature is
Summary
The free-running mode is an alternative mode to the clock sources if all clocks fail.
Benefits
When all clock sources are lost, this feature can keep the eNodeB in normal service for up to
90 days.
Description
When all clock sources are lost, the eNodeB internal clock can work in the free-running mode
to keep the eNodeB running.
The enhanced stratum 3 Oven Controlled Crystal Oscillator (OCXO) with a high accuracy
works as the master clock of the eNodeB. The OCXO can keep the eNodeB in normal service
for up to 90 days.
Enhancement
None
Dependency
None
1.3.5.3 LBFD-00300503 Synchronization with GPS
Availability
This feature is

eRAN7.0

Summary
The eNodeB can work in multiple clock synchronization modes to suit different clock
topologies. Global Positioning System (GPS) can be one of the synchronization sources.
Benefits
This feature provides GPS as one of the synchronization sources. The eNodeB internal clock
can be synchronized with the transport network and no auxiliary clock equipment is needed,
in order to reduce the cost. The synchronized clock is of the required accuracy to meet both
radio frequency and transmission network requirements.
Description
In compliance with 3GPP, the eNodeB clock must have a higher clock precision. The
frequency stability of the 10-MHz master clock of the eNodeB should be lower than ±0.05
ppm.
It is required if a GPS clock is used as the clock source.
The clock signals are processed and synchronized as follows:
The GPS antenna and feeder system receives GPS signals at 1575.42 MHz, and transmits the
signals to the GPS card. The system can simultaneously trace up to eight (normally three or
four) satellites. The GPS card processes the signals and transmits them to the main clock
module.
Enhancement
None
Dependency
None
1.3.5.4 LBFD-00300504 Synchronization with BITS
Availability
This feature is
Summary
topologies. Building Integrated Timing Supply System (BITS) can be one of the
synchronization sources.

eRAN7.0
Benefits
This feature provides BITS as one of the synchronization sources. The eNodeB internal clock
can be synchronized with the transport network and no auxiliary clock equipment is needed,
in order to reduce the cost. The synchronized clock is of the required accuracy to meet both
radio frequency and transmission network requirements.
Description
ppm.
The eNodeB can synchronize its clocks with the 2-MHz clock signal from an external
reference clock. The reference clock can be a BITS or a 2-MHz clock from the transmission
equipment. Through phase locking and frequency dividing, the main clock module converts
the clock signals into various clock signals required by the eNodeB.
Enhancement
None
Dependency
 eNodeB
USCU(Universal Satellite Card and Clock Unit) card is required
1.3.5.5 LBFD-00300505 Synchronization with 1PPS
Availability
This feature is
Summary
topologies. 1PPS+TOD can be one of the synchronization sources.
Benefits
This feature provides 1PPS+TOD as one of the synchronization sources. The eNodeB
internal clock can be synchronized with the transport network and no auxiliary clock
equipment is needed, in order to reduce the cost. The synchronized clock is of the required
accuracy to meet both radio frequency and transmission network requirements.
Description
ppm.

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

eRAN7.0
1.3.6 LBFD-003006 IPv4/IPv6 Dual Stack

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

eRAN7.0
1.4 Operation & Maintenance

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

Availability
This feature is

eRAN7.0

Summary
The Huawei iManager U2000 provides FCPSS management functions for operators at the
management center.
Benefits
All LTE network elements can be managed at the management center, which effectively
reduces OPEX.
Description
The Huawei iManager U2000 provides all necessary fault management, configuration
management, performance management, security management and software management
(FCPSS defined by 3GPP) management functions to help operators to manage their network
elements on a sub-network.
FCPSS involves the following contents:
 Centralized fault management
 Centralized configuration management
 Centralized performance management
 Centralized security management
 Centralized software management
Enhancement
None
Dependency
 OSS
The Huawei iManager U2000 is required.
1.4.3 LBFD-004003 Security Socket Layer

Availability
This feature is

eRAN7.0
Summary
Security Socket Layer (SSL) is a layer between the TCP layer and the O&M application layer.
SSL provides the secured data transfer function between the eNodeB and the Huawei
iManager U2000
Benefits
All remote operation and maintenance tasks are performed through encrypted protocols.
Description
Security Socket Layer (SSL) is a layer between the TCP layer and the O&M application layer.
SSL provides the secured data transfer function between the eNodeB and the Huawei
iManager U2000. All O&M application data transferred through SSL is encrypted. FTP over
SSL is also supported.
Enhancement
 In eRAN3.0
This feature supports TLSv1.2. Transport Layer Security (TLS) and its
predecessor-Secure Sockets Layer (SSL), are cryptographic protocols that provide
communications security between eNodeBs and Huawei iManager U2000 above
Transport Layer. TLSv1.2 is the latest version of TLS series. And TLS1.2 supports
stronger authentication algorithm SHA256.
Dependency
 OSS
1.4.4 LBFD-004004 Software Version Upgrade Management

Availability
This feature is
Summary
This feature provides efficient and correct installation and upgrade of the software and version
management functions.
Benefits
The eNodeB software management enables efficient and correct software installation, upgrade,
and version management.

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

Availability
This feature is

eRAN7.0

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

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

eRAN7.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 disruption.
 Fault detection
Fault detection includes physical layer and link layer environment monitoring and KPI
alarm monitoring and other fault detection. A small portion of faults may have a negative
impact on the traffic if self-testing, such as RAM self-testing and transport link loopback
testing, is performed. Among those faults, some are detected automatically in the board
startup phase, and some can be manually triggered by executing fault testing commands.
Fault detection methods are carefully designed to avoid false alarms and intermittent alarms.
 Fault handling
The eNodeB will perform fault isolation and fault automatic recovery to minimize the impacts
on service.
 Fault correlation
Fault management supports a run-time fault correlation handling mechanism and makes it
possible to notify operators of the most important alarms (the root cause and impacts on the
traffic) instead of all the related ones when a fault occurs. The number of alarms can be
greatly reduced in this way, which makes it easier to locate and solve the network problems.
This mechanism is predefined and embedded in the network elements, and operators can
customize more alarm correlation handling rules on the Huawei iManager U2000.
 Fault reporting
Faults are reported to users in the form of alarms. Because of the alarm correlation function,
the information of the correlation between alarms is contained in alarms. If any correlative
alarms occur, operators can get the root alarm by simply right-clicking the service-affecting
faults.
The operators can browse real-time alarm information, query history alarm information, and
store alarm information. The online help provides detailed troubleshooting methods for each
type of alarm.
Enhancement
 In eRAN2.0
Huawei LTE eRAN2.0 supports KPI alarm detection.
 In eRAN2.2
When RRU power supply is AC, RRU could detect AC power down and provide
warning signal to the eNodeB.
Dependency
 OSS

eRAN7.0
Fault management can be implemented on the Huawei iManager U2000 or the eNodeB
LMT.
1.4.7 LBFD-004007 Configuration Management

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

eRAN7.0
GUI wizards are added to help users with capacity expansion and migration jobs.
Dependency
 OSS
Configuration management can be implemented on the Huawei iManager U2000 or the
LMT.
1.4.8 LBFD-004008 Performance Management

Availability
This feature is
Summary
This feature provides various performance measurement (PM) counters to monitor the
performance of the eNodeB. The real-time KPI monitoring is an enhanced feature to help user
locate performance problems quickly.
Benefits
The performance management function provides an efficient way to monitor the network
performance so that network troubleshooting and optimization can be implemented, and the
real-time KPI monitoring is a more efficient feature.
Description
Performance measurement gives the detailed information of the network. Such information
facilitates troubleshooting and network optimization.
 PM administration
The performance measurement administration provides operators with a means to manage the
available measurements.
For the new commissioning network elements (eNodeB), the predefined performance
measurements will start after initial startup phase. The performance measurements can be
suspended and resumed manually.
The network elements (eNodeB) provide machine-machine interfaces, allowing the Huawei
iManager U2000 to collect the necessary statistics and to set the related parameters including
statistical counters and the measurement period.
The statistics are obtained by the Huawei iManager U2000 in binary format in every
measurement period.
Each eNodeB can store a maximum of 288 files as backups that are useful when data transfer
fails, which makes it possible for the Huawei iManager U2000 to recollect the lost data later.
− If the measurement period is 15 minutes, an eNodeB can store measurement results sampled
in a maximum period of 72 hours.

eRAN7.0
− If the measurement period is 60 minutes, an eNodeB can store measurement results sampled
in a maximum period of 288 hours.
 PM counters
The PM counters include key counters and other counters. The key counters are used to
generate the key performance indicators (KPIs) of the network, which are defined on the
Huawei iManager U2000, and these counters are predefined and initialized as soon as the
eNodeB starts. The KPIs, related original counters and formulas can be added, modified and
deleted on the Huawei iManager U2000. Other counters reflecting the other aspects of
network performance can be started when needed.
 Real-time KPI monitoring
This feature provides the monitoring of KPIs and graphical representation of network
performance. Therefore, it is convenient for troubleshooting, drive tests and network
optimization. The real-time KPI measurement period of each monitoring task can vary, but
must be a multiple of 30 seconds within the range of 30 seconds to 15 minutes. By default,
eNodeBs of eRAN2.2 and later releases use a monitoring period of 1 minute.
Enhancement
None
Dependency
 OSS
Performance management is implemented on the Huawei iManager U2000 or LMT.
1.4.9 LBFD-004009 Real-time Monitoring of System Running

Information
Availability
This feature is
Summary
This feature provides the function of monitoring the running information of the equipment,
RF system, cells, subscribers and transport links.
Benefits
This feature is convenient for troubleshooting, drive tests and network optimization.
Description
This feature provides real-time monitoring and graphical representation of system operation
information and quality. It is a test facility which helps operators to diagnose faults through
precise information about cells, subscribers and links..

eRAN7.0
The following monitoring items are supported:

 Equipment running information monitoring: involving clock source quality
 Subscriber-level running information monitoring: involving SIR measurement and UE
TX power
 Cell-level running information monitoring: involving the number of cell users,
throughput, and resource block usage
 Transport link running information monitoring: involving SCTP links and IP paths
 RF monitoring: involving RF performance and RF interference detection
Enhancement
None
Dependency
None
1.4.10 LBFD-004010 Security Management

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

eRAN7.0
Security alarms are added.
Dependency
 OSS
1.4.11 LBFD-004011 Optimized eNodeB Commissioning Solution

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

eRAN7.0
Dependency
 OSS
U2000 or an USB for USB commissioning is required.
1.4.12 LBFD-004012 Environment Monitoring

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

Availability
This feature is

eRAN7.0
Summary
The Huawei iManager U2000 retrieves inventory information automatically from the eNodeB
after commissioning and synchronize the information on the eNodeB every day.
Benefits
With this function, operators can obtain the timely and accurate inventory data of the existing
network for decision making.
Description
Inventory management helps operators to manage the asset information of the network. With
this function, the assets can be queried and managed on the Huawei iManager U2000.
The objects which are managed by this function include physical objects (such as racks,
frames, slots, boards, ports, and fans) and logical objects (such as software and patches).
When requested from the Huawei iManager U2000, an asset information file in .xml format is
generated and is sent to the Huawei iManager U2000. The Huawei iManager U2000 stores the
uploaded information in the network inventory database.
The Huawei iManager U2000 retrieves inventory information automatically from the eNodeB
after commissioning and synchronize the information on the eNodeB every day.
Enhancement
 In eRAN2.0
The Huawei iManager U2000 retrieves inventory information automatically from the
eNodeB after commissioning.
Inventory change notification function has been added to eNodeB. When inventory
changes in eNodeB, a notification will be sent from eNodeB to U2000(Micro eNodeB
will not send this notification), so that the inventory information could be synchronized
quickly between U2000 and eNodeB.
Dependency
 OSS
1.4.14 LBFD-004014 License Management

Availability
This feature is
Summary
This feature involves the eNodeB license control.

eRAN7.0
Benefits
With this feature, the operators can purchase the license based on the network development,
thus reducing the initial cost of the network deployment.
Description
The license file is used to determine whether the optional features are available and how many
optional features are available.
The license file can be downloaded remotely to the eNodeB. The operators can manage and
query the contents in the license file through the LMT or the U2000 client.
The license file is stored in the eNodeB.
Figure 1-10 License file management
New or upgraded license files can be ordered from Huawei.
Enhancement
None
Dependency
None
1.4.15 LBFD-004015 License Control for Urgency

Availability
This feature is
Summary
With this feature, the license limitation is withdrawn in emergencies, so the operator can
handle the sudden increase of network capacity.

eRAN7.0
Benefits
This feature helps operator to face the situations where there is an unusual increase of traffic
(p N Y …) by b g mp y RAN g
permanent over-dimensioning and thus adapting the capacity costs to the real usage.
Description
The license limitation is withdrawn through manual execution of the MML commands on the
LMT or U2000. Thus, the equipment can be used effectively to optimum capacity.
For each R version, the operation personnel have three chances to withdraw the license
limitation through the MML commands. The operation takes effect immediately after the
commands are executed. The validity period is seven days. When the three chances are used
up, a new chance can be obtained only through the software upgrade.
Enhancement
None
Dependency
None
1.4.16 LBFD-070104 Site Transmission Equipment Fault Detection

Availability
This feature is
 not applicable to Macro
Summary
A small-cell base station and the transmission equipment in direct connection can be bound
together by means of NE self-discovery reports. Transmission Equipment Fault Detection
enables users to query information on the iManager U2000 MBB about the transmission
equipment that is bound to the small-cell base station, including equipment type and MAC
address. This facilitates troubleshooting if the small-cell base station goes out of service or
becomes disconnected. Based on the information queried on the iManager U2000 MBB, users
can easily detect and locate faults on the transmission equipment by using the special network
management system.
Benefits
This feature facilitates fault location. When a small-cell base station goes out of service or
becomes disconnected, this feature enables fault detection on the last-mile transmission
equipment, thereby improving troubleshooting efficiency.
Description
 Process for a small-cell base station to obtain the peer equipment information

eRAN7.0
Link Layer Discovery Protocol (LLDP) is a layer 2 protocol and is independent of vendors.
Network equipment uses this protocol to claim the equipment identity and performance in the
local subnet. Layer 2 Discovery provides the following information:
- Network equipment and its ports
- Network equipment that is connected on the ports
- Topologies between a small-cell base station and the transmission equipment in direct
connection
The following figure shows the process for a small-cell base station to discover a piece of
peer equipment.
Users enable LLDP between Small cell and Peer network element. The procedure for
discovering the topology between Small cell and Peer NE over LLDP is as follows:
1. Small cell sends Peer NE the LLDP packets containing local information (including
system name, description, port number, and MAC address).
2. Peer NE analyzes the LLDP packets and stores the analysis result into its database. This
analysis result is used as neighbor information that will be accessed when the iManager
U2000 MBB obtains network topology information.
3. Similarly, Peer NE sends Small cell the LLDP packets containing local information.
Small cell analyzes the LLDP packets and stores the analysis result into its database.
4. The iManager U2000 MBB queries LLDP-related information about Small cell to obtain
local information and neighbor information about Small cell and Peer NE. Finally, the
iManager U2000 MBB learns about the topology of the entire network..
 Process for users to query information about the peer equipment of a small-cell base
station
When the transmission equipment is enabled with the LLDP function, users can select a
small-cell base station and activate LLDP and query peer NE information for the small-cell
base station. When users manually query peer NE information, the small-cell base station and
peer NE information is displayed in a table. The table contains the fields Local NE, Local
Port, Peer NE Type, Peer Port, Peer MAC Address, and Peer OM IP. Peer NE Type and
Peer MAC Address are mandatory in the table.

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

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

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

eRAN7.0
Dependency
None

eRAN7.0
eRAN7.0 LTE FDD Basic Feature Description 2 Acronyms and Abbreviations
2 Acronyms and Abbreviations
Table 2-1 Acronyms and Abbreviations
3GPP Third Generation Partnership Project
ABS Almost-blank subframe
ACK acknowledgment
ACL Access Control List
AES Advanced Encryption Standard
AFC Automatic Frequency Control
AH Authentication Header
AMBR Aggregate Maximum Bit Rate
AMC Adaptive Modulation and Coding
AMR Adaptive Multi-Rate
ANR Automatic Neighboring Relation
ARP Allocation/Retention Priority
ARQ Automatic Repeat Request
BCH Broadcast Channel
BCCH Broadcast Control Channel
BITS Building Integrated Timing Supply System
BLER Block Error Rate
CA Carrier aggregation
C/I Carrier-to-Interference Power Ratio
CCCH Common Control Channel

eRAN7.0
CDMA Code Division Multiple Access
CEU Cell Edge Users
CGI Cell Global Identification
CP Cyclic Prefix
CPICH Common Pilot Channel
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
CRS Cell-specific reference signal
CSI-RS Channel state information reference signal
DCCH Dedicated Control Channel
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Services
DL-SCH Downlink Shared Channel
DRB Data Radio Bearer
DRX Discontinuous Reception
DSCP DiffServ Code Point
DTCH Dedicated Traffic Channel
ECM EPS Control Management
eCSFB Enhanced CS Fallback
EDF Early Deadline First
EF Expedited Forwarding
eHRPD Evolved high rate packet data
eICIC Enhanced Inter-cell Interference

Coordination
eMBMS evolved Multimedia Broadcast Multimedia

System
EMM EPS Mobility Management
EMS Element Management System
eNodeB evolved NodeB
EPC Evolved Packet Core
EPS Evolved Packet System

eRAN7.0
ESP Encapsulation Security Payload
ETWS Earthquake and Tsunami Warning System
E-UTRA Evolved –Universal Terrestrial Radio

Access
FCPSS Fault, Configuration, Performance, Security

and Software Managements
FDD Frequency Division Duplex
FEC Forward Error Correction
FTP File Transfer Protocol
GBR Guaranteed Bit Rate
GERAN GSM/EDGE Radio Access Network
GPS Global Positioning System
HARQ Hybrid Automatic Repeat Request
HII High Interference Indicator
HMAC Hash Message Authentication Code
HMAC_MD5 HMAC Message Digest 5
HMAC_SHA HMAC Secure Hash Algorithm
HO Handover
HRPD High Rate Packet Data
ICIC Inter-cell Interference Coordination
IKEV Internet Key Exchange Version
IMS IP Multimedia Service
IP PM IP Performance Monitoring
IPsec IP Security
IRC Interference Rejection Combining
KPI Key Performance Indicator

eRAN7.0
CME Configuration Management Express
LMT Local Maintenance Terminal
MAC Medium Admission Control
MIB Master Information Block
MCH Multicast Channel
MCCH Multicast Control Channel
MCS Modulation and Coding Scheme
MIMO Multiple Input Multiple Output
min_GBR Minimum Guaranteed Bit Rate
MME Mobility Management Entity
MML Man-Machine Language
MOS Mean Opinion Score
MRC Maximum-Ratio Combining
MTCH Multicast Traffic Channel
MU-MIMO Multiple User-MIMO
NACC Network Assisted Cell Changed
NACK Non acknowledgment
NAS Non-Access Stratum
NRT Neighboring Relation Table
OCXO Oven Controlled Crystal Oscillator
OFDM Orthogonal Frequency Division

Multiplexing
OFDMA Orthogonal Frequency Division

Multiplexing Access
OI Overload Indicator
OMC Operation and Maintenance Center
OOK On-Off-Keying
PBCH Physical Broadcast Channel

eRAN7.0
PCCH Paging Control Channel
PCFICH Physical Control Format Indicator Channel
PCH Paging Channel
PCI Physical Cell Identity
PDB Packet Delay Budget
PDCCH Physical Downlink Control Channel
PDCP Packet Data Convergence Protocol
PDH Plesiochronous Digital Hierarchy
PDSCH Physical Downlink Shared Channel
PF Proportional Fair
PHB Per-Hop Behavior
PHICH Physical Hybrid ARQ Indicator Channel
PM Performance Measurement
PLMN Public Land Mobile Network
PMCH Physical Multicast Channel
PRACH Physical Random Access Channel
PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Shared Channel
QAM Quadrature Amplitude Modulation
QCI QoS Class Identifier
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RA Random Access
RACH Random Access Channel
RAM Random Access Memory
RAT Radio Access Technology
RB Resource Block
RCU Radio Control Unit
RET Remote Electrical Tilt

eRAN7.0
RF Radio Frequency
RLC Radio Link Control
RRC Radio Resource Control
RRM Radio Resource Management
RRU Remote Radio Unit
RS Reference Signal
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
RSSI Received Signal Strength Indicator
RTT Round Trip Time
RV Redundancy Version
Rx Receive
S1 interface between EPC and E-UTRAN
SBT Smart Bias Tee
SC-FDMA Single Carrier-Frequency Division Multiple

Access
SCTP Stream Control Transmission Protocol
SDH Synchronous Digital Hierarchy
SFBC Space Frequency Block Coding
SFP Small Form – factor Pluggable
SGW Serving Gateway
SIB System Information Block
SID Silence Indicator
SINR Signal to Interference plus Noise Ratio
SRB Signaling Radio Bearer
SRS Sounding Reference Signal
SSL Security Socket Layer
STBC Space Time Block Coding
STMA Smart TMA

eRAN7.0
TAC Transport Admission Control
TCP Transmission Control Protocol
TDD Time Division Duplex
TMA Tower Mounted Amplifier
TMF Traced Message Files
ToS Type of Service
TTI Transmission Time Interval
Tx Transmission
UE User Equipment
UL-SCH Uplink Shared Channel
USB Universal Serial Bus
U2000 Huawei OMC
VLAN Virtual Local Area Network
VoIP Voice over IP
WRR Weighted Round Robin
X2 interface among eNodeBs


eRAN7 0 LTE FDD Basic Feature Description 01 20140915 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

eRAN7 0 LTE FDD Basic Feature Description 01 20140915 PDF

Uploaded by

Copyright:

Available Formats

eRAN7.

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

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

Issue 01 (2014-05-04) Huawei Proprietary and Confidential ii

1.2.19.3 LBFD-00201803 Cell Selection and Re-selection .............................................................................................. 30

Issue 01 (2014-05-04) Huawei Proprietary and Confidential iii

1.3.5.1 LBFD-00300501 Clock Source Switching Manually or Automatically ............................................................... 66

2 Acronyms and Abbreviations ................................................................................................... 91

Issue 01 (2014-05-04) Huawei Proprietary and Confidential iv

Figure 1-1 3*10M 2T2R ..................................................................................................................................... 35

Figure 1-3 Overview of Earthquake and Tsunami Warning System ................................................................. 43

Figure 1-4 RRU channel cross connection under MIMO .................................................................................... 47

Figure 1-6 Star topology ...................................................................................................................................... 57

Figure 1-7 Chain topology .................................................................................................................................. 58

Figure 1-8 Tree topology ..................................................................................................................................... 60

Figure 1-9 ML-PPP/MC-PPP .............................................................................................................................. 65

Figure 1-10 License file management ................................................................................................................. 85

Issue 01 (2014-05-04) Huawei Proprietary and Confidential v

Table 1-1 Preamble formats and cell access radius.............................................................................................. 19

Table 1-5 Relationship between QCI and DSCP ................................................................................................. 61

Issue 01 (2014-05-04) Huawei Proprietary and Confidential vi

About This Chapter

1.1 Standards Compliance

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 1

1.1.2 LBFD-001007 3GPP R9 Specifications

1.1.3 LBFD-001008 3GPP R10 Specifications

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 2

 applicable to Micro from eRAN3.0

1.1.4 LBFD-001002 FDD mode

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 3

1.1.5 LBFD-001003 Scalable Bandwidth

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 4

1.1.6 LBFD-001004 CP length

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 5

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

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 6

1.1.8 LBFD-001006 AMC

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 7

1.2 RAN Architecture & Features

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 8

1.2.2 LBFD-002002 Transport Channel Management

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 9

1.2.3 LBFD-002003 Physical Channel Management

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 10

1.2.4 LBFD-002004 Integrity Protection

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 11

1.2.5 LBFD-002005 DL Asynchronous HARQ

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 12

1.2.6 LBFD-002006 UL Synchronous HARQ

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 13

1.2.7 LBFD-002007 RRC Connection Management

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 14

 RRC connection reconfiguration: This procedure is performed to modify an RRC

1.2.8 LBFD-002008 Radio Bearer Management

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 15

1.2.9 LBFD-002009 Broadcast of system information

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 16

 SystemInformationBlockType5 contains the information about other E-UTRA

1.2.10 LBFD-002010 Random Access Procedure

Issue 01 (2014-05-04) Huawei Proprietary and Confidential 17