Huawei LTE eRAN2.1 Feature Description.doc

eRAN2.1 Feature Description

Issue V1.0

Date 09/25/2010

HUAWEI TECHNOLOGIES CO., LTD.

Feature Description of Huawei LTE eRAN2.1

Copyright © Huawei Technologies Co., Ltd. 2010. 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 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

HUAWEI CONFIDENTIAL i

mailto:[email protected]

http://www.huawei.com/


Contents

1 Basic Features Description...................................................11.1 LBFD-001001 3GPP R8 Specifications..........................................................................................1

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

1.3 LBFD-001002 FDD mode...............................................................................................................2

1.4 LBFD-001003 Scalable Bandwidth.................................................................................................3

1.5 LBFD-001004 CP length.................................................................................................................4

1.5.1 LBFD-00100401 Normal CP.................................................................................................4

1.6 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM....................................5

1.7 LBFD-001006 AMC........................................................................................................................6

1.8 LBFD-002001 Logical Channel Management................................................................................7

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

1.10 LBFD-002003 Physical Channel Management...........................................................................11

1.11 LBFD-002004 Integrity Protection..............................................................................................12

1.12 LBFD-002005 DL Asynchronous HARQ...................................................................................13

1.13 LBFD-002006 UL Synchronous HARQ.....................................................................................14

1.14 LBFD-002007 RRC Connection Management...........................................................................16

1.15 LBFD-002008 Radio Bearer Management..................................................................................17

1.16 LBFD-002009 Broadcast of System Information........................................................................17

1.17 LBFD-002010 Random Access Procedure..................................................................................19

1.18 LBFD-002011 Paging..................................................................................................................20

1.19 LBFD-002012 Cell Access Radius up to 15km...........................................................................21

1.20 LBFD-002023 Admission Control..............................................................................................22

1.21 LBFD-002024 Congestion Control.............................................................................................24

1.22 LBFD-002025 Basic Scheduling.................................................................................................25

1.23 LBFD-002026 Uplink Power Control.........................................................................................26

1.24 LBFD-002016 Dynamic Downlink Power Allocation................................................................27

1.25 LBFD-002017 DRX....................................................................................................................28

1.26 LBFD-002018 Mobility Management.........................................................................................30

1.26.1 LBFD-00201801 Coverage Based Intra-frequency Handover...........................................30

1.26.2 LBFD-00201802 Coverage Based Inter-frequency Handover...........................................31

1.26.3 LBFD-00201803 Cell Selection and Reselection..............................................................32

HUAWEI CONFIDENTIAL i


1.27 LBFD-002022 Static Inter-Cell Interference Coordination.........................................................33

1.27.1 LBFD-00202201 Downlink Static Inter-Cell Interference Coordination..........................33

1.27.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination...............................34

1.28 LBFD-002020 Antenna Configuration........................................................................................36

1.28.1 LBFD-00202001 UL 2-Antenna Receive Diversity...........................................................36

1.29 LBFD-002021 Reliability............................................................................................................37

1.29.1 LBFD-00202101 Main Processing and Transport Unit Cold Backup...............................37

1.29.2 LBFD-00202102 Cell Rebuild between Baseband Processing Units................................37

1.29.3 LBFD-00202103 SCTP Multi-homing...............................................................................39

1.29.4 LBFD-00202104 Intra-baseband Card Resource Pool(user level/cell level).....................40

1.30 LBFD-002027 Support of UE Category 1..................................................................................41

1.31 LBFD-002028 Emergency Call...................................................................................................42

1.32 LBFD-003001 Transport Networking.........................................................................................44

1.32.1 LBFD-00300101 Star Topology.........................................................................................44

1.32.2 LBFD-00300102 Chain Topology......................................................................................45

1.32.3 LBFD-00300103 Tree Topology........................................................................................46

1.33 LBFD-003002 Basic QoS Management......................................................................................47

1.33.1 LBFD-00300201 DiffServ QoS Support............................................................................47

1.34 LBFD-003003 VLAN Support (IEEE 802.1p/q).........................................................................48

1.35 LBFD-003004 Compression and Multiplexing over E1/T1........................................................49

1.35.1 LBFD-00300401 IP Header Compression.........................................................................49

1.35.2 LBFD-00300402 PPP MUX...............................................................................................50

1.35.3 LBFD-00300403 ML-PPP/MC-PPP..................................................................................51

1.36 LBFD-003005 Synchronization...................................................................................................52

1.36.1 LBFD-00300501 Clock Source Switching Manually or Automatically............................52

1.36.2 LBFD-00300502 Free-running Mode................................................................................53

1.36.3 LBFD-00300503 Synchronization with GPS.....................................................................53

1.36.4 LBFD-00300504 Synchronization with BITS...................................................................54

1.36.5 LBFD-00300505 Synchronization with 1PPS...................................................................55

1.36.6 LBFD-00300506 Synchronization with E1/T1..................................................................56

1.37 LBFD-004001 Local Maintenance on the LMT..........................................................................56

1.38 LBFD-004002 Centralized M2000 Management........................................................................57

1.39 LBFD-004003 Security Socket Layer.........................................................................................58

1.40 LBFD-004004 Software Version Upgrade Management............................................................59

1.41 LBFD-004005 Hot Patch Management.......................................................................................60

1.42 LBFD-004006 Fault Management...............................................................................................61

1.43 LBFD-004007 Configuration Management................................................................................62

1.44 LBFD-004008 Performance Management..................................................................................63

1.45 LBFD-004009 Real-time Monitoring of System Running Information......................................65

1.46 LBFD-004010 Security Management..........................................................................................66

1.47 LBFD-004011 Optimized eNodeB Commissioning Solution.....................................................66

HUAWEI CONFIDENTIAL ii


1.48 LBFD-004012 Environment Monitoring.....................................................................................67

1.49 LBFD-004013 Inventory Management.......................................................................................68

1.50 LBFD-004014 License Management..........................................................................................69

2 Optional Features Description............................................712.1 LOFD-001001 DL 2x2 MIMO......................................................................................................71

2.2 LOFD-001002 UL 2x2 MU-MIMO..............................................................................................72

2.3 LOFD-001003 DL 4x2 MIMO......................................................................................................73

2.4 LOFD-001005 UL 4-Antenna Receive Diversity..........................................................................74

2.5 LOFD-001006 UL 64QAM...........................................................................................................75

2.6 LOFD-001012 UL Interference Rejection Combining..................................................................76

2.7 LOFD-001014 Dynamic Inter-Cell Interference Coordination.....................................................77

2.7.1 LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination.......................77

2.7.2 LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination............................78

2.8 LOFD-001007 High Speed Mobility.............................................................................................79

2.9 LOFD-001008 Ultra High Speed Mobility....................................................................................80

2.10 LOFD-001009 Extended Cell Access Radius..............................................................................81

2.11 LOFD-001030 Support of UE Category 2/3/4............................................................................82

2.12 LOFD-001031 Extended CP........................................................................................................83

2.13 LOFD-001048 TTI Bundling......................................................................................................84

2.14 LOFD-001015 Enhanced Scheduling..........................................................................................85

2.14.1 LOFD-00101501 CQI Adjustment.....................................................................................85

2.14.2 LOFD-00101502 Dynamic Scheduling..............................................................................86

2.15 LOFD-001016 VoIP Semi-persistent Scheduling........................................................................88

2.16 LOFD-001017 RObust Header Compression (ROHC)...............................................................89

2.17 LOFD-001026 TCP Proxy Enhancer...........................................................................................90

2.18 LOFD-001027 Acitve Queue Management (AQM)....................................................................92

2.19 LOFD-001029 Enhanced Admission Control.............................................................................93

2.19.1 LOFD-00102901 Radio/transport Resource Pre-emption..................................................93

2.20 LOFD-001038 RRU Channel Cross Connection Under MIMO.................................................94

2.21 LOFD-001018 S1-flex.................................................................................................................96

2.22 LOFD-001047 LoCation Services (LCS)....................................................................................98

2.23 LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN.................................99

2.24 LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN...............................101

2.25 LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000.........................103

2.26 LOFD-001022 SRVCC to UTRAN...........................................................................................105

2.27 LOFD-001023 SRVCC to GERAN...........................................................................................106

2.28 LOFD-001032 Intra-LTE Load Balancing................................................................................108

2.29 LOFD-001044 Inter-RAT Load Sharing to UTRAN.................................................................109

2.30 LOFD-001045 Inter-RAT Load Sharing to GERAN.................................................................110

2.31 LOFD-001043 Service based inter-RAT handover to UTRAN.................................................111

HUAWEI CONFIDENTIAL iii


2.32 LOFD-001046 Service based inter-RAT handover to GERAN.................................................112

2.33 LOFD-001033 CS Fallback to UTRAN....................................................................................113

2.34 LOFD-001034 CS Fallback to GERAN....................................................................................114

2.35 LOFD-001035 CS Fallback to CDMA2000 1xRTT..................................................................115

2.36 LOFD-001036 RAN Sharing with Common Carrier................................................................116

2.37 LOFD-001037 RAN Sharing with Dedicated Carrier...............................................................118

2.38 LOFD-001024 Remote Electrical Tilt Control..........................................................................119

2.39 LOFD-001025 Adaptive Power Consumption..........................................................................120

2.40 LOFD-001039 RF Channel Intelligent Shutdown.....................................................................121

2.41 LOFD-001040 Low Power Consumption Mode.......................................................................122

2.42 LOFD-001041 Power Consumption Monitoring.......................................................................123

2.43 LOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage..................................124

2.44 LOFD-002001 Automatic Neighbor Relation (ANR)...............................................................125

2.45 LOFD-002002 Inter-RAT ANR.................................................................................................127

2.46 LOFD-002004 Self-configuration.............................................................................................129

2.47 LOFD-002005 Mobility Robust Optimization (MRO).............................................................132

2.48 LOFD-002007 PCI Collision Detection & Self-Optimization..................................................133

2.49 LOFD-002010 Sleeping Cell Detection....................................................................................134

2.50 LOFD-002011 Antenna Fault Detection....................................................................................135

2.51 LOFD-002012 Cell Outage Detection and Compensation........................................................136

2.52 LOFD-001010 Security Mechanism..........................................................................................137

2.52.1 LOFD-00101001 Encryption: AES..................................................................................137

2.52.2 LOFD-00101002 Encryption: SNOW 3G........................................................................138

2.53 LOFD-003002 2G/3G and LTE Co-transmission......................................................................139

2.54 LOFD-003004 Ethernet OAM...................................................................................................141

2.54.1 LOFD-00300401 Ethernet OAM(802.3ah)......................................................................141

2.54.2 LOFD-00300402 Ethernet OAM(802.1ag)......................................................................142

2.55 LOFD-003007 Bidirectional Forwarding Detection.................................................................142

2.56 LOFD-003005 OM Channel Backup.........................................................................................144

2.57 LOFD-003006 IP Route Backup...............................................................................................144

2.58 LOFD-003008 Ethernet Link Aggregation (802.3ad)...............................................................145

2.59 LOFD-003009 IPSec.................................................................................................................146

2.60 LOFD-003010 Public Key Infrastructure (PKI)........................................................................148

2.61 LOFD-003015 Access Control based on 802.1x.......................................................................149

2.62 LOFD-003014 Integrated Firewall............................................................................................150

2.62.1 LOFD-00301401 ACL.....................................................................................................150

2.63 LOFD-003011 Enhanced Transport QoS Management.............................................................151

2.63.1 LOFD-00301101 Transport Overbooking........................................................................151

2.63.2 LOFD-00301102 Transport Differentiated Flow Control................................................152

2.63.3 LOFD-00301103 Transport Resource Overload Control.................................................153

2.64 LOFD-003012 IP Performance Monitoring..............................................................................154

HUAWEI CONFIDENTIAL iv


2.64.1 LOFD-00301201 IP Performance Monitoring.................................................................154

2.64.2 LOFD-00301202 Transport Dynamic Flow Control........................................................155

2.65 LOFD-003016 Different Transport Paths based on QoS Grade................................................155

2.66 LOFD-003013 Enhanced Synchronization................................................................................156

2.66.1 LOFD-00301301 Synchronization with Ethernet (ITU-T G.8261).................................156

2.66.2 LOFD-00301302 IEEE1588 V2 Clock Synchronization.................................................157

2.66.3 LOFD-00301303 Clock over IP (Huawei Proprietary)....................................................160

2.67 LTE Multi-mode Common Transmission..................................................................................162

2.67.1 MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)...............162

2.68 LTE Multi-mode Common Reference Clock.............................................................................166

2.68.1 MRFD-231601 Multi-mode BS Common Reference Clock(eNodeB)............................166

3 Acronyms and Abbreviations............................................................170

HUAWEI CONFIDENTIAL v


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

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

Figure 1-7 Stream Control Transmission Protocol.............................................................................39

Figure 1-8 Star topology.....................................................................................................................44

Figure 1-9 Chain topology..................................................................................................................45

Figure 1-10 Tree topology..................................................................................................................46

Figure 1-11 ML-PPP/MC-PPP............................................................................................................51

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

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

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

Figure 2-4 CS fallback in EPS architecture......................................................................................112



Figure 2-7 Automatic neighbor relation function.............................................................................125

Figure 2-8 Inter-RAT ANR function.................................................................................................127

Figure 2-9 general network topology................................................................................................130

Figure 2-10 2G/3G and LTE co-transmission...................................................................................141

Figure 2-11 the one-hop and multi-hop BFD application scenarios.................................................144

Figure 2-12 the Ethernet link aggregation........................................................................................147

Figure 2-13 IPSec.............................................................................................................................148

Figure 2-14 eRAN certificate application scenario..........................................................................149

HUAWEI CONFIDENTIAL vi


Figure 2-15 eRAN 802.1x application scenario...............................................................................150

Figure 2-16 Basic principle of the Synchronization with Ethernet...................................................158

Figure 2-17 basic principle defined by the IEEE1588 protocol......................................................159

Figure 2-18 synchronization principle of the IEEE1588 protocol...................................................160

Figure 2-19 Framework of Huawei proprietary protocol.................................................................162

HUAWEI CONFIDENTIAL vii


Tables

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

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

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

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

HUAWEI CONFIDENTIAL Page 1 of 196


Change History

Date Version Description Author

05/14/2010 1.0 PDCP release LTE Team

05/17/2010 LBFD-00300504 Synchronization with BITS re-added

08/20/2010 remove LOFD-002013 RF Parameter Automatic Optimization. Change LOFD-002012 from Cell Outage Detection and Compensation to Cell Outage Detection. Add LOFD-001047 TTI Bundling

09/08/2010 2 LTE Multi-mode optional feaures added

09/08/2010 5 features’ description updated by performance team for Aug. 2010.

09/25/2010 Updated according to review comments of 2010 Aug. FL/FD review



1 Basic Features Description

1.1 LBFD-001001 3GPP R8 Specifications

Availability

This feature is available from eRAN1.0.

Summary

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

Benefits

None

Description


Huawei is an active participant and great contributor to 3GPP specification development. This high-level involvement enables Huawei to actively contribute, and closely follow 3GPP standard development during Huawei product development. LTE eNodeB supports 3GPP Release 8 2009Q3.

Enhancement

None

Dependency

None



1.2 LBFD-001007 3GPP R9 Specifications

Availability


Summary


Benefits

None

Description


Huawei is an active participant and great contributor to 3GPP specification development. This high-level involvement enables Huawei to actively contribute, and closely follow 3GPP standard development during Huawei product development. LTE eNodeB supports 3GPP Release 2010Q1, which is the latest version of LTE standard.

Enhancement

None

Dependency

None

1.3 LBFD-001002 FDD mode

Availability


Summary

Huawei LTE eRAN2.0 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.4 LBFD-001003 Scalable Bandwidth

Availability


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.

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.

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

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

UEs should support the same bandwidth as the eNodeB.



1.5 LBFD-001004 CP length

1.5.1 LBFD-00100401 Normal CP

Availability


Summary

In an OFDM symbol, the Cyclic Prefix (CP) is a time-domain replication of the end of the symbol and is appended to the beginning of the symbol. It provides the guard interval in the OFDM to decrease the inter-symbol interference due to the multipath delay.

Benefits

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

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

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

Enhancement

None

Dependency

UEs should support the same CP length as the eNodeB.



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

Availability


Summary

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

Benefits

This feature provides a wide range of modulation schemes to be chosen based on the channel condition. Higher-order modulation schemes, such as DL 64QAM, can be used under excellent channel conditions to achieve higher data rates, which improves the system throughput and spectrum efficiency.

Description

This feature provides a wide range of modulation schemes that can be used by both the eNodeB and the UE in uplink and downlink.

The following modulation schemes are supported:

Uplink/downlink Quadrature Phase Shift Keying (QPSK)

Uplink/downlink 16 Quadrature Amplitude Modulation (16QAM)

Downlink 64QAM

The characteristics are as follows:

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

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

64QAM allows up to six information bits modulated per symbol due to 64 different 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.

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

For example, when a UE is in a poor radio environment, it may use a low-order QPSK modulation scheme for uplink transmission to meet the requirement of the call quality. When a UE is in an excellent radio environment, it can use a high-order QAM modulation (such as 16QAM) scheme for uplink transmission to achieve high bit rates.



Enhancement

None

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.7 LBFD-001006 AMC

Availability


Summary

The Adaptive Modulation and Coding (AMC) function allows an eNodeB to adaptively select the optimal Modulation and Coding Scheme (MCS) according to the channel condition. This improves the spectrum efficiency after the system resource and transmit power are fixed. Therefore, the throughput can be maximized and the Quality of Service (QoS) requirements can be met.

Benefits

The AMC provides the following benefits:

Maximizes the system throughput by selecting the optimal MCS.

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

Description

The AMC function allows an eNodeB to adaptively select the optimal MCS according to the channel information. This improves the spectrum efficiency after the system resource and 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. Then, the MCS may be adjusted according to the received uplink Sounding Reference Signal (SRS) or Demodulation Reference Signal (DMRS). 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

Dependency

None

1.8 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 defined according to the type of the transmitted data. They are generally classified into two types: control channels and traffic channels.

In Huawei LTE eRAN2.0, 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)



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

I. In the uplink,

CCCH can be mapped to UL-SCH.

DCCH can be mapped to UL-SCH.

DTCH can be mapped to UL-SCH.

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

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

II. In the downlink

BCCH can be mapped to BCH.

BCCH can be mapped to DL-SCH.

PCCH can be mapped to PCH.

CCCH can be mapped to DL-SCH.

DCCH can be mapped to DL-SCH.

DTCH can be mapped to DL-SCH.

MTCH can be mapped to DL-SCH.

MTCH can be mapped to MCH.

MCCH can be mapped to DL-SCH.

MCCH can be mapped to MCH.

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



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

In Huawei LTE eRAN2.0, all logical channels are supported except those related to the eMBMS functionality, such as MCCH and MTCH.

Enhancement

None

Dependency

None

1.9 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 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 eRAN2.0, 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)

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

In the uplink,

UL-SCH can be mapped to PUSCH.

RACH can be mapped to PRACH.

Figure 1-1 depicts the mapping between uplink transport and uplink physical channels:

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

In the downlink,

DL-SCH can be mapped to PDSCH.

BCH can be mapped to PBCH.

PCH can be mapped to PDSCH.

MCH can be mapped to PMCH.

Figure 1-2 depicts the mapping between downlink transport and downlink physical channels:



Figure 1-2 Mapping between downlink transport channels and downlink physical channels

In Huawei LTE eRAN2.0, all transport channels are supported except those related to the eMBMS functionality, such as MCH.

Enhancement

None

Dependency

None

1.10 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 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 eRAN2.0, all physical channels are supported except those related to the eMBMS functionality, such as PMCH.

Benefits

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



Description

Each physical channel corresponds to a set of resource elements carrying the information from higher layers.

Downlink physical channels are classified into the following types:

Physical Broadcast Channel (PBCH)

Physical Control Format Indicator Channel (PCFICH)

Physical Downlink Control Channel (PDCCH)

Physical Hybrid ARQ Indicator Channel (PHICH)

Physical Downlink Shared Channel (PDSCH)

Physical Multicast Channel (PMCH)

Uplink physical channels are classified into the following types:

Physical Uplink Control Channel (PUCCH)

Physical Uplink Shared Channel (PUSCH)

Physical Random Access Channel (PRACH)

In Huawei LTE eRAN2.0, all physical channels are supported except those related to the eMBMS functionality, such as PMCH.

Enhancement

None

Dependency

None

1.11 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 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

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) by using 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 the message. If the two codes are inconsistent, the receiver knows that the message has been modified illegally.

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

Enhancement

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

Dependency

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

1.12 LBFD-002005 DL Asynchronous HARQ

Availability


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. 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 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 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.13 LBFD-002006 UL Synchronous HARQ

Availability


Summary

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

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 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 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. When a retransmission occurs, UL HARQ information will indicate whether the data belongs to the retransmitted data and its corresponding RV. After the retransmitted data is received, according to its RV, HARQ process in the eNodeB will soft-combine the retransmitted data with the previously buffered content and forward the combined data to the FEC for decoding. The soft-combined data will help increase the probability of successful FEC decoding, thus increasing the data reception success rate.



In LTE specifications, multiple uplink HARQ processes are adopted to fully utilize system resources. It greatly improves the system throughput and reduces the latency, but it requires more buffer space and signaling overhead.

Enhancement

In eRAN2.0, Huawei supports a synchronous adaptive UL HARQ transmission. While in eRAN1.0, Uplink HARQ is a synchronization non-adaptive transmission process.

Dependency

None

1.14 LBFD-002007 RRC Connection Management

Availability


Summary

RRC connection is the layer 3 connection between the UE and eNodeB. The RRC connection management aims to manage the layer 3 connection, including establishment, maintenance, and release of the connection.

Benefits

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

Description

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

RRC connection establishment: This procedure is performed to establish an RRC connection. RRC connection establishment involves Signaling Radio Bearer 1 (SRB1) establishment. The procedure is also used to transmit the initial NAS dedicated information or messages from the UE to the E-UTRAN.

RRC connection reconfiguration: This procedure is performed to modify an RRC connection, for example, to establish, modify, or release radio bearers, to perform handovers, and to configure or modify measurements. As a part of the procedure, NAS dedicated information may be transmitted from the E-UTRAN to the UE.

RRC connection re-establishment: This procedure is performed to re-establish an RRC connection after a handover failure or radio link failure. RRC connection re-establishment involves the restoration of SRB1 operation and



the re-activation of security. A UE in RRC_CONNECTED mode, for which security has been activated, may initiate the procedure 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.15 LBFD-002008 Radio Bearer Management

Availability


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

Dependency

None



1.16 LBFD-002009 Broadcast of System Information

Availability


Summary

System information (SI) includes:

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

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

Information about neighboring cells

Important messages that should be send 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);

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 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 they can be identified through the System Information RNTI (SI-RNTI). Both the MIB and SystemInformationBlockType1 use a fixed schedule within a period of 40 and 80 ms respectively while the scheduling of other SI messages is flexible and indicated by SystemInformationBlockType1.

The eNodeB may schedule DL-SCH transmissions concerning logical channels other than BCCH in the same subframe as used for BCCH. The minimum UE capability restricts the BCCH mapped to DL-SCH, for example, regarding the maximum 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 eRAN2.0 supports MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, and SIB8.

Enhancement

None

Dependency

None

1.17 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 is performed for the following five events:

Initial access from RRC_IDLE

RRC Connection Re-establishment procedure

Handover

DL data arrival during RRC_CONNECTED requiring random access procedure

UL data arrival during RRC_CONNECTED requiring random access procedure

Benefits

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

Description

The random access procedure enables the UE to establish uplink timing synchronization and to request for setup of a connection to an eNodeB.

The procedure can be either contention-based (applicable to all the preceding five events) or non-contention-based (applicable to only handover and DL data arrival). Normal DL/UL transmission may occur after the random access procedure.

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

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

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

After receiving the Random Access Response, the UE performs the first scheduled UL transmission over the UL-SCH.

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 has successfully accessed the network.

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

The eNodeB assigns the Random Access Preamble and PRACH resource through dedicated signaling to request the UE to initiate the random access procedure.

The UE transmits the assigned Random Access Preamble over the assigned PRACH.

The eNodeB transmits a Random Access Response after receiving the Random Access Preamble. Then, the UE successfully accesses the network when it receives the Random Access Response.



Huawei eNodeB supports the two types of random access procedures. In addition, Huawei eNodeB supports random access preamble formats 0–3 and PRACH configurations 0–63 (TS 36.211).

Enhancement

None

Dependency

None

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

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 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.19 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, and 3), 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, and 3) for PRACH are defined to support different values of cell access radius, as shown in Table 1-1.

Table 1-1 Preamble formats and cell access radius

Preamble Format

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 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.20 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:

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 available transmission bandwidth, 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 mistakenly rejecting a service request due to low QoS satisfaction ratio when there are a lot of idle 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 be accepted 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 is mapped to one of the five QoS classes defined at cell level: Conversational Voice, Buffered Streaming, IMS signaling, Guaranteed Bit Rate (GBR), and Non-GBR. 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

None

Dependency

None

1.21 LBFD-002024 Congestion Control

Availability


Summary

The congestion control feature is used to adjust the system loading when the system is in congestion or the QoS cannot be met.

The main goal of congestion control feature is to guarantee the QoS for the admitted services while achieving the maximum radio resource utilization.

Benefits

The congestion control feature provides the following benefits:

Prevent system from being unstable due to overload;

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

Description

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

The load measures include the power, the available physical resource block at the air interface, 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 to the service.

The second method is GBR downsizing. The basic idea behind the GBR downsizing is to slightly reduce the guaranteed data rate for all Guaranteed Bit Rate (GBR) services but still above the minimum bit rate. By sacrificing the quality of GBR services slightly but still maintaining acceptable quality, it might



improve the overall QoS satisfaction ratio. The GBR services could be divided into 3 groups: Gold, Silver, and Bronze with different thresholds. GBR downsizing will start firstly with Bronze group when congestion happens.

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

Enhancement

None

Dependency

None

1.22 LBFD-002025 Basic Scheduling

Availability


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)

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

With PF, users are scheduled according to the value of R/r, where R is the maximum data rate corresponding to the channel quality, and r is the average data rate of the user. The PF scheduler, based on the radio channel quality of an individual user, provides the user with an average throughput proportional to its average channel quality. This algorithm is typically used by a wireless system to achieve a moderate cell capacity while to ensure fairness among users.

Enhancement

Round Robin is added in this feature from eRAN 2.0.

Dependency

None

1.23 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 cells, to improve the system throughput. Uplink control power applies to Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), and Physical Random Access Channel (PRACH).

Benefits

The uplink power control can reduce the interference between neighboring cells by carefully controlling the transmit power of UEs by the eNodeB and therefore, increase the overall throughput in an LTE system. The uplink power control can also ensure the quality, such as the block error rate (BLER), of service applications. In addition, uplink power control can reduce the power consumption of UE

Description

