ErAN

eRAN V100R002C00 Feature Configuration Guide

Issue Draft

Date 2010-05-20

HUAWEI TECHNOLOGIES CO., LTD.

Draft (2010–05–20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. i

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]

http://www.huawei.com/

mailto:[email protected]

eRAN eRAN Feature Configuration Guide About This Document

Draft (2010–05–20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

iii

About This Document

Purpose This document provides instructions on how to enable and disable eRAN features.

Product Version The following table lists the product versions related to this document.

Product Name Product Version

DBS3900 LTE V100R002C00

DBS3900 TDLTE V100R002C00

BTS3900 LTE V100R002C00

BTS3900A LTE V100R002C00

BTS3900L LTE V100R002C00

Intended Audience This document is intended for:

Network planners Network operators System engineers

Organization 1 Changes in the eRAN Feature Configuration Guide

This chapter provides the changes in the eRAN Feature Configuration Guide.

2 eRAN Feature Configuration

About This Document eRAN

eRAN Feature Configuration Guide

iv Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Draft (2010–05–20)

This chapter describes the procedures for enabling and disabling the features that are configurable.

Conventions

Symbol Conventions The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk that, if not avoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or save time.

Provides additional information to emphasize or supplement important points of the main text.

General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

eRAN eRAN Feature Configuration Guide About This Document


v


{ x | y | ... } Alternative items are grouped in braces and separated by vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

GUI Conventions


Boldface Buttons, menus, parameters, tabs, windows, and dialog titles are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

Keyboard Operation

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Mouse Operation

Action Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certain position.

eRAN eRAN Feature Configuration Guide Contents


vii

Contents

About This Document................................................................................................................... iii

1 Changes in the eRAN Feature Configuration Guide..........................................................1-1

2 eRAN Feature Configuration...................................................................................................2-1 2.1 Configuring Normal CP ................................................................................................................................2-8

2.1.1 Enabling Normal CP ............................................................................................................................2-8 2.2 Configuring Integrity Protection ...................................................................................................................2-9

2.2.1 Enabling Integrity Protection ...............................................................................................................2-9 2.2.2 Disabling Integrity Protection............................................................................................................2-10

2.3 Configuring Admission Control ..................................................................................................................2-10 2.3.1 Enabling Admission Control ..............................................................................................................2-10 2.3.2 Disabling Admission Control.............................................................................................................2-12

2.4 Configuring Congestion Control .................................................................................................................2-13 2.4.1 Enabling Congestion Control.............................................................................................................2-13 2.4.2 Disabling Congestion Control............................................................................................................2-14

2.5 Configuring DRX........................................................................................................................................2-14 2.5.1 Enabling DRX....................................................................................................................................2-14 2.5.2 Disabling DRX...................................................................................................................................2-15

2.6 Configuring Coverage Based Intra-Frequency Handover ...........................................................................2-16 2.6.1 Enabling Coverage Based Intra-Frequency Handover .......................................................................2-16 2.6.2 Disabling Coverage Based Intra-Frequency Handover......................................................................2-16

2.7 Configuring Coverage Based Inter-Frequency Handover ...........................................................................2-17 2.7.1 Enabling Coverage Based Inter-Frequency Handover .......................................................................2-17 2.7.2 Disabling Coverage Based Inter-Frequency Handover......................................................................2-18

2.8 Configuring Downlink Static Inter-Cell Interference Coordination............................................................2-18 2.8.1 Enabling Downlink Static Inter-Cell Interference Coordination........................................................2-18 2.8.2 Disabling Downlink Static Inter-Cell Interference Coordination.......................................................2-19

2.9 Configuring Uplink Static Inter-Cell Interference Coordination.................................................................2-20 2.9.1 Enabling Uplink Static Inter-Cell Interference Coordination.............................................................2-20 2.9.2 Disabling Uplink Static Inter-Cell Interference Coordination ...........................................................2-21

2.10 Configuring SCTP Multi-Homing.............................................................................................................2-21 2.10.1 Enabling SCTP Multi-Homing.........................................................................................................2-21 2.10.2 Disabling SCTP Multi-Homing .......................................................................................................2-22

Contents eRAN


viii Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Draft (2010–05–20)

2.11 Configuring VLAN Support (IEEE 802.1p/q)...........................................................................................2-22 2.11.1 Enabling VLAN Support (IEEE 802.1p/q) ......................................................................................2-22 2.11.2 Disabling VLAN Support (IEEE 802.1p/q) .....................................................................................2-24

2.12 Configuring IP Header Compression ........................................................................................................2-24 2.12.1 Enabling IP Header Compression ....................................................................................................2-24 2.12.2 Disabling IP Header Compression ...................................................................................................2-25

2.13 Configuring PPP MUX .............................................................................................................................2-25 2.13.1 Enabling PPP MUX .........................................................................................................................2-25 2.13.2 Disabling PPP MUX ........................................................................................................................2-26

2.14 Configuring ML-PPP/MC-PPP .................................................................................................................2-27 2.14.1 Enabling ML-PPP/MC-PPP.............................................................................................................2-27 2.14.2 Disabling ML-PPP/MC-PPP............................................................................................................2-28

2.15 Configuring Clock Source Switching Manually or Automatically............................................................2-28 2.15.1 Enabling Clock Source Switching Manually or Automatically .......................................................2-28 2.15.2 Disabling Clock Source Switching Manually or Automatically ......................................................2-29

2.16 Configuring Free-Running Mode..............................................................................................................2-30 2.16.1 Enabling Free-Running Mode..........................................................................................................2-30 2.16.2 Disabling Free-Running Mode.........................................................................................................2-30

2.17 Configuring Synchronization with GPS....................................................................................................2-31 2.17.1 Enabling Synchronization with GPS................................................................................................2-31 2.17.2 Disabling Synchronization with GPS...............................................................................................2-32

2.18 Configuring Synchronization with E1/T1 .................................................................................................2-32 2.18.1 Enabling Synchronization with E1/T1 .............................................................................................2-32 2.18.2 Disabling Synchronization with E1/T1............................................................................................2-33

2.19 Configuring UL 2x2 MU-MIMO ..............................................................................................................2-33 2.19.1 Enabling UL 2x2 MU-MIMO..........................................................................................................2-33 2.19.2 Disabling UL 2x2 MU-MIMO.........................................................................................................2-35

2.20 Configuring Uplink 64QAM.....................................................................................................................2-36 2.20.1 Enabling Uplink 64QAM.................................................................................................................2-36 2.20.2 Disabling Uplink 64QAM................................................................................................................2-36

2.21 Configuring Encryption: AES ...................................................................................................................2-37 2.21.1 Enabling Encryption: AES...............................................................................................................2-37 2.21.2 Disabling Encryption: AES..............................................................................................................2-38

2.22 Configuring Encryption: SNOW 3G.........................................................................................................2-38 2.22.1 Enabling Encryption: SNOW 3G.....................................................................................................2-38 2.22.2 Disabling Encryption: SNOW 3G....................................................................................................2-39

2.23 Configuring UL Interference Rejection Combining..................................................................................2-39 2.23.1 Enabling UL Interference Rejection Combining..............................................................................2-39

2.24 Configuring Downlink Dynamic Inter-Cell Interference Coordination ....................................................2-40 2.24.1 Enabling Downlink Dynamic Inter-Cell Interference Coordination ................................................2-40 2.24.2 Disabling Downlink Dynamic Inter-Cell Interference Coordination ...............................................2-41

2.25 Configuring Uplink Dynamic Inter-Cell Interference Coordination .........................................................2-42



ix

2.25.1 Enabling Uplink Dynamic Inter-Cell Interference Coordination .....................................................2-42 2.25.2 Disabling Uplink Dynamic Inter-Cell Interference Coordination....................................................2-43

2.26 Configuring CQI Adjustment ....................................................................................................................2-43 2.26.1 Enabling CQI Adjustment................................................................................................................2-43 2.26.2 Disabling CQI Adjustment...............................................................................................................2-44

2.27 Configuring TCP Proxy Enhancement (TPE) ...........................................................................................2-44 2.27.1 Enabling TCP Proxy Enhancement (TPE) .......................................................................................2-44 2.27.2 Disabling TCP Proxy Enhancement (TPE) ......................................................................................2-45

2.28 Configuring Active Queue Management(AQM).......................................................................................2-46 2.28.1 Enabling Active Queue Management(AQM)...................................................................................2-46 2.28.2 Disabling Active Queue Management(AQM)..................................................................................2-46

2.29 Configuring Radio/Transport Resource Rre-emption................................................................................2-47 2.29.1 Enabling Radio Resource Pre-emption ............................................................................................2-47 2.29.2 Disabling Radio Resource Pre-emption ...........................................................................................2-48 2.29.3 Enabling Transport Resource Rre-emption ......................................................................................2-48 2.29.4 Disabling Transport Resource Rre-emption.....................................................................................2-49

2.30 Configuring RObust Header Compression (ROHC) .................................................................................2-50 2.30.1 Enabling ROHC...............................................................................................................................2-50 2.30.2 Disabling ROHC..............................................................................................................................2-51

2.31 Configuring S1-Flex..................................................................................................................................2-52 2.31.1 Enabling S1-Flex .............................................................................................................................2-52 2.31.2 Disabling S1-Flex ............................................................................................................................2-53

2.32 Configuring PS Inter-RAT Mobility Between E-UTRAN and UTRAN ...................................................2-54 2.32.1 Enabling PS Inter-RAT Mobility Between E-UTRAN and UTRAN...............................................2-54 2.32.2 Disabling PS Inter-RAT Mobility Between E-UTRAN and UTRAN..............................................2-55

2.33 Configuring PS Inter-RAT Mobility Between E-UTRAN and GERAN ...................................................2-55 2.33.1 Enabling PS Inter-RAT Mobility Between E-UTRAN and GERAN...............................................2-55 2.33.2 Disabling PS Inter-RAT Mobility Between E-UTRAN and GERAN..............................................2-56

2.34 Configuring PS Inter-RAT Mobility Between E-UTRAN and CDMA2000.............................................2-57 2.34.1 Enabling PS Inter-RAT Mobility Between E-UTRAN and CDMA2000.........................................2-57 2.34.2 Disabling PS Inter-RAT Mobility Between E-UTRAN and CDMA2000........................................2-58

2.35 Configuring SRVCC to UTRAN...............................................................................................................2-58 2.35.1 Enabling SRVCC to UTRAN...........................................................................................................2-58 2.35.2 Disabling SRVCC to UTRAN .........................................................................................................2-59

2.36 Configuring SRVCC to GERAN...............................................................................................................2-59 2.36.1 Enabling SRVCC to GERAN...........................................................................................................2-59 2.36.2 Disabling SRVCC to GERAN .........................................................................................................2-60

2.37 Configuring Extended CP .........................................................................................................................2-61 2.37.1 Enabling Extended CP .....................................................................................................................2-61 2.37.2 Disabling Extended CP ....................................................................................................................2-62

2.38 Configuring Intra-LTE Load Balancing ....................................................................................................2-62 2.38.1 Enabling Intra-LTE Load Balancing ................................................................................................2-62

Contents eRAN


x Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Draft (2010–05–20)

2.38.2 Disabling Intra-LTE Load Balancing ...............................................................................................2-63 2.39 Configuring Inter-RAT Load Sharing to UTRAN.....................................................................................2-64

2.39.1 Enabling Inter-RAT Load Sharing to UTRAN.................................................................................2-64 2.39.2 Disabling Inter-RAT Load Sharing to UTRAN................................................................................2-64

2.40 Configuring Inter-RAT Load Sharing to GERAN.....................................................................................2-65 2.40.1 Enabling Inter-RAT Load Sharing to GERAN.................................................................................2-65 2.40.2 Disabling Inter-RAT Load Sharing to GERAN................................................................................2-66

2.41 Configuring Service Based Inter-RAT Handover to UTRAN ...................................................................2-66 2.41.1 Enabling Service Based Inter-RAT Handover to UTRAN...............................................................2-66 2.41.2 Disabling Service Based Inter-RAT Handover to UTRAN..............................................................2-67

2.42 Configuring Service Based Inter-RAT Handover to GERAN ...................................................................2-68 2.42.1 Enabling Service Based Inter-RAT Handover to GERAN...............................................................2-68 2.42.2 Disabling Service Based Inter-RAT Handover to GERAN..............................................................2-69

2.43 Configuring CS Fall Back to UTRAN ......................................................................................................2-69 2.43.1 Enabling CS Fall Back to UTRAN ..................................................................................................2-69 2.43.2 Disabling CS Fall Back to UTRAN.................................................................................................2-70

2.44 Configuring CS Fall Back to GERAN ......................................................................................................2-71 2.44.1 Enabling CS Fall Back to GERAN ..................................................................................................2-71 2.44.2 Disabling CS Fall Back to GERAN.................................................................................................2-72

2.45 Configuring CS Fall Back to CDMA2000 1xRTT....................................................................................2-72 2.45.1 Enabling CS Fall Back to CDMA2000 1x RTT...............................................................................2-72 2.45.2 Disabling CS Fall Back to 1x RTT ..................................................................................................2-73

2.46 Configuring RAN Sharing with Common Carrier ....................................................................................2-74 2.46.1 Enabling RAN Sharing with Common Carrier ................................................................................2-74 2.46.2 Disabling RAN Sharing with Common Carrier ...............................................................................2-75

2.47 Configuring RAN Sharing with Dedicated Carrier ...................................................................................2-75 2.47.1 Enabling RAN Sharing with Dedicated Carrier ...............................................................................2-75 2.47.2 Disabling RAN Sharing with Dedicated Carrier..............................................................................2-76

2.48 Configuring RRU Channel Cross Connection Under MIMO ...................................................................2-77 2.48.1 Enabling RRU Channel Cross Connection Under MIMO ...............................................................2-77 2.48.2 Disabling RRU Channel Cross Connection Under MIMO ..............................................................2-79

2.49 Configuring Adaptive Power Consumption ..............................................................................................2-80 2.49.1 Enabling Adaptive Power Consumption ..........................................................................................2-80 2.49.2 Disabling Adaptive Power Consumption .........................................................................................2-81

2.50 Configuring RF Channel Intelligent Shutdown.........................................................................................2-82 2.50.1 Enabling RF Channel Intelligent Shutdown.....................................................................................2-82 2.50.2 Disabling RF Channel Intelligent Shutdown ...................................................................................2-82

2.51 Configuring Low Power Consumption Mode ...........................................................................................2-83 2.51.1 Enabling Low Power Consumption Mode.......................................................................................2-83 2.51.2 Disabling Low Power Consumption Mode......................................................................................2-84

2.52 Configuring Intelligent Power-Off of Carriers in the Same Coverage ......................................................2-84 2.52.1 Enabling Intelligent Power-Off of Carriers in the Same Coverage..................................................2-84



xi

2.52.2 Disabling Intelligent Power-Off of Carriers in the Same Coverage.................................................2-85 2.53 Configuring ANR......................................................................................................................................2-86

2.53.1 Enabling ANR..................................................................................................................................2-86 2.53.2 Disabling ANR.................................................................................................................................2-87

2.54 Configuring Inter-RAT ANR.....................................................................................................................2-87 2.54.1 Enabling Inter-RAT ANR.................................................................................................................2-87 2.54.2 Disabling Inter-RAT ANR................................................................................................................2-88

2.55 Configuring PCI Collision Detection ........................................................................................................2-88 2.55.1 Enabling PCI Collision Detection....................................................................................................2-88 2.55.2 Disabling PCI Collision Detection...................................................................................................2-89

2.56 Configuring Ethernet OAM (IEEE 802.3ah).............................................................................................2-90 2.56.1 Enabling Ethernet OAM (IEEE 802.3ah) ........................................................................................2-90 2.56.2 Disabling Ethernet OAM (IEEE 802.3ah) .......................................................................................2-91

2.57 Configuring Ethernet OAM (IEEE 802.1ag).............................................................................................2-91 2.57.1 Enabling Ethernet OAM (IEEE 802.1ag) ........................................................................................2-91 2.57.2 Disabling Ethernet OAM (IEEE 802.1ag) .......................................................................................2-93

2.58 Configuring Bidirectional Forwarding Detection......................................................................................2-94 2.58.1 Enabling Bidirectional Forwarding Detection .................................................................................2-94 2.58.2 Disabling Bidirectional Forwarding Detection ................................................................................2-94

2.59 Configuring OM Channel Backup ............................................................................................................2-95 2.59.1 Enabling OM Channel Backup ........................................................................................................2-95 2.59.2 Disabling OM Channel Backup .......................................................................................................2-96

2.60 Configuring Ethernet Link Aggregation(IEEE 802.3ad)...........................................................................2-96 2.60.1 Enabling Ethernet Link Aggregation(IEEE 802.3ad).......................................................................2-96 2.60.2 Disabling Ethernet Link Aggregation(IEEE 802.3ad) .....................................................................2-97

2.61 Configuring IPSec.....................................................................................................................................2-98 2.61.1 Enabling IPSec.................................................................................................................................2-98 2.61.2 Disabling IPSec................................................................................................................................2-99

2.62 Configuring PKI........................................................................................................................................2-99 2.62.1 Enabling PKI....................................................................................................................................2-99 2.62.2 Disabling PKI.................................................................................................................................2-101

2.63 Configuring Access Control Based on 802.1x ........................................................................................2-101 2.63.1 Enabling Access Control Based on 802.1x ....................................................................................2-101 2.63.2 Disabling Access Control Based on 802.1x ...................................................................................2-102

2.64 Configuring Access Control List(ACL) ..................................................................................................2-102 2.64.1 Enabling Access Control List(ACL) ..............................................................................................2-102 2.64.2 Disabling Access Control List(ACL) .............................................................................................2-103

2.65 Configuring Transport Overbooking .......................................................................................................2-104 2.65.1 Enabling Transport Overbooking...................................................................................................2-104 2.65.2 Disabling Transport Overbooking..................................................................................................2-105

2.66 Configuring Transport Differentiated Flow Control................................................................................2-106 2.66.1 Enabling Transport Differentiated Flow Control ...........................................................................2-106

Contents eRAN


xii Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Draft (2010–05–20)

2.66.2 Disabling Transport Differentiated Flow Control ..........................................................................2-107 2.67 Configuring Resource Overload Flow Control .......................................................................................2-108

2.67.1 Enabling Resource Overload Flow Control ...................................................................................2-108 2.67.2 Disabling Transport Resource Overload Flow Control ..................................................................2-109

2.68 Configuring IP Performance Monitoring ................................................................................................2-109 2.68.1 Enabling IP Performance Monitoring ............................................................................................2-109 2.68.2 Disabling IP Performance Monitoring ........................................................................................... 2-111

2.69 Configuring Transport Dynamic Flow Control ....................................................................................... 2-111 2.69.1 Enabling Transport Dynamic Flow Control ................................................................................... 2-111 2.69.2 Disabling Transport Dynamic Flow Control ..................................................................................2-112

2.70 Configuring Synchronization with Ethernet(ITU-T G.8261) ..................................................................2-113 2.70.1 Enabling Synchronization with Ethernet(ITU-T G.8261) ..............................................................2-113 2.70.2 Disabling Synchronization with Ethernet(ITU-T G.8261) .............................................................2-114

2.71 Configuring IEEE1588 V2 Clock Synchronization ................................................................................2-114 2.71.1 Enabling IEEE1588 V2 Clock Synchronization ............................................................................2-114 2.71.2 Disabling IEEE1588 V2 Clock Synchronization ...........................................................................2-115

2.72 Configuring Clock over IP (Huawei Proprietary) ...................................................................................2-116 2.72.1 Enabling Clock over IP (Huawei Proprietary) ...............................................................................2-116 2.72.2 Disabling Clock over IP (Huawei Proprietary) ..............................................................................2-117

eRAN eRAN Feature Configuration Guide Figures


xiii

Figures

Figure 2-1 Monitoring MU-MIMO ..................................................................................................................2-34

Figure 2-2 MU-MIMO monitoring result.........................................................................................................2-35

Figure 2-3 RF cable connections for RRU channel cross-connection under MIMO........................................2-78

Figure 2-4 RF cable connections in ordinary situations ...................................................................................2-79

eRAN eRAN Feature Configuration Guide Tables


xv

Tables

Table 2-1 Overview of eRAN basic feature configuration .................................................................................2-1

Table 2-2 Overview of eRAN optional feature configuration ............................................................................2-4

eRAN eRAN Feature Configuration Guide 1 Changes in the eRAN Feature Configuration Guide


1-1

1 Changes in the eRAN Feature Configuration Guide

This chapter provides the changes in the eRAN Feature Configuration Guide.

Draft (2010-05-20) Compared with issue 02 (2010-03-31) of eRAN1.1, draft (2010-05-20) incorporates the changes listed in the following table.

Type of Change

Feature Name Feature ID

Normal CP LBFD-00100401

Extended CP LOFD-001031

TCP Proxy Enhancer (TPE) LOFD-001026

Active Queue Management(AQM) LOFD-001027

Radio/transport Resource Pre-emption LOFD-00102901

RRU Channel Cross Connection Under MIMO

LOFD-001038

Intra-LTE Load Balancing LOFD-001032

Inter-RAT Load Sharing to UTRAN LOFD-001044

Inter-RAT Load Sharing to GERAN LOFD-001045

Service based inter-RAT handover to UTRAN

LOFD-001043

Service based inter-RAT handover to GERAN

LOFD-001046

CS Fallback to UTRAN LOFD-001033

CS Fallback to GERAN LOFD-001034

New contents

CS Fallback to CDMA2000 1xRTT LOFD-001035

1 Changes in the eRAN Feature Configuration Guide eNodeB


1-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Draft (2010–05–20)

Type of Change

Feature Name Feature ID

RAN Sharing with Common Carrier LOFD-001036

RAN Sharing with Dedicated Carrier LOFD-001037

RF Channel Intelligent Shutdown LOFD-001039

Low Power Consumption Mode LOFD-001040

Intelligent Power-Off of Carriers in the Same Coverage

LOFD-001042

Access Control based on 802.1x LOFD-003015

eRAN eRAN Feature Configuration Guide 2 eRAN Feature Configuration


2-1

2 eRAN Feature Configuration

eRAN features are classified into basic and optional features, as listed in Table 2-1 and Table 2-2 respectively.

If a feature is license-controlled, you must activate the associated license before the feature can be enabled. Otherwise, you do not need to activate the license for that feature.

If a feature is configurable, you need to follow the associated procedure described in this chapter to enable or disable the feature. Otherwise, the feature is enabled by default (after the associated license is activated if the feature is license-controlled).

Table 2-1 Overview of eRAN basic feature configuration

Feature Category Feature Name Feature ID License-Controlled? Configurable?

3GPP R8 Specifications LBFD-001001 No No

FDD mode LBFD-001002 No No

Scalable Bandwidth LBFD-001003 No No

CP length LBFD-001004 No No

Normal CP LBFD-00100401 No Yes

Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM

LBFD-001005 No No

Standards Compliance

AMC LBFD-001006 No No

Logical Channel Management

LBFD-002001 No No

Transport Channel Management

LBFD-002002 No No

Physical Channel Management

LBFD-002003 No No

RAN Architecture & Features

Integrity Protection LBFD-002004 No Yes

2 eRAN Feature Configuration eRAN



Draft (2010–05–20)

DL Asynchronous HARQ

LBFD-002005 No No

UL Synchronous HARQ LBFD-002006 No No

RRC Connection Management

LBFD-002007 No No

Radio Bearer Management

LBFD-002008 No No

Broadcast of system information

LBFD-002009 No No

Random Access Procedure

LBFD-002010 No No

Paging LBFD-002011 No No

Cell Access Radius up to 15km

LBFD-002012 No No

Admission Control LBFD-002023 No Yes

Congestion Control LBFD-002024 No Yes

Basic Scheduling LBFD-002025 No No

Uplink Power Control LBFD-002026 No No

Dynamic Downlink Power Allocation

LBFD-002016 No No

DRX LBFD-002017 No Yes

Mobility Management LBFD-002018 No No

Coverage Based Intra-frequency Handover

LBFD-00201801 No Yes

Coverage Based Inter-frequency Handover


Cell Selection and Re-selection

LBFD-00201803 No No

Static Inter-Cell Interference Coordination

LBFD-002022 No No

Downlink Static Inter-Cell Interference Coordination


Uplink Static Inter-Cell Interference Coordination


Antenna Configuration LBFD-002020 No No



2-3

UL 2-Antenna Receive Diversity

LBFD-00202001 No No

Reliability LBFD-002021 No No

Main Processing and Transport Unit Cold Backup

LBFD-00202101 No No

Cell Re-build Between Baseband Processing Units

LBFD-00202102 No No

SCTP Multi-homing LBFD-00202103 No Yes

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

LBFD-00202104 No No

Support of UE Category 1

LBFD-002027 No No

Transport Networking LBFD-003001 No No

Star Topology LBFD-00300101 No No

Chain Topology LBFD-00300102 No No

Transport Networking

Tree Topology LBFD-00300103 No No

Basic Qos Management LBFD-003002 No No

DiffServ QoS Support LBFD-00300201 No No

VLAN Support (IEEE 802.1p/q)

LBFD-003003 No Yes

Compression & Multiplexing over E1/T1

LBFD-003004 No No

IP Header Compression LBFD-00300401 No Yes

PPP MUX LBFD-00300402 No Yes

Transport QoS

ML-PPP/MC-PPP LBFD-00300403 No Yes

Synchronization LBFD-003005 No No

Clock Source Switching Manually or Automatically


Free-running Mode LBFD-00300502 No Yes

Synchronization with GPS


Transport Synchronization

Synchronization with 1PPS

LBFD-00300505 No No




Draft (2010–05–20)

Synchronization with E1/T1


Local Maintenance of the LMT

LBFD-004001 No No

Centralized M2000 Management

LBFD-004002 No No

Security Socket Layer LBFD-004003 No No

Software Version Upgrade Management

LBFD-004004 No No

Hot Patch Management LBFD-004005 No No

Fault Management LBFD-004006 No No

Configuration Management

LBFD-004007 No No

Performance Management

LBFD-004008 No No

Real-time Monitoring of System Running Information

LBFD-004009 No No

Security Management LBFD-004010 No No

Optimized eNodeB Commissioning Solution

LBFD-004011 No No

Environment Monitoring LBFD-004012 No No

Operation and Maintenance

Inventory Management LBFD-004013 No No

Table 2-2 Overview of eRAN optional feature configuration


DL 2x2 MIMO LOFD-001001 Yes No

UL 2x2 MU-MIMO LOFD-001002 Yes Yes

DL 4x2 MIMO LOFD-001003 Yes No

UL 4-Antenna Receive Diversity

LOFD-001005 Yes No

UL 64QAM LOFD-001006 Yes Yes

UL Interference Rejection Combining

LOFD-001012 Yes Yes

Coverage and Capacity

Dynamic Inter-Cell Interference Coordination

LOFD-001014 Yes No



2-5


Downlink Dynamic Inter-Cell Interference Coordination

LOFD-00101401 Yes Yes

Uplink Dynamic Inter-Cell Interference Coordination


High Speed Mobility LOFD-001007 Yes No

Ultra High Speed Mobility

LOFD-001008 Yes No

Extended Cell Access Radius

LOFD-001009 Yes No

Support of UE Catagory2/3/4

LOFD-001030 Yes No

Extended CP LOFD-001031 Yes Yes

Enhanced Scheduling LOFD-001015 Yes No

CQI Adjustment LOFD-00101501 Yes Yes

Dynamic Scheduling LOFD-00101502 Yes No

VoIP Semi-persistent Scheduling

LOFD-001016 Yes No

RObust Header Compression (ROHC)

LOFD-001017 Yes Yes

TCP Proxy Enhancer (TPE)

LOFD-001026 Yes Yes

Active Queue Management(AQM)

LOFD-001027 Yes Yes

Enhanced Admission Control

LOFD-001029 Yes No

Radio/transport Resource Pre-emption


RRU Channel Cross Connection Under MIMO

LOFD-001038 Yes Yes

Service and QoS

S1-flex LOFD-001018 Yes Yes

PS Inter-RAT Mobility between E-UTRAN and UTRAN

LOFD-001019 Yes Yes Convergence and Evolution

PS Inter-RAT Mobility between E-UTRAN and GERAN

LOFD-001020 Yes Yes




Draft (2010–05–20)


PS Inter-RAT Mobility between E-UTRAN and CDMA2000

LOFD-001021 Yes Yes

SRVCC to UTRAN LOFD-001022 Yes Yes

SRVCC to GERAN LOFD-001023 Yes Yes

Intra-LTE Load Balancing

LOFD-001032 Yes Yes

Inter-RAT Load Sharing to UTRAN

LOFD-001044 Yes Yes

Inter-RAT Load Sharing to GERAN

LOFD-001045 Yes Yes

Service based inter-RAT handover to UTRAN

LOFD-001043 Yes Yes

Service based inter-RAT handover to GERAN

LOFD-001046 Yes Yes

CS Fallback to UTRAN LOFD-001033 Yes Yes

CS Fallback to GERAN LOFD-001034 Yes Yes

CS Fallback to CDMA2000 1xRTT

LOFD-001035 Yes Yes

RAN Sharing with Common Carrier

LOFD-001036 Yes Yes

RAN Sharing with Dedicated Carrier

LOFD-001037 Yes Yes

Remote Electrical Tilt Control

LOFD-001024 Yes No

Adaptive Power Consumption

LOFD-001025 Yes Yes

RF Channel Intelligent Shutdown

LOFD-001039 Yes Yes

Low Power Consumption Mode

LOFD-001040 Yes Yes

Power Consumption Monitoring

LOFD-001041 Yes No

Site and Equipment

Intelligent Power-Off of Carriers in the Same Coverage

LOFD-001042 Yes Yes

SON Automatic Neighbour Relation(ANR)

LOFD-002001 Yes Yes



2-7


Inter-RAT ANR: G/U/C LOFD-002002 Yes Yes

Self-configuration LOFD-002004 Yes No

Mobility Robust Optimization (MRO)

LOFD-002005 Yes No

PCI Collision Detection & Self-Optimization

LOFD-002007 Yes Yes

Sleeping Cell Detection LOFD-002010 Yes No

Antenna Fault Detection LOFD-002011 Yes No

Security Mechanism LOFD-001010 Yes No

Encryption: AES LOFD-00101001 Yes Yes

Transport and Security

Encryption: SNOW 3G LOFD-00101002 Yes Yes

Transport Networking 2G/3G and LTE Co-transmission

LOFD-003002 Yes No

Ethernet OAM LOFD-003004 Yes No

Ethernet OAM(IEEE 802.3ah)


Ethernet OAM(IEEE 802.1ag)


Transport Operation and Maintenance

Bidirectional Forwarding Detection

LOFD-003007 Yes Yes

OM Channel Backup LOFD-003005 Yes Yes

IP Route Backup LOFD-003006 Yes No

Transport Reliability

Ethernet Link Aggregation(IEEE 802.3ad)

LOFD-003008 Yes Yes

IPSEC LOFD-003009 Yes Yes

Public Key Infrastructure(PKI)

LOFD-003010 Yes Yes

Access Control based on 802.1x

LOFD-003015 Yes Yes

Integrated Firewall LOFD-003014 Yes No

Transport Security

Access Control List(ACL)


Transport QoS Enhanced Transport QoS Management

LOFD-003011 Yes No




Draft (2010–05–20)


Transport Overbooking LOFD-00301101 Yes Yes

Transport Differentiated Flow Control


Transport Resource Overload Control


IP Performance Monitoring

LOFD-003012 Yes No

IP Performance Monitoring


Transport Dynamic Flow Control


Different Transport Paths based on QoS Grade

LOFD-003016 Yes No

Enhanced Synchronization

LOFD-003013 Yes No

Synchronization with Ethernet(ITU-T G.8261)


IEEE1588 V2 Clock Synchroniztion


Transport Synchronization

Clock over IP (Huawei proprietary)


2.1 Configuring Normal CP 2.1.1 Enabling Normal CP

Prerequisite You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.

eNodeB The version is eRAN1.0 or later.

Transport network None.

NEs in the EPC None.



2-9

Item Requirement

OSS

None.

Context Setting Uplink cyclic prefix length or Downlink cyclic prefix length to

NORMAL_CP(Normal), which is performed when a cell is added, takes effect after the cell is activated.

To learn about the principles and rules for setting the parameters of this feature, see the Extended Cell Range Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the ADD CELL command to add a cell. In this step, set the Uplink cyclic prefix length

or Downlink cyclic prefix length parameter to NORMAL_CP(Normal).

Step 2 Run the ACT CELL command to activate the cell.

Step 3 Run the LST CELL command to check the cell configuration. The result indicates that the value of Uplink cyclic prefix length or Downlink cyclic prefix length is Normal.

----End

2.2 Configuring Integrity Protection 2.2.1 Enabling Integrity Protection

Prerequisite You have familiarized yourself with the integrity protection feature. For details about the

feature, see the Security Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE The UE supports the integrity protection algorithms of AES and SNOW 3G.




OSS None.




Draft (2010–05–20)

Context To learn about the principles and rules for setting the parameters of this feature, see the Security Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD ENODEBINTEGRITYCAP command to set the first-, second-, and

third-priority integrity protection algorithms.

If PrimaryIntegrityAlg is set to NULL, integrity protection is disabled.

Step 2 Run the LST ENODEBINTEGRITYCAP command to check the first-, second-, and third-priority integrity protection algorithms. The results are the same as the settings made in the previous step.

----End

2.2.2 Disabling Integrity Protection

Prerequisite You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB properly.

Context None.

Procedure Step 1 Run the MOD ENODEBINTEGRITYCAP command to set the integrity protection

capabilities of the eNodeB. In this step, set PrimaryIntegrityAlg to NULL.

Step 2 Run the LST ENODEBINTEGRITYCAP command to check the integrity protection capabilities of the eNodeB. The result indicates that the value of PrimaryIntegrityAlg is NULL.

----End

2.3 Configuring Admission Control 2.3.1 Enabling Admission Control

Prerequisite You have familiarized yourself with the admission control feature. For details, see the

Load Control Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB




2-11

Item Requirement

UE None.




OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the Load Control Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable admission control. In this step,

set the RAC algorithm switch parameter.

Select the LCEM_RAC_ALG_DL_SWITCH(dlCacSwitch) check box to enable the downlink admission control algorithm based on the QoS satisfaction rate.

Select the LCEM_RAC_ALG_UL_SWITCH(ulCacSwitch) check box to enable the uplink admission control algorithm based on the QoS satisfaction rate.

Select the LCEM_RAC_ALG_DL_PREDICT_SWIT(dlCacPredictSwitch) check box to enable the downlink admission control algorithm based on prediction.

Select the LCEM_RAC_ALG_UL_PREDICT_SWIT(ulCacPredictSwitch) check box to enable the uplink admission control algorithm based on prediction.

Select the LCEM_RAC_ALG_GBR_USAGE_SWITCH(GbrUsedPRbCheckSwitch) check box to enable the function for checking the number of PRBs occupied by the GBR services.

Step 2 Run the LST CELLALGOSWITCH command to check the status of the related algorithm.

If the downlink admission control algorithm based on the QoS satisfaction rate is enabled, the value of dlCacSwitch is On.

If the uplink admission control algorithm based on the QoS satisfaction rate is enabled, the value of ulCacSwitch is On.

If the downlink admission control algorithm based on prediction is enabled, the value of dlCacPredictSwitch is On.

If the uplink admission control algorithm based on prediction is enabled, the value of ulCacPredictSwitch is On.

If the function for checking the number of PRBs occupied by the GBR services is enabled, the value of GbrUsedPRbCheckSwitch is On.

----End




Draft (2010–05–20)

2.3.2 Disabling Admission Control


Context When the uplink/downlink admission control algorithm based on the QoS satisfaction

rate is disabled, admission control based on the QoS satisfaction rate is not implemented for the new service or handover request on the uplink/downlink. Therefore, resource overload may occur on the uplink/downlink.

When the uplink/downlink admission control algorithm based on prediction is disabled, admission control based on prediction is not implemented for the new service or handover request on the uplink/downlink. Therefore, resource overload may occur on the uplink/downlink.

When the function for checking the number of PRBs occupied by the GBR services is disabled, the GBR services may occupy too many PRBs. Therefore, the cell access success rate drops and the number of admitted UEs in the cell decreases.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable admission control. In this step,


Clear the LCEM_RAC_ALG_DL_SWITCH(dlCacSwitch) check box to disable the downlink admission control algorithm based on the QoS satisfaction rate.

Clear the LCEM_RAC_ALG_UL_SWITCH(ulCacSwitch) check box to disable the uplink admission control algorithm based on the QoS satisfaction rate.

Clear the LCEM_RAC_ALG_DL_PREDICT_SWIT(dlCacPredictSwitch) check box to disable the downlink admission control algorithm based on prediction.

Clear the LCEM_RAC_ALG_UL_PREDICT_SWIT(ulCacPredictSwitch) check box to disable the uplink admission control algorithm based on prediction.

Clear the LCEM_RAC_ALG_GBR_USAGE_SWITCH(GbrUsedPRbCheckSwitch) check box to disable the function for checking the number of PRBs occupied by the GBR services.


If the downlink admission control algorithm based on the QoS satisfaction rate is disabled, the value of dlCacSwitch is Off.

If the uplink admission control algorithm based on the QoS satisfaction rate is disabled, the value of ulCacSwitch is Off.

If the downlink admission control algorithm based on prediction is disabled, the value of dlCacPredictSwitch is Off.

If the uplink admission control algorithm based on prediction is disabled, the value of ulCacPredictSwitch is Off.

If the function for checking the number of PRBs occupied by the GBR services is disabled, the value of GbrUsedPRbCheckSwitch is Off.

----End



2-13

2.4 Configuring Congestion Control 2.4.1 Enabling Congestion Control

Prerequisite You have familiarized yourself with the congestion control feature. For details, see the

Load Control Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.




OSS None.


Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable congestion control. In this step,


Select the LCEM_RAC_ALG_DL_LDC_SWITCH(dlLdcSwitch) check box to enable the downlink load control algorithm.

Select the LCEM_RAC_ALG_UL_LDC_SWITCH(ulLdcSwitch) check box to enable the uplink load control algorithm.

Enable the downlink or uplink load control algorithm, and then select the LCEM_LDC_ALG_REL_DRB_SWITCH(LdcDrbRelSwitch) check box to enable the service release function.


If the downlink load control algorithm is enabled, the value of dlLdcSwitch is On. If the uplink load control algorithm is enabled, the value of ulLdcSwitch is On. If the service release function is enabled, the value of LdcDrbRelSwitch is On.

----End




Draft (2010–05–20)

2.4.2 Disabling Congestion Control


Context If the uplink/downlink load control is disabled, the system cannot determine whether the

uplink/downlink resources are overloaded in the cell. In addition, load control cannot be implemented when the uplink/downlink load is heavy in the cell. As a result, the call drop rate increases and the QoS satisfaction rate drops.

When the service release function is disabled, the congestion cannot be relieved in the case of resource overload.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable congestion control. In this step,


Clear the LCEM_RAC_ALG_DL_LDC_SWITCH(dlLdcSwitch) check box to disable the downlink load control algorithm.

Clear the LCEM_RAC_ALG_UL_LDC_SWITCH(ulLdcSwitch) check box to disable the uplink load control algorithm.

Clear the LCEM_LDC_ALG_REL_DRB_SWITCH(LdcDrbRelSwitch) check box to disable the service release function.


If the downlink load control algorithm is disabled, the value of dlLdcSwitch is Off. If the uplink load control algorithm is disabled, the value of ulLdcSwitch is Off. If the service release function is disabled, the value of LdcDrbRelSwitch is Off.

----End

2.5 Configuring DRX 2.5.1 Enabling DRX

Prerequisite You have familiarized yourself with the DRX feature. For details, see the DRX Feature

Parameter Description. You have logged in to the eNodeB LMT. The LMT communicates with the eNodeB

properly. The requirements of the feature listed in the following table are fulfilled.

Item Requirement

UE None.



2-15

Item Requirement

eNodeB The version is eRAN1.1.



OSS None.

Context When DRX is enabled, the UE shall enable and disable its receiver periodically. In this

case, the service delay is increased, and the power consumption of the UE is reduced when the receiver is disabled.

To learn about the principles and rules for setting the parameters of this feature, see the DRX Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD DRX command and set the DrxAlgSwitch parameter to ON(On).

Step 2 Run the LST DRX command to check the DRX configuration. If the result indicates that the value of DrxAlgSwitch is On, it is an indication that DRX is enabled.

----End

2.5.2 Disabling DRX

Prerequisite You have logged in to the eNodeB LMT. The LMT communicates with the eNodeB properly.

Context After DRX is disabled, the system cannot provide the DRX feature. In this case, the service delay is reduced and the power consumption of the UE is increased.

Procedure Step 1 Run the MOD DRX command and set the DrxAlgSwitch parameter to OFF(Off).

The eNodeB instructs a UE to exit from the DRX state when the UE initiates DRX reconfiguration.

Step 2 Run the LST DRX command to check the DRX configuration. If the result indicates that the value of DrxAlgSwitch is Off, it is an indication that DRX is disabled.

----End




Draft (2010–05–20)

2.6 Configuring Coverage Based Intra-Frequency Handover 2.6.1 Enabling Coverage Based Intra-Frequency Handover

Prerequisite You have familiarized yourself with the coverage-based intra-frequency handover feature.

For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.

You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB properly.

The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.




OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the

Mobility Management in Connected Mode Feature Parameter Description and eNodeB MO Reference.

By default, the coverage-based intra-frequency handover feature is enabled. Typically, no manual enabling is required.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable coverage-based

intra-frequency handover. In this step, select the IntraFreqHoSwitch(IntraFreqHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. The result indicates that the value of IntraFreqHoSwitch is on.

----End

2.6.2 Disabling Coverage Based Intra-Frequency Handover




2-17

Context After the coverage-based intra-frequency handover feature is disabled, the eNodeB cannot provide the handover service.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable coverage-based

intra-frequency handover. In this step, clear the IntraFreqHoSwitch(IntraFreqHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. The result indicates that the value of IntraFreqHoSwitch is off.

----End

2.7 Configuring Coverage Based Inter-Frequency Handover 2.7.1 Enabling Coverage Based Inter-Frequency Handover

Prerequisite You have familiarized yourself with the coverage-based inter-frequency handover feature.

For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.



Item Requirement

UE The UE supports gap-assisted measurements.




OSS None.



By default, the coverage-based inter-frequency handover feature is enabled. Typically, no manual enabling is required.




Draft (2010–05–20)

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable coverage-based

inter-frequency handover. In this step, select the InterFreqHoSwitch(InterFreqHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. The result indicates that the value of InterFreqHoSwitch is on.

----End

2.7.2 Disabling Coverage Based Inter-Frequency Handover


Context After the coverage-based inter-frequency handover feature is disabled, the eNodeB cannot provide the coverage-based inter-frequency handover service.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable coverage-based

inter-frequency handover. In this step, clear the InterFreqHoSwitch(InterFreqHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. The result indicates that the value of InterFreqHoSwitch is off.

----End

2.8 Configuring Downlink Static Inter-Cell Interference Coordination 2.8.1 Enabling Downlink Static Inter-Cell Interference Coordination

Prerequisite

You have familiarized yourself with the downlink static inter-cell interference coordination (ICIC) feature. For details about the feature, see the ICIC Feature Parameter Description.


The edge band and center band of the cell have been determined and configured.




2-19

Item Requirement

UE None.




OSS None.

Context

To learn about the principles and rules for setting the parameters of this feature, see the ICIC Feature Parameter Description and eNodeB MO Reference.

Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, select DlIcicStaticSwitch_ON_ENUM under the DlIcicAlgoSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of DlIcicAlgoSwitch is DlIcicStaticSwitch_ON_ENUM, you can infer that downlink static ICIC is enabled.

----End

2.8.2 Disabling Downlink Static Inter-Cell Interference Coordination

Prerequisite


Context

If this feature is disabled, downlink inter-cell interference cannot be mitigated in static mode.

Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, select DlIcicSwitch_OFF_ENUM under the DlIcicAlgoSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of DlIcicAlgoSwitch is DlIcicSwitch_OFF_ENUM, you can infer that downlink static ICIC is disabled.

To disable only downlink static ICIC rather than overall downlink ICIC, perform the operations provided in section 2.24 "Configuring Downlink Dynamic Inter-Cell Interference Coordination."

----End




Draft (2010–05–20)

2.9 Configuring Uplink Static Inter-Cell Interference Coordination 2.9.1 Enabling Uplink Static Inter-Cell Interference Coordination

Prerequisite

You have familiarized yourself with the uplink static inter-cell interference coordination feature. For details about the feature, see the ICIC Feature Parameter Description.


The edge band and center band of the cell have been determined and configured.


Item Requirement

UE None.




OSS None.

Context


Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, set UlicicFreqSwitch to STATIC.

To enable time-domain UL ICIC, select the UlicicIntraSwitch(Uplink Intra-eNB ICIC switch) check box under the UlIcicTimeSwitch parameter. It is recommended that time-domain UL ICIC be enabled after frequency-domain UL ICIC is enabled.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of UlicicFreqSwitch is STATIC, you can infer that frequency-domain static UL ICIC is enabled. If the value of UlIcicTimeSwitch is Uplink Intra-eNB ICIC switch:On, you can infer that time-domain UL ICIC is enabled.

----End



2-21

2.9.2 Disabling Uplink Static Inter-Cell Interference Coordination

Prerequisite


Context

If this feature is disabled, uplink inter-cell interference cannot be mitigated in static mode.

Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, set UlicicFreqSwitch to OFF.

To disable time-domain UL ICIC, clear the UlicicIntraSwitch(Uplink Intra-eNB ICIC switch) check box under the UlIcicTimeSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of UlicicFreqSwitch is OFF, you can infer that frequency-domain static UL ICIC is disabled. If the value of UlIcicTimeSwitch is Uplink Intra-eNB ICIC switch:Off, you can infer that time-domain UL ICIC is disabled.

----End

2.10 Configuring SCTP Multi-Homing 2.10.1 Enabling SCTP Multi-Homing

Prerequisite Physical ports and logical ports have been configured. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly. The ports involved support the SCTP multi-homing feature. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement


CN

None.

OSS None.

eNodeB The software version is eRAN1.0 or later.




Draft (2010–05–20)

Context For parameter setting principles and rules related to this feature, see the Transport Management Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the ADD SCTPLNK command to add two SCTP links. In this step, set the following

parameters: SCTP Link No., Slot No., First Local IP Address, Second Local IP Address, Local SCTP Port No., First Peer IP Address, Second Peer IP Address, and Peer SCTP Port No..

Step 2 Run the LST SCTPLNK command to check the SCTP link configuration. If the results are the same as the settings made in the previous step, it is an indication that SCTP multi-homing is enabled.

----End

2.10.2 Disabling SCTP Multi-Homing


Context Disabling SCTP multi-homing may reduce transport reliability.

Procedure Step 1 Run the RMV SCTPLNK command to remove an SCTP link. In this step, set SCTP Link

No. to the number of the SCTP link to be removed.

Step 2 Run the LST SCTPLNK command to check the SCTP link configuration. In this step, set SCTP Link No. to the number of the SCTP link removed. If the information about the link is not displayed, it is an indication that SCTP multi-homing is disabled.

----End

2.11 Configuring VLAN Support (IEEE 802.1p/q) 2.11.1 Enabling VLAN Support (IEEE 802.1p/q)





2-23

Item Requirement



OSS None.

eNodeB Software requirement: The version is eRAN1.0 or later.

Context If different operators require differentiated services, VLAN Mode should be set to

SINGLEVLAN. In addition, if one operator requires differentiated services, VLAN Mode should be set to VLANGROUP.

For parameter setting principles and rules related to this feature, see the Transport Management Feature Parameter Description and eNodeB MO Reference.

Procedure To configure the policy between the eNodeB and the VLANs, perform the following steps:

Step 1 Run the ADD VLANMAP command to add a next-hop VLAN mapping relationship. In this step, specify the corresponding VLAN record, Next Hop IP, and VLAN Mode. When VLAN Mode is set to SINGLEVLAN, the mapping between VLANs and DSCPs is not required.

If... Then...

VLAN Mode is SINGLEVLAN Specify VLAN ID.

VLAN Mode is VLANGROUP Specify VLAN Group No..

Step 2 Run the LST VLANMAP command to list the mapping relationship between Address Resolution Protocol (ARP) and VLAN. Check the configuration in the result displayed on the eNodeB LMT.

----End

To configure the VLAN priority mapping, proceed with the following steps:

Step 1 Run the ADD VLANCLASS command to add a VLAN priority mapping relationship. In this step, specify VLAN Group No., Traffic Type, and VLAN ID.

Step 2 Run the LST VLANCLASS command to list the VLAN priority mapping relationships. Check the configuration in the result displayed on the eNodeB LMT.

----End




Draft (2010–05–20)

2.11.2 Disabling VLAN Support (IEEE 802.1p/q)


Context After a VLAN mapping relationship is removed, services related to this VLAN ID cannot run properly.

Procedure Step 1 Run the RMV VLANMAP command to disable the VLAN Support (IEEE 802.1p/q) function.

In this step, specify Next Hop IP for which the function needs to be disabled.

Step 2 Run the LST VLANMAP command. If the value of Next Hop IP is not displayed in the result, you can infer that the VLAN Support (IEEE 802.1p/q) function is disabled.

----End

2.12 Configuring IP Header Compression 2.12.1 Enabling IP Header Compression

Prerequisite The E1/T1 port has been configured. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement


CN None.

OSS None.





2-25

Procedure Step 1 Run the ADD PPPLNK command. In this step, specify Slot No., PPP Link No., Port No.,

Authentication Type, Time Slot No., Local IP, Mask and Peer IP, and set IP Header Compression to ENABLE(Enable).

Step 2 Run the LST PPPLNK command to check the PPP link configuration. If the value of IP Header Compression is Enable, it is an indication that IP header compression is enabled.

----End

2.12.2 Disabling IP Header Compression


Context If IP header compression is disabled, UDP/IP headers in user plane packets on the S1 or X2 interface are not compressed, thereby failing to achieve the goals of reducing layer 3 overhead and improving transmission efficiency.

Procedure Step 1 Run the RMV PPPLNK command. In this step, specify Slot No., PPP Link No., Port No.,

Authentication Type, Time Slot No., Local IP, Mask and Peer IP, and set IP Header Compression to DISABLE(Disable).

Step 2 Run the LST PPPLNK command to check the PPP link configuration. If the value of IP Header Compression is Disable, it is an indication that IP header compression is disabled.

----End

2.13 Configuring PPP MUX 2.13.1 Enabling PPP MUX



Item Requirement


CN None.




Draft (2010–05–20)

Item Requirement

OSS None.



Procedure Step 1 Run the ADD PPPLNK command. In this step, specify Slot No., PPP Link No., Port No.,

Authentication Type, Time Slot No., Local IP, Mask and Peer IP; set PPPMUX to ENABLE(Enable), and then specify Maximum Length of PPP Mux Subframe (byte), Maximum Length of PPP Muxframe (byte), and PPP Muxframe Combination Timeout(ms).

Step 2 Run the LST PPPLNK command to check the PPP link configuration. If the value of PPPMUX is Enable, it is an indication that PPP MUX is enabled.

----End

2.13.2 Disabling PPP MUX


Context If PPP MUX is disabled, multiplexing of PPP frames on a PPP link is not implemented, thereby failing to achieve the goals of reducing overhead and improving transmission efficiency.

Procedure Step 1 Run the RMV PPPLNK command. In this step, specify Slot No., PPP Link No., Port No.,

Authentication Type, Time Slot No., Local IP, Mask and Peer IP and set PPPMUX to DISABLE(Disable).

Step 2 Run the LST PPPLNK command to check the PPP link configuration. If the value of PPPMUX is Disable, it is an indication that PPP MUX is disabled.

----End



2-27

2.14 Configuring ML-PPP/MC-PPP 2.14.1 Enabling ML-PPP/MC-PPP



Item Requirement


CN None.

OSS None.



Procedure To enable MLPPP, perform the following steps:

Step 1 Run the ADD MPGRP command to add an MLPPP group. In this step, specify Slot No., MLPPP Group No., Authentication Type, Local IP, Mask, and Peer IP.

Step 2 Run the ADD MPLNK command to add an MLPPP link. In this step, set the following parameters: Slot No., ML PPP Group No., PPP Link No., E1/T1 Slot No., E1/T1 Port No., and Time Slot No..

Step 3 Run the LST MPLNK command to check the MLPPP link configuration. If the results are the same as the settings made in the previous step, it is an indication that MLPPP is enabled.

----End

To enable MCPPP, perform the following steps:

Step 1 Run the ADD MPGRP command. In this step, specify Slot No., MLPPP Group No., Authentication Type, Local IP, Mask and Peer IP and set Multi-Class PPP to ENABLE(Enable).

Step 2 Run the LST MPGRP command to check the MLPPP group configuration. If the value of Multi-Class PPP is Enable, it is an indication that MCPPP is enabled.

----End




Draft (2010–05–20)

2.14.2 Disabling ML-PPP/MC-PPP


Context If MLPPP or MCPPP is disabled, PPP links are not grouped, thereby failing to achieve the goal of improving transmission efficiency.

Procedure To disable MLPPP, perform the following steps:

Step 1 Run the RMV MPLNK command to remove an MLPPP link. In this step, specify Slot No. and PPP Link No..

Step 2 Run the RMV MPGRP command to remove an MLPPP group. In this step, specify Slot No. and MLPPP Group No..

Step 3 Run the LST MPGRP command to check the MLPPP group configuration. If the MLPPP group removed in the previous step is not displayed in the result, it is an indication that MLPPP is disabled.

----End

To disable MCPPP, perform the following steps:

Step 1 Run the RMV MPGRP command. In this step, specify Slot No., MLPPP Group No., Authentication Type, Local IP, Mask and Peer IP and set Multi-Class PPP to DISABLE(Disable).

Step 2 Run the LST MPGRP command to check the MLPPP group configuration. If the value of Multi-Class PPP is Disable, it is an indication that MCPPP is disabled.

----End

2.15 Configuring Clock Source Switching Manually or Automatically 2.15.1 Enabling Clock Source Switching Manually or Automatically

Prerequisite You have familiarized yourself with the feature of manual/automatic switching of clock

sources. For details about the feature, see the Synchronization Feature Parameter Description.



2-29



Item Requirement

UE None.




OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the Synchronization Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the SET CLKMODE command to set the working mode of the clock. In this step, set

Clock Work Mode to MANUAL(Manual) or AUTO(Auto).

Step 2 Run the LST CLKMODE command to check the working mode of the clock. The result indicates that the value of Clock Work Mode is the same as the setting made in the previous step.

----End

2.15.2 Disabling Clock Source Switching Manually or Automatically


Context None.


Clock Work Mode to FREE(Free).

Step 2 Run the LST CLKMODE command to check the working mode of the clock. The result indicates that the value of Clock Work Mode is Free.

----End




Draft (2010–05–20)

2.16 Configuring Free-Running Mode 2.16.1 Enabling Free-Running Mode

Prerequisite You have familiarized yourself with the feature of free-running mode. For details about

the feature, see the Synchronization Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.




OSS None.



Clock Work Mode to FREE(Free).

Step 2 Run the LST CLKMODE command to check the working mode of the clock. The result indicates that the value of Clock Work Mode is Free.

----End

2.16.2 Disabling Free-Running Mode


Context None.



2-31


Clock Work Mode to MANUAL(Manual) or AUTO(Auto).

Step 2 Run the LST CLKMODE command to check the working mode of the clock. The result indicates that the value of Clock Work Mode is the same as the setting made in the previous step.

----End

2.17 Configuring Synchronization with GPS 2.17.1 Enabling Synchronization with GPS

Prerequisite You have familiarized yourself with the feature of synchronization with the GPS clock.

For details about the feature, see the Synchronization Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.

eNodeB The eNodeB supports the GPS antenna system, and the eNodeB version is eRAN1.1 or later.



OSS None.


Procedure Step 1 Run the ADD CLKSRC command to add a clock source. In this step, set Clock Source Type

to GPS(GPS), and specify Clock Source Priority.

Step 2 Run the ADD GPS command to add a GPS clock link. In this step, set Slot No. to the number of the slot where the GPS card is located.

Step 3 Run the DSP CLKSRC command to check the status of the clock source. The result indicates that the status of the GPS clock is Available.

----End




Draft (2010–05–20)

2.17.2 Disabling Synchronization with GPS


Context When the working mode of the clock is manual, the clock source in use cannot be

removed. If the GPS clock is the only clock source of the LTE system, disabling synchronization

with the GPS clock results in a loss of the system clock source. This affects the operation of the LTE system.

Procedure Step 1 Run the RMV GPS command to remove the GPS clock link.

Step 2 Run the RMV CLKSRC command to remove the clock source. In this step, set Clock Source Type to GPS(GPS).

Step 3 Run the LST CLKSRC command to check clock sources. The GPS clock is not displayed in the result.

----End

2.18 Configuring Synchronization with E1/T1 2.18.1 Enabling Synchronization with E1/T1

Prerequisite You have familiarized yourself with the feature of synchronization with the E1/T1 line

clock. For details about the feature, see the Synchronization Feature Parameter Description.



Item Requirement

UE None.

eNodeB The eNodeB is configured with the UTRP, and the eNodeB version is eRAN1.1 or later.



OSS None.



2-33



to LINECLK(Lineclk), and specify Clock Source Priority.

Step 2 Run the ADD LINECLK command to add an E1/T1 line clock link. In this step, set Slot No. and Port No. to the number of the slot and the number of the port where the E1/T1 line clock is configured respectively.

Step 3 Run the DSP CLKSRC command to check the status of the clock source. The result indicates that the status of the E1/T1 line clock is Available.

----End

2.18.2 Disabling Synchronization with E1/T1



removed. If the E1/T1 line clock is the only clock source of the LTE system, disabling

synchronization with the E1/T1 line clock results in a loss of the system clock source. This affects the operation of the LTE system.

Procedure Step 1 Run the RMV LINECLK command to remove the E1/T1 line clock link.

Step 2 Run the RMV CLKSRC command to remove the clock source. In this step, set Clock Source Type to LINECLK(Lineclk).

Step 3 Run the LST CLKSRC command to check clock sources. The E1/T1 line clock is not displayed in the result.

----End

2.19 Configuring UL 2x2 MU-MIMO 2.19.1 Enabling UL 2x2 MU-MIMO

Prerequisite The license for this feature has been activated.




Draft (2010–05–20)

You have familiarized yourself with this feature by reading the MIMO Feature Parameter Description.



Item Requirement



UE None.

Context To learn about the principles and rules for setting the parameters of this feature, see the MIMO Feature Parameter Description, eNodeB Parameter Reference, and eNodeB MO reference.

Procedure Step 1 Run the MOD CELLULSCHALGO command. In this step, set UpLink Virtual MIMO

Switch to ON.

Step 2 Run the LST CELLULSCHALGO command. If the value of UpLink Virtual MIMO Switch is ON, the feature has been enabled.

Step 3 Log in to the LMT. In the navigation tree of the LMT, click the Monitor tab, and then double-click Realtime Performance Monitoring and Cell Performance Monitoring. A dialog box is displayed, as shown in Figure 2-1. Click Multi User-MIMO in the Monitor Item drop-down list, set Monitor Period(ms) and Cell ID, and then click Submit. In the displayed real-time monitoring window, view the number of MIMO user pairs.

Figure 2-1 Monitoring MU-MIMO



2-35

If the displayed number of MIMO user pairs is not 0, the UL 2x2 MU-MIMO feature has been enabled.

Figure 2-2 shows the MU-MIMO monitoring result.

Figure 2-2 MU-MIMO monitoring result

----End

2.19.2 Disabling UL 2x2 MU-MIMO


Context Disabling the UL 2x2 MU-MIMO feature reduces the system throughput.

Procedure Step 1 Run the MOD CELLULSCHALGO command. In this step, set UpLink Virtual MIMO

Switch to OFF.

Step 2 Run the LST CELLULSCHALGO command. If the value of UpLink Virtual MIMO Switch is OFF, the feature has been disabled.

Step 3 Log in to the LMT. In the navigation tree of the LMT, click the Monitor tab, and then double-click Realtime Performance Monitoring and Cell Performance Monitoring to start cell performance monitoring. Click Multi User-MIMO in the Monitor Item drop-down list, set Monitor Period(ms) and Cell ID, and then click Submit. In the displayed real-time monitoring window, view the number of MIMO user pairs. If the displayed number of MIMO user pairs is 0, the UL 2x2 MU-MIMO feature has been disabled.

----End




Draft (2010–05–20)

2.20 Configuring Uplink 64QAM 2.20.1 Enabling Uplink 64QAM

Prerequisite The license of the feature has been activated. You have familiarized yourself with 3GPP TS 36.211. You have logged in to the eNodeB LMT. The LMT communicates with the eNodeB


Item Requirement

UE The UE supports uplink 64QAM.




OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the Scheduling Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD PUSCHCFG command to enable uplink 64QAM. In this step, set the Qam64

enabled parameter to BOOLEAN_TRUE(True).

Step 2 Run the LST PUSCHCFG command. Verify that the value of Qam64 enabled is True.

----End

2.20.2 Disabling Uplink 64QAM


Context In favorable radio conditions, the uplink data rate is affected if uplink 64QAM is disabled.



2-37

Procedure Step 1 Run the MOD PUSCHCFG command to disable uplink 64QAM. In this step, set the Qam64

enabled parameter to BOOLEAN_FALSE(False).

Step 2 Run the LST PUSCHCFG command. Verify that the value of Qam64 enabled is False.

----End

2.21 Configuring Encryption: AES 2.21.1 Enabling Encryption: AES

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of encryption based on Advanced

Encryption Standard (AES). For details about the feature, see the Security Feature Parameter Description.



Item Requirement

UE The UE supports the AES ciphering algorithm.




OSS None.


Procedure Step 1 Run the MOD ENODEBCIPHERCAP command to set the ciphering capabilities of the

eNodeB. In this step, set at least one of PrimaryCiperAlg and SecondCiperAlg to AES.

If PrimaryCiperAlg is set to NULL, encryption is disabled.

Step 2 Run the LST ENODEBCIPHERCAP command to check the ciphering capabilities of the eNodeB. The results are the same as the settings made in the previous step.

----End




Draft (2010–05–20)

2.21.2 Disabling Encryption: AES


Context None.


eNodeB. In this step, set PrimaryCiperAlg to NULL.

Step 2 Run the LST ENODEBCIPHERCAP command to check the ciphering capabilities of the eNodeB. The result indicates that the value of PrimaryCiperAlg is NULL.

----End

2.22 Configuring Encryption: SNOW 3G 2.22.1 Enabling Encryption: SNOW 3G

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of encryption based on SNOW 3G. For

details about the feature, see the Security Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE The UE supports the SNOW 3G ciphering algorithm.




OSS None.




2-39


eNodeB. In this step, set at least one of PrimaryCiperAlg and SecondCiperAlg to Snow3G.

If PrimaryCiperAlg is set to NULL, encryption is disabled.

Step 2 Run the LST ENODEBCIPHERCAP command to check the ciphering capabilities of the eNodeB. The results are the same as the settings made in the previous step.

----End

2.22.2 Disabling Encryption: SNOW 3G


Context None.


eNodeB. In this step, set PrimaryCiperAlg to NULL.

Step 2 Run the LST ENODEBCIPHERCAP command to check the ciphering capabilities of the eNodeB. The result indicates that the value of PrimaryCiperAlg is NULL.

----End

2.23 Configuring UL Interference Rejection Combining 2.23.1 Enabling UL Interference Rejection Combining

Prerequisite The license for the UL interference rejection combining feature has been activated.

You have familiarized yourself with this feature. For details about the feature, see the ICIC Feature Parameter Description.



Item Requirement

UE None.




Draft (2010–05–20)

Item Requirement

eNodeB The version is eRNA1.0 or later. The eNodeB is configured with multiple RX antennas.



OSS None.

Context


Procedure

No configuration is required after the license is activated.

2.24 Configuring Downlink Dynamic Inter-Cell Interference Coordination 2.24.1 Enabling Downlink Dynamic Inter-Cell Interference Coordination

Prerequisite

The license for the downlink dynamic inter-cell interference coordination feature has been activated.



Two neighboring cells have the same frequency and bandwidth. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.




OSS None.



2-41

Context


Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, select DlIcicDynamicSwitch_ON_ENUM under the DlIcicAlgoSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of DlIcicAlgoSwitch is DlIcicDynamicSwitch_ON_ENUM, you can infer that downlink dynamic ICIC is enabled.

----End

2.24.2 Disabling Downlink Dynamic Inter-Cell Interference Coordination

Prerequisite


Context

If this feature is disabled, downlink inter-cell interference cannot be mitigated in dynamic mode.

Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, select DlIcicSwitch_OFF_ENUM under the DlIcicAlgoSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of DlIcicAlgoSwitch is DlIcicSwitch_OFF_ENUM, you can infer that downlink dynamic ICIC is disabled.

To disable only dynamic downlink ICIC rather than overall downlink ICIC, perform the operations provided in section 2.8 "Configuring Downlink Static Inter-Cell Interference Coordination."

----End




Draft (2010–05–20)

2.25 Configuring Uplink Dynamic Inter-Cell Interference Coordination 2.25.1 Enabling Uplink Dynamic Inter-Cell Interference Coordination

Prerequisite

The license for the uplink dynamic inter-cell interference coordination feature has been activated.



Two neighboring cells have the same frequency and bandwidth.


Item Requirement

UE None.




OSS None.

Context


Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, set UlicicFreqSwitch to DYNAMIC.

To enable time-domain UL ICIC, select the UlicicIntraSwitch(Uplink Intra-eNB ICIC switch) check box under the UlIcicTimeSwitch parameter. It is recommended that time-domain UL ICIC be enabled after frequency-domain UL ICIC is enabled.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of UlicicFreqSwitch is DYNAMIC, you can infer that frequency-domain dynamic UL ICIC is enabled. If the value of UlIcicTimeSwitch is Uplink Intra-eNB ICIC switch:On, you can infer that time-domain UL ICIC is enabled.

----End



2-43

2.25.2 Disabling Uplink Dynamic Inter-Cell Interference Coordination

Prerequisite


Context

If this feature is disabled, uplink inter-cell interference cannot be mitigated in dynamic mode.

Procedure

Step 1 Run the MOD ENODEBALGOSWITCH command. In this step, set UlicicFreqSwitch to OFF.

To disable time-domain UL ICIC, clear the UlicicIntraSwitch(Uplink Intra-eNB ICIC switch) check box under the UlIcicTimeSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command. If the value of UlicicFreqSwitch is OFF, you can infer that frequency-domain dynamic UL ICIC is disabled. If the value of UlIcicTimeSwitch is Uplink Intra-eNB ICIC switch:Off, you can infer that time-domain UL ICIC is disabled.

----End

2.26 Configuring CQI Adjustment 2.26.1 Enabling CQI Adjustment

Prerequisite You have familiarized yourself with the scheduling feature. For details about the

scheduling feature, see the Scheduling Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.




OSS None.




Draft (2010–05–20)

Context To learn about the principles and rules for setting the parameters of this feature, see the Scheduling Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable CQI adjustment. In this step,

select the CqiAdjAlgoSwitch check box under the Cqi Adjust algorithm switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of CqiAdjAlgoSwitch is On.

----End

2.26.2 Disabling CQI Adjustment


Context The reported CQI may not indicate the channel quality accurately. If CQI adjustment is disabled, the IBLER of the UE transmission may fail to approach the IBLER target. In this case, the system capacity decreases.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable CQI adjustment. In this step,

clear the CqiAdjAlgoSwitch check box under the Cqi Adjust algorithm switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of CqiAdjAlgoSwitch is Off.

----End

2.27 Configuring TCP Proxy Enhancement (TPE) 2.27.1 Enabling TCP Proxy Enhancement (TPE)

Prerequisite The license for the feature is activated. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB




2-45

Item Requirement

UE None.



CN None.

OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the TPE Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable TPE. In this step, select the

TpeAlgoSwitch check box under the Tpe algorithm Visual switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. If the result indicates that the value of TpeAlgoSwitch is On, it is an indication that TPE is enabled.

----End

2.27.2 Disabling TCP Proxy Enhancement (TPE)


Context None.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable TPE. In this step, clear the

TpeAlgoSwitch check box under the Tpe algorithm Visual switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. If the result indicates that the value of TpeAlgoSwitch is Off, it is an indication that TPE is disabled.

----End




Draft (2010–05–20)

2.28 Configuring Active Queue Management(AQM) 2.28.1 Enabling Active Queue Management(AQM)

Prerequisite The license for this feature has been activated. You have familiarized yourself with the principles of AQM. For details about the feature,

see the AQM Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.




OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the AQM Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable AQM. In this step, select the

AqmAlgoSwitch check box under the AQM algorithm switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of AqmAlgoSwitch is On.

----End

2.28.2 Disabling Active Queue Management(AQM)


Context None.



2-47

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable AQM. In this step, clear the

AqmAlgoSwitch check box under the AQM algorithm switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of AqmAlgoSwitch is Off.

----End

2.29 Configuring Radio/Transport Resource Rre-emption 2.29.1 Enabling Radio Resource Pre-emption

Prerequisite The license for this feature has been activated. You have familiarized yourself with the load control feature. For details about the feature,

see the Load Control Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.




OSS None.


Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable radio resource pre-emption. In

this step, select the LCEM_RAC_ALG_PREEMPTION_SWITCH(PreemptionSwitch) check box under the RAC algorithm switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of PreemptionSwitch is On.

----End




Draft (2010–05–20)

2.29.2 Disabling Radio Resource Pre-emption


Context If radio resource pre-emption is disabled, pre-emption is not applicable when radio resources are insufficient.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable radio resource pre-emption. In

this step, clear the LCEM_RAC_ALG_PREEMPTION_SWITCH(PreemptionSwitch) check box under the RAC algorithm switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of PreemptionSwitch is Off.

----End

2.29.3 Enabling Transport Resource Rre-emption

Prerequisite Physical ports and logical ports have been configured. Transport admission control has been enabled. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement


CN None.

OSS None.


Context When the transmission bandwidth is sufficient, enabling transport resource pre-emption

increases the access success rate of high-priority services, but it also increases the drop rate of low-priority services.




2-49

Procedure To enable uplink transport resource pre-emption, perform the following steps:

Step 1 Run the SET TACALG command to enable uplink transport resource pre-emption. In this step, set Uplink Admission Control Algorithm Switch and Uplink Pre-emption Algorithm Switch to ON(On).

Step 2 Run the LST TACALG command to check the admission control configuration. If the values of Uplink Admission Control Algorithm Switch and Uplink Pre-emption Algorithm Switch are both On, it is an indication that uplink transport resource pre-emption is enabled.

----End

To enable downlink transport resource pre-emption, perform the following steps:

Step 1 Run the SET TACALG command to enable downlink transport resource pre-emption. In this step, set Downlink Admission Control Algorithm Switch and Downlink Pre-emption Algorithm Switch to ON(On).

Step 2 Run the LST TACALG command to check the admission control configuration. If the values of Downlink Admission Control Algorithm Switch and Downlink Pre-emption Algorithm Switch are both On, it is an indication that downlink transport resource pre-emption is enabled.

----End

2.29.4 Disabling Transport Resource Rre-emption


Context If transport resource pre-emption is disabled, the high access success rate cannot be guaranteed for high-priority services, but the call drop rate is not affected.

Procedure To disable uplink transport resource pre-emption, perform the following steps:

Step 1 Run the SET TACALG command to disable uplink transport resource pre-emption. In this step, set Uplink Pre-emption Algorithm Switch to OFF(Off).

Step 2 Run the LST TACALG command to check the admission control configuration. If the value of Uplink Pre-emption Algorithm Switch is Off, it is an indication that uplink transport resource pre-emption is disabled.

----End




Draft (2010–05–20)

To disable downlink transport resource pre-emption, perform the following steps:

Step 1 Run the SET TACALG command to disable downlink transport resource pre-emption. In this step, set Downlink Pre-emption Algorithm Switch to OFF(Off).

Step 2 Run the LST TACALG command to check the admission control configuration. If the value of Downlink Pre-emption Algorithm Switch is Off, it is an indication that downlink transport resource pre-emption is disabled.

----End

2.30 Configuring RObust Header Compression (ROHC) 2.30.1 Enabling ROHC

Prerequisite The license for this feature has been activated. You have familiarized yourself with the ROHC feature. For details about the feature, see

the ROHC Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE The UE must support the ROHC function.




OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the ROHC Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD PDCPROHCPARA command to enable ROHC. In this step, set

ROHCSwitch to ON(On), and then set HighestMode and Profiles according to the service requirements.

Step 2 Run the DSP PDCPROHC command. The result indicates that the value of ROHCSwitch is ON(On) and that HighestMode and Profiles are the target values.

Step 3 On the M2000, view the performance counters L.PDCP.DL.RoHC.HdrCompRatio and L.PDCP.DL.ROCH.PktCompRatio.



2-51

If the value of L.PDCP.DL.RoHC.HdrCompRatio is smaller than 1, the ROHC function is enabled.

If the value of L.PDCP.DL.RoHC.PktCompRatio is smaller than 1, the ROHC function is enabled.

The ROHC function is applicable only to the compression and decompression of data on the user

plane. Therefore, you can view the preceding performance counters only when the eNodeB is transmitting data over the user plane.

After the ROHC function is enabled, extra information is contained in the header of the data packet transmitted by the eNodeB in adverse radio conditions. This facilitates the decompression of the data packet at the UE. In this case, the collected L.PDCP.DL.RoHC.HdrCompRatio and L.PDCP.DL.RoHC.PktCompRatio values may be greater than 1, which also indicates that the ROHC function is enabled.

----End

2.30.2 Disabling ROHC


Context Disabling ROHC indicates that the system cannot provide the ROHC function.

Procedure Step 1 Run the MOD PDCPROHCPARA command to disable ROHC. In this step, set

ROHCSwitch to OFF(Off).

Step 2 Run the DSP PDCPROHCPARA command. The result indicates that the value of ROHCSwitch is OFF(Off).

Step 3 On the M2000, view the performance counters L.PDCP.DL.RoHC.HdrCompRatio and L.PDCP.DL.ROCH.PktCompRatio.

If the value of L.PDCP.DL.RoHC.HdrCompRatio is 1, the ROHC function is disabled.

If the value of L.PDCP.DL.RoHC.PktCompRatio is 1, the ROHC function is disabled.

The ROHC function is applicable only to the compression and decompression of data on the user plane. Therefore, you can view the preceding performance counters only when the eNodeB is transmitting data over the user plane.

----End




Draft (2010–05–20)

2.31 Configuring S1-Flex 2.31.1 Enabling S1-Flex

Prerequisite The license for this feature has been activated. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.



NEs in the EPC The EPC supports MME resource pools, MME load rebalancing, and MME overload processing.

OSS None.

Context An S1 interface is set up based on an SCTP link. The status of the SCTP link must be

normal. Otherwise, the S1 Setup Request message is not sent over the S1 interface. To learn about the principles and rules for setting the parameters of this feature, see the

S1-Flex Feature Parameter Description and eNodeB MO reference.

Procedure Step 1 Run the MOD GLOBALPROCSWITCH command to enable the S1-Flex feature. In this

step, set the value of the S1FlexSwitch parameter to ON(on).

Step 2 Run the DSP S1INTERFACE command to query the information about the S1 interfaces that are already set up for the eNodeB. In this step, set the value of the S1InterfaceId parameter to null.

Step 3 Run the LST SCTPLNK command to check whether the SCTP link used by the added S1 interface is already configured. If this SCTP link is not configured yet, run the ADD SCTPLNK command to add it.

Step 4 Run the DSP SCTPLNK command to check whether the status of this SCTP link is normal.

Step 5 Run the ADD S1INTERFACE command to add an S1 interface for the current eNodeB.

Step 6 Run the DSP S1INTERFACE command to check whether the S1 interface is successfully added and whether its status is normal. In this step, set the value of the S1InterfaceId parameter to the ID of the added S1 interface.

Step 7 If more S1 interfaces need to be added, repeat Step 3 through Step 6 for each S1 interface to be added.



2-53

Step 8 Use a UE to access the network. Meanwhile, initiate message tracing on the LMT for S1 interfaces. If the UE can successfully attach to the network through an S1 interface and the traced messages corresponding to the UE are normal, the S1-Flex feature can be used normally.

----End

2.31.2 Disabling S1-Flex


Context The S1-Flex feature can be disabled only if the eNodeB has an S1-MME connection with

only one MME. To learn about the principles and rules for setting the parameters of this feature, see the

S1-Flex Feature Parameter Description and eNodeB MO reference.

Procedure Step 1 Run the DSP S1INTERFACE command to query the information about the S1 interfaces that

are already set up for the eNodeB. In this step, set the value of the S1InterfaceId parameter to null.

If the eNodeB is connected to only one MME, go to Step 6. If the eNodeB is connected to multiple MMEs, go to Step 2.

Step 2 Run the DSP S1INTERFACE command to check the status of the S1 interface to be removed. In this step, set the value of the S1InterfaceId parameter to the ID of the S1 interface to be removed.

If the status of the S1 interface is normal, go to Step 3. If the status of the S1 interface is abnormal, go to Step 5.

Step 3 Run the BLK S1INTERFACE command to block the S1 interface.

Step 4 Run the DSP S1INTERFACE command to query the number of users over the S1 interface. Ensure that this number is 0, which means all users served by the corresponding MME are released.

Step 5 Run the RMV S1INTERFACE command to remove the S1 interface, thereby removing the S1-MME connection between the eNodeB and the corresponding MME. Then, go to Step 1.

Step 6 Run the MOD GLOBALPROCSWITCH command to disable the S1-Flex feature. In this step, set the value of the S1FlexSwitch parameter to OFF(off).

----End




Draft (2010–05–20)

2.32 Configuring PS Inter-RAT Mobility Between E-UTRAN and UTRAN 2.32.1 Enabling PS Inter-RAT Mobility Between E-UTRAN and UTRAN

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of PS inter-RAT mobility between

E-UTRAN and UTRAN. In addition, the UTRAN meets the conditions of PS inter-RAT mobility between E-UTRAN and UTRAN. For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.



Item Requirement

UE The UE supports gap-assisted measurements and the UMTS system.




OSS None.



By default, the feature of PS inter-RAT mobility between E-UTRAN and UTRAN is enabled. Typically, no manual enabling is required.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable PS inter-RAT mobility

between LTE and UTRAN. In this step, select the UTRANHoSwitch(UTRANHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of UTRANHoSwitch is on.

----End



2-55

2.32.2 Disabling PS Inter-RAT Mobility Between E-UTRAN and UTRAN


Context Disabling this feature causes the system not to provide the service of PS inter-RAT mobility between E-UTRAN and UTRAN.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable PS inter-RAT mobility

between LTE and UTRAN. In this step, clear the UTRANHoSwitch(UTRANHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of UTRANHoSwitch is off.

----End

2.33 Configuring PS Inter-RAT Mobility Between E-UTRAN and GERAN 2.33.1 Enabling PS Inter-RAT Mobility Between E-UTRAN and GERAN


E-UTRAN and GERAN. In addition, the GERAN meets the conditions of PS inter-RAT mobility between E-UTRAN and GERAN. For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.



Item Requirement

UE The UE supports gap-assisted measurements and the GERAN system.

eNodeB

The version is eRAN1.0 or later.





Draft (2010–05–20)

Item Requirement


OSS None.



By default, the feature of PS inter-RAT mobility between E-UTRAN and GERAN is enabled. Typically, no manual enabling is required.


between LTE and GERAN. In this step, select the GERANHoSwitch(GERANHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of GERANHoSwitch is on.

----End

2.33.2 Disabling PS Inter-RAT Mobility Between E-UTRAN and GERAN


Context Disabling this feature causes the system not to provide the service of PS inter-RAT mobility between E-UTRAN and GERAN.


between LTE and GERAN. In this step, clear the GERANHoSwitch(GERANHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of GERANHoSwitch is off.

----End



2-57

2.34 Configuring PS Inter-RAT Mobility Between E-UTRAN and CDMA2000 2.34.1 Enabling PS Inter-RAT Mobility Between E-UTRAN and CDMA2000


E-UTRAN and CDMA2000. In addition, the CDMA2000 system meets the conditions of PS inter-RAT mobility between E-UTRAN and CDMA2000. For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.



Item Requirement

UE The UE supports gap-assisted measurements and the CDMA2000 system.




OSS None.



By default, the feature of PS inter-RAT mobility between E-UTRAN and CDMA2000 is enabled. Typically, no manual enabling is required.


between LTE and CDMA2000. In this step, select the CDMAHRPDHoSwitch(CDMAHRPDHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of CDMAHRPDHoSwitch is on.

----End




Draft (2010–05–20)

2.34.2 Disabling PS Inter-RAT Mobility Between E-UTRAN and CDMA2000


Context Disabling this feature causes the system not to provide the service of PS inter-RAT mobility between E-UTRAN and CDMA2000.


between LTE and CDMA2000. In this step, clear the CDMAHRPDHoSwitch(CDMAHRPDHoSwitch) check box under the HoAlgSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of CDMAHRPDHoSwitch is off.

----End

2.35 Configuring SRVCC to UTRAN 2.35.1 Enabling SRVCC to UTRAN

Prerequisite The license for this feature has been activated. You have familiarized yourself with SRVCC to UTRAN. In addition, the UMTS system

meets the conditions of SRVCC to UTRAN. For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.



Item Requirement





OSS None.



2-59



By default, the feature of SRVCC to UTRAN is enabled. Typically, no manual enabling is required.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable SRVCC to UTRAN. In this

step, select the UTRANSrvccSwitch(UTRANSrvccSwitch) check box under the SrvccAlgoSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of UTRANSrvccSwitch is on.

----End

2.35.2 Disabling SRVCC to UTRAN


Context Disabling this feature causes the system not to provide the service of SRVCC to UTRAN.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable SRVCC to UTRAN. In this

step, clear the UTRANSrvccSwitch(UTRANSrvccSwitch) check box under the SrvccAlgoSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of UTRANSrvccSwitch is off.

----End

2.36 Configuring SRVCC to GERAN 2.36.1 Enabling SRVCC to GERAN

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of SRVCC to GERAN. In addition, the

GERAN system meets the conditions of SRVCC to GERAN. For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.




Draft (2010–05–20)



Item Requirement





OSS None.



By default, the feature of SRVCC to GERAN is enabled. Typically, no manual enabling is required.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable SRVCC to GERAN. In this

step, select the GERANSrvccSwitch(GERANSrvccSwitch) check box under the SrvccAlgoSwitch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of GERANSrvccSwitch is on.

----End

2.36.2 Disabling SRVCC to GERAN


Context Disabling this feature causes the system not to provide the service of SRVCC to GERAN.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable SRVCC to GERAN. In this

step, clear the GERANSrvccSwitch(GERANSrvccSwitch) check box under the SrvccAlgoSwitch parameter.



2-61

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of GERANSrvccSwitch is off.

----End

2.37 Configuring Extended CP 2.37.1 Enabling Extended CP



Item Requirement

UE None.




OSS None.

Context Setting Uplink cyclic prefix length or Downlink cyclic prefix length to

EXTENDED_CP(Extended), which is performed when a cell is added, takes effect after the cell is activated.


Procedure Step 1 Run the ADD CELL command to add a cell. In this step, set the Uplink cyclic prefix length

or Downlink cyclic prefix length parameter to EXTENDED_CP(Extended).


Step 3 Run the LST CELL command to check the cell configuration. The result indicates that the value of Uplink cyclic prefix length or Downlink cyclic prefix length is Extended.

----End




Draft (2010–05–20)

2.37.2 Disabling Extended CP


Context When a cell is modified, the Uplink cyclic prefix length or Downlink cyclic prefix

length parameter can be set to NORMAL_CP(Normal) for the cell. The configuration takes effect after the cell is activated.


Procedure Step 1 Run the DEA CELL command to deactivate a cell.

Step 2 Run the MOD CELL command to modify the cell. In this step, set the Uplink cyclic prefix length or Downlink cyclic prefix length parameter to NORMAL_CP(Normal).


Step 4 Run the LST CELL command to check the cell configuration. The result indicates that the value of Uplink cyclic prefix length or Downlink cyclic prefix length is Normal.

----End

2.38 Configuring Intra-LTE Load Balancing 2.38.1 Enabling Intra-LTE Load Balancing




Item Requirement

UE None.




OSS None.



2-63


Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable intra-LTE load balancing.

To enable intra-frequency load balancing, select the IntraFreqMlbThd(Intra-Frequency Load Balance) check box under the Load Balancing Algorithm Switch parameter.

To enable inter-frequency load balancing, select the InterFreqMlbThd(Inter-Frequency Load Balance) check box under the Load Balancing Algorithm Switch parameter.

Step 2 Run the LST CELLALGOSWITCH command.

If the value of Intra-Frequency Load Balance is On, it is an indication that intra-frequency load balancing is enabled.

If the value of Inter-Frequency Load Balance is On, it is an indication that inter-frequency load balancing is enabled.

----End

2.38.2 Disabling Intra-LTE Load Balancing


Context If intra-frequency load balancing is disabled, load transfer to an intra-frequency cell is

not performed before the load in a cell reaches the congestion control threshold. If inter-frequency load balancing is disabled, load transfer to an inter-frequency cell is

not performed before the load in a cell reaches the congestion control threshold.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable intra-LTE load balancing.

To disable intra-frequency load balancing, clear the IntraFreqMlbThd(Intra-Frequency Load Balance) check box under the Load Balancing Algorithm Switch parameter.

To disable inter-frequency load balancing, clear the InterFreqMlbThd(Inter-Frequency Load Balance) check box under the Load Balancing Algorithm Switch parameter.

Step 2 Run the LST CELLALGOSWITCH command.

If the value of Intra-Frequency Load Balance is Off, it is an indication that intra-frequency load balancing is disabled.




Draft (2010–05–20)

If the value of Inter-Frequency Load Balance is Off, it is an indication that inter-frequency load balancing is disabled.

----End

2.39 Configuring Inter-RAT Load Sharing to UTRAN 2.39.1 Enabling Inter-RAT Load Sharing to UTRAN




Item Requirement

UE None.




OSS None.


Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable inter-RAT load sharing. In this

step, select the InterRatMlbSwitch(Inter-RAT Load Balance) check box under the Load Balancing Algorithm Switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of Inter-RAT Load Balance is On.

----End

2.39.2 Disabling Inter-RAT Load Sharing to UTRAN




2-65

Context If inter-RAT load balancing is disabled, load transfer to an inter-RAT cell is not performed before the load in an LTE cell reaches the congestion control threshold.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable inter-RAT load sharing. In this

step, clear the InterRatMlbSwitch(Inter-RAT Load Balance) check box under the Load Balancing Algorithm Switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of Inter-RAT Load Balance is Off.

----End

2.40 Configuring Inter-RAT Load Sharing to GERAN 2.40.1 Enabling Inter-RAT Load Sharing to GERAN




Item Requirement

UE None.




OSS None.


Procedure Step 1 Run the MOD CELLALGOSWITCH command to enable inter-RAT load sharing. In this

step, select the InterRatMlbSwitch(Inter-RAT Load Balance) check box under the Load Balancing Algorithm Switch parameter.




Draft (2010–05–20)

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of Inter-RAT Load Balance is On.

----End

2.40.2 Disabling Inter-RAT Load Sharing to GERAN


Context If inter-RAT load balancing is disabled, load transfer to an inter-RAT cell is not performed before the load in an LTE cell reaches the congestion control threshold.

Procedure Step 1 Run the MOD CELLALGOSWITCH command to disable inter-RAT load sharing. In this

step, clear the InterRatMlbSwitch(Inter-RAT Load Balance) check box under the Load Balancing Algorithm Switch parameter.

Step 2 Run the LST CELLALGOSWITCH command to check the switch setting. The result indicates that the value of Inter-RAT Load Balance is Off.

----End

2.41 Configuring Service Based Inter-RAT Handover to UTRAN 2.41.1 Enabling Service Based Inter-RAT Handover to UTRAN

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of service-based inter-RAT handover to

UTRAN. For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.



Item Requirement






2-67

Item Requirement


OSS None.



By default, the feature of service-based inter-RAT handover to UTRAN is enabled. Typically, no manual enabling is required.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable service-based inter-RAT

handover to UTRAN. In this step, select the UTRAN_SWITCH check box under the Service Base HandOver Switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of UTRAN_SWITCH is on.

----End

2.41.2 Disabling Service Based Inter-RAT Handover to UTRAN


Context Disabling this feature causes the system not to provide the service of service-based inter-RAT handover to UTRAN.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable service-based inter-RAT

handover to UTRAN. In this step, clear the UTRAN_SWITCH check box under the Service Base HandOver Switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of UTRAN_SWITCH is off.

----End




Draft (2010–05–20)

2.42 Configuring Service Based Inter-RAT Handover to GERAN 2.42.1 Enabling Service Based Inter-RAT Handover to GERAN

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of service-based inter-RAT handover to

GERAN. For details about the feature, see the Mobility Management in Connected Mode Feature Parameter Description.



Item Requirement





OSS None.



By default, the feature of service-based inter-RAT handover to GERAN is enabled. Typically, no manual enabling is required.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable service-based inter-RAT

handover to GERAN. In this step, select the GERAN_SWITCH check box under the Service Base HandOver Switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of GERAN_SWITCH is on.

----End



2-69

2.42.2 Disabling Service Based Inter-RAT Handover to GERAN


Context Disabling this feature causes the system not to provide the service of service-based inter-RAT handover to GERAN.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable service-based inter-RAT

handover to GERAN. In this step, clear the GERAN_SWITCH check box under the Service Base HandOver Switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of GERAN_SWITCH is off.

----End

2.43 Configuring CS Fall Back to UTRAN 2.43.1 Enabling CS Fall Back to UTRAN



Item Requirement





OSS None.




Draft (2010–05–20)

Context If CS fallback to UTRAN is implemented by means of PS handover, the related switch

under the HoAlgSwitch parameter needs to be turned on. If CS fallback is implemented by means of redirection, parameter setting is not required.

To learn about the principles and rules for setting the parameters of this feature, see the CS Fallback Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 If CS fallback to UTRAN is implemented by means of PS handover, run the MOD

ENODEBALGOSWITCH command to enable PS handover. In this step, select the UTRANHoSwitch(UTRAN HoSwitch) check box under the HoAlgSwitch parameter. If CS fallback to UTRAN is not implemented by means of PS handover, go to Step 2.

Step 2 Run the MOD ENODEBALGOSWITCH command to enable CS fallback to UTRAN. In this step, select the UTRAN_FALLBACK_SWITCH check box under the CS FallBack Switch parameter.

If the eNodeB is configured to provide blind handovers, go to Step 3. If the eNodeB is configured to manage measurement-based handovers, go to Step 5.

Step 3 Run the MOD ENODEBALGOSWITCH command to enable blind handover. In this step, set Blind HandOver Switch to ON.

Step 4 Run the MOD CSFBBLIND command to set the priorities of blind handovers to different RATs. In this step, set the following parameters: Highest PRI InterRat, SECONDPRIRAT, and LOWESTPRIRAT.

Step 5 Make a voice call by using a UE. If the voice service is running normally, it is an indication that CS fallback is enabled.

----End

2.43.2 Disabling CS Fall Back to UTRAN


Context To learn about the principles and rules for setting the parameters of this feature, see the CS Fallback Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable CS fallback to UTRAN. In

this step, clear the UTRAN_FALLBACK_SWITCH check box under the CS FallBack Switch parameter.



2-71

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of UTRAN_FALLBACK_SWITCH is Off.

----End

2.44 Configuring CS Fall Back to GERAN 2.44.1 Enabling CS Fall Back to GERAN



Item Requirement





OSS None.

Context If CS fallback to GERAN is implemented by means of PS handover or CCO/NACC, the

related switch under the HoAlgSwitch parameter needs to be turned on. If CS fallback is implemented by means of redirection, parameter setting is not required.

To learn about the principles and rules for setting the parameters of this feature, see the CS Fallback Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 If CS fallback to GERAN is implemented by means of PS handover, CCO, or NACC, run the

MOD ENODEBALGOSWITCH command to enable PS handover, CCO, or NACC respectively. Otherwise, go to Step 2.

To enable PS handover, select the GERANHoSwitch(GERANHoSwitch) check box under the HoAlgSwitch parameter.

To enable CCO, select the GERANNotNACCSwitch(GERANNotNACCSwitch) check box under the HoAlgSwitch parameter.

To enable NACC, select the GERANNACCSwitch(GERANNACCSwitch) check box under the HoAlgSwitch parameter.




Draft (2010–05–20)

Step 2 Run the MOD ENODEBALGOSWITCH command to enable CS fallback to GERAN. In this step, select the GERAN_FALLBACK_SWITCH check box under the CS FallBack Switch parameter.





----End

2.44.2 Disabling CS Fall Back to GERAN



Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable CS fallback to GERAN. In

this step, clear the GERAN_FALLBACK_SWITCH check box under the CS FallBack Switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of GERAN_FALLBACK_SWITCH is Off.

----End

2.45 Configuring CS Fall Back to CDMA2000 1xRTT 2.45.1 Enabling CS Fall Back to CDMA2000 1x RTT





2-73

Item Requirement

UE The UE supports gap-assisted measurements and the CDMA2000 1xRTT system.




OSS None.


Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to enable CS fallback to CDMA2000

1xRTT. In this step, select the CDMA_1XRTT_FALLBACK_SWITCH check box under the CS FallBack Switch parameter.





----End

2.45.2 Disabling CS Fall Back to 1x RTT






Draft (2010–05–20)

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command to disable CS fallback to CDMA2000

1xRTT. In this step, clear the CDMA_1XRTT_FALLBACK_SWITCH check box under the CS FallBack Switch parameter.

Step 2 Run the LST ENODEBALGOSWITCH command to check the switch setting. The result indicates that the value of CDMA_1XRTT_FALLBACK_SWITCH is Off.

----End

2.46 Configuring RAN Sharing with Common Carrier 2.46.1 Enabling RAN Sharing with Common Carrier

Prerequisite You have familiarized yourself with the feature of eRAN sharing with common carrier.

For details about the feature, see the eRAN Sharing Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly. The license for this feature has been activated. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE The UE can read more than one PLMN ID at a time.



NEs in the EPC The EPCs of the operators are separated. The operators share TACs but use different MMECs.

OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the eRAN Sharing Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD ENODEBSHAREMODE command to enable eRAN sharing with common

carrier. In this step, set eNodeBShareMode to SHARED_FREQ(Shared Frequency Sharing Mode).

In addition to the setting of the eNodeB sharing mode, eRAN sharing with common carrier requires setting of the following information: operators, TAs, S1 interfaces, cells, and license sharing policies.



2-75

Step 2 Run the LST ENODEBSHAREMODE command to check the eNodeB sharing mode. The result indicates that the value of eNodeBShareMode is Shared Frequency Sharing Mode.

----End

2.46.2 Disabling RAN Sharing with Common Carrier


properly. The information about license sharing policies, cells, S1 interfaces, TAs, and operators

has been removed from the eNodeB in sequence.

Context Disabling the feature of eRAN sharing with common carrier disrupts all services of the operators, and therefore an agreement must be reached between the operators before this feature is disabled.

Procedure Step 1 Run the MOD ENODEBSHAREMODE command to disable eRAN sharing with common

carrier. In this step, set eNodeBShareMode to INDEPENDENT(Independent Operator Mode).

Step 2 Run the LST ENODEBSHAREMODE command to check the eNodeB sharing mode. The result indicates that the value of eNodeBShareMode is Independent Operator Mode.

----End

2.47 Configuring RAN Sharing with Dedicated Carrier 2.47.1 Enabling RAN Sharing with Dedicated Carrier

Prerequisite You have familiarized yourself with the feature of eRAN sharing with dedicated carrier.

For details about the feature, see the eRAN Sharing Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly. The license for this feature has been activated. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.






Draft (2010–05–20)

Item Requirement

NEs in the EPC The EPCs of the operators are separated. The operators share TACs but use different MMECs.

OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the eRAN Sharing Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD ENODEBSHAREMODE command to enable eRAN sharing with dedicated

carrier. In this step, set eNodeBShareMode to SEPARATED_FREQ(Separate Frequency Sharing Mode).

In addition to the setting of the eNodeB sharing mode, eRAN sharing with dedicated carrier requires setting of the following information: operators, TAs, S1 interfaces, cells, PLMNs that cells belong to, and license sharing policies.

Step 2 Run the LST ENODEBSHAREMODE command to check the eNodeB sharing mode. The result indicates that the value of eNodeBShareMode is Separate Frequency Sharing Mode.

----End

2.47.2 Disabling RAN Sharing with Dedicated Carrier


properly. The information about license sharing policies, PLMNs that cells belong to, cells, S1

interfaces, TAs, and operators has been removed from the eNodeB in sequence.

Context Disabling the feature of eRAN sharing with dedicated carrier disrupts all services of the operators, and therefore an agreement must be reached between the operators before this feature is disabled.

Procedure Step 1 Run the MOD ENODEBSHAREMODE command to disable eRAN sharing with dedicated

carrier. In this step, set eNodeBShareMode to INDEPENDENT(Independent Operator Mode).

Step 2 Run the LST ENODEBSHAREMODE command to check the eNodeB sharing mode. The result indicates that the value of eNodeBShareMode is Independent Operator Mode.

----End



2-77

2.48 Configuring RRU Channel Cross Connection Under MIMO 2.48.1 Enabling RRU Channel Cross Connection Under MIMO

Prerequisite The license for this feature has been activated. You have familiarized yourself with the principles of RRU channel cross-connection

under MIMO. For details about the feature, see the eNodeB Technical Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.




OSS None.

Context The feature of RRU channel cross-connection under MIMO is applicable only to the

sectors whose Antenna mode is set to 2T2R. This feature is applicable only when the LRRUs or LRFUs corresponding to the sectors

are connected to CPRI ports 0 to 2 on one LBBP in a star topology. Before this feature is enabled, the LRRUs or LRFUs must be cross-connected to the

antennas through RF cables, as shown in Figure 2-3.




Draft (2010–05–20)

Figure 2-3 RF cable connections for RRU channel cross-connection under MIMO

LRRU 0

Antenna 0

LRRU 1 LRRU 2

LBBP

CPRI 0 CPRI 1 CPRI 2

Antenna 1 Antenna 2

Sector 0 Sector 1 Sector 2

R0A R0B R0A R0B R0A R0B

Procedure Step 1 Run the DEA CELL command to deactivate the cells in the related sectors.

Step 2 Run the RMV CELL command to remove the cells.

Step 3 Run the RMV SECTOR command to remove the related sectors.

If the LRRUs or LRFUs are not connected directly to CPRI ports 0, 1, and 2 on the LBBP, you must remove the indirectly connected LRRUs or LRFUs and the associated data configuration, including the RET antennas and TMAs. This procedure describes the operations performed in the situation that the LRRUs or LRFUs are connected directly to CPRI ports 0, 1, and 2 on the LBBP.

Step 4 Re-connect the LRRUs or LRFUs to the antennas so that they are cross-connected, as shown in Figure 2-3.

Step 5 Run the ADD SECTOR command to add sectors. In this step, set Sector Mode to AIDMIMO(mutual-aid MIMO). Adhere to the following constraints:

The two antenna ports for one sector must be located on different LRRUs or LRFUs. The mapping between the sectors and the antenna ports must be the same as that shown

in Figure 2-3. For example, sector 0 uses port R0A on RRU 0 and port R0B on RRU 1.

Step 6 Run the ADD CELL command to add cells.

Step 7 Run the ACT CELL command to activate the cells.



2-79

Step 8 Run the DSP CELL command to check the cell information. If the value of CELL TOPO TYPE is MIMO Help Mode Type, it is an indication that the feature of RRU channel cross-connection under MIMO is enabled.

----End

2.48.2 Disabling RRU Channel Cross Connection Under MIMO


Context Before the feature of RRU channel cross-connection under MIMO is disabled, the LRRUs or LRFUs must be connected to the antennas in a one-to-one manner through RF cables. Figure 2-4 shows the one-to-one connections that are changed from the cross-connections shown in Figure 2-3.

Figure 2-4 RF cable connections in ordinary situations

LRRU 0

Antenna 0

LRRU 1 LRRU 2

LBBP

CPRI 0 CPRI 1 CPRI 2

Antenna 1 Antenna 2

Sector 0 Sector 1 Sector 2

R0A R0B R0A R0B R0A R0B




Draft (2010–05–20)

Procedure Step 1 Run the DEA CELL command to deactivate the cells in the related sectors.

Step 2 Run the RMV CELL command to remove the cells.

Step 3 Run the RMV SECTOR command to remove the related sectors.

Step 4 Connect the LRRUs or LRFUs to the antennas in a one-to-one manner, as shown in Figure 2-4.

Step 5 Run the ADD SECTOR command to add sectors. In this step, set Sector Mode to NormalMIMO(Normal MIMO).

Step 6 Run the ADD CELL command to add cells.

Step 7 Run the ACT CELL command to activate the cells.

Step 8 Run the DSP CELL command to check the cell configuration. If the value of CELL TOPO TYPE is Invalid Type, it is an indication that the feature of RRU channel cross-connection under MIMO is disabled.

----End

2.49 Configuring Adaptive Power Consumption 2.49.1 Enabling Adaptive Power Consumption



Item Requirement



UE None.

Context The adaptive power consumption feature has the following two functions:

Dynamic voltage adjustment Based on the output power from the power amplifier, the eNodeB dynamically adjusts the work status of the power amplifier. In this way, the power amplifier efficiency is optimized, and the power consumption of the eNodeB is reduced.

Scheduled power-on and power-off The eNodeB is automatically powered on and powered off at scheduled times. In this way, power consumption is reduced.



2-81

Procedure To enable dynamic voltage adjustment, perform the following steps:

Step 1 Run the MOD CELLALGOSWITCH command. In this step, select the DynAdjVoltSwitch(DynAdjVoltSwitch) check box under the DynAdjVoltSwitch parameter.

Step 2 Run the LST CELLALGOSWITCH command. If the value of the DynAdjVoltSwitch parameter is On, the function has been enabled.

----End

To enable scheduled power-on and power-off, perform the following steps:

Step 1 Run the MOD ENODEB command. In this step, set the value of the AUTOPOWEROFFSWITCH parameter to On and set the POWERONTIME and POWEROFFTIME parameters to appropriate values.

Step 2 Run the LST ENODEB command. If the value of the Auto power control switch parameter is ON, the function has been enabled.

----End

2.49.2 Disabling Adaptive Power Consumption


Context Disabling dynamic voltage adjustment prevents the system from reducing the power

consumption of the power amplifier. After the scheduled power-on and power-off function is disabled, the system is always

powered on unless powered off manually.

Procedure To disable dynamic voltage adjustment, perform the following steps:

Step 1 Run the MOD CELLALGOSWITCH command. In this step, clear the DynAdjVoltSwitch(DynAdjVoltSwitch) check box under the DynAdjVoltSwitch parameter.

Step 2 Run the LST CELLALGOSWITCH command. If the value of the DynAdjVoltSwitch parameter is Off, the function has been disabled.

----End

To disable scheduled power-on and power-off, perform the following steps:

Step 1 Run the MOD ENODEB command. In this step, set the value of the AUTOPOWEROFFSWITCH parameter to Off.




Draft (2010–05–20)

Step 2 Run the LST ENODEB command. If the value of the Auto power control switch parameter is OFF, the function has been disabled.

----End

2.50 Configuring RF Channel Intelligent Shutdown 2.50.1 Enabling RF Channel Intelligent Shutdown



Item Requirement

UE None.




OSS None.

Context To learn about the principles and rules for setting the parameters of this feature, see the Energy Conservation and Emission Reduction Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD CELLRFSHDINFO command to enable RF channel intelligent shutdown. In

this step, set RF intelligent shutdown switch to ON(On), and then set RF intelligent shutdown start time, RF intelligent shutdown stop time, and Signal power delta(dB).

Step 2 Run the LST CELLRFSHDINFO command. If the value of RF intelligent shutdown switch is On, it is an indication that RF channel intelligent shutdown is enabled.

----End

2.50.2 Disabling RF Channel Intelligent Shutdown




2-83

Context If RF channel intelligent shutdown is disabled, the eNodeB transmits signals on all channels even if there is no user in some cells. This is a waste of energy.

Procedure Step 1 Run the MOD CELLRFSHDINFO command to disable RF channel intelligent shutdown. In

this step, set RF intelligent shutdown switch to OFF(Off).

Step 2 Run the LST CELLRFSHDINFO command. If the value of RF intelligent shutdown switch is Off, it is an indication that RF channel intelligent shutdown is disabled.

----End

2.51 Configuring Low Power Consumption Mode 2.51.1 Enabling Low Power Consumption Mode


properly. The cell is not in the states of RF channel intelligent shutdown or intelligent Power-Off

of Carriers in the Same Coverage. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.




OSS None.


Procedure Step 1 Run the MOD CELLLOWPOWERINFO command to enable the low power consumption

mode. In this step, set Low power consumption mode switch to ON(On), and then set the following parameters: Bandwidth limit timer(min), Power reduce timer(min), RF




Draft (2010–05–20)

shutdown timer(min), Signal power reduce delta(dB), and Usable service power reduce percent(%).

Step 2 Run the LST CELLLOWPOWERINFO command. If the value of Low power consumption mode switch is On, it is an indication that the low power consumption mode is enabled.

----End

2.51.2 Disabling Low Power Consumption Mode


Context If the low power consumption mode is disabled, the cell does not enter the low power consumption mode when a board hardware fault alarm is reported because of the low voltage. In this case, services may be disrupted.

Procedure Step 1 Run the MOD CELLLOWPOWERINFO command to disable the low power consumption

mode. In this step, set Low power consumption mode switch to OFF(Off).

Step 2 Run the LST CELLLOWPOWERINFO command. If the value of Low power consumption mode switch is Off, it is an indication that the low power consumption mode is disabled.

----End

2.52 Configuring Intelligent Power-Off of Carriers in the Same Coverage 2.52.1 Enabling Intelligent Power-Off of Carriers in the Same Coverage


properly. A neighboring frequency of the carrier to be shut down has been configured in the same

eNodeB. Inter-frequency neighboring relations have been configured in the cells on the carrier to

be shut down, and the blind handover priorities of the inter-frequency cells are greater than 0.



2-85


Item Requirement

UE None.




OSS None.


Procedure Step 1 Run the MOD CELLDBSHDINFO command to enable intelligent power-off of carriers in

the same coverage. In this step, set Dual-band intelligent shutdown switch to ON(On), and then set the following parameters: Dual-band intelligent shutdown start time, Dual-band intelligent shutdown stop time, DL PRB close threshold(%), DL PRB open threshold delta(%), UL PRB close threshold(%), and UL PRB open threshold delta(%).

Step 2 Run the LST CELLDBSHDINFO command. If the value of Dual-band intelligent shutdown switch is On, it is an indication that intelligent power-off of carriers in the same coverage is enabled.

----End

2.52.2 Disabling Intelligent Power-Off of Carriers in the Same Coverage


Context If intelligent power-off of carriers in the same coverage is disabled, the eNodeB retains the few users on a carrier. It does not shut down the carrier with few users or divert the users to another carrier. This is a waste of energy.

Procedure Step 1 Run the MOD CELLDBSHDINFO command to disable intelligent power-off of carriers in

the same coverage. In this step, set Dual-band intelligent shutdown switch to OFF(Off).




Draft (2010–05–20)

Step 2 Run the LST CELLDBSHDINFO command. If the value of Dual-band intelligent shutdown switch is Off, it is an indication that intelligent power-off of carriers in the same coverage is disabled.

----End

2.53 Configuring ANR 2.53.1 Enabling ANR

Prerequisite The license for the ANR feature has been activated. You have familiarized yourself with the ANR feature. For details, see the ANR

Management Feature Parameter Description. The list of the E-UTRAN Absolute Frequency Channel Numbers (EARFCNs) of

inter-frequency neighboring cells has been configured for a serving cell. You have logged in to the eNodeB LMT or M2000 client, and the LMT or M2000 client

communicates with the eNodeB properly. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement



UE None.


OSS None.


ANR Management Feature Parameter Description and eNodeB MO Reference. Activating the ANR algorithm involves enabling PCI collision detection and evaluating

abnormal neighboring cells.

Procedure Step 1 Run the MOD ENODEBALGOSWITCH command and set the SON ANR algorithm

switch parameter. If the IntraRatEventAnrSwitch check box is selected, it indicates that the intra-RAT ANR is activated. If the IntraRatFastAnrSwitch check box is selected, it indicates that the intra-RAT fast ANR is activated.

Step 2 Run the LST ENODEBALGOSWITCH command. If the intra-RAT ANR is activated, the IntraRatEventAnrSwitch parameter is set to On. If the intra-RAT fast ANR is activated, the IntraRatFastAnrSwitch parameter is set to On.

----End



2-87

2.53.2 Disabling ANR

Prerequisite You have logged in to the eNodeB LMT or M2000 client, and the LMT or M2000 client communicates with the eNodeB properly.

Context After ANR is disabled, the system cannot provide automatic management of neighbor relations.


switch parameter. If the IntraRatEventAnrSwitch check box is cleared, it indicates that the intra-RAT ANR is deactivated. If the IntraRatFastAnrSwitch check box is cleared, it indicates that the intra-RAT fast ANR is deactivated.

Step 2 Run the LST ENODEBALGOSWITCH command. If the intra-RAT ANR is deactivated, the IntraRatEventAnrSwitch parameter is set to Off. If the intra-RAT fast ANR is deactivated, the IntraRatFastAnrSwitch parameter is set to Off.

----End

2.54 Configuring Inter-RAT ANR 2.54.1 Enabling Inter-RAT ANR

Prerequisite The license for the ANR feature has been activated. You have familiarized yourself with the ANR feature. For details, see the ANR

Management Feature Parameter Description. The list of the inter-RAT Absolute Frequency Channel Numbers (EARFCNs) of

inter-frequency neighboring cells has been configured for a serving cell. You have logged in to the eNodeB LMT or M2000 client, and the LMT or M2000 client

communicates with the eNodeB properly. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement



UE None.


OSS None.




Draft (2010–05–20)

Context To learn about the principles and rules for setting the parameters of this feature, see the ANR Management Feature Parameter Description and eNodeB MO Reference.


switch parameter. If the InterRatEventAnrSwitch check box is selected, it indicates that the inter-RAT ANR is activated. If the InterRatAnrAutoDelSwitch check box is selected, it indicates that the inter-RAT fast ANR is activated.

Step 2 Run the LST ENODEBALGOSWITCH command. If the inter-RAT ANR is activated, the InterRatEventAnrSwitch parameter is set to On. If the inter-RAT fast ANR is activated, the InterRatAnrAutoDelSwitch parameter is set to On.

----End

2.54.2 Disabling Inter-RAT ANR


Context After inter-RAT ANR is disabled, the system cannot provide automatic management of inter-RAT neighbor relations.


switch parameter. If the InterRatEventAnrSwitch check box is cleared, it indicates that the inter-RAT ANR is deactivated. If the InterRatAnrAutoDelSwitch check box is cleared, it indicates that the inter-RAT fast ANR is deactivated.

Step 2 Run the LST ENODEBALGOSWITCH command. If the inter-RAT ANR is deactivated, the InterRatEventAnrSwitch parameter is set to Off. If the inter-RAT fast ANR is deactivated, the InterRatAnrAutoDelSwitch parameter is set to Off.

----End

2.55 Configuring PCI Collision Detection 2.55.1 Enabling PCI Collision Detection

Prerequisite The license for the ANR feature has been activated. The ANR algorithm for the feature has been activated.



2-89

You have familiarized yourself with the ANR feature. For details, see the ANR Management Feature Parameter Description.

You have logged in to the M2000 client, and the LMT or M2000 client communicates with the eNodeB properly.


Item Requirement



UE None.


OSS None.


ANR Management Feature Parameter Description and eNodeB MO Reference. The ANR feature is enabled after the intra-RAT ANR is activated.

Procedure Step 1 On the M2000 client, choose Configuration > LTE Optimization.

Step 2 Click the Optimization tab. On the displayed Optimization tab page, choose Optimization Tasks > PCI Optimization Task.

Step 3 On the displayed PCI Optimization Task tab page, click on the right of PCI Collision Information to refresh the information.

----End

2.55.2 Disabling PCI Collision Detection


Context After ANR is disabled, PCI collision detection is directly disabled.

Procedure Deactivate the ANR algorithm by referring to section 2.53.2 "Disabling ANR."




Draft (2010–05–20)

2.56 Configuring Ethernet OAM (IEEE 802.3ah) 2.56.1 Enabling Ethernet OAM (IEEE 802.3ah)

Prerequisite Ethernet ports are used. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly. The requirements of the feature have been fulfilled. When the Ethernet OAM (IEEE

802.3ah) function is used, the peer device must support this function. The following table lists the requirements of the feature.

Item Requirement

Transport network Ethernet OAM (IEEE 802.3ah) is supported.

Peer device Ethernet OAM (IEEE 802.3ah) is supported.

eNodeB Hardware requirement: Ethernet ports are used. Software requirement: The version is eRAN1.0 or later.

Context IEEE 802.3ah provides the following four functions: automatic discovery, link

monitoring, fault finding, and remote loopback. IEEE 802.3ah defines two working modes: Active and Passive. If the Active mode is

used, the local end automatically initiates the negotiation. If the Passive mode is used, the local end waits for the negotiation packet from the peer end rather than automatically initiating the negotiation. The working modes of both ends of a point-to-point link cannot be set to Passive mode at the same time.

If the remote loopback function defined in IEEE 802.3ah is used, services may be interrupted.


Procedure To enable the automatic discovery, link monitoring, and fault detection functions in Ethernet OAM (IEEE 802.3ah), perform the following steps:

Step 1 Run the ACT ETHOAM3AH command. In this step, specify Slot No., Port Type, Port No., and Working Mode according to the negotiation mode.

Step 2 Run the LST ETHOAM3AH command to list the configuration of Ethernet OAM (IEEE 802.3ah). Check the configuration status in the result displayed on the eNodeB LMT.

Step 3 Run the DSP ETHOAM3AH command to list the dynamic attributes of Ethernet OAM (IEEE 802.3ah). Check the dynamic attributes of Ethernet OAM (IEEE 802.3ah) in the result displayed on the eNodeB LMT.

----End



2-91

To enable the remote loopback function defined in Ethernet OAM (IEEE 802.3ah), proceed with the following steps:

Step 1 Run the STR ETHOAMLOOPTST command to start the Ethernet OAM (IEEE 802.3ah) loopback.

Step 2 Run the DSP ETHOAM3AH command to list the dynamic attributes of Ethernet OAM (IEEE 802.3ah). Check the dynamic attributes of Ethernet OAM (IEEE 802.3ah) in the result displayed on the eNodeB LMT.

Step 3 Run the STP ETHOAMLOOPTST command to stop the Ethernet OAM (IEEE 802.3ah) loopback.

After the execution of STR ETHOAMLOOPTST, the loopback automatically ends. You can also run STP ETHOAMLOOPTST to end the loopback.

----End

2.56.2 Disabling Ethernet OAM (IEEE 802.3ah)


Context After the Ethernet OAM (IEEE 802.3ah) function is disabled, the system cannot monitor the link status effectively.

Procedure Step 1 Run the DEA ETHOAM3AH command to disable the Ethernet OAM (IEEE 802.3ah)

function. In this step, specify Slot No., Port Type, and Port No..

Step 2 Run the LST ETHOAM3AH command. If the values of Slot No., Port Type, and Port No. for which the Ethernet OAM (IEEE 802.3ah) function needs to be disabled are not displayed in the result, you can infer that the Ethernet OAM (IEEE 802.3ah) function is disabled.

----End

2.57 Configuring Ethernet OAM (IEEE 802.1ag) 2.57.1 Enabling Ethernet OAM (IEEE 802.1ag)

Prerequisite Ethernet ports are used. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly.




Draft (2010–05–20)

The requirements of the feature have been fulfilled. When the Ethernet OAM (IEEE 802.1ag) function is used, the peer device must support this function. The following table lists the requirements of the feature.

Item Requirement

Transport network Ethernet OAM (IEEE 802.1ag) is supported.

Peer device Ethernet OAM (IEEE 802.1ag) is supported.

eNodeB Hardware requirement: Ethernet ports are used. Software requirement: The version is eRAN1.1.

Context To enable the Ethernet OAM (IEEE 802.1ag) function, the Maintenance Domain (MD),

Maintenance Association (MA), and Maintenance End Points (MEPs) need to be configured.

Ethernet OAM (IEEE 802.1ag) provides three functions: Connectivity Check (CC), loopback, and linktrace.


Procedure Step 1 Run the ADD CFMMD command to configure the MD. In this step, specify MD Name.

Step 2 Run the ADD CFMMA command to configure the MA. In this step, specify MD Name, MA Name, Slot No., and VLAN ID.

Step 3 Run the ADD CFMMEP command to configure the local MEP. In this step, specify MD Name, MA Name, Slot No., and Port No..

Step 4 Run the LST CFMMEP command to check the configuration of the local MEP.

Step 5 Run the ADD CFMRMEP command. In this step, specify MD Name, MA Name, RMEP ID, and MAC Address of the remote MEP (RMEP).

Step 6 Run the LST CFMRMEP command to check the configuration of the RMEP.

Step 7 Run the DSP CFMRMEP command to check the status of the RMEP.

If... Then...

Connectivity Fault Management (CFM) CC needs to be enabled

a. Run the ACT CFMCC command. In this step, specify MD Name, MA Name, and MEP ID.

b. Run the DEA CFMCC command. In this step, specify MD Name, MA Name, and MEP ID.

c. Run the LST CFMMEP command. If CC Status of the MEP is Disable, you can infer that CFM CC is disabled.

CFM loopback needs to be enabled

a. Run the CFMPING command to start CFM loopback. b. Run the STP command to stop CFM loopback.



2-93

If... Then...

CFM linktrace needs to be enabled

a. Run the CFMTRACE command to start CFM linktrace. b. Run the STP command to stop CFM linktrace. c. Run the DSP CFMMEP command to check the system

running status after the function is enabled.

----End

2.57.2 Disabling Ethernet OAM (IEEE 802.1ag)


Context After Ethernet OAM (IEEE 802.1ag) is disabled, the system cannot provide the end-to-end maintenance of the Ethernet link.

Procedure Step 1 Run the RMV CFMRMEP command. In this step, specify MD Name, MA Name, and

RMEP ID.

Step 2 Run the LST CFMRMEP command. If MD Name, MA Name, and RMEP ID are not displayed in the result, you can infer that the RMEP is removed.

Step 3 Run the RMV CFMMEP command. In this step, specify MD Name, MA Name, and MEP ID.

Step 4 Run the LST CFMMEP command. If MD Name, MA Name, and MEP ID are not displayed in the result, you can infer that the local MEP is removed.

Step 5 Run the RMV CFMMA command. In this step, specify MD Name and MA Name.

Step 6 Run the LST CFMMA command. If MA Name is not displayed in the result, you can infer that the MA is removed.

Step 7 Run the RMV CFMMD command. In this step, specify MD Name.

Step 8 Run the LST CFMMD command. If MD Name is not displayed in the result, you can infer that the Ethernet OAM (IEEE 802.1ag) functions are disabled.

----End




Draft (2010–05–20)

2.58 Configuring Bidirectional Forwarding Detection 2.58.1 Enabling Bidirectional Forwarding Detection

Prerequisite You have familiarized yourself with the Bidirectional Forwarding Detection (BFD)

feature. For details, see the Transport Management Feature Parameter Description and eNodeB MO Reference.


The requirements of the feature have been fulfilled. When BFD is used to detect IP route faults, the peer device must support BFD. The following table lists the requirements of the feature.

Item Requirement

Transport network

None.

Peer device BFD is supported.

eNodeB Hardware requirement: Ethernet ports are used. Software requirement: The version is eRAN1.1.

Context When a new BFD session is added to the eNodeB, the source IP address or the

destination IP address cannot be the same as that of any existing BFD session. When the BFD session is configured, the hop type of the BFD session must be specified.

Single-hop BFD sessions are used for point-to-point detection, and multi-hop BFD sessions are used for end-to-end connectivity detection.


Procedure Step 1 Run the ADD BFDSESSION command to enable the BFD function. In this step, specify Slot

No., Session ID, Source IP, Destination IP, and Hop Type.

Step 2 Run the DSP BFDSESSION command. If the displayed result shows that the status of the BFD session is normal, you can infer that the BFD function is enabled.

----End

2.58.2 Disabling Bidirectional Forwarding Detection




2-95

Context After BFD is disabled, the system cannot provide the BFD function.

Procedure Step 1 Run the RMV BFDSESSION command to disable the BFD function. In this step, specify

Slot No. and Session ID.

Step 2 Run the LST BFDSESSION command. If Slot No. and Session ID for which the BFD function needs to be disabled are not displayed in the result, you can infer that the BFD function is disabled.

----End

2.59 Configuring OM Channel Backup 2.59.1 Enabling OM Channel Backup

Prerequisite Physical ports have been configured. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement


CN None.

OSS None.


Context When the peer IP address (the IP address of the M2000) and the local IP address are not

on the same segment, a route needs to be bound. Otherwise, the route does not need to be bound.


Procedure Step 1 Run the ADD OMCH command to add two OM channels. In this step, specify the following

parameters: Slot No., Active/Standby Flag, Local IP, Local Mask, Peer IP, and Peer Mask. The Active/Standby Flag parameter indicates the active/standby state of each OM channel.




Draft (2010–05–20)

Step 2 Run the LST OMCH command to check the OM channel configuration. If the result indicates two OM channels with Active/Standby Flag of one channel being Active and that of the other channel being Standby, it is an indication that OM channel backup is enabled.

----End

2.59.2 Disabling OM Channel Backup


Context If OM channel backup is disabled, active/standby switchover cannot be performed when the active OM channel fails, thereby failing to achieve the goal of improving transmission reliability.

Procedure Step 1 Run the RMV OMCH command to disable OM channel backup. In this step, set

Active/Standby Flag to STANDBY(Standby).

Step 2 Run the LST OMCH command to check the OM channel configuration. If the information about the standby OM channel is not displayed, it is an indication that OM channel backup is disabled.

----End

2.60 Configuring Ethernet Link Aggregation(IEEE 802.3ad) 2.60.1 Enabling Ethernet Link Aggregation(IEEE 802.3ad)

Prerequisite Physical ports have been configured. Ethernet ports are used. The directly connected transport equipment supports Ethernet link aggregation. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement


CN None.

OSS None.



2-97

Item Requirement



Procedure Step 1 Run the ADD ETHTRK command to add an Ethernet trunk. In this step, specify Slot No.,

Trunk No., and Trunk Type. It is recommended that Trunk Type be set to STATIC(Static). Ensure that the settings are identical at both ends of the trunk.

Step 2 Run the ADD ETHTRKLNK command to add a member port to the Ethernet trunk. In this step, specify Slot No., Trunk No., Ethernet Port No., and Port Priority.

Step 3 Run the LST ETHTRKLNK command to check the configuration of member ports in Ethernet trunks. If the results are the same as the settings made in the previous step, it is an indication that Ethernet link aggregation (IEEE 802.3ad) is enabled.

----End

2.60.2 Disabling Ethernet Link Aggregation(IEEE 802.3ad)


Context Disabling Ethernet link aggregation (IEEE 802.3ad) may fail to achieve the goals of increasing the bandwidth and enhancing error tolerance.

Procedure Step 1 Run the RMV ETHTRKLNK command to disable Ethernet link aggregation (IEEE 802.3ad).

In this step, specify Slot No., Trunk No., and Ethernet Port No..

Step 2 Run the LST ETHTRKLNK command to check the configuration of member ports in Ethernet trunks. If the information about the port removed is not displayed in the result, it is an indication that Ethernet link aggregation (IEEE 802.3ad) is disabled.

----End




Draft (2010–05–20)

2.61 Configuring IPSec 2.61.1 Enabling IPSec

Prerequisite The license for the feature is activated. The ACL feature has been enabled. For details, see section 2.64.1 "Enabling ." You have familiarized yourself with the IP Security (IPSec) feature. For details about the

feature, see the Security Feature Parameter Description. You have logged in to the LMT, and the LMT communicates with the eNodeB properly. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.


Transport network The IPSec feature is configured on the Security Gateway (SeGW).


OSS None.


Procedure Step 1 Run the ADD IKEPROP command to add an IKE security proposal.

If Authentication Method is set to PRE_SHARED_KEY(Pre-shared key), go to Step 2.

If Authentication Method is set to IKE_RSA_SIG(RSA_Signature), enable PKI first. For details, see section 2.62.1 "Enabling PKI."

Step 2 Run the ADD IKEPEER command to set the information that is used for IKE negotiation with the peer end.

Step 3 Run the ADD IPSECPROP command to add an IPSec security proposal.

Step 4 Run the ADD IPSECPOLICY command to add an IPSec security policy. The IPSec security policy consists of the ACL number, IPSec security proposal, and name of the IKE peer end.

Step 5 Run the ADD IPSECBIND command to apply the IPSec security policy to a specified port.

Step 6 Run the DSP IKESA command. If in the returned result the value of SA Flag is Ready, the IKE negotiation is successful.

Step 7 Run the DSP IPSECSA command. If the returned result contains the IPSec SA information, the IPSec negotiation is successful.

----End



2-99

2.61.2 Disabling IPSec

Prerequisite You have logged in to the LMT, and the LMT communicates with the eNodeB properly.

Context Disabling IPSec interrupts the transmission of the eNodeB.

Procedure Step 1 Run the RMV IPSECBIND command to cancel the application of the IPSec security policy

to a specified port.

Step 2 Run the RMV IPSECPOLICY command to delete the IPSec security policy.

Step 3 Run the RMV IPSECPROP command to delete the IPSec security proposal.

Step 4 Run the RMV IKEPEER command to delete the configured IKE negotiation information.

Step 5 Run the RMV IKEPROP command to delete the IKE security proposal.

Step 6 Run the LST IKEPEER command to query the IKE peer information. The returned result must not contain the deleted IKE peer end.

Step 7 Run the LST IPSECBIND command to query the binding relationship between the specified port and the security policy. The returned result must not contain the deleted binding relationship.

----End

2.62 Configuring PKI 2.62.1 Enabling PKI

Prerequisite The license of the feature is activated. The identities of peer ends are authenticated on the basis of certificates. You have familiarized yourself with the Public Key Infrastructure (PKI) feature. For

details about the PKI feature, see the Security Feature Parameter Description. You have logged in to the M2000 client, and the M2000 client communicates with the

eNodeB properly. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.


Transport network The PKI feature is supported.




Draft (2010–05–20)

Item Requirement

NEs in the EPC The PKI feature is supported.

OSS The PKI feature is supported.

Context Enabling PKI after the certificate is replaced interrupts the transport link. To learn about the principles and rules for setting the parameters of this feature, see the

Security Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the MOD CERTREQ command to set the basic parameters of the equipment certificate.

Step 2 Run the CRE CERTREQFILE command to create the certificate request file.

Step 3 Run the ULD NEFILE command to upload the certificate request file to a specified path on the M2000.

Step 4 Submit the certificate request file to the CA administrator by sending an Email or using storage device. Then, the administrator submits the certificate request file to the CA, which then grants the equipment certificate.

Step 5 The CA approves the request for the equipment certificate and sends the equipment certificate to the certificate database. The maintenance personnel obtain the equipment certificate and the certificate of the operator's root CA by using a storage device and copy the certificates to the specified path on the M2000.

Step 6 Run the DLD GENFILE command to download the certificate of the operator's root CA, namely the trust certificate, to the eNodeB.

Step 7 Run the ADD TRUSTCERT command to configure the downloaded certificate of the operator's root CA as the trust certificate of the eNodeB, which thus trusts all the certificates that are granted by the operator's root CA.

Step 8 Run the DLD GENFILE command to download the equipment certificate from the M2000 to the eNodeB.

Step 9 Run the ADD CERTMK command to check the downloaded equipment certificate by comparing it with the certificate request file that is created in Step 2.

Step 10 Run the TST APPCERT command to establish the IPSec connection by using the equipment certificate and query the execution result on the M2000.

Step 11 When the setup of the IPSec connection is successful, run the MOD APPCERT command to set the preceding equipment certificate as the equipment certificate used by the eNodeB.

----End



2-101

2.62.2 Disabling PKI

Prerequisite The IPSec feature has been disabled. For details, see section 2.61.2 "Disabling IPSec."

Or the authentication method is changed to pre-shared key. You have logged in to the LMT, and the LMT communicates with the eNodeB properly.

Context Disabling PKI interrupts the transmission of the eNodeB.

Procedure Step 1 Run the RMV CERTMK command to revoke the equipment certificate on the eNodeB.

Step 2 Run the LST CERTMK command to query the equipment certificate. The returned result must not contain the revoked equipment certificate.

----End

2.63 Configuring Access Control Based on 802.1x 2.63.1 Enabling Access Control Based on 802.1x

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of access control based on 802.1x. For

details about the feature, see the Security Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE The UE supports the integrity protection algorithms of AES and SNOW 3G.


Transport network The authentication access device, such as a LAN switch, supports 802.1x-based authentication. The authentication server, such a RADIUS server, is installed with Huawei root CA certificate and configured with the ESN of Huawei eNodeB.


OSS None.




Draft (2010–05–20)


Procedure Step 1 Run the ACT DOT1X command to activate 802.1x-based authentication.

Step 2 Run the DSP DOT1X command to check the setting of 802.1x-based authentication. If the value of Active Sign is Active, it is an indication that 802.1x-based authentication is enabled.

----End

2.63.2 Disabling Access Control Based on 802.1x


Context None.

Procedure Step 1 Run the DEA DOT1X command to deactivate 802.1x-based authentication.

Step 2 Run the DSP DOT1X command to check the setting of 802.1x-based authentication. If the value of Active Sign is DEACTIVE, it is an indication that 802.1x-based authentication is disabled.

----End

2.64 Configuring Access Control List(ACL) 2.64.1 Enabling Access Control List(ACL)

Prerequisite The license of the feature is activated. You have familiarized yourself with the Access Control List (ACL) feature. For details

about the feature, see the Security Feature Parameter Description. You have logged in to the LMT, and the LMT communicates with the eNodeB properly. The requirements of the feature listed in the following table have been fulfilled.

Item Requirement

UE None.



2-103

Item Requirement




OSS None.

Context The ACL is used both for packet filtering and IPSec protection. To learn about the principles and rules for setting the parameters of this feature, see the

Security Feature Parameter Description and eNodeB MO Reference.

Procedure Step 1 Run the ADD ACL command to add an ACL.

Step 2 Run the ADD ACLRULE command to add an ACL rule.

Step 3 If the added ACL is used to filter packets, run the ADD PACKETFILTER command to add the binding relationship between the ACL and the physical port.

Step 4 Run the LST ACL command to check whether the return result of the system contains the planned ACL number.

Step 5 Run the LST ACLRULE command to check whether the return result of the system contains the planned data about the ACL rules.

Step 6 If the added ACL is used to filter packets, run the LST PACKETFILTER command and check whether the returned result contains the binding relationship between the added ACL and the physical port.

----End

2.64.2 Disabling Access Control List(ACL)

Prerequisite If the ACL is used for the IPSec feature, the IPSec has been disabled. For details about

how to disable IPSec, see section 2.61.2 "Disabling IPSec." You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly.

Context None.




Draft (2010–05–20)

Procedure Step 1 If the ACL to be removed is used to filter packets, run the RMV PACKETFILTER

command to remove the binding relationship between the ACL and the physical port.

Step 2 Run the RMV ACLRULE command to remove the ACL rule.

Step 3 Run the RMV ACL command to remove the ACL.

Step 4 If the removed ACL was used to filter packets, run the LST PACKETFILTER command to check that the binding relationship between the ACL and the physical port does not exist.

Step 5 Run the LST ACLRULE command to check that the preceding ACL rule does not exist.

Step 6 Run the LST ACL command to check that the preceding ACL does not exist.

----End

2.65 Configuring Transport Overbooking 2.65.1 Enabling Transport Overbooking

Prerequisite Physical ports and logical ports are configured. Mapping relationships between service QCI types and DSCPs, and between DSCPs and

queues at the logical port are configured. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement



OSS None.


Context The transport overbooking of the eNodeB is classified into overbooking of the logical

ports and overbooking of physical ports. Through overbooking of logical ports, activity factors are configured for statistical multiplexing of the bandwidth of logical ports. Through overbooking of physical ports, the transmit bandwidth or receive bandwidth of logical ports is configured for statistical multiplexing of the bandwidth of physical ports.

A smaller activity factor of a user data type indicates more admitted services, but lower probabilities that required service bandwidths are guaranteed.




2-105

Procedure Step 1 Turn on the admission algorithm switch by running theSET TACALG command. In this step,

set Uplink Admission Control Algorithm Switch and Downlink Admission Control Algorithm Switch to ON.

Step 2 Turn on the switches of the traffic shaping algorithm and back-pressure algorithm by running the SET LGCPORTALG command to set traffic shaping. In this step, specify Slot No. and Logical Port Type, and set TX Traffic Shaping Switch to ON and Traffic Control Switch to ENABLE.

If... Then...

The overbooking function at the logical port needs to be enabled

a. Run the SET TACALG command to enable the overbooking function for logical ports. In this step, ensure that the activity factor of the user data type is not set to 100.

b. Run the LST TACALG command. If the displayed activity factor of the user data type is not 100, you can infer that the overbooking function at the logical port is enabled.

The overbooking function at the physical port needs to be enabled

a. Run the MOD IPLGCPORT command to enable the overbooking function at the physical port. In this step, specify Slot No. and Logical Port Type, set TX Bandwidth and RX Bandwidth, and ensure that the sum of TX Bandwidth and RX Bandwidth is greater than the bandwidth configured at the physical port.

b. Run the DSP IPLGCPORT command. If the result shows that the sum of TX Bandwidth and RX Bandwidth is greater than the bandwidth configured at the physical port, you can infer that the overbooking function at the physical port is enabled.

----End

2.65.2 Disabling Transport Overbooking


Context After transport overbooking is disabled, the admitted services become fewer, and the probability that the service bandwidth is guaranteed increases.




Draft (2010–05–20)

Procedure

If... Then...

The overbooking function at the logical port needs to be disabled

a. Run the SET TACALG command to disable the overbooking function for logical ports. In this step, set the activity factor of the user data type to 100.

b. Run the LST TACALG command. If the displayed activity factor of the user data type is 100, you can infer that the overbooking function at the logical port is disabled.

The overbooking function at the physical port needs to be disabled

a. Run the MOD IPLGCPORT command to disable the overbooking function at the physical port. In this step, set TX Bandwidth and RX Bandwidth, and ensure that the sum of TX Bandwidth and RX Bandwidth is less than or equal to the bandwidth configured at the physical port.

b. Run the DSP IPLGCPORT command. If the result shows that the sum of TX Bandwidth and RX Bandwidth is less than or equal to the bandwidth configured at the physical port, you can infer that the overbooking function at the physical port is disabled.

----End

2.66 Configuring Transport Differentiated Flow Control 2.66.1 Enabling Transport Differentiated Flow Control




Item Requirement



OSS None.




2-107

Context If congestion occurs on the eNodeB interface boards, the transport differentiated flow

control function can be enabled. After this function is enabled, the services that do not require flow control are processed preferentially to guarantee the service quality. The rates of non-real-time services are limited to achieve the differentiated allocation of bandwidth among the non-real-time services, that is, to allocate the remaining bandwidth according to the weighted factor, while maintaining the minimum Guaranteed Bit Rate (GBR).

The transport differentiated flow control is composed of the traffic shaping algorithm of the logical ports, the queue scheduling algorithm of logical ports, and the back-pressure algorithm. The traffic shaping algorithm of logical ports ensures that the transmit rate of logical ports does not exceed the bottleneck bandwidth of the transport network, so that congestion of the transport network can be prevented. The queue scheduling algorithm of logical ports ensures that the services that do not require flow control are processed preferentially. The back-pressure algorithm implements flow control on the flow-control services (including the non-real-time services), so that the transmit rate can be limited and differentiation can be achieved.


Procedure Step 1 Run the SET LGCPORTALG command. In this step, specify Slot No. and Logical Port

Type of the logical port for which differentiated flow control needs to be enabled. Then, set TX Traffic Shaping Switch to ON, configure the back-pressure algorithm, and specify PQ Number of the queue scheduling algorithm of logical ports. The configuration of the back-pressure algorithm involves the following operations: setting Traffic Control Switch to ENABLE, and specifying Drop Packet Number Threshold, Congestion Time Threshold, Congestion Clear Time Threshold, and OM/FTP Traffic Control Switch.

Step 2 Run the LST LGCPORTALG command to list the configuration of the logical port for which differentiated flow control needs to be enabled. Then, check the configuration of transport differentiated flow control in the result displayed on the eNodeB LMT.

----End

2.66.2 Disabling Transport Differentiated Flow Control


Context After transport differentiated flow control is disabled, the differentiation and fairness of the transmission cannot be guaranteed if the transport bandwidth is limited.

Procedure Step 1 Run the SET LGCPORTALG command. In this step, specify Slot No. and Logical Port

Type of the logical port for which differentiated flow control needs to be disabled. Then, set




Draft (2010–05–20)

TX Traffic Shaping Switch to OFF, configure the back-pressure algorithm, and delete PQ Number of the queue scheduling algorithm of logical ports. The configuration of the back-pressure algorithm involves the following operations: setting Traffic Control Switch to DISABLE, and specifying Congestion Time Threshold, Congestion Clear Time Threshold, and OM/FTP Traffic Control Switch.

Step 2 Run the LST LGCPORTALG command to list the configuration of the logical port for which differentiated flow control needs to be disabled. Then, check the configuration of transport differentiated flow control in the result displayed on the eNodeB LMT.

----End

2.67 Configuring Resource Overload Flow Control 2.67.1 Enabling Resource Overload Flow Control




Item Requirement



OSS None.


Context When the transport bandwidth is changed or the services that do not require flow control

are overloaded, the bandwidth used by low-priority services is released to guarantee the quality of high-priority services.

When both the uplink/downlink OLC algorithm switch and the uplink/downlink admission control algorithm switch are set to ON, the uplink/downlink OLC release threshold must be higher than or equal to the uplink/downlink high priority user admission threshold.


Procedure Step 1 Run the SET TOLCALG command. In this step, set Uplink OLC Algorithm Switch and

Downlink OLC Algorithm Switch to ON.



2-109

Step 2 Run the LST TOLCALG command to list the configuration of the OLC algorithm. Then, check the configuration of resource overload flow control in the result displayed on the eNodeB LMT.

----End

2.67.2 Disabling Transport Resource Overload Flow Control


Context After transport resource overload control is disabled, the quality of high-priority services cannot be guaranteed if the transport bandwidth is changed or the services that do not require flow control are overloaded.

Procedure Step 1 Run SET TOLCALG command to disable transport resource overload control. In this step,

set Uplink OLC Algorithm Switch and Downlink OLC Algorithm Switch to OFF.

Step 2 Run LST TOLCALG command. If the result shows that both Uplink OLC Algorithm Switch and Downlink OLC Algorithm Switch are OFF, you can infer that transport resource overload control is disabled.

----End

2.68 Configuring IP Performance Monitoring 2.68.1 Enabling IP Performance Monitoring

Prerequisite The license of the feature is activated. Physical ports and logical ports are configured. IP Performance Monitoring (IP PM) can be successfully enabled only when the devices

at both ends (local and peer ends) support IP PM. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement


NEs in the EPC IP PM is supported.

OSS None.




Draft (2010–05–20)

Item Requirement


Context IP PM is a mechanism for monitoring the transmission quality of the IP layer. It is used

to monitor the transmission quality between the eNodeB and the S-GW. The eNodeB inserts the PM packets into the IP packet flows to monitor the transmission performance counters, including the transmission KPIs such as the number of transmitted or received packets, packet loss rate, unidirectional delay variation, and bi-directional delay. IP PM works with the transport dynamic flow control algorithm to prevent dynamic changes in the transport bandwidth from affecting the service quality.

To prevent the fragmentation of the transport network from affecting the calculation of the number of transmitted and received packets, you are advised to enable transport differentiated flow control when you use IP PM to monitor the logical port.


Procedure To enable transport differentiated flow control, perform the following steps:

Step 1 Run the SET LGCPORTALG command. In this step, specify Slot No. and Logical Port Type of the logical port for which IP PM needs to be enabled, and enable differentiated flow control for this port. Then, set TX Traffic Shaping Switch to ON, configure the back-pressure algorithm, and specify PQ Number of the queue scheduling algorithm of logical ports. The configuration of the back-pressure algorithm involves the following operations: setting Traffic Control Switch to ENABLE, and specifying Congestion Time Threshold, Congestion Clear Time Threshold, and OM/FTP Traffic Control Switch.

Step 2 Run the LST LGCPORTALG command to list the configuration of the logical port for which differentiated flow control needs to be enabled. Then, check the configuration of transport differentiated flow control in the result displayed on the eNodeB LMT.

----End

To enable the IP PM function, perform the following steps:

Step 1 Run the ADD IPPMSESSION command to enable the IP PM function. In this step, specify IPPM Session ID, Local IP, Peer IP, IPPM Session DSCP, and Activate Direction.

Step 2 Run the DSP IPPMSESSION command. If the result shows that the configuration of the IPPM session for which the IP PM function needs to be enabled is normal, you can infer that the IP PM function is enabled. The configuration information about the IPPM session consists of IPPM Session ID, Local IP, Peer IP, IPPM Session DSCP, and Activate Direction.

----End



2-111

2.68.2 Disabling IP Performance Monitoring


Context If transport dynamic flow control is required for logical ports, at least one IP PM flow needs to be activated. Otherwise, the transmission congestion decision cannot be performed.

Procedure Step 1 Run the RMV IPPMSESSION command. In this step, specify IPPM Session ID for which

the IP PM function needs to be disabled.

Step 2 Run the LST IPPMSESSION command. If the configuration of the IPPM session for which the IP PM function needs to be disabled is not displayed in the result, you can infer that the IP PM function is disabled. The configuration information about the IPPM session consists of IPPM Session ID, Local IP, Peer IP, IPPM Session DSCP, and Activate Direction.

----End

2.69 Configuring Transport Dynamic Flow Control 2.69.1 Enabling Transport Dynamic Flow Control

Prerequisite Physical ports and logical ports are configured. If transport dynamic flow control is required for logical ports, the IP PM function needs

to be enabled and at least one IP PM flow needs to be activated. Otherwise, the transmission congestion decision cannot be performed.



Item Requirement


NEs in the EPC IP PM is supported.

OSS None.





Draft (2010–05–20)

Context The transport dynamic flow control estimates the bottleneck bandwidth of the transport

network according to the transmission quality checked through IP PM. Then, the transmit rate of the logical ports of the eNodeB interface boards is adjusted dynamically and controlled so that the rate does not exceed the bottleneck bandwidth. Transport dynamic flow control is used to prevent the congestion of the transport network, which guarantees the transmission quality of services in scenarios where the transport bandwidth changes dynamically.

To guarantee the correctness of the IP PM statistics and to guarantee the fairness and differentiation among non-real-time services, transport differentiated flow control must be implemented.


Procedure To turn on the back-pressure algorithm switch or enable transport differentiated flow control, perform the following steps:

Step 1 Run the SET LGCPORTALG command. In this step, specify Slot No. and Logical Port Type of the logical port. Then, set TX Traffic Shaping Switch to ON, configure the back-pressure algorithm, and specify PQ Number of the queue scheduling algorithm of logical ports. The configuration of the back-pressure algorithm involves the following operations: setting Traffic Control Switch to ENABLE, and specifying Congestion Time Threshold, Congestion Clear Time Threshold, and OM/FTP Traffic Control Switch.

Step 2 Run the LST LGCPORTALG command to list the configuration of the logical port algorithm. Then, check the configuration of transport differentiated flow control in the result displayed on the eNodeB LMT.

----End

To enable transport dynamic flow control, proceed with the following steps:

Step 1 Run the SET LGCPORTALG command. In this step, set TX Bandwidth Adjustment Switch and RX Bandwidth Adjustment Switch of the logical port for which transport dynamic flow control needs to be enabled to ON.

Step 2 Run the LST LGCPORTALG command. If the result shows that TX Bandwidth Adjustment Switch and RX Bandwidth Adjustment Switch of the logical port for which transport dynamic flow control needs to be enabled are ON, you can infer that transport dynamic flow control is enabled.

----End

2.69.2 Disabling Transport Dynamic Flow Control




2-113

Context After transport dynamic flow control is disabled, the congestion of the transport network cannot be prevented, thus the transmission quality of services in scenarios where the transport bandwidth changes dynamically.

Procedure Step 1 Run the SET LGCPORTALG command. In this step, set TX Bandwidth Adjustment

Switch and RX Bandwidth Adjustment Switch of the logical port for which transport dynamic flow control needs to be disabled to OFF.

Step 2 Run the LST LGCPORTALG command. If the result shows that TX Bandwidth Adjustment Switch and RX Bandwidth Adjustment Switch of the logical port for which transport dynamic flow control needs to be disabled are OFF, you can infer that transport dynamic flow control is disabled.

----End

2.70 Configuring Synchronization with Ethernet(ITU-T G.8261) 2.70.1 Enabling Synchronization with Ethernet(ITU-T G.8261)

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of synchronous Ethernet. For details

about the feature, see the Synchronization Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.


Transport network The peer equipment supports synchronous Ethernet.

NEs in the EPC The peer equipment supports synchronous Ethernet.

OSS None.





Draft (2010–05–20)


to SYNCETH(Synceth), and specify Clock Source Priority.

Step 2 Run the ADD SYNCETH command to add a synchronous-Ethernet clock link. In this step, set Slot No. and Port No. to the number of the slot and the number of the port where the synchronous-Ethernet clock is configured respectively.

Step 3 Run the DSP CLKSRC command to check the status of the clock source. The result indicates that the status of the synchronous-Ethernet clock is Available.

----End

2.70.2 Disabling Synchronization with Ethernet(ITU-T G.8261)



removed. If the synchronous-Ethernet clock is the only clock source of the LTE system, disabling

synchronous Ethernet results in a loss of the system clock source. This affects the operation of the LTE system.

Procedure Step 1 Run the RMV SYNCETH command to remove the synchronous-Ethernet clock link.

Step 2 Run the RMV CLKSRC command to remove the clock source. In this step, set Clock Source Type to SYNCETH(Synceth).

Step 3 Run the LST CLKSRC command to check clock sources. The synchronous-Ethernet clock is not displayed in the result.

----End

2.71 Configuring IEEE1588 V2 Clock Synchronization 2.71.1 Enabling IEEE1588 V2 Clock Synchronization

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of IEEE1588 V2 clock synchronization.

For details about the feature, see the Synchronization Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB

properly.



2-115


Item Requirement

UE None.


Transport network The peer equipment supports IEEE1588 V2 clock synchronization.

NEs in the EPC The peer equipment supports IEEE1588 V2 clock synchronization.

OSS None.

Context IEEE1588 V2 clock synchronization supports the layer 3 unicast and layer 2 multicast modes. To learn about the principles and rules for setting the parameters of this feature, see the Synchronization Feature Parameter Description and eNodeB MO Reference.


to IPCLK(Ipclk), and specify Clock Source Priority.

Step 2 Run the ADD IPCLKLINK command to add an IEEE1588 V2 clock link. In this step, set Protocol Type to PTP(PTP), and set Slot No. to the number of the slot where the IEEE1588 V2 clock is configured.

To set the IEEE1588 V2 clock to the layer 3 unicast mode, set Template Type to UNICAST(Unicast), and specify Server IP.

To set the IEEE1588 V2 clock to the layer 2 multicast mode, set Template Type to MULTICAST_MULTICAST(Sync Multicast, Delay Request Multicast), and set Network Type to L2_MULTICAST(L2 Multicast).

Step 3 Run the DSP CLKSRC command to check the status of the clock source. The result indicates that the status of the IEEE1588 V2 clock is Available.

----End

2.71.2 Disabling IEEE1588 V2 Clock Synchronization



removed. If the IEEE1588 V2 clock is the only clock source of the LTE system, disabling

IEEE1588 V2 clock synchronization results in a loss of the system clock source. This affects the operation of the LTE system.




Draft (2010–05–20)

Procedure Step 1 Run the RMV IPCLKLINK command to remove the IEEE1588 V2 clock link.

Step 2 Run the RMV CLKSRC command to remove the clock source. In this step, set Clock Source Type to IPCLK(Ipclk).

Step 3 Run the LST CLKSRC command to check clock sources. The IEEE1588 V2 clock is not displayed in the result.

----End

2.72 Configuring Clock over IP (Huawei Proprietary) 2.72.1 Enabling Clock over IP (Huawei Proprietary)

Prerequisite The license for this feature has been activated. You have familiarized yourself with the feature of clock over IP. For details about the

feature, see the Synchronization Feature Parameter Description. You have logged in to the eNodeB LMT, and the LMT communicates with the eNodeB


Item Requirement

UE None.




OSS None.



to IPCLK(Ipclk), and specify Clock Source Priority.

Step 2 Run the ADD IPCLKLINK command to add a link of clock over IP. In this step, set Protocol Type to HW_DEFINED(HW Defined), set Slot No. to the number of the slot where the clock is configured, and specify Server IP.



2-117

Step 3 Run the DSP CLKSRC command to check the status of the clock source. The result indicates that the status of the clock over IP is Available.

----End

2.72.2 Disabling Clock over IP (Huawei Proprietary)



removed. If the clock over IP is the only clock source of the LTE system, disabling clock over IP

(Huawei proprietary) results in a loss of the system clock source. This affects the operation of the LTE system.

Procedure Step 1 Run the RMV IPCLKLINK command to remove the clock over IP.

Step 2 Run the RMV CLKSRC command to remove the clock source. In this step, set Clock Source Type to IPCLK(Ipclk).

Step 3 Run the LST CLKSRC command to check clock sources. The clock over IP is not displayed in the result.

----End

Documents

ErAN