LTE eRAN1.1 Feature Description V2.1(20091110).pdf

7/27/2019 LTE eRAN1.1 Feature Description V2.1(20091110).pdf

1/134

LTE eRAN1.1

Feature Description

Issue V2.1

Date 2009-09-09

HUAWEI TECHNOLOGIES CO., LTD.


2/134

Feature Description of Huawei LTE eRAN1.1

HUAWEI CONFIDENTIAL i

Copyright Huawei Technologies Co., Ltd. 2009. 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 the warranty of any kind,

express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]
http://www.huawei.com/mailto:[email protected]:[email protected]://www.huawei.com/


3/134


HUAWEI CONFIDENTIAL i

Contents

1.1 LBFD-001001 3GPP R8 Specifications (2009-03)............................................................... 11.2 LBFD-001002 FDD mode ................................................................................................. 21.3 LBFD-001003 Scalable Bandwidth................................................................................... 21.4 LBFD-001004 CP length ................................................................................................... 31.4.1 LBFD-00100401 Normal CP ........................................................................................... 31.5 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM .......................... 41.6 LBFD-001006 AMC .......................................................................................................... 51.7 LBFD-002001 Logical Channel Management ................................................................... 61.8 LBFD-002002 Transport Channel Management ............................................................... 81.9 LBFD-002003 Physical Channel Management ............................................................... 101.10 LBFD-002004 Integrity Protection ................................................................................ 111.11 LBFD-002005 DL Asynchronization HARQ................................................................. 121.12 LBFD-002006 UL Synchronization HARQ ................................................................... 131.13 LBFD-002007 RRC Connection Management .............................................................. 141.14 LBFD-002008 Radio Bearer Management..................................................................... 151.15 LBFD-002009 Broadcast of System Information........................................................... 161.16 LBFD-002010 Random Access Procedure ..................................................................... 181.17 LBFD-002011 Paging.................................................................................................... 191.18 LBFD-002012 Cell Access Radius up to 15km .............................................................. 201.19 LBFD-002023 Admission Control................................................................................. 211.20 LBFD-002024 Congestion Control ................................................................................ 221.21 LBFD-002025 Basic Scheduling.................................................................................... 231.22 LBFD-002026 Uplink Power Control............................................................................ 24


4/134


HUAWEI CONFIDENTIAL ii

1.23 LBFD-002016 Dynamic Downlink Power Allocation................................................... 261.24 LBFD-002017 DRX ....................................................................................................... 271.25 LBFD-002018 Mobility Management ........................................................................... 291.25.1 LBFD-00201801 Coverage Based Intra-frequency Handover ..................................... 291.25.2 LBFD-00201802 Coverage Based Inter-frequency Handover ..................................... 301.25.3 LBFD-00201803 Cell Selection and Reselection......................................................... 311.26 LBFD-002022 Static Inter-Cell Interference Coordination ........................................... 321.26.1 LBFD-00202201 Downlink Static Inter-Cell Interference Coordination.................... 321.26.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination......................... 331.27 LBFD-002020 Antenna Configuration.......................................................................... 341.27.1 LBFD-00202001 UL 2-Antenna Receive Diversity ..................................................... 341.28 LBFD-002021 Reliability .............................................................................................. 351.28.1 LBFD-00202102 Cell Rebuild between Baseband Processing Units .......................... 351.28.2 LBFD-00202103 SCTP Multi-homing........................................................................ 371.29 LBFD-002027 Support of UE Category 1 ...................................................................... 381.30 LBFD-003001 Transport Networking........................................................................... 391.30.1 LBFD-00300101 Star Topology .................................................................................. 391.30.2 LBFD-00300102 Chain Topology ............................................................................... 401.30.3 LBFD-00300103 Tree Topology.................................................................................. 411.31 LBFD-003002 Basic QoS Management ......................................................................... 431.31.1 LBFD-00300201 DiffServ QoS Support ..................................................................... 431.32 LBFD-003003 VLAN Support (IEEE 802.1p/q).............................................................. 441.33 LBFD-003004 Compression and Multiplexing over E1/T1 ........................................... 451.33.1 LBFD-00300401 IP Header Compression................................................................... 451.33.2 LBFD-00300402 PPP MUX ......................................................................................... 461.33.3 LBFD-00300403 ML/MC-PPP..................................................................................... 461.34 LBFD-003005 Synchronization..................................................................................... 481.34.1 LBFD-00300501 Clock Source Switching Manually or Automatically....................... 481.34.2 LBFD-00300502 Free-running Mode.......................................................................... 49


5/134


HUAWEI CONFIDENTIAL iii

1.34.3 LBFD-00300503 Synchronization with GPS .............................................................. 491.34.4 LBFD-00300505 Synchronization with 1PPS ............................................................. 501.34.5 LBFD-00300506 Synchronization with E1/T1 ............................................................ 511.35 LBFD-004001 Local Maintenance on the LMT ............................................................. 511.36 LBFD-004002 Centralized M2000 Management ........................................................... 521.37 LBFD-004003 Security Socket Layer............................................................................. 531.38 LBFD-004004 Software Version Upgrade Management............................................... 541.39 LBFD-004005 Hot Patch Management.......................................................................... 551.40 LBFD-004006 Fault Management ................................................................................. 561.41 LBFD-004007 Configuration Management................................................................... 571.42 LBFD-004008 Performance Management ..................................................................... 581.43 LBFD-004009 Real-time Monitoring of System Running Information ........................ 601.44 LBFD-004010 Security Management ............................................................................ 611.45 LBFD-004011 Optimized eNodeB Commissioning Solution ....................................... 611.46 LBFD-004012 Environment Monitoring....................................................................... 621.47 LBFD-004013 Inventory Management.......................................................................... 632.1 LOFD-001001 DL 2x2 MIMO ......................................................................................... 652.2 LOFD-001002 UL 2x2 MU-MIMO .................................................................................. 662.3 LOFD-001003 DL 4x2 MIMO ......................................................................................... 672.4 LOFD-001005 UL 4-Antenna Receive Diversity............................................................. 682.5 LOFD-001006 UL 64QAM .............................................................................................. 692.6 LOFD-001007 High Speed Mobility .............................................................................. 702.7 LOFD-001008 Ultra High Speed Mobility ..................................................................... 702.8 LOFD-001009 Extended Cell Access Radius .................................................................. 712.9 LOFD-001010 Security Mechanism................................................................................ 722.9.1 LOFD-00101001 Encryption: AES................................................................................ 722.9.2 LOFD-00101002 Encryption: SNOW 3G...................................................................... 732.10 LOFD-001012 UL Interference Rejection Combining.................................................. 742.11 LOFD-001014 Dynamic Inter-Cell Interference Coordination ..................................... 75


6/134


HUAWEI CONFIDENTIAL iv