Uplink power control is one of the most important features for an LTE system. It 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 measured SINR and SINRTarget, the transmit power of the PUSCH is periodically adjusted according to the channel environment change. If the measured SINR is greater than SINRTarget, the eNodeB sends a TPC command, ordering a decrease of the transmit power. If the measured SINR is smaller than SINRTarget, the eNodeB sends a TPC command, ordering an increase of the transmit power.

Based on the OI information from the neighboring cell, the power headroom (PH) information of the current UE, its number of scheduled RBs, and some other measured values, like SINRTarget, are periodically adjusted.

From eRAN2.0, a new close loop power control scheme is adopted. Based on the OI information from the neighboring cell, the power headroom (PH) information of the current UE, its number of scheduled RBs, this scheme controls UE transmission power spectrum density to make UE throughput more stable and obtain better system throughputs.

For Semi-persitent Scheduling: In Semi-persistent Scheduling, based on the difference between the

measured IBLER and IBLERTarget, the transmit power of the PUSCH is periodically adjusted according to the channel environment change. If the measured IBLER is greater than IBLERTarget, the eNodeB sends a TPC command to the UE, ordering an increase of the transmit power. If the measured IBLER is smaller than IBLERTarget, the eNodeB sends a TPC command to the UE, ordering a decrease of the transmit power.

The PUSCH TPCs of multiple VoIP users are sent to the UEs through DCI Format 3/3A. By doing so, signaling overheads over PDCCH are reduced.

The PUCCH power control employs the same power controlling mechanism 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 as the PUSCH power control with identical parameter settings. Note that the initial power is calculated in the same way as PUSCH, except that a power offset configured by RRC is added.

