ELTE2.3 DBS3900 LTE TDD Basic Feature Description

eLTE2.
3 DBS3900 LTE TDD
Basic Feature Description
Issue
Draft
Date
2014-02-1029
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. 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
Draft (2014-02-10)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
eLTE2.3 DBS3900 LTE TDD

About This Document
About This Document

Change History
Issue
Date
Author
Description
Draft
2014-02-10
Ouyangfan/0
0149383
This draft is based on eLTE2.2 Basic Feature

Description Draft
Add new features:
TDLBFD-070111 Multi-Cell Interference
Randomizing
Draft (2014-02-10)

ii

Contents
Contents
About This Document .................................................................................................................... ii
1 Standards Compliance ................................................................................................................. 1
1.1 TDLBFD-001001 3GPP R8 Specifications ...................................................................................................... 1
1.2 TDLBFD-001008 3GPP R9 Specifications ...................................................................................................... 2
1.3 TDLBFD-001009 3GPP R10 Specifications .................................................................................................... 2
1.4 TDLBFD-001002 TDD mode .......................................................................................................................... 3
1.5 TDLBFD-001003 Scalable Bandwidth ............................................................................................................ 3
1.6 TDLBFD-001004 CP length ............................................................................................................................ 5
1.6.1 TDLBFD-00100401 Normal CP ............................................................................................................. 5
1.7 TDLBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM ................................................ 6
1.8 TDLBFD-001006 AMC ................................................................................................................................... 7
1.9 TDLBFD-001007 Basic uplink-downlink subframe configuration .................................................................. 8
1.9.1 TDLBFD-00100701 uplink-downlink subframe configuration type1&2 ............................................... 8
1.9.2 TDLBFD-00100702 uplink-downlink special subframe configuration type 7 ....................................... 9
2 RAN Architecture & Features ..................................................................................................... 1

2.1 TDLBFD-002001 Logical Channel Management ............................................................................................ 1
2.2 TDLBFD-002002 Transport Channel Management ......................................................................................... 2
2.3 TDLBFD-002003 Physical Channel Management ........................................................................................... 3
2.4 TDLBFD-002004 Integrity Protection ............................................................................................................. 4
2.5 TDLBFD-002005 DL Asynchronous HARQ ................................................................................................... 4
2.6 TDLBFD-002006 UL Synchronous HARQ ..................................................................................................... 6
2.7 TDLBFD-002007 RRC Connection Management ........................................................................................... 7
2.8 TDLBFD-002008 Radio Bearer Management ................................................................................................. 8
2.9 TDLBFD-002009 Broadcast of System Information ....................................................................................... 9
2.10 TDLBFD-002010 Random Access Procedure ............................................................................................. 10
2.11 TDLBFD-002011 Paging ............................................................................................................................. 11
2.12 TDLBFD-002012 Cell Access Radius up to 15km ...................................................................................... 12
2.13 TDLBFD-002023 Admission Control .......................................................................................................... 13
2.14 TDLBFD-002024 Congestion Control ......................................................................................................... 13
2.15 TDLBFD-002025 Basic Scheduling ............................................................................................................ 14
2.16 TDLBFD-002026 Uplink Power Control ..................................................................................................... 15
Draft (2014-02-10)

iii

Contents
2.17 TDLBFD-002016 Dynamic Downlink Power Allocation ............................................................................ 17

2.18 TDLBFD-002018 Mobility Management .................................................................................................... 18
2.18.1 TDLBFD-00201801 Coverage Based Intra-frequency Handover ....................................................... 18
2.18.2 TDLBFD-00201802 Coverage Based Inter-frequency Handover ....................................................... 19
2.18.3 TDLBFD-00201803 Cell Selection and Re-selection ......................................................................... 21
2.18.4 TDLBFD-00201804 Distance Based Inter-frequency Handover ........................................................ 22
2.18.5 TDLBFD-00201805 Service Based Inter-frequency Handover .......................................................... 22
2.18.6 TDLBFD-00201806 Multi-Band Compatibility Enhancement ........................................................... 23
2.19 TDLBFD-070111 Multi-Cell Interference Randomizing ............................................................................. 24
2.20 TDLBFD-002020 Antenna Configuration.................................................................................................... 25
2.20.1 TDLBFD-00202001 UL 2-Antenna Receive Diversity ...................................................................... 25
2.21 TDLBFD-002021 Reliability ....................................................................................................................... 26
2.21.1 TDLBFD-00202102 Cell Rebuild between Baseband Processing Units ............................................ 26
2.21.2 TDLBFD-00202103 SCTP Multi-homing .......................................................................................... 27
2.21.3 TDLBFD-00202104 Intra-baseband Card Resource Pool(user level/cell level) ................................. 28
2.22 TDLBFD-002027 Support of UE Category 1 .............................................................................................. 29
2.23 TDLBFD-002031 Support of aperiodic CQI reports.................................................................................... 31
2.24 TDLBFD-002032 Extended-QCI ................................................................................................................. 32
2.25 TDLBFD-002035 Multi Carrier ................................................................................................................... 32
3 Transport ......................................................................................................................................... 1
3.1 TDLBFD-003001 Transmission Networking ................................................................................................... 1
3.1.1 TDLBFD-00300101 Star Topology ........................................................................................................ 1
3.1.2 TDLBFD-00300102 Chain Topology ..................................................................................................... 2
3.1.3 TDLBFD-00300103 Tree Topology ........................................................................................................ 3
3.2 TDLBFD-003006 IPv4/IPv6 Dual Stack ......................................................................................................... 4
4 Transport QoS ................................................................................................................................ 1

4.1 TDLBFD-003002 Basic QoS Management ..................................................................................................... 1
4.1.1 TDLBFD-00300201 DiffServ QoS Support ........................................................................................... 1
4.2 TDLBFD-003003 VLAN Support (IEEE 802.1p/q) ........................................................................................ 2
5 Transport Synchronization ......................................................................................................... 1

5.1 TDLBFD-003005 Synchronization .................................................................................................................. 1
5.1.1 TDLBFD-00300501 Clock Source Switching Manually or Automatically ............................................ 1
5.1.2 TDLBFD-00300502 Free-running Mode ................................................................................................ 2
5.1.3 TDLBFD-00300503 Synchronization with GPS .................................................................................... 2
5.1.4 TDLBFD-00300505 Synchronization with 1PPS+TOD ......................................................................... 3
6 Operation and Maintenance ....................................................................................................... 1

6.1 TDLBFD-004001 Local Maintenance on the LMT ......................................................................................... 1
6.2 TDLBFD-004002 Centralized M2000 Management........................................................................................ 2
6.3 TDLBFD-004003 Security Socket Layer ......................................................................................................... 2
6.4 TDLBFD-004004 Software Version Upgrade Management ............................................................................ 3
Draft (2014-02-10)
iv

Contents
6.5 TDLBFD-004005 Hot Patch Management ...................................................................................................... 4

6.6 TDLBFD-004006 Fault Management .............................................................................................................. 5
6.7 TDLBFD-004007 Configuration Management ................................................................................................ 6
6.8 TDLBFD-004008 Performance Management .................................................................................................. 7
6.9 TDLBFD-004009 Real-time Monitoring of System Running Information ...................................................... 8
6.10 TDLBFD-004010 Security Management ....................................................................................................... 9
6.11 TDLBFD-004011 Optimized eNodeB Commissioning Solution ................................................................. 10
6.12 TDLBFD-004012 Environment Monitoring ................................................................................................ 11
6.13 TDLBFD-004013 Inventory Management ................................................................................................... 12
6.14 TDLBFD-004014 License Management ...................................................................................................... 12
6.15 TDLBFD-004015 License Control for Urgency .......................................................................................... 13
Draft (2014-02-10)


1 Standards Compliance
Standards Compliance
1.1 TDLBFD-001001 3GPP R8 Specifications

Availability
This feature was introduced in LTE TDD eRAN2.0.
Summary
Huawei LTE TDD eRAN2.0 is based on 3GPP Release 8 specifications (2009-03).
Benefits
In complying with 3GPP Release 8 specifications (2009-03), Huawei LTE TDD eRAN2.0
provides users with higher performance services to improve operator competitiveness.
Description
Huawei LTE TDD eRAN2.0 is compliant with 3GPP Release 8 specifications (2009-03).
Huawei is an active participant in and contributor to 3GPP specification development. This
high-level involvement improves Huawei product development. LTE TDD eRAN2.0 was
developed based on 3GPP Release 8 specifications (2009-03).
Enhancement
None
Dependencies
None
Draft (2014-02-10)



Availability
Summary
Huawei LTE TDD eNodeB is based on 3GPP Release 9 specifications (2010-09).
Benefits
Description
Huawei LTE TDD eNodeB is compliant with 3GPP Release 9 specifications (2010-09).
high-level involvement enables Huawei to closely follow evolving 3GPP specifications during
Huawei product improvement. LTE TDD eRAN2.1 was developed based on 3GPP Release 9
specifications (2010-09).
Enhancement
None
Dependency
None

Availability
Summary
Benefits
Description
Draft (2014-02-10)



high-level involvement enables Huawei to closely follow evolving 3GPP specifications during
Huawei product improvement. LTE TDD eRAN3.0 was developed based on 3GPP Release 10
specifications (2011-03).
Enhancement
None
Dependencies
None
1.4 TDLBFD-001002 TDD mode

Availability
Summary
Huawei LTE TDD supports the time division duplex (TDD) mode.
Benefits
The 3GPP specifications define frequency division duplex (FDD) and time division duplex
(TDD) modes. In the uplink and downlink, FDD mode uses different frequency bands, whereas
TDD mode uses the same frequency band.
Description
In TDD mode, the same frequency band is used for both uplink and downlink.
Enhancement
None
Dependencies
The related network elements (NEs) must support TDD mode.
1.5 TDLBFD-001003 Scalable Bandwidth

Availability
Draft (2014-02-10)


Summary
Huawei eNodeBs support scalable channel bandwidths, including 5 MHz, 10 MHz, 15 MHz,
and 20 MHz.
Benefits
Larger bandwidth produces higher throughput and better user experience.
Flexible bandwidth configuration improves the frequency band utilization.
Description
In LTE TDD eRAN1.0, eNodeBs support 10 MHz and 15 MHz bandwidths. Bandwidths can be
configured using software.
Enhancement
In LTE TDD eRAN3.0, eNodeBs support the 5 MHz bandwidth with some limitations.
In LTE TDD eRAN6.1, eNodeBs support the 15 MHz bandwidth.
Dependencies
Only the RRU3232, RRU3252, and RRU3256 support the 5 MHz bandwidth.
The LBBPc supports the 5 MHz bandwidth only in 2T2R mode.
The LBBPd2 supports the 5 MHz bandwidth in 2T2R or 4T4R mode.
UEs must support the same bandwidth as the eNodeB does.
If the eNodeB bandwidth is 5 MHz, the following features cannot work:
Draft (2014-02-10)
TDLOFD-001049 Single Streaming Beamforming
TDLOFD-001061 Dual Streaming Beamforming
TDLOFD-001077 MU-Beamforming
TDLOFD-001008 Ultra High Speed Mobility
TDLOFD-001075 SFN
TDLOFD-002008 Adaptive SFN/SDMA
TDLOFD-001098 Inter-BBP SFN
TDLOFD-001080 Inter-BBU SFN
TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
TDLOFD-001005 UL 4-Antenna Receive Diversity (with LBBPc board)
TDLOFD-001062 UL 8-Antenna Receive Diversity (with LBBPd board)
TDLOFD-001031 Extended CP
TDLOFD-001036 RAN Sharing with Common Carrier
TDLOFD-001037 RAN Sharing with Dedicated Carrier
TDLOFD-001066 Intra-eNodeB UL CoMP
TDLOFD-001039 RF Channel Intelligent Shutdown