2.11.1 LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination ............. 752.11.2 LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination................... 762.12 LOFD-001015 Enhanced Scheduling............................................................................ 772.12.1 LOFD-00101501 CQI Adjustment.............................................................................. 772.12.2 LOFD-00101502 Dynamic Scheduling....................................................................... 782.13 LOFD-001016 VoIP Semi-persistent Scheduling ....................................................... 792.14 LOFD-001017 RObust Header Compression (ROHC) ................................................. 812.15 LOFD-001018 S1-flex.................................................................................................... 822.16 LOFD-001019 PS Inter-RAT Mobility between LTE and UMTS ................................. 842.17 LOFD-001020 PS Inter-RAT Mobility between LTE and GERAN ............................... 852.18 LOFD-001021 PS Inter-RAT Mobility between LTE and CDMA2000 ......................... 862.19 LOFD-001022 SRVCC to UMTS................................................................................... 882.20 LOFD-001023 SRVCC to GERAN ................................................................................ 892.21 LOFD-001024 Remote Electrical Tilt Control ............................................................... 912.22 LOFD-001025 Adaptive Power Consumption .............................................................. 922.23 LOFD-001041 Power Consumption Monitoring.......................................................... 932.24 LOFD-002001 ANR ...................................................................................................... 942.25 LOFD-002004 Self-configuration ................................................................................. 962.26 LOFD-002007 PCI Collision Detection ........................................................................ 982.27 LOFD-003002 2G/3G and LTE Co-transmission........................................................... 992.28 LOFD-003004 Ethernet OAM ..................................................................................... 1002.28.1 LOFD-00300401 Ethernet OAM(802.3ah)................................................................. 1002.28.2 LOFD-00300402 Ethernet OAM(802.1ag) ................................................................. 1012.29 LOFD-003007 Bidirectional Forwarding Detection.................................................... 1022.30 LOFD-003005 OM Channel Backup........................................................................... 1032.31 LOFD-003006 IP Route Backup .................................................................................. 1042.32 LOFD-003008 Ethernet Link Aggregation (802.3ad)................................................... 1052.33 LOFD-003009 IPSEC .................................................................................................. 1062.34 LOFD-003010 PKI ...................................................................................................... 107


7/134


HUAWEI CONFIDENTIAL v

2.35 LOFD-003014 Integrated Firewall .............................................................................. 1082.35.1 LOFD-00301401 ACL ............................................................................................... 1082.36 LOFD-003011 Enhanced Transport QoS Management .............................................. 1092.36.1 LOFD-00301101 Transport Overbooking................................................................ 1092.36.2 LOFD-00301102 Transport Differentiated Flow Control ......................................... 1102.36.3 LOFD-00301103 Transport Resource Overload Control .......................................... 1112.37 LOFD-003012 IP Performance Monitoring................................................................. 1122.37.1 LOFD-00301201 IP Performance Monitoring........................................................... 1122.37.2 LOFD-00301202 Transport Dynamic Flow Control ................................................. 1132.38 LOFD-003013 Enhanced Synchronization.................................................................. 1142.38.1 LOFD-00301301 Synchronization with Ethernet (ITU-T G.8261)............................. 1142.38.2 LOFD-00301302 IEEE1588 V2 Clock Synchronization............................................. 1152.38.3 LOFD-00301303 Clock over IP (Huawei Proprietary) .............................................. 117


8/134


HUAWEI CONFIDENTIAL vi

Figures

Figure 1-1 Mapping between uplink logical channels and uplink transport channels ..................7

Figure 1-2 Mapping between downlink logical channels and downlink transport channels ........8

Figure 1-3 Mapping between uplink transport channels and uplink physical channels................ 9

Figure 1-4 Mapping between downlink transport channels and downlink physical channels....10

Figure 1-5 DRX cycle......................................................... ........................................................... .. 28

Figure 1-6 3*10M 2T2R..................................................... ........................................................... .. 37

Figure 1-7 3*20M 2T2R..................................................... ........................................................... .. 37

Figure 1-8 Stream Control Transmission Protocol .................................................. ...................... 38

Figure 1-9 Star topology..................................................... ........................................................... .. 41

Figure 1-10 Chain topology ......................................................... ................................................... 42

Figure 1-11 Tree topology ............................................................ ................................................... 43

Figure 1-12 ML/MC-PPP................................................... ........................................................... .. 48

Figure 2-1 connection topology between MME Pool and eNodeBs ............................................ 85

Figure 2-2 SRVCC from E-UTRAN to UTRAN..................................................... ...................... 91

Figure 2-3 SRVCC from E-UTRAN to GERAN..................................................... ...................... 92

Figure 2-4 Automatic neighboring relation function ..................................................... ................ 96

Figure 2-5 general network topology .................................................... ......................................... 99

Figure 2-6 2G/3G and LTE co-transmission .................................................. .............................. 101Figure 2-7 the one-hop and multi-hop BFD application scenarios............................................. 105

Figure 2-8 the Ethernet link aggregation........................................................ .............................. 107

Figure 2-9 IPsec ........................................................ ........................................................... .......... 108

Figure 2-10 eRAN certificate application scenario ........................................................... .......... 110

Figure 2-11 Basic principle of the Synchronization with Ethernet............................................. 116

Figure 2-12 basic principle defined by the IEEE1588 protocol ................................................ 117

Figure 2-13 synchronization principle of the IEEE1588 protocol............................................. 118

Figure 2-14 Framework of Huawei proprietary protocol.................................................. .......... 119


9/134


HUAWEI CONFIDENTIAL Page 1 of134

Tables

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

Table 1-2 Relationship between QCI and DSCP ..................................................... ...................... 44

Table 2-1 Preamble formats and cell access radius.................................................. ...................... 74

Table 2-2 ROHC profile identifier and header compression protocol.......................................... 84


10/134



1 Basic Features Description1.1 LBFD-001001 3GPP R8 Specifications (2009-03)

Availability

This feature is available from eRAN1.0.

Summary

Huawei LTE eRAN1.1 is based on 3GPP Release 8 specifications (2009-03).

Benefits

None

Description

Huawei LTE eRAN1.1 is compliant with 3GPP Release 8 specifications (2009-03).

Huawei is an active participant in the specification development in 3GPP and makes

great contributions. This high-level involvement enables Huawei to activelycontribute to and closely follow the 3GPP development during Huawei product

development. LTE eRAN1.1 is based on 3GPP Release 8 in March 2009, which isthe latest version of the LTE standard.

Enhancement

None

Dependency

None


11/134



1.2 LBFD-001002 FDD mode

AvailabilityThis feature is available from eRAN1.0.

Summary

Huawei LTE eRAN1.1 supports the Frequency Division Duplex (FDD) mode .

Benefits

None

Description

The 3GPP specifications support the FDD mode. In FDD mode, separate frequency

bands are used for the uplink and the downlink.

Enhancement

None

Dependency

The related network elements (NEs) should support FDD mode .

1.3 LBFD-001003 Scalable Bandwidth

Availability


Summary

Huawei LTE eRAN1.1 supports the bandwidths of 5 MHz, 10 MHz, 15 MHz, and

20 MHz.

Benefitsz Larger bandwidth produces higher throughput and better user experience.

z Flexible bandwidth configuration helps operators use frequency bands.

Description

Huawei LTE eRAN1.1 supports the channel bandwidths 5 MHz, 10 MHz, 15 MHz,

and 20 MHz. The bandwidth can be configured by the software.


12/134



Enhancement

None

Dependency

UEs should support the same bandwidth as the eNodeB.

1.4 LBFD-001004 CP length

1.4.1 LBFD-00100401 Normal CP

AvailabilityThis feature is available from eRAN1.0.

Summary

In an OFDM symbol, the Cyclic Prefix (CP) is a time-domain replication of the end

of the symbol and is appended to the beginning of the symbol. It provides the guard

interval in the OFDM to decrease the inter-symbol interference due to the multipathdelay.

Benefits

The CP is used to decrease the inter-symbol interference due to the multipath delay.

Description

The CP is the guard interval used in the OFDM to decrease the interference due tothe multipath delay.

There are two CP lengths defined in 3GPP specifications: normal CP and extended

CP.

In the case of 15 kHz subcarrier spacing, the normal CP corresponds to seven OFDM

symbols per slot in the downlink and seven SC-FDMA symbols per slot in the uplink.

The normal CP length (time) is calculated as follows:z In the downlink

