eran7.0 lte fdd basic feature description 01 20140915.pdf

eRAN7.0 V100R007C00

eRAN7.0 LTE FDD Basic Feature Description

Issue 01

Date 2014-05-04

HUAWEI TECHNOLOGIES CO., LTD.

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

Copyright Huawei Technologies Co., Ltd. i

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

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

eRAN7.0

eRAN7.0 LTE FDD Basic Feature Description Contents


Copyright Huawei Technologies Co., Ltd.

ii

Contents

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

1.1 Standards Compliance .................................................................................................................................................. 1

1.1.1 LBFD-001001 3GPP R8 Specifications..................................................................................................................... 1

1.1.2 LBFD-001007 3GPP R9 Specifications..................................................................................................................... 2

1.1.3 LBFD-001008 3GPP R10 Specifications................................................................................................................... 2

1.1.4 LBFD-001002 FDD mode ......................................................................................................................................... 3

1.1.5 LBFD-001003 Scalable Bandwidth ........................................................................................................................... 4

1.1.6 LBFD-001004 CP length ........................................................................................................................................... 5

1.1.6.1 LBFD-00100401 Normal CP .................................................................................................................................. 5

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

1.1.8 LBFD-001006 AMC .................................................................................................................................................. 7

1.2 RAN Architecture & Features ....................................................................................................................................... 8

1.2.1 LBFD-002001 Logical Channel Management ........................................................................................................... 8

1.2.2 LBFD-002002 Transport Channel Management ........................................................................................................ 9

1.2.3 LBFD-002003 Physical Channel Management ....................................................................................................... 10

1.2.4 LBFD-002004 Integrity Protection .......................................................................................................................... 11

1.2.5 LBFD-002005 DL Asynchronous HARQ ................................................................................................................ 12

1.2.6 LBFD-002006 UL Synchronous HARQ .................................................................................................................. 13

1.2.7 LBFD-002007 RRC Connection Management ........................................................................................................ 14

1.2.8 LBFD-002008 Radio Bearer Management .............................................................................................................. 15

1.2.9 LBFD-002009 Broadcast of system information ..................................................................................................... 16

1.2.10 LBFD-002010 Random Access Procedure ............................................................................................................ 17

1.2.11 LBFD-002011 Paging ............................................................................................................................................ 18

1.2.12 LBFD-002012 Cell Access Radius up to 15km ..................................................................................................... 19

1.2.13 LBFD-002023 Admission Control ......................................................................................................................... 20

1.2.14 LBFD-002024 Congestion Control ........................................................................................................................ 21

1.2.15 LBFD-002025 Basic Scheduling ........................................................................................................................... 22

1.2.16 LBFD-002026 Uplink Power Control.................................................................................................................... 23

1.2.17 LBFD-002016 Dynamic Downlink Power Allocation ........................................................................................... 25

1.2.18 LBFD-002017 DRX .............................................................................................................................................. 26

1.2.19 LBFD-002018 Mobility Management ................................................................................................................... 27

1.2.19.1 LBFD-00201801 Coverage Based Intra-frequency Handover ............................................................................ 27

1.2.19.2 LBFD-00201802 Coverage Based Inter-frequency Handover ............................................................................ 28

eRAN7.0




iii

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

1.2.19.4 LBFD-00201804 Distance Based Inter-frequency Handover ............................................................................. 31

1.2.19.5 LBFD-00201805 Service Based Inter-frequency Handover ............................................................................... 31

1.2.20 LBFD-002020 Antenna Configuration .................................................................................................................. 32

1.2.20.1 LBFD-00202001 UL 2-Antenna Receive Diversity ........................................................................................... 32

1.2.21 LBFD-002021 Reliability ...................................................................................................................................... 33

1.2.21.1 LBFD-00202101 Main Processing and Transport Unit Cold Backup ................................................................ 33

1.2.21.2 LBFD-00202102 Cell Re-build Between Baseband Processing Units ............................................................ 34

1.2.21.3 LBFD-00202103 SCTP Multi-homing ............................................................................................................... 36

1.2.21.4 LBFD-00202104 Intra-baseband Card Resource Pool (user level/cell level) ..................................................... 37

1.2.22 LBFD-002022 Static Inter-Cell Interference Coordination ................................................................................... 37

1.2.22.1 LBFD-00202201 Downlink Static Inter-Cell Interference Coordination............................................................ 37

1.2.22.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination ................................................................ 38

1.2.23 LBFD-002027 Support of UE Category 1 ............................................................................................................. 39

1.2.24 LBFD-002028 Emergency Call ............................................................................................................................. 41

1.2.25 LBFD-002029 Earthquake and Tsunami Warning System (ETWS) ...................................................................... 42

1.2.26 LBFD-002031 Support of aperiodic CQI reports .................................................................................................. 44

1.2.27 LBFD-002032 Extended-QCI ................................................................................................................................ 44

1.2.28 LBFD-002033 SCTP Congestion Control ............................................................................................................. 45

1.2.29 LBFD-002034 RRU Channel Cross Connection Under MIMO ............................................................................ 46

1.2.30 LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting ............................................................... 48

1.2.31 LBFD-060102 Enhanced UL Frequency Selective Scheduling ............................................................................. 49

1.2.32 LBFD-060103 Enhanced DL Frequency Selective Scheduling ............................................................................. 50

1.2.33 LBFD-070103 Multi-Band Compatibility Enhancement ....................................................................................... 51

1.2.34 LBFD-070101 Uplink Timing Based on PUCCH ................................................................................................. 52

1.2.35 LBFD-070102 MBR>GBR Configuration ............................................................................................................ 53

1.2.36 LBFD-070105 IoT-based PUSCH Power Control ................................................................................................. 54

1.2.37 LBFD-070106 PDSCH Efficiency Improvement .................................................................................................. 55

1.2.38 LBFD-070107 PDCCH Utilization Improvement ................................................................................................. 56

1.3 Transmission & Security ............................................................................................................................................. 57

1.3.1 LBFD-003001 Transmission Networking ................................................................................................................ 57

1.3.1.1 LBFD-00300101 Star Topology ........................................................................................................................... 57