Only RRU3232, RRU3251, RRU3252, and RRU3256 support the 15 MHz bandwidth.
Only the LBBPd2 supports the 15 MHz bandwidth in 2T2R or 4T4R mode.
Only the DBS3900 supports the 15 MHz bandwidth.
If the eNodeB bandwidth is 15 MHz, the following features cannot work:
TDLOFD-001062 UL 8-Antenna Receive Diversity
TDLOFD-001008 Ultra High Speed Mobility
TDLOFD-001076 CPRI Compression
TDLOFD-001075 SFN
TDLOFD-002008 Adaptive SFN/SDMA
TDLAOFD-001001 Carrier Aggregation Introduction Package (Two Component

Carriers)
TDLAOFD-001002 Carrier Aggregation to a Total of 40 MHz Bandwidth
TDLAOFD-00100202 Support of UE Category 6
TDLAOFD-001004 Multi-SA Carrier Aggregation for Downlink 2CC
TDLAOFD-002001 Static TDM eICIC
In addition, multi-carrier networks only support the following bandwidth combinations:
15 MHz and 15 MHz
10 MHz and 15 MHz
15 MHz and 20 MHz
Micro eNodeBs do not support the bandwidth of 5 MHz or 15 MHz.
1.6 TDLBFD-001004 CP length

1.6.1 TDLBFD-00100401 Normal CP
Availability
Summary
In an OFDM symbol, the cyclic prefix (CP) is a time-domain replication of the end of the
symbol and is appended to the beginning of the symbol. It provides the guard interval between
Draft (2014-02-10)


OFDM symbols to decrease inter-symbol interference due to multipath delay and