Normal CP: TCP = 160 x Ts (OFDM symbol #0), TCP = 144 x Ts (OFDM symbol #1

to #6)

z In the uplink

NormalCP: 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


13/134



Enhancement

None

Dependency

UEs should support the same CP length as the eNodeB.

1.5 LBFD-001005 Modulation: DL/UL QPSK, DL/UL16QAM, DL 64QAM

Availability


Summary

This feature shows the different modulation schemes supported by the UE andeNodeB.

Benefits

This feature provides a wide range of modulation schemes to be chosen based on the

channel condition. Higher-order modulation schemes, such as DL 64QAM, can be

used under excellent channel conditions to achieve higher data rates, whichimproves the system throughput and spectral efficiency.

Description

This feature provides a wide range of modulation schemes that can be used by both

the eNodeB and the UE in uplink and downlink.

The following modulation schemes are supported:

z Uplink/downlink Quadrature Phase Shift Keying (QPSK)

z Uplink/downlink 16 Quadrature Amplitude Modulation (16QAM)

z

Downlink 64QAM

The characteristics are as follows:

z QPSK allows up to two information bits modulated per symbol due to fourneighboring alternatives.

z 16QAM allows up to four information bits modulated per symbol due to 16different neighboring alternatives.

z 64QAM allows up to six information bits modulated per symbol due to 64different neighboring alternatives.

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.


14/134



A more favorable channel condition is required to support a higher-order modulationscheme.

For example, when a UE is in a poor radio environment, it may use a low-order

QPSK modulation scheme for uplink transmission to meet the requirement of thecall quality. When a UE is in an excellent radio environment, it can use a high-order

QAM modulation (such as 16QAM) scheme for uplink transmission to achieve highbit rates.

Enhancement

None

Dependency

This feature relies on the support from both the eNodeB and UEs. For example, if an

eNodeB supports 64QAM in the downlink but a UE does not support the scheme,then the eNodeB cannot use 64QAM for downlink transmission to the UE.

1.6 LBFD-001006 AMC

Availability


SummaryThe Adaptive Modulation and Coding (AMC) function allows an eNodeB or a UE to

adaptively select the optimal Modulation and Coding Scheme (MCS) according tothe channel condition. This improves the spectral efficiency after the systemresource and transmit power are fixed. Therefore, the throughput can be maximized

and the Quality of Service (QoS) requirements can be met.

Benefits

The AMC provides the following benefits:

z Maximizes the system throughput by selecting the optimal MCS.

z Meets the QoS requirement (such as the packet loss rate) by selecting theoptimal MCS to achieve the best tradeoff between data rate and block error rate.

Description

The AMC function allows an eNodeB or a UE to adaptively select the optimal MCS

according to the channel information. This improves the spectrum efficiency afterthe system resource and transmitting power are fixed. Therefore, the throughput canbe maximized and the QoS requirements can be met.

In the uplink, the initial MCS can be selected on the basis of the Signal toInterference plus Noise Ratio (SINR) of the uplink Reference Signal (RS) measured

by the eNodeB. Then, the MCS may be adjusted according to the received uplink


15/134



Sounding Reference Signal (SRS). It can also be adjusted on the basis of whether theuplink transmission involves control signals. Note that control signals might require

a lower-order MCS for ensuring a reliable transmission. The power headroom of

UEs should also be considered for MCS optimization. To reduce the interference toneighboring cells, the AMC solution also considers the input from uplink Inter-cellInterference Coordination (ICIC) if uplink Inter-cell Interference Coordination

function is enabled and uplink power control.

In the downlink, the eNodeB first selects the MCS for each UE based on the CQIreported from the UE and assigned power for the UE. Then, the eNodeB can adjust

the MCS based on the load of traffic sent to the UE and the remaining resources suchas the available resource blocks and transmit power, in order to maximize the usageof the radio resources.

Enhancement

None

Dependency

None

1.7 LBFD-002001 Logical Channel Management

Availability


Summary

The logical channels are provided between the Medium Access Control (MAC)

layer and the Radio Link Control (RLC) layer. Each logical channel type is definedaccording to the type of the transmitted data. They are generally classified into two

types: control channels and traffic channels.

In Huawei LTE eRAN1.1, all logical channels are supported except those related tothe evolved Multimedia Broadcast Multicast Service (eMBMS) functionality.

Benefits

The logical channels are responsible for what type of information is transferred.

Description

The logical channels are provided between the MAC layer and the RLC layer. They

are responsible for what is transported. They are generally classified into twotypes:

z Control channels: for transmitting the control plane information

z Traffic channels: for transmitting the user plane information


16/134



Control channels include:

z Broadcast Control Channel (BCCH)

z

Paging Control Channel (PCCH)z Common Control Channel (CCCH)

z Multicast Control Channel (MCCH)

z Dedicated Control Channel (DCCH)

Traffic channels include:

z Dedicated Traffic Channel (DTCH)

z Multicast Traffic Channel (MTCH)

The mapping between logical channels and transport channels is as follows:

I. In the uplink,

z CCCH can be mapped to UL-SCH.

z DCCH can be mapped to UL-SCH.

z DTCH can be mapped to UL-SCH.

Figure 1-1 depicts the mapping between uplink logical channels and uplink transportchannels:

Figure 1-1Mapping between uplink logical channels and uplink transport channels

CCCH DCCH DTCH

UL-SCHRACH

Uplink

Logical channels

Uplink

Transport channels

II. In the downlinkz BCCH can be mapped to BCH.

z BCCH can be mapped to DL-SCH.

z PCCH can be mapped to PCH.

z CCCH can be mapped to DL-SCH.

z DCCH can be mapped to DL-SCH.

z DTCH can be mapped to DL-SCH.

z MTCH can be mapped to DL-SCH.

z MTCH can be mapped to MCH.

z

MCCH can be mapped to DL-SCH.


17/134



z MCCH can be mapped to MCH.

Figure 1-2 depicts the mapping between downlink logical channels and downlink

transport channels:

Figure 1-2Mapping between downlink logical channels and downlink transportchannels

In Huawei LTE eRAN1.1, all logical channels are supported except those related to

the eMBMS functionality, such as MCCH and MTCH.

Enhancement

None

Dependency

None

1.8 LBFD-002002 Transport Channel Management

Availability


Summary

Transport channels that are provided between the MAC layer and the physical layer,

are defined according to the type of transmitted data and the method of datatransmission over the radio interface. They are used to offer the information about

transmission services for the MAC and higher layers. In Huawei LTE eRAN1.1, alltransport channels except those related to the eMBMS functionality are supported.

Benefits

The transport channels are responsible for what type of data is transmitted and how

the data is transmitted.


18/134



Description

The transport channels are provided between the MAC layer and the physical layer.

They are responsible for what type of data is transmitted and how the data istransmitted over the radio interface.

Downlink transport channels are classified into the following types:

z Broadcast Channel (BCH)

z Downlink Shared Channel (DL-SCH)

z Paging Channel (PCH)

z Multicast Channel (MCH)

Uplink transport channels are classified into the following types:

z Uplink Shared Channel (UL-SCH)

z Random Access Channel (RACH)

The mapping between transport channels and physical channels is as follows:

In the uplink,

z UL-SCH can be mapped to PUSCH.

z RACH can be mapped to PRACH.

Figure 1-3 depicts the mapping between uplink transport and uplink physical

channels:

Figure 1-3Mapping between uplink transport channels and uplink physical channels

In the downlink,

z DL-SCH can be mapped to PDSCH.

z BCH can be mapped to PBCH.

z PCH can be mapped to PDSCH.

z MCH can be mapped to PMCH.

Figure 1-4 depicts the mapping between downlink transport and downlink physical

channels:


19/134



Figure 1-4Mapping between downlink transport channels and downlink physicalchannels

In Huawei LTE eRAN1.1, all transport channels are supported except those related

to the eMBMS functionality, such as MCH.

Enhancement

None

Dependency

None

1.9 LBFD-002003 Physical Channel Management

Availability


Summary

The physical layer is responsible for coding, physical-layer hybrid-ARQ processing,

modulation, multi-antenna processing, and mapping from the signal to theappropriate physical time-frequency resources. Based on the mapping, a transport

channel at the higher layer can serve one or several physical channels at the physicallayer.

In Huawei LTE eRAN1.1, all physical channels are supported except those related to

the eMBMS functionality, such as PMCH.

Benefits

Each physical channel provides a set of resource blocks for information

transmission.


20/134



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:

z Physical Broadcast Channel (PBCH)

z Physical Control Format Indicator Channel (PCFICH)

z Physical Downlink Control Channel (PDCCH)

z Physical Hybrid ARQ Indicator Channel (PHICH)

z Physical Downlink Shared Channel (PDSCH)

z Physical Multicast Channel (PMCH)

Uplink physical channels are classified into the following types:

z Physical Uplink Control Channel (PUCCH)

z Physical Uplink Shared Channel (PUSCH)

z Physical Random Access Channel (PRACH)

In Huawei LTE eRAN1.1, all physical channels are supported except those related to

the eMBMS functionality, such as PMCH.

Enhancement

None

Dependency

None

1.10 LBFD-002004 Integrity Protection

Availability


Summary

The feature offers the integrity protection for signaling data. It enables the receiving

entity (either UE or eNodeB) to check whether the signaling data has been illegallymodified. It encrypts or decrypts the signaling data by using a certain integrityalgorithm through an RRC message.

Benefits

The integrity protection procedure prevents the signaling data from illegalmodification.


21/134



Description

The integrity protection function prevents the signaling data from illegal

modification.LTE offers the integrity protection for RRC signaling messages at the PDCP layer.The sender calculates a message authentication code MAC-I based on the RRC

message and some parameters (such as the key, bearer ID, direction, and count) byusing an integrity algorithm, and then sends the code to the receiver together with the

message. The receiver recalculates the code and compares it with the code in themessage. If the two codes are inconsistent, the receiver knows that the message has

been modified illegally.

The eNodeB decides whether to use the integrity algorithm and informs each UE ofthe algorithm through an RRC message.

Huawei eRAN1.1 supports the integrity algorithm both the EIA1 (SNOW3G) and

EIA2 (AES).

Enhancement

In addition to the AES, Huawei eRAN1.1 also supports encryption algorithm

SNOW3G.

Dependency

The UE should support the same integrity algorithm as the eNodeB.

1.11 LBFD-002005 DL Asynchronization HARQ

Availability


Summary

The Hybrid Automatic Repeat Request (HARQ) provides robustness againsttransmission errors. It is also a mechanism for capacity enhancement. As HARQ

retransmissions are fast, many services allow one or multiple times ofretransmissions, thereby forming an implicit (closed loop) rate-control mechanism.

An asynchronization protocol is the basis for downlink HARQ operation. Hence,downlink retransmissions may occur at any time after the initial transmission, and an

explicit HARQ process number is used to indicate the HARQ process.

Benefits

DL HARQ functionality is a fast retransmission protocol to ensure successful data

transmission from the eNodeB to a UE at the physical layer and MAC layer. A UEcan request for retransmissions of data that was incorrectly decoded through anNACK message and soft-combine the retransmitted data with the previously

received data to improve the decoding performance.


22/134



This feature helps improve user throughput and reduce transmission latency in thedownlink.

DescriptionThe HARQ is a link enhancement technique combining Forward Error Correction(FEC) and ARQ technologies. Compared with the ARQ, the HARQ can provide

faster and more efficient retransmissions with lower transmission latency. In thedownlink, if the data received by the UE is decoded correctly by the FEC and passes

the Cyclic Redundancy Check (CRC), the UE will send an ACK message to informthe eNodeB that the data was received correctly. Otherwise, the UE will send aNACK message to the eNodeB to request for data retransmission.

Downlink HARQ is an asynchorization adaptive transmission process, which meansthat the scheduler of the HARQ transmission is not predetermined to the UE. In

addition, the DL HARQ information, such as the location of the allocated resource

blocks and MCSs, may be different from that of the previous transmissions.

In LTE specifications, the DL HARQ scheme is based on an IncrementalRedundancy (IR) algorithm. When a retransmission occurs, the DL HARQ

information will indicate whether the data belongs to the retransmitted data and its

corresponding Redundancy Version (RV). After the retransmitted data is received,according to its RV, the HARQ process in the UE will soft-combine the retransmitted

data with the previously buffered content and then forward the combined data to theFEC for decoding. The soft-combined data will help increase the probability ofsuccessful FEC decoding, thus increasing the data reception success rate.

In LTE specifications, multiple downlink HARQ processes are adopted to fully

utilize system resources. It greatly improves the system throughput and reduces the

latency, but it requires more buffer space and signaling overhead.

Enhancement

None

Dependency

None

1.12 LBFD-002006 UL Synchronization HARQ

Availability


Summary

Compared with the downlink HARQ, uplink retransmission is based on a

synchronization protocol. It occurs at a predefined time after the initial transmissionand the number of retransmissions can be implicitly derived.


23/134



Benefits

The UL HARQ functionality is a fast retransmission protocol to ensure successful

data transmission from the UE to the eNodeB at the physical layer and MAC layer.An eNodeB can request for retransmissions of data that was incorrectly decoded and

soft-combine the retransmitted data with the previously received data to improve thedecoding performance.

This feature helps improve the user throughput and reduce transmission latency in

the uplink.

Description

The HARQ is a link enhancement technique combining FEC and ARQ technologies.

Compared with the ARQ, the HARQ can provide faster and more efficientretransmissions with lower transmission latency. In the uplink, if the data received

by the eNodeB is decoded correctly by the FEC and passes the CRC check, theeNodeB will send an ACK message over the PHICH to inform the UE that the datawas received correctly. Otherwise, the eNodeB will send an NACK message to the

UE to request for data retransmission.

Uplink HARQ is a synchronization non-adaptive transmission process, which meansthat HARQ transmission blocks are predetermined for transmission and

retransmission. In addition, the UL HARQ information, such as the location of theallocated resource blocks and MCSs, is predetermined by the eNodeB.

In LTE specifications, UL HARQ scheme is based on an IR algorithm. When aretransmission occurs, UL HARQ information will indicate whether the databelongs to the retransmitted data and its corresponding RV. After the retransmitted

data is received, according to its RV, HARQ process in the eNodeB willsoft-combine the retransmitted data with the previously buffered content and

forward the combined data to the FEC for decoding. The soft-combined data willhelp increase the probability of successful FEC decoding, thus increasing the data

reception success rate.

In LTE specifications, multiple uplink HARQ processes are adopted to fully utilize

system resources. It greatly improves the system throughput and reduces the latency,

but it requires more buffer space and signaling overhead.

Enhancement

None

Dependency

None

1.13 LBFD-002007 RRC Connection Management

Availability



24/134



Summary

RRC connection is the layer 3 connection between the UE and eNodeB. The RRC

connection management aims to manage the layer 3 connection, includingestablishment, maintenance, and release of the connection.

Benefits

The RRC connection management is essential from the UE to E-UTRAN, and servesall service procedures and NAS procedures.

Description

RRC connection management involves RRC connection establishment, RRC

connection reconfiguration, RRC connection re-establishment, and RRC connection

release.z RRC connection establishment: This procedure is performed to establish an

RRC connection. RRC connection establishment involves Signaling Radio

Bearer 1 (SRB1) establishment. The procedure is also used to transmit theinitial NAS dedicated information or messages from the UE to the E-UTRAN.

z RRC connection reconfiguration: This procedure is performed to modify anRRC connection, for example, to establish, modify, or release radio bearers, to

perform handovers, and to configure or modify measurements. As a part of theprocedure, NAS dedicated information may be transmitted from the E-UTRANto the UE.

z RRC connection re-establishment: This procedure is performed to re-establish

an RRC connection after a handover failure or radio link failure. RRCconnection re-establishment involves the restoration of SRB1 operation and the

re-activation of security. A UE in RRC_CONNECTED mode, for whichsecurity has been activated, may initiate the procedure in order to continue the

RRC connection. The connection re-establishment will succeed only if the cellhas a valid UE context.

z RRC connection release: This procedure is performed to release an RRCconnection. RRC connection release involves the release of the establishedradio bearers and the release of all radio resources.

Enhancement

None

Dependency

None

1.14 LBFD-002008 Radio Bearer Management

Availability



25/134



Summary

Radio bearer management aims to manage SRB2 and Data Radio Bearer (DRB).

The radio bearer management includes the establishment, maintenance, and releaseof radio bearers.

Benefits

This feature provides configuration function of radio resources.

Description

Radio bearer management involves the establishment, maintenance, and release of

radio bearers, as well as the configuration of associated radio resources, for examplePDCP, RLC, logical channel, DRX,CQI, power headroom report (PHR), and

physical layer configuration. The radio bearer management is implemented duringthe RRC connection reconfiguration procedure.

Enhancement

None

Dependency

None

1.15 LBFD-002009 Broadcast of System Information

Availability


Summary

System information (SI) includes:

z Basic information for a UE to access the E-UTRAN, such as basic radio and

channel parametersz Information about cell selection and reselection parameters used by the UE in

RRC_IDLE mode

z Information about neighboring cells

z Important messages that should be send to each UE, such as earthquakewarning information

The SI broadcasted over the BCCH can be read without setting an RRC connection,

and it can be read by the UE in RRC_IDLE mode and RRC_CONNECTED mode.

SI may also be provided to the UE by means of dedicated signaling, for example, inthe case of handover.


26/134



Benefits

This feature is the basis for the UE to access the E-UTRAN.

Description

SI is classified into the MasterInformationBlock (MIB) and a number ofSystemInformationBlocks (SIBs):

z MasterInformationBlock defines the information about the most essentialphysical layers of the cell required for receiving further system information;

z SystemInformationBlockType1 contains the information for checking whethera UE is allowed to access a cell and for defining the scheduling of other systeminformation blocks;

z SystemInformationBlockType2 contains the information about common and

shared channels;z SystemInformationBlockType3 contains cell re-selection information, mainly

related to the serving cell;

z SystemInformationBlockType4 contains the information about the servingfrequency and intra-frequency neighboring cells related to cell re-selection

(including common cell re-selection parameters for a frequency andcell-specific re-selection parameters);

z SystemInformationBlockType5 contains the information about other E-UTRAfrequencies and inter-frequency neighboring cells related to cell re-selection


z SystemInformationBlockType6 contains the information about UTRA

frequencies and UTRA neighboring cells related to cell re-selection (including

common cell re-selection parameters for a frequency and cell-specificre-selection parameters);

z SystemInformationBlockType7 contains the information about GERANfrequencies related to cell re-selection (including cell re-selection parametersfor each frequency);

z SystemInformationBlockType8 contains the information about CDMA2000frequencies and CDMA2000 neighboring cells related to cell re-selection


z SystemInformationBlockType9 contains a home eNodeB identifier (HNBID);

z SystemInformationBlockType10 contains an ETWS primary notification;

z SystemInformationBlockType11 contains an ETWS secondary notification.

The MIB is mapped on the BCCH and carried on the BCH while all other SI

messages are mapped on the BCCH and dynamically carried on DL-SCH where theycan be identified through the System Information RNTI (SI-RNTI). Both the MIB

and SystemInformationBlockType1 use a fixed schedule within a period of 40 and80 ms respectively while the scheduling of other SI messages is flexible and

indicated by SystemInformationBlockType1.

The eNodeB may schedule DL-SCH transmissions concerning logical channelsother than BCCH in the same subframe as used for BCCH. The minimum UE


27/134



capability restricts the BCCH mapped to DL-SCH, for example, regarding themaximum rate.

The paging message is used to inform the UEs in RRC_IDLE and the UEs in

RRC_CONNECTED of the change of the system information.

Huawei LTE eRAN1.1 supports MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB7,and SIB8.

Enhancement

None

Dependency

None

1.16 LBFD-002010 Random Access Procedure

Availability


Summary

Random access is the essential function of LTE system, which allows a UE to

achieve the uplink synchronization and to request for a connection setup. It isperformed for the following five events:

z Initial access from RRC_IDLE

z RRC Connection Re-establishment procedure

z Handover

z DL data arrival during RRC_CONNECTED requiring random accessprocedure

z UL data arrival during RRC_CONNECTED requiring random accessprocedure

Benefits

This feature is the basis for the UE to access the E-UTRAN.

Description

The random access procedure enables the UE to establish uplink timing

synchronization and to request for setup of a connection to an eNodeB.

The procedure can be either contention-based (applicable to all the preceding fiveevents) or non-contention-based (applicable to only handover and DL data arrival).

Normal DL/UL transmission may occur after the random access procedure.

There are four steps for the contention-based random access procedure:


28/134



z The UE selects a Random Access Preamble randomly and transmits it over theavailable PRACH, which is set according to the PRACH configuration of thecell.

z The eNodeB transmits a Random Access Response after receiving the RandomAccess Preamble.

z After receiving the Random Access Response, the UE performs the firstscheduled UL transmission over the UL-SCH.

z The eNodeB transmits the contention resolution over the DL-SCH based on the

first scheduled UL transmission from the UE, to check whether the UE hassuccessfully accessed the network.

There are three steps for the non-contention-based random access procedure:

z The eNodeB assigns the Random Access Preamble and PRACH resource

through dedicated signaling to request the UE to initiate the random access

procedure.z The UE transmits the assigned Random Access Preamble over the assigned

PRACH.

z The eNodeB transmits a Random Access Response after receiving the Random

Access Preamble. Then, the UE successfully accesses the network when itreceives the Random Access Response.

Huawei eNodeB supports the two types of random access procedures. In addition,

Huawei eNodeB supports random access preamble formats 03 and PRACH

configurations 011 (TS 36.211).

Enhancement

None

Dependency

None

1.17 LBFD-002011 Paging

Availability


Summary

The purpose of paging is to transmit paging information to a UE in RRC_IDLE

mode, and/or to inform UEs in RRC_IDLE and UEs in RRC_CONNECTED mode

of a system information change.

Benefits

This feature is used to page a UE or inform UEs of system information change.


29/134



Description

E-UTRAN initiates the paging procedure by transmitting the paging message, which

can be sent by the MME or eNodeB.When an eNodeB receives a paging message from an MME over the S1 interface,the eNodeB shall perform paging of the UE in cells which belong to tracking areas

indicated in the "List of TAIs" Information Element (IE) in the paging message.

When the system information changes, the eNodeB should inform all UEs in the cellthrough paging. The eNodeB should guarantee that every UE can receive the paging

message, that is, the eNodeB should send the paging message on each possiblepaging occasion throughout a DRX cycle. Support for UE discontinuous reception

must be broadcasted to the entire cell coverage area and mapped to physicalresources.

EnhancementNone

Dependency

None

1.18 LBFD-002012 Cell Access Radius up to 15km

Availability


Summary

To improve wireless network coverage, 3GPP TS 36.211 has defined four types of

preamble formats (0, 1, 2, 3), among which the basic format 0 corresponds to 15 kmof cell access radius.

Benefits

This feature is used in small cell scenarios.

Description

According to 3GPP TS 36.211, four types of preamble formats (0, 1, 2, 3) forPRACH are defined to support different values of cell access radius, as shown in

Table 1-1.


30/134



Table 1-1Preamble formats and cell access radius

Preamble Format CPT SEQT Cell Access Radius

0 s3168 T s24576 T

About 15 km

1 s21024 T s24576 T

About 70 km

2 s6240 T s245762 T

About 30 km

3 s21024 T s245762 T

About 100 km

For format 0, the supported cell access radius is about 15 km, which is used in smallcell scenarios. For format 3, the supported cell access radius is about 100 km, which

is used in large cell scenarios to enhance the system coverage.

Enhancement

None

Dependency

None

1.19 LBFD-002023 Admission Control

Availability


Summary

Admission control function ensures the system stability and guarantees the QoS

performance by controlling the establishment of the connections within the

maximum resource utilization while satisfying the QoS requirements.

Benefits

Admission control function provides the following benefits:

z Reducing the risk of cell instability by controlling the number of admitted calls

z Achieving an optimal tradeoff between maximizing resource utilization andensuring QoS, by avoiding congestion and checking QoS satisfaction

Description

Admission control is a cell-based operation applied to both uplink and downlink. It

is one of the key Radio Resource Management (RRM) functions. Admission control

is performed when there are new incoming calls or incoming handover attempts. In


31/134



Huawei admission control solution, system resource limitation and QoS satisfactionratio are the main considerations for admission control.

When a new incoming call or incoming handover request arrives, admission control

is first to check the system resource limitation (including available transmissionbandwidth, hardware resource usage, and system overload indication). If any of the

resources is found to be limited, the new service request will be rejected.

If the resource limitation check passes, the QoS satisfaction ratio is the second

criterion for decision of whether to admit the call. In order to avoid mistakenlyrejecting a service request due to low QoS satisfaction ratio when there are a lot ofidle RBs, the RB occupancy and power-limit should be checked first. If the RB

occupancy is low and the power is not limited, the service request should beaccepted without QoS satisfaction ratio check.

When the RB occupancy is above the threshold or the transmit power headroom is

limited, the QoS satisfaction ratio is considered for admission decision. The QoS

satisfaction ratio is evaluated based on the QoS Class Identifier (QCI). QCI ismapped to one of the five QoS classes defined at cell level: Conversational Voice,

Buffered Streaming, IMS signaling, Guaranteed Bit Rate (GBR), and Non-GBR.

Each QoS class has different QoS satisfaction criteria: Conversational Voice andBuffered Streaming are evaluated by Mean Opinion Score (MOS); IMS signaling is

evaluated by packet loss rate; GBR and Non-GBR are evaluated by whetherthroughput achieves GBR or Minimum Guaranteed Bit Rate (min_GBR). If the QoSsatisfaction ratio for the evaluated QoS class is better than a predefined admission

threshold, the call request would be accepted; otherwise, it will be rejected.

Note that an incoming handover request has a higher priority than a new incomingcall request, because admission control gives a preference to an existing call

(handover request) over a new call.The Allocation/Retention Priority (ARP) can be used to classify Gold, Silver, andBronze categories with different admission control thresholds. ARP is an attribute of

services and is inherited from Evolved Packet Core (EPC).

Enhancement

None

Dependency

None

1.20 LBFD-002024 Congestion Control

Availability



32/134



Summary

The congestion control feature is used to adjust the system loading when the system

is in congestion or the QoS cannot be met.The main goal of congestion control feature is to guarantee the QoS for the admittedservices while achieving the maximum radio resource utilization.

Benefits

The congestion control feature provides the following benefits:

Prevent system from being unstable due to overload;

Guarantee QoS satisfaction rate of services in the system by effectively reduce the

system loading;

Description

This feature is critical to maintain the system stability and deliver acceptable Qualityof Service (QoS) when the system is in congestion.

The load measures include the power, the available physical resource block at the airinterface, and the transmission resource usage at S1-u interface.

In eRAN1.0, congestion control is provided in which two methods are introduced:

The first method is to release low-priority services to alleviate the overloaded system,

where the priority is determined based on the QoS Class Identifier (QCI) assigned tothe service.

The second method is GBR downsizing. The basic idea behind the GBR downsizing

is to slightly reduce the guaranteed data rate for all Guaranteed Bit Rate (GBR)services but still above the minimum bit rate. By sacrificing the quality of GBRservices slightly but still maintaining acceptable quality, it might improve the overall

QoS satisfaction ratio.

For VoIP services using the semi-persistent scheduling, only the first method is

applicable.

Enhancement

None

Dependency

None

1.21 LBFD-002025 Basic Scheduling

Availability



33/134



Summary

The basic scheduling feature provides two common scheduling algorithms (MAX

C/I and PF). The operator can select either algorithm.

Benefits

This feature provides the flexibility for the operator to select the scheduling

algorithm, considering the system capacity and fairness among the users.

Description

Scheduling algorithm enables the system to decide the resource allocation for each

UE during each TTI. This feature provides different scheduling algorithms,considering the tradeoff between system capacity and fairness among the users.

There are two scheduling algorithms provided and the operator can decide whichalgorithm to take.

z MAX C/I

z PF (proportional fair)

With MAX C/I, users are scheduled based on their radio channel quality. The radio

channel quality is the only factor to be considered in this algorithm and therefore, thefairness among users cannot be guaranteed.

With PF, users are scheduled according to the value of R/r, where R is the maximumdata rate corresponding to the channel quality, and r is the average data rate of the

user. The PF scheduler, based on the radio channel quality of an individual user,

provides the user with an average throughput proportional to its average channelquality. This algorithm is typically used by a wireless system to achieve a moderate

cell capacity while to ensure fairness among users.

Enhancement

None

Dependency

None

1.22 LBFD-002026 Uplink Power Control

Availability


Summary

Uplink power control in LTE system is essential to the control of the eNodeB over

the uplink transmit power of UEs. It also controls the interference to the neighboring


34/134



cells, to improve the system throughput. Uplink control power applies to PhysicalUplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH),

Sounding Reference Signal (SRS), and Physical Random Access Channel

(PRACH).

Benefits

The uplink power control can reduce the interference between neighboring cells by

carefully controlling the transmit power of UEs by the eNodeB and therefore,

increase the overall throughput in an LTE system. By using the power control, theuplink power control can ensure the quality, such as the block error rate (BLER), ofservice applications.

Description

Uplink power control is one of the most important features for an LTE system. Bycareful control over the UE transmit power, the interference to the neighboring cellscan be reduced and therefore the overall system throughput is improved. The uplinkpower control includes the mechanisms of PUSCH power control, PUCCH power

control, SRS power control, and PRACH power control.

The PUSCH power control includes the inner and outer loop power control. The

inner loop power control further consists of the open loop and closed loop powercontrol.

z When a UE starts the initial access to PUSCH, the open loop power control isused to set the transmit power according to the expected received power from

UE at the eNodeB (conveyed from the eNodeB to the UE via downlink control

channels) and the path loss estimated by the UE.z The uplink closed loop power control is used to compensate for the potential

inaccuracy caused by the open-loop power control. The eNodeB generates a

Transmit Power Control (TPC) command based on the Signal to InterferenceNoise Ratio (SINR) of the received uplink frames (e.g. SRS) from the UE. The

TPC command carries the recommended transmit power adjustment for the UE.The UE can then adjust the transmit power according to the TPC command

from the eNodeB.

z The outer loop power control is used to maintain the communication quality at

the level required by the service bearer by adjusting the SINR target (translatedto BLER target). The eNodeB compares the measured uplink BLER with the

BLER target. If the measured uplink BLER is higher than the BLER target, the

eNodeB increases the SINR target; otherwise, it decreases the SINR target.

The PUCCH power control employs the same power control mechanism (inner and

outer loop) as the PUSCH power control with different parameter settings (e.g.different SINR targets for the outer loop power control).

The uplink SRS power control also employs the same power control mechanism asthe PUSCH power control with identical parameter settings. Note that the initialpower is calculated in the same way as PUSCH, except that a power offset

configured by RRC is added.

For the PRACH power control, the UE will calculate the transmit power for theinitial Random Access (RA) preamble by estimating the downlink path loss and

based on the aforementioned expected received power from UE at eNodeB


35/134



obtained by monitoring the broadcast channel. If the RA preamble attempt fails (e.g.no RA preamble response for the eNodeB), the UE can increase the transmit power

for the next RA preamble attempt according to the settings configured by the RRC

layer.

Enhancement

None

Dependency

None

1.23 LBFD-002016 Dynamic Downlink PowerAllocation

Availability


Summary

Dynamic Downlink Power Allocationallows an eNodeB to dynamically set the

transmit power at downlink channels to reduce power consumption while

maintaining the quality of radio links. It provides flexible power allocation fordownlink channels based on the users channel quality and maintains acceptablequality of the downlink connections.

Benefits

This feature allows flexible power allocation for downlink channels based on theusers channel quality and maintains acceptable quality of the downlink connections.

Therefore, it can improve the edge user throughput and transmission power usage.

Description

This feature allows an eNodeB to dynamically set the transmit power at downlinkchannels to reduce power consumption while maintaining the quality of radio links.

The LTE downlink power allocation consists of several parts corresponding to

different types of downlink channels, such as Physical Downlink Shared Channel(PDSCH), Physical Downlink Control Channel (PDCCH), Physical HARQIndicator Channel (PHICH), Physical Broadcast Channel (PBCH), and Physical

Control Format Indicator Channel (PCFICH).

z For the PDSCH portion reserved for the logical common control channel, thepower allocation is semi-static in order to meet the coverage requirement. For

the PDSCH portion used for data transmission, in order to maximize datathroughput and provide higher cell edge data rates, the power resource is

dynamically allocated to each UE based on the reported Channel Quality


36/134



Indicator (CQI). The initial power is decided by the eNodeB for each UEaccording to the reported CQI and QoS requirement including the Guaranteed

Bit Rate (GBR) and Aggregate Maximum Bit Rate (AMBR). The transmit

power will be adjusted based on the reported CQI, in order to guarantee therequired data rate and maximize the power resource usage.

z For PDCCH and PHICH, besides the preceding power adjustment according to

the received CQI, outer-loop power control is used to adjust the SINR target inthe CQI report.

z For PCFICH and PBCH, fixed power allocation is employed instead ofdynamic power allocation, to ensure the decoding performance of all UEs in thesame cell.

Enhancement

None

Dependency

None

1.24 LBFD-002017 DRX

Availability


Summary

DRX (Discontinuous Reception) is a working mode in RRC_CONNECTED, inwhich UE switching the receiver on and off alternately according to the

configuration of eNB to continue or suspend the receiving of data and signals fromnetwork. The parameters of DRX allow an UE to communicate with the network in

order to define a time interval in which the network should not send anything to it.

Benefits

This feature reduces the power consumption of UEs and enhances the usage ofsystem control channel.

Description

To support the feature, UE should be configured by RRC with DRX functionality

that allows it to discontinuously monitor PDCCH on specific sub-frames..

There are two states in DRX mode, which are active state and sleep state namelyDRX state. During the active time, UE monitor PDCCH for the possible downlink

transmisstion from network.


37/134



Switching between two of the DRX states depends on several timers, which are OnDuration timer, DRX Inactivity timer, DRX Retransmission timer and Contention

Resolution Timer.

z The DRX cycle: specifies the periodic repetition of the On Duration followedby a possible period of inactivity (please refer to the figure below).

z The On Duration timer: specifies the number of consecutive

PDCCH-subframe(s) during which the UE shall monitor the PDCCH forpossible allocations. The On Duration timer is a part of a DRX Cycle.

Figure 1-5DRX cycle

z The DRX Inactivity timer: specifies the number of consecutivePDCCH-subframe(s), the timer is started or re-started when the UE shall

monitor the PDCCH after successfully decoding a PDCCH indicating an initialUL or DL user data transmission for this UE.

z The DRX Retransmission timer: specifies the maximum number of consecutive

PDCCH-subframe(s) during which the UE shall monitor the PDCCH for assoon as a DL retransmission is expected by the UE.

z The Contention Resolution Timer: Specifies the number of consecutivePDCCH-subframe(s) during which the UE shall monitor the PDCCH after the

uplink message containing the C-RNTI MAC control element or the uplinkmessage associated with UE Contention Resolution Identity submitted from

upper layer is transmitted.

Enhancement

None

Dependency

None


38/134



1.25 LBFD-002018 Mobility Management

1.25.1 LBFD-00201801 Coverage Based Intra-frequencyHandover

Availability


Summary

Handover functionality is important in any cellular telecommunications network. Itis performed to ensure no disruption to services. Handover plays a significant role in

LTE system performance since its main purpose is to decrease the communicationdelay, enlarge the coverage and then enhance the system performance.

Intra-Frequency Handover enables a UE in connected mode to be servedcontinuously when it moves across different cells that are operating at the samefrequency.

Benefits

The coverage-based intra-frequency handover feature provides supplementarycoverage in intra-frequency LTE systems to prevent call drop, enable seamless

coverage and therefore improve the network performance and end user experience.

Description

This feature is one of the fundamental functions of an LTE system. The purpose of

handover is to ensure that a UE in RRC-CONNECTED mode is served continuouslywhen it moves. Handover in LTE is characterized by the handover procedure in

which the original connection is released before a new connection is set up.

Intra-frequency handover refers to the handover between cells operating at the samefrequency band. It can be triggered by coverage or load. In eRAN1.0, the

coverage-based intra-frequency handover is supported.

The intra-frequency handover procedure can be divided into three phases: handovermeasurement, handover decision, and handover execution.

E-UTRAN configures the handover-related measurement through theRRC

Connection Reconfiguration message. The UE could measure either ReferenceSignal Received Power (RSRP) or Reference Signal Received Quality (RSRQ) for

intra-frequency handover.

Upon receiving a measurement report from the UE, the eNodeB makes a handoverdecision according to certain triggering criteria. If a handover is required, thehandover execution procedure will be invoked and the UE will be handed over from

the source eNodeB to the target eNodeB. Huawei eRAN1.0 follows the

intra-frequency handover procedures specified in 3GPP TS 36.300.

The following scenarios are considered in the intra-frequency handover:


39/134



z Handover between two cells configured in the same eNodeB. No externalneighbor is needed.

z Handover between two cells configured in different eNodeBs with an X2

interface available. In this case, the source eNodeB sends a HANDOVERREQUEST message over the X2 interface.

z Handover between two cells configured in different eNodeBs with no X2interface available. In this case, the source eNodeB sends a HANDOVERREQUIRED message over the S1 interface.

Enhancement

None

Dependency

None

1.25.2 LBFD-00201802 Coverage Based Inter-frequencyHandover

Availability


Summary

Inter-Frequency Handover enables a UE in connected mode to be served

continuously when it moves across different cells that are operating at differentfrequencies.

Benefits

The coverage-based inter-frequency handover provides supplementary coverage in

inter-frequency LTE systems to prevent call drop, enable seamless coverage, andtherefore improve the network performance and end user experience.

Description

This feature is one of the fundamental functions for an LTE system. The purpose of

inter-frequency handover is to ensure that a UE in RRC-CONNECTED mode is

served continuously when it moves across different cells operating at differentfrequencies.

The inter-frequency handover procedure can be divided into four phases:measurement triggering, handover measurement, handover decision, and handover

execution.

In inter-frequency handover, neighboring cell measurements are inter-frequency

measurements. The measurement is gap assisted for UEs with one RF receiver. Themeasurement is triggered by an event A2 and stopped by an event A1, based on the

monitoring on the value of RSRP or RSRQ.


40/134



In inter-frequency handover, the UE sends measurement reports to the eNodeB whenthe RSRP or RSRQ meets the criteria set in the measurement configuration.

Upon receiving a measurement report from the UE, the eNodeB makes a handover

decision. If the measurement meets the handover criteria, the eNodeB will performthe corresponding inter-frequency handover as specified in TS 36.300.