For the PRACH power control, the UE will calculate the transmit power for the initial Random Access (RA) preamble by estimating the downlink path loss and based on the aforementioned “expected received power from UE at eNodeB” obtained by monitoring the broadcast channel. If the RA preamble attempt fails (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.24 LBFD-002016 Dynamic Downlink Power Allocation

Availability


Summary

Dynamic Downlink Power Allocation allows an eNodeB to dynamically set the transmit power at downlink channels to reduce power consumption while maintaining the quality of radio links. It provides flexible power allocation for downlink channels based on the user’s channel quality and maintains acceptable quality of the downlink connections.

Benefits

This feature allows flexible power allocation for downlink channels based on the user’s channel quality and maintains acceptable quality of the downlink connections. Therefore, it can improve the edge user throughput and transmission power usage.

Description

The LTE downlink power allocation consists of several parts corresponding to different types of downlink channels, such as Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical HARQ Indicator Channel (PHICH), Physical Broadcast Channel (PBCH), and Physical Control Format Indicator Channel (PCFICH).

A Fixed power setting is performed for the cell-specific reference signal, synchronization signal, PBCH, PCFICH, and channels carrying common information of the cell such as PDCCH and PDSCH; since the transmit power of those signals and channels are needed to ensure the downlink coverage of the cell.

SINRRS estimation is based on the CQI report. Based on the difference between the estimated SINRRS and SINRTarget, the transmit power of the PHICH is periodically adjusted according to the path loss and shading. If SINRRS is smaller than SINRTarget, the transmit power is increased. Otherwise, the transmit power is decreased.）

In dynamic scheduling, the power of the PDSCH is determined by PA, and the power is adjusted by updating PA. When the eNodeB receives a reported CQI from the UE, it compares it with that reported in the previous time. If there exist a great difference between the two CQI values, the power adjustment is performed, and a process of re-calculating the PA for the UE is started. In semi-static scheduling, based on the difference between the measured IBLER of VoIP packets and IBLERTarget, the transmit power of the PDSCH is periodically adjusted to meet IBLERTarget requirements. If the measured IBLER is smaller than IBLERTarget, the transmit power is decreased. Otherwise, the transmit power is increased.



Enhancement

In eRAN1.0, PDSCH and PDCCH support dynamic power control.

In eRAN2.0, PDSCH and PDCCH dynamic power control have been optimized.

Dependency

None

1.25 LBFD-002017 DRX

Availability


Summary

DRX(Discontinuous Reception) is a working mode in RRC_CONNECTED, in which UE switching 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 reduces the power consumption of UEs and enhances the usage of system 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 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, DRX Retransmission timer and Contention Resolution Timer but also related with other some special situation such as that HARQ buffer is not empty, and UE is in RA response process.

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

The On Duration timer: specifies the number of consecutive PDCCH-sub-frame(s) during which the UE shall monitor the PDCCH for possible allocations. The On Duration timer is a part of a DRX Cycle.



Figure 1-1 DRX cycle

UE shall monitor PDCCH

On Duration

DRX Cycle

Opportunity for DRX

The DRX Inactivity timer: specifies the number of consecutive PDCCH-sub-frame (s), the timer is started or re-started when the UE shall monitor the PDCCH after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.

The DRX Retransmission timer: specifies the maximum number of consecutive PDCCH-sub-frame (s) during which the UE shall monitor the PDCCH for as soon as a DL retransmission is expected by the UE.

The Contention Resolution Timer: Specifies the number of consecutive PDCCH-sub-frame (s) during which the UE shall monitor the PDCCH after the uplink message containing the C-RNTI MAC control element or the uplink message associated with UE Contention Resolution Identity submitted from upper layer is transmitted.

Enhancement

None

Dependency

None

1.26 LBFD-002018 Mobility Management

1.26.1 LBFD-00201801 Coverage Based Intra-frequency Handover

Availability


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

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

Handover between two cells configured in different eNodeBs with an X2 interface available. In this case, the source eNodeB sends a HANDOVER REQUEST message over the X2 interface.

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

Enhancement

None



Dependency

None

1.26.2 LBFD-00201802 Coverage Based Inter-frequency Handover

Availability


Summary

Inter-Frequency Handover enables a UE in connected mode to be served continuously when it moves across different cells that are operating at different frequencies.

Benefits

The coverage-based inter-frequency handover 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.

In inter-frequency handover, neighboring cell measurements are inter-frequency measurements. The measurement is gap assisted for UEs with one RF receiver. The measurement is triggered by an event A2 and stopped by an event A1, based on the monitoring on the value of RSRP or RSRQ.

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

Upon receiving a measurement report from the UE, the eNodeB makes a handover decision. If the measurement meets the handover criteria, the eNodeB will perform the corresponding inter-frequency handover as specified in TS 36.300.

The following inter-frequency handover scenarios are applicable:

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

Handover between two cells configured in different eNodeBs with an X2 interface available. In this case, the source eNodeB sends a HANDOVER REQUEST message over the X2 interface.



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

Enhancement

None

Dependency

None

1.26.3 LBFD-00201803 Cell Selection and Reselection

Availability


Summary

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

Benefits

This feature provides a mechanism for UE in idle mode to select/reselect a cell to camp 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.



Enhancement

None

Dependency

None

1.27 LBFD-002022 Static Inter-Cell Interference Coordination

1.27.1 LBFD-00202201 Downlink Static Inter-Cell Interference Coordination

Availability


Summary

The downlink static inter-cell interference coordination function is used to reduce the downlink inter-cell interference. The basic principle is that the cell edge users of different neighboring cells are allocated with non-overlapping frequency bands by static configuration so as to mitigate frequency interference.

Benefits

The downlink ICIC feature reduces the downlink inter-cell interference, therefore improves cell edge user’s throughput.

Description

In a LTE system, a cell can use the entire system frequency band and therefore it is inevitable to cause inter-cell interference for a multi-cell deployment, particularly at the cell edge area. It is important to develop an efficient solution to mitigate the inter-cell interference in the multi-cell environment in order to achieve the performance target. A common solution is to coordinate the transmission frequency bands among neighboring cells to reduce the inter-cell interference.

In Huawei downlink static ICIC solution, for each cell, a fixed portion of the system frequency band is allocated to the cell edge users (CEUs). Between neighboring cells, the allocation of the static CEU frequency band is carefully planned to avoid overlapping. The 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 among the cell edge users within neighboring cells can be reduced, which is the major source of the inter-cell interference. A simple example of the static ICIC solution is the so-call frequency reuse 3. Among three neighboring cells, each cell will use different 1/3 of the frequency band for the CEUs.



ICIC consider cell center load and cell edge load in version eRAN2.0. Every cell can dynamically adjust the numbers of CCU and CEU according to the cell load. It can balance scheduling of GBR service and non-GBR service.

Enhancement

In eRAN2.0, static ICIC is optimized to consider cell center load and cell edge load. Every cell can dynamically adjust the numbers of CCU and CEU according to the cell load, especially when the cell edge user’s GBR can’t be satisfied, cell center user is not congested and GBR service is satisfied. It can balance scheduling of GBR service and non-GBR service.

Dependency

None

1.27.2 LBFD-00202202 Uplink Static Inter-Cell Interference Coordination

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 by static configuration so as to mitigate frequency interference between cell edge users in neighboring cells.

Benefits

Uplink ICIC reduces inter-cell interference; therefore improve cell edge users 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 and resource allocation in both frequency and time domains between neighboring cells. It can improve the throughput of cell edge users and reduce impact of interference on system performance. ICIC in both frequency and time domains are supported.

In Huawei uplink static ICIC solution, different strategies are applied to the Intra-eNodeB and Inter-eNodeB scenarios respectively. For the Intra-eNodeB UL ICIC, the coordination is achieved at either frequency domain or time domain due to the natural synchronization among the cells. For the Inter-eNodeB UL ICIC, the coordination is achieved at the frequency domain, where the cell edge users of Inter-eNodeBs are given non-overlapping frequency bands. That is, the frequency band allocation for static UL ICIC is per cell basis.



Between the neighboring cells, the allocation of the static CEU frequency band of neighbor cells is carefully planned to avoid overlapping. By doing so, the interference among the cell edge users in neighboring cells can be reduced, which is the major source of the inter-cell interference. Additionally, the overload indication message from X2 interface is also used for power control purpose to avoid the interference due to overloaded frequency band.

Enhancement

In eRAN2.0, the coordination at frequency domain is the mainly methodology. And the coordination at time domain is achieved, too.

Dependency

None

1.28 LBFD-002020 Antenna Configuration

1.28.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 network capacity and data rates. Huawei eNodeB supports both RX diversity mode and no RX diversity mode.

Benefits

This feature can improve the receiver sensitivity and uplink coverage.

Description

Receive diversity is a technique to monitor signals at multiple frequencies from the same signal source, or to monitor time division signals at the same frequency from the same signal source, in order to combat signal fading and interference.

Receive diversity is one way to enhance the reception over uplink channels, including PUSCH, PUCCH, PRACH, and SRS.

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


http://www.answers.com/topic/interference

http://www.answers.com/topic/fading

http://www.answers.com/topic/frequency

http://www.answers.com/topic/interference

http://www.answers.com/topic/fading


In RX diversity mode, the eNodeB does not require additional devices and works with the Maximum-Ratio Combining (MRC) or Interference Rejection Combining (IRC) algorithms. Compared with 1-way reception without RX diversity, 2-way RX diversity requires twice the number of RX channels. The number of RX channels depends on the settings of the antenna connectors. The antennas to be used can be space-interlace antennas or cross polarization antennas.

Enhancement

None

Dependency

RX diversity requires the eNodeB to provide enough RF channels and demodulation resources that can match the number of diversity antennas. This feature has no special requirements on UEs.

1.29 LBFD-002021 Reliability

1.29.1 LBFD-00202101 Main Processing and Transport Unit Cold Backup

Availability


Summary

The feature provides cold backup capability to the LMPT (LTE Main Processing and Transport Unit) board of Huawei eNodeB.

Benefits

If there is only one LMPT board configured in the system, the failure of this board will cause long-time service outage of the base station. However, service can be automatically recovered within 3 minutes with LMPT redundancy. LMPT redundancy design is helpful for eNodeB to reach higher availability, greater than 0.99999.

Description

Two LMPT boards are configured in the system. When the system starts, the arbitrator module located on each LMPT board decides which board becomes active or standby. The active board handles several control and operation functions and provides for the most common transport network connectivity requirements. When it detects hardware or software faults on the board, it will switch to the standby state. Meanwhile, the standby board switches to the active state. The service can be automatically recovered within 3 minutes. The operator can also manually trigger LMPT switchover by EMS (Element Management System).



Enhancement

None

Dependency

To support this feature, the eNodeB must be configured with two LMPT boards.

1.29.2 LBFD-00202102 Cell Rebuild between Baseband Processing Units

Availability


Summary

In Huawei eNodeB, multiple LTE Baseband Processing (LBBP) boards can be configured to serve multiple cells. When an LBBP fails, the cell/cells served by the failed LBBP can be rebuilt on another operating LBBP with spare resources or on a backup LBBP if available.

Benefits

This feature ensures the cell coverage by cell re-establishment and improves the system reliability in case of an LBBP failure.

Description

Generally an eNodeB is equipped with multiple LBBP boards that serve multiple cells. The following figures show the example of configurations of 3*10M 2T2R with CPRI interface backup respectively.



Figure 1-1 3*10M 2T2R

When an LBBP board fails due to a hardware fault, communication interface failure, etc., the eNodeB is able to detect and locate the failure and tries to choose a target LBBP board on which the cell/cells are to be rebuilt. The target LBBP should have a CPRI connection with the RRU serving the cell/cells involved, as shown in the preceding figures. The selection of a target LBBP board mainly depends on the spare resources at the potential target LBBP board. In case of inadequate spare resources at the target LBBP, the bandwidth of the rebuilt cell/cells, or even that of the existing cells, can be decreased.

Enhancement

None

Dependency

The eNodeB should be equipped with at least two LBBP boards.



1.29.3 LBFD-00202103 SCTP Multi-homing

Availability


Summary

Stream Control Transmission Protocol (SCTP) is the signaling bearer protocol of the S1/X2 interface. It provides the similar service features of TCP and UDP, but ensures reliability, in-sequence transport of messages with congestion control, and offers multi-homing support for fault recovery by failover between redundant network paths.

Benefits

This feature provides reliability of signaling bearers.

Description

Figure 1-1 Stream Control Transmission Protocol

SCTP is the signaling bearer protocol of the S1/X2 interface. With this function, one SCTP association has two paths (IP-couple). An SCTP association is the logical channel between two SCTP ends. The two paths in one SCTP association are a master path and a slave path. Generally, the master path is active. When the master path fails, the slave path is activated.

Enhancement

None

Dependency

None



1.29.4 LBFD-00202104 Intra-baseband Card Resource Pool(user level/cell level)

Availability


Summary

In this feature, the processing resources in a baseband processing board of Huawei eNodeB are aggregated into a baseband resource pool in which all they are shared for the load processing.

Benefits

This feature ensures the stability and robustness of eNodeB, in which the processing resources are aggregated into a pool to share all load and thus to prevent individual resource from outage due to overload. The feature also improves the average cell capacity of eNodeB.

Description

The baseband processing board of Huawei eNodeB consists of several processing resources including DSP, FPGA, etc. A baseband processing board is capable of supporting multiple cells depending on the bandwidths. In this feature, the processing resources are aggregated into a resource pool to be shared for user data processing by multiple cells. A new user will be assigned to a resource which has the least load. In an occasional situation, if a resource should be overloaded or in outage, the eNodeB can reduce the load of the individual resource or move its existing users to other resources.

Enhancement

None

Dependency

None

1.30 LBFD-002027 Support of UE Category 1

Availability




Summary

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

Benefits

This feature can enable base station to support UE category 1.

Description

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

Downlink physical layer parameter values set by the field UE-Category:

UE Category

Maximum number of DL-SCH transport blocks bits received within a TTI

Maximum number of bits of a DL-SCH transport block received within a TTI

Total number of soft channel bits

Maximum number of supported layers for spatial multiplexing in DL

Category 1 10296 10296 250368 1

Category 2 51024 51024 1237248 2

Category 3 102048 75376 1237248 2

Category 4 150752 75376 1827072 2

Category 5 299552 149776 3667200 4

Uplink physical layer parameter values set by the field UE-Category:

UE Category Maximum number of bits of an UL-SCH transport block transmitted within a TTI

Support for 64QAM in UL

Category 1 5160 No

Category 2 25456 No





Category 3 51024 No

Category 4 51024 No

Category 5 75376 Yes

Total layer 2 buffer sizes set by the field UE-Category:

UE Category Total layer 2 buffer size [kBytes]

Category 1 150

Category 2 700

Category 3 1400

Category 4 1900

Category 5 3500

Enhancement

None

Dependency

UE should support the same category as eNodeB.

1.31 LBFD-002028 Emergency Call

Availability

This feature is available from eRAN2.1

Summary

The emergency call service is an operator-assisted service that connects a caller in a life-threatening or time-critical situation to an emergency service organization.



Benefits

This feature provides all users, even those without SIM, a prioritized connection to an emergency service organization.

.

Description

The emergency Call service is an operator-assisted service that connects a caller in a life threatening or time-critical situation to an emergency service organization such as police, hospital and fireman.

New features in E-UTRAN to support emergency call are as follows: Support of identifying emergency call users Support of special processing such as access class barring and priority

handling for the network access and mobility management Support of location service for emergency call users

Admission of an emergency call is prioritized over other ongoing sessions in the eNodeB to enable call completion. Regardless of network features/services activated in the network (e.g., unconditional call-forwarding, incoming call barring, etc.), the Public Safety Answering Point (PSAP, used in US)/ Emergency Centre (EC, used in Europe) is able to get emergency caller’s location by means of LCS and call back the caller once an emergency call has been placed. The emergency call, served on LTE with multi-mode terminal, fallbacks to UMTS or GSM depending upon LTE VoIP support.

Four types of users are permitted to initiate an emergency call:

Common user: normal subscriber Common restricted user: normal subscriber, whose calls are restricted for

some reasons (for example, out of coverage of own PLMN, etc) Restricted user with SIM card: User, whose SIM card fails to authenticate,

uses IMEI (International Mobile Equipment Identity) to initiate an emergency call.

Restricted user without SIM card: User, without SIM card, uses IMEI to initiate an emergency call

This feature supports 911 Emergency Calls (North America) / 112 Emergency Calls (Europe) in its SAE/LTE solution as defined by 3GPP specification.

Enhancement

None

Dependency UE should support IMS based voice service on LTE or voice service on

2G/3G. The location service for emergency call users function is dependant of the

optional feature LCS. The emergency call should be supported in the core network. If IMS is not deployed, the support of the optional feature CS Fallback to

GERAN/UTRAN/CDMA2000 will be needed.



1.32 LBFD-003001 Transport Networking

1.32.1 LBFD-00300101 Star Topology

Availability


Summary

Star topology is easy to implement and manage with high reliability. It provides simple topology between eNodeB interfaces.

Benefits The simplest topology

Simple management and high reliability

Description

Figure 1-1 Star topology

The eNodeB supports star topology. eNodeBs connect to the core network by layer2 or layer3 data network. The interface between the eNodeB and core network element is the S1 interface.

There are also connections between eNodeBs by the X2 interface, which enable information exchange between the eNodeBs.

Enhancement

None



Dependency

None

1.32.2 LBFD-00300102 Chain Topology

Availability


Summary

eNodeBs can be connected in chain topology applied to the strip-shape areas of sparse population.

Benefits

Chain networking can reduce costs of transmission equipment, engineering, construction, and transmission link lease.

Description

eNodeBs can be connected in chain topology. This network topology is applicable to the strip-shape areas of sparse population, such as expressways and railways. In these areas, the chain topology can meet the requirement with much less transmission equipment. However, chain networking reduces reliability because signals are transferred across many intermediate systems.

The following figure shows the chain topology.

Figure 1-1 Chain topology

Enhancement

None

Dependency

None



1.32.3 LBFD-00300103 Tree Topology

Availability


Summary

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

Benefits

Tree networking is suitable for microwave transmission networks. Tree topology requires fewer transmission links than star networking.

Description

The eNodeB can be connected in tree topology. In most scenarios, the MW (Microwave) network is typically in tree topology. It is suitable for the MW network.

The use of transport lines is less than that for star networking. However, tree connections reduce reliability because signals are transferred across many intermediate systems. A fault occurring in the upper-level eNodeB may affect the operation of the lower-level eNodeBs. The networking topology is applicable to a large, sparsely populated area. Capacity expansion may result in reconstruction of the network.

The following figure shows the tree topology.

Figure 1-1 Tree topology



Enhancement

None

Dependency

This feature requires E1/T1.

1.33 LBFD-003002 Basic QoS Management

1.33.1 LBFD-00300201 DiffServ QoS Support

Availability


Summary

Huawei supports DiffServ (Differentiated Services) to provide QoS guarantee by classifying and managing different traffic in the network.

Benefits

This feature provides a kind of QoS guarantee mechanism. It is a standard mechanism used by Mainstream vendors.

Description

DiffServ can provide QoS in the network. It is a kind of QoS guarantee mechanism that classifies and manages different traffic with parameters of IP packets, such as DSCP (DiffServ Code Point) or TOS (Type of Service).

There are three important concepts in the DiffServ mechanism, including Classification, Marking, and PHB (Per-Hop Behavior). The relationship between them is that Marking marks different traffic with different PHBs by Classification.

The definition of PHB is as follows:

Default PHB is typically for best-effort traffic.

Expedited Forwarding (EF) PHB is for low-loss and low-latency traffic.

Assured Forwarding (AF) is a behavior group.

Class Selector PHB is defined to maintain backward compatibility with the IP Precedence field.

The classification of LTE traffic is based on QoS Class Indicators (QCIs). With Huawei configuration tool, users can configure the relationship between QCI and DSCP, i.e. the Marking way. The DSCP is used to describe the priority of PHB. The table below is an example of relationship between QCI and DSCP.



Table 1-1 Relationship between QCI and DSCP

Data Type QCI Resource Type

DSCP

User plane 1 GBR 0x2E

2 0x1A

3 0x1A

4 0x22

5 Non-GBR 0x2E

6 0x12

7 0x12

8 0x0A

9 0

Control plane SCTP 　 0x2E

OM MML 　 0x2E

FTP 　 0

Enhancement

None

Dependency

None

1.34 LBFD-003003 VLAN Support (IEEE 802.1p/q)

Availability


Summary

This feature enables Virtual Local Area Network (VLAN) functionality to provide traffic differentiation, manage data priority and security scheduling at the MAC layer.



Benefits Traffic isolation at the MAC layer

Priority at the MAC layer

Security at the MAC layer

Description

The eNodeB supports the Virtual Local Area Network (VLAN) functionality, complying with the IEEE 802.1p/q protocol. It provides traffic isolation, such as marking different VLANs for OAM data and traffic data, and priority and security at the MAC layer.

The following two VLAN Marking ways are applicable:

Marking VLAN tag according to DSCP

Marking VLAN tag according to the next-hop IP address

Enhancement

None

Dependency

None

1.35 LBFD-003004 Compression and Multiplexing over E1/T1

1.35.1 LBFD-00300401 IP Header Compression

Availability


Summary

IP header compression provides a method to compress IP header information in order to increase the efficiency of E1/T1 interfaces.

Benefits

IP header compression can save S1/X2 IP transport resource to provide higher transport efficiency of S1/X2 IP transmission.

Description

This feature focuses on the compression technology in UDP/IP layer.



When UDP/IP/MLPPP/E1/T1 is used for transport, the UDP/IP encapsulation is too large for packets of small payloads and results in low transport efficiency.

IP header compression is adopted to enhance the transport efficiency. The 28 bytes of UDP/IP header can be compressed into 4-7 bytes.

Enhancement

None

Dependency Optional UTRP(Universal Transmission Processing unit) card

IP over E1/T1 is used for transport

The peer equipment supported the IP header compression functionality.

1.35.2 LBFD-00300402 PPP MUX

Availability


Summary

PPP MUX (Point-to-Point multiplex) provides a method to multiplex the IP header in order to increase the efficiency of E1/T1 interfaces.

Benefits

PPP MUX can save S1/X2 IP transport resource to provide high transport efficiency for S1/X2 IP transmission.

Description

This feature focuses on the multiplex technology in PPP/ML-PPP layer.

When UDP/IP/ML-PPP/E1 is used for transport, the UDP/IP/ML-PPP encapsulation is too large for packets of small payloads and results in low transport efficiency.

PPP MUX technology is adopted to enhance the transport efficiency. With PPP MUX mechanism, several IP packets can be multiplexed into one PPP frame to reduce the transport consumption of PPP.

Enhancement

None


IP over E1/T1 is used for transport

PPP or ML-PPP is used for transport



The peer equipment supports PPP MUX function.

1.35.3 LBFD-00300403 ML-PPP/MC-PPP

Availability


Summary

ML-PPP/MC-PPP (Multilink and Multiclass Point-to-Point Protocol) is the extend protocols of PPP. ML-PPP is a protocol for binding several PPP links to one logic PPP link. The priority is provided for PPP link traffic via MC-PPP protocol.

Benefits Increase the bandwidth of the PPP link.

Load balancing in multi-PPP links

Enhance the reliability of the PPP link

Provide priorities for traffic on PPP link.

Transport efficiency is enhanced when PPP header compression is used.

Description

PPP is a point-to-point transport protocol. The PPP header compression can be provided to enhance the transport efficiency.

ML-PPP is an extend protocol of PPP. When ML-PPP is used, several PPP links are bound to one logic PPP link group. The ML-PPP increases the bandwidth of the PPP link and enhances the reliability of the PPP link between the eNodeB and the directly connected equipments. If one link of PPP link group is broken, the ML-PPP will not break. Only thing happen is the bandwidth decreases correspondingly.

MC-PPP is an extend protocol of PPP. When MC-PPP is used, the traffic on the PPP links can be marked with different priorities according to DSCP which is mapped to QCI in eNodeB.

The following figure shows the ML/MC-PPP

Figure 1-1 ML-PPP/MC-PPP



Enhancement

None


The peer transport equipment shall support ML-PPP/MC-PPP when ML-PPP/MC-PPP is used to transport.

E1/T1 interfaces are used.

1.36 LBFD-003005 Synchronization

1.36.1 LBFD-00300501 Clock Source Switching Manually or Automatically

Availability


Summary

This feature enables manual or automatic switching between clock sources.

Benefits

If unexpected events occur in the current clock sources, the system will not be affected.

Description

The eNodeB can work in multiple clock synchronization modes. The system clock source can be chosen in a convenient and flexible manner. When one clock source fails, the system clock can be manually or automatically switched to another available one.

The eNodeB clock sources that can be selected are as follows:

Synchronization with Ethernet(ITU-T G.8261)

Synchronization with the clock over IP (IEEE1588V2)

Synchronization with the clock over IP (Huawei proprietary solution)

Synchronization with GPS

Synchronization with the BITS

Synchronization with E1/T1 interface

Synchronization with 1PPS

In addition to the previous clock sources, the eNodeB can work with the local oscillator.



Enhancement

None

Dependency

None

1.36.2 LBFD-00300502 Free-running Mode

Availability


Summary

The free-running mode is an alternative mode to the clock sources if all clocks fail.

Benefits

When all clock sources are lost, this feature can keep the eNodeB in normal service for up to 90 days.

Description

When all clock sources are lost, the eNodeB internal clock can work in the free-running mode to keep the eNodeB running.

The enhanced stratum 3 Oven Controlled Crystal Oscillator (OCXO) with a high accuracy works as the master clock of the eNodeB. The OCXO can keep the eNodeB in normal service for up to 90 days.

Enhancement

None

Dependency

None

1.36.3 LBFD-00300503 Synchronization with GPS

Availability


Summary

The eNodeB can work in multiple clock synchronization modes to suit different clock topologies. Global Positioning System (GPS) can be one of the synchronization sources.



Benefits

This feature provides GPS as one of the synchronization sources. The eNodeB internal clock can be synchronized with the transport network and no auxiliary clock equipment is needed, in order to reduce the cost. The synchronized clock is of the required accuracy to meet both radio frequency and transmission network requirements.

Description

In compliance with 3GPP, the eNodeB clock must have a higher clock precision. The frequency stability of the 10-MHz master clock of the eNodeB should be lower than ±0.05 ppm.

It is required if a GPS clock should be used as the clock source.

The clock signals are processed and synchronized as follows:

The GPS antenna and feeder system receives GPS signals at 1575.42 MHz, and transmits the signals to the GPS card. The system can simultaneously trace up to eight (normally three or four) satellites. The GPS card processes the signals and transmits them to the main clock module.

Enhancement

None

Dependency GPS antenna and feeder system

Optional USCU (Universal satellite Card and Clock Unit) card.

1.36.4 LBFD-00300504 Synchronization with BITS

Availability


Summary

The eNodeB can work in multiple clock synchronization modes to suit different clock topologies. Building Integrated Timing Supply System (BITS) can be one of the synchronization sources.

Benefits

This feature provides BITS as one of the synchronization sources. The eNodeB internal clock can be synchronized with the transport network and no auxiliary clock equipment is needed, in order to reduce the cost. The synchronized clock is of the required accuracy to meet both radio frequency and transmission network requirements.



Description


The eNodeB can synchronize its clocks with the 2-MHz clock signal from an external reference clock. The reference clock can be a BITS or a 2-MHz clock from the transmission equipment. Through phase locking and frequency dividing, the main clock module converts the clock signals into various clock signals required by the eNodeB.

Enhancement

None

Dependency Optional USCU (Universal satellite Card and Clock Unit) card.

1.36.5 LBFD-00300505 Synchronization with 1PPS

Availability


Summary

The eNodeB can work in multiple clock synchronization modes to suit different clock topologies. 1PPS can be one of the synchronization sources.

Benefits

This feature provides 1PPS as one of the synchronization sources. The eNodeB internal clock can be synchronized with the transport network and no auxiliary clock equipment is needed, in order to reduce the cost. The synchronized clock is of the required accuracy to meet both radio frequency and transmission network requirements.

Description


This feature provides 1PPS as one of the synchronization sources.

Enhancement

None



Dependency Optional USCU (Universal satellite Card and Clock Unit) card

1.36.6 LBFD-00300506 Synchronization with E1/T1

Availability


Summary

The eNodeB can work in multiple clock synchronization modes to suit different clock topologies. Synchronization with E1/T1 is one option.

Benefits

This feature provides synchronization with E1/T1 option. The eNodeB internal clock can be synchronized with the transport network and no auxiliary clock equipment is needed, in order to reduce the cost. The synchronized clock is of the required accuracy to meet both radio frequency and transmission network requirements.

Description


The clock source of the eNodeB can be synchronized with the E1/T1 line clock sources. When the S1 interface is over E1/T1, the eNodeB can be synchronized with the E1/T1 line clock.

Enhancement

None


1.37 LBFD-004001 Local Maintenance on the LMT

Availability




Summary

This feature is used in local maintenance of eNodeB.

Benefits

Local maintenance of eNodeB is available when centralized M2000 management is not available, when the transmission between M2000 and eNodeB is not available or when faults occur and field operation is required.

Description

The Local Maintenance Terminal (LMT) provides the following functions and tools:

Execution of MML commands

Querying of eNodeB alarms

Local eNodeB commissioning functions (applicable, for example, when the transmission between the Huawei iManager M2000 and eNodeB is not available), such as download and activation of software

Local eNodeB expert fault diagnosis functions

Real-time performance monitoring functions, such as RF output power monitoring, RF interference detection, and transmission quality monitoring for transport links

Enhancement

From eRAN2.0, The LMT functions can be achieved through a web browser.

Dependency

A web browser is required to achieve the function.

1.38 LBFD-004002 Centralized M2000 Management

Availability


Summary

The Huawei iManager M2000 provides FCPSS management functions for operators at the management center.

Benefits

All LTE network elements can be managed at the management center, which effectively reduces OPEX.



Description

The Huawei iManager M2000 provides all necessary fault management, configuration management, performance management, security management and software management (FCPSS defined by 3GPP) management functions to help operators to manage their network elements on a sub-network.

FCPSS involves the following contents:

Centralized fault management

Centralized configuration management

Centralized performance management

Centralized security management

Centralized software management

Enhancement

None.

Dependency

The Huawei iManager M2000 is required.

1.39 LBFD-004003 Security Socket Layer

Availability


Summary

Security Socket Layer (SSL) is a layer between the TCP layer and the O&M application layer. SSL provides the secured data transfer function between the eNodeB and the Huawei iManager M2000.

Benefits

All remote operation and maintenance tasks are performed through encrypted protocols.

Description

Security Socket Layer (SSL) is a layer between the TCP layer and the O&M application layer. SSL provides the secured data transfer function between the eNodeB and the Huawei iManager M2000. All O&M application data transferred through SSL is encrypted. FTP over SSL is also supported.



Enhancement

None.

Dependency

Related certifications are required.

1.40 LBFD-004004 Software Version Upgrade Management

Availability


Summary

This feature provides efficient and correct installation and upgrade of the software and version management functions.

Benefits

The eNodeB software management enables efficient and correct software installation, upgrade, and version management.

Description

The eNodeB software management covers the following functions:

Efficient and correct installation and upgrade of the software

− Automatic compatibility check on the software and hardware versions to verify a successful software installation and upgrade.

− Automatic data conversion for the software upgrade, which requires no manual configuration updates.

− Software download by configuration can reduce 30% of the software package size and shorten the download time. For adding a board, the system supports automatic download of software files for the board from the Huawei iManager M2000 if the files are not downloaded previously.

− If the network recovers in 24 hours after breakdown, the system supports resumption of the software download with no need to download the software from scratch.

− A maximum of 500 eNodeBs can be selected to download and activate the software in batches automatically.

− Hot patch can be upgraded together with software in Huawei iManager M2000 software management wizard.

Version management, for example, the hardware and software version query



The process for upgrading software at a network element involves the following two activities:

Downloading the software package from the Huawei iManager M2000 to the eNodeB. This may take some time because of the limited bandwidth of the OM link but does not have impacts on services.

Running the software activation command on the Huawei iManager M2000 client. The system will automatically load the software to the target boards and activate the software. To activate the software, the target boards will be reset and the service on the boards will be disrupted.

The above-mentioned two activities can be done seperately. E.g. downloading software package to eNodeBs at daytime and activating the software at midnight. The seperate software upgrade procedure helps to reduce the risk of software upgrade failures and service disruption of the sub-network.

Enhancement

None

Dependency

The Huawei iManager M2000 is required.

1.41 LBFD-004005 Hot Patch Management

Availability


Summary

This feature provides hot patch management functions, such as installation, uninstall and rollback.

Benefits

The eNodeB supports the hot patches so that the software bugs can be fixed without interrupting the ongoing services.

Description

A hot patch is a path that is used to fix bugs and does not interrupt the ongoing services. Huawei LTE hot patch management involves the following functions:

Hot patch installation.

There are two ways to install a released hot patch package on the eNodeB:

− Running only a single installation command: In this way, the patch is downloaded, loaded, activated and confirmed automatically.



− Running different commands at different steps of the patch installation: In this way, users have full control over the installation procedure: download, load, activat and confirm.

Rollback of the last installed hot patch

Uninstall of the hot patch

Enhancement

None

Dependency

Hot patch management can be implemented on the Huawei iManager M2000 or the eNodeB LMT.

1.42 LBFD-004006 Fault Management

Availability


Summary

This feature provides automatic fault supervision and handling of eNodeB.

Benefits

This feature enables the automatic fault supervision of the equipment in the network elements. With real-time alarm lists and alarm logs, operators can have a comprehensive view of the actual status of the network at any time.

Description

Fault management involves fault detection, fault handling, fault correlation, and fault reporting. With these features, operators can be informed as soon as the fault occurs in the network and take proper actions to minimize or prevent service disruption.

Fault detection

Fault detection includes physical layer and link layer environment monitoring and KPI alarm monitoring and other fault detection. A small portion of faults may have a negative impact on the traffic if self-testing, such as RAM self-testing and transport link loopback testing, is performed. Among those faults, some are detected automatically in the board startup phase, and some can be manually triggered by executing fault testing commands.

Fault detection methods are carefully designed to avoid false alarms and intermittent alarms.

Fault handling



The eNodeB will perform fault isolation and fault automatic recovery to minimize the impacts on service.

Fault correlation

Fault management supports a run-time fault correlation handling mechanism and makes it possible to notify operators of the most important alarms (the root cause and impacts on the traffic) instead of all the related ones when a fault occurs. The number of alarms can be greatly reduced in this way, which makes it easier to locate and solve the network problems. This mechanism is predefined and embedded in the network elements, and operators can customize more alarm correlation handling rules on the Huawei iManager M2000.

Fault reporting

Faults are reported to users in the form of alarms. Because of the fault correlation function, the information of the correlation between alarms is contained in alarms. If any service-affecting faults occur, operators can get the root fault by simply right-clicking the service-affecting faults.

The operators can browse real-time alarm information, query history alarm information, and store alarm information. The online help provides detailed troubleshooting methods for each type of alarm.

Enhancement

Huawei LTE eRAN2.0 supports KPI alarm detection..

Dependency

Fault management can be implemented on the Huawei iManager M2000 or the eNodeB LMT.

1.43 LBFD-004007 Configuration Management

Availability


Summary

This feature provides online and offline configuration functions which support quick installation, expansion and configuration of the network.

Benefits

This feature provides a good overview of the current status of the network and supports fast installation, expansion and configuration of the network.



Description

Configuration management provides operators with a means to collect and manage the data of the network element. The manageable element data covers the physical aspect (equipment) and logical/functional aspect (such as cells and links). The graphic user interface makes it easy to implement the management.

To minimize the impact of reconfiguration on the system, Huawei configuration management function has the following important features:

Physical modifications are independent of the related logical modifications.

All the required modifications to satisfy a defined task are completely checked to ensure their validity before the modifications can be applied to the eNodeB.

Configuration data consistency between the NE and the Huawei iManager M2000 are always ensured.

Both offline configuration and online configuration are supported.

Offline configuration

CME (Configuration Management Express) is a graphic offline configuration tool. In addition to general configuration functions, it provides some configuration templates to ease site deployment jobs. It also provides some GUI wizards to help user to finish capacity expansion and migration jobs.

Online configuration

All configuration data can be modified and queried online through MML commands.

Enhancement

GUI wizards are added to help users with capacity expansion and migration jobs.

Dependency

Configuration management can be implemented on the Huawei iManager M2000 or the LMT.

1.44 LBFD-004008 Performance Management

Availability


Summary

This feature provides various performance measurement (PM) counters to monitor the performance of the eNodeB. The real-time KPI monitoring is an enhanced feature to help user locate performance problems quickly.



Benefits

The performance management function provides an efficient way to monitor the network performance so that network troubleshooting and optimization can be implemented, and the real-time KPI monitoring is a more efficient feature.

Description

Performance measurement gives the detailed information of the network. Such information facilitates troubleshooting and network optimization.

PM administration

The performance measurement administration provides operators with a means to manage the available measurements.

For the new commissioning network elements (eNodeB), the predefined performance measurements will start after initial startup phase. The performance measurements can be suspended and resumed manually.

The network elements (eNodeB) provide machine-machine interfaces, allowing the Huawei iManager M2000 to collect the necessary statistics and to set the related parameters including statistical counters and the measurement period.

The statistics are obtained by the Huawei iManager M2000 in binary format in every measurement period. The result files are also stored in the network element (eNodeB) for up to 3x24 hours as backups that are useful when data transfer fails, which makes it possible for the Huawei iManager M2000 to recollect the lost data later.

PM counters

The PM counters include key counters and other counters. The key counters are used to generate the key performance indicators (KPIs) of the network, which are defined on the Huawei iManager M2000, and these counters are predefined and initialized as soon as the eNodeB starts. The KPIs, related original counters and formulas can be added, modified and deleted on the Huawei iManager M2000. Other counters reflecting the other aspects of network performance can be started when needed.

The counters related to the following types of measurement are supported:

− Cell measurement

− Neighboring cell measurement

− Inter-RAT neighboring cell measurement

− eNodeB overall measurement

− IP transport measurement

− Standard interface measurement

− Network element hardware measurement

Real-time KPI monitoring

This feature provides the monitoring of KPIs and graphical representation of network performance. Therefore, it is convenient for troubleshooting, drive tests and network optimization. The smallest sample frequency is 10 seconds.



Enhancement

Many of PM counters are added.

Dependency

Performance management is implemented on the Huawei iManager M2000.

1.45 LBFD-004009 Real-time Monitoring of System Running Information

Availability


Summary

This feature provides the function of monitoring the running information of the equipment, RF system, cells, subscribers and transport links.

Benefits

This feature is convenient for troubleshooting, drive tests and network optimization.

Description

This feature provides real-time monitoring and graphical representation of system operation information and quality. It is a test facility which helps operators to diagnose faults through precise information about cells, subscribers and links. The results are illustrated by graphical representation, and monitoring tasks are managed by the eNodeB Local Maintenance Terminal (LMT).

The monitoring tasks are managed by the LMT. The data monitored is not only shown in graphics but also stored in files automatically for later reviews.

The following monitoring items are supported:

Equipment running information monitoring: involving clock source quality

Subscriber-level running information monitoring: involving SIR measurement and UE TX power

Cell-level running information monitoring: involving eNodeB TX power, the number of cell users, throughput, and resource block usage

Transport link running information monitoring: involving SCTP links and IP paths

RF monitoring: involving RF performance and RF interference detection



Enhancement

None

Dependency

Real-time monitoring of system running information can be implemented on the LMT.

1.46 LBFD-004010 Security Management

Availability


Summary

This feature provides the user authorization, system data backup and restore, security log auditing and security-related alarms functions.

Benefits

This feature provides the user authorization and management mechanism to enhance network security.

Description

Security management covers the following functions to enhance system security:

User management: This mechanism allows setting of user accounts and permissions, so that the related authorized groups and operators can be managed.

System data backup and restoration

Collection of operation logs and auditing of security logs

Triggering of alarms when, for example, network attacks are detected or the number of unauthorized sessions exceeds the preset threshold

Enhancement

Security alarms are added.

Dependency

Security management is implemented on the Huawei iManager M2000



1.47 LBFD-004011 Optimized eNodeB Commissioning Solution

Availability


Summary

The optimized eNodeB commissioning solution supports USB commissioning and automatic obtaining of software and configuration data from the Huawei iManager M2000.

Benefits

This feature simplifies the eNodeB commissioning procedure.

Description

This feature simplifies the on-site commissioning procedure from the following aspects:

If eNodeB data is ready on the Huawei iManager M2000 and transmission of this eNodeB is ready, Huawei on-site manual commissioning task is very simple:

− Installing the hardware and powering on the eNodeB

− Waiting for the eNodeB startup and checking whether any alarm is reported

− If the eNodeB has a GPS, field engineer need do nothing because eNodeB will report the location to iManager M2000 and iManager M2000 will automatically select the correct configuration data for it.

− Or, if field engineer has a laptop, the engineer can use laptop to input very simply information (eNodeBID). iManager M2000 can use this information to automatically select a correct configuration data.

− Or , filed engineer can call the administration center and report the physical identity of the eNodeB

In the procedure, the newly installed equipment will automatically set up the connection with the Huawei iManager M2000 by using DHCP, download software and data from the Huawei iManager M2000, and install the software.

USB commissioning is supported. The associated software and data of the eNodeB can be copied to a USB disk at the administration center. A local commissioning engineer only needs to obtain the USB disk, install the hardware, and connect the USB disk to the USB port on the eNodeB. After that, the eNodeB can automatically install the software and load data, start up, and set up the connection to the Huawei iManager M2000. No more local configuration is required.

Enhancement

This feature simplifies eNodeB commissioning.



Dependency

The optimized eNodeB commissioning solution depends on the Huawei iManager M2000. USB commissioning requires USB disks.

1.48 LBFD-004012 Environment Monitoring

Availability


Summary

This feature provides environment fault alarming and customized environment alarms functions.

Benefits

This feature enables centralized environment monitoring of Huawei eNodeB equipment.

Description

This feature enables centralized environment monitoring of Huawei eNodeB equipment in terms of, for example, the temperature, humidity, smoke, water immersion, access control, and power supply. Besides, Huawei equipment can be connected to third-party analog and digital sensors, which enable operators to customize environment alarms.

Enhancement

None

Dependency

The Huawei iManager M2000 or LMT is required.

1.49 LBFD-004013 Inventory Management

Availability




Summary

The Huawei iManager M2000 retrieves inventory information automatically from the eNodeB after commissioning and synchronize the information on the eNodeB every day.

Benefits

With this function, operators can obtain the timely and accurate inventory data of the existing network for decision making.

Description

Inventory management helps operators to manage the asset information of the network. With this function, the assets can be queried and managed on the Huawei iManager M2000.

The objects which are managed by this function include physical objects (such as racks, frames, slots, boards, ports, and fans) and logical objects (such as software and patches).

When requested from the Huawei iManager M2000, an asset information file in .xml format is generated and is sent to the Huawei iManager M2000. The Huawei iManager M2000 stores the uploaded information in the network inventory database.

The Huawei iManager M2000 retrieves inventory information automatically from the eNodeB after commissioning and synchronize the information on the eNodeB every day.

Enhancement

The Huawei iManager M2000 retrieves inventory information automatically from the eNodeB after commissioning.

Inventory change notification function has been added to eNodeB. When inventory changes in eNobeB, a notification will be sent from eNobeB to M2000. So that the inventory information could be synchronized quickly between M2000 and eNodeB.

Dependency

The inventory information can be viewed only on the Huawei iManager M2000.

1.50 LBFD-004014 License Management

Availability




Summary

This feature involves the eNodeB license control.

Benefits

With this feature, the operators can purchase the license based on the network development, thus reducing the initial cost of the network deployment.

Description

The license file is used to determine whether the optional features are available and how many optional features are available.

The license file can be downloaded remotely to the eNodeB. The operators can manage and query the contents in the license file through the LMT or the M2000 client.

The license file is stored in the eNodeB.

New or upgraded license files can be ordered from Huawei.

Enhancement

None.

Dependency

None.


M2000

eNodeB 1

Lic

eNodeB 2

Lic

eNodeB n

Lic

……


2 Optional Features Description

2.1 LOFD-001001 DL 2x2 MIMO

Availability


Summary

Huawei eRAN1.0 supports DL 2x2 MIMO, 2-antenna transmit diversity and adaptive MIMO schemes between the UE and the eNodeB, improving system downlink performance.

Benefits

This feature can significantly improve downlink system throughput and coverage performance and also provide good user experience by offering higher data rates.

Description

The downlink 2x2 MIMO is a critical feature to allow an LTE system to deliver better performance, such as higher data rates, than the legacy system. Downlink 2x2 MIMO is supported in Huawei LTE eRAN1.0. Both space diversity and spatial multiplexing are supported as defined in LTE specifications, so Huawei eNodeB supports four DL 2x2 MIMO modes:

transmit diversity

open-loop spatial multiplexing

closed-loop spatial multiplexing

closed-loop rank-1 precoding

If two transmit antennas are configured in the eNodeB, the eNodeB adaptively selects one of the four modes based on UE rate and channel quality on the downlink.



Transmit diversity and closed-loop rank-1 precoding are solutions to combat signal fading and interference. By providing several signal branches that present independent varying signal levels, space diversity increases the robustness of the radio link because the probability that all signal copies are simultaneously in deep fading is low.

Spatial multiplexing including open-loop spatial multiplexing and closed-loop spatial multiplexing is a technique to transmit independent and separately encoded data signals, known as streams, from each of the transmit antennas. Therefore, the space dimension is reused, or multiplexed. If the transmitter is equipped with Ntx antennas and the receiver has Nrx antennas, the maximum spatial multiplexing order is Ns = min (Ntx, Nrx). If the spatial channels are independent of each other, which mean that Ns different data streams are transmitted over several independent (spatial) channels, it leads to an Ns increase of the spectrum efficiency or capacity.

Enhancement

None.

Dependency

DL 2x2 MIMO requires the eNodeB to provide 2 TX channels and 2 antennas per sector and the UE to provide at least 2 RX receive antennas.

2.2 LOFD-001002 UL 2x2 MU-MIMO

Availability


Summary

Huawei eRAN1.0 supports UL 2x2 MU-MIMO between UE and eNodeB improving system uplink performance.

Benefits

This feature can improve the overall cell uplink throughput, because it allows multiple users to transmit data using the same time-frequency resources.

Description

The uplink virtual MIMO is one of the important features to deliver the superior performance for LTE systems. It refers to a technique of multiplexing several users using the same time and frequency resources on the uplink.



Uplink virtual MIMO is a way to improve the throughput of the LTE system. With N receive antennas for an LTE eNodeB, no more than N virtual MIMO users can be demodulated. The uplink virtual MIMO does not involve UEs and it is transparent to UEs. Huawei eRAN1.0 eNodeB supports two receive antennas and thus supports two virtual MIMO users.

With uplink virtual MIMO, the eNodeB requires the matching demodulation algorithm and channel estimation algorithm in order to successfully demodulate the signals from different virtual MIMO users that use the same frequency-time resources.

If two receive antennas are configured in eNodeB, the eNodeB measures the UE’s uplink channel SINR and channel orthogonality with another UE. If the UE have good CQI and good channel orthogonality with the other UE, 2x2 MU-MIMO is used. Otherwise, 2-Antenna Receive Diversity is used.

UL 2x2 MU-MIMO is only used for the physical uplink shared channel (PUSCH).

If two receive antennas are configured in the eNodeB, the eNodeB adaptively selects between UL 2x2 MU-MIMO and UL 2-Antenna Receive Diversity.

Enhancement

None

Dependency

UL 2x2 MU-MIMO requires the eNodeB to provide 2 RX channels and 2 antennas per sector.

2.3 LOFD-001003 DL 4x2 MIMO

Availability


Summary

DL 4x2 MIMO, in accord with the 3GPP TS36.211 specification, involves 4-antenna transmit diversity, 4x2 MIMO and adaptive MIMO schemes between the UE and the eNodeB. In eRAN2.0, 4-antenna transmit diversity, 4x2 MIMO and adaptive MIMO schemes between the UE and the eNodeB are supported.

Benefits

This feature can significantly improve downlink system throughput and coverage performance and also provide good user experience by offering higher data rates.

Description

Besides DL 2x2 MIMO, DL 4x2 MIMO is supported by Huawei eNodeB. Huawei eNodeB also supports four DL 4x2 MIMO modes: transmit diversity, open-loop



spatial multiplexing, closed-loop spatial multiplexing, and closed-loop rank-1 precoding. If four transmit antennas are configured in eNodeB, the eNodeB adaptively selects one of the four modes, the scheme is similar to DL 2x2 MIMO.

Comparing with DL 2x2 MIMO, DL 4x2 MIMO can get more diversity gain, the system capacity and coverage will greatly improved, especially for cell edge use’s throughput.

Enhancement

In eRAN1.0, only 2-antenna transmit diversity and 2x2 MIMO are supported.

In eRAN2.0, 4-antenna transmit diversity , 4x2 MIMO and adaptive MIMO schemes between the UE and the eNodeB are supported.

Dependency

DL 4x2 MIMO requires the eNodeB to provide 4 TX channels and 4 antennas per sector and the UE provide at least two 2 RX receive antennas.

2.4 LOFD-001005 UL 4-Antenna Receive Diversity

Availability


Summary

Receive diversity is the common type of multiple-antenna technology to improve signal reception and to combat signal fading and interference. It improves network capacity and data rates. Besides UL 2-Antenna Receive Diversity, Huawei eNodeB also supports 4 RX diversity.

Benefits

This feature can improve the receiver sensitivity and uplink coverage.

Description

Receiving diversity is a technique to monitor multiple frequencies from the same signal source or multiple radios and antennas monitoring the same frequency, in order to combat signal fading and interference.

Receive diversity is a way to enhance the reception of uplink channels, including the PUSCH, physical uplink control channel (PUCCH), physical random access channel (PRACH), and sounding reference signal (SRS).

Huawei eNodeB supports both with RX diversity mode and without RX diversity mode. In RX diversity mode, Huawei eNodeB in eRAN2.0 can be configured with 4



antennas (4-way) through the antenna magnitude parameter in addition to UL 2-antenna receive diversity.

Enhancement

None

Dependency

RX diversity requires the eNodeB to provide enough RF channels and demodulation resources that can match the number of diversity antennas. This feature has no special requirements on UEs.

2.5 LOFD-001006 UL 64QAM

Availability


Summary

UL 64QAM enhances the uplink modulation scheme and allows UE in good radio environments to transmit data to the eNodeB at a higher data rate. The feature increases uplink data throughput and provides fast data transmission.

Benefits

This feature provides a higher service bit rate to increase cell throughput and improve user experience.

Description

The uplink 64QAM is a complementary modulation scheme to Quadrature Phase Shift Keying (QPSK) and 16QAM. The uplink 64QAM is intended to increase the bit rate for UEs in excellent channel condition. Compared with two information bits carried at each symbol using QPSK and four information bits using 16QAM, six information bits can be modulated with each symbol using 64QAM. Therefore, 64QAM can significantly improve the system capacity in uplink.

Depending upon the quality of radio environment, the eNodeB can select QAM modulation schemes of different orders. If a UE in a good radio environment, the eNodeB could select the highest order QAM modulation (64QAM mode) and large transport blocks for uplink transmission to achieve a higher data rate.

Enhancement

None



Dependency

This modulation scheme can be used only for UEs in excellent channel condition. The UE should support 64QAM modulation and the eNodeB should support 64QAM demodulation.

2.6 LOFD-001012 UL Interference Rejection Combining

Availability


Summary

Beside DL and UL inter-cell interference coordination (ICIC), Huawei eRAN1.0 provides interference rejection combining to effectively overcome the inter-cell interference. The method can be used with receiving diversity and can be used for MIMO decoding in any scenario.

Benefits

This feature can improve the system performance in the presence of interference. Therefore, enhanced network coverage and better service quality are provided for cell edge users (CEUs).

Description

Interference Rejection Combining (IRC) is a receive-antenna combining technique to effectively combat the inter-cell interference. IRC is often used together with receive diversity. In theory, IRC can be used for Multiple Input Multiple Output (MIMO) decoding in any scenario, and it is particularly effective for colored interference.

The main advantage of IRC lies in that it can outperform Maximum Ratio Combining (MRC) in terms of demodulation of a signal in the presence of interference or jamming. The essence of IRC is to model the interference as a random process, and use optimal filtering techniques to pre-whiten the received data—thereby make the interference like the white noise so that a conventional detector can be applied. Consequently, this method requires the knowledge of some parameters associated with the interference (for instance, its covariance matrix).

Enhancement

None

Dependency

The eNodeB must be equipped with multiple receive antennas (equal to or more than two).



2.7 LOFD-001014 Dynamic Inter-Cell Interference Coordination

2.7.1 LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination

Availability


Summary

The DL dynamic ICIC feature dynamically adjusts the system frequency band for CEU according to DL ICIC message.

Benefits

The DL ICIC feature can reduce the DL inter-cell interference and improve the CEU’s throughput. It is particularly effective when the loading in neighboring cells is unbalanced.

Description

Huawei DL ICIC solution uses employ power control and CEU scheduling to adjust the resource allocation for the CEUs in frequency domain to reduce the DL inter-cell interference. By keeping the non-overlapping downlink frequency bands for CEUs in neighboring cells, the DL inter-cell interference can be controlled under certain level. Therefore, the CEU’s Signal-to-Noise Ratio (SNR) and throughput can be improved.

Downlink Dynamic Inter-Cell Interference Coordination is an enhancement compared to the Downlink Static Inter-Cell Interference Coordination feature. It will dynamically adjust the frequency bandwidth according to the cell load.

The eNodeB adjusts the edge band of the serving cell and informs the scheduler about it. The adjustment is based on the following information: Band division schemes determined during network planning DL ICIC messages from neighboring cell Target neighboring cells for ICIC

These cells are selected based on neighboring cell information and inter-cell interference. The neighboring cell list is managed based on the DL ICIC messages from neighboring cells and the RSRP measurement reports from UEs.

Load determination resultsThe eNodeB checks the cell load and decides whether to block some RBs on the center band based on the load determination results. The eNodeB adjusts the UE types based on the RSRP measurement reports from UEs and the load determination results.

The scenario that benefits the most from DL ICIC is when the loading among the neighboring cells is unbalanced. The lightly-loaded cell can schedule the CEUs at the CEU frequency band with less bandwidth to allow the heavily-loaded cell to expand its CEU frequency band.



Enhancement

None

Dependency

None

2.7.2 LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination

Availability


Summary

The uplink dynamic ICIC feature dynamically adjusts the system frequency band for the CEU according to the cell load.

Benefits

UL ICIC can reduce inter-cell interference and improve the throughput of edge users, as well as the cell coverage.

Description

The UL ICIC is a technique to combat the inter-cell interference for a LTE system by coordinating transmit power control and resource allocation in both frequency and time domain among neighboring cells. It can improve the throughput of CEUs and reduce impact of interference on system performance. Different from static ICIC, the frequency bands of Inter-eNodeB or Intra eNobeB cells can be adjusted dynamically for cell edge users based on the cell load information exchanged via X2 Interface (for dynamic Inter-eNodeB UL ICIC) or internally (for dynamic Intra-eNodeB UL ICIC) when UL dynamic ICIC is enabled. Huawei eRAN1.0 supports ICIC in both frequency domain and time domain.

In Huawei eRAN1.0, different strategies are employed for the intra-eNodeB scenario and the inter-eNodeB scenario. For the neighboring cells in the same eNodeB (intra-eNodeB), the coordination is achieved at time domain thanks to the natural synchronization among the cells, for example, the interference coordination ensures the CEU located at three neighbor intra-eNodeB cells are scheduled at different TTIs. For the inter-eNodeB neighboring cells, the coordination is achieved at the frequency domain, where the CEUs in neighboring cells use non-overlapping CEU frequency bands.

The uplink dynamic inter-cell coordination is achieved by exchanging High Interference Indication (HII) and Overload Indication (OI) messages through X2 interface (for dynamic Inter-eNodeB UL ICIC) or internally (for dynamic Intra-eNodeB UL ICIC). HII is primarily used for frequency resource allocation to avoid interference. It is also used for dynamically adjustment of the frequency band used for CEUs. After the interference is generated, the interfered cell might broadcast OI to neighboring cells to reduce interference.



Enhancement

In eRAN2.0, UL ICIC algorithm changes the division of basic cell edge frequency based on eNodeB to the division of basic cell edge frequency base on cell. It also changes the coordination ways that it is coordinate between two cells in the old version to coordinate among all the necessary neighbor cells.

Dependency

None

2.8 LOFD-001007 High Speed Mobility

Availability


Summary

Huawei eRAN1.0 supports the mobility up to 120 km/h with good performance.

Benefits

High speed access is one of the key differentiators for Huawei LTE solutions to provide high speed coverage. This feature brings the following benefits:

Allows Huawei LTE system to support high-speed UEs at up to 120 km/h with good performance.

Provides a seamless user experience in a high-speed scenario.

Description

This feature allows a Huawei LTE system to operate in a high-speed scenario and deliver good performance.

The higher the velocity that the UE experiences, the severer the effect of fast fading that the system suffers. Therefore, it is more difficult to achieve the same performance in high-speed scenario as in the normal speed.

Huawei eRAN1.0 supports the UE velocity up to 120 km/h, which almost covers all mobility scenarios in an uran environment. The eNodeB should measure the UE mobility speed and refine the channel estimation scheme accordingly. In addition, the MIMO scheme and resource allocation mechanism is adaptively adjusted by the radio resource management (RRM) function to meet the high-speed performance requirement. For example, it is suitable to use frequency diversity mode rather than frequency-selective scheduling, or transmit diversity rather than spatial multiplexing for a UE at a high speed.

Enhancement

None



Dependency

None

2.9 LOFD-001008 Ultra High Speed Mobility

Availability


Summary

Huawei eRAN2.0 can support the mobility up to 350 km/h with good performance.

Benefits

High speed access is one of the key differentiators for Huawei LTE solutions to provide high speed coverage. This feature brings the following benefits:

Allows Huawei LTE system to be deployed in any high speed scenario and supports UEs at a speed of up to 350 km/h and 450km/h.

Provides a seamless user experience in a high speed scenario.

Description

In addition to the availability of speed at 120 km/h, this feature allows Huawei LTE system to support UEs with almost any mobility profile at up to 350 km/h in any scenario and deliver good performance. For example, a UE on a high-speed train could reach up to 350 km/h.

The higher the velocity that the UE experiences, the severer the effect of Doppler shift and fast fading that the system suffers. In Huawei RRM solution, the MIMO scheme and resource allocation mechanism is adaptively adjusted to meet the high-speed performance requirement. In addition, a function called Automatic Frequency Control (AFC) is implemented at the eNodeB to solve the Doppler shift problem and to support access by such high-speed UEs.

Enhancement

In eRAN1.0, 350km/h is supported.

In eRAN2.0, 450km/h is supported.

Dependency

None



2.10 LOFD-001009 Extended Cell Access Radius

Availability


Summary

To improve wireless network coverage, 3GPP TS36.211 has defined four types of preamble formats (0, 1, 2, 3). For format 0, it corresponds to small cell access radius, for format 1, 2 and 3, they correspond to extended cell access radius.

Benefits

This feature is used in large cell scenario to extend the cell access radius.

Description

This feature provides operator with support of extended cell radius. According to the 3GPP TS36.211, there are four types of preamble format (0-3) for PRACH are defined to support different cell access radius, shown in Table 2-1.

Table 2-1 Preamble 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, it is used in small cell scenario, and considered as basic cell radius. The extended cell radius consit of format 1, 2 and 3. For format 3, the supported cell access radius is about 100 km, which is used in the large cell scenario to enhance the system coverage.

Enhancement

None

Dependency

None



2.11 LOFD-001030 Support of UE Category 2/3/4

Availability


Summary

E-UTRAN needs to respect the signaled UE radio access capability parameters when configuring the UE and when scheduling the UE. So there are five categories defined in the protocol. This feature can enable BS to support UE category 2/3/4.

Benefits

This feature can enable BS to support UE category 2/3/4.

Description

E-UTRAN needs to respect the signaled UE radio access capability parameters when configuring the UE and when scheduling the UE. So there are five categories defined in the protocol. This feature can enable base station to support UE category 2/3/4.

Downlink physical layer parameter values set by the field UE-Category:

UE Category

Maximum number of DL-SCH transport blocks bits received within a TTI

Maximum number of bits of a DL-SCH transport block received within a TTI

Total number of soft channel bits

Maximum number of supported layers for spatial multiplexing in DL

Category 1 10296 10296 250368 1

Category 2 51024 51024 1237248 2

Category 3 102048 75376 1237248 2

Category 4 150752 75376 1827072 2

Category 5 299552 149776 3667200 4



Uplink physical layer parameter values set by the field UE-Category:



Category 1 5160 No

Category 2 25456 No

Category 3 51024 No

Category 4 51024 No

Category 5 75376 Yes

Total layer 2 buffer sizes set by the field UE-Category:

UE Category Total layer 2 buffer size [kBytes]

Category 1 150

Category 2 700

Category 3 1400

Category 4 1900

Category 5 3500

Enhancement

None

Dependency

UE should support the same category as eNodeB.

2.12 LOFD-001031 Extended CP

Availability


Summary

The Cyclic Prefix (CP) is the guard interval used in the OFDM to decrease the interference caused by the multi-path delay. The 3GPP TS36.211 supports two types of CP length, namely normal CP and extended CP.



Benefits

The normal CP and the extended CP are used in different cell scenarios. In case of small multi-path delay scenario, normal CP can achieve better system performance. In case of large multi-path delay scenario, extended CP can achieve better system performance.

Description

For both downlink and uplink, the extended CP is calculated as follows:

Extended cyclic prefix: TCP = 512*Ts

Where Ts = 1 / (2048*f), f = 15 kHz

For normal CP there are 7 symbols available in one slot. While for extended CP there are 6 symbols available in one slot. The extended CP increases overhead in exchange for larger multi-path capability.

The CP length is set in the network planning phase according to the system application scenario.

Dependency

None

Enhancement

UEs should support the extended CP length as the eNodeB.

2.13 LOFD-001048 TTI Bundling

Availability


Summary

Compared to WCDMA, the LTE radio access has a significantly shorter Transmission Time Interval (TTI) in order to reduce end-to-end delays. However, if a UE at the cell edge is limited by its available transmission power, it may not be able to transmit an entire packet during one TTI if the instantaneous source data rate is too high (e.g. VOIP). TTI bundling can help to improve the uplink coverage. In TTI bundling, a packet is transmitted as a single PDU during a bundle of subsequent TTIs without waiting for the HARQ feedback. HARQ feedback is only expected for the last transmission of the bundle.



Benefits

TTI bundling could help to improve uplink coverage and in-house reception for voice.

Description

TTI bundling transmission is introduced to improve LTE uplink coverage without the issues of overhead associated with L2 segmentation and ACK (Acknowledgement)/ NACK (Negative Acknowledgement) errors. The UEs in cell boundary can reduce transmission delay by means of TTI bundling transmission. The activation and deactivation of TTI bundling transmission is controlled by RRC signaling message.

If TTI bundling is configured by the RRC layer, a parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle. Within a TTI bundle, HARQ retransmissions are non-adaptive and shall be performed without waiting for feedbacks (e.g. NACK or ACK ) related to previous transmissions according to the parameter TTI_BUNDLE_SIZE. A feedback for a TTI bundle is only received for a specific TTI corresponding to TTI_BUNDLE_SIZE. A retransmission of a TTI bundle is also a TTI bundle.

Enhancement

None.

Dependency

The UE should support TTI Bundling.

2.14 LOFD-001015 Enhanced Scheduling

2.14.1 LOFD-00101501 CQI Adjustment

Availability


Summary

This function reinforces the traditional AMC feature by introducing downlink Channel Quality Indicator (CQI) adjustment.



Benefits

This feature brings the following benefits:

Effectively compensates for the inaccurate CQI measurement and makes the MCS selection more accurate by using a closed-loop mechanism.

Improves the system capacity by selecting more accurate MCS.

Allows an adaptive CQI measurement for different scenarios and therefore improves the system capacity.

Description

The CQI adjustment scheme enhances the conventional AMC scheme by introducing downlink CQI adjustment. It could provide additional performance gains.

Under the conventional AMC scheme, the eNodeB chooses a Modulation and Coding Scheme (MCS) for a UE based on the reported CQI. As a result, MCS will mainly change according to the reported CQI. Since the UE measurement error and channel fading could make the reported CQI somewhat inaccurate, the MCS selection based on the inaccurate CQI could cause the DL transmission fails to reach the Block Error Rate (BLER) target. The conventional AMC scheme does not have a closed-loop feedback mechanism to guarantee that the actual BLER reaches the BLER target.

The CQI adjustment scheme introduces a closed-loop mechanism to compensate for the CQI measurement errors. When an eNodeB selects the MCS for the DL transmission, besides the CQI and transmits power, the eNodeB also considers the difference between the target BLER and the actually measured BLER. Note that the actually measured BLER is calculated on the basis of the closed-loop ACK/NACK that the eNodeB received from the DL transmission. In addition, the closed-loop solution used by the CQI adjustment scheme allows the eNodeB to instruct a UE to change the BLER target for CQI reporting, which could maximize the system throughput.

Enhancement

None

Dependency

None

2.14.2 LOFD-00101502 Dynamic Scheduling

Availability


Summary

The dynamic scheduling feature provides the function that guarantees the user QoS and achieves efficient resource utilization. The fairness between different UEs is also considered in the function. The dynamic scheduling algorithm mainly focuses on the GBR and non-GBR services.



Benefits

The scheduling feature is the core function to provide QoS in a LTE system. Huawei scheduling solution could provide the following benefits:

Guarantees the QoS for GBR, and non-GBR services.

Achieves an optimal tradeoff among throughput, fairness, and the QoS.

Description

The scheduling function facilitates to the achievement of efficient resource utilization on a shared channel. In a LTE system, the scheduler allocates resources to the UEs every 1 ms or every one TTI. The scheduling algorithm needs to meet the QoS requirements for different services and to achieve a good tradeoff between priority differentiation among different services and the fairness among users.

The QoS specification is based on the nine QoS QCI defined in LTE standards. The nine different QCI classes can be divided into GBR and Non-GBR service. The scheduling solution is required to guarantee the bit rate requirement for GBR services, and enforce the AMBR for Non-GBR services. Minimum Bit Rate (Min-BR) is set for Non-GBR services to avoid starvation.

The UL scheduler uses token bucket algorithm to achieve rate control function for GBR and Non-GBR services. Proportional Fair (PF) algorithm is the basic strategy to ensure scheduling priorities (based on QCI) among different services. Higher priority is assigned to IMS signaling and GBR services. Semi-persistent scheduling is employed for VoIP service to ensure the voice quality. When the congestion indicator from load control algorithm is received, the scheduler might reduce the guaranteed data rate for GBR service. The scheduler might also consider the input from UL ICIC to reduce interference.

In eRAN2.1, uplink schedule will divide the LCG according to Operator configure. VOIP will be assigned with signaling in the same LCG and non-GBR will have two LCG. These can guarantee the high priority non-GBR in uplink schedule. PBR will not be the same as min-GBR and PBR will be configurable for operator.

The DL scheduler employs an enhanced scheduling strategy. During a given time window, the scheduler is required to guarantee GBR and AMBR for all services. For GBR services, the user channel quality and the service packet delay are taken into account when calculating the priority. For Non-GBR services, in addition to the user channel quality, the scheduled service throughput is also considered when calculating the priority. Note that semi-persistent scheduling is used for VoIP service again and the bandwidth allocated for VoIP traffic is not scheduled by the scheduler. The enhanced DL scheduler can achieve an optimal tradeoff among throughput, fairness, and QoS guarantee. The same as the UL scheduler, the DL scheduler also considers the input from DL ICIC to reduce the inter-cell interference.

Enhancement

None

Dependency

None



2.15 LOFD-001016 VoIP Semi-persistent Scheduling

Availability


Summary

Semi-persistent Scheduling is a technique for efficiently assigning resources for spurts of traffic in a wireless communication system. A semi-persistent resource assignment is valid as long as more data is sent within a predetermined time period from last sent data, and expires if no data is sent within the predetermined time period. For VoIP, a semi-persistent resource assignment may be granted for a voice frame in anticipation of a spurt of voice activity.

Benefits

The semi-persistent scheduling is critical for VoIP services and provides the following benefits:

Guarantees the QoS for VoIP services.

Reduces the control signaling overhead for VoIP transmission.

Maximizes the resource utilization by dynamically activating/deactivating resource allocation according to the transition between silent period and talk spurt.

Description

This feature is critical to deliver the voice service with acceptable quality. LTE is optimized in terms of packet data transfer, and the core network is purely IP packet-based. The voice is transmitted by means of VoIP instead of using the traditional circuit-based method. To ensure the voice quality, a semi-persistent scheduling solution is used for VoIP services.

VoIP is a real-time service with small and fixed-length data packets and constant time of arrival. VoIP traffic consists of talk spurts and silent periods. The Adaptive Multi-Rate (AMR) codec could yield quiet burst voice traffic. During the talk spurt, VoIP packets normally arrive at intervals of 20 ms; during the silent period, Silence Indicator (SID) packets arrive at an interval of 160ms.

The semi-persistent scheduling allocates a certain amount of resources (such as resource blocks) for the voice call during the call setup period through RRC signaling. The allocation is semi-persistent and does not need to be requested again through UL/DL control signaling until the call ends and the resources are released. To allow the maximum resource utilization during the silent period, the resource allocation will be deactivated by means of explicit signaling exchanged over the Physical Downlink Control Channel (PDCCH). When the VoIP call transits from the silent period to the talk spurt, similar PDCCH signaling is used to activate the semi-persistent resource allocation. The semi-persistent scheduling significantly reduces the PDCCH overhead and ensures the QoS for VoIP services by reserving the resources in a semi-persistent



fashion. It also improves the resource utilization by dynamically activating or deactivating resource allocation activities between talk spurt and silent period.

If both VOIP and data traffic are present for an UE, dynamic scheduling is used in stead of semi-persistent scheduling.

Starting from eRAN2.1, when it is 1.4MHz system bandwidth, it will not use semi-persistent schedule and when it is other system bandwidth, it will preserve some percent of total RB resource. The reason is that if VOIP occupies a lot of resource, it will impact the schedule of signal, which is scheduled after VOIP.

Enhancement

None

Dependency

None

2.16 LOFD-001017 RObust Header Compression (ROHC)

Availability


Summary

ROHC provides an efficient and flexible header compression mechanism which is particularly important to improve the bandwidth utilization for VoIP service with small payload size.

Benefits

ROHC can reduce the size of IP packet head and significantly improve the payload/header ratio for VoIP service with small payload. It also shortens the response time in order to guarantee the high ratio of link usage between the eNodeB and the UE.

Description

As more and more wireless technologies are being deployed to carry IP traffic, it is a vital significance to reduce the total size of header of transmission, because the overhead of the packet is large. This can improve the usage of the bandwidth resources, particularly for service with small payload (for example, VoIP service).

On an end-to-end transmission path, the entire header information is necessary for all packets in the flow. However, over a wireless link (a portion of the end-to-end path),



some of the information become redundant and can be reduced over the link, since they can be transparently recovered at the receiving side.

ROHC protocol provides an efficient, flexible, and future-proof header compression concept based on compression/decompression of IP/UDP/RTP/ESP packets header. It is designed to operate efficiently and robustly over various link technologies with different characteristics, especially for wireless transmission.

In LTE system, the ROHC function is located in Packet Data Convergence Protocol (PDCP) entities associated with user plane packets. For the UL, the packets are compressed by the UE and decompressed by the eNodeB; for the DL, the packets are compressed by the eNodeB and decompressed by the UE.

The relative gain for specific flows or applications depends on the size of the payload used in each packet. Header compression is expected to significantly improve the bandwidth utilization for VoIP service with small payload size.

Huawei LTE eNodeB supports profiles 0x0000–0x0004 based on both IPv4 and IPv6. Table 2-1 shows the profile identifiers and their associated header compression protocols.

Table 2-1 ROHC profile identifier and header compression protocol

Profile Identifier

Usage:

0x0000 No compression

0x0001 RTP/UDP/IP

0x0002 UDP/IP

0x0003 ESP/IP

0x0004 IP

Enhancement

None

Dependency

None

2.17 LOFD-001026 TCP Proxy Enhancer

Availability




Summary

A series of enhanced TCP functions adaptive to the link characteristics on the RAN side are implemented in the eNodeB. This feature enables the performance of the TCP protocol derived from the wired network to be greatly improved in the wireless network, thus improving user experience and system efficiency.

Benefits

This feature mitigates the impact of some factors such as packet loss in the RAN side to improve the performance of TCP data transmission, accelerates the slow startup and fast retransmission of the server during the data transmission, increases the UL/DL data transmission efficiency, and reduces the UL/DL transmission delay, thus greatly improving the PS data transmission performance.

Description

The TCP/IP protocol is extensively used all over the world. It was initially developed for wired transmission and later also used in wireless networks. However wireless networks exhibit some characteristics quite different from the wired network. A typical example is that of packet losses which, in a wired network, is commonly due to congestion in some network elements, whereas in a wireless network such losses can be due to transmission errors over the air interface. This has a significant impact on the overall performance of the data transmission, due to the way the TCP/IP protocols reacts to such packet losses. To mitigate this effect, a number of enhancements have been implemented in the eNodeB.

A TPE (TCP Proxy Entity) functionality is implemented in the eNodeB, which improves the data transmission performance in the wireless network. The TPE processes the TCP/IP packets by adopting TCP performance optimization technologies such as buffering and sorting of DL data, ACK splitting, DupACK duplication, local retransmission, building Window Scaling (WS) indication and enhanced simultaneous DL/UL data transmission. This feature accelerates the slow startup and congestion avoidance of the server and improves the DL throughput in the case of simultaneous uploading and downloading. Therefore, this feature greatly improves the PS data transmission performance.

ACK splitting

In TCP, the congestion window is updated according to the number of received ACK messages and is expanded by increasing the number of ACK messages. When a slow startup occurs at the transmitting end, ACK splitting can quickly recover the congestion window; when the transmitting end works in congestion avoidance mode, ACK splitting can accelerate the expansion of the congestion window.

DupACK duplication

In TCP, a lost TCP packet is retransmitted after three DupACK are received. With this feature, after the TPE receives the ACK message from the UE, the TPE immediately duplicates three DupACK messages and sends them to the server if it detects that the packets requested by the ACK are not in the buffer. This shortens the time for packet retransmission.

Local retransmission



When packet loss occurs on the air interface, the TPE, rather than the transmitting end, retransmits the packet to the receiving end, thus reducing the time for retransmission.

Packet sorting

The TPE sorts and transmits the disordered DL packets to avoid unnecessary transmission of DupACKs in the uplink and to prevent TPE local retransmission caused by disordered packets. In this way, transmission resources are saved.

Building WS indication

When TCP window size in server side is 64KB, the synchronization packet will not include WS indication. If the receiving side detects that there is no WS indication, the synchronization ACK packet returned by receiving side will not include WS indication. In this case, even if the capability of the receiving end is greater than 64KB, the window size is limited to 64KB. Therefore, the throughput is decreased if the actual receiving capability exceeds 64KB.

Enhanced simultaneous downlink and uplink transmission

If data are transmitted in the uplink and downlink simultaneously, UE needs to send data and TCP ACK/NACK information corresponding to downlink data. However, TCP ACK/NACK information may be blocked on the UE side by uplink data packet. Therefore, the TCP ACK information of downlink data is delayed, which may affect the downlink throughput. This feature can monitor the TCP packet reception in UE. If a TCP packet is received by UE correctly, TPE builds ACK information and sends it to the server. Then, the server TCP tx window can slide more quickly and the downlink throughput will be increased.

Enhancement

None

Dependency

None

2.18 LOFD-001027 Acitve Queue Management (AQM)

Availability


Summary

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



Benefits

The Active Queue Management feature improves the end user service in different ways. With AQM, where the buffer fill level is balanced to the UE data rate, the delay is significantly reduced.

Description

In an interactive packet-data connection, the packet data to be transferred is typically characterized by large variations, so the buffer is introduced to even out the variations. However, if the buffer is filled up or an overflow situation takes place, it will result in loss of data packets.

Currently, TCP as the main transport layer protocol is used on Internet. Packet loss is regarded as link congestion by TCP, and TCP will correspondingly reduce the data transmission rate. TCP protocol is also sensitive to round trip delay and it will take actions differently in case just one packet is lost or if a burst of packets is lost. In case of uncontrolled packet losses, it may take a considerable time for the data rate to increase again, leading to poor radio link utilization and causing long delays for the end user.

In addition, in case a user is performing parallel activities, e.g. FTP downloading and web browsing, if the file downloading as a dominant stream would fill the buffers and thereby cause a long delay for web browsing, before anything would happen when clicking on a link.

The functionality of AQM is provided as an optimized buffer handling method, in order to interact with the TCP protocol in a favorable manner and reduce the buffering delay while guaranteeing the high throughput. Huawei AQM solution is implemented based on the basic theory of RED (Random Early Detection). It introduces two congestion detection thresholds, including congestion threshold and maximum congestion threshold to detect PDCP buffer occupancy. Once the buffer is filled up to one of the thresholds, packet dropping mechanism will be applied correspondingly, avoiding buffer congestion or subsequent packets from being discarded.

The Huawei AQM solution is closely coupled with the TPE function. While TPE is working, packet dropping mechanism in AQM would not be triggered if the buffer occupancy is higher than the thresholds. Instead, TPE performs to constrain the downlink bit rate.

Operators can switch on/off the Active Queue Management function.

Enhancement

None

Dependency

None



2.19 LOFD-001029 Enhanced Admission Control

2.19.1 LOFD-00102901 Radio/transport Resource Pre-emption

Availability


Summary

This feature enables service differentiation when the network is congested to provide better services for high-priority users.

Benefits

This feature provides operators with a method to differentiate users according to their priority. High priority users can obtain the system resources in case of resource limitation. In this way, operators can provide better service to those high priority users.

Description

Pre-emption is the function related to admission control and is the method for differentiating services. It enables operators to provide different services by setting different priorities, which will affect the user call setup success rate during the call setup procedure. If there are not enough resources and a new call is not admitted to access to the network, high priority user will have more chances to access to the network than low priority users by pre-empting other low priority users.

The priority information is obtained from the E-RAB Level QoS Parameters including ARP (Allocation / Retention Priority), in the message of ERAB SETUP REQUEST. The eNodeB will assign the user priority based on ARP.

Pre-emption will take action if admitting a call fails due to lack of resource, including S1 transmission resource and radio resource (for example, QoS satisfaction ratio based admission check is failure). The service with the attribution of Pre-emption Capability and Pre-emption Vulnerability indicates the service ability of pre-empt and pre-emption vulnerability. The pre-emption capability indicates the pre-emption capability of the request on other E-RABs, and pre-emption vulnerability indicates the vulnerability of the E-RAB to preemption of other E-RABs.

In case of Signaling Radio Bearer (SRB), the pre-emption will not be triggered if resource allocation for SRB fails. For the emergency call (e.g., E911) service, on account of their very high priority, it always has the preemption capability. For the SRB, emergency call and IMS signaling, they cannot be preempted.

Enhancement

None



Dependency

Dependency on other NEs

This feature needs the core network to bring the ARP IE to eNodeB during E-RAB assignment procedure so that eNodeB can get the service priority with those E-RAB parameters.

2.20 LOFD-001038 RRU Channel Cross Connection Under MIMO

Availability


Benefits

When deployed in the field, perhaps the RRU is installed on top of the tower or the base station is installed in inaccessible area. The equipment cannot be easily maintained. In this case, if one RRU or RFU fails, the sector will be out of service for a long time. However, with this new scheme, one RRU or RFU failure will not cause the outage of the whole sector so that the service coverage can be ensured.

By reliability prediction, the availability of RRU will increase from 0.99999844 to 0.99999932. In addition, this scheme does NOT increase any hardware cost!

Description

This scheme can greatly increase equipment reliability without increasing hardware cost. By utilizing the independency of the MIMO channels, the sector service can be processed through different RRU. When one RRU fails, the other RRU can still process the service data of that sector so the total outage of that sector will not occur. Meanwhile, the performance of that faulty sector will be decreased. This scheme can be applied in X sector configuration and mTnR MIMO architecture.

Taking 2T2R RRU for example, there are three RRUs (from left to right is RRU1, RRU2 and RRU3) The left chart is for the legacy scheme and the right one is for the load sharing scheme. Antenna 1 is connected to RRU1 and RRU2. Antenna 2 is connected to RRU2 and RRU3. Antenna 3 is connected to RRU3 and RRU1. In the legacy scheme, when one RRU fails, the sector connected is totally out of service. While applying MIMO load sharing scheme, when one RRU, for example RRU1 fails, the other antenna of that sector is connected to RRU2, service in that faulty sector can still be processed. In the meanwhile, that operation mode is changed from 2T2R to 1T1R and the performance decreases (such as coverage area, throughput, etc). On the other hand, as sector 3 uses one transmit/receive channel of RRU1, the performance decreases as well. Moreover, because the antenna mode has change for both sector1 and sector3, it is necessary to reconfigure the cell data, which will cause 20s outage of service.



Enhancement

None

Dependency

This feature is more suitable for RRUs installed on top of the tower.

2.21 LOFD-001018 S1-flex

Availability




Summary

This feature is part of the MME Pool solution which needs the support from both the eNodeB and the MME. It allows an eNodeB to be connected to multiple MMEs simulately.

In eRAN2.0, Huawei eNodeB supports a maximum of 16 S1 interfaces. There is one MME on each S1 interface which can be also connected to several MMEs.

Benefits

This feature increases the flexibility of S1 interface and provides the following benefits:

Increases the overall usage of capacity of MME pool.

Improves the load sharing across MMEs in pool.

Avoids unnecessary signaling in the core network when the UE moves in the MME Pool Area because the served MME of the UE will not change.

Description

A connection topology between MME Pool and eNodeBs is shown as Figure 2-1:

Figure 2-1 connection topology between MME Pool and eNodeBs

If an eNodeB connects to a MME Pool, it indicates that the eNodeB must be able to determine which MME in the pool should receive the signaling sent from a UE:

If the UE gives the registered MME in the RRC signal message, the eNodeB will select the MME according with this information.

If the UE does not give the registered MME or the registered MME is not connected to the eNodeB, the eNodeB will select a MME as follow:



Topology-based MME Pool selection

The MME is selected based the network topology to reduces the possibility of switching MME during mobility.

Load-based MME selection

The MME is selected based on its capacity and load. The capacity of the MME can be informed to the eNodeB during the S1 setup by the MME. When an MME is overloaded, the eNodeB will not assign new UEs to the MME.

Enhancement

None

Dependency

MME must support MME Pool function simultaneously

2.22 LOFD-001047 LoCation Services (LCS)

Availability


Summary

LCS (LoCation Services) provides a method to identify UE’s geographical location through radio signal measurement.

Benefits

The feature LCS (LoCation Services) can be used to identify UE’s geographical location information such as longitude, latitude, velocity and so on. The geographical location information can be used to offer a range of location based value added services. For instance, it can be used by navigation applications, or for location requirements in emergency call/lawful interception situations. For example, for E911 service, the alarm center can locate the emergency call originator then conduct the appropriate rescue. The accuracy of LCS is about 50-300 meters, depending on method used and radio environment.

Description

The feature LCS provides a method to identify UE’s geographical location by radio signal measurement. A network element, E-SMLC (Enhanced Serving Mobile Location Centre), is needed to support this feature. It can be an independent network element in LTE core network or integrated in the MME.

The different positioning methods supported are:

Cell ID based – Basic accuracy (depending on radio network density)



OTDOA (Observed Time Difference Of Arrival) – Medium accuracy A-GPS – High accuracy

LCS feature is implemented mainly in E-SMLC and UE while the eNodeB acts as a transparent entity for messages and information measurement forwarding. A typical LCS procedure is:

MME receives LCS requirement for a target UE location, or MME starts LCS service by itself.

MME sends LCS requirement to E-SMLC. E-SMLC sends auxiliary data to UE, check related measurement information

from UE/eNodeB. E-SMLC calculates out location information of target UE and forward it to MME.

If MME does not host the LCS, MME will forward the location information to the network element which hosts the LCS.

Enhancement

None

Dependency UE should support LCS for A-GPS and OTDOA. OTDOA requires Time synchronization for E-UTRAN. MME should support LPPa protocol. E-SMLC is required.

2.23 LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN

Availability


Summary

PS inter-RAT Mobility between E-UTRAN and UTRAN provides the function of inter-RAT cell selection and reselection between E-UTRAN and UTRAN, and the function that the UEs can be handed over to an inter-RAT UTRAN cell for the reason of limited cell coverage. If the PS handover is not supported by the current networks, the PS redirection between E-UTRAN and UTRAN is provided to realize the inter-RAT mobility. Moreover, the blind handover is provided if inter-RAT measurements may be omitted (to save time and resources) or can be unavailable.

PS handover between E-UTRAN and UTRAN also supports the function that the UEs can be handed over to an inter-RAT UTRAN cell when there is uplink coverage restriction on E-UTRAN.

PS handover based on uplink power is supported. When UE’s service QoS is limited in uplink, eNodeB can trigger an inter-RAT handover to UTRAN to guarantee the service QoS.



Benefits

The feature provides the following benefits:

Enables the seamless co-existence between E-UTRAN and UTRAN Guarantees smooth evolution from legacy wireless systems to LTE systems. Provides supplementary coverage for E-UTRAN in the early phase using the

legacy wireless systems to prevent call drop, thus, seamless user coverage Improves the network performance and end user experience

Description

Handover between E-UTRAN and UTRAN is a critical feature to allow seamless co-existence and a smooth evolution from the legacy wireless communication systems to LTE system. It is one type of inter-Radio Access Technology (RAT) handover. It exists in the early E-UTRAN deployment when a UE moves to an area where E-UTRAN does not have coverage while UTRAN has.

In Huawei eRAN1.0, handover is based on the coverage by evaluating the cells’ DL reference signals that can be RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality) of E-UTRAN, and Received Signal Code Power (RSCP) or Ec/N0 of UTRAN .

When a UE moves out of the area of E-UTRAN, the eNodeB decides whether to handover it from E-UTRAN to UTRAN according to its reported measurement. The UE performs handover to the target UTRAN cell when it receives the handover command from the source eNodeB.The inter-RAT measurement of the target cell is gap-assisted for the UE with only one RF receiver. In the serving cell, the inter-RAT measurement is triggered by an event A2 that means the DL reference signal quality of E-UTRAN become worse than the absolute threshold, and stopped by an event A1 that means the DL reference signal quality of E-UTRAN becomes better than absolute threshold. The inter-RAT handover is triggered by an event B1 that means the Common Pilot Channel (CPICH), RSCP and/or Ec/N0 of UTRAN cells is better than absolute threshold. After receiving the measurement report from the UE, the eNodeB decides wether to hand over it to UTRAN. Huawei eNodeB also supports PS handover from UTRAN to E-UTRAN.

In some specific scenario, inter-RAT measurements may be omitted (to save time and resources) or can be unavailable. In such a scenario, Huawei provides Blind Handover to realize inter-RAT handover from E-UTRAN to UTRAN in eRAN2.0. For example, if an E-UTRAN cell is co-sited with a UTRAN site, and having the same coverage range, operators can configure the UTRAN cell as the E-UTRAN cell’s blind handover target cell. When handover trigger conditions (load, service) are met, the eNodeB can handover the UE to the blind handover target cell without inter-RAT measurement. Blind handover, compared to PS handover, features more reduced handover time.

If the legacy UTRAN or UEs can not support PS handover, Huawei provides PS redirection functionality to realize inter-RAT handover between UTRAN and E-UTRAN in eRAN2.0. There is no update requirement for legacy UTRAN and UEs to support PS Redirection. The procedure of PS redirection is the same as that of RRCConnectionRelease in which the carrier frequency infromation of the target redirection system will be included in the RRCConnectionRelease message. After a RRC connection of a UE is released by the source LTE system, the UE reselects the target system based on the received carrier frequency information during the release procedure and re-establishes



the connection with the target system. In summary, the handover mechanism of PS redirection consists of connection release, carrier-frequency re-selection, and connection re-establishment.

Note that the above description refers to a UE in active mode mobility. In idle mode mobiliy, Cell Selection and Reselection are procedures used for searching a new RAT serving cell. The UE will continually perform this procedure when it moves. Cell selection and Reselection for inter-RAT is usually performed in the following scenarios: Cell Selection: Procedure of cell selection is invoked when the UE initially turns

on. The cell of which technology is selected by the UE is based on the priority setting.

E-UTRAN toUTRAN Cell Reselection: The UE has initially camped on the LTE cell. When the UE moves out of E-UTRAN coverage, the UE needs to reselect UTRAN if available.

UTRAN to E-UTRAN Cell Reselection: The UE has camped initially either on a UTRAN cell. When the UE enters a cell of E-UTRAN coverage, and if E-UTRAN is configured with higher priority, the UE will reselect E-UTRAN. The priority information is broadcasted in cell system information.

When camping on a cell, the UE regularly searches for a better cell according to the cell reselection criteria. If a better cell is found, that cell is selected.

Generally speaking, LTE system is limited in uplink. Sometimes, QoS can be guaranteed in downlink, but in uplink it is not satisfied even UE has transmitted its full power. To guarantee UE’s service QoS in this scenario, Huawei supports uplink transmission power based inter-RAT handover to UTRAN.

While eNodeB detected UE’s QoS is limited, eNodeB will send measurement control message to UE. When UE reports B1 event to eNodeB, eNodeB decides whether to handover to UTRAN.

Enhancement

In eRAN2.0, PS Redirection and Blind Handover between E-UTRAN and UTRAN are supported.

In eRAN2.1, the Handover based on UL power is supported. It guarantees service continuity in uplink limited power or limited E-UTRAN coverage when a UE moves to the cell edge.

Dependency

The functionality of PS handover between E-UTRAN and UTRAN depends on UTRAN and Core Network’ support.



2.24 LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN

Availability


Summary

PS inter-RAT Mobility between E-UTRAN and GERAN provides the function of inter-RAT cell selection and reselection between E-UTRAN and GERAN, and the function that the UE can handover to an inter-RAT GERAN cell for the reasons of limited cell coverage. If the PS handover is not supported by the current network, the PS redirection between E-UTRAN and GERAN is provided to realize the inter-RAT mobility. Moreover, the blind handover is provided if inter-RAT measurements may be omitted (to save time and resources) or can be unavailable.

PS handover between E-UTRAN and GERAN supports also the function that the UEs can be handed over to an inter-RAT GERAN cell when there is uplink coverage restriction on E-UTRAN.

PS handover based on uplink power is supported. When UE’s service QoS is limited in uplink, eNodeB can trigger an inter-RAT handover to GERAN to guarantee the service QoS.

Benefits


Enables the seamless co-existence between E-UTRAN and GERAN Guarantees smooth evolution from legacy wireless systems to LTE systems Provides supplementary coverage for E-UTRAN in early phase using the legacy

wireless systems to prevent call drop, thus, seamless overage for the UE Improves the network performance and end user experience

Description

Handover between E-UTRAN and GERAN is a critical feature to allow a seamless co-existence and a smooth evolution from the legacy wireless communication systems to LTE systems. It is one type of the inter-RAT handover. It exists in the early phase of E-UTRAN when a UE moves into an area where E-UTRAN does not have coverage but GERAN has.

In Huawei eRAN1.0, handover is based on the coverage by evaluating the cells’ DL reference signals which can be RSRP, RSRQ of E-UTRA, and carrier Received Signal Strength Indicator (carrier RSSI) of GSM .When a UE moves out of E-UTRAN area, the eNodeB can decide whether to handover it from E-UTRA to GERAN according to its reported measurement. The UE performs handover to the target GERAN cell after receiving the handover command from the eNodeB.The inter-RAT measurement of the target cell is gap-assisted for UE with one RF receiver. In the serving cell, the inter-RAT measurement is triggered by an event A2 that means the quality of E-UTRAN DL reference signal becomes worse than the



absolute threshold, and stopped by an event A1 that means the quality of E-UTRAN DL reference signal is better than absolute threshold. The inter-RAT handover is triggered by an event B1 that means the carrier RSSI of GSM becomes better than absolute threshold. After receiving the measurement report from UE, the eNodeB decides to hand over the UE to GERAN. Huawei eNodeB also supports the PS handover between GERAN and E-UTRAN. In addtion to PS handover, Huawei eRAN1.0 also supports Cell Change Order (CCO) with or without NACC (Network Assisted Cell Change).

In some specific scenario, inter-RAT measurements may be omitted (to save time and resources) or can be unavailable. In such a scenario, Huawei provides Blind Handover solution to realize inter-RAT handover from E-UTRAN to GERAN in eRAN2.0. For example, if an E-UTRAN cell is co-sited with a GERAN cell, and having the same coverage range, operators can configure the GERAN cell as the E-UTRAN cell’s blind handover target cell. When handover trigger condition (load, service) is met, the eNodeB can handover the UE to the blind handover target cell without inter-RAT measurement. Blind handover, compared to PS handover, features more reduced handover time.

If the legacy GERAN networks or UEs can not support PS handover, Huawei provides PS redirection functionality to realize inter-RAT handover between GERAN and E-UTRAN in eRAN2.0. There is no update requirement for legacy GERAN networks and UEs to support PS Redirection. The procedure of PS redirection is the same as that of RRCConnectionRelease in which the carrier frequency information of the target redirection system will be included in the RRCConnectionRelease message. After a RRC connection of a UE is released by the source system, the UE reselects to the target system based on the received carrier frequency information during the release procedure and re-establishes the connection with the target system. In summary, the handover mechanism of PS redirection consists of connection release, carrier frequency re-selection, and connection re-establishment.

Note that the above description refers to a UE in active mode mobility. In idle mode mobiliy, Cell Selection and Reselection are procedures used for searching a new serving cell. The UE will continually perform this procedure when it moves. Cell selection and reselection for inter-RAT is usually performed in the following scenarios: Cell Selection: procedure of cell selection is invoked when the UE initially turns

on. the cell of which technology is selected by the UE is based on the priority setting.

E-UTRAN to GERAN Cell Reselection: the UE has initially camped on the LTE cell. When the UE moves out of E-UTRAN coverage, the UE needs to reselect GERAN if available.

GERAN to E-UTRAN Cell Reselection: the UE has camped initially either on a GERAN cell. When the UE enters a cell of E-UTRAN coverage, and if E-UTRAN is configured with higher priority, the UE will reselect E-UTRAN. The priority information is broadcasted in cell system information.

When camping on a cell, the UE regularly searches for a better cell according to the cell reselection criteria. If a better cell is found, that cell is selected.

Generally speaking, LTE system is limited in uplink. Sometimes, QoS can be guaranteed in downlink, but in uplink it is not satisfied even UE has transmitted its full power. To guarantee UE’s service QoS in this scenario, Huawei supports uplink transmission power based inter-RAT handover to GERAN.



While eNodeB detected UE’s QoS is limited, eNodeB will send measurement control message to UE. When UE reports B1 event to eNodeB, eNodeB decides whether to handover to GERAN.

Enhancement

In eRAN2.0, PS Redirection and Blind Handover between E-UTRAN and GERAN are supported.

In eRAN2.1, the Handover based on UL power is supported. It guarantees service continuity in uplink limited power or limited E-UTRAN coverage when a UE moves to the cell edge.

Dependency

The functionality of PS handover between GERAN and E-UTRAN depends on GERAN and Core Network’ support. NACC also requires GERAN and Core Network’ support.

2.25 LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000

Availability


Summary

This feature provides the function of inter-RAT cell selection and reselection between LTE and CDMA2000 and enables High Rate Packet Data (HRPD) services to be handed over between E-UTRAN and the CDMA2000.

Benefits


Enables seamless co-existence of E-UTRAN and CDMA2000.

Supports smooth evolution from CDMA2000 to E-UTRAN

Provides supplementary coverage for E-UTRAN in the early phase to prevent call drops and enables seamless coverage, thus improving the network performance and user experience.

Description

Handover between E-UTRAN and CDMA2000 (only for HRPD) enables seamless co-existence of E-UTRAN and CDMA2000 and supports smooth evolution from CDMA2000 to E-UTRAN. It is a type of Inter-Radio Access Technology (RAT) handover. It is available in the early phase of LTE when a UE moves from an E_UTRAN coverage area to a CDMA2000 coverage area.



In Huawei LTE eRAN1.0, handover is based on the coverage by evaluating the downlink reference signals of the cells in terms of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ) of E-UTRA, and Rx Power Strength of CDMA2000. For handover from E-UTRAN to HRPD, Huawei supports both non-optimized and optimized handover mechanisms specified in 3GPP TS 23.402. In the procedure of non-optimized handover, a UE does not pre-register in the HRPD system. When it moves out of the area of E-UTRA, the UE can decide whether to perform handover from E-UTRA to HRPD according to the measurement results, and then initiate the handover to the target HRPD cell. In the procedure of optimized handover, a UE pre-registers in the HRPD system. When it moves out of the area of E-UTRA, the eNodeB can decide whether to perform handover from E-UTRA to HRPD according to the measurement report from the UE. Then, the UE initiates the handover to the target HRPD cell after receiving the handover command sent by the eNodeB.The inter-RAT measurement of the target cell is gap-assisted for the UE with one RF receiver. It is triggered by event A2 that means the quality of E-UTRA downlink reference signals becomes worse than the absolute threshold and stopped by event A1 that means the quality of E-UTRA downlink reference signals becomes better than the absolute threshold. The inter-RAT measurement of the target cell is gap-assisted for UE with one RF receiver. In the serving cell, the inter-RAT measurement is triggered by an event A2 that meansthe quality of E-UTRAN DL reference signal becomes worse than the absolute threshold, and stopped by an event A1 that means the quality of E-UTRAN DL reference signal is better than absolute threshold. The parameters for inter-RAT handover can be configured for different services.The previously mentioned handover is PS handover from E-UTRAN to CDMA2000 (only for HRPD).

Huawei eNodeB also supports PS handover from CDMA2000 to E-UTRAN, but from an E2E solution point of view, this type of handover depends not only on LTE capability, but also whether the CDMA2000 system and the core network support it.

Enhancement

None

Dependency

The functionality of PS handover from CDMA2000 to E-UTRAN depends on whether the CDMA2000 system and the core network support this type of handover.

2.26 LOFD-001022 SRVCC to UTRAN

Availability




Summary

Single Radio Voice Call Continuity (SRVCC) is voice call continuity between IMS over PS access and CS access for calls that are anchored in the IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time.

Benefits

When a UE moves from E-UTRAN to UTRAN, SRVCC maintains voice call continuity for the UE.

Description

When a UE moves from E-UTRAN to UTRAN, SRVCC is used to maintain voice call continuity for the UE.

For facilitating session transfer (SRVCC) of the voice component to the CS domain, the IMS multimedia telephony sessions need to be anchored in the IMS.

For SRVCC from E-UTRAN to UTRAN, the MME first receives the handover request from E-UTRAN with the indication that this is for SRVCC handling, and then triggers the SRVCC procedure with the MSC Server enhanced for SRVCC through the Sv reference point if the MME has SRVCC STN-SR information for this UE. The MSC Server enhanced for SRVCC then initiates the session transfer procedure to the IMS and coordinates it with the CS handover procedure to the target cell. The MSC Server enhanced for SRVCC then sends the Forward Relocation Response to the MME, which includes the necessary CS HO command information for the UE to access the UTRAN.

Handling of any non-voice PS bearer is done by the PS bearer splitting function in the MME. The MME may suppress the handover of non-voice PS bearer during the SRVCC procedure. The handover of non-voice PS bearer is performed according to the inter-RAT handover procedure defined in 3GPP TS 23.401. The MME is responsible for processing the Forward Relocation Response from the MSC Server during the SRVCC and PS-PS handover procedures.

Figure 2-1 shows the SRVCC from E-UTRAN to UTRAN



Figure 2-1 SRVCC from E-UTRAN to UTRAN

UE E-UTRAN MME MSC ServerTarget

UTRAN/GERAN

MeasurementReports

Handover to UTRAN/GERAN required

3GPP IMS

Initiates SRVCC for voice component

CS handover preparation

IMS Service Continuity ProcedureHandles PS-PS HO for

non-voice if needed

PS HO response to MME(CS resources)

To eUTRANCoordinates SRVCC and PS HO response Handover CMD

Handoverexecution

Enhancement

None

Dependency

IMS multimedia telephony

2.27 LOFD-001023 SRVCC to GERAN

Availability


Summary

SRVCC is voice call continuity between IMS over PS access and CS access for calls that are anchored in the IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time.

Benefits

When a UE moves from E-UTRAN to GERAN, SRVCC maintains voice call continuity for the UE.

Description

When a UE moves from E-UTRAN to GERAN, SRVCC is used to maintain voice call continuity for the UE.



For facilitating session transfer (SRVCC) of the voice component to the CS domain, the IMS multimedia telephony sessions need to be anchored in the IMS.

For SRVCC from E-UTRAN to GERAN, the MME first receives the handover request from E-UTRAN with the indication that this is for SRVCC handling, and then triggers the SRVCC procedure with the MSC Server enhanced for SRVCC through the Sv reference point if the MME has SRVCC STN-SR information for this UE. The MSC Server enhanced for SRVCC then initiates the session transfer procedure to the IMS and coordinates it with the CS handover procedure to the target cell. The MSC Server enhanced for SRVCC then sends the Forward Relocation Response to the MME, which includes the necessary CS HO command information for the UE to access the GERAN.

Handling of any non-voice PS bearer is done by the PS bearer splitting function in the MME. The MME may suppress the handover of non-voice PS bearer during the SRVCC procedure. The handover of non-voice PS bearer is performed according to the inter-RAT handover procedure defined in 3GPP TS 23.401. The MME is responsible for processing the Forward Relocation Response from the MSC Server during the SRVCC and PS-PS handover procedures.

Figure 2-1 shows the SRVCC from E-UTRAN to GERAN

Figure 2-1 SRVCC from E-UTRAN to GERAN

UE E-UTRAN MME MSC ServerTarget

UTRAN/GERAN

MeasurementReports

Handover to UTRAN/GERAN required

3GPP IMS

Initiates SRVCC for voice component

CS handover preparation

IMS Service Continuity ProcedureHandles PS-PS HO for

non-voice if needed

PS HO response to MME(CS resources)

To eUTRANCoordinates SRVCC and PS HO response Handover CMD

Handoverexecution

Enhancement

None

Dependency

IMS multimedia telephony



2.28 LOFD-001032 Intra-LTE Load Balancing

Feature Number: LOFD-001032

Availability


Summary

It can resolve the unbalance between the service cell and the intra-frequency or inter-frequency neighbor cells.

Benefits

It can utilize the network resource fully and improve the system capacity by balancing the load between the neighbor cells. In addition, it reduces the rate of system overload and improves the access success rate.

Description

In some situation of commercial LTE network, some serving cells have high load but other neighbor cells load is low because of the differentia of UE service. Under this condition, it can trigger load balancing algorithm.

The serving cell measures the cell load and receives the neighboring cell’s load at the same time. The serving cell evaluates the load and decides whether to handover to neighboring cell. If the serving cell load is very high which is beyond the threshold, at the same time, the neighboring cell’s load is low, some UEs begin to handover to neighboring cell in advance. The cell load is defined according to TS 36314, which is utilization rate of PRB.

For intra-frequency load balancing, there are two type of load balance: active load balancing and idle load balancing. The idle load balancing is to update Qoffset and notice UE by system broadcast information.

The active load balancing procedure includes the following steps: load measurement and evaluation, load information exchanges, load balance decision, modification of CIO parameter and monitoring of performance.

For inter-frequency load balancing, there is only one type of load balancing: active load balancing. The active load balancing procedure includes the following steps: load measurement and evaluation, load information exchanges and load balance decision.

Intra-LTE load balancing is used in the scenario of overlap coverage area by the multi intra-frequency LTE cells or multi inter-frequency LTE cells.

Enhancement

None



Dependency

An X2 interface is required to support intra-LTE intra-frequency. It also depends on the load control function to get the cell load information and mobility management to finish handover.

2.29 LOFD-001044 Inter-RAT Load Sharing to UTRAN


Availability


Summary

This feature is used in the LTE and UMTS which coverage the same area and the two system’s load is unbalance.

Benefits

It can improve the system resource utilization rate at the same time that it can guarantee the service QoS. It can reduce the possibility of system overload and decrease the service dropping rate.

Description

In some situation of commercial LTE network, LTE cells have high load but UMTS system load is low because of the differentia of UE service. Under this condition, it can trigger load balance algorithm.

The LTE cell measures the cell load and evaluates the load. Then it decides whether to handover to neighboring cell. If the LTE cell load is very high which is beyond the threshold, some UE begins to handover to UMTS system. The cell load is defined according to TS 36314, which is utilization rate of PRB.

There is only one type of inter-LTE load balance: active load balance. The active load balance procedure includes the following steps: load measurement and evaluation, load balance trigger, UE dedicate priority update, choosing handover UE and handover execution.

This feature is used in the scenario of repetition coverage area by LTE and UMTS.

Enhancement

In eRAN2.1, the Inter-RAT Load Sharing to UTRAN feature is enhanced with the following administration functions:

Switch: user can enable or disable the Inter-RAT Load Sharing to UTRAN function.



Dependency

It depends on the Inter-RAT handover function to execute the load balancing.

2.30 LOFD-001045 Inter-RAT Load Sharing to GERAN


Availability


Summary

This feature is used in the LTE and GSM which coverage the same area and the two system’s load is unbalance.

Benefits

It can improve the system resource utilization rate at the same time that it can guarantee the service QoS. It can reduce the possibility of system overload and decrease the service dropping rate.

Description

In some situation of commercial LTE network, LTE cells have high load but GERAN system load is low because of the differentia of UE service. Under this condition, it can trigger load balance algorithm.



The LTE cell measures the cell load and evaluates the load. Then it decides whether to handover to neighboring cell. If the LTE cell load is very high which is beyond the threshold, some UE begins to handover to GERAN system. The cell load is defined according to TS 36314, which is utilization rate of PRB.

There is only one type of inter-LTE load balance: active load balance. The active load balance procedure includes the following steps: load measurement and evaluation, load balance trigger, UE dedicate priority update, choosing handover UE and handover execution.

This feature is used in the scenario of repetition coverage area by LTE and GERAN.

Enhancement

In eRAN2.1, the Inter-RAT Load Sharing to GERAN feature is enhanced with the following administration functions:

Switch: user can enable or disable the Inter-RAT Load Sharing to GERAN function.

Dependency

It depends on the Inter-RAT handover function to execute the load balancing.

2.31 LOFD-001043 Service based inter-RAT handover to UTRAN


Availability


Summary

It is to steer the VOIP service to UMTS and LTE system support PS service during the service setup phase.

Benefits

It can utilize the legacy network resource and improve LTE system capacity at the same time that it can guarantee the service QoS. It can reduce the possibility of system overload and decrease the service dropping rate.

Description

LTE system sends inter-system measurement control message to UE which want to set up VOIP service and notices it to execute the measurement. When UE reports B1



event to eNodeB, eNodeB decides whether to setup service in the UMTS based on RAB QCI handover strategy.

Enhancement

None

Dependency

It depends on the inter-RAT handover function to execute the handover. It is also related with RAB QCI, which decides whether to execute handover.

2.32 LOFD-001046 Service based inter-RAT handover to GERAN


Availability


Summary

It is to steer the VOIP service to GERAN and LTE system support PS service during the service setup phase.

Benefits

It can utilize the legacy network resource and improve LTE system capacity at the same time that it can guarantee the service QoS. It can reduce the possibility of system overload and decrease the service dropping rate.

Description

LTE system sends inter-system measurement control message to UE which want to set up VOIP service and notices it to execute the measurement. When UE reports B1 event to eNodeB, eNodeB decides whether to setup service in the GERAN based on ERAB (EPS RAB) QCI handover strategy.

Enhancement

None

Dependency

It depends on the inter-RAT handover function to execute the handover. It is also related with RAB QCI, which decides whether to execute handover.



2.33 LOFD-001033 CS Fallback to UTRAN

Availability

This feature is available in eRAN2.0

Summary

When UE is in the E-UTRAN and UTRAN coverage overlapped area and E-UTRAN cannot provide CS-domain services for the UE, we can use CS fallback to UTRAN to provide CS-domain service for the UE.

Benefits

We can use CS fallback to UTRAN to provide CS-domain service for the UE which is camped in the E-UTRAN that cannot provide any CS-domain service for the UE

DescriptionThe CS fallback in EPS enables the provisioning of CS-domain services by reuse of CS infrastructure when the UE is served by E-UTRAN. A CS fallback enabled terminal, connected to E-UTRAN may use UTRAN to establish one or more CS-domain services. This function is only available in case E-UTRAN coverage is overlapped by UTRAN coverage.CS fallback and IMS-based services shall be able to co-exist in the same operator’s network.The CS fallback in EPS function is realized by using the SGs interface mechanism between the MSC Server and the MME.Figure 2-1 CS fallback in EPS architecture

The MGW is not shown in the figure since the CS fallback in EPS does not have any impacts to the U-plane handling.

Enhancement

None



Dependency

This feature depends on LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN.

2.34 LOFD-001034 CS Fallback to GERAN

Availability

This feature is available in eRAN2.0

Summary

When UE is in the E-UTRAN and GERAN coverage overlapped area and E-UTRAN cannot provide CS-domain services for the UE, we can use CS fallback to GERAN to provide CS-domain service for the UE.

Benefits

We can use CS fallback to GERAN to provide CS-domain service for the UE which is camped in the E-UTRAN that cannot provide any CS-domain service for the UE

DescriptionThe CS fallback in EPS enables the provisioning of CS-domain services by reuse of CS infrastructure when the UE is served by E-UTRAN. A CS fallback enabled terminal, connected to E-UTRAN may use GERAN to establish one or more CS-domain services. This function is only available in case E-UTRAN coverage is overlapped by GERAN coverage.CS fallback and IMS-based services shall be able to co-exist in the same operator’s network.The CS fallback in EPS function is realized by using the SGs interface mechanism between the MSC Server and the MME.Figure 2-1 CS fallback in EPS architecture




Enhancement

None

Dependency

This feature depends on LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN.

2.35 LOFD-001035 CS Fallback to CDMA2000 1xRTT


Availability


Summary

When UE is in the E-UTRAN and overlapped CDMA2000 1xRTT coverage area and E-UTRAN cannot provide CS-domain services for the UE, we can use CS fallback to CDMA2000 1xRTT to provide CS-domain service for the UE.

Benefits

We can use CS fallback to CDMA2000 1xRTT to provide CS-domain service for the UE which is camped in the E-UTRAN that cannot provide any CS-domain service for the UE

DescriptionThe CS fallback in EPS enables the provisioning of CS-domain services by reuse of CS infrastructure when the UE is served by E-UTRAN. A CS fallback enabled terminal, connected to E-UTRAN may use CDMA2000 1xRTT to establish one or more CS-domain services. This function is only available in case E-UTRAN coverage is overlapped by CDMA2000 1xRTT coverage.CS fallback and IMS-based services shall be able to co-exist in the same operator’s network.The CS fallback in EPS function is realized by using the S102 interface mechanism between the 1x CS IWS (1xCS Interworking Solution) and the MME. S102 interface provides a tunnel between the MME and the 1xCS IWS to relay 3GPP2 1xCS signaling messages.



Figure 2-1 CS fallback in EPS architecture


Enhancement

None

Dependency

It depends on the inter-RAT handover function to execute the handover.

2.36 LOFD-001036 RAN Sharing with Common Carrier

Availability


Summary

The eNodeB supports multiple operators sharing the same Radio Access Network (RAN), where the operators use common carriers in the same eNodeB

Benefits

Operators can share the RAN resource to reduce CAPEX and OPEX.

Description

The MOCN (Multiple Operator Core Network) network sharing solution is to share the RAN resources, including frequency and baseband resources for all the operators. Different operators share the same cell and each eNodeB can connect with all



operators’ Core Networks. The system information broadcasted in each shared cell contains the PLMN-id of each operator

(up to 4) and a single tracking area code (TAC), which is valid within all the PLMNs sharing the radio access network resources. The architecture is depicted as follows.

All the LTE UEs supporting MOCN should be able to read up to 4 PLMN-ids and select one of the PLMN-ids at initial attachment. UEs indicate the selected PLMN-id to the eNodeB. The eNodeB shall select an appropriate MME for the PLMN-ids indicated by the UE.

The MOCN Network Sharing solution supports shared master OSS which is linked to different NMS through different interfaces.

The shared eNodeB and non-shared eNodeB can be connected to each other. In the shared area, a UE can hand over from one shared eNodeB to another one. If UE moves to a non shared area, the eNodeB will select an appropriate neighbor cell for the handover based on some principles, for example, the same operator’s network may be considered firstly. The Inter-working between different RATs may be used during the handover.

The MOCN Network Sharing has the following features.

Multi PLMN-ids are broadcasted on the common carrier and the Core Network is separated.

Support independent logo and name display.

The shared OSS connects different NMS through Itf-N interference.

Support up to 4 operators.

Enhancement

None

Dependency

This feature depends on LOFD-001018 S1-flex.



2.37 LOFD-001037 RAN Sharing with Dedicated Carrier

Availability


Summary

The eNodeB supports multiple operators to share the same Radio Access Network (RAN), where the operators use dedicated carriers in the same eNodeB.

Benefits

Operators can share the RAN resource to reduce Capital of Expenditure (CAPEX) and Operational Expenditure (OPEX).

Description

Huawei supports Radio Access Network sharing as a part of Network sharing functions. The LTE RAN Sharing Solution with dedicated carrier enables multiple operators to share all eNodeB hardware resources. Different core networks are connected to the same eNodeB separately. Multiple operators can cover the same area with their own frequency in a single physical RAN. A tracking area should include multiple completed shared cells. The architecture is shown in the following figure.

When a UE accesses a cell, the eNodeB identifies which core network it should be routed to according to the cell it comes from its originating cell. Different cells are corresponding to different operators. If S1-flex is applied, the eNodeB may select an MME node for UE by GUMMEI which is part of UE’s GUTI.

The Network Sharing solution supports shared master OSS which is linked to different NMS through different interfaces. Cell-level FM&PM data can be independent for all operators.

The shared eNodeB can be connected to non-shared eNodeB and there is no restriction for a UE to hand over from a shared eNodeB to a non-shared one .When operators



have dedicated network in the non-shared area, the UE will be only handed over to the same operator’s network although the target network (same operator) might not be LTE.

The dedicated carrier Network Sharing has the following features:

Each operator broadcasts its own PLMN-id using its own carrier and within its own Core Network separately.

Support independent logo and name display.

Independent cell-level FM&PM. The shared OSS connects different NMS through Itf-N interference.

Independent License Management.

Independent feature activation and deactivation.

Enhancement

None

Dependency

This feature depends on LOFD-001018 S1-flex.

2.38 LOFD-001024 Remote Electrical Tilt Control

Availability


Summary

Remote Electrical Tilt Control improves the efficiency and minimizes the OM cost for adjusting the down tilt of the antenna. Huawei LTE RET solution complies with the AISG2.0 specification, and it is backward compatible with AISG1.1.

Benefits

The application of the RET prominently improves the efficiency and minimizes the OM cost for adjusting the down tilt of the antenna. The application of the RET brings the following benefits:

The RET antennas at multiple sites can be adjusted remotely within a short period. This improves the efficiency and reduces the cost of network optimization.

Adjustment of the RET antenna can be performed in all weather conditions.

The RET antennas can be deployed on some sites that are difficult to access.

RET downtilt adjustment can keep the coverage pattern undistorted, therefore strengthening the antenna signal and reducing neighboring cell interference.



Description

The Remote Electrical Tilt (RET) refers to an antenna system whose down tilt is controlled electrically and remotely.

After an antenna is installed, the down tilt of the antenna needs to be adjusted to optimize the network. In this situation, the phases of signals that reach the elements of the array antenna can be adjusted under the electrical control. Then, the vertical pattern of the antenna can be changed.

The phase shifter inside the antenna can be adjusted through the step motor outside the antenna. The down tilt of the RET antenna can be adjusted when the system is powered on, and the down tilt can be monitored in real time. Thus, the remote precise adjustment of the down tilt of the antenna can be achieved.

Huawei LTE RET solution complies with the AISG2.0 specification, and it is compatible with AISG1.1.

Enhancement

None

Dependency

Huawei OMC M2000 or the eNodeB LMT should support the control commands to RET.

2.39 LOFD-001025 Adaptive Power Consumption

Availability


Summary

Huawei LTE eRAN2.0 supports the green eNodeB solution with power saving management. This solution has two sub-features: Adaptive Power Adjustment and eNodeB regular time shutdown and startup.

Benefits

This feature improves the efficiency of the power amplifier (PA) and saves power consumption of the eNodeB.

Description

Huawei LTE eRAN2.0 supports the green eNodeB solution with power saving management. This solution has two sub-features: Adaptive Power Adjustment and eNodeB regular time shutdown and startup.



Adaptive power Adjustment

Huawei Adaptive Power Adjustment solution, based on the traffic load, supports dynamic adjustment of the PA working state, and thereby improves PA efficiency and saves eNodeB power consumption.

The typical application scenarios are described as follows:

1. According to the change of traffic load in the day and at night, the PA working state is changed dynamically.

2. According to the change of traffic load in the working days and non-working days in the business districts, the PA working state is changed dynamically.

3. At the early stage of network deployment, the traffic is usually low, and the PA working state should be adjusted based on the actual traffic.

eNodeB regular time shutdown and startup

In some scenarios, such as high-speed railway, which will stop operating at late night, the RRU transmission channel of eNodeB can be shutdown and startup automatically at preset time based on the operator's configuration.

Enhancement

None

Dependency

The EMS system should support the configuration of eNodeB regular time shutdown and startup.

2.40 LOFD-001039 RF Channel Intelligent Shutdown

Availability


Summary

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

Benefits

Without load, the eNodeB can switch off carrier on some transmit channels to reduce the power consumption of the eNodeB.



Description

An eNodeB in the LTE system is usually configured with two or four antennas. The traffic in the cell varies by time. In some certain periods, for example, from the midnight to the early morning (operators can customize the periods), there is no traffic. When the idle status is detected by the eNodeB, it switched off the carrier on one transmission channel (if there are two transmission channels) or on two transmission channels (if there are four transmission channels) to decrease the power consumption. When a UE accesses the cell or the periods end, the eNodeB can automatically switch on the carrier that is switched off. Then, the cell recovers to the normal state and continues with services. The service quality of the cell is not affected.

Enhancement

None

Dependency

DL 2 x 2 MIMO or DL 4 x 2 MIMO

2.41 LOFD-001040 Low Power Consumption Mode

Availability


Summary

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

Benefits

In some cases like power outage, an eNodeB can be forced to run in low power consumption mode. When an eNodeB is derated, its power consumption is reduced and its in-service time powered by battery is expanded. Therefore, the possibility of eNodeB going out of service is reduced when power supply cannot come back to service in time.

Description

The low consumption running mode is implemented in four levels. If the power supply still cannot recover to the normal state when the power consumption of a level reaches the time threshold preset by the operator, the eNodeB enters into the low consumption running mode of the next level till the cell exits from services.

The low power consumption mode of the eNodeB is triggered by one of the following conditions:



Alarms of the power system

If the power insufficiency or power failure lasts for the period preset by the operator, an alarm is generated to trigger the low power consumption mode of the eNodeB.

Forcible command delivered by the EMS

The operator can deliver a command through the EMS to force the eNodeB to enter or exit from the low power consumption mode.

Enhancement

None

Dependency

None

2.42 LOFD-001041 Power Consumption Monitoring

Availability


Summary

The eNodeB reports the power consumption status to the EMS. Through the EMS, the change in power consumption of the eNodeB can be monitored by the operator, and a report on the power consumption can be generated.

Benefits

The eNodeB reports the power consumption status to the EMS. Therefore, the operator can monitor the power consumption of the eNodeB. With the report on the power consumption, the operator can exactly know the benefits brought by the decrease in power consumption.

Description

The eNodeB periodically monitors the power of each monitoring point and reports the power consumption within a period. The EMS receives and collects all data about power consumption. Through the EMS, the operator can observe the change in the power consumption and analyze the power consumption according to a statistics report generated by the EMS.



Enhancement

None

Dependency

None

2.43 LOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage

Availability


Summary

When there is little traffic in an area that is covered by multiple carriers, some of the carriers can be blocked, and all services can be automatically taken over by the carriers that remain in service. When the traffic increases to a certain degree, the carriers that are blocked can be unblocked again automatically to provide services.

Benefits

When there is little traffic in an area that is covered by multiple carriers, some of the carriers can be blocked, and all services can be taken over by the carriers that remain in service. This can help reduce the power consumption of the eNodeB without any impact on the service quality.

Description

When multiple carriers provide coverage for the same area, the traffic of the area varies by time. In some certain periods, for example from the midnight to the early morning (the periods can be preset by the operator), the traffic is light. When the eNodeB detects the light traffic, it triggers UEs to perform migration to some of the carriers and then blocks the carriers without any load. In this way, the power consumption is reduced. When the traffic increases or the preset periods end, the eNodeB can automatically switch on the carriers that are unblocked to recover the functionality of the carriers. In this way, the system capacity is increased without any impact on the service quality.

Enhancement

None

Dependency

None



2.44 LOFD-002001 Automatic Neighbor Relation (ANR)

Availability


Summary

The automatic neighbor relation feature takes advantage of the eNodeB algorithm to plan and configure automatically the neighbor relations, and to solve the problems of incorrect neighboring relations configuration. This feature greatly reduces the OPEX for the operator by avoiding human intervention and saving labor work.

Benefit

This feature provides the following benefits:

Missing or incorrect neighboring relations can be found or optimized. Therefore, no handover failure is caused by missing or incorrect neighboring relations configuration.

The Physical Cell Identity (PCI) collision detection can be triggered

Description

ANR can automatically add and update neighboring relations in the Neighboring Relation Table (NRT). However, the manual configuration of NRT’s attribution including NO HO and NO REMOVAL has higher priority than ANR algorithm. For example, if operator sets up NO REMOVAL, ANR will not remove this record from NRT.

The ANR process is described as follow:

Figure 2-1 Automatic neighbor relation function

The eNodeB instructs the UE for which the LTE frequency needs to be measured.



The UE sends a measurement report regarding cell B. This report contains cell B’s PCI, but not includes its GCI (Global Cell Identity). When the eNodeB receives a UE measurement report containing the PCI that is not included in the NRT for that cell, the following sequence may be used.

The eNodeB instructs the UE to use the newly discovered PCI as parameter to read the GCI of the related neighboring cell. The eNodeB may need to schedule appropriate gaps to allow the UE to read the GCI of the neighboring cell, as the UE needs to decode the new cell’s broadcasted GCI.

When the UE has read the new cell’s GCI, it reports the detected GCI to the serving cell eNodeB.

The eNodeB decides to add this neighboring relation and uses the PCI and GCI to perform the following operations: Searches a transport layer address to the new eNodeB (OM search or MME

search mechanisms that have been already standardized by the 3GPP. Updates its NRT

There are two major mechanisms for the eNodeB/cell to find new neighboring cell.

The neighboring cell’s PCI is reported to the eNodeB in the UE measurement report, and then, the eNodeB instructs the UE to read the GCI of the new neighboring cell.

The neighboring cell’s GCI is sent to the eNodeB in the UE history information of HANDOVER REQUEST, and then the eNodeB requests the PCI of the new neighboring cell.

After the eNodeB adds the new neighboring cell, the PCI collision detection procedure will be activated. For details on PCI collision detection, refer to LOFD-002007 PCI Collision Detection & Self-Optimization.

If needed, an X2 link establishment can also be activated through the Automatic Transport Setup function in feature LOFD-002004 Self-configuration.

The periodic ANR is supported. Its measurements refer to select and configure UEs to report for strongest cells (intra LTE) on a periodical time basis. In case a UE reports an unknown layer 1 cell identity (PCI) the eNodeB shall trigger ANR measurements to find out the corresponding GCI. Periodical ANR increases handover performance.

EnhancementIn eRAN2.1, ANR feature is enhanced with the following administration functions: Log: records the key event during the SON process and this information can be

used for query and statistic. Operator can also analyse the log information to master the feature running process and key event.

Dependency This feature should be supported by EMS equipment (Huawei iManager M2000

and Huawei i-Plan in the case of simulation preview). The PCI collision detection requires LOFD-002007 PCI Collision Detection &

Self-Optimization. The automatic X2 link configuration requires LOFD-002004 Self-configuration.



2.45 LOFD-002002 Inter-RAT ANR

Availability


Summary

The inter-RAT ANR functionality takes advantage of the eNodeB algorithm to plan, configure neighboring relations, and solve the problem of incorrect neighboring relations between E-UTRAN and GERAAN/UTRAN/CDMA2000.

Benefit

In LTE system, the inter-RAT neighboring relations can be automatically added without human intervention, thus reducing the OPEX of the operator.

Description

Inter-RAT ANR can add neighboring relations in the LTE eNodeB automatically through UE inter-RAT measurement.

The coverage of particular radio technologies (RAT) will be broadcasted in E-UTRAN. Then, the UE can measure and report the existence of these RATs to the LTE eNodeB instructing it to build up inter-RAT neighboring relations for further inter-RAT mobility.

The inter-RAT ANR consists of the following functions:

Measures the existence of the CDMA2000 cell, UTRAN cell, and GERAN cell Establishes E-UTRAN -> other RAT neighboring relations inside the LTE

eNodeB Establishes E-UTRAN -> other RAT mobility constraints (for example, operator

mobility limitation policy)The inter-RAT ANR process is described as follow:



Figure 2-1 Inter-RAT ANR function

It is assumed that this function is executed by mean of the M2000 (Huawei OM platform) system, which can manage:

Inter-RAT/frequency Searchlist: List of RATs/frequencies that shall be searched.

Inter-RAT/frequency ANR Blacklist: List of cells that shall not be included in the eNodeB inter-RAT/frequency neighbor lists.

It is also assumed that the OM system is informed about changes in the eNodeB inter-RAT/frequency neighbor lists.

The eNodeB serving cell A has an ANR function. During a normal call procedure, the eNodeB instructs each UE to perform measurements and detect cells on other RATs/frequencies. The eNodeB may use different policies for instructing the UE to perform measurements and then to report them to the eNodeB.

The eNodeB instructs the UE to search neighboring cells in the target RATs/frequencies. The eNodeB may need to schedule appropriate gaps to allow the UE to scan all cells in the target RATs/frequencies.

The UE reports the PCI of the detected cells in the target RATs/frequencies and their respective signal quality. The carrier frequency and Primary Scrambling Code (PSC) define the PCI in case of UTRAN cell, and the Band Indicator + BSIC + BCCH ARFCN in case of GERAN cell.

When the eNodeB receives UE reports containing Phy-CIDs of cells that are not already in inter-RAT/frequency neighbor lists of that cell, the following sequence may be used.

The eNodeB instructs the UE to use the newly discovered Phy-CID as parameter and read the Global-CID of the detected neighboring cell in the target RAT/frequency. The eNodeB may need to schedule appropriate gaps to allow the



UE to read the Global-CID from the broadcast channel of the detected neighboring cell.

When the UE has read the new cell’s Global-CID, it reports the detected Global-CID to the serving cell eNodeB.

The eNodeB updates its inter-RAT/frequency neighbor lists.

Periodic inter-RAT ANR is supported. Its measurements refer to select and configure UEs to 'report for strongest cells' (intra LTE) or 'report for strongest cells for SON' (inter-RAT) on a periodical time base. In case a UE reports an unknown layer 1 cell identity (PCI, PSC, and BSIC) the eNodeB shall trigger inter-RAT ANR measurements to find out the corresponding GCI. Periodic inter-RAT ANR increases performance in handover procedure

Enhancement

In eRAN2.1, the inter-RAT-ANR feature is enhanced with the following administration functions:

Setting: Switch: user can enable or disable the feature or sub-function such as

periodic inter-RAT HO function in inter-RAT HO Log: records the key event during the SON process and this information can be

used for query and statistical. Operator can also analyse the log information to master the feature running process and key event.

Dependency

This feature should be supported by EMS equipment (Huawei iManager M2000 and Huawei i-Plan in the case of simulation preview).

2.46 LOFD-002004 Self-configuration

Availability


Summary

The eNodeB can automatically establish an OM link, obtain the configuration data file and software from the EMS, and then activate the configuration data file and software automatically. The configuration data file contains radio parameters and transport parameters. Finally, the eNodeB performs a self-test and reports the test result to the EMS.

The eNodeB can be trigged automatically by the M2000 or LMT to launch a comprehensive self-test after the software and configuration data file are downloaded. After the test is complete, the M2000 or LMT can obtain a test report.



Benefits

Except hardware installation, no other manual operation needs to be performed by field engineers for the eNodeB startup for the first time.

Description

When the eNodeB is powered on, it obtains the data needed to establish the OM link, such as the IP address, subnet mask, IP address of the EMS, and IP address of the security gateway, through the DHCP server. When the OM link is established successfully, the eNodeB downloads and activates the configuration data file and software automatically according to the instruction from the EMS. Then, the eNodeB performs a self-test to ensure that it is ready to provide services and reports the test result to the EMS.

After the software and configuration data file are downloaded, the M2000 or LMT automatically launches a comprehensive self-test procedure on the eNodeB. After the test is complete, the M2000 or LMT obtains a test report, indicating the eNodeB status.

The test report contains the following contents:

eNodeB basic information, such as type, name, MNC, MCC, and electrical serial number

Software version information

Board status information, such as information about the baseband and RF units

Transport status information ( physical layer and link layer)

Clock status

Cell status

Environment temperature and humidity

Enhancement

In eRAN2.0, the eNodeB can establish an IPSec link with the security gateway automatically during the self-configuration procedure.

In eRAN2.0, if the eNodeB is equipped with a GPS device, it can report geographical information (from the GPS device) to the EMS, and the EMS will identify the eNodeB automatically by comparing the received geographical information with the predefined geographical information.

In eRAN2.0, automatic transport setup is supported. The eNodeB has three types of transport-related interfaces: S1 interface, X2 interface, and OM channel interface. Accordingly, the eNodeB provides three automatic transport setup processes: S1 setup, X2 setup, and OM channel setup. The general network topology is shown in the following figure.



Figure 2-1 general network topology

EMBED Word.Picture.8

The eNodeB has parameters pre-configured in factory or other places before the installation, such as the MAC address, local OM IP, unique ID, and security key. All these parameters need not be set or modified manually.

The automatic transport setup procedure is as follows:

When the eNodeB is powered on, it negotiates automatically the transport layer 1/2 (PHY/MAC) parameters, such as duplex mode, with the peer device. The peer device can be a LAN switch, router, or another eNodeB.

The eNodeB receives the OM channel parameters from the DHCP server, such as the Internet IP address, Network Element Management (NEM) IP address, and SeGW IP address.

The eNodeB establishes an IPSec tunnel with the SeGW, obtains the Internal IP address, and then establishes the OM channel with the NEM.

After the software and configuration file are downloaded and installed, the eNodeB receives the necessary transport parameters of the S1 interface from the NEM, such as the eNodeB traffic IP address and MME SCTP IP.

The eNodeB starts the S1 interface self-configuration procedure and establishes the S1 link.

This feature also includes the X2 interface auto setup function of the Automatic Neighbor Relation feature. When the network is launched, the eNodeB can find out its new neighboring site, which is not configured as neighboring site. After receiving necessary transport data from the NEM, the eNodeB establishes the X2 link with this new neighboring site automatically.

Dependency

The X2 interface automatic setup function in this feature depends on the optional ANR feature.



2.47 LOFD-002005 Mobility Robust Optimization (MRO)

Availability


Summary

MRO aims to avoid ping-pong handover, handover too early, and handover too late. It mainly optimizes the typical mobility control parameters.

Benefits

This feature provides the following benefits:

Lowers call drop rate, reduces handover failure rate, and speeds up cell reselection.

Saves man power cost for typical and common mobility optimization scenarios

Description

This feature addresses too-early and too-late handover failures, together with ping-pong events.

The major MRO parameter adjustment are the CIO (Cell Individual Offset) for intra-frequency MRO, CIO and A2 measurement threshold for inter-frequency MRO, A2 and B1 measurements threshold for inter-RAT MRO. A2 and B1 measurements threshold adjustments reduce respectively UE dropping rate without A2 report, and handover failure or dropping rate without B1 report.CIO will be adjusted online for the offset, which explicitly declares the HO threshold between measurement results of signaling quality from both of the source and target cells. Hence, changing the CIO will significantly speed up or delay handover. The major MRO parameter adjustment is the CIO.

Both too early and too late handovers are captured at the source eNodeB by exploiting the fact that the source eNodeB is informed of too late handovers that have been prepared by the UE context release mechanism. Only outgoing handover failures are captured. There is no need to capture incoming handovers.

The reduction of ping-pong handovers exploits the UE History Information that is passed from the source eNodeB to the target eNodeB during the handover preparation. When the UE History Information is received, the target eNodeB identifies ping-pong if the second newest cell's GCI is equal to that of the target cell and the time spent in the source cell is less than a ping-pong time threshold. Ping-pong is corrected by decreasing the Cell Individual Offset.

Huawei eRAN2.0 supports both intra-frequency and inter-frequency/inter-RAT Mobility Robust Optimization.

Enhancement

In eRAN2.1, MRO feature is enhanced with the following administration functions:



Switch: user can enable or disable the inter-RAT MRO. Log: records the key event during the SON process and this information can be

used for query and statistic. Operator can also analyse the log information to master the feature running process and key event.

Dependency

None

2.48 LOFD-002007 PCI Collision Detection & Self-Optimization

Availability


Summary

This feature detects Physical Cell Identity (PCI) collision through ANR functionality.

Benefits

This feature detects the Physical Cell Identity (PCI) collision automatically.

Description

The physical cell identity (PCI) is an essential configuration parameter of an E-UTRAN cell. It corresponds to a unique combination of one orthogonal sequence and one pseudo-random sequence. In LTE, there are only 504 physical cell id that can be repeated for a large scale eNodeB deployment, but the key is that the two cells that share a physical cell ID cannot be geographically close or they will interfere will each other.

When a new eNodeB is brought into the field, a PCI, used to transmit data over the cell, needs to be selected for each of its supported cells, avoiding collision with respective neighboring cells that results in interference and service deterioration. The PCI assignment must meet the following conditions:

Collision-free: The PCI is unique in the coverage area of the cell. Confusion-free: A cell must not have neighboring cells with identical PCI.

Whenever the new neighboring relation is added by the eNodeB, the PCI collision detection procedure is triggered to check the possible PCI collision within the neighboring cells.

Enhancement

In eRAN2.1, PCI Collision Detection is enhanced with Self-optimization implemented in EMS to solve the detected collisions. In order to allocate the optimal candidate PCI



for the whole network, and to minimize the interference among neighboring cells, the sites engineering information (longitude, latitude, Azimuth), GCI, and neighbor list are taken into the PCI assignment. The new assigned PCI can be configured in 3 manners:

Immediate & Automatic delivery: The EMS will deliver the new PCIs to the eNodeB as soon as it is generated.

Regular & Automatic delivery: The EMS will deliver the new PCI at a cycle time basis.

Manually confirmed delivery: the EMS will generate a notice for confirmation before delivery to the eNodeB

PCI Collision Detection and Self-optmization feature is enhanced with the following administration functions:

Setting: can be divided into: Policy setting: operator can setup some policy of the feature (like

Optimization Analysis Mode). Break point: operator can setup break points to increase the control

capability on the feature. The algorithm can be stopped at the break points and operator confirmation is needed for the process continuity.

Log: records the key event during the SON process and this information can be used for query and statistical. Operator can also analyse the log information to master the feature running process and key event.

Dependency This feature should also be supported by EMS equipment (Huawei iManager

M2000 and Huawei i-Plan in the case of simulation preview).

2.49 LOFD-002010 Sleeping Cell Detection

Availability


Summary

Sleeping cell refers to one cell may have some serious problems but no obvious abnormal event or alarm had been triggered. UEs may camp in this cell but they cannot setup any service connection or access into the network. This feature is provided to detect such issues and to notify operator.

Benefits

This feature will shorten the time to detect some cell with serious fault problem but not having triggered an alarm yet



Description

The sleeping cell detection is a function that an eNodeB can automatically detect fault cell which cannot provide normal service but eNodeB does not report alarm to EMS, so operator does not know if cell is under sleeping status and cannot solve it in time.

eNodeB can detect sleeping cell itself and report alarm to EMS. EMS also can implement an algorithm to detect sleeping cell and generate an alarm. These two ways can be combined together to find sleeping cell more accurately than only by one way.

eNodeB uses the connected user measurement method to detect the sleeping cell. eNodeB will count connected user every second. If the user number keeps zero for a given period of time (this time value can be configured), eNodeB will generate an alarm to EMS. EMS will correlate this alarm with some other alarms (for example, the alarm from antenna which the cell associated, the alarm from the Tx/Rx channel, etc). This alarm is generated when the eNodeB detects that the cell has no accessing of any user for a long time.

After detecting the dormant cell, the eNodeB will deactivate and activate the cell automatically.

It is suggested that this feature will be used with EMS sleeping cell detection feature together to get more accurate result.

Enhancement

None

Dependency

None

2.50 LOFD-002011 Antenna Fault Detection

Availability


Summary

The faults on the antenna system and radio frequency (RF) channels are caused by the improper installation of projects when the projects are created, relocated, or optimized. The faults can also be caused by natural or external changes.

This feature provides the function of detecting faults on eRAN antennas and enables users to detect and locate antenna faults.



Benefits

This feature implements the detection of common antenna faults, thus improving the efficiency and accuracy of fault diagnosis.

By using this feature, RF engineers need not use equipment to measure eNodeB on site every time, thus reducing the project cost.

Description

The antenna system plays an important role in mobile communications. The performance of the entire network is affected by the following problems:

Improper type or location of the antenna system

Improperly configured parameters of the antenna system

Faulty antenna system

The antenna fault detection system can detect the following faults and raise related alarms:

− Weak receiving signal

− Drop of a single antenna or one antenna of dual-antenna

− Mismatch of radiation patterns between the main and the diversity

Enhancement

None

Dependency

None.

2.51 LOFD-002012 Cell Outage Detection and Compensation

Availability


Summary

Cell Outage Detection and Compensation provides automatic detection of cell outage, and automatic adjustment of mobility related RRM parameters to compensate outage cells. It solves and shortens the duration of cell outage that is a critical situation in the network, especially if there is only one frequency/RAT.



Benefits

This feature enables the operators to shorten the duration of the cell outage detection, and to keep subscribers’ service in outage cell with best effort.

Description

Cell outage is a critical situation, especially if there is only one frequency/RAT. It can cause service failure or great KPI degradation. In other hand, if there are alternative frequencies/RATs, it is preferred to move UEs from the outage cell to these alternative frequencies/RATs by triggering handover process to another frequency or system instead of compensating the coverage of surrounding cells.

This feature consists of three functions, which are cell outage detection, RRM compensation and Cell outage recovery.

Cell outage detection:

It consits of real time time monitoring of both pre-defined alarms and cell KPI. According to the pre-defined alarms the system will detect wether the cell is out of service or not. The KPI monitoring will help to detect abnormal outage cases that will not trigger alarms through the cell KPI degradation including sleeping cell. Note that this KPI threshold is configurable by operator.

RRM compensation:

This function will adjust the mobility related RRM parameters, so that the UEs can be moved to the surrounding cells for services continuity. And the outage cell will be added into the blacklist to prevent handover/reselection from neighbor cells. The priority for handover triggering is defined by the mobility features to keep the service continuity. MRO and MLB with surrounding cells are also disabled.

Cell outage recovery:

After cell outage detected, the system will reset eNodeB to recover the cell.

After outage recovery, the system will reverse the compensation.

Enhancement

None

DependencyRRM compensation needs the support of the optional feature LOFD-001019 PS Inter-

RAT Mobility between E-UTRAN and UTRAN, LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN, LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000



2.52 LOFD-001010 Security Mechanism

2.52.1 LOFD-00101001 Encryption: AES

Availability


Summary

The encryption function provides confidentiality protection for both signaling data and user data between the eNodeB and the UE.

Benefits

The procedure provides confidentiality protection for signaling data and user data in order to keep them from illegal interception and modifying.

Description

LTE handles the ciphering protection for the RRC signaling and user data. The encryption function includes both ciphering and deciphering and it is performed at PDCP layer. The ciphering is activated by the initial security activation procedure after receiving the UE context from the EPC. Upon connection establishment, the ciphering algorithm and key to be used are generated by the RRC, which is common for all radio bearers, for example, the configuration is used for the radio bearers carrying signaling data as well as for those carrying user data.

The ciphering algorithms can only be changed with handover. The ciphering keys change with handover or RRC connection re-establishment. An intra-cell handover procedure may be used to change the keys in RRC_CONNECTED mode.

From eRAN1.0, encryption algorithm AES is supported.

Enhancement

None

Dependency

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



2.52.2 LOFD-00101002 Encryption: SNOW 3G

Availability


Summary

The encryption function provides confidentiality protection for both signaling data and user data between the eNodeB and the UE.

Benefits

The procedure provides confidentiality protection for signaling data and user data in order to keep them from illegal interception and modifying.

Description

LTE handles the ciphering protection for the RRC signaling and user data. The encryption function includes both ciphering and deciphering and it is performed at PDCP layer. The ciphering is activated by the initial security activation procedure after receiving the UE context from the EPC. Upon connection establishment, the ciphering algorithm and key to be used are generated by the RRC, which is common for all radio bearers, for example, the configuration is used for the radio bearers carrying signaling data as well as for those carrying user data.

The ciphering algorithms can only be changed with handover. The ciphering keys change with handover or RRC connection re-establishment. An intra-cell handover procedure may be used to change the keys in RRC_CONNECTED mode.

Huawei eRAN2.0 supports SNOW3G with 128 bits keys.

Enhancement

None

Dependency

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

2.53 LOFD-003002 2G/3G and LTE Co-transmission

Availability




Summary

2G/3G and LTE co-transmission provides the operators the possibility of LTE co-transmission with legacy networks such as GSM, UMTS, or CDMA for better resources utilization and OPEX reduction.

Benefits

In a co-site scenario:

Better utilization of transmission resources is achieved.

OPEX (rental fees of the transmission resources) is reduced.

Description

The eNodeB supports co-transmission with other 2G/3G base stations.

During eNodeB site deployment, it is possible that an eNodeB shares a site with a base station of different technologies such as GSM, UMTS, or CDMA. In this case, co-transmission facilitates better utilization of transmission resources and reduces the OPEX (rental fees of the transmission resources).

The following figure shows the 2G/3G and LTE co-transmission

Figure 2-1 2G/3G and LTE co-transmission

The implementation of the co-transmission function depends on four sub functions: multiple ports, IP route, DHCP relay, and Weighted Round Robin (WRR) scheduling. They are described as follows:

Multiple ports: eNodeB supports several Ethernet and E1/T1 interfaces.

IP route: The data of the cascaded base station is switched to IP network by the IP route function in the eNodeB. IP routes can be configured by users.

DHCP relay: In general, a cascaded base station obtains the IP address by the DHCP function. With the DHCP function, the DHCP client, that is the base station, and the DHCP server are required to be located in the same broadcast domain. In the co-transmission scenario, however, the cascaded base station is not located in the same broadcast domain as the DHCP server. DHCP relay provides a means to transfer DHCP messages between different broadcast domains.



WRR scheduling: It ensures fairness between the cascaded base station and the eNodeB for the data transport. Data are scheduled on the basis of the weight computed according to the traffic bandwidth. Each base station and eNodeB has a weight and then has a chance to be scheduled.

Enhancement

None

Dependency

The base stations of other standards support IP.

The feature is based on E1/T1 and Ethernet interfaces.

2.54 LOFD-003004 Ethernet OAM

2.54.1 LOFD-00300401 Ethernet OAM(802.3ah)

Availability


Summary

Ethernet OAM (803.3ah) provides the fault isolation and troubleshooting capabilities for point-to-point Ethernet services.

Benefits

Ethernet OAM between two directly connected devices is available.

Description

Ethernet OAM is a protocol at the MAC layer in which the protocol is defined to facilitate the operation, administration, and maintenance (OAM) of Ethernet. Ethernet OAM includes 802.3ah and 802.1ag.

802.3ah supports point-to-point OAM between two directly connected devices.

802.1ag provides the end-to-end OAM function.

The basic functions supported by 802.3ah are as follows:

Discovery: OAM session setup procedure. The device sends OAM PDUs (Protocol Data Unit) periodically to know whether the peer device supports 802.3ah function properly or not.

Remote failure indication: When detecting faults such as a link fault, dying gasp, critical event, the device informs the peer device of the faults with OAM PDUs.

Link monitoring: The device supports link bit error rate (such as error frame and error signal) monitoring. When the error rate exceeds the threshold, it will report the event to the peer device with OAM PDUs.



Remote loopback: The device sends a loopback control PDU to ask the peer device to loop back. With loopback, it is easy to locate the fault and test the link quality.

Enhancement

None

Dependency The peer equipment must support IEEE802.3ah when IEEE802.3ah is used.

Ethernet interface is used

2.54.2 LOFD-00300402 Ethernet OAM(802.1ag)

Availability

This feature is available in from eRAN2.0

Summary

Ethernet OAM (803.1ag) provides the fault isolation and troubleshooting capabilities for end-to-end Ethernet services.

Benefits Ethernet OAM (IEEE802.1ag) can help the operator to detecting network fault.

Ethernet OAM (IEEE802.1ag) achieves reliability and high availability of Ethernet services, enables the service provider to provide economical and efficient advanced Ethernet services.

Description

Ethernet OAM (IEEE802.1ag) can report the status of the network at the data link layer, thus monitoring and managing the network more effectively.

It establishes end-to-end detection to perform maintenance of the Ethernet based on the services as follows:

Continuity Check: Detecting the connectivity of two Ethernet elements.

Loop Back: The link status detecting, similar as IP ping.

Link Trace: Locate the fault of link, similar as IP trace route.

Enhancement

None

Dependency The peer equipment must support IEEE802.1ag when IEEE802.1ag is used




2.55 LOFD-003007 Bidirectional Forwarding Detection

Availability


Summary

BFD is a kind of bidirectional-detecting mechanism, which can be used to detect the fault of the IP route.

Benefits BFD help the operator to detecting network fault.

BFD achieve reliability and high availability of Ethernet services, enables the service provider to provide economical and efficient advanced Ethernet services.

Description

The BFD feature is a method for IP connectivity failure detection by periodically transmitting BFD packets between two nodes. When no BFD packets are received during the detection interval, failure is declared and related recover action will be triggered, such as IP route, to avoid traffic drop. BFD can detecting the failure rapidly, so it could use for telecom service above IP network.

The one-hop and multi-hop BFD is supported by eNodeB.

The one-hop BFD is used for the gateway availability detection when router is used.

The multi-hop BFD is used for detecting the connectivity of two network elements, such as eNodeB to eNodeB, eNodeB to SGW/MME and eNodeB to transport equipment. The following figure shows the one-hop and multi-hop BFD application scenarios:

Figure 2-1 the one-hop and multi-hop BFD application scenarios



Enhancement

None

Dependency The peer equipment must support BFD when BFD is used to detect the fault of

the IP route.


2.56 LOFD-003005 OM Channel Backup

Availability


Summary

The OM channel backup solution provides reliability of OM channel with an alternative OM channel if OM main channel happen to fail.

Benefits

This feature provides reliability of OM channels.

Description

The OM channel backup function provides reliability of OM channels.

In the OM channel backup solution, there are two OM channels: master and slave. The key is that each channel has an OM IP address. Usually, only the master channel is active. When the master channel fails, the slave channel is activated.

Enhancement

None

Dependency

None

2.57 LOFD-003006 IP Route Backup

Availability




Summary

IP backup solution provides reliability of IP route with an alternative IP route if the IP main route happens to fail.

Benefits

This feature provides reliability at the IP layer.

Description

The IP route backup function provides reliability at the IP layer.

Users can configure two routes with the same destination IP address but different next-hop addresses and priorities. Usually, the route of the higher priority is active. When this route fails and the outage, for example, through network ping, the route of the lower priority will be activated.

Enhancement

None

Dependency

The peer device must also support the IP route backup function.

2.58 LOFD-003008 Ethernet Link Aggregation (802.3ad)

Availability


Summary

The Ethernet Link Aggregation binds several Ethernet links to one logical link.

Benefits Ethernet link aggregation enhances the reliability of Ethernet link between

eNodeB and transport equipment.

Ethernet provides loading balance on the link between the eNodeB and transport equipment and increases the bandwidth of the link.

Description

Ethernet link aggregation is a protocol defined in IEEE802.3ad. IEEE802.3ad defines a link aggregation control protocol (LACP). The links status of link group could be detected by LACP.



The eNodeB supports static LACP. For static LACP, the parameters of the link group are configured manually. The fault detecting uses the LACP.

The Ethernet link aggregation can be used in the following figure.

Figure 2-1 the Ethernet link aggregation

Enhancement

None

Dependency The Ethernet link aggregation should be supported by the directly connected

transport equipment.

Ethernet interfaces are used

2.59 LOFD-003009 IPSec

Availability


Summary

IPSec is used to protect, authenticate, and encrypt data flow for necessary security between two network entities at the IP layer.

Benefits

This feature provides the security mechanism, confidentiality, integrity, and authentication between participating peers at the IP layer.

Description

The following Error: Reference source not found shows the IPSec



Figure 2-1 IPSec

IP Security (IPSec) provides a framework of open standards dealing with data confidentiality, integrity, and authentication between participating hosts. IPSec provides these security services at the IP layer. It uses IKEV1 & IKEV2 (Internet Key Exchange) to handle negotiation of protocols and algorithms based on the local policy and to generate the encryption and authentication keys used by IPSec.

IPSec can be used to protect one or more data flows between two eNodeBs, between eNodeB and SGW/MME, or between security gateway and eNodeB.

The key characteristics of IPSec are as follows:

Two encapsulation modes: transport mode and channel mode

Two security protocols: Authentication Header (AH) and Encapsulation Security Payload (ESP)

Main encryption methods: NULL, Data Encryption Standard (DES), Triple Data Encryption Standard (3DES), and Advanced Encryption Standard (AES)

Main integrity protection methods: HMAC_SHA-1 and HMAC_MD5, where HMAC stands for Hash Message Authentication Code, SHA stands for Secure Hash Algorithm, and MD5 stands for Message Digest 5

Enhancement

In eRAN2.0, PKI (Public Key infrastructure) could be used to provide authentication for IPSEC. This needs the support of feature LOFD-003010 Public Key Infrastructure (PKI).

Dependency

Security gateway is needed. And it should support IPSec.

This feature depends on LOFD-003010 Public Key Infrastructure (PKI).


http://en.wikipedia.org/wiki/Internet_key_exchange


2.60 LOFD-003010 Public Key Infrastructure (PKI)

Availability


Summary

eNodeB supports PKI (Public Key infrastructure). It is a framework to support certificate authentication which is applied to IPSec Tunnel between eNodeB and security gateway, and SSL channel between eNodeB and OMC.

Benefits

This feature provides digital certificate authentication between two network devices, improving security in network domain.

Description

eNodeB supports PKI (Public Key infrastructure), which is a framework to manage digital certificate. Digital certificate is used to provide authentication between two network elements. Such as it is applied to IPSec Tunnel between eNodeB and security gateway, and SSL channel between eNodeB and OMC.

The digital certification management includes certificate create, store, distribute, revoke, CRL (Certificate Revocation List) distribution and so on.

In general, a PKI system includes CA(Certificate Authority), CR(Certificate Repository) ,CRL Server and users which need authentication. eNodeB and security gateway are users of PKI system. eNodeB interacts with CA, CR and CRL Server with assistance of M2000.

eNodeB supports pre-reserved certificate in factory and the certificate format is complied with X.509 V3. After base station is running, it supports certificate replacing.

The following figure shows the scenario of eRAN certificate application.



Figure 2-1 eRAN certificate application scenario

Enhancement

In eRAN2.0, eNodeB can download a CRL file from a LDAP server. And eNodeB can update digital certificates automatically through M2000 proxy.

In eRAN2.1, this feature is enhanced to support automatic certificate distribution using CMPv2. With the introduction of CMPv2 between CA and eNodeB, the procedure of certificate enrollment and update can be automated. In case of huge amount of base station deployed over carrier's network, base station certificate issuing and updating will get more efficiency when CMPv2 is introduced to establish direct tunnel from eNB to CA.

The Certificate Management Protocol (CMP) is an Internet protocol used for X.509 digital certificate creation and management in a Public Key Infrastructure (PKI).

An EE can utilize CMP to obtain certificates from the CA. This can be done through an CMP "initial registration/certification", a "key pair update" or a "certificate update" message sequence. By means of a CMP revocation request message it can also get one of its own certificates revoked. Using a CMP "cross-certification request" message a CA can get a certificate signed by another CA.

Means of transportation for conveying CMP messages:

Encapsulated in a HTTP/HTTPs message.

Dependency

The peer device needs to support the PKI functionality.



2.61 LOFD-003015 Access Control based on 802.1x

Availability


Summary

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

Benefits

This feature provides digital certificate authentication between eNodeB and LAN-Switch, improving security in network domain.

Description

802.1x (Port-Based Network Access Control) uses the physical access characteristics of IEEE 802 LAN infrastructures to provide a means of authenticating and authorizing devices attached to a LAN port that has point-to-point connection characteristics, and of preventing access to that port in cases the authentication and authorization process fails.

The authentication and authorization of 802.1x uses framework of EAP (Extensible Authentication Protocol), and refer to eNodeB, LAN-Switch, and AAA-Server (RADIUS-Server).

Figure 2-1 eRAN 802.1x application scenario

Before the authentication and authorization process succeeds, only EAPoL (Extensible Authentication Protocol over LAN) packet can across the LAN-Switch, and all the other packets will be dropped by LAN-Switch.

Enhancement

None

Dependency

The peer device needs to support the 802.1x functionality.



This feature depends on LOFD-003010 Public Key Infrastructure (PKI).

2.62 LOFD-003014 Integrated Firewall

2.62.1 LOFD-00301401 ACL

AvailabilityThis feature is available from eRAN2.0.

SummaryAccess Control List is comprised of a series rules, the eNodeB provides packet filtering based on Access Control List.

Benefits The eNodeB provides packets filtering according to Access Control List to

prevent some attacks.

The eNodeB identifies specific kinds of packets, which need to be encrypted and authenticated by IPSec according to Access Control List.

Description

Access Control List (ACL) is comprised of a series rules. The operating in the system is according to the rules of ACL.

ACL is supported by eNodeB. With ACL rules, the eNodeB provides packets filtering according the packet attributes, such as, source IP addresses, destination IP addresses, source port numbers and destination port numbers of the packets. The ACL rules can also be based on the Type of service (TOS), DSCP and address wildcard.

When IPSec is applied to guarantee security of the data flows, operators can select data flows that need to encrypted and authenticated by IPSec with Access Control List.

Enhancement

None

Dependency

None



2.63 LOFD-003011 Enhanced Transport QoS Management

2.63.1 LOFD-00301101 Transport Overbooking

Availability


Summary

The transmission overbooking allows admission of more users with the guarantee of certain quality with the enhanced admission control mechanism (TAC: Transport Admission Control) and QoS mechanism (traffic shaping and congestion control).

Benefits

This feature allows admission of more users with the guarantee of certain traffic quality.

Description

The transmission overbooking mechanism allows admission of more users with the guarantee of certain traffic quality.

The implementation of this function depends on the sub-functions TAC, traffic shaping, and congestion control.

TAC: It allows the bandwidth for user admission control to be larger than the bandwidth of the physical port. That is, operators can set the admission threshold to allow admission of more users.

Traffic shaping: It guarantees that the total available traffic bandwidth is not larger than the total configured bandwidth. The minimum transport bandwidth supported by eNodeB is 64kps for each logical port, which is configurable. The bandwidth granularity is 1kbps.

Congestion control: It detects congestion. If congestion occurs, two steps would be taken. First, a signal is sent to the data source to indicate the congestion. Second, some low-priority packets are discarded.

Enhancement

None

Dependency

Because the TAC of the S1 interface is managed by SAE, the transmission overbooking feature should be supported by SAE equipment.



2.63.2 LOFD-00301102 Transport Differentiated Flow Control

Availability


Summary

Transmission Differentiated Flow Control enhances the admission control mechanism (TAC: Transport Admission Control) and QoS mechanism (WRR scheduling: Weighted Round Robin scheduling) to provide users with differentiated services while guaranteeing fairness.

Benefits

This feature provides users with differentiated services while guaranteeing fairness.

Description

Transmission Differentiated Flow Control provides users with differentiated services while guaranteeing fairness.

Fairness: Each admission user should be allocated some bandwidth to avoid hungry phenomenon.

Differentiation: High-priority users take precedence over low-priority ones.

The implementation of this function depends on the sub-functions TAC and WRR scheduling.

TAC: If the GBR requirement exists, the transport bandwidth is computed on the basis of the GBR; otherwise, it is computed on the basis of the default reserved bandwidth of, for example, non-GBR services.

WRR scheduling: Services are scheduled on the basis of the weight computed according to the traffic bandwidth. Each user has a weight and then has a chance to be scheduled.

Enhancement

None

Dependency

None

2.63.3 LOFD-00301103 Transport Resource Overload Control

Availability




Summary

Transmission Resource Overload is a way to rapidly enhance the transmission stability when overloaded happen unexpectedly.

Benefits

This feature provides protection for the system when transmission resources are overloaded unexpectedly.

Description

Transmission Resource Overload Control provides protection for the system when transmission resources are overloaded unexpectedly.

There are two scenarios of the unexpected overload:

A great bandwidth change of transport bearer (the bandwidth available in the system) occurs. For example, the transmission bandwidth decreases from 20 Mb/s to 10 Mb/s because of network failure.

A great bandwidth change of service traffic (the bandwidth used in the system) occurs. For example, the traffic bandwidth increases from 5 Mb/s to 10 Mb/s rapidly.

When the above-mentioned scenarios happen, it is necessary to take some extreme actions such as releasing low-priority users to guarantee high-priority users’ QoS.

The strategy depends on QoS Class Identifier (QCI) and Allocation and Retention Priority (ARP). QCI defines the user priority. ARP defines whether user could be released during overload or not.

Enhancement

None

Dependency

None

2.64 LOFD-003012 IP Performance Monitoring

2.64.1 LOFD-00301201 IP Performance Monitoring

Availability




Summary

The IP Performance Monitoring enhances the performance management function by providing an end to end network monitoring mechanism and KPIs(key performance indicator) are acquired, such as information about traffic volume, packet loss rate, delay and jitter.

Benefits End-to-end network performance monitoring is available.

System maintainability and testability are enhanced.

System performance is improved.

Description

IP Performance Monitoring (PM) is Huawei specific function. It can provide an end-to-end network performance monitoring mechanism with period detecting packets. eNodeB periodically sends detecting packets to peer device such as SGW, and the peer device returns the response packets. eNodeB acquires the KPIs, such as traffic volume, packet loss rate, delay, and jitter from these response packets.

With these KPIs, users can know the network quality and take actions, such as network optimization and network expansion.

The IP PM feature facilitates fault identification too. If the LTE device including eNodeB, SGW have the feature, it is easy to identify whether the fault is located in the transmission network device or the LTE device. Furthermore, if every node on a network has the feature, it is easy to locate the fault quickly.

Enhancement

None

Dependency

None

2.64.2 LOFD-00301202 Transport Dynamic Flow Control

Availability


Summary

According to the network quality detected by IP PM (IP Performance Monitoring) mechanism, Transmission Dynamic Flow Control can dynamically adjust flow control parameters.



Benefits

This feature dynamically adjusts flow control parameters according to the network quality, which changes dynamically.

Description

In some scenarios, the quality of network changes frequently. In order to adopt these scenarios, it is better to dynamically adjust QoS parameters, such as bandwidth. Transmission Dynamic Flow Control provides a method to complete it according to the network quality detected by IP PM(IP Performance Monitoring). With good network quality, it automatically increases the bandwidth step by step, otherwise decreases the parameter.

IP PM provides the end-to-end network performance monitoring function to acquire information of network quality such as traffic volume, packet loss rate, delay, and jitter.

Enhancement

None

Dependency

This feature is based on the IP PM feature

2.65 LOFD-003016 Different Transport Paths based on QoS Grade

Availability


Summary

Different transport paths based on QoS grade is a transport networking solution that consists on different transport paths implementation for different QCI grades.

Benefits Different transport paths to reduce operator OPEX

Different transport-paths implementation to improve the network reliability

Description

Different transport paths based on QoS grade consist of two paths between eNodeB and S-GW. Operator can configure traffic to have two groups of different QCIs being allocated to the two different paths, high QoS path and low QoS path. The high QoS path provides lower bandwidth for less high QoS traffic, and the low QoS path



provides higher bandwidth for more low QoS traffic. Thereby, operator can reduce the network operation expenditures OPEX.

Figure: Two paths configuration between eNodeB and S-GW

Different transport paths based on QoS grade can also improve the network reliability. When failure happens to one path, the connection will be dropped out, and the new data traffic will be handed off over the second path. After the failed path recovery, the related traffic flow can be again transmitted over the originally path. The path failure detection is handleable by means of the different OAM mechanisms supported by Huawei eNodeB such as BFD, Ethernet OAM, and Ping, and so on.

EnhancementNone

Dependency

S-GW must support two paths configurations.

2.66 LOFD-003013 Enhanced Synchronization

2.66.1 LOFD-00301301 Synchronization with Ethernet (ITU-T G.8261)

Availability


Summary

Huawei eRAN2.0 can support Synchronize with Ethernet (ITU-T G.8261) Clock.

Benefits

The Synchronization with Ethernet technology is an economical and convenient solution for all-IP networks.



Description

The Synchronization with Ethernet, which adopts Ethernet link code streams to retrieve clocks, is a physical layer based clock synchronization method. A highly accurate clock is used by the Ethernet physical layer (PHY) for data transmission. The receiver extracts and retrieves the clock signals from data streams, and the high accuracy can be maintained. Figure 2-1 shows the framework of the Synchronization with Ethernet.

Figure 2-1 Basic principle of the Synchronization with Ethernet

The eNodeB does not require extra synchronization equipment or hardware to implement synchronization with Ethernet.

Enhancement

None

Dependency

All the devices on the clock relay path must support the Synchronization with Ethernet.

2.66.2 LOFD-00301302 IEEE1588 V2 Clock Synchronization

Availability


Summary

IEEE1588 defines the PTP (Precision Time Protocol) protocol, which applies to the standard Ethernet, with the precision to microseconds.



The IEEE1588 V2 clock synchronization targets precise synchronization of distributed and independent clocks in measurement and control systems. In LTE applications, high-accuracy frequency synchronization and time synchronization between clock servers and eNodeBs can be achieved.

IEEE1588V2 clock synchronization is an alternative clock solution for the GPS clock synchronization.

Benefits

Compared with the GPS clock solution, the IEEE1588V2 clock synchronization reduces the network deployment cost for the operator and is easy for management and maintenance.

Description The basic principle of the IEEE 1588.

Figure 2-1 shows the basic principle defined by the IEEE1588 protocol.

Figure 2-1 basic principle defined by the IEEE1588 protocol

The NE with the master clock sends synchronization timing packets to the NE with the slave clock. The intermediate switching device connects to the NE with the master clock as a slave clock to obtain the timing information on the transmission of the master clock. Then, the intermediate switching device function as a master clock and connects to other devices functioning as slave clocks.

The Time Stamp Unit (TSU) provides the ability of precise time synchronization, thus reducing delay and jitter caused by the intermediate switching device and accurately sending timing information. In this way, the work related to synchronization processing is shifted to be processed at the layer between the physical layer and the MAC layer.



Synchronization principle

Figure 2-2 shows the synchronization principle of the IEEE1588 protocol.

Figure 2-2 synchronization principle of the IEEE1588 protocol

The signaling procedure shown in Figure 2-14 is described as follows:

Step 1 The clock server (for example, the IPCLK1000) periodically sends a Sync message to the eNodeB.

The Sync message carries the standard time information, such as year, month, date, hour, minute, second, and nanosecond. The eNodeB records T2, the arrival time of the Sync message at the eNodeB. The time for sending or receiving the message needs to be measured and recorded at the underlying physical layer or the position close to the physical layer to improve the clock accuracy.

In the IEEE1588 standard, the optional hardware assist techniques are designed to improve the clock accuracy. If the Sync message is generated through the hardware assist techniques, the message can also carry the timestamp T1, at which the message is sent. If the delay of sending the Sync message from the clock server is uncertain, the clock server generates a Follow_UP message, which carries the timestamp T1. The Follow_UP message is optional.

Step 2 The eNodeB sends a Delay_req message to the clock server at T3.

The eNodeB records T3. The clock server receives the Delay_req message at T4 and then generates a Delay_resp message that carries the timestamp T4 to the eNodeB. The delay of sending the Delay_resp message does not affect T4. Therefore, the Delay_resp message need not be processed in real time.



Step 3 The eNodeB saves the complete information of T1, T2, T3, and T4.

Then, the delay of message propagation between the clock server and the eNodeB is calculated as follows:

Delay = [(T4 – T1) – (T3 – T2)]/2

In principle, the absolute time of the eNodeB is equal to the standard time carried in the Sync message plus the delay.

Enhancement

None

Dependency

All the devices on the clock relay path must support the IEEE1588V2 protocol.

2.66.3 LOFD-00301303 Clock over IP (Huawei Proprietary)

Availability


Summary

Clock over IP is an alternative network clock synchronization solution if the network does not support the IEEE1588 V2 Clock Synchronization. It is Huawei proprietary clock protocol.

Benefits

Huawei proprietary clock over IP protocol does not require extra requirement to be invested into the IP network. This feature has the same requirements for the network as the service transmission.

Description

The IEEE 1588V2 clock synchronization solution requires that all the devices on the clock relay path support IEEE1588V2 protocol. If the network does not support IEEE1588V2 protocol, Huawei LTE eRAN2.0 can use Huawei proprietary protocol to support clock over IP.

Figure 2-1 shows the framework of Huawei proprietary protocol. The clock servers generate time stamps and send the time stamps to eNodeBs, which act as clock clients in this case. Because there is delay and jitter in packet networks, eNodeBs use an adaptive method to get rid of the delay and retrieve the timing signals. The time stamps are set in packets at the UDP layer and will be transmitted at the physical layer after the related packet header is added, so there will be an extra expense in bandwidth.



Figure 2-1 Framework of Huawei proprietary protocol

Pay attention to the following information:

There are clock servers and clock clients. The servers can be located in the network independently, and the clients are integrated into the eNodeBs.

An adaptive algorithm is involved in the system. The clock servers send time stamps, and clock clients receive time stamps to retrieve the frequency.

One clock server serves a maximum of 512 eNodeBs.

Two or more clock servers can be used together to improve the reliability. This is optional.

The required transmission bandwidth for time stamps in unicast mode is from 5kbit/s to 100kbit/s for each clock client. In most cases, 25kbit/s is recommended.

This proprietary protocol only supports frequency synchronization. Frequency accuracy obtained in the eNodeB is 0.05ppm.

Enhancement

None

Dependency

None



2.67 LTE Multi-mode Common Transmission

2.67.1 MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)

Availability

This feature is available from SRAN5.0.

SRAN6.0(GBSS 13.0RAN 13.0eRAN 2.1)


SRAN3.0(GBSS 9.0RAN 11.1)


SRAN1.0(GBSS8.0RAN10.0)

M N(GL, UL) 　　　

I. IP-Based GBTS and eNodeB Co-Transmission

Summary

Huawei radio equipment supports the GSM/LTE base station co-transmission in IP mode on the MBTS side from SRAN5.0. The dynamic multiplexing of the GSM and LTE data on the MBTS side saves the transmission resources of the last mile between the MBTS and the router.what’s more, When GSM services are transitted to LTE services gradually, the wireless transmission network can support the smooth evolution.

Benefits

This feature allows operators to simplify the wireless transmission network and minimize the investments in transmission infrastructure. Therefore, the sharing of the GSM transmission bandwidth reduces the deployment cost or lease cost of the transport network. what’s more, When GSM services are transitted to LTE services gradually, the wireless transmission network can support the smooth evolution.

Description

Huawei radio equipment supports the GSM/LTE co-transmission in IP mode on the MBTS side. The dynamic multiplexing of the GSM and LTE data on the MBTS side saves the transmission resources of the last mile between the MBTS and the router and simplies the wireless transmission network. This feature is applicable to MBTS or GBTS、eNodeB co-sited scenarios.

The GSM and LTE data can be dynamically multiplexed onto the IP transport network. Based on different destination IP addresses, the GSM and LTE services can be routed to the corresponding BSC or MME/S-GW. The following figure shows the co-transmission principles.



pTR

AU

pTR

AU

pTR

AU

IP

GBSC

eNodeB

GBTS

MME/S-GW

Co-transmission

UDP

IP

/

PPP

IP SW

Router

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

LTEGSM

LTEGSM

pTR

AU

pTR

AU

pTR

AU

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

UDP

IP

/

PPP

IP SW

Router

pTRAU Packetlized TRAU framepT

RA

UpT

RA

UpT

RA

U

IP

GBSC

eNodeB

GBTS

MME/S-GW

Co-transmission

UDP

IP

/

PPP

IP SW

Router

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

LTEGSMLTE

GSMLTE

GSMLTE

GSM

pTR

AU

pTR

AU

pTR

AU

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

UDP

IP

/

PPP

IP SW

Router

pTRAU Packetlized TRAU frame

The GSM data and LTE data packed in the IP packets share the transmission resources on the S1 interface. LMPT can provide the multiplex interface for GSM and LTE . The multiplex interface could GE electrical or GE optical.

When the co-transmission is implemented on the S1 interface, the GSM data is switched to the LTE transmission board through the FE port on the GSM transmission board. The LTE transmission board multiplex the GSM data and LTE data and then transmits it on the shared GE transmission bandwidth on the transmission link. The following figure shows the co-transmission principles.

IP MW/PTN/IP MW/PTN/NGSDH/IP MPLSNGSDH/IP MPLS

MME/S-GW

BSC

IP over GE

2G BSC data

eNodeB integrate BTS data into IP over GE pipe

PTN/Router/LAN switch, router the traffic to MME/S-GW and BSC according to different VLAN or destination IP

IP over GE

LTE data

GSM BTS data

GTMU

LMPT

FE E1

GE/FE GE/FE


MME/S-GW

BSC

IP over GE

2G BSC data

eNodeB integrate BTS data into IP over GE pipe

PTN/Router/LAN switch, router the traffic to MME/S-GW and BSC according to different VLAN or destination IP

IP over GE

LTE data

GSM BTS data

GTMU

LMPT

FE E1

GE/FE GE/FE

This scheme implements the co-transmission in IP mode between the MBTS and the router.

Enhancement

None.

Dependency

Impacts on the MBSC hardware

None.

Impacts on the MBTS hardware

GSM and LTE base station should share the BBU to support this feature

The co-transmission on the GE port is achieved by adding the universal extension transmission processing unit (UTRP). For electrical GE interface, UTRP9 is necessary. For optical GE interface, UTRP2 is necessary.



Dependency on other features of the GBSS/RAN

GBFD-118601 Abis over IP


None.

Dependency on other Modes

This feature has to be activated with MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB) simultaneously

II. IP-Based NodeB and eNodeB Co-Transmission

Summary

Huawei radio equipment supports the UMTS /LTE co-transmission in IP mode on the MBTS side from SRAN5.0. The dynamic multiplexing of the UMTS and LTE data on the MBTS side saves the transmission resources of the last mile between the MBTS and the router and simplifies the wireless transmission network.

Benefits

This feature allows operators to minimize the investments in transmission infrastructure and simplify the wireless transmission network. In the case that the UMTS network and LTE network are deployed together, the co-transmission scheme saves the transmission cost. When UMTS services are transitted to LTE services gradually, the wireless transmission network can support the smooth evolution.

Description

Huawei radio equipment supports the UMTS /LTE co-transmission in IP mode on the MBTS side. The dynamic multiplexing of the UMTS and LTE data on the MBTS side saves the transmission resources of the last mile between the MBTS and the router. This feature is applicable to MBTS or NodeB、eNodeB co-sited scenarios.

The UMTS and LTE data can be dynamically multiplexed onto the IP transport network. Based on different destination IP addresses, the UMTS and LTE services can be routed to the corresponding RNC or MME/S-GW. The following figure shows the co-transmission principles.

IP

RNC

eNodeB

NodeB

MME/S-GW

Co-transmission

UDP

IP

/

PPP

IP SW

Router

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

LTEUMTS

LTEUMTS

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

UDP

IP

/

PPP

IP SW

Router

FP Frame Protocol

FPFPFP FPFPFP

IP

RNC

eNodeB

NodeB

MME/S-GW

Co-transmission

UDP

IP

/

PPP

IP SW

Router

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

LTEUMTS

LTEUMTS

LTEUMTS

LTEUMTS

GTP

-UG

TP-U

GTP

-U

GTP

-UG

TP-U

UDP

IP

/

PPP

IP SW

Router

FP Frame Protocol

FPFPFP FPFPFP

The UMTS data and LTE data packed in the IP packets share the transmission resources on the S1 interface. LMPT or UTRP can provide the multiplex interface for UMTS and LTE . The multiplex interface could be E1/T1, FE electrical, FE optical, GE electrical or GE optical.



When the co-transmission is implemented on the S1 interface, the UMTS data is switched to the LTE transmission board through the FE port on the UMTS transmission board. The LTE transmission board multiplex the UMTS data and LTE data, then transmits it on the shared FE/GE/E1/T1 transmission bandwidth on the transmission link. The following figure shows the co-transmission principles.


IP over GE

UMTS RNC data

eNodeB integrate NodeB data into IP over GE pipe

PTN/Router/LAN switch, router the traffic to MME/S-GW and RNC according to different VLAN or destination IP

IP over GE

LTE data

UMTS BTS data

WMPT

LMPT

FE E1/T1

GE/FE GE/FE

RNC


IP over GE

UMTS RNC data

eNodeB integrate NodeB data into IP over GE pipe

PTN/Router/LAN switch, router the traffic to MME/S-GW and RNC according to different VLAN or destination IP

IP over GE

LTE data

UMTS BTS data

WMPT

LMPT

FE E1/T1

GE/FE GE/FE

RNC

This scheme implements the co-transmission in IP mode between the MBTS and the router.

Enhancement

None.

Dependency


NA


UMTS mode and LTE mode boards must be co-located within the same BBU.

The co-transmission on the GE port is achieved by adding the universal extension transmission processing unit (UTRP). For electrical GE interface, UTRP9 is necessary. For optical GE interface, UTRP2 is necessary.


WRFD-050402 IP Transmission Introduction on Iub Interface


NA


This feature has to be activated with MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB) simultaneously



2.68 LTE Multi-mode Common Reference Clock

2.68.1 MRFD-231601 Multi-mode BS Common Reference Clock(eNodeB)

Availability

This feature is available from SRAN5.0





SRAN1.0(GBSS8.0RAN10.0)

M N(GL, UL) 　　　

I. GBTS and eNodeB Common Reference Clock

Summary

Huawei Multi-mode Base Station provides common reference clock of GSM and LTE when GSM and LTE co-BBU box from SRAN5.0. It can save the CAPEX and OPEX when GSM and LTE is deployed.

Benefits

It is a cost-effective solution to provide common reference clock when the BTS works in GSM and LTE co-BBU solution.

Description

Huawei Multi-mode Base Station provides common reference clock of GSM and LTE when GSM and LTE co-BBU box. Following cases is supported:

Common GPS reference clock

For common GPS reference clock, only one set of external equipment is needed for GSM and LTE dual mode. And one set of external equipment is saved. Also one set of feeder and antenna is needed, the installation cost and deployment cost is saved accordingly.

Common BITS reference clock

For common BITS reference clock, only one set of external equipment is needed for GSM and LTE dual mode. And one set of external equipment is saved and the cost is saved accordingly.

Common E1/T1 reference clock from Abis interface

When GSM Abis interface is based on TDM of E1/T1, and LTE S1 interface is based on IP of FE/GE, LMPT can get the reference clock from the clock synchronized from the Abis E1/T1 in GTMU. Clock server is not necessary to be configured for LTE and the cost is saved accordingly.

Common E1/T1 reference clock from Iub interface



When GSM and LTE BTS sharing the same transmission interface based on IP over E1/T1 or hybrid transmission based on IP, GTMU can get the reference clock from the clock synchronized from the S1 E1/T1 in UTRP for LTE mode. Clock server is not necessary to be configured and the cost is saved accordingly. Clock server is not necessary to be configured for GSM and the cost is saved accordingly.

Common Ethernet reference clock from S1 interface

When GSM and LTE BTS sharing the same transmission interface based on Synchronous Ethernet，LTE mode board will provide the sharing transmission interface and GSM can get the clock via BBU backplane from LMPT or UTRP.

Common IP network 1588V2 reference clock from S1 interface

When GSM and LTE BTS sharing the same transmission interface based on IP network supporting 1588V2 reference clock, only one 1588V2 clock server and client is required, LTE mode board will provide the sharing transmission interface and GSM can get the clock via BBU backplane from LMPT.

Enhancement

None

Dependency


None.


the GSM and LTE base station should share the BBU to support this feature

Common GPS/BITS reference clock

BBU have to be configurated with USCU（Universal satellite Card and Clock Unit） board


IP Clock Server have to be configurated.



GBFD-510401 BTS GPS Synchronization


LOFD-00301301 Synchronization with Ethernet(ITU-T G.8261)


GBFD-118601 Abis over IP

LOFD-00301302 IEEE1588 V2 Clock Synchroniztion




None.


This feature has to be activated with MRFD-231601 Multi-mode BS Common Reference Clock(eNodeB) simultaneously

II. NodeB and eNodeB Common Reference Clock

Summary

Huawei Multi-mode Base Station provides common reference clock of UMTS and LTE when UMTS and LTE co-BBU box from SRAN5.0. It can save the CAPEX and OPEX when UMTS and LTE is deployed.

Benefits

It is a cost-effective solution to provide common reference clock when the BTS works in UMTS and LTE co-BBU solution.

Description

Huawei Multi-mode Base Station provides common reference clock of UMTS and LTE when UMTS and LTE co-BBU box. Following cases is supported:


For common GPS reference clock, only one set of external equipment is needed for UMTS and LTE dual mode. And one set of external equipment is saved. Also one set of feeder and antenna is needed, the installation cost and deployment cost is saved accordingly.

Common BITS reference clock

For common BITS reference clock, only one set of external equipment is needed for UMTS and LTE dual mode. And one set of external equipment is saved and the cost is saved accordingly.

Common E1/T1 reference clock from Iub interface

When UMTS Iub interface is based on TDM of E1/T1, and LTE S1 interface is based on IP of GE, LMPT can get the reference clock from the clock synchronized from the Iub E1/T1 in WMPT or UTRP. Clock server is not necessary to be configured for UMTS and the cost is saved accordingly.


When UMTS and LTE BTS sharing the same transmission interface based on Synchronous Ethernet，LTE mode board will provide the sharing transmission interface and UMTS can get the clock via BBU backplane from LMPT.


When UMTS and LTE BTS sharing the same transmission interface based on IP network supporting 1588V2 reference clock, only one 1588V2 clock server and client is required, LTE mode board will provide the sharing transmission interface and UMTS can get the clock via BBU backplane from LMPT.



Enhancement

None

Dependency


NA


the UMTS and LTE base station should share the BBU to support this feature

Common GPS/BITS reference clock

BBU have to be configurated with USCU（Universal satellite Card and Clock

Unit）board


IP Clock Server has to be configurated.



MRFD-210501 BTS/NodeB Clock


LOFD-00301301 Synchronization with Ethernet(ITU-T G.8261)


WRFD-050402 IP Transmission Introduction on Iub Interface

LOFD-00301302 IEEE1588 V2 Clock Synchroniztion


NA


This feature has to be activated with MRFD-231601 Multi-mode BS Common Reference Clock(eNodeB) simultaneously



3 Acronyms and Abbreviations

3GPP Third Generation Partnership Project

ACK acknowledgment

ACL Access Control List

AES Advanced Encryption Standard

AFC Automatic Frequency Control

AH Authentication Header

AMBR Aggregate Maximum Bit Rate

AMC Adaptive Modulation and Coding

AMR Adaptive Multi-Rate

ANR Automatic Neighboring Relation

ARP Allocation/Retention Priority

ARQ Automatic Repeat Request

BCH Broadcast Channel

BCCH Broadcast Control Channel

BLER Block Error Rate

C/I Carrier-to-Interference Power Ratio

CCCH Common Control Channel

CDMA2000 Code Division Multiple Access (3G standard)

CEU Cell Edge Users



CGI Cell Group Indicator

CP Cyclic Prefix

CPICH Common Pilot Channel

CQI Channel Quality Indicator

CRC Cyclic Redundancy Check

DCCH Dedicated Control Channel

DES Data Encryption Standard

DHCP Dynamic Host Configuration Protocol

DiffServ Differentiated Services

DL-SCH Downlink Shared Channel

DRB Data Radio Bearer

DRx Discontinuous Reception

DSCP DiffServ Code Point

DTCH Dedicated Traffic Channel

ECM EPS Control Management

EDF Early Deadline First

EF Expedited Forwarding

eMBMS evolved Multimedia Broadcast Multimedia System

EMM EPS Mobility Management

EMS Element Management System

eNodeB evolved NodeB

EPC Evolved Packet Core

EPS Evolved Packet System

ESP Encapsulation Security Payload

ETWS Earthquake and Tsunami Warning System

E-UTRA Evolved –Universal Terrestrial Radio Access

FCPSS Fault, Configuration, Performance, Security and Software Managements

FDD Frequency Division Duplex

FEC Forward Error Correction



FTP File Transfer Protocol

GBR Guaranteed Bit Rate

GERAN GSM/EDGE Radio Access Network

GPS Global Positioning System

HARQ Hybrid Automatic Repeat Request

HII High Interference Indicator

HMAC Hash Message Authentication Code

HMAC_MD5 HMAC Message Digest 5

HMAC_SHA HMAC Secure Hash Algorithm

HO Handover

HRPD High Rate Packet Data

ICIC Inter-cell Interference Coordination

IKEV Internet Key Exchange Version

IMS IP Multimedia Service

IP PM IP Performance Monitoring

IPSec IP Security

IRC Interference Rejection Combining

KPI Key Performance Indicator

CME Configuration Management Express

LMT Local Maintenance Terminal

M2000 Huawei OMC

MAC Medium Admission Control

MIB Master Information Block

MCH Multicast Channel

MCCH Multicast Control Channel

MCS Modulation and Coding Scheme



MIMO Multiple Input Multiple Output

min_GBR Minimum Guaranteed Bit Rate

MME Mobility Management Entity

MML Man-Machine Language

MOS Mean Opinion Score

MRC Maximum-Ratio Combining

MTCH Multicast Traffic Channel

MU-MIMO Multiple User-MIMO

NACC Network Assisted Cell Changed

NACK Non acknowledgment

NAS Non-Access Stratum

NRT Neighboring Relation Table

OCXO Oven Controlled Crystal Oscillator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiplexing Access

OI Overload Indicator

OMC Operation and Maintenance Center

OOK On-Off-Keying

PBCH Physical Broadcast Channel

PCCH Paging Control Channel

PCFICH Physical Control Format Indicator Channel

PCH Paging Channel

PCI Physical Cell Identity

PDB Packet Delay Budget

PDCCH Physical Downlink Control Channel

PDCP Packet Data Convergence Protocol

PDH Plesiochronous Digital Hierarchy

PDSCH Physical Downlink Shared Channel

PF Proportional Fair



PHB Per-Hop Behavior

PHICH Physical Hybrid ARQ Indicator Channel

PM Performance Measurement

PLMN Public Land Mobile Network

PMCH Physical Multicast Channel

PRACH Physical Random Access Channel

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

QAM Quadrature Amplitude Modulation

QCI QoS Class Identifier

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access Channel

RAM Random Access Memory

RAT Radio Access Technology

RB Resource Block

RCU Radio Control Unit

RET Remote Electrical Tilt

RF Radio Frequency

RLC Radio Link Control

RRC Radio Resource Control

RRM Radio Resource Management

RRU Remote Radio Unit

RS Reference Signal

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

RSSI Received Signal Strength Indicator

RTT Round Trip Time

RV Redundancy Version



Rx Receive

S1 interface between EPC and E-UTRAN

SBT Smart Bias Tee

SC-FDMA Single Carrier-Frequency Division Multiple Access

SCTP Stream Control Transmission Protocol

SDH Synchronous Digital Hierarchy

SFBC Space Frequency Block Coding

SFP Small Form – factor Pluggable

SGW Serving Gateway

SIB System Information Block

SID Silence Indicator

SINR Signal to Interference plus Noise Ratio

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SSL Security Socket Layer

STBC Space Time Block Coding

STMA Smart TMA

TAC Transport Admission Control

TCP Transmission Control Protocol

TDD Time Division Duplex

TMA Tower Mounted Amplifier

TMF Traced Message Files

ToS Type of Service

TTI Transmission Time Interval

Tx Transmission

UE User Equipment

UL-SCH Uplink Shared Channel

USB Universal Serial Bus



VLAN Virtual Local Area Network

VoIP Voice over IP

WRR Weighted Round Robin

X2 interface among eNodeBs


Documents

Huawei LTE eRAN2.1 Feature Description.doc