1.3.1.2 LBFD-00300102 Chain Topology ........................................................................................................................ 58

1.3.1.3 LBFD-00300103 Tree Topology ........................................................................................................................... 59

1.3.2 LBFD-003002 Basic Qos Management ................................................................................................................... 60

1.3.2.1 LBFD-00300201 DiffServ QoS Support .............................................................................................................. 60

1.3.3 LBFD-003003 VLAN Support (IEEE 802.1p/q) ..................................................................................................... 62

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

1.3.4.1 LBFD-00300401 IP Header Compression ............................................................................................................ 63

1.3.4.2 LBFD-00300402 PPP MUX ................................................................................................................................. 63

1.3.4.3 LBFD-00300403 ML-PPP/MC-PPP ..................................................................................................................... 64

1.3.5 LBFD-003005 Synchronization ............................................................................................................................... 66

eRAN7.0




iv

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

1.3.5.2 LBFD-00300502 Free-running Mode ................................................................................................................... 67

1.3.5.3 LBFD-00300503 Synchronization with GPS ....................................................................................................... 67

1.3.5.4 LBFD-00300504 Synchronization with BITS ...................................................................................................... 68

1.3.5.5 LBFD-00300505 Synchronization with 1PPS ...................................................................................................... 69

1.3.5.6 LBFD-00300506 Synchronization with E1/T1 ..................................................................................................... 70

1.3.6 LBFD-003006 IPv4/IPv6 Dual Stack ...................................................................................................................... 71

1.4 Operation & Maintenance ........................................................................................................................................... 72

1.4.1 LBFD-004001 Local Maintenance of the LMT ....................................................................................................... 72

1.4.2 LBFD-004002 Centralized U2000 Management ..................................................................................................... 72

1.4.3 LBFD-004003 Security Socket Layer ..................................................................................................................... 73

1.4.4 LBFD-004004 Software Version Upgrade Management ......................................................................................... 74

1.4.5 LBFD-004005 Hot Patch Management ................................................................................................................... 75

1.4.6 LBFD-004006 Fault Management ........................................................................................................................... 76

1.4.7 LBFD-004007 Configuration Management ............................................................................................................. 78

1.4.8 LBFD-004008 Performance Management ............................................................................................................... 79

1.4.9 LBFD-004009 Real-time Monitoring of System Running Information .................................................................. 80

1.4.10 LBFD-004010 Security Management .................................................................................................................... 81

1.4.11 LBFD-004011 Optimized eNodeB Commissioning Solution ................................................................................ 82

1.4.12 LBFD-004012 Environment Monitoring ............................................................................................................... 83

1.4.13 LBFD-004013 Inventory Management .................................................................................................................. 83

1.4.14 LBFD-004014 License Management ..................................................................................................................... 84

1.4.15 LBFD-004015 License Control for Urgency ......................................................................................................... 85

1.4.16 LBFD-070104 Site Transmission Equipment Fault Detection .............................................................................. 86

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

eRAN7.0

eRAN7.0 LTE FDD Basic Feature Description Figures



v

Figures

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

Figure 1-2 Stream Control Transmission Protocol .............................................................................................. 36

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

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

Figure 1-5 Comparing with no MIMO load Sharing ........................................................................................... 48

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

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

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

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

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

eRAN7.0

eRAN7.0 LTE FDD Basic Feature Description Tables



vi

Tables

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

Table 1-2 Downlink physical layer parameter values set by the field UE-Category ........................................... 40

Table 1-3 Uplink physical layer parameter values set by the field UE-Category ................................................ 40

Table 1-4 Total layer 2 buffer sizes set by the field UE-Category ....................................................................... 40

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

Table 2-1 Acronyms and Abbreviations ............................................................................................................... 91

eRAN7.0

eRAN7.0 LTE FDD Basic Feature Description 1 Basic Features



1

1 Basic Features About This Chapter

1.1 Standards Compliance

1.2 RAN Architecture & Features

1.3 Transmission & Security

1.4 Operation & Maintenance

1.1 Standards Compliance

1.1.1 LBFD-001001 3GPP R8 Specifications

Availability

This feature is

applicable to Macro from eRAN1.0

applicable to Micro from eRAN3.0

applicable to Lampsite from eRAN6.0

Summary

Huawei LTE eNodeB is compliant with 3GPP Release 8 specifications 2009Q3.

Benefits

None

Description

Huawei LTE eNodeB is compliant with 3GPP Release 8 specifications 2009Q3.

Huawei is an active participant and great contributor to 3GPP specification development. This

high-level involvement enables Huawei to actively contribute, and closely follow 3GPP

eRAN7.0




2

standard development during Huawei product development. LTE eNodeB supports 3GPP

Release 8 2009Q3.

Enhancement

None

Dependency

None


Availability

This feature is




Summary

Huawei LTE eNodeB is compliant with 3GPP Release 9 specifications 2010.09 version.

Benefits

None

Description





Release 9 specifications 2010.09 version, which is the latest version of LTE standard.

Enhancement

None

Dependency

None


Availability

This feature is


eRAN7.0




3



Summary

Huawei LTE eNodeB is compliant with 3GPP Release 10 specifications.

Benefits

None

Description





Release 10 specifications 2011.03 version.

Enhancement

None

Dependency

None

1.1.4 LBFD-001002 FDD mode

Availability

This feature is




Summary

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

Benefits

None

Description

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

used for the uplink and the downlink.

eRAN7.0




4

Enhancement

None

Dependency Others

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

1.1.5 LBFD-001003 Scalable Bandwidth

Availability

This feature is




Summary

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

Huawei LTE eRAN2.0 supports two new bandwidths of 1.4 MHz and 3 MHz to extend the

range of bandwidth support for the LTE technology. Micro eNodeB does not support 1.4 MHz

and 3 MHz bandwidth.

Benefits Larger bandwidth produces higher throughput and better user experience.

Flexible bandwidth configuration helps operators use frequency bands.

Besides the existing bandwidths supported by eRAN1.0, the introduction of 1.4 MHz

and 3 MHz bandwidths enables the flexibility for operators to allocate smaller bandwidth

less than 5 MHz, thus saving radio resources. This is not applicable to Micro eNodeB.

Description

Huawei LTE eRAN2.0 supports the channel bandwidths from 1.4 MHz to 20 MHz, including

1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz. The bandwidth can be configured

by the software.

Enhancement In eRAN2.0

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

MHz.

Huawei LTE eRAN2.0 supports two new bandwidths of 1.4 MHz and 3 MHz.

Dependency UE

UEs should support the same bandwidth as the eNodeB.

eRAN7.0




5

1.1.6 LBFD-001004 CP length

1.1.6.1 LBFD-00100401 Normal CP

Availability

This feature is




Summary

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

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

OFDM to decrease the inter-symbol interference due to the multipath delay.

Benefits

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

Description

The CP is the guard interval used in the OFDM to decrease the interference due to the

multipath delay.

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

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

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

length (time) is calculated as follows:

In the downlink

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

In the uplink

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

to #6)

Where, Ts = 1 / (2048 x Df), Df = 15 kHz

Enhancement

None

Dependency

None

eRAN7.0




6

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

Availability

This feature is




Summary

This feature shows the different modulation schemes supported by the UE and eNodeB.

Benefits

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

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

excellent channel conditions to achieve higher data rates, which improves the system

throughput and spectrum efficiency.

Description

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

eNodeB and the UE in uplink and downlink.

The following modulation schemes are supported:

Uplink/downlink Quadrature Phase Shift Keying (QPSK)

Uplink/downlink 16 Quadrature Amplitude Modulation (16QAM)

Downlink 64QAM

The characteristics are as follows:

QPSK allows up to two information bits modulated per symbol due to four different

neighboring alternatives.

16QAM allows up to four information bits modulated per symbol due to 16 different


64QAM allows up to six information bits modulated per symbol due to 64 different


This feature allows the eNodeB and UE to choose an optimal modulation scheme based on the

current channel condition to achieve the best tradeoff between the user data rate and the frame

error rate (FER) during transmission.

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

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

modulation scheme for uplink transmission to meet the requirement of the call quality. When

a UE is in an excellent radio environment, it can use a high-order QAM modulation (such as

16QAM) scheme for uplink transmission to achieve high bit rates.

eRAN7.0




7

Enhancement

None

Dependency UE

The UE should support the same modulation scheme.

1.1.8 LBFD-001006 AMC

Availability

This feature is




Summary

The Adaptive Modulation and Coding (AMC) function allows an eNodeB to adaptively select

the optimal Modulation and Coding Scheme (MCS) according to the channel condition. This

improves the spectrum efficiency after the system resource and transmitting power are fixed.

Therefore, the throughput can be maximized and the Quality of Service (QoS) requirements

can be met.

Benefits

The AMC provides the following benefits:

Maximizes the system throughput by selecting the optimal MCS.

Meets the QoS requirement (such as the packet loss rate) by selecting the optimal MCS

to achieve the best tradeoff between data rate and block error rate.

Description

The AMC function allows an eNodeB to adaptively select the optimal MCS according to the

channel information. This improves the spectrum efficiency after the system resource and

transmitting power are fixed. Therefore, the throughput can be maximized and the QoS

requirements can be met.

In the uplink, the initial MCS can be selected on the basis of the Signal to Interference plus

Noise Ratio (SINR) of the uplink Reference Signal (RS) measured by the eNodeB. It can also

be adjusted on the basis of whether the uplink transmission involves control signals. Note that

control signals might require a lower-order MCS for ensuring a reliable transmission.

In the downlink, the eNodeB first selects the MCS for each UE based on the CQI reported

from the UE and assigned power for the UE. Then, the eNodeB can adjust the CQI to impact

MCS based on the BLER, in order to maximize the usage of the radio resources.

Enhancement

None

eRAN7.0




8

Dependency

None

1.2 RAN Architecture & Features

1.2.1 LBFD-002001 Logical Channel Management

Availability

This feature is




Summary

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

Radio Link Control (RLC) layer. Each logical channel type is defined according to the type of

the transmitted data. They are generally classified into two types: control channels and traffic

channels.

In Huawei LTE eNodeB, all logical channels are supported except those related to the evolved

Multimedia Broadcast Multicast Service (eMBMS) functionality.

Benefits

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

Description

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

responsible for "what is transported". They are generally classified into two types:

Control channels: for transmitting the control plane information

Traffic channels: for transmitting the user plane information

Control channels include:

Broadcast Control Channel (BCCH)

Paging Control Channel (PCCH)

Common Control Channel (CCCH)

Multicast Control Channel (MCCH)

Dedicated Control Channel (DCCH)

Traffic channels include:

Dedicated Traffic Channel (DTCH)

Multicast Traffic Channel (MTCH)

eRAN7.0




9

In Huawei LTE eNodeB, all logical channels are supported except those related to the

eMBMS functionality, such as MCCH and MTCH.

Enhancement

None

Dependency

None

1.2.2 LBFD-002002 Transport Channel Management

Availability

This feature is




Summary

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

defined according to the type of transmitted data and the method of data transmission over the

radio interface. They are used to offer the information about transmission services for the

MAC and higher layers. In Huawei LTE eNodeB, all transport channels except those related

to the eMBMS functionality are supported.

Benefits

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

transmitted.

Description

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

responsible for what type of data is transmitted and how the data is transmitted over the radio

interface.

Downlink transport channels are classified into the following types:

Broadcast Channel (BCH)

Downlink Shared Channel (DL-SCH)

Paging Channel (PCH)

Multicast Channel (MCH)

Uplink transport channels are classified into the following types:

Uplink Shared Channel (UL-SCH)

Random Access Channel (RACH)

In Huawei LTE eNodeB, all transport channels are supported except those related to the

eMBMS functionality, such as MCH.

eRAN7.0




10

Enhancement

None

Dependency

None

1.2.3 LBFD-002003 Physical Channel Management

Availability

This feature is




Summary

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

modulation, multi-antenna processing, and mapping from the signal to the appropriate

physical time-frequency resources. Based on the mapping, a transport channel at the higher

layer can serve one or several physical channels at the physical layer.

In Huawei LTE eNodeB, all physical channels are supported except those related to the

eMBMS functionality, such as PMCH.

Benefits

Each physical channel provides a set of resource blocks for information transmission.

Description

Each physical channel corresponds to a set of resource blocks carrying the information from

higher layers.

Downlink physical channels are classified into the following types:

Physical Broadcast Channel (PBCH)

Physical Control Format Indicator Channel (PCFICH)

Physical Downlink Control Channel (PDCCH)

Physical Hybrid ARQ Indicator Channel (PHICH)

Physical Downlink Shared Channel (PDSCH)

Physical Multicast Channel (PMCH)

Uplink physical channels are classified into the following types:

Physical Uplink Control Channel (PUCCH)

Physical Uplink Shared Channel (PUSCH)

Physical Random Access Channel (PRACH)

eRAN7.0




11

In Huawei LTE eNodeB, all physical channels are supported except those related to the

eMBMS functionality, such as PMCH.

Enhancement

None

Dependency

None

1.2.4 LBFD-002004 Integrity Protection

Availability

This feature is




Summary

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

(either UE or eNodeB) to check whether the signaling data has been illegally modified. It

encrypts or decrypts the signaling data by using a certain integrity algorithm through an RRC

message.

Benefits

The integrity protection procedure prevents the signaling data from illegal modification.

Description

LTE offers the integrity protection for RRC signaling messages at the PDCP layer. The sender

calculates a message authentication code MAC-I based on the RRC message and some

parameters (such as the key, bearer ID, direction, and count) by using an integrity algorithm,

and then send the code to the receiver together with the message. The receiver recalculates the

code and compares it with the code in the message. If the two codes are inconsistent, the

receiver knows that the message has been modified illegally.

The eNodeB decides which integrity algorithm to use and informs each UE of it through an

RRC message.


In addition to the AES, Huawei eRAN2.0 also supports integrity algorithm SNOW3G.

In eRAN6.0

Macro also supports integrity algorithm ZUC.

In eRAN7.0

Micro also supports integrity algorithm ZUC.

eRAN7.0




12

Dependency UE

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

1.2.5 LBFD-002005 DL Asynchronous HARQ

Availability

This feature is




Summary

The Hybrid Automatic Repeat Request (HARQ) provides robustness against transmission

errors. It is also a mechanism for capacity enhancement. As HARQ retransmissions are fast,

many services allow one or multiple times of retransmissions, thereby forming an implicit

(closed loop) rate-control mechanism. An asynchronous protocol is the basis for downlink

HARQ operation. Hence, downlink retransmissions may occur at any time after the initial

transmission, and an explicit HARQ process number is used to indicate the HARQ process.

Benefits

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

transmission from the eNodeB to a UE at the physical layer and MAC layer. A UE can request

for retransmissions of data that was incorrectly decoded through an NACK message and

soft-combine the retransmitted data with the previously received data to improve the decoding

performance.

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

Description

The HARQ is a link enhancement technique combining Forward Error Correction (FEC) and

ARQ technologies. Compared with the ARQ, the HARQ can provide faster and more efficient

retransmissions with lower transmission latency. In the downlink, if the data received by the

UE is decoded correctly by the FEC and passes the Cyclic Redundancy Check (CRC), the UE

will send an ACK message to inform the eNodeB that the data was received correctly.

Otherwise, the UE will send a NACK message to the eNodeB to request for data

retransmission.

Downlink HARQ is an asynchronous adaptive transmission process, which means that the

scheduler of the HARQ transmission is not predetermined to the UE. In addition, the DL

HARQ information, such as the location of the allocated resource blocks and MCSs, may be

different from that of the previous transmissions.

In LTE specifications, the DL HARQ scheme is based on an Incremental Redundancy (IR)

algorithm. After the retransmitted data is received, the HARQ process in the UE will

soft-combine the retransmitted data with the previously buffered content and then forward the

combined data to the FEC for decoding. The soft-combined data will help increase the

probability of successful FEC decoding, thus increasing the data reception success rate.

eRAN7.0




13

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

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

more buffer space and signaling overhead.

Enhancement

None

Dependency

None

1.2.6 LBFD-002006 UL Synchronous HARQ

Availability

This feature is




Summary

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

protocol. It occurs at a predefined time after the initial transmission and the number of

retransmissions can be implicitly derived.

Benefits

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

transmission from the UE to the eNodeB at the physical layer and MAC layer. An eNodeB

can request for retransmissions of data that is incorrectly decoded and soft-combine the

retransmitted data with the previously received data to improve the decoding performance.

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

Description

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

Compared with the ARQ, the HARQ can provide faster and more efficient retransmissions

with lower transmission latency. In the uplink, if the data received by the eNodeB is decoded

correctly by the FEC and passes the CRC check, the eNodeB will send an ACK message over

the PHICH to inform the UE that the data was received correctly. Otherwise, the eNodeB will

send an NACK message to the UE to request for data retransmission.

In eRAN1.0, Uplink HARQ is a synchronization non-adaptive transmission process, which

means that HARQ transmission blocks are predetermined for transmission and retransmission.

In addition, the UL HARQ information, such as the location of the allocated resource blocks

and MCSs, is predetermined by the eNodeB.

In eRAN2.0, Huawei supports a synchronous adaptive UL HARQ transmission. While

retransmitting, the allocated resource block, coding and modulation scheme may be changed

eRAN7.0




14

according to the channel quality. But the retransmission transport block size remains the same

as the first transmission.

In LTE specifications, UL HARQ scheme is based on an IR algorithm. After the retransmitted

data is received, HARQ process in the eNodeB will soft-combine the retransmitted data with

the previously buffered content and forward the combined data to the FEC for decoding. The

soft-combined data will help increase the probability of successful FEC decoding, thus

increasing the data reception success rate.

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

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

more buffer space and signaling overhead.


Huawei supports a synchronous adaptive UL HARQ transmission. While in eRAN1.0,

Uplink HARQ is a synchronization non-adaptive transmission process.

Dependency

None

1.2.7 LBFD-002007 RRC Connection Management

Availability

This feature is




Summary

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

management aims to manage the layer 3 connection, including establishment, maintenance,

and release of the connection.

Benefits

The RRC connection management is essential from the UE to E-UTRAN, and serves all

service procedures and NAS procedures.

Description

RRC connection management involves RRC connection establishment, RRC connection

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

RRC connection establishment: This procedure is performed to establish an RRC

connection. RRC connection establishment involves Signaling Radio Bearer 1 (SRB1)

establishment. The procedure is also used to transmit the initial NAS dedicated

information or messages from the UE to the E-UTRAN.

eRAN7.0




15

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

connection, for example, to establish, modify, or release radio bearers, to perform

handovers, and to configure or modify measurements. As a part of the procedure, NAS

dedicated information may be transmitted from the E-UTRAN to the UE.

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

connection after a handover failure or radio link failure. RRC connection

re-establishment involves the restoration of SRB1 operation and the re-activation of

security. A UE in RRC_CONNECTED mode, for which security has been activated, may

initiate the procedure in order to continue the RRC connection. The connection

re-establishment will succeed only if the cell has a valid UE context.

RRC connection release: This procedure is performed to release an RRC connection.

RRC connection release involves the release of the established radio bearers and the

release of all radio resources.

Enhancement

None

Dependency

None

1.2.8 LBFD-002008 Radio Bearer Management

Availability

This feature is




Summary

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

bearer management includes the establishment, maintenance, and release of radio bearers.

Benefits

This feature provides configuration function of radio resources.

Description

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

bearers, as well as the configuration of associated radio resources, for example PDCP, RLC,

logical channel, DRX,CQI, power headroom report (PHR), and physical layer configuration.

The radio bearer management is implemented during the RRC connection reconfiguration

procedure.

Enhancement

None

eRAN7.0




16

Dependency

None

1.2.9 LBFD-002009 Broadcast of system information

Availability

This feature is




Summary

System information (SI) includes:

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

parameters

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

RRC_IDLE mode

Information about neighboring cells

Important messages that should be sent to each UE, such as earthquake warning

information

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

be read by the UE in RRC_IDLE mode and RRC_CONNECTED mode. SI may also be

provided to the UE by means of dedicated signaling, for example, in the case of handover.

Benefits

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

Description

SI is classified into the MasterInformationBlock (MIB) and a number of

SystemInformationBlocks (SIBs):

MasterInformationBlock defines the information about the most essential physical layers

of the cell required for receiving further system information;

SystemInformationBlockType1 contains the information for checking whether a UE is

allowed to access a cell and for defining the scheduling of other system information

blocks;

SystemInformationBlockType2 contains the information about common and shared

channels;

SystemInformationBlockType3 contains cell re-selection information, mainly related to

the serving cell;

SystemInformationBlockType4 contains the information about the serving frequency and

intra-frequency neighboring cells related to cell re-selection (including common cell

re-selection parameters for a frequency and cell-specific re-selection parameters);

eRAN7.0




17

SystemInformationBlockType5 contains the information about other E-UTRA

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

common cell re-selection parameters for a frequency and cell-specific re-selection

parameters);

SystemInformationBlockType6 contains the information about UTRA frequencies and

UTRA neighboring cells related to cell re-selection (including common cell re-selection

parameters for a frequency and cell-specific re-selection parameters);

SystemInformationBlockType7 contains the information about GERAN frequencies

related to cell re-selection (including cell re-selection parameters for each frequency);

SystemInformationBlockType8 contains the information about CDMA2000 frequencies

and CDMA2000 neighboring cells related to cell re-selection (including common cell

re-selection parameters for a frequency and cell-specific re-selection parameters);

SystemInformationBlockType9 contains a home eNodeB identifier (HNBID);

SystemInformationBlockType10 contains an ETWS primary notification;

SystemInformationBlockType11 contains an ETWS secondary notification.

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

RRC_CONNECTED of the change of the system information.

Huawei eNodeB supports MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, SIB10 and

SIB11.

Enhancement

None

Dependency

None

1.2.10 LBFD-002010 Random Access Procedure

Availability

This feature is




Summary

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

uplink synchronization and to request for a connection setup. It is performed for the following

five events:

Initial access from RRC_IDLE

RRC Connection Re-establishment procedure

Handover

DL data arrival during RRC_CONNECTED and UE is out-of-sync with eNodeB in

uplink

eRAN7.0




18

UL data arrival during RRC_CONNECTED and UE is out-of-sync with eNodeB in

uplink

Benefits

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

Description

The random access procedure enables the UE to establish uplink timing synchronization and

to request for setup of a connection to an eNodeB.

The procedure can be either contention-based (applicable to all the preceding five events) or

non-contention-based (applicable to only handover and DL data arrival). Normal DL/UL

transmission may occur after the random access procedure.

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

eNodeB supports random access preamble formats 03 and PRACH configurations 063 (TS 36.211).

Enhancement

None

Dependency

None

1.2.11 LBFD-002011 Paging

Availability

This feature is




Summary

The purpose of paging is to transmit paging information to a UE in RRC_IDLE mode, and/or

to inform UEs in RRC_IDLE and UEs in RRC_CONNECTED mode of a system information

change.

Benefits

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

Description

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

sent by the MME or eNodeB.

eRAN7.0




19

When an eNodeB receives a paging message from an MME over the S1 interface, the eNodeB

shall perform paging of the UE in cells which belong to tracking areas indicated in the "List

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

When the system information changes, the eNodeB should inform all UEs in the cell through

paging, and should guarantee that every UE can receive the paging message. That is, the

eNodeB should send the paging message on each possible paging occasion throughout a DRX

cycle. Support for UE discontinuous reception must be broadcasted to the entire cell coverage

area and mapped to physical resources.

Enhancement

None

Dependency

None

1.2.12 LBFD-002012 Cell Access Radius up to 15km

Availability

This feature is


not applicable to Micro

not applicable to Lampsite

Summary

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

formats (0, 1, 2, 3) for frame structure type 1, among which the basic format 0 corresponds to

15 km of cell access radius.

Benefits

This feature is used in small cell scenarios.

Description

This feature provides operator with support of 15km cell radius. According to 3GPP TS

36.211, four types of preamble format (0, 1, 2, 3) for PRACH are defined to support diff Table 1-1.

Table 1-1 Preamble formats and cell access radius

Preamble Format

Cell Access Radius

0

About 15 km

1

About 70 km

2

About 30 km

eRAN7.0




20

3

About 100 km

For format 0, the supported cell access radius is about 15 km, which is used in small cell

scenarios, and considered as basic cell radius. For format 3, the supported cell access radius is

about 100 km, which is used in large cell scenarios to enhance the system coverage.

Enhancement

None

Dependency

None

1.2.13 LBFD-002023 Admission Control

Availability

This feature is




Summary

Admission control function ensures the system stability and guarantees the QoS performance

by controlling the establishment of the connections within the maximum resource utilization

while satisfying the QoS requirements.

Benefits

Admission control function provides the following benefits:

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

Achieving an optimal tradeoff between maximizing resource utilization and ensuring

QoS, by avoiding congestion and checking QoS satisfaction

Description

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

the key Radio Resource Management (RRM) functions. Admission control is performed when

there are new incoming calls or incoming handover attempts. In Huawei admission control

solution, system resource limitation and QoS satisfaction ratio are the main considerations for

admission control.

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

check the system resource limitation (including hardware resource usage, and system

overload indication). If any of the resources is found to be limited, the new service request

will be rejected.

eRAN7.0




21

If the resource limitation checking passes, for Non-GBR service it will be admitted and for

the GBR service it will check the QoS satisfaction ratio The QoS satisfaction ratio is

evaluated based on the QoS Class Identifier (QCI). If the QoS satisfaction ratio for the

evaluated QoS class is better than a predefined admission threshold, the call request would be

accepted; otherwise, it will be rejected.

Note that an incoming handover request has a higher priority than a new incoming call request,

because admission control gives a preference to an existing call (handover request) over a

new call.

The Allocation/Retention Priority (ARP) can be used to classify Gold, Silver, and Bronze

categories with different admission control thresholds. ARP is an attribute of services and is

inherited from Evolved Packet Core (EPC).

Enhancement eRAN7.0

In user admission, UE numbers are reserved for privileged UEs to increase the admission

success rate of these UEs. Privileged UEs include emergency UEs and high-priority UEs

whose cause value of RRC connection establishment request is "highPriorityAccess".

Dependency

None

1.2.14 LBFD-002024 Congestion Control

Availability

This feature is




Summary

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

congestion or the QoS cannot be met.

The main goal of congestion control feature is to guarantee the QoS for the admitted services

while achieving the maximum radio resource utilization.

Benefits

The congestion control feature provides the following benefits:

Prevent system from being unstable due to overload;

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

loading;

eRAN7.0




22

Description

This feature is critical to maintain the system stability and deliver acceptable Quality of

Service (QoS) when the system is in congestion.

In eNodeB, congestion control is provided in which a method are introduced:

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

priority is determined based on the ARP assigned to the service.

Enhancement

Size reduction on GBR service is not accepted by most operators and is not recommended

according to 3GPP. Function of size reduction on GBR service is removed when cell is in

congestion.

Dependency

None

1.2.15 LBFD-002025 Basic Scheduling

Availability

This feature is




Summary

The basic scheduling feature provides three common scheduling algorithms (MAX C/I and

RR and PF). The operator can select either algorithm.

Benefits

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

considering the system capacity and fairness among the users.

Description

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

each TTI. This feature provides different scheduling algorithms, considering the tradeoff

between system capacity and fairness among the users.

There are three scheduling algorithms provided and the operator can decide which algorithm

to take.

MAX C/I

Round Robin

PF (proportional fair)

eRAN7.0




23

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

quality is the only factor to be considered in this algorithm and therefore, the fairness among

users cannot be guaranteed.

With Round Robin, users are scheduled on turn and neglects of their radio quality. So all the

users have the same chance to get the resource and the fairness among uses is guaranteed. But

the system capacity is lowest among three scheduling algorithms.

With PF, users are scheduled according to the value of R/r, where R is the maximum data rate

corresponding to the channel quality, and r is the average data rate of the user. The PF

scheduler, based on the radio channel quality of an individual user, provides the user with an

average throughput proportional to its average channel quality. This algorithm is typically

used by a wireless system to achieve a moderate cell capacity while to ensure fairness among

users.


Round Robin is added in this feature.

Dependency

None

1.2.16 LBFD-002026 Uplink Power Control

Availability

This feature is




Summary

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

transmitting power of UEs. It also controls the interference to the neighboring cells, to

improve the system throughput. Uplink control power applies to Physical Uplink Shared

Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Sounding Reference Signal

(SRS), and Physical Random Access Channel (PRACH).

Benefits

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

controlling the transmitting power of UEs by the eNodeB and therefore, increase the overall

throughput in an LTE system. The uplink power control can also ensure the quality, such as

the block error rate (BLER), of service applications. In addition, uplink power control can

reduce the power consumption of UE

Description

Uplink power control is one of the most important features for an LTE system. By controlling

the UE transmission power carefully, the interference to the neighboring cells can be reduced

eRAN7.0




24

and therefore the overall system throughput is improved. The uplink power control includes

the mechanisms of PUSCH power control, PUCCH power control, SRS power control, and

PRACH power control.

The PUSCH power control includes power adjustment for both Dynamic Scheduling and

Semi-persistent scheduling.

For Dynamic Scheduling:

Based on the difference between the estimated transmission power spectrum density

(PSD) and PSDTarget, the transmitting power of the PUSCH is periodically adjusted

according to the channel environment change. If the estimated PSD is greater than

PSDTarget, the eNodeB sends a TPC command, ordering a decrease of the transmitting

power. If the estimated PSD is smaller than PSDTarget, the eNodeB sends a TPC

command, ordering an increase of the transmitting power.

For Semi-persistent Scheduling:

In Semi-persistent Scheduling, based on the difference between the measured IBLER

and IBLERTarget, the transmitting power of the PUSCH is periodically adjusted

according to the channel environment change. If the measured IBLER is greater than

IBLERTarget, the eNodeB sends a TPC command to the UE, ordering an increase of the

transmitting power. If the measured IBLER is smaller than IBLERTarget, the eNodeB

sends a TPC command to the UE, ordering a decrease of the transmitting power.

The PUSCH TPCs of multiple VoIP users are sent to the UEs through DCI Format 3/3A.

By doing so, signaling overheads over PDCCH are reduced.

For PUCCH power control:

Based on the difference between the measured SINR and SINRTarget, the transmitting

power of the PUCCH is periodically adjusted according to the channel environment

change. If the measured SINR is greater than SINRTarget, the eNodeB sends a TPC

command, ordering a decrease of the transmitting power. If the measured SINR is

smaller than SINRTarget, the eNodeB sends a TPC command, ordering an increase of the

transmitting power.

The uplink SRS power control also employs the same power control mechanism as the

PUSCH power control with identical parameter settings. Note that the initial power is

calculated in the same way as PUSCH, except that a power offset configured by RRC is

added.

For the PRACH power control, the UE will calculate the transmitting power for the initial

Random Access (RA) preamble by estimating the downlink path loss and based on the

aforementioned "expected received power from UE at eNodeB" obtained by monitoring the

broadcast channel. If the RA preamble attempt fails (e.g. no RA preamble response for the

eNodeB), the UE can increase the transmitting power for the next RA preamble attempt

according to the settings configured by the RRC layer.

Enhancement

None

Dependency

None

eRAN7.0




25

1.2.17 LBFD-002016 Dynamic Downlink Power Allocation

Availability

This feature is




Summary

Dynamic Downlink Power Allocation allows an eNodeB to dynamically set the transmitting

power at downlink channels to reduce power consumption while maintaining the quality of

radio links. It provides flexible power allocation for downlink channels based on the user's

channel quality and maintains acceptable quality of the downlink connections.

Benefits

This feature allows flexible power allocation for downlink channels based on the user's

channel quality and maintains acceptable quality of the downlink connections. Therefore, it

can improve the edge user throughput and transmission power usage.

Description

The LTE downlink power allocation consists of several parts corresponding to different types

of downlink channels, such as Physical Downlink Shared Channel (PDSCH), Physical

Downlink Control Channel (PDCCH), Physical HARQ Indicator Channel (PHICH), Physical

Broadcast Channel (PBCH), and Physical Control Format Indicator Channel (PCFICH).

A Fixed power setting is performed for the cell-specific reference signal, synchronization

signal, PBCH, PCFICH, and channels carrying common information of the cell such as

PDCCH and PDSCH; since the transmitting power of those signals and channels are

needed to ensure the downlink coverage of the cell.

SINRRS estimation is based on the CQI report. Based on the difference between the

estimated SINRRS and SINRTarget, the transmitting power of the PHICH is periodically

adjusted according to the path loss and shading. If SINRRS is smaller than SINRTarget,

the transmitting power is increased. Otherwise, the transmitting power is decreased.)

In dynamic scheduling, the power of the PDSCH is determined by PA, and the power

is adjusted by updating PA. When the eNodeB receives a reported CQI from the UE,

it compares it with that reported in the previous time. If there is a great difference

between the two CQI values, the power adjustment is performed, and a process of

re-calculating the PA for the UE is started.

In semi-static scheduling, based on the difference between the measured IBLER of

VoIP packets and IBLERTarget, the transmitting power of the PDSCH is periodically

adjusted to meet IBLERTarget requirements. If the measured IBLER is smaller than

IBLERTarget, the transmitting power is decreased. Otherwise, the transmitting power

is increased. The transmit power for the PDCCH is periodically adjusted according to

the DTX. If the DTX cannot meet system demand, transmit power is increased.


eRAN7.0




26

PDSCH and PDCCH dynamic power control is optimized.

Dependency

None

1.2.18 LBFD-002017 DRX

Availability

This feature is




Summary

In RRC_CONNECTED status, UE working on DRX (Discontinuous Reception) mode

switches the receiver on and off alternately according to the configuration of eNodeB to

continue or suspend the receiving of data and signals from network.

Benefits

This feature is mainly used to reduce the power consumption of UEs.

Description

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

it to discontinuously monitor PDCCH on specific sub-frames.

There are two states in DRX mode, which are active state and sleep state namely DRX state.

During the active time, UE monitor PDCCH for the possible downlink transmission from

network.

Switching between two of the DRX states is not only related with several timers, which are

On Duration timer, DRX Inactivity timer and DRX Retransmission timer but also related

with other some special situation such as that HARQ buffer is not empty, and UE is in RA

response process.

DRX may also be used for CGI measurement in ANR.

Enhancement In eRAN 3.0

Up to 320ms Long DRX cycle in sync is introduced, while up to 40ms Long DRX cycle

in sync was supported in version before.

Dependency

None

eRAN7.0




27

1.2.19 LBFD-002018 Mobility Management

1.2.19.1 LBFD-00201801 Coverage Based Intra-frequency Handover

Availability

This feature is




Summary

Handover functionality is important in any cellular telecommunications network. It is

performed to ensure no disruption to services. Handover plays a significant role in LTE

system performance since its main purpose is to decrease the communication delay, enlarge

the coverage and then enhance the system performance.

Intra-Frequency Handover enables a UE in RRC-CONNECTED mode to be served

continuously when it moves across different cells that are operating at the same frequency.

Benefits

The coverage-based intra-frequency handover feature provides supplementary coverage in

intra-frequency LTE systems to prevent call drop, enable seamless coverage and therefore

improve the network performance and end user experience.

Description

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

is to ensure that a UE in RRC-CONNECTED mode is served continuously when it moves.

Handover in LTE is characterized by the handover procedure in which the original connection

is released before a new connection is set up.

Intra-frequency handover refers to the handover between cells operating at the same

frequency band. It can be triggered by coverage or load. In eRAN1.0, the coverage-based

intra-frequency handover is supported.

The intra-frequency handover procedure can be divided into three phases: handover

measurement, handover decision, and handover execution.

E-UTRAN configures the handover-related measurement through the RRC Connection

Reconfiguration message. The UE could measure either Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ) for intra-frequency handover.

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

according to certain triggering criteria. If a handover is required, the handover execution

procedure will be invoked and the UE will be handed over from the source eNodeB to the

target eNodeB. Huawei eRAN1.0 follows the intra-frequency handover procedures specified

in 3GPP TS 36.300.

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

eRAN7.0




28

Handover between two cells configured in the same eNodeB. No external neighbor cell

is needed. This scenario is not applicable to Micro eNodeB because Micro eNodeB only

supports one cell.

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

available. In this case, the source eNodeB sends a HANDOVER REQUEST message

over the X2 interface.

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

available. In this case, the source eNodeB sends a HANDOVER REQUIRED message

over the S1 interface.


Each PLMN id of eNodeB will have its own PLMN list; each PLMN list can contain at

most 8 PLMN Identities; PLMN list is used as an access list for serving cell to judge

whether UE could handover to target cell in Inter-PLMN handover; Other cell, whose

PLMN ids are all different with serving cell PLMN id in which UE is located and at

same time are not in its PLMN list, will not be considered as target cell in handover

process for this UE.

Dependency

None

1.2.19.2 LBFD-00201802 Coverage Based Inter-frequency Handover

Availability

This feature is




Summary

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

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

Benefits

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

inter-frequency LTE systems to prevent call drop, enable seamless coverage, and therefore

improve the network performance and end user experience.

Description

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

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

continuously when it moves across different cells operating at different frequencies.

The inter-frequency handover procedure can be divided into four phases: measurement

triggering, handover measurement, handover decision, and handover execution.

eRAN7.0




29

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

measurements. The measurement is gap assisted for UEs with one RF receiver. The

measurement is triggered by an event A2 and stopped by an event A1, based on the

monitoring on the value of RSRP or RSRQ.

In inter-frequency handover, the UE sends measurement reports to the eNodeB when the

RSRP or RSRQ meets the criteria set in the measurement configuration.

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

If the measurement meets the handover criteria, the eNodeB will perform the corresponding

inter-frequency handover as specified in TS 36.300.

The following inter-frequency handover scenarios are applicable:

Handover between two cells configured in the same eNodeB. In this case, the UE

performs the handover between two cells configured in the same eNodeB and no

external interface is required. This scenario is not applicable to Micro eNodeB because

Micro eNodeB only supports one cell.

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

available. In this case, the source eNodeB sends a HANDOVER REQUEST message

over the X2 interface.

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

available. In this case, the source eNodeB sends a HANDOVER REQUIRED message

over the S1 interface.

Enhancement eRAN2.2

Each PLMN id of eNodeB will have its own PLMN list; each PLMN list can contain at

most 8 PLMN Identities; PLMN list is used as an access list for serving cell to judge

whether UE could handover to target cell in Inter-PLMN handover; Other cell, whose

PLMN ids are all different with serving cell PLMN id in which UE is located and at

same time are not in its PLMN list, will not be considered as target cell in handover

process for this UE.

eRAN3.0

The inter-frequency handover based on UL power is supported. It guarantees service

continuity in uplink limited power when a UE moves to the cell edge.

eRAN6.0

The urgent redirection function has been provided by this feature. After a UE accesses a

cell, the eNodeB delivers two sets of event A2 configurations. One is used for triggering

measurements, and the other is used for triggering urgent redirection. The triggering of

event A2 for urgent redirection indicates that the signal quality in the serving cell has

become too poor to provide services for the UE. In this case, the eNodeB blindly

redirects the UE to a neighboring GERAN, UTRAN, or E-UTRAN cell.

Dependency UE

UE should support for inter-frequency Gap measurements

eRAN7.0




30

1.2.19.3 LBFD-00201803 Cell Selection and Re-selection

Availability

This feature is




Summary

Cell selection/reselection is a mechanism for UE in idle mode to select/reselect a cell to camp

on and to receive the most appropriate service support upon session activation in LTE

systems.

Benefits

This feature provides a mechanism for UE in idle mode to select/reselect a cell to camp on by

supplementary coverage in LTE systems.

This feature facilitates the automatic selection of the network for UE in idle mode and avoids

the complexity of manual operations.

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

Description

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

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

cell selection should be performed, for instance, by indicating the RAT(s) associated with the

selected PLMN and by maintaining a list of forbidden registration areas and a list of

equivalent PLMN. The UE shall select a suitable cell based on idle mode measurements and

cell selection criteria.

UE in RRC_IDLE can perform cell reselection if UE find a cell with a better radio

environment. When camping on a cell, UE shall regularly search for a better cell according to

the cell reselection criteria. If a better cell is found, that cell is reselected.

Absolute priorities of different E-UTRAN frequencies can be provided to the UE in the

system information and optionally in the RRC message releasing the RRC connection.

Compared with Macro eNodeBs, higher priorities will be set for frequencies of Micro

eNodeBs so that the UE prefers to camp on Micro eNodeB cells.

In case a Micro cell is on the same frequency with a Macro cell, the eNodeB configuration

also makes the cell selection or reselection to the Micro cell easier than to the Macro cell.

Enhancement

None

Dependency

None

eRAN7.0




31

1.2.19.4 LBFD-00201804 Distance Based Inter-frequency Handover

Availability

This feature is


not applicable to Micro

not applicable to Lampsite

Summary

Huawei LTE eNodeB supports distance based inter-frequency handover.

Benefits

Better End user Experience (Always Best Connected)

Description

When moving around away from the serving eNodeB with frequency F1, the user may still

experience a relatively strong signal from F1 so that the condition of A2 event can't be

satisfied to trigger an inter-frequency handover, even though the neighboring inter-frequency

eNodeB signal is much better than F1. In order to make the user always keep the best

connection, a distance based inter-frequency handover is employed.

When distance based HO algorithm is used, eNodeB should continuously measure the

distance to each UE based on the TA measurement, once the distance exceeds an operator

configured distance threshold, inter-frequency gap measurements of neighboring eNodeB will

be triggered to find an optimal handover candidate to improv

eran7.0 lte fdd basic feature description 01 20140915.pdf

Documents

huawei trademarks

huawei proprietary

huawei industrial base

basic features

v100r007c00 eran7

gpp r8 specifications

gpp r9 specifications

gpp r10 specifications