The following inter-frequency handover scenarios are applicable:

z Handover between two cells configured in the same eNodeB. In this case, theUE performs the handover between two cells configured in the same eNodeBand no external interface is required.

z Handover between two cells configured in different eNodeBs with an X2

interface available. In this case, the source eNodeB sends a HANDOVERREQUEST message over the X2 interface.

z Handover between two cells configured in different eNodeBs with no X2

interface available. In this case, the source eNodeB sends a HANDOVERREQUIRED message over the S1 interface.

Enhancement

None

Dependency

None

1.25.3 LBFD-00201803 Cell Selection and Reselection

Availability


Summary

Cell selection/reselection is a mechanism for UE in idle mode to select a cell toselect/reselect a cell to camp on and to receive the most appropriate service support

upon session activation in LTE systems.

BenefitsThis feature provides a mechanism for UE in idle mode to select/reselect a cell tocamp by supplementary coverage in LTE systems.

This feature facilitates the automatic selection of the network for UE in idle modeand avoids the complexity of manual operations.

The UE is always bound to a relatively good cell to obtain better service quality.

Description

When UE selects a PLMN or transition from RRC-CONNECTED to RRC-IDLE,

cell selection is required. The Non-Access Stratum (NAS) can determine the RAT(s)


41/134



in which the cell selection should be performed, for instance, by indicating theRAT(s) associated with the selected PLMN and by maintaining a list of forbidden

registration areas and a list of equivalent PLMN. The UE shall select a suitable cell

based on idle mode measurements and cell selection criteria.UE in RRC_IDLE can perform cell reselection if UE find a cell with a better radio

environment. When camping on a cell, UE shall regularly search for a better cellaccording to the cell reselection criteria. If a better cell is found, that cell is

reselected.

Absolute priorities of different E-UTRAN frequencies can be provided to the UE inthe system information and optionally in the RRC message releasing the RRC

connection.

Enhancement

None

Dependency

None

1.26 LBFD-002022 Static Inter-Cell InterferenceCoordination

1.26.1 LBFD-00202201 Downlink Static Inter-CellInterference Coordination

Availability


Summary

The downlink static inter-cell interference coordination function is used to reducethe downlink inter-cell interference. The basic principle is that the cell edge users of

different neighboring cells are allocated with non-overlapping frequency bands bystatic configuration so as to mitigate frequency interference.

Benefits

The downlink ICIC feature reduces the downlink inter-cell interference, thereforeimproves cell edge users throughput.

Description

In a LTE system, a cell can use the entire system frequency band and therefore it isinevitable to cause inter-cell interference for a multi-cell deployment, particularly at

the cell edge area. It is important to develop an efficient solution to mitigate the


42/134



inter-cell interference in the multi-cell environment in order to achieve theperformance target. A common solution is to coordinate the transmission among

neighboring cells to reduce the inter-cell interference.

In Huawei downlink static ICIC solution, for each cell, a fixed portion of the systemfrequency band is allocated to the cell edge users (CEUs). Between neighboring

cells, the allocation of the static CEU frequency band is carefully planned to avoidoverlapping. The transmit power for cell center users are limited below a certain

threshold, but no such limit for cell edges users. By doing so, the interference amongthe cell edge users within neighboring cells can be reduced, which is the major

source of the inter-cell interference. A simple example of the static ICIC solution isthe so-call the 1/3 partition. Among three neighboring cells, each cell will usedifferent 1/3 of the frequency band for the CEUs.

Enhancement

None

Dependency

None

1.26.2 LBFD-00202202 Uplink Static Inter-Cell InterferenceCoordination

Availability


Summary

The uplink static inter-cell interference coordination function is used to reduce the

uplink inter-cell interference. The basic principle is that the cell edge users of

different neighboring cells are allocated with non-overlapping frequency bands bystatic configuration so as to mitigate frequency interference.

Benefits

Uplink ICIC reduces inter-cell interference; therefore improve cell edge users and

overall throughput as well as the cell coverage.

Description

The uplink Inter-cell interference coordination (ICIC) is a technique to combat the

inter-cell interference for a LTE system by coordinating transmit power control andresource allocation in both frequency and time domains between neighboring cells.

It can improve the throughput of cell edge users and reduce impact of interference onsystem performance. Huawei eRAN1.1 supports ICIC in both frequency and time

domains.

In Huawei uplink static ICIC solution, different strategies are applied to the

Intra-eNodeB and Inter-eNodeB scenarios respectively. For the Intra-eNodeB UL


43/134



ICIC, the coordination is achieved at time domain due to the natural synchronizationamong the cells, where the cell edge users of different cells of Intra-eNodeB are

scheduled at different TTIs. For the Inter-eNodeB UL ICIC, the coordination is

achieved at the frequency domain, where the cell edge users of Inter-eNodeBs aregiven non-overlapping frequency bands. That is, the frequency band allocation forstatic UL ICIC is per eNodeB basis.

Between the neighboring cells, the allocation of the static CEU frequency band of

neighbor eNodeBs is carefully planned to avoid overlapping. By doing so, theinterference among the cell edge users in neighboring cells can be reduced, which is

the major source of the inter-cell interference. Additionally, the overload indicationmessage from X2 interface is also used for scheduling and power control purpose toavoid the interference due to overloaded frequency band.

Enhancement

None

Dependency

None

1.27 LBFD-002020 Antenna Configuration

1.27.1 LBFD-00202001 UL 2-Antenna Receive Diversity

Availability


Summary

Receive diversity is a common type of multiple antennas technology to improve

signal reception and to combat signal fading and interference. It improves networkcapacity and data rates. Huawei eNodeB supports both RX diversity mode and no

RX diversity mode.

Benefits

This feature can improve the receiver sensitivity and uplink coverage.

Description

Receive diversity is a technique to monitor signals at multiple frequencies from the

same signal source, or to monitor time division signals at the same frequencyfromthe same signal source, in order to combat signal fading and interference.

Receive diversity is one way to enhance the reception over uplink channels,including PUSCH, PUCCH, PRACH, and SRS.
http://www.answers.com/topic/fadinghttp://www.answers.com/topic/interferencehttp://www.answers.com/topic/frequencyhttp://www.answers.com/topic/frequencyhttp://www.answers.com/topic/fadinghttp://www.answers.com/topic/interferencehttp://www.answers.com/topic/interferencehttp://www.answers.com/topic/fadinghttp://www.answers.com/topic/frequencyhttp://www.answers.com/topic/interferencehttp://www.answers.com/topic/fading


44/134



Huawei eNodeB supports both RX diversity mode and no RX diversity mode. In RXdiversity mode, the eNodeB can be configured with 2 antennas (2-way) through the

Antenna Magnitude parameter.

In RX diversity mode, the eNodeB does not require additional devices and workswith the Maximum-Ratio Combining (MRC) or Interference Rejection Combining

(IRC) algorithms. Compared with 1-way reception without RX diversity, 2-way RXdiversity requires twice the number of RX channels. The number of RX channels

depends on the settings of the antenna connectors. The antennas to be used can bespace-interlace antennas or cross polarization antennas.

Enhancement

None

DependencyRX diversity requires the eNodeB to provide enough RF channels and demodulation

resources that can match the number of diversity antennas. This feature has nospecial requirements on UEs.

1.28 LBFD-002021 Reliability

1.28.1 LBFD-00202102 Cell Rebuild between BasebandProcessing Units

Availability


Summary

In Huawei eNodeB, multiple LTE Baseband Processing (LBBP) boards can beconfigured to serve multiple cells. When an LBBP fails, the cell/cells served by the

failed LBBP can be rebuilt on another operating LBBP with sp

LTE eRAN1.1 Feature Description V2.1(20091110).pdf

Documents

Transcript of LTE eRAN1.1 Feature Description V2.1(20091110).pdf