synchronization error.
Benefits
The CP decreases inter-symbol interference due to multipath delay and synchronization error.
Description
There are two CP lengths defined in 3GPP specifications: normal CP and extended CP.
In the case of 15 kHz subcarrier spacing, the normal CP corresponds to seven OFDM symbols
per slot in the downlink and seven SC-FDMA symbols per slot in the uplink. The normal CP
length (time) is calculated as follows:
In the downlink
Normal CP: TCP = 160 x Ts (OFDM symbol #0), TCP = 144 x Ts (OFDM symbol #1 to #6)
In the uplink
Normal CP: TCP = 160 x Ts (SC-FDMA symbol #0), TCP = 144 x Ts (SC-FDMA symbol #1
to #6)
Where Ts = 1/(2048 x f), f = 15 kHz
Enhancement
None
Dependencies
None
1.7 TDLBFD-001005 Modulation: DL/UL QPSK, DL/UL

16QAM, DL 64QAM
Availability
Summary
When this feature is enabled, UEs and eNodeBs support multiple modulation schemes.
Benefits
This feature provides multiple modulation scheme choices based on channel condition.
High-order modulation schemes, such as DL 64QAM, can be used under excellent channel
conditions to achieve high data rates, which improves system throughput and spectral
efficiency.
Draft (2014-02-10)


Description
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 a maximum of two information bits modulated per symbol due to four
different neighboring alternatives.
16QAM allows a maximum of four information bits modulated per symbol due to 16
64QAM allows a maximum of six information bits modulated per symbol due to 64
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 match call quality. When a UE has an excellent
radio environment, it can use a high-order QAM modulation (such as 16QAM) scheme for
uplink transmission to achieve high bit rates.
Enhancement
None
Dependencies
UEs must support the same modulation scheme as the eNodeB.
1.8 TDLBFD-001006 AMC

Availability
Summary
The adaptive modulation and coding (AMC) function allows an eNodeB to select the optimal
modulation and coding scheme (MCS) according to the channel condition. This improves the
spectral efficiency when the system resource and transmit power are fixed. Throughput can
therefore be maximized and quality of service (QoS) requirements can be met.
Benefits
The AMC provides the following benefits:
Draft (2014-02-10)


Maximizes the system throughput.
Meets the QoS requirement (such as the packet loss rate) to achieve the best tradeoff
between the data rate and block error rate.
Description
In the uplink, the initial MCS can be selected based on the signal to interference plus noise ratio
(SINR) of the uplink reference signal (RS) measured by the eNodeB. The MCS can be adjusted
based on control signals if they are transmitted in the uplink.
Control signals may require a low-order MCS to ensure reliable transmission.
In the downlink, the eNodeB first selects the MCS for each UE based on the channel quality
indicator (CQI) reported from the UE and the power assigned to the UE. Then, the eNodeB can
adjust the CQI to select a proper MCS based on the block error rate (BLER) to maximize radio
resource usage.
Enhancement
None
Dependencies
None
1.9 TDLBFD-001007 Basic uplink-downlink subframe

configuration
1.9.1 TDLBFD-00100701 uplink-downlink subframe configuration
type1&2
Availability
Summary
eNodeBs support different uplink-downlink subframe configurations.
Benefits
This feature allows operators to flexibly configure the uplink-downlink subframe ratio based on
different service requirements.
Description
eNodeBs support different uplink-downlink subframe configurations specified in 3GPP TS
36.211, including:
Draft (2014-02-10)


Type 1: The ratio of uplink subframe to downlink subframe is 2:2. When this configuration
is used, the uplink and downlink traffic are symmetrical.
Type 2: The ratio of uplink subframe to downlink subframe is 1:3. When this configuration
is used, the downlink throughput is larger than the uplink throughput.
The table shown in the following figure lists subframe configurations.

Uplink-downlink
configuration
1
2
Downlink-to-Uplink
Switch-point periodicity
5 ms
5 ms
0
D
D
1
S
S
2
U
U
Subframe number
3 4 5 6 7
U D D S U
D D D S U
8
U
D
9
D
D
In the preceding figure, D denotes the subframe reserved for downlink transmissions, U denotes
the subframe reserved for uplink transmissions, and S denotes a special subframe that consists
of the downlink pilot timeslot (DwPTS), guard period (GP), and uplink pilot timeslot (UpPTS).
Enhancement
None
Dependencies
Subframe configuration type 1 cannot be used with the following features:
Subframe configuration type 2 cannot be used with the featureTDLOFD-001048 TTI Bundling.
1.9.2 TDLBFD-00100702 uplink-downlink special subframe

configuration type 7
Availability
Summary
eNodeBs support different special subframe configurations (DwPTS, GP, and UpPTS lengths).
Benefits
This feature enables the customer to flexibly configure special subframe configurations in
application scenarios, such as a different cell radius.
Draft (2014-02-10)


Description
eNodeBs support different special subframe configurations (DwPTS, GP, and UpPTS lengths)
specified in 3GPP TS 36.211. The GP length can determine the cell radius.
Type 7: The length ratio of DwPTS to GP to UpPTS is 10:2:2. When this configuration is used,
the maximum cell radius is 15 km.
The following table describes special subframe configuration type 7.
Special Subframe
Configuration
Normal CP
DwPTS
GP
UpPTS
21952 Ts
4384 Ts
4384 Ts
Enhancement
None
Dependencies
None
Draft (2014-02-10)

10

2 RAN Architecture & Features
RAN Architecture & Features
2.1 TDLBFD-002001 Logical Channel Management

Availability
Summary
Logical channels are provided between the Media Access Control (MAC) layer and the Radio
Link Control (RLC) layer. Logical channel types are defined based on the type of transmitted
data. They are generally classified into two types: control channels and traffic channels.
Huawei LTE TDD eNodeBs support all logical channels except those related to the evolved
Multimedia Broadcast Multicast Service (eMBMS) functionality.
Benefits
Each logical channel is used to transmit a type of data.
Description
Logical channels are generally classified into two types:
Control channels: used to transmit control-plane data
Traffic channels: used to transmit user-plane data
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:
Draft (2014-02-10)
Dedicated traffic channel (DTCH)


Multicast traffic channel (MTCH)
Huawei LTE TDD eNodeBs support all logical channels except those related to the eMBMS
functionality, such as the MCCH and MTCH.
Enhancement
None
Dependencies
None
2.2 TDLBFD-002002 Transport Channel Management

Availability
Summary
Transport channels are provided between the MAC layer and the physical layer. Transport
channel types are defined based on the type of transmitted data and the method of data
transmission over the radio interface. They are used to transmit service information to the MAC
layer and higher layers. Huawei LTE TDD eNodeBs support all transport channels except those
related to the eMBMS functionality.
Benefits
Each transport channel is used to transmit a type of data.
Description
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)
Huawei LTE TDD eNodeBs support all transport channels except those related to the eMBMS
functionality, such as the MCH.
Enhancement
None
Draft (2014-02-10)


Dependencies
None
2.3 TDLBFD-002003 Physical Channel Management

Availability
Summary
The physical layer performs 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 a high layer can serve
one or several physical channels at the physical layer.
Huawei LTE TDD eNodeBs support all physical channels except those related to the eMBMS
functionality, such as the PMCH.
Benefits
Each physical channel provides a set of resource blocks for transmission.
Description
Each physical channel corresponds to a set of resource elements carrying the information from
higher layers.
Downlink physical channels are classified into the following types:
Physical broadcast channel (PBCH)
Physical control format indicator channel (PCFICH)
Physical downlink control channel (PDCCH)
Physical hybrid ARQ indicator channel (PHICH)
Physical downlink shared channel (PDSCH)
Physical multicast channel (PMCH)
Uplink physical channels are classified into the following types:
Physical uplink control channel (PUCCH)
Physical uplink shared channel (PUSCH)
Physical random access channel (PRACH)
Huawei LTE TDD eNodeBs support all physical channels except those related to the eMBMS
functionality, such as the PMCH.
Enhancement
None
Draft (2014-02-10)


Dependencies
None
2.4 TDLBFD-002004 Integrity Protection

Availability
Summary
This feature offers integrity protection for signaling data. It enables the receiver (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
This feature prevents illegal modification of signaling data.
Description
Integrity protection is provided 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 sends the MAC-I code in the message to the receiver. The receiver recalculates the
X-MAC code and compares it with the MAC-I code in the message. If the two codes are
inconsistent, the receiver regards the message as illegally modified.
The eNodeB determines which integrity algorithm to use and informs each UE of the algorithm
with an RRC message.
Huawei LTE TDD eRAN2.0 supports both the EIA1 (SNOW3G) encryption algorithm and the
EIA2 (AES) integrity algorithm.
Enhancement
None
Dependencies
UEs must support the same integrity algorithms as the eNodeB.
2.5 TDLBFD-002005 DL Asynchronous HARQ

Availability
Draft (2014-02-10)


Summary
Hybrid automatic repeat and request (HARQ) improves robustness against transmission errors.
It is also a mechanism for capacity enhancement. Because HARQ retransmissions are fast,
many services allow one or multiple times of retransmissions, therefore forming an implicit
(closed-loop) rate-control mechanism. In the downlink, HARQ is based on an asynchronous
transmission protocol. Therefore, 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
retransmissions of incorrectly decoded data by using a NACK message. The retransmitted data
and previously received data can be soft-combined to improve 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
automatic repeat request (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 sends an ACK message to inform the eNodeB that the data was received
correctly. Otherwise, the UE sends a NACK message to the eNodeB to request data
retransmission.
Downlink HARQ is an asynchronous adaptive transmission process, in which the scheduler of
the HARQ retransmission is not predetermined for 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 previous transmissions.
As defined in 3GPP specifications, the DL HARQ scheme is based on an incremental
redundancy (IR) algorithm. After the retransmitted data is received, the UE soft-combines the
retransmitted data with the previously buffered content and then forwards the combined data to
the FEC for decoding. The soft-combined data helps increase the probability of successful FEC
decoding, therefore increasing the data reception success rate.
Multiple downlink HARQ processes are adopted to fully utilize system resources. This greatly
improves system throughput and reduces latency, but requires more buffer space and signaling
overhead.
Enhancement
None
Dependencies
None
Draft (2014-02-10)


2.6 TDLBFD-002006 UL Synchronous HARQ

Availability
Summary
Unlike 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 retransmissions of incorrectly decoded data. The retransmitted data can be
soft-combined with the previously received data to improve decoding performance.
This feature helps improve user throughput and reduce transmission latency in the uplink.
Description
The HARQ is a link enhancement technique combining FEC and ARQ technologies. Compared
with the ARQ, the HARQ can provide faster and more efficient retransmissions with shorter
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 sends an ACK message over the PHICH to
inform the UE that the data was received correctly. Otherwise, the eNodeB sends a NACK
message to the UE to request data retransmission.
In LTE TDD eRAN1.0, uplink HARQ is a synchronization non-adaptive transmission process,
in which HARQ transmission blocks are predetermined for transmission and retransmission. In
addition, the UL HARQ information, such as the location of the allocated resource blocks and
MCSs, is predetermined by the eNodeB.
In LTE TDD eRAN2.0, Huawei supports a synchronous adaptive UL HARQ transmission.
During retransmission, the allocated resource blocks and MCS may be changed according to
the channel quality. However, the size of retransmitted blocks remains the same as that of the
initial transmission.
As defined in 3GPP specifications, the uplink HARQ scheme is based on an IR algorithm. After
the retransmitted data is received, the eNodeB soft-combines the retransmitted data with the
previously buffered content and then forwards the combined data to the FEC for decoding. The
soft-combined data helps increase the probability of successful FEC decoding, therefore
increasing the data reception success rate.
Multiple uplink HARQ processes are adopted to fully utilize system resources. This greatly
improves system throughput and reduces latency, but requires more buffer space and signaling
overhead.
In LTE TDD eRAN2.0, Huawei supports a synchronous adaptive uplink HARQ transmission.
While in eRAN1.0, uplink HARQ is a synchronization non-adaptive transmission process.
Draft (2014-02-10)


Enhancement
None
Dependencies
None
2.7 TDLBFD-002007 RRC Connection Management

Availability
Summary
An RRC connection is a layer-3 connection between a UE and an eNodeB. RRC connection
management involves establishing, reconfiguring, re-establishing, and releasing RRC
connections.
Benefits
RRC connection management is essential for UEs and eNodeBs, and meets all service and NAS
procedures.
Description
RRC connection management involves the following procedures:
RRC connection establishment

Used to establish an RRC connection. RRC connection establishment involves signaling
the radio bearer 1 (SRB1) establishment. In this procedure, the initial NAS dedicated
information or messages are transmitted from the UE to the E-UTRAN.
RRC connection reconfiguration

Used 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

Used 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 this procedure to continue the RRC connection. The connection
re-establishment will succeed only if the cell has a valid UE context.
RRC connection release

Used to release an RRC connection. RRC connection release involves releasing all radio
resources.
Draft (2014-02-10)


Enhancement
This feature was enhanced in LTE TDD eRAN6.0. According to 3GPP Release 9 specifications,
eNodeBs support the following UE types:
UEs with the same FDD and TDD capabilities

When the UEs move between TDD and FDD cells, eNodeBs do not need to obtain UE
EUTRA capability information.
UEs with different FDD and TDD capabilities

When the UEs move between TDD and FDD cells, eNodeBs need to obtain UE EUTRA
capability information.
When a UE supports both TDD and FDD, the eNodeB checks whether the UE has the same or
different FDD and TDD capabilities as follows:
If the UE-EUTRA-Capability IE contains the tdd-Add-UE-EUTRA-Capabilities-r9 or

fdd-Add-UE-EUTRA-Capabilities-r9 IE, the UE has different FDD and TDD capabilities.
If the UE-EUTRA-Capability IE contains neither the

tdd-Add-UE-EUTRA-Capabilities-r9 nor fdd-Add-UE-EUTRA-Capabilities-r9 IE, the
UE has the same FDD and TDD capabilities.
The eNodeB can obtain the UE EUTRA capability information from the MME or UE, including
the functions supported by both FDD and TDD cells, optional functions supported by TDD
cells, and optional functions supported by FDD cells. Then, the eNodeB enables the functions
supported by the serving cell.
During an S1 or X2 handover from a TDD cell to an FDD cell, the TDD eNodeB sends a
handover request message with the UE-EUTRA-Capability IE to the FDD eNodeB.
During an S1 or X2 handover from an FDD cell to a TDD cell, the TDD eNodeB enables the
functions supported by both the FDD and TDD cells and the optional functions supported by
the TDD cell, which are indicated in the UE-EUTRA-Capability IE.
Dependencies
None
2.8 TDLBFD-002008 Radio Bearer Management

Availability
Summary
Radio bearer management involves establishing, maintaining, and releasing SRB2 and Data
Radio Bearer (DRB). Radio bearer management includes the establishment, maintenance, and
release of radio bearers.
Benefits
When this feature is enabled, radio resources can be configured.
Draft (2014-02-10)


Description
Radio bearer management involves establishing, maintaining, and releasing radio bearers, as
well as configuring associated radio resources, such as the PDCP, RLC, logical channel,
discontinuous reception (DRX), CQI, power headroom report (PHR), and physical layer
configuration.
Enhancement
None
Dependencies
None
2.9 TDLBFD-002009 Broadcast of System Information

Availability
Summary
System information (SI) includes:
Basic information for a UE to access the E-UTRAN, such as radio and channel parameters
Cell selection and reselection parameter settings for a UE in RRC_IDLE mode
Information about neighboring cells
Important messages that should be sent to each UE, such as Earthquake and Tsunami
Warning System (ETWS) notifications
The SI broadcast over the BCCH can be read without an RRC connection, and it can be read by
UEs in RRC_IDLE mode and RRC_CONNECTED mode. SI may also be provided to the UE
by using dedicated signaling messages, for example, in the case of handover.
Benefits
This feature is required for the UE to access the E-UTRAN.
Description
SI is classified into the master information block (MIB) and system information blocks (SIBs):
Draft (2014-02-10)
MIB defines the most essential physical layer information of the cell required for receiving
further system information.
SIB1 contains the information for checking whether a UE is allowed to access a cell and
for defining the scheduling of other system information blocks.
SIB2 contains the information about common and shared channels.
SIB3 contains cell reselection information, mainly related to the serving cell.

SIB4 contains the information about the serving frequency and intra-frequency
neighboring cells related to cell reselection (including common cell reselection parameters
for a frequency and cell-specific reselection parameters).
SIB5 contains the information about other E-UTRA frequencies and inter-frequency
SIB6 contains the information about UTRA frequencies and UTRA neighboring cells
related to cell reselection (including common cell reselection parameters for a frequency
and cell-specific reselection parameters).
SIB7 contains the information about GERAN frequencies related to cell reselection
(including cell reselection parameters for each frequency).
SIB8 contains the information about CDMA2000 frequencies and CDMA2000

SIB9 contains a home eNodeB identifier (HNBID).
SIB10 contains an ETWS primary notification.
SIB11 contains an ETWS secondary notification.
The paging message is used to inform the UEs in RRC_IDLE and RRC_CONNECTED modes
of system information changes.
Huawei LTE TDD eNodeB supports MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB10,
and SIB11.
Enhancement
None
Dependencies
None
2.10 TDLBFD-002010 Random Access Procedure

Availability
Summary
Random access is the essential function of the LTE system, which allows a UE to achieve
uplink synchronization and to request a connection to an eNodeB. It is performed in the
following situations:
Draft (2014-02-10)
Initial access from RRC_IDLE mode
RRC connection re-establishment procedure
Handover
DL data arrival in RRC_CONNECTED mode (random access procedure required)
UL data arrival in RRC_CONNECTED mode (random access procedure required)

10

Benefits
This feature is required for the UE to access the E-UTRAN.
Description
Huawei eNodeB supports both types of random access procedures:
Contention-based
Applies to all preceding situations.
Non-contention-based
Applies only to handover and DL data arrival.
Data can be transmitted after the random access procedure.

Huawei TDD eNodeBs support random access preamble format 0 and format 4.
Enhancement
None
Dependencies
None
2.11 TDLBFD-002011 Paging

Availability
Summary
The purpose of paging is to transmit paging information to a UE in RRC_IDLE mode, and/or to
inform UEs in RRC_IDLE and RRC_CONNECTED modes of a system information change.
Benefits
With this feature, eNodeBs can page UEs or inform UEs of system information change.
Description
An eNodeB initiates the paging procedure by using a paging message, which can be sent by the
MME or eNodeB.
When an eNodeB receives a paging message from an MME over the S1 interface, the eNodeB
pages UEs in the cells that belong to tracking areas indicated in the List of TAIs Information
Element (IE) in the paging message.
When the system information changes, the eNodeB must inform all UEs in a cell by paging. In
order for the eNodeB to guarantee that every UE can receive the paging message, the eNodeB
must send the paging message on each possible paging occasion throughout a discontinuous
Draft (2014-02-10)

11

reception (DRX) cycle. Support for UE DRX must be broadcast to the entire cell coverage area
and mapped to physical resources.
Enhancement
None
Dependencies
None
2.12 TDLBFD-002012 Cell Access Radius up to 15km

Availability
Summary
To improve wireless network coverage, 3GPP TS 36.211 defines five types of preamble formats
(0, 1, 2, 3, and 4), where the basic format 0 corresponds to a cell radius of 15 km.
Benefits
This feature allows eNodeBs to support a cell radius up to 15 km.
Description
According to 3GPP TS 36.211, five preamble formats (0, 1, 2, 3, and 4) for the PRACH are
defined to support different cell radius values, as shown in Table 2-1.
Table 2-1 Preamble formats and cell radius
Preamble Format
TCP
TSEQ
Cell Radius
103.1 s
800 s
About 15 km
684.4 s
800 s
About 70 km
203.1 s
1600 s
About 30 km
684.4 s
1600 s
About 100 km
14.58 s
133.33 s
About 1.4 km
Huawei TDD eNodeBs support random access preamble format 0 and format 4.
Enhancement
None
Draft (2014-02-10)

12

Dependencies
This feature is not applicable to micro eNodeBs
2.13 TDLBFD-002023 Admission Control

Availability
Summary
Admission control ensures system stability by controlling connection establishment within
maximum resource utilization while satisfying QoS requirements.
Benefits
This feature provides the following benefits:
Improves cell stability by controlling the number of admitted services
Achieves an optimal tradeoff between maximizing resource utilization and ensuring QoS
by preventing congestion and checking QoS satisfaction
Description
Admission control is a cell-based operation applied to both uplink and downlink and is a key
radio resource management (RRM) function. Admission control is performed when there are
new incoming calls or incoming handover attempts. In Huawei admission control solution,
system resource limitation and the QoS satisfaction ratio are the main considerations for
admission control.
When a new incoming call or incoming handover request arrives, the eNodeB checks the
system resource limitation (including hardware resource usage and system overload indication)
first. If any of the resources is limited, the new service request will be rejected.
Enhancement
None
Dependencies
None
2.14 TDLBFD-002024 Congestion Control

Availability
Draft (2014-02-10)

13

Summary
Congestion control reduces the system load when the system is congested or QoS requirements
cannot be met.
Benefits
Prevents an unstable system due to overload
Improves the QoS satisfaction rate for admitted services while achieving the maximum
radio resource utilization.
Description
To maintain the system stability and meet QoS requirements for an overloaded system, an
eNodeB enabled with congestion control performs the following operations:
Releases low-priority services to reduce the system load

The priority is determined based on the QoS Class Identifier (QCI) assigned to the service.
Downsizes guaranteed bit rate (GBR) services

The eNodeB decreases the GBR service rate slightly while still maintaining higher than
the minimum rate to improve the overall QoS satisfaction ratio.
Enhancement
None
Dependencies
None
2.15 TDLBFD-002025 Basic Scheduling

Availability
Summary
Basic scheduling provides two common scheduling algorithms (MAX C/I and PF). Operators
can select either algorithm.
Benefits
This feature provides operator flexibility to select the scheduling algorithm while considering
system capacity and fairness among users.
Draft (2014-02-10)

14

Description
An eNodeB uses scheduling algorithms to allocate resources to each UE during each TTI.
Considering the tradeoff between system capacity and fairness among users, two scheduling
algorithms are available:
MAX C/I
By using the MAX C/I algorithm, users are scheduled based on their radio channel quality.
However, fairness among users cannot be guaranteed because the radio channel quality is
the only factor to be considered in this algorithm.
Proportional fair (PF)

By using the PF algorithm, users are scheduled based on 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. Based on the radio channel quality of an individual user, the PF scheduler
provides the user with an average throughput proportional to its average channel quality.
In most cases, this algorithm is used to ensure fairness among users while achieving a
moderate cell capacity.
Enhancement
None
Dependencies
None
2.16 TDLBFD-002026 Uplink Power Control

Availability
Summary
Uplink power control allows eNodeBs to control the transmit power of UEs and the
interference to neighboring cells, improving system throughput. This feature applies to the
physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), sounding
reference signal (SRS), and physical random access channel (PRACH).
Benefits
Draft (2014-02-10)
Reduces UE power consumption and interference between neighboring cells
Increases overall throughput in an LTE system
Ensures quality of service applications, such as the block error rate (BLER)

15

Description
Uplink power control is one of the most important features of an LTE system. This feature uses
the power control mechanisms for the PUSCH, PUCCH, SRS, and PRACH.
PUSCH power control
PUSCH power control includes power adjustment for both dynamic scheduling and
semi-persistent scheduling.
For dynamic scheduling

Based on the difference between the estimated transmission power spectrum density
(PSD) and PSDTarget, the transmit power of the PUSCH is periodically adjusted
according to changes in the channel environment. If the estimated PSD is greater than
the PSDTarget, the eNodeB sends a TPC command to decrease the transmit power. If
the estimated PSD is less than the PSDTarget, the eNodeB sends a TPC command to
increase the transmit power.
Based on the overload indication (OI) from the neighboring cell and estimated channel
condition, the PSDTarget is periodically adjusted to adapt to the channel environment
changes and neighboring cell interference.
For semi-persistent scheduling

Based on the difference between the measured IBLER and IBLERTarget, the transmit
power of the PUSCH is periodically adjusted according to changes in the channel
environment. If the measured IBLER is greater than the IBLERTarget, the eNodeB
sends a TPC command to the UE to increase the transmit power. If the measured
IBLER is less than the IBLERTarget, the eNodeB sends a TPC command to the UE to
decrease the transmit power.
The PUSCH TPC commands of multiple VoIP users are sent to the UEs by using DCI
format 3 or 3A. This reduces signaling overheads over PDCCH.
PUCCH power control

Based on the difference between the measured SINR and SINRTarget, the transmit power
of the PUCCH is periodically adjusted according to changes in the channel environment.
If the measured SINR is greater than the SINRTarget, the eNodeB sends a TPC command
to decrease the transmit power. If the measured SINR is less than the SINRTarget, the
eNodeB sends a TPC command to increase the transmit power.
Uplink SRS power control

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 the RRC
layer is added.
PRACH power control

The UE will calculate the transmit power for the initial random access (RA) preamble by
estimating the downlink path loss and based on the expected received power from the UE
on the eNodeB, which is obtained by monitoring the broadcast channel. If the RA
preamble attempt fails (for example, no RA preamble response for the eNodeB), the UE
can increase the transmit power for the next RA preamble attempt according to the settings
configured by the RRC layer.
BTS3205Es do not support the following power control algorithms:
Draft (2014-02-10)
PUCCH outer loop power control
PUSCH inner loop power control at the UE level

16

PUSCH outer loop control at the UE level
PUSCH absolute closed-loop power control at the UE level
Closed-loop power control for power saving enhancement at the UE level
Enhancement
None
Dependencies
None
2.17 TDLBFD-002016 Dynamic Downlink Power

Allocation
Availability
Summary
Dynamic downlink power allocation allows eNodeBs to set the transmit power on downlink
channels to reduce power consumption while maintaining radio link quality. It provides flexible
power allocation for downlink channels based on the UE channel quality and maintains
acceptable downlink connection quality.
Benefits
This feature improves edge user throughput and transmit power usage.
Description
The LTE downlink power allocation is implemented on different types of downlink channels,
including the 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).
Draft (2014-02-10)
The fixed power setting is used for the cell-specific reference signal, synchronization
signal, PBCH, PCFICH, and channels carrying common cell information (such as PDCCH
and PDSCH) to ensure the downlink cell coverage.
SINR estimation is based on the CQI report. Based on the difference between the
estimated SINR and SINRTarget, the transmit power of the PHICH is periodically
adjusted according to path loss and shading. If the estimated SINR is less than the
SINRTarget, the transmit power is increased. Otherwise, the transmit power is decreased.
In dynamic scheduling, the PDSCH power is determined by PA and adjusted by updating

PA. After receiving a CQI reported from the UE, the eNodeB compares it with what the
CQI previously reported. If the difference between the two CQI values is great, the
eNodeB adjusts the PDSCH power and re-calculates the PA for the UE.
17

In semi-static scheduling, based on the difference between the measured IBLER of VoIP
packets and the IBLERTarget, the transmit power of the PDSCH is periodically adjusted to
meet IBLERTarget requirements. If the measured IBLER is less than the IBLERTarget, the
transmit power is decreased. Otherwise, the transmit power is increased.
In LTE TDD eRAN1.0, the PDSCH and PDCCH support dynamic power control.
In LTE TDD eRAN2.0, PDSCH and PDCCH dynamic power control have been optimized.
Enhancement
None
Dependencies
None
2.18 TDLBFD-002018 Mobility Management

2.18.1 TDLBFD-00201801 Coverage Based Intra-frequency
Handover
Availability
Summary
Handover functionality is important in cellular telecommunications networks. It is performed to
ensure no interruption of services. Handovers play a significant role in LTE system
performance because its main purpose is to decrease communication delay, enlarge coverage,
and enhance system performance.
An intra-frequency handover enables a UE in RRC_CONNECTED mode to be continuously
served when it moves across different cells operating at the same frequency.
Benefits
This feature provides supplementary coverage in intra-frequency LTE systems to prevent
service drops, enable seamless coverage, and improve the network performance and user
experience.
Description
During a handover in the LTE system, the original connection is released before a new
connection is set up.
An intra-frequency handover is performed between cells operating at the same frequency band.
It can be triggered by coverage or load. LTE TDD eRAN1.0 supports coverage-based
intra-frequency handover.
Draft (2014-02-10)

18

The intra-frequency handover procedure can be divided into three phases: handover
measurement, handover decision, and handover execution.
1.
An eNodeB configures and delivers the handover-related measurement in the RRC

Connection Reconfiguration message to a UE. The UE can measure either the reference
signal received power (RSRP) or reference signal received quality (RSRQ) for
intra-frequency handover.
2.
Upon receiving a measurement report from the UE, the eNodeB makes a handover
decision according to certain triggering criteria.
3.
If a handover is required, the handover execution procedure is invoked and the UE is

handed over from the source eNodeB to the target eNodeB.
Huawei LTE TDD eRAN1.0 follows the intra-frequency handover procedures specified in
3GPP TS 36.300.
Intra-frequency handovers apply to the following scenarios:
Handover between two cells configured for the same eNodeB

In this scenario, no external neighboring cell is necessary.
Handover between two cells configured for different eNodeBs with an X2 interface
available
In this scenario, the source eNodeB sends a HANDOVER REQUEST message over the
X2 interface.
Handover between two cells configured for different eNodeBs with no X2 interface
available
In this scenario, the source eNodeB sends a HANDOVER REQUIRED message over the
S1 interface.
Enhancement
None
Dependencies
None
2.18.2 TDLBFD-00201802 Coverage Based Inter-frequency

Handover
Availability
Summary
An inter-frequency handover enables a UE in RRC_CONNECTED mode to be served
continuously when it moves across different cells operating at different frequencies.
Draft (2014-02-10)

19

Benefits
This feature provides supplementary coverage in inter-frequency LTE systems to prevent
service drops, enable seamless coverage, and improve the network performance and user
experience.
Description
The inter-frequency handover procedure can be divided into four phases: measurement
triggering, handover measurement, handover decision, and handover execution.
1.
A neighboring cell measurement is triggered by event A2 and stopped by event A1, based
on the measured value of RSRP or RSRQ. In inter-frequency handovers, neighboring cell
measurements are inter-frequency gap-assisted measurements for UEs with one RF
receiver.
2.
The UE sends measurement reports to the eNodeB when the RSRP or RSRQ meets the
criteria set in the measurement configuration.
3.
Upon receiving a measurement report from the UE, the eNodeB makes a handover
decision.
4.
If the measurement meets the handover criteria, the eNodeB performs the inter-frequency
handover as specified in 3GPP TS 36.300.
Inter-frequency handovers apply to the following scenarios:
Handover between two cells configured for the same eNodeB

In this scenario, no external interface is required.
Handover between two cells configured for different eNodeBs with an X2 interface
available
In this scenario, the source eNodeB sends a HANDOVER REQUEST message over the
X2 interface.
Handover between two cells configured for different eNodeBs with no X2 interface
available
In this scenario, the source eNodeB sends a HANDOVER REQUIRED message over the
S1 interface.
Enhancement
In LTE TDD eRAN6.0, this feature is enhanced as follows:
Event A2 for coverage-based inter-frequency blind redirection is added.

Coverage-based inter-frequency blind redirection and coverage-based inter-RAT blind
redirection use the same event A2 for blind redirection. Blind redirection is performed if
event A2 for blind redirection is triggered, regardless of the measurement result.
The frequency priority for UEs in connected mode is applied in blind redirection.
In eRAN6.0, the target frequency of an inter-frequency blind redirection can now be
selected based on the frequency priority configuration. This simplifies the neighboring
cell configuration in the early LTE network deployment phase.
After a UE accesses a cell, the UE reports two A2 events based on the signal quality of
neighboring cells:
Draft (2014-02-10)
One event is used to trigger an inter-frequency handover measurement.
The other is used to trigger blind redirection.

20

If event A2 for blind redirection is triggered, the signal quality in the serving cell has
become too poor to provide services for the UE. If this happens in the early LTE network
deployment stage when neighbor relationships have not been configured, handovers
cannot be performed. In this situation, the eNodeB performs a blind redirection for the UE.
Different priorities for blind redirection and measurement priorities are used in LTE TDD
and FDD.
For coverage-based handovers, operators can configure different event A2 thresholds to
differentiate measurement-based handover priorities for LTE TDD and FDD, and can
configure the top two RAT priorities to the priorities for coverage-based inter-frequency
blind handovers in LTE TDD and FDD.
EPLMNs can be used as the target PLMN in handovers.

Both the EPLMNs delivered by the core network and the PLMNs in the available PLMN
list configured on the eNodeB can be used as the target PLMN in handovers.
Dependencies
This feature is implemented on the eNodeB, M2000, and CME. These NEs must support
parameter settings related to this feature.
2.18.3 TDLBFD-00201803 Cell Selection and Re-selection

Availability
Summary
Cell selection and reselection allow UEs in RRC_IDLE mode to select/reselect a cell on which
to camp, experiencing the optimal service support upon session activation in the LTE system.
Benefits
This feature facilitates automatic cell selection and reselection for UEs in RRC_IDLE mode
and reduces manual operations.
The UE is always bound to a relatively good-quality cell to obtain better service quality.
Description
When a UE selects a PLMN or the UE mode is changed from RRC_CONNECTED to
RRC_IDLE, cell selection is required. The non-access stratum (NAS) maintains a list of
forbidden registration areas and a list of equivalent PLMN and specifies the RAT associated
with the selected PLMN to determine the RAT type of the cell to be selected. The UE selects a
suitable cell based on the measurement results and cell selection criteria.
When camping on a cell, a UE regularly searches for a cell with a better radio environment
based on cell reselection criteria. If a cell with a better radio environment is detected, the UE
reselects the cell.
Absolute priorities of different E-UTRAN frequencies are provided for UEs in the system
information and optional in RRC connection release messages.
Draft (2014-02-10)

21

Enhancement
None
Dependencies
None
2.18.4 TDLBFD-00201804 Distance Based Inter-frequency

Handover
Availability
Summary
Huawei LTE eNodeBs support distance-based inter-frequency handovers.
Benefits
This feature improves user experience.
Description
When moving away from the serving eNodeB working at frequency F1, a UE may still
experience a relatively strong signal from the eNodeB. As a result, the condition of A2 event
cannot be satisfied to trigger an inter-frequency handover even though the signal quality of the
inter-frequency neighboring eNodeB is much better than that of the serving eNodeB. To
provide better-quality UE connections, a distance-based inter-frequency handover is
performed.
When the distance-based handover algorithm is used, the eNodeB must continuously measure
the distance to each UE based on the TA measurement. Once the distance exceeds the distance
threshold configured by the operator, inter-frequency gap-assisted measurements of the
neighboring eNodeB are triggered to search for an optimal candidate cell for the handover.
Enhancement
None
Dependencies
UEs must support inter-frequency gap-assisted measurements.
2.18.5 TDLBFD-00201805 Service Based Inter-frequency Handover

Availability
Draft (2014-02-10)

22

Summary
Huawei LTE eNodeBs support service-based inter-frequency handovers. UEs with specific
service can move to the configured frequency cell.
Benefits
This feature improves system efficiency and capacity.
Description
An operator can configure a group of policies for service-based inter-frequency handovers.
Each group is associated with a QCI. The default policy is to prohibit handovers. Service-based
inter-frequency handovers are not recommended for the bearers with QCI 5 and QCIs of default
bearers.
When the service-based inter-frequency handover algorithm is used, the eNodeB continuously
monitors the UE service status. If the QCI (each type of service is mapping to a QCI) is changed,
inter-frequency measurements of the configured group are triggered to search for an optimal
candidate cell for the handover.
Enhancement
None
Dependency
UEs must support inter-frequency gap-assisted measurements.
This feature applies to macro eNodeBs only.
2.18.6 TDLBFD-00201806 Multi-Band Compatibility Enhancement

Availability
Summary
If a cell works at a frequency that belongs to multiple bands, it can be configured as a
multi-band cell.
Benefits
Draft (2014-02-10)
Frequency resource efficiency improves and UEs supporting multiple bands can access a
network configured with these bands. For example, if a cell is configured with both bands
38 and 41, UEs supporting the two bands can access the cell.
UE management and maintenance workload is reduced. For example, a UE supporting

both bands 38 and 41 can access the networks configured with these bands, and therefore
fewer UE models must be maintained.

23

Description
According to 3GPP TS 36.331 released before October, 2012, the information about the band
supported by a cell is sent to a UE by using an SIB, and each cell supports only one band. If the
band indicated in the SIB differs from the band supported by the UE, the UE cannot access the
cell.
3GPP TS 36.331, released in October 2012, defines the extended fields for SIBs:
SIB1: contains the multi-band indicator of the serving cell.
SIB2: contains additionalSpectrumEmission of different bands.
SIB5: contains the multi-band indicator of a neighboring cell.
SIB6: contains the multi-band indicator of a UMTS cell.
In LTE TDD eRAN6.0, a cell can work at multiple bands and the preceding types of SIBs are
sent to UEs.
If a UE supports one of the bands at which a cell works, the UE can access the cell.
If a UE supports one of the bands configured for a neighboring cell, the UE can be handed over
to this cell. More candidate cells are therefore available for a UE handover.
If a UTRAN cell is configured with different bands, SIB6 is used to send the band information
to UEs. If a UE supports one of the bands, more candidate cells are available for inter-RAT cell
reselection.
Enhancement
None
Dependencies
This feature depends on TDLBFD-002009 Broadcast of System Information.
UEs 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.
2.19 TDLBFD-070111 Multi-Cell Interference

Randomizing
Availability
This feature is introduced in eRAN TDD 7.0.
Summary
This feature offers the following benefits:
Draft (2014-02-10)
Increases the spectral efficiency, proportion of high-order MCSs, handover success rate,
and service rate experienced by users.
Decreases the service drop rate..

24

Benefits
This feature improves receiver sensitivity and uplink coverage.
Description
This feature is implemented on the eNodeB.
The eNodeB uses the PCI of a cell to determine the start position of the resource block groups
(RBGs) that are allocated to the UEs in this cell. Therefore, the UEs in different cells are
allocated different resources because the cells under the same eNodeB are configured with
different PCIs. In this way, co-channel interference between cells is reduced and the signal
quality is improved.
Enhancement
None
Dependencies
None.
2.20 TDLBFD-002020 Antenna Configuration

2.20.1 TDLBFD-00202001 UL 2-Antenna Receive Diversity
Availability
Summary
Receive (RX) diversity is a common multiple-antenna technology to improve signal reception
performance and to mitigate the signal fading effect and interference. It improves network
capacity and data rates. Huawei eNodeBs can work with or without RX diversity.
Benefits
This feature improves receiver sensitivity and uplink coverage.
Description
This feature enables eNodeBs 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,
therefore mitigating the signal fading effect and interference.
RX diversity enhances signal reception performance over uplink channels, including the
PUSCH, PUCCH, PRACH, and SRS.
Draft (2014-02-10)

25

In RX diversity mode, an eNodeB can be configured with 2 antennas (2-way) by setting the
antenna magnitude. No additional device is required and the eNodeB uses the maximum ratio
combining (MRC) or interference rejection combining (IRC) algorithm.
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 antenna connector settings.
Space-interlace antennas or cross polarization antennas can be used for this feature.
Enhancement
None
Dependencies
eNodeBs must provide sufficient RF channels and demodulation resources that can match the
number of diversity antennas.
2.21 TDLBFD-002021 Reliability

2.21.1 TDLBFD-00202102 Cell Rebuild between Baseband
Processing Units
Availability
This feature was introduced in Huawei LTE TDD eRAN2.1.
Summary
In Huawei eNodeB, multiple LTE baseband process units (LBBPs) can be configured to serve
multiple cells. When an LBBP fails, the cell/cells served by the failed LBBP can be
reestablished on another operating LBBP with spare resources or on a backup LBBP if
available.
Benefits
This feature ensures cell coverage through cell reestablishment and improves system reliability
in case of an LBBP failure.
Description
Generally, an eNodeB is equipped with multiple LBBPs that serve multiple cells. Figure 2-1
shows an LBBP configuration example.
Draft (2014-02-10)

26

Figure 2-1 LBBP configuration example
In this example, two LBBPs are configured to serve three 10 MHz cells and to connect to three
2T2R RRUs with CPRI interface backup.
When an LBBP fails due to, for example, a hardware fault or an interface failure, the eNodeB
can detect and locate the failure and select a target LBBP on which the cell(s) are to be
reestablished. The target LBBP must have a CPRI connection to the RRU serving the cell(s)
involved, as shown in Figure 2-1. The target LBBP is selected depending on the spare resources
on the LBBP. If the spare resources on the target LBBP are inadequate, the bandwidth of the
cell(s) to be reestablished or even that of the existing cells can be decreased.
Enhancement
None
Dependencies
RRUs with two transmit channels must be used.
eNodeBs must be equipped with at least two LBBPs.
2.21.2 TDLBFD-00202103 SCTP Multi-homing

Availability
Summary
Stream Control Transmission Protocol (SCTP) is the signaling bearer protocol of the S1/X2
interface. It provides service features similar to Transmission Control Protocol (TCP) and User
Draft (2014-02-10)

27

Datagram Protocol (UDP), ensures reliable and in-sequence transmission of messages with
congestion control, and offers multi-homing support for fault recovery with switchover
between redundant network paths.
Benefits
This feature ensures signaling bearer reliability.
Description
An SCTP link is a logical channel between the eNodeB and MME. It has two IP-couple paths: a
master path and a slave path, as shown in Figure 2-2. Generally, the master path is active. When
the master path fails, the slave path is activated.
Figure 2-2 SCTP protocol
Enhancement
None
Dependencies
None
2.21.3 TDLBFD-00202104 Intra-baseband Card Resource Pool(user

level/cell level)
Availability
Summary
This feature aggregates the processing resources on a baseband processing board installed in a
Huawei eNodeB into a baseband resource pool where resources are shared for service
processing. This prevents individual resource outage due to overload.
Draft (2014-02-10)

28

Benefits
Ensures eNodeB stability and robustness
Balances cell load
Improves eNodeB average cell capacity
Description
The baseband processing board installed in a Huawei eNodeB consists of several processing
resources. A baseband processing board can be configured with multiple cells, depending on
the bandwidths. In this feature, the aggregated resources in a pool are shared to process user
data in multiple cells. A new user is assigned to a resource with the lightest load. If a resource is
overloaded or in outage, the eNodeB can reduce the individual resource load or transfer the
users served by the resource to other resources.
Enhancement
None
Dependencies
None
2.22 TDLBFD-002027 Support of UE Category 1

Availability
Summary
An eNodeB must obtain the signaled UE radio access capability parameters when configuring
and scheduling the UE. There are five categories defined in the protocol. When this feature is
enabled, eNodeBs support UE category 1.
Benefits
eNodeBs support UE category 1.
Description
The following table lists the downlink physical layer parameter values in the ue-Category field.
Draft (2014-02-10)

29

UE
Category
Maximum
Number of
DL-SCH
Transport Block
Bits Received
Within a TTI
Maximum
Number of Bits
of a DL-SCH
Transport Block
Received Within
a TTI
Total
Number of
Soft
Channel
Bits
Maximum
Number of
Supported
Layers for DL
Spatial
Multiplexing
Category 1
10296
10296
250368
Category 2
51024
51024
1237248
Category 3
102048
75376
1237248
Category 4
150752
75376
1827072
The following table lists the uplink physical layer parameter values in the ue-Category field.
UE Category
Maximum Number of Bits of an

UL-SCH Transport Block
Transmitted Within a TTI
Support for UL
64QAM
Category 1
5160
No
Category 2
25456
No
Category 3
51024
No
Category 4
51024
No
The following table lists the total layer-2 buffer sizes in the ue-Category field.
UE Category
Total Layer-2 Buffer Size (Kbytes)
Category 1
150
Category 2
700
Category 3
1400
Category 4
1900
Enhancement
None
Dependencies
UEs must support the same category as the eNodeB.
Draft (2014-02-10)

30

2.23 TDLBFD-002031 Support of aperiodic CQI reports

Availability
Summary
Aperiodic CQI can be reported on the PUSCH. UEs can be configured to report periodic CQI
and aperiodic CQI together or individually.
Benefits
Aperiodic CQI offers detailed channel quality information, which improves scheduler
efficiency.
Description
Aperiodic CQI is triggered by the UL scheduler and the CQI Request field in the UL grant
indicates the aperiodic CQI report. There are five aperiodic reporting modes.
Wideband-configured
Mode 1-2: A wideband CQI per codeword and multiple precoding matrix indications
(PMIs) for each subband are reported.
UE selected (subband CQI)
Mode 2-0: A wideband CQI and a subband CQI for M preferred subbands are reported.
Mode 2-2: A wideband CQI and a subband CQI for M preferred subbands per
codeword are reported. A wideband PMI and a subband PMI for M preferred subbands
are also reported.
Higher layer-configured
Mode 3-0: A wideband CQI and multiple subband CQIs for each subband are reported.
Mode 3-1: A wideband CQI and multiple subband CQIs for each subband per
codeword are reported. A wideband PMI is also reported.
The reporting mode is configured at the RRC layer.

Huawei eNodeBs support all aperiodic report modes and simultaneous reporting of periodic
CQI and aperiodic CQI.
Enhancement
None
Dependencies
None
Draft (2014-02-10)

31

2.24 TDLBFD-002032 Extended-QCI

Availability
Summary
Huawei eNodeBs support extended QoS class identifier (QCI) (255 QCI including 9 standard
QCI defined in 3GPP specifications). Extended QCI can be used as operator-defined QCI to
support customized non-GBR services. Extended QCI index can be defined by operators and
the SAE must support it.
Benefits
It can be configurable flexibly by operators and meet operators' requirements for differentiated
services.
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 eNodeBs currently support extended non-GBR QCI. An eNodeB obtains the QCI
index, and then set the ARP and QoS parameters (such as PDB, PLER, schedule weight) related
to the QCI index.
Enhancement
None
2.25 TDLBFD-002035 Multi Carrier

Availability
Summary
This feature is used to increase system capacity when frequency resources are sufficient.
Draft (2014-02-10)

32

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

33

3 Transport
Transport
3.1 TDLBFD-003001 Transmission Networking

3.1.1 TDLBFD-00300101 Star Topology
Availability
Summary
Star topology is easy to implement and manage and is highly reliable. It provides a simple
topology between eNodeB interfaces.
Benefits
Simple topology
Simple management and high reliability
Description
Figure 3-1 illustrates star topology.
Draft (2014-02-10)


3 Transport
Figure 3-1 Star topology
eNodeBs support star topology.

eNodeBs connect to the EPC through the layer-2 or layer-3 data network. The interface between
the eNodeB and EPC is the S1 interface.
In addition, connections are set up between eNodeBs over the X2 interface to enable
information exchange between the eNodeBs.
Enhancement
None
Dependencies
None
3.1.2 TDLBFD-00300102 Chain Topology

Availability
Summary
eNodeBs can be connected in the chain topology.
Benefits
This feature reduces the costs of transmission equipment, engineering, construction, and
transmission link leasing.
Draft (2014-02-10)


3 Transport
Description
The chain topology applies to sparsely populated strip-shape areas, such as expressways and
railways. In these areas, the chain topology can meet requirement with relatively less
transmission equipment. However, chain networking reduces transmission reliability because
signals are transmitted across many intermediate systems.
Figure 3-2 shows the chain topology.
Figure 3-2 Chain topology
Enhancement
None
Dependencies
None
3.1.3 TDLBFD-00300103 Tree Topology

Availability
Summary
eNodeBs can be connected in the tree topology.
Benefits
Tree networking requires fewer transmission links than star networking.
Description
The tree topology applies to microwave transmission networks.
Due to fewer required transmission links, tree topology reduces transmission reliability because
signals are transmitted across many intermediate systems. A fault occurring in the upper-level
eNodeB may affect operation of lower-level eNodeBs.
The tree topology is used in large, sparsely populated areas. Capacity expansion may
necessitate in reconstruction of the network.
Figure 3-3 illustrates tree topology.
Draft (2014-02-10)


3 Transport
Figure 3-3 Tree topology
Enhancement
None
Dependencies
The feature is based on E1/T1 and Ethernet interfaces.
3.2 TDLBFD-003006 IPv4/IPv6 Dual Stack

Availability
Summary
A fundamental IPv4-to-IPv6 transition technology involves the presence of two IP software
implementations in an operating system, one for IPv4 and another for IPv6.
This feature provides support for the IPv6 protocol stack. It also enables IPv4 and IPv6 protocol
stacks to work at the same time. Application-level protocols (such as S1 and X2) over IPv6 are
not supported by this feature.
IPv4-to-IPv6 transition requires compatibility with widely installed IPv4 hosts and routers.
Benefits
This feature streamlines IPv4-to-IPv6 transition.
Draft (2014-02-10)


3 Transport
Description
The most straightforward way for IPv6 nodes to remain compatible with IPv4-only nodes is by
providing complete IPv4 implementation. IPv6 nodes that provide complete IPv4 and IPv6
implementations are called IPv6/IPv4 dual-stack nodes, which can 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 eNodeBs can work in one of the following modes:
With IPv4 stack enabled and IPv6 stack disabled
With IPv6 stack enabled and IPv4 stack disabled
With both IPv4 and IPv6 stacks enabled
A switch for disabling either IPv4 or IPv6 stack is available for Huawei eNodeBs.
Enhancement
None
Dependencies
None
Draft (2014-02-10)


4 Transport QoS
Transport QoS
4.1 TDLBFD-003002 Basic QoS Management

4.1.1 TDLBFD-00300201 DiffServ QoS Support
Availability
Summary
Differentiated Services (DiffServ) is a QoS guarantee mechanism and enables eNodeBs to
classify and manage different services based on QCIs. It is a standard mechanism used by
mainstream vendors.
Benefits
This feature guarantees QoS.
Description
The DiffServ mechanism uses IP packet parameters, such as differentiated services code point
(DSCP) and type of service (TOS).
This mechanism involves classification, marking, and per-hop behavior (PHB). Different
services are classified and then marked with different PHBs based on the classifications:
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.
LTE services are classified QoS class indicators (QCIs). With Huawei configuration tool, users
can configure the relationships between QCIs and DSCPs, that is, by marking. The DSCP is
used to describe the PHB priority. Table 4-1 describes an example of relationships between
QCIs and DSCPs.
Draft (2014-02-10)


4 Transport QoS
Table 4-1 Relationships between QCIs and DSCPs

Data Type
QCI
Resource Type
DSCP
User plane
GBR
0x2E
0x1A
0x1A
0x22
Non-GBR
0x2E
0x12
0x12
0x0A
Control plane
SCTP
0x2E
OM
MML
0x2E
FTP
Enhancement
None
Dependencies
None
4.2 TDLBFD-003003 VLAN Support (IEEE 802.1p/q)

Availability
Summary
This feature enables the virtual local area network (VLAN) functionality to provide service
differentiation and manage data priority and security scheduling at the MAC layer.
Benefits
This feature provides the following benefits at the MAC layer:
Draft (2014-02-10)
Traffic isolation
Security

4 Transport QoS
Description
eNodeBs support the VLAN functionality, in compliance with the IEEE 802.1p/q protocol. It
provides traffic isolation (such as marking different VLAN tags for OAM data and service data)
and priority and security at the MAC layer. OAM is short for operation, administration and
maintenance.
VLAN tags are marked based on the DSCP or next-hop IP address.
Enhancement
None
Dependencies
None
Draft (2014-02-10)


5 Transport Synchronization
Transport Synchronization
5.1 TDLBFD-003005 Synchronization

5.1.1 TDLBFD-00300501 Clock Source Switching Manually or
Automatically
Availability
Summary
This feature enables manual or automatic switching between clock sources.
Benefits
If unexpected events occur in the current clock sources, the system will not be affected.
Description
The eNodeB can work in multiple clock synchronization modes. The system clock source can
be selected conveniently and flexibly. When one clock source fails, the system clock can be
manually or automatically switched to another available clock source.
The following clock sources are available:
GPS
IEEE1588V2
1PPS+TOD
In addition to the previous clock sources, the eNodeB can work with the local oscillator.
Enhancement
None
Draft (2014-02-10)


Dependencies
None
5.1.2 TDLBFD-00300502 Free-running Mode

Availability
Summary
Free-running mode is an alternative to the clock sources if all clocks fail.
Benefits
When all clock sources are lost, this feature can keep the eNodeB work properly for up to 8 or
24 hours.
Description
When all clock sources are lost, the eNodeB internal clock can work in free-running mode.
The highly accurate stratum 3 oven controlled crystal oscillator (OCXO) works as the eNodeB
master clock. The OCXO can keep the eNodeB working properly for up to 8 hours.
If the following conditions are met, the eNodeB can work normally for 24 hours with time
synchronization when the clock is in holdover mode:
The UMPT is used as the main control board.
The eNodeB synchronizes with the GPS/RGPS clock.
The clock has worked in locked mode for 24 hours or longer before the clock enters the
holdover mode.
In other cases, the eNodeB can work normally for 8 hours with time synchronization when
the clock is in holdover mode.
Enhancement
None
Dependencies
None
5.1.3 TDLBFD-00300503 Synchronization with GPS

Availability
Draft (2014-02-10)


Summary
The eNodeB can work in multiple clock synchronization modes to suit different clock
topologies. Global Positioning System (GPS) is one synchronization source.
Benefits
The eNodeB internal clock can be synchronized with the transmission network. No auxiliary
clock equipment is required, therefore reducing cost.
The synchronized clock meets both radio frequency and transmission network accuracy
requirements.
Description
In compliance with 3GPP specifications, the eNodeB clock must have a high precision if the
GPS clock is used as the clock source. The frequency stability and phase stability of the
10-MHz master clock in the eNodeB must be lower than 0.05 ppm and 1.5 s, respectively.
Clock signals are processed and synchronized as follows:
The GPS antenna system receives GPS signals at 1575.42 MHz and transmits the signals to the
GPS card. The system can simultaneously trace a maximum of eight (generally, three or four)
satellites. The GPS card processes the signals and transmits them to the main clock module.
To synchronize with the GPS, the eNodeB must receive signals from at least four satellites.
However, in some specific scenarios, the eNodeB can receive signals from only one to three
satellites. This is insufficient for GPS synchronization.
In eRAN3.0, single satellite synchronization is implemented to enhance this feature. If antenna
location information (latitude, longitude, and altitude) has been correctly configured on the
eNodeB, the eNodeB can implement GPS synchronization. The location information is very
important. Inaccurate location information affects synchronization precision.
Enhancement
None
Dependencies
The GPS antenna system is required.
5.1.4 TDLBFD-00300505 Synchronization with 1PPS+TOD

Availability
Summary
The eNodeB can work in multiple clock synchronization modes to suit different clock
topologies. 1PPS+TOD is one synchronization source.
Draft (2014-02-10)


Benefits
The eNodeB internal clock can be synchronized with the transmission network. No auxiliary
clock equipment is required, therefore reducing cost.
The synchronized clock meets both radio frequency and transmission network accuracy
requirements.
Description
In compliance with 3GPP specifications, the eNodeB clock must have a high precision. The
frequency stability and phase stability of the 10-MHz master clock in the eNodeB must be
lower than 0.05 ppm and 1.5 s, respectively.
Enhancement
None
Dependencies
eNodeBs must be equipped with universal satellite card and clock units (USCU).
Draft (2014-02-10)


6 Operation and Maintenance
Operation and Maintenance
6.1 TDLBFD-004001 Local Maintenance on the LMT

Availability
Summary
This feature allows local maintenance of eNodeBs.
Benefits
Engineers can locally maintain eNodeBs when the following conditions exist:
Centralized management on the M2000 is not available.
Transmission between the M2000 and eNodeB is not available.
Onsite operations are required to rectify faults.
Description
The local maintenance terminal (LMT) provides the following functions and tools:
MML command execution
eNodeB alarm query
Local eNodeB commissioning, such as software download and activation
Local eNodeB fault diagnosis
Real-time performance monitoring, such as sector performance monitoring, RRU

performance monitoring, and spectrum detection
Enhancement
Engineers can use LMT function by using a web browser.
Dependencies
A web browser must be installed when the web LMT is used.
Draft (2014-02-10)


6.2 TDLBFD-004002 Centralized M2000 Management

Availability
Summary
Huawei iManager M2000 provides fault, configuration, performance, security and software
management (FCPSS defined by 3GPP) functions to help operators administer NEs on a
sub-network.
Benefits
All LTE NEs can be directed at the management center, which effectively reduces OPEX.
Description
FCPSS involves centralized management of the following items:
Faults
Configurations
Performance
Security
Software
Enhancement
None
Dependencies
Huawei iManager M2000 is required.
6.3 TDLBFD-004003 Security Socket Layer

Availability
Summary
Secure Sockets Layer (SSL) exists between the TCP layer and the O&M application layer. SSL
ensures data transmission security between the eNodeB and Huawei iManager M2000.
Benefits
All remote operation and maintenance tasks are performed based on encrypted protocols.
Draft (2014-02-10)


Description
All O&M application data transmitted at the SSL is encrypted. FTP over SSL is also supported.
From eRAN3.0, this feature supports TLSv1.2. Transport Layer Security (TLS) and its
predecessor, SSL, are cryptographic protocols that provide communications security between
the eNodeBs and Huawei iManager M2000 at the transport layer. TLSv1.2, which maps to
SSLv3.3, is the latest version in the TLS series.
Enhancement
None
Dependencies
Related certifications are required.
6.4 TDLBFD-004004 Software Version Upgrade

Management
Availability
Summary
This feature provides efficient and correct installation and upgrade of software and version
management functions.
Benefits
eNodeB software is efficiently and correctly installed and upgraded.
eNodeB software versions can be effectively managed.
Description
This feature involves the following functions:
Automatic compatibility check on software and hardware versions

This function ensures a successful software installation and upgrade.
Automatic data conversion for the software upgrade

This function requires no manual configuration updates.
Software download and activation

Software download by configuration can reduce the software package size by 30% and
significantly shorten download time. When a board is added to an eNodeB, the eNodeB
automatically downloads the board software from Huawei iManager M2000 if the
Draft (2014-02-10)


software has not been previously downloaded. A maximum of 600 eNodeBs can be
selected to automatically download and activate the software in batches.
Resumable download
If the network recovers within one hour of a breakdown, the eNodeB can resume the
software download from the last disconnected download location.
Patch installation
Hot patch can be installed during a software upgrade on Huawei iManager M2000.
Version management, for example, hardware and software version query
A software upgrade process involves the following procedures:
Downloading the software package from Huawei iManager M2000 to the eNodeB
The download duration depends on the bandwidth of the OM link. The download does not
affect services.
Activating the software by running MML commands on Huawei iManager M2000 client
The eNodeB automatically loads the software to the target boards and activates the
software. To activate the software, the target boards must be reset. In this case, service on
the boards will be interrupted.
The two software upgrade procedures can be completed separately. For example, the software
package to eNodeBs can be downloaded during the day and the software can be activated at
midnight. The separate software upgrade procedures help reduce the risk of software upgrade
failures and network service interruption.
Enhancement
None
Dependencies
This feature requires Huawei iManager M2000.
6.5 TDLBFD-004005 Hot Patch Management

Availability
Summary
This feature provides hot patch management functions, such as installation, uninstall, and
rollback.
Benefits
Software defects can be repaired without interrupting ongoing services.
Draft (2014-02-10)


Description
A hot patch is used to repair software defects and does not interrupt ongoing services. Huawei
LTE TDD hot patch management involves the following functions:
Hot patch installation

There are two ways to install a hot patch package on the eNodeB:
Running only a single installation command: The patch is downloaded, loaded,

activated, and verified automatically.
Running separate commands in the steps of patch installation: Users have full control
over the installation procedure: download, load, activation and verification.
Hot patch rollback
Hot patch uninstall
Enhancement
None
Dependencies
This feature requires Huawei iManager M2000 or LMT.
6.6 TDLBFD-004006 Fault Management

Availability
Summary
This feature provides eNodeB fault management.
Benefits
With real-time alarm lists and alarm logs, operators can have a comprehensive view of the
network running status at any time.
Description
Fault management involves fault detection, fault handling, fault correlation, and fault reporting.
With these functions, operators can be informed as soon as the network fault occurs and take
proper actions to minimize or prevent service interruption.
Fault detection
Fault detection includes physical layer and link layer environment monitoring, KPI alarm
monitoring, and other fault detection. A small number of faults may have a negative
impact on services if a self-test (such as a RAM self-test or transport link loopback test) is
performed. Some of these faults are detected automatically in the board startup phase, and
some can be manually triggered by executing fault testing commands.
Draft (2014-02-10)


Fault detection methods are designed to minimize false alarms and intermittent alarms.
Fault handling
The eNodeB performs fault isolation and automatic recovery to minimize service impacts.
Fault correlation
Fault management supports a run-time fault correlation handling mechanism so that
operators can be notified of the most important alarms (the root cause and traffic impacts)
rather than all related alarms when a fault occurs. The number of alarms greatly decreases,
which makes it easier for operators to locate and solve network problems. This mechanism
is predefined and embedded in the NEs, and operators can customize alarm correlation
handling rules on Huawei iManager M2000.
Fault reporting
Faults are reported to users in the form of alarms. With the alarm correlation function, the
report contains the correlation between alarms. If a correlative alarm is reported, users can
right-click the correlative alarm to check the root alarm.
The operators can browse real-time alarm information, query historical alarm information, and
save alarm information. The online help provides detailed troubleshooting methods.
Huawei LTE TDD eRAN2.0 supports KPI alarm detection.
When an RRU uses AC power in Huawei LTE TDD eRAN2.2, the RRU can detect AC power
failure and send warning signals to the eNodeB.
Enhancement
None
Dependencies
6.7 TDLBFD-004007 Configuration Management

Availability
Summary
This feature provides online and offline configuration functions, which support quick
installation, expansion, and configuration of the network.
Benefits
This feature allows operators to learn about network running status.
Description
Configuration management allows operators to collect and manage NE configurations,
including physical configurations (such as equipment) and logical configurations (such as cells
Draft (2014-02-10)


and links). Huawei iManager M2000 provides a graphical user interface (GUI) to implement
configuration management.
To minimize the impact of configuration modifications on the system, configuration
management has the following characteristics:
Physical configuration modifications are independent of the related logical configuration

modifications.
All required modifications are completely checked to ensure their validity before the
modifications take effect on eNodeBs.
Configuration data consistency between the NEs and Huawei iManager M2000 are always
verified.
Both offline and online configurations are supported.
Offline configuration
Configuration Management Express (CME) is a graphical configuration tool. In addition
to general configuration functions, it provides configuration templates to ease site
deployment, and provides GUI wizards for capacity expansion and migration.
Online configuration
You can run MML commands on Huawei iManager M2000 to perform the following
operations:
Configuration data query and modification
Capacity expansion
Migration
Enhancement
None
Dependencies
This feature requires Huawei iManager M2000, LMT, or CME.
6.8 TDLBFD-004008 Performance Management

Availability
Summary
Various performance measurement counters are used to monitor network performance.
Real-time KPI monitoring is an enhanced feature to help users quickly locate performance
problems.
Draft (2014-02-10)


Benefits
This feature improves the efficiency of network performance monitoring. Operators learn
detailed information about network performance, which facilitates troubleshooting and
network optimization.
Description
Performance measurement administration

This function allows operators to manage performance measurement tasks.
For newly-deployed eNodeBs, the created tasks for performance measurement will start
after the initial startup phase. The performance measurements can be suspended and
resumed manually.
Machine-machine interfaces are available between eNodeBs and Huawei iManager
M2000 to collect necessary statistics and to configure performance measurement tasks
(including the performance counter involved in the tasks and the measurement period).
Huawei iManager M2000 provides performance measurement results in binary format in
every measurement period. The results are also stored as backup files on eNodeBs for up
to 72 hours. When data transfer fails, Huawei iManager M2000 uses these files to recollect
data.
Performance measurement counters

Performance measurement counters include key counters and other counters. The key
counters are used to generate key performance indicators (KPIs) of the network, which are
defined on Huawei iManager M2000. Key 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 Huawei iManager M2000. Other counters for monitoring the
additional aspects of network performance can be started when necessary.
Real-time KPI monitoring

This function facilitates troubleshooting, drive tests, and network optimization. The
shortest sampling interval is 10 seconds.
Enhancement
None
Dependencies
6.9 TDLBFD-004009 Real-time Monitoring of System

Running Information
Availability
Draft (2014-02-10)


Summary
This feature provides running status monitoring of the equipment, RF system, cells, subscribers,
and transmission links.
Benefits
This feature facilitates troubleshooting, drive tests, and network optimization.
Description
This feature provides real-time monitoring and graphical representation of system running
status and quality. The monitoring results help operators to diagnose faults.
The following monitoring items are supported:
Equipment running status: involves the clock source quality.
UE running status: involves the signal-to-interference ratio (SIR) measurement and UE

transmit (TX) power.
Cell running status: involves the number of users, throughput, and resource block usage in
a cell.
Transport link running status: involves SCTP links and IP paths.
RF system: involves RF performance and RF interference detection.
Enhancement
None
Dependencies
None
6.10 TDLBFD-004010 Security Management

Availability
Summary
This feature provides user authorization, system data backup and restoration, security log
auditing, and security-related alarm functions.
Benefits
This feature enhances network security.
Description
Security management involves the following functions:
Draft (2014-02-10)


User management
This function allows user account and permission settings, so that the related authorized
groups and operators can be managed.
System data backup and restoration
Operation log collection and security log auditing
Security alarm reporting

For example, an alarm is reported when network attacks are detected or the number of
unauthorized sessions exceeds a specific threshold.
Enhancement
None
Dependencies
6.11 TDLBFD-004011 Optimized eNodeB Commissioning

Solution
Availability
Summary
This feature enables USB-based commissioning on eNodeBs and allows eNodeBs to
automatically download the software and configuration data from Huawei iManager M2000. (1)
The security of the USB port is ensured by encryption. (2) When the USB port functions as a
commissioning Ethernet port, it ensures that an OM port has been opened and the user has
obtained required authorities for accessing the base station through the OM port.
Benefits
This feature simplifies the eNodeB commissioning procedure.
Description
This feature simplifies the on-site commissioning procedure with the following aspects:
If Huawei iManager M2000 has the eNodeB software and configuration, a local
commissioning engineer needs to only install boards in the eNodeB and power on the
eNodeB.
After the eNodeB starts:
Draft (2014-02-10)
If the eNodeB is connected to the GPS, the eNodeB automatically reports the location
to Huawei iManager M2000. Then, Huawei iManager M2000 automatically delivers
correct configuration data to the eNodeB.
10

If a notebook computer is available, the local commissioning engineer can use the
computer to log in to Huawei iManager M2000 and enter the eNodeB ID. Then,
Huawei iManager M2000 automatically delivers correct configuration data to the
eNodeB.
The local commissioning engineer can report the electronic serial number (ESN) of the
eNodeB to the administration center.
As part of the procedure, the newly-deployed eNodeB automatically sets up a connection

to Huawei iManager M2000 by using the DHCP, downloads software and configuration
data from Huawei iManager M2000, and installs the software.
USB commissioning is supported. The associated eNodeB software and data must be
copied to a USB disk at the administration center. A local commissioning engineer needs
to only obtain the USB disk, install the hardware, and connect the USB disk to the USB
port on the eNodeB. After that, the eNodeB automatically installs the software and loads
data, starts up, and sets up the connection to Huawei iManager M2000. No further local
configuration is required.
Enhancement
None
Dependencies
This feature requires Huawei iManager M2000. USB commissioning requires USB disks.
6.12 TDLBFD-004012 Environment Monitoring

Availability
Summary
Environment monitoring is implemented by using environment fault alarms and customized
environment alarms.
Benefits
This feature allows operators to perform centralized environment monitoring of eNodeBs.
Description
Operators can perform centralized environment monitoring of eNodeBs in terms of temperature,
humidity, smoke, water immersion, access control, and power supply. In addition, eNodeBs can
be connected to third-party analog and digital sensors, which allow operators to customize
environment alarms.
Enhancement
None
Draft (2014-02-10)

11

Dependencies
6.13 TDLBFD-004013 Inventory Management

Availability
Summary
Huawei iManager M2000 obtains inventory information automatically from eNodeBs after
commissioning and synchronizing with eNodeBs on a daily basis.
Benefits
Operators can obtain real-time and accurate inventory information about the network.
Description
Inventory management helps operators to manage network asset information on Huawei
iManager M2000. The information includes physical objects (such as cabinets, subracks, slots,
boards, ports, and fans) and logical objects (such as software and patches).
When requested from Huawei iManager M2000, an asset information file in .xml format is
generated and sent to Huawei iManager M2000. Huawei iManager M2000 stores the
information in the network inventory database.
Enhancement
None
Dependencies
6.14 TDLBFD-004014 License Management

Availability
Summary
This feature involves eNodeB license control.
Draft (2014-02-10)

12

Benefits
With this feature, the operators can purchase the license required for network development,
therefore reducing initial cost.
Description
A license file is used to determine whether 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 license control items in the license file on the LMT or the M2000 client.
The license file is stored on the eNodeB.
New or upgraded licenses can be ordered from Huawei.
Enhancement
None
Dependencies
None
6.15 TDLBFD-004015 License Control for Urgency

Availability
Summary
With this feature, the license limitation is removed in emergencies to temporarily increase RAN
resources for eNodeBs.
Benefits
This feature prevents permanent over-dimensioning and adapts capacity costs to the actual
usage when traffic suddenly increases.
Draft (2014-02-10)

13

Description
The license limitation can be removed by running MML commands on the LMT or M2000.
Then, eNodeBs can operate at optimum capacity.
For each R version, operators have three opportunities to remove the license limitation by
running MML commands. The removal takes effect immediately after the commands are
executed. The validity period is seven days. When the three opportunities are exhausted, a new
opportunity can be obtained only after a software upgrade.
Enhancement
None
Dependencies
None
Draft (2014-02-10)

14

Acronyms and Abbreviations
Numerics
1xCS IWS
Circuit Switched Fallback Interworking Solution Function

for 3GPP2 1xCS
3GPP
3rd Generation Partnership Project
Draft (2014-02-10)
ACK
acknowledgment
ACL
access control list
AES
advanced encryption standard
AFC
automatic frequency control
AH
authentication header
AMBR
aggregate maximum bit rate
AMC
adaptive modulation and coding
AMR
adaptive multi-rate
ANR
automatic neighbor relation
ARP
allocation/retention priority
ARQ
automatic repeat request

15

B
BBU
baseband unit
BCCH
broadcast control channel
BCH
broadcast channel
BE
best effort
BLER
block error rate
Draft (2014-02-10)
CAPEX
capital expenditure
CCCH
common control channel
CCO
cell change order
CCU
cell center user
CDMA2000
Code Division Multiple Access 2000
CDMA2000 1xRTT
CDMA2000 1x radio transmission technology
CEU
cell edge user
CGI
cell global identification
C/I
carrier-to-interference power ratio
CME
Configuration Management Express
CP
cyclic prefix
CPICH
common pilot channel
CPRI
common public radio interface
CPU
central processing unit

16

CQI
channel quality indicator
CRC
cyclic redundancy check
CPU
central processing unit
CS
circuit switched
D
DCCH
dedicated control channel
DES
data encryption standard
DHCP
Dynamic Host Configuration Protocol
DiffServ
Differentiated Services
DL-SCH
downlink shared channel
DRB
data radio bearer
DRX
discontinuous reception
DSCP
differentiated services code point
DTCH
dedicated traffic channel
Draft (2014-02-10)
ECM
EPS control management
EDF
early deadline first
EDGE
Enhanced Data rates for GSM Evolution
EF
expedited forwarding
eHRPD
evolved high rate packet data
EMM
EPS mobility management

17

EMS
element management system
eNodeB
E-UTRAN NodeB
EPC
evolved packet core
EPS
evolved packet system
E-RAB
E-UTRAN radio access bearer
ESP
Encapsulation Security Payload
ETWS
Earthquake and Tsunami Warning System
E-UTRAN
evolved universal terrestrial radio access network
F
FCPSS
fault, configuration, performance, security and software

management
FDD
frequency division duplex
FEC
forward error correction
FTP
File Transfer Protocol
G
GBR
guaranteed bit rate
GERAN
GSM/EDGE radio access network
GPS
Global Positioning System
GSM
Global System for Mobile Communications
GUL
GSM/UMTS/LTE
H
Draft (2014-02-10)

18

HARQ
hybrid automatic repeat request
HII
high interference indication
HMAC
hash-based message authentication code
HMAC_MD5
HMAC message digest 5
HMAC_SHA
HMAC secure hash algorithm
HO
handover
HRPD
high rate packet data
HSPA
High Speed Packet Access
HSS
home subscriber server
I
ICIC
inter-cell interference coordination
IKEv
Internet Key Exchange version
IMS
IP multimedia service
IPPM
IP performance monitoring
Ipsec
IP security
IRC
interference rejection combining
IV
initial vector
K
KPI
key performance indicator
Draft (2014-02-10)

19

LAI
location area identity
LMT
local maintenance terminal
LTE
Long Term Evolution
M
M2000
Huawei OMC
MAC
Media Access Control
MCH
multicast channel
MCCH
multicast control channel
MCS
modulation and coding scheme
MGW
media gateway
MIB
master information block
MinBR
minimum bit rate
MIMO
multiple-input multiple-output
MME
mobility management entity
MML
man-machine language
MOS
mean opinion score
MRC
maximum ratio combining
MTCH
multicast traffic channel
MU-MIMO
multi-user MIMO
N
NACC
Draft (2014-02-10)
network assisted cell changed

20

NACK
negative acknowledgment
NAS
non-access stratum
NE
network element
NMS
network management system
NRT
neighboring relation table
O
OCXO
oven controlled crystal oscillator
OFDM
orthogonal frequency division multiplexing
OFDMA
orthogonal frequency division multiple access
OI
overload indicator
OMC
operation and maintenance center
OOK
on-off-keying
OPEX
operating expense
Draft (2014-02-10)
PBCH
physical broadcast channel
PCCH
paging control channel
PCFICH
physical control format indicator channel
PCH
paging channel
PCI
physical cell identifier
PDB
packet delay budget
PDCCH
physical downlink control channel

21

PDCP
Packet Data Convergence Protocol
PDH
plesiochronous digital hierarchy
PDN
packet data network
PDSCH
physical downlink shared channel
PF
proportional fair
P-GW
PDN gateway
PHB
per-hop behavior
PHICH
physical HARQ indicator channel
PLMN
public land mobile network
PM
performance measurement
PMCH
physical multicast channel
PRACH
physical random access channel
PS
packet switched
PUCCH
physical uplink control channel
PUSCH
physical uplink shared channel
Q
QAM
quadrature amplitude modulation
QCI
QoS class identifier
QoS
quality of service
QPSK
quadrature phase shift keying
Draft (2014-02-10)

22

Draft (2014-02-10)
RA
random access
RACH
random access channel
RAM
random access memory
RAN
radio access network
RAT
radio access technology
RB
resource block
RCU
radio control unit
RET
remote electrical tilt
RF
radio frequency
RIM
RAN information management
RLC
Radio Link Control
RNC
radio network controller
RRC
radio resource control
RRM
radio resource management
RRU
remote radio unit
RS
reference signal
RSRP
reference signal received power
RSRQ
reference signal received quality
RSSI
received signal strength indicator
RTT
round trip time
RV
redundancy version
RX
receive

23

S
S1
interface between the 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
SDMA
space division multiple access
SeGW
security gateway
SFBC
space frequency block coding
SFN
single frequency network
SFP
small form-factor pluggable
S-GW
serving gateway
SIB
system information block
SID
silence indicator
SINR
signal to interference plus noise ratio
SPID
subscriber profile ID
SRB
signaling radio bearer
SRS
sounding reference signal
SSL
Secure Sockets Layer
STBC
space time block coding
STMA
smart tower-mounted amplifier
Draft (2014-02-10)

24

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
transmit
U
UE
user equipment
UL-SCH
uplink shared channel
UMTS
Universal Mobile Telecommunications System
USB
Universal Serial Bus
UTRAN
universal terrestrial radio access network
V
VLAN
virtual local area network
VoIP
voice over IP
W
WRR
Draft (2014-02-10)
weighted round robin

25

X
X2
Draft (2014-02-10)
interface between eNodeBs

26

ELTE2.3 DBS3900 LTE TDD Basic Feature Description

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

ELTE2.3 DBS3900 LTE TDD Basic Feature Description

Cargado por

Copyright:

Formatos disponibles

eLTE2.

3 DBS3900 LTE TDD

Basic Feature Description

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential