Volteeran8 161124091619

eRAN
VoLTE Feature Parameter

Description
Issue 03
Date 2015-06-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2015-06-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
VoLTE Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 2
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between eNodeB Types.............................................................................................................................. 6
2 Overview......................................................................................................................................... 8
2.1 Background.....................................................................................................................................................................8
2.2 Introduction.................................................................................................................................................................... 9
2.3 Benefits......................................................................................................................................................................... 10
2.4 Architecture.................................................................................................................................................................. 10
3 Basic VoLTE Functions...............................................................................................................14

3.1 Speech Codec Scheme and Traffic Model....................................................................................................................15
3.2 VoLTE Voice Policy Selection......................................................................................................................................16
3.2.1 Common Scenarios....................................................................................................................................................16
3.2.1.1 General Principles for Voice Policy Selection........................................................................................................16
3.2.1.2 VoLTE Mobility Capability Decision..................................................................................................................... 18
3.2.2 VoLTE-Prohibited Scenario....................................................................................................................................... 19
3.3 Radio Bearer Management........................................................................................................................................... 21
3.3.1 Radio Bearer Setup.................................................................................................................................................... 21
3.3.2 Radio Bearer QoS Management................................................................................................................................ 23
3.4 Admission and Congestion Control..............................................................................................................................24
3.4.1 Overview................................................................................................................................................................... 24
3.4.2 Load Monitoring........................................................................................................................................................24
3.4.3 Admission Control.....................................................................................................................................................25
3.4.4 Congestion Control....................................................................................................................................................25
3.5 Dynamic Scheduling and Power Control..................................................................................................................... 26
3.5.1 Dynamic Scheduling..................................................................................................................................................26
3.5.2 Power Control in Dynamic Scheduling..................................................................................................................... 27
4 Enhanced VoLTE Features......................................................................................................... 28

4.1 Capacity Enhancement................................................................................................................................................. 29
4.1.1 Semi-Persistent Scheduling and Power Control........................................................................................................ 29
4.1.1.1 Semi-Persistent Scheduling.................................................................................................................................... 29
Issue 03 (2015-06-30) Huawei Proprietary and Confidential ii

eRAN
4.1.1.2 Power Control in Semi-Persistent Scheduling........................................................................................................32

4.1.2 ROHC........................................................................................................................................................................ 33
4.2 Coverage Improvement................................................................................................................................................ 34
4.2.1 TTI Bundling............................................................................................................................................................. 34
4.2.1.1 Overview................................................................................................................................................................ 34
4.2.1.2 Principles................................................................................................................................................................ 34
4.2.2 ROHC........................................................................................................................................................................ 36
4.2.3 Uplink RLC Segmentation Enhancement..................................................................................................................37
4.3 Quality Improvement....................................................................................................................................................38
4.3.1 Voice Characteristic Awareness Scheduling..............................................................................................................38
4.3.2 Uplink Compensation Scheduling............................................................................................................................. 39
4.3.3 Voice-Specific AMC..................................................................................................................................................41
4.4 Power Saving................................................................................................................................................................ 41
4.5 Mobility Management.................................................................................................................................................. 42
4.5.1 Overview................................................................................................................................................................... 42
4.5.2 Intra-Frequency Handover.........................................................................................................................................43
4.5.3 Inter-Frequency Handover.........................................................................................................................................43
4.5.4 Inter-RAT Handover.................................................................................................................................................. 45
4.5.4.1 Handover Type........................................................................................................................................................45
4.5.4.2 Handover Mode...................................................................................................................................................... 47
5 Special Processing by Other Features......................................................................................48

6 Related Features...........................................................................................................................51
6.1 LOFD-001016 VoIP Semi-persistent Scheduling.........................................................................................................52
6.2 LOFD-001048 TTI Bundling....................................................................................................................................... 53
6.3 Uplink RLC Segmentation Enhancement.....................................................................................................................54
6.4 LOFD-081229 Voice Characteristic Awareness Scheduling........................................................................................ 54
6.5 LBFD-081104 UL Compensation Scheduling............................................................................................................. 55
6.6 LBFD-081105 Voice-Specific AMC............................................................................................................................ 55
6.7 Other Features...............................................................................................................................................................55
7 Network Impact........................................................................................................................... 58
7.1 LOFD-001016 VoIP Semi-persistent Scheduling.........................................................................................................59
7.2 LOFD-001048 TTI Bundling....................................................................................................................................... 59
7.3 Uplink RLC Segmentation Enhancement.....................................................................................................................60
7.4 LOFD-081229 Voice Characteristic Awareness Scheduling........................................................................................ 60
7.5 LBFD-081104 UL Compensation Scheduling............................................................................................................. 61
7.6 LBFD-081105 Voice-Specific AMC............................................................................................................................ 61
7.7 Other Features...............................................................................................................................................................62
8 Voice Service Performance Evaluation................................................................................... 64

8.1 QoS Requirements........................................................................................................................................................ 64
8.2 Quality Evaluation........................................................................................................................................................ 64
8.2.1 Subjective Evaluation................................................................................................................................................ 64
Issue 03 (2015-06-30) Huawei Proprietary and Confidential iii

eRAN
8.2.2 Objective Evaluation................................................................................................................................................. 65

8.2.3 Measurement-based Evaluation.................................................................................................................................65
8.3 Capacity Evaluation......................................................................................................................................................67
8.4 Performance Evaluation............................................................................................................................................... 68
9 Engineering Guidelines............................................................................................................. 69
9.1 Overview...................................................................................................................................................................... 69
9.2 Basic Functions.............................................................................................................................................................70
9.2.1 When to Use Basic Functions....................................................................................................................................70
9.2.2 Required Information................................................................................................................................................ 71
9.2.3 Deployment............................................................................................................................................................... 71
9.2.3.1 Requirements.......................................................................................................................................................... 71
9.2.3.2 Data Preparation..................................................................................................................................................... 71
9.2.3.3 Precautions..............................................................................................................................................................73
9.2.3.4 Hardware Adjustment.............................................................................................................................................73
9.2.3.5 Initial Configuration............................................................................................................................................... 73
9.2.3.6 Activation Observation...........................................................................................................................................76
9.2.3.7 Reconfiguration...................................................................................................................................................... 78
9.2.3.8 Deactivation............................................................................................................................................................78
9.2.4 Performance Monitoring............................................................................................................................................79
9.2.4.1 Voice KPIs.............................................................................................................................................................. 79
9.2.4.2 Voice QoS............................................................................................................................................................... 83
9.2.4.3 Voice Quality.......................................................................................................................................................... 84
9.2.4.4 Voice Capacity........................................................................................................................................................ 87
9.2.5 Parameter Optimization............................................................................................................................................. 89
9.2.6 Troubleshooting......................................................................................................................................................... 90
9.3 Semi-Persistent Scheduling.......................................................................................................................................... 90
9.3.1 When to Use Semi-Persistent Scheduling and Deploy Power Control..................................................................... 90
9.3.2 Required Information................................................................................................................................................ 91
9.3.3 Deployment of Semi-Persistent Scheduling.............................................................................................................. 91
9.3.3.1 Requirements.......................................................................................................................................................... 91
9.3.3.2 Data Preparation..................................................................................................................................................... 92
9.3.3.3 Precautions..............................................................................................................................................................93
9.3.3.4 Hardware Adjustment.............................................................................................................................................93
9.3.3.5 Initial Configuration............................................................................................................................................... 93
9.3.3.6 Activation Observation...........................................................................................................................................96
9.3.3.7 Reconfiguration...................................................................................................................................................... 99
9.3.3.8 Deactivation............................................................................................................................................................99
9.3.4 Performance Monitoring..........................................................................................................................................100
9.3.5 Parameter Optimization........................................................................................................................................... 100
9.3.6 Troubleshooting....................................................................................................................................................... 101
9.4 TTI Bundling.............................................................................................................................................................. 101
9.4.1 When to Deploy TTI Bundling................................................................................................................................101
Issue 03 (2015-06-30) Huawei Proprietary and Confidential iv

eRAN
9.4.2 Required Information.............................................................................................................................................. 101

9.4.3 Deployment of TTI Bundling.................................................................................................................................. 101
9.4.3.1 Requirements........................................................................................................................................................ 101
9.4.3.2 Data Preparation................................................................................................................................................... 102
9.4.3.3 Precautions............................................................................................................................................................104
9.4.3.4 Hardware Adjustment...........................................................................................................................................104
9.4.3.5 Initial Configuration............................................................................................................................................. 104
9.4.3.6 Activation Observation.........................................................................................................................................106
9.4.3.7 Reconfiguration.................................................................................................................................................... 108
9.4.3.8 Deactivation..........................................................................................................................................................108
9.5 UL RLC Segmentation Enhancement........................................................................................................................ 109
9.5.1 When to Use Uplink RLC Segmentation Enhancement..........................................................................................110
9.5.2 Required Information...............................................................................................................................................110
9.5.3 Deployment..............................................................................................................................................................110
9.5.3.1 Requirements........................................................................................................................................................ 110
9.5.3.3 Precautions............................................................................................................................................................111
9.5.3.4 Hardware Adjustment........................................................................................................................................... 111
9.5.3.5 Initial Configuration..............................................................................................................................................111
9.5.3.6 Activation Observation......................................................................................................................................... 113
9.5.3.8 Deactivation.......................................................................................................................................................... 115
9.6 Voice Characteristic Awareness Scheduling............................................................................................................... 116
9.6.1 When to Use Voice Characteristic Awareness Scheduling...................................................................................... 116
9.6.2 Required Information...............................................................................................................................................116
9.6.3 Deployment..............................................................................................................................................................116
9.6.3.1 Requirements........................................................................................................................................................ 116
9.6.3.3 Precautions............................................................................................................................................................118
9.6.3.4 Hardware Adjustment........................................................................................................................................... 118
9.6.3.8 Deactivation..........................................................................................................................................................121
Issue 03 (2015-06-30) Huawei Proprietary and Confidential v

eRAN

9.7 Uplink Compensation Scheduling.............................................................................................................................. 123
9.7.1 When to Use Uplink Compensation Scheduling..................................................................................................... 123
9.7.3 Deployment............................................................................................................................................................. 123
9.7.3.1 Requirements........................................................................................................................................................ 123
9.7.3.3 Precautions............................................................................................................................................................124
9.7.3.8 Deactivation..........................................................................................................................................................128
9.8 Voice-Specific AMC...................................................................................................................................................129
9.8.1 When to Use Voice-Specific AMC..........................................................................................................................129
9.8.3 Deployment............................................................................................................................................................. 129
9.8.3.1 Requirements........................................................................................................................................................ 129
9.8.3.3 Precautions............................................................................................................................................................130
9.8.3.8 Deactivation..........................................................................................................................................................134
10 Parameters................................................................................................................................. 136
11 Counters.................................................................................................................................... 215
12 Glossary..................................................................................................................................... 247
13 Reference Documents............................................................................................................. 248
Issue 03 (2015-06-30) Huawei Proprietary and Confidential vi

eRAN
VoLTE Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes Voice over LTE (VoLTE), including its technical principles, related
features, network impact, and engineering guidelines. VoLTE is based on IP multimedia
subsystem (IMS).
This document covers the following features:
l LOFD-001016 VoIP Semi-persistent Scheduling
l LOFD-001048 TTI Bundling
l LOFD-081229 Voice Characteristic Awareness Scheduling
l LBFD-081104 UL Compensation Scheduling
l LBFD-081105 Voice-Specific AMC
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
Micro base BTS3202E

station
LampSite DBS3900 LampSite
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
Issue 03 (2015-06-30) Huawei Proprietary and Confidential 1

eRAN
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN8.1 03 (2015-06-30)
This issue includes the following changes.
Change Change Description Parameter Affected

Type Change Entity
Feature None None Macro, micro,

change and LampSite
eNodeBs
Editorial Revised the following sections: None -

change 4.1.1 Semi-Persistent Scheduling
and Power Control
4.3.1 Voice Characteristic
Awareness Scheduling
4.3.2 Uplink Compensation
Scheduling
eRAN8.1 02 (2015-04-30)

eRAN

Type Change Entity
Feature Changed the optional feature Voice- None Macro, micro,

change Specific AMC to a basic feature, and and LampSite
changed the feature ID from eNodeBs
LOFD-081230 to LBFD-081105.
Editorial Revised the following sections: None -

change 3.2.1.2 VoLTE Mobility Capability
Decision
3.2.2 VoLTE-Prohibited Scenario
9.2.3.1 Requirements
9.2.6 Troubleshooting
eRAN8.1 01 (2015-03-23)

Type Change Entity
Feature Modified the LOFD-081229 Voice Added the Macro, micro,

change Characteristic Awareness Scheduling following and LampSite
feature to add independent parameter: eNodeBs
configurations for the UE inactivity CELLALGOS
timer for voice services. For details, WITCH.UEIn
see the following sections: activeTimerQC
2.4 Architecture I1Switch
4.3.1 Voice Characteristic
7.4 LOFD-081229 Voice
Characteristic Awareness
Scheduling
Editorial Added network impact descriptions. None -

change For details, see the following
sections:
7.1 LOFD-001016 VoIP Semi-
persistent Scheduling
7.2 LOFD-001048 TTI Bundling
eRAN8.1 Draft A (2015-01-15)

Compared with Issue 05 (2014-11-13) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1
includes the following changes.

eRAN

Type Change Entity
Feature Modified the voice quality Added the Macro, micro,

change monitoring mechanism as follows: following and LampSite
l The voice quality threshold parameters: eNodeBs
becomes configurable. l VQMAlgo.
l The downlink voice quality VqiExcellen
evaluation is changed from E- tThd
Model to VQI-Model. l VQMAlgo.
For details, see 8.2.3 Measurement- VqiPoorThd
based Evaluation. l VQMAlgo.
VqiGoodTh
d
l VQMAlgo.
VqiBadThd
Added policy control for Added the Macro, micro,

measurements (such as ANR GlobalProcSwi and LampSite
measurement) by UEs performing tch.VoipWithG eNodeBs
voice services. apMode
For details, see 5 Special Processing parameter.
by Other Features.
Added the descriptions of the None Macro, micro,

relationship between LOFD-001016 and LampSite
VoIP Semi-persistent Scheduling and eNodeBs
LAOFD-0010014 DL 2x2 MIMO
based on TM9. For details, see 4.1.1
Semi-Persistent Scheduling and
Power Control.
Modified the relationship between None Macro, micro,

LOFD-001048 TTI Bundling and and LampSite
LAOFD-001001 LTE-A eNodeBs
Introduction. For details, see 4.2.1
TTI Bundling.

eRAN

Type Change Entity
Modified the functions of TTI Added the Macro, micro,

bundling: following and LampSite
l Enabled the configuration of parameter: eNodeBs
applicable services of TTI l CellAlgoSw
bundling. The applicable services itch.TtiBun
include VoLTE or a combination dlingTrigge
of VoLTE and data. rStrategy
l Added five key parameters to l CellAlgoSw
TTI bundling. itch.
For details, see 4.2.1 TTI Bundling. StatisticNu
mThdForTt
ibTrig
l CellAlgoSw
itch.
StatisticNu
mThdForTt
ibExit
l CellAlgoSw
itch.
HystToExit
TtiBundling
l CellAlgoSw
itch.
TtiBundling
RlcMaxSeg
Num
l CellAlgoSw
itch.
TtiBundling
HarqMaxT
xNum
Added LOFD-081229 Voice l Added the Macro, micro,

Characteristic Awareness CellAlgoSw and LampSite
Scheduling. For details, see 4.3.1 itch.UlDela eNodeBs
Voice Characteristic Awareness ySchStrateg
Scheduling and 9.6 Voice y parameter.
Characteristic Awareness l Added the
Scheduling. UlVoLTED
ataSizeEstS
witch option
to the
CellAlgoSw
itch.UlEnhe
ncedVoipSc
hSw
parameter.

eRAN

Type Change Entity
Added LBFD-081104 UL Added the Macro, micro,

Compensation Scheduling. For UlVoipSchOpt and LampSite
details, see 4.3.2 Uplink Switch option eNodeBs
Compensation Scheduling and 9.7 to the
Uplink Compensation Scheduling. CellAlgoSwitc
h.UlEnhenced
VoipSchSw
parameter.
Added LOFD-081230 Voice- Added the Macro, micro,

Specific AMC. For details, see 4.3.3 CellAlgoSwitc and LampSite
Voice-Specific AMC and 9.8 Voice- h.SinrAdjTarge eNodeBs
Specific AMC. tIblerforVoLTE
parameter.
Editorial Modified the document structure to None -

change enhance readability.
Added 8.2.2 Objective Evaluation. None -
Added counters to measure handover None -

success rates for VoLTE services.
For details, see 9.2.4.1 Voice KPIs.
Added 4.3.1 Voice Characteristic None -

Awareness Scheduling, which
incorporates the description of
uplink delay-based dynamic
scheduling.
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs
VoIP services are implemented on the basis of multiple features and functions. The following
table lists the differences of VoIP-related features between eNodeB types. For details about
other features and functions, see the corresponding feature parameter descriptions.
Feature ID Feature Name Suppor Supported Supported by

ted by by Micro LampSite
Macro eNodeBs eNodeBs
eNode
Bs
LOFD-001016 VoIP Semi-persistent Yes Yes Yes

Scheduling
LOFD-001048 TTI Bundling Yes Yes Yes

eRAN
Feature ID Feature Name Suppor Supported Supported by

ted by by Micro LampSite
Macro eNodeBs eNodeBs
eNode
Bs
LOFD-081229 Voice Characteristic Yes Yes Yes

LBFD-081105 UL Compensation Yes Yes Yes

Scheduling
LBFD-081105 Voice-Specific AMC Yes Yes Yes
Function Implementation in Macro, Micro, and LampSite eNodeBs

Function Difference
High speed Micro and LampSite eNodeBs do not support high speed mobility. The
mobility dynamic scheduling policies for high speed mobility described herein
apply only to macro eNodeBs. For details, see 3.5.1 Dynamic
Scheduling.
1.4 MHz Micro and LampSite eNodeBs do not support 1.4 MHz bandwidth. The
bandwidth dynamic scheduling policies for 1.4 MHz bandwidth described herein
apply only to macro eNodeBs. For details, see 3.5.1 Dynamic
Scheduling.

eRAN
VoLTE Feature Parameter Description 2 Overview
2 Overview
2.1 Background
The LTE voice solution is as follows:
l Voice solution based on dual-standby UEs

A dual-standby UE is capable of receiving or sending signals in both E-UTRAN and
GERAN or UTRAN. Dual-standby UEs automatically select GERAN or UTRAN to
perform voice services and select E-UTRAN to perform data services. That is, the E-
UTRAN provides dual-standby UEs with only data services.
l Voice solution based on CSFB
In the initial phase of LTE network deployment, CSFB is a transitional solution to
provide voice services for LTE users if the IMS is not yet deployed. Figure 2-1 shows
the voice solution based on CSFB.
Figure 2-1 Voice solution based on CSFB
With the CSFB solution, when a UE initiates a CS service in the E-UTRAN, the MME
instructs the UE to fall back to the legacy CS domain of the GERAN or UTRAN before

eRAN
the UE performs the service. For details about CSFB, see CS Fallback Feature
Parameter Description.
l Voice solution based on IMS
This solution is used in the mature stage of the LTE network when the IMS is deployed,
as shown in Figure 2-2. With this solution, UEs can directly perform voice services in an
LTE network. This solution is also termed as the Voice over LTE (VoLTE) solution.
When LTE coverage has not been complete, UEs may move out of LTE coverage and
their voice services may be discontinued. Huawei uses the following methods to ensure
voice service continuity:
– If the PS domain of the UTRAN/GERAN does not support VoIP services, VoIP
services are handed over to the CS domain of the UTRAN/GERAN through single
radio voice call continuity (SRVCC). For details about SRVCC, see SRVCC Feature
– If the PS domain of the UTRAN/GERAN supports VoIP services, VoIP services are
handed over to the UTRAN/GERAN through PS handovers. For details about PS
handovers, see Inter-RAT Mobility Management in Connected Mode Feature
Figure 2-2 Voice solution based on IMS
2.2 Introduction
VoLTE is the voice service supported by the IP transmission network between UEs in the E-
UTRAN and the IMS. That is, with VoLTE, UEs in the LTE network can perform voice
services directly.
Emergency services are not described in this document. For details about emergency services,
see Emergency Call Feature Parameter Description.

eRAN
2.3 Benefits
VoLTE provides UEs in the E-UTRAN with voice services, without the need of falling back
to GERAN or UTRAN. VoLTE features the following characteristics:
l Higher spectral efficiency

l Better user experience, such as lower access delay and better voice quality
2.4 Architecture
Network Architecture
Figure 2-3 illustrates the LTE/SAE architecture in non-roaming scenarios. SAE is short for
System Architecture Evolution. For details about the architectures in roaming and non-
roaming scenarios, see section 4.2 "Architecture reference model" in 3GPP TS 23.401.
Figure 2-3 LTE/SAE architecture in non-roaming scenarios
MME: mobility management entity S-GW: serving gateway

SGSN: serving GPRS support node HSS: home subscriber server
PCRF: policy and charging rule function PDN Gateway: packet data network
gateway
IP multimedia subsystem (IMS) includes multiple network elements (NEs). These NEs
perform voice session control and multimedia negotiation between the calling and called UEs.
Function Architecture
Table 2-1 describes the basic functions of VoLTE.

eRAN
Table 2-1 Basic VoLTE functions

Function Description
Speech codec scheme During a VoLTE call, the UEs negotiate a speech codec scheme
and traffic model with the IMS. The commonly used codec scheme is Adaptive
Multirate (AMR). For details about its voice traffic model, see
3.1 Speech Codec Scheme and Traffic Model.
VoLTE voice policy During the attach procedure, the UE negotiates with the MME
selection and selects VoLTE as the voice policy. For details about voice
policy selection, see 3.2 VoLTE Voice Policy Selection.
Radio bearer Radio bearers with QoS class identifiers (QCIs) of 1 and 5 are
management set up between the calling and called UEs to carry
conversational voice and signaling, respectively. For details
about radio bearer management, see 3.3 Radio Bearer
Management.
Admission and The eNodeB performs admission and congestion control for
congestion control conversational voice (QCI 1) and signaling (QCI 5). For details
about admission and congestion control, see 3.4 Admission
and Congestion Control.
Dynamic scheduling and By default, the eNodeB performs dynamic scheduling and uses
power control power control policies that are suitable for dynamic scheduling.
For details about dynamic scheduling and power control, see
3.5 Dynamic Scheduling and Power Control.
UEs can perform VoLTE services after the preceding functions are enabled. Table 2-2
describes the features that help improve VoLTE performance such as capacity, coverage, and
voice quality.
Table 2-2 Enhanced VoLTE features/functions

Category Feature/Function Description
Name
Capacity Semi-persistent The eNodeB performs semi-persistent

enhanceme scheduling and power scheduling and uses suitable power control
nt control policies for UEs during talk spurts.
This feature applies only to voice services. For
details about semi-persistent scheduling and
power control, see 4.1.1 Semi-Persistent
Scheduling and Power Control.
The eNodeB performs dynamic scheduling and
uses suitable power control policies for UEs at
voice service setup and during silent periods.

eRAN

Name
Robust header ROHC compresses the headers of voice packets

compression (ROHC) to reduce air interface overheads.
details about how ROHC works for VoLTE, see
4.1.2 ROHC.
Coverage Transmission time Multiple TTIs are bound together for UEs with
improveme interval (TTI) bundling poor signal quality to transmit the same data.
nt This increases the once-off transmission
success rate.
This feature applies only to uplink voice
services. For details, see 4.2.1 TTI Bundling.
Robust header ROHC compresses the headers of voice packets

compression (ROHC) to reduce air interface overheads and increase
the once-off transmission success rate.
details about how ROHC works for VoLTE, see
4.2.2 ROHC.
Uplink RLC segmentation This feature restricts the transport block size
enhancement (TBS) in UL dynamic scheduling to control the
number of uplink RLC segments for VoLTE
packets. This restriction improves voice quality
when channel quality is poor. For details about
this feature, see 4.2.3 Uplink RLC
Segmentation Enhancement.
Quality Voice characteristic During uplink dynamic scheduling, the eNodeB

Improveme awareness scheduling adjusts the scheduling priorities of UEs based
nt on their waiting time and estimates the voice
volume to be dynamically scheduled in the
uplink. An independent inactivity timer is
configured for voice services. The purpose is to
improve voice quality, decrease the service
drop rate, and increase the proportion of
satisfied voice service users.
details about how UL delay-based dynamic
scheduling, UL VoLTE volume estimation for
dynamic scheduling, and independent
configuration for voice inactivity timer work
for VoLTE, see 4.3.1 Voice Characteristic
Awareness Scheduling.

eRAN

Name
Uplink compensation For each voice user, the eNodeB measures the
scheduling duration in which the user is not scheduled in
the uplink. If the duration reaches a threshold,
the eNodeB performs uplink compensation
scheduling for the UE. The purpose is to ensure
that uplink voice packets can be timely
transmitted, shorten their waiting time, and
reduce the number of packets discarded
because of the expiry of PDCP Discard Timer.
details, see 4.3.2 Uplink Compensation
Scheduling.
Voice-specific AMC The eNodeB sets a target IBLER for uplink

voice services.
details, see 4.3.3 Voice-Specific AMC.
Power Discontinuous reception With DRX, UEs enter the sleep state when data
saving (DRX) is not transmitted, saving UE power.
For details about how DRX works for VoLTE,
see 4.4 Power Saving.
Mobility Intra-frequency handover The eNodeB performs intra-frequency, inter-

managemen frequency, or inter-RAT handovers to transfer
t Inter-frequency handover UEs performing voice services to appropriate
Inter-RAT handover neighboring cells to maintain voice continuity.
For details about how mobility management
works for VoLTE, see 4.5 Mobility
Management.
Voice service performance can be evaluated on various dimensions. For details about voice
service performance evaluation, see 8 Voice Service Performance Evaluation.

eRAN
VoLTE Feature Parameter Description 3 Basic VoLTE Functions
3 Basic VoLTE Functions
The ENodeBAlgoSwitch.EutranVoipSupportSwitch parameter specifies whether to enable

VoLTE.
l When this parameter is set to ON(On) on an eNodeB, this eNodeB supports VoLTE and
allows the establishment, access, incoming handover, and reestablishment of the
dedicated bearer with a QCI of 1.
l When this parameter is set to OFF(Off)) on an eNodeB, this eNodeB does not support
VoLTE and does not allow the establishment, access, incoming handover, and
reestablishment of the dedicated bearer with a QCI of 1.

eRAN
3.1 Speech Codec Scheme and Traffic Model

The speech codec scheme is classified into AMR and G.7 series. VoLTE uses the AMR-based
speech codec scheme.
AMR
Adaptive Multi Rate (AMR) is an audio data compression scheme optimized for speech
coding and is now widely used in GERAN and UTRAN. AMR is classified into adaptive
multirate wideband (AMR-WB) and adaptive multirate narrowband (AMR-NB).
l AMR-NB has eight speech coding rates. They are 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4
kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s.
l AMR-WB has nine speech coding rates. They are 23.85 kbit/s, 23.05 kbit/s, 19.85 kbit/s,
18.25 kbit/s, 15.85 kbit/s, 14.25 kbit/s, 12.65 kbit/s, 8.85 kbit/s, and 6.6 kbit/s.
NOTE
AMR-NB herein corresponds to AMR in the protocol.
Figure 3-1 shows the voice service traffic model when AMR is used as the codec scheme for
VoLTE services. Whether AMR-WB or AMR-NB is used is negotiated between the UEs and
the IMS.
Figure 3-1 Voice traffic model
There are two VoLTE traffic states:
l Talk spurts
During talk spurts, the uplink of UEs transmits voice packets or the downlink of UEs
receives voice packets. Voice packets are transmitted at intervals of 20 ms, and the
packet size is determined by the speech coding rate.
l Silent period
During silent periods, the UE transmits silence insertion descriptor (SID) frames or
receives SID frames at intervals of 160 ms. For different AMR speech codec rates, the
SID frame sizes are all 56 bits.
The differences between talk spurts and silent period are as follows:
l The size of voice frames is greater than the size of SID frames.

eRAN
l The interval between neighboring voice frames is different from the interval between
SID frames.
The eNodeB distinguishes between voice frames and SID frames based on the preceding
differences.
G.7 Series
The widely used G.7 series standards include G.711, G.729, and G.726.
l G.711
G.711, also known as pulse code modulation (PCM), is primarily used in fixed-line
telephony. It supports a coding rate of 64 kbit/s.
l G.729
G.729, known for the high voice quality and low delay, is widely used in various
domains of data communications. It supports a coding rate of 8 kbit/s.
l G.726
G.726 supports coding rates of 16 kbit/s to 40 kbit/s. The most commonly used rate is 32
kbit/s. In actual application, voice packets are sent at intervals of 20 ms.
3.2 VoLTE Voice Policy Selection

UE capability and configurations on the MME determine whether a UE uses VoLTE.
However, VoLTE may be inappropriate for certain sites or regions. This case is termed as
VoLTE-prohibited scenario.
This section describes voice policy selection for UEs in common and VoLTE-prohibited
scenarios.
3.2.1 Common Scenarios
3.2.1.1 General Principles for Voice Policy Selection

During the UE attach and tracking area update (TAU) period, the MME selects a voice policy
based on the UE capability and configuration on the MME side. The MME then sends the UE
the voice policy contained in the Attach Accept and TAU Accept messages. During voice
policy selection, the MME selects a voice policy based on the following principles:
l If the UE supports only CSFB, the corresponding voice policy is CS Voice only.
l If the UE supports only VoLTE, the corresponding voice policy is IMS PS Voice only,
that is, VoLTE.
l If the UE supports both CSFB and VoLTE, the voice policy used before negotiation with
the MME is one of the following voice policies specified by operators during UE
registration:
– CS Voice only
That is, CSFB.
– IMS PS Voice only
That is, VoLTE.

eRAN
– Prefer CS Voice with IMS PS Voice as secondary

That is, CSFB takes precedence over VoLTE.
For details about the voice policy negotiation procedures between the UE and MME
when this policy is used, see Annex A.2 in 3GPP TS 23.221 V9.4.0.
– Prefer IMS PS Voice with CS Voice as secondary
That is, VoLTE takes precedence over CSFB.
Figure 3-2 and Figure 3-3 show the voice policy negotiation procedures between
the UE and MME when this policy is used. For details about the voice service
policy negotiation, see Annex A.2 in 3GPP TS 23.221 V9.4.0.
Figure 3-2 Procedures for voice policy selection (non-combined attach)

eRAN
Figure 3-3 Procedures for voice policy selection (combined attach)
3GPP Release 11 introduced VoLTE mobility capability decision, which further helps the
MME in selecting a VoLTE policy.
3.2.1.2 VoLTE Mobility Capability Decision
Figure 3-4 Signaling procedure of VoLTE mobility capability decision
1. During the UE attach period, the MME sends the UE Radio Capability Match Request
message to the eNodeB to query whether the UE has the VoLTE mobility capability.
2. If the eNodeB does not receive the UE radio capability message from the UE, the
eNodeB sends a UE Capability Enquiry message to the UE.
3. The UE reports its radio capability through the UE Capability Information message. For
details, see section 5.6.3 "UE Capability Transfer" in 3GPP TS 36.331 R10.

eRAN
4. If the eNodeB determines that the UE can ensure mobility after the UE performs VoLTE
services, the eNodeB replies the MME with the decision result through the UE Radio
Capability Match Response message.
The SupportS1UeCapMatchMsg option of the GlobalProcSwitch.ProtocolSupportSwitch
parameter specifies whether the eNodeB supports the VoLTE mobility decision.
l When the SupportS1UeCapMatchMsg(SupportS1UeCapMatchMsg) option is
selected, the UE can ensure mobility after the performing VoLTE services if the UE
meets any of the following conditions:
– The UE supports UTRAN and SRVCC from E-UTRAN to UTRAN.
– The UE supports GERAN and SRVCC from E-UTRAN to GERAN.
– The UE supports the PS domain of UTRAN-FDD (VoHSPA), SRVCC from the PS
domain to the CS domain of UTRAN-FDD, and SRVCC from the PS domain of
UTRAN-FDD to the CS domain of GERAN.
– The UE supports the PS domain of UTRAN-TDD (VoHSPA), SRVCC from the PS
domain to the CS domain of UTRAN-TDD, and SRVCC from the PS domain of
UTRAN-TDD to the CS domain of GERAN.
l When the SupportS1UeCapMatchMsg option is deselected, the eNodeB does not
perform VoLTE mobility capability decision. In this case, the eNodeB replies ERROR
INDICATION when receiving the UE RADIO CAPABILTY MATCH REQUEST
message. If the UE uses VoLTE but does not support SRVCC, VoLTE mobility cannot be
ensured.
NOTE
The UE RADIO CAPABILTY MATCH REQUEST message is introduced in 3GPP Release 11.
The MME informs the eNodeB of the MME's SRVCC capability in the Initial UE Context Setup
message.
l After the eNodeB obtains the MME's SRVCC capability, it also considers the MME's capability
while determining the preceding conditions. Otherwise, the eNodeB replies to the eNodeB that the
VoLTE mobility cannot be ensured.
l If the eNodeB is not informed of the MME's SRVCC capability, for example, the UE RADIO
CAPABILTY MATCH REQUEST message arrives at the eNodeB earlier than the Initial UE Context
Setup message, the eNodeB does not consider the MME's capability while determining UE voice
service continuity.
3.2.2 VoLTE-Prohibited Scenario

The E-UTRAN supports VoLTE after the IMS is deployed. However, a non-VoLTE solution
(such as CSFB) is used in the following scenarios because VoLTE is not appropriate for these
scenarios:
l Transmission delay is large.
Voice services have high requirements on end-to-end delay. Figure 3-5 shows the
relationship between end-to-end delay and perceived voice quality, as per ITU-T
Recommendation G.114. As shown in the figure, the end-to-end delay threshold to
achieve very satisfied user experience is 200 ms, and that to achieve satisfied user
experience is 275 ms. That is, VoLTE users become dissatisfied on voice quality when
the end-to-end delay exceeds 275 ms. The recommended packet delay budget for the Uu
interface is 80 ms, as per Table 6.1.7: Standardized QCI characteristics in section 6.1.7.2
"Standardized QCI characteristics" of 3GPP TS 23.203. The delay budget between the
EPC and eNodeB is 20 ms. If the transmission delay between the EPC and eNodeB is
greater than 20 ms, voice quality may not be guaranteed after VoLTE is deployed on the
eNodeB.

eRAN
Figure 3-5 Relationship between delay and voice quality
l Voice services are not allowed on certain frequency bands.

Certain operators expect that some frequency bands such as LTE TDD bands do not
serve voice service but serve only data services.
MMEs are required in the preceding scenarios to prohibit VoLTE in certain areas.
Operators can allocate dedicated tracking area identities (TAIs) to regions. After setting
dedicated TAIs on the MME, areas in such scenarios use CSFB instead of VoLTE. During the
Attach and tracking area update (TAU), UEs negotiate or re-negotiate with the MME about
voice policies. Voice policy negotiation between the UE and the MME is transparent to the
eNodeB.
You can turn off the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch for eNodeBs

with dedicated TAIs working in the preceding scenarios. For eNodeBs with non-dedicated
TAIs, you can select the VoipHoControlSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter and configure the VoLTE handover blacklist
in the EutranVoipHoBlkList MO. This prevents UEs performing voice services from
handing over to these eNodeBs or reestablished on the eNodeBs.
After the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch is turned off and VoLTE is

disabled for a specific tracking area on the MME, the statistics about VoLTE-related KPIs
such as E-RAB Setup Success Rate (VoIP) become 0.
The following is an example.
The MCC and MNC of a network are 001 and 02, respectively. In this network, tracking area
code (TAC) 1 corresponds to eNodeB A, and the other TACs correspond to eNodeBs B to Z.
CSFB is to be used in the area that is labeled TAC 1.
The configurations are as follows:
1. On the MME, configure CSFB for TAC1.

eRAN
2. On eNodeB A, run the following command:

MOD ENODEBALGOSWITCH:EutranVoipSupportSwitch=OFF;
3. (Optional) On eNodeBs B to Z, perform the following command:

MOD ENODEBALGOSWITCH:EutranVoipSupportSwitch=ON;
4. On eNodeBs B to Z, run the following command:

MOD ENODEBALGOSWITCH:HoAlgoSwitch=VoipHoControlSwitch-1;
5. On eNodeBs B to Z, run the following command:

ADD EUTRANVOIPHOBLKLIST: Mcc="001", Mnc="02", Tac=TAC1;
NOTE
In the preceding VoLTE-prohibited scenarios, when a UE performing voice services triggers an intra-
RAT intra-frequency or inter-frequency handover, the eNodeB determines whether to filter out cells in
the VoLTE handover blacklist (specified by the EutranVoipHoBlkList MO) depending on the settings
of the VoipHoControlSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter.
According to current 3GPP specifications, voice policies can be configured only on a TAC basis on the
MME. ENODEBALGOSWITCH.EutranVoipSupportSwitch and
ENODEBALGOSWITCH.HoAlgoSwitch.VoipHoControlSwitch parameters for the eNodeB are used
to support the configuration of TAC-based voice policies on the MME side.
For details about the VoLTE handover blacklist and target cell selection procedures for VoLTE
handovers, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
When the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch is turned on, dedicated bearer for
services with QCI of 1 can be set up for the eNodeB. When this switch is turned off, dedicated bearer for
services with QCI of 1 is not allowed to be set up for the eNodeB.
3.3 Radio Bearer Management
3.3.1 Radio Bearer Setup

From the perspective of eNodeBs, voice session setup includes the following procedures:
RRC connection setup, QCI 5 radio bearer setup, and QCI 1 radio bearer setup. Figure 3-6
shows the process of setting up a voice session between the calling and called UEs.

eRAN
Figure 3-6 Voice session setup process
The process is as follows:

1. In the RRC connection setup procedure, a radio connection is set up between a UE and
an eNodeB so that the UE can send service requests and data packets to upper-layer NEs.
2. In the EPS bearer setup (QCI 5) procedure, a QCI 5 radio bearer is set up for signaling
exchange between the UE and the IMS.
3. After the QCI 5 radio bearer is set up, the calling UE and the IMS perform Session
Initiation Protocol (SIP) negotiation on the speech codec scheme, IP address, port
number, called UE's information, and other information.
4. In the EPS bearer establishment (QCI 1) procedure, a QCI 1 radio bearer is set up to
carry voice packets.

eRAN
NOTE
If VoLTE is determined as the voice solution for a UE according to negotiation with the MME, a QCI 5
radio bearer is set up when the UE enters RRC_CONNECTED mode, irrespective of whether the UE is
performing a voice service or not.
When ENodeBAlgoSwitch.EutranVoipSupportSwitch is set to OFF(Off), the eNodeB cannot set up
QCI 1 radio bearers (the eNodeB sends to the EPC a message containing the cause value "Not supported
QCI Value") but can set up QCI 5 radio bearers.
If the UE initiates a conversational video service, a radio bearer (QCI 2) is also set up in the preceding
procedures.
eNodeBs provide the following QCI 1-specific timer settings:
ENodeBConnStateTimer.S1MsgWaitingTimerQci1,
ENodeBConnStateTimer.X2MessageWaitingTimerQci1,
ENodeBConnStateTimer.UuMessageWaitingTimerQci1,
RrcConnStateTimer.UeInactiveTimerQci1, and CellStandardQci.TrafficRelDelay. For details about
these parameters, see Connection Management Feature Parameter Description.
3.3.2 Radio Bearer QoS Management

Radio bearer QoS management for voice services complies with the Policy and Charging
Control architecture defined in 3GPP specifications.
Figure 3-7 shows the architecture of radio bearer QoS management for voice services.
Figure 3-7 Architecture of radio bearer QoS management
The dedicated bearers for voice services perform QoS parameter control based on the
dynamic PCC rule as follows:
1. The IMS (P-CSCF) sends QCI information to the PCRF over the Rx interface.

eRAN
2. Based on the received QCI information and subscription information, the PCRF
generates a QoS rule (including the following key QoS parameters: QCI, ARP, GBR, and
MBR) and sends the rule to the P-GW over the Gx interface.
3. Based on the QoS rule sent from the PCRF, the P-GW instructs the S-GW, MME, and
eNodeB to set up EPS bearers. Services of different QoS requirements are carried by
radio bearers with different QCIs. According to 3GPP specifications, the QCIs for
conversational voice, conversational video, and IMS signaling are 1, 2, and 5,
respectively. Table 3-1 lists their QoS parameters. QoS parameters are set in
StandardQci MOs, and the Radio Link Control (RLC) modes for setting up
conversational voice, conversational video, and IMS signaling E-RABs are specified by
the RlcPdcpParaGroup.RlcMode parameter. For details, see 3GPP 23.203.
Table 3-1 QoS parameters for conversational voice, conversational video, and IMS
signaling
QC Resource Priorit Delay Packet Loss Service Type

I Type y Rate
1 GBR 2 100 ms 10-2 Conversational

voice
2 GBR 4 150 ms 10-3 Conversational

video
5 Non-GBR 1 100 ms 10-6 IMS signaling
NOTE
A smaller priority value indicates a higher priority.

For details about QCIs and RLC modes, see QoS Management Feature Parameter
Description.
3.4 Admission and Congestion Control
3.4.1 Overview
This section describes how the basic features LBFD-002023 Admission Control and
LBFD-002024 Congestion Control work for VoLTE. For details about the two features, see
Admission and Congestion Control Feature Parameter Description.
The eNodeB performs admission and congestion control for conversational voice (QCI of 1)
and IMS signaling (QCI of 5) separately.
3.4.2 Load Monitoring

Load monitoring provides decision references for admission and congestion control. The
eNodeB monitors various resources in a cell to obtain the usage of physical resource blocks
(PRBs), QoS satisfaction rates of GBR services, and resource insufficiency indicators. In this
way, the eNodeB can know the current status of a cell.

eRAN
Conversational Voice (QCI 1)

For the method of calculating the QoS satisfaction rate of QCI 1, see Admission and
Congestion Control Feature Parameter Description.
IMS Signaling (QCI 5)

QCI 5 indicates non-GBR services. There is no need to calculate their QoS satisfaction rates.
3.4.3 Admission Control

Admission control determines whether to admit a GBR service (new service or handover
service) based on the cell load reported by the load monitoring module. The cell load is
represented by the PRB usage, QoS satisfaction rates of GBR services, and resource
insufficiency indicators. For details, see Admission and Congestion Control Feature

The admission control of GBR services with a QCI of 1is performed based on load-based
decisions.

Admission control for non-GBR services (QCI 5) is not based on load. If SRS and PUCCH
resources are successfully allocated, non-GBR services (QCI 5) are directly admitted.
NOTE
The allocation of SRS resources needs to be considered during admission control of non-GBR services
(QCI 5) only when the eNodeB is configured with the LBBPc. The services can be admitted only after
SRS resources are successfully allocated.
Even if the PreemptionSwitch option under the CellAlgoSwitch.RacAlgoSwitch parameter

is selected, IMS signaling (QCI 5) cannot be preempted.
3.4.4 Congestion Control

When the network is congested, the eNodeB preferentially releases low-priority GBR services
to free up resources for other services. For details, see Admission and Congestion Control
Feature Parameter Description.

The eNodeB monitors PRB usage and QoS satisfaction rate to evaluate load status. When the
eNodeB determines that a cell is congested, the eNodeB rejects service access requests and
triggers congestion control to decrease load. The congestion threshold is specified the
CellRacThd.Qci1CongThd parameter. For details about how to set this parameter, see
Admission and Congestion Control Feature Parameter Description.

N/A

eRAN
3.5 Dynamic Scheduling and Power Control
3.5.1 Dynamic Scheduling

This section describes how the optional feature LOFD-00101502 Dynamic Scheduling works
for VoLTE. For details about the principles and engineering guidelines of dynamic scheduling,
see Scheduling Feature Parameter Description.
Overview
Voice services have demanding requirements on delay. Therefore, the Huawei scheduler
optimizes the handling of voice service priorities to ensure voice service QoS. When VoLTE
is deployed, it is recommended that the enhanced proportional fair (EPF) scheduling policy be
used in the uplink and downlink. That is:
l The CellAlgoSwitch.UlschStrategy parameter is set to ULSCH_STRATEGY_EPF.
l The CellAlgoSwitch.UlschStrategy parameter is set to DLSCH_PRI_TYPE_EPF.
On commercial LTE networks, the EPF scheduling policy is used in the uplink and downlink
by default.
For details about dynamic scheduling for voice services, see Scheduling Feature Parameter
Description.
Uplink Dynamic Scheduling

When uplink dynamic scheduling uses the enhanced proportional fair (EPF) algorithm, the
priority of conversational voice (QCI 1) is lower than the priorities of data retransmitted using
HARQ, signaling radio bearer 1 (SRB1), SRB2, and IMS signaling (QCI 5), but higher than
the priorities of other initially transmitted data.
It is recommended that the UlLast2RetransSchOptSwitch option of the
CELLALGOSWITCH.UlSchSwitch parameter be selected when dynamic scheduling is
used and there are voice services. Selecting this option decreases the packet loss rate of voice
services and improves user experience on voice services.
Uplink voice preallocation is introduced to reduce the delay of voice services. When the
number of UEs in a cell exceeds 50, the eNodeB preallocates uplink resources only to UEs
performing voice services. When the number of UEs in a cell is less than or equal to 50, the
eNodeB retains the existing uplink preallocation or uplink smart preallocation mechanism for
all UEs. For details, see Scheduling Feature Parameter Description. Uplink voice
preallocation is controlled by the UlVoipPreAllocationSwtich option of the
CellAlgoSwitch.UlEnhencedVoipSchSw parameter.
Downlink Dynamic Scheduling

When dynamic scheduling is used, the scheduling priority is related to whether the
LOFD-001109 DL Non-GBR Packet Bundling feature is enabled:
l If the LOFD-001109 DL Non-GBR Packet Bundling feature is not enabled: When the
EPF downlink scheduling algorithm is used, the priority for scheduling voice packets
(QCI of 1) is lower than that for scheduling common control messages, user-level control

eRAN
messages, IMS signaling (QCI of 5), HARQ retransmission data, and RLC AM status
report. However, the priority for scheduling voice packets (QCI of 1) is higher than that
for scheduling initial transmission data.
l If the LOFD-001109 DL Non-GBR Packet Bundling feature is enabled: The priority for
scheduling voice packets (QCI of 1) is no longer higher than that for scheduling initial
transmission data. Instead, the eNodeB sorts overall priorities.
When dynamic scheduling is used, the MCS selection policy depends on the value for the
VoipTbsBasedMcsSelSwitch option of the CellAlgoSwitch.DlSchSwitch parameter.
l When this option is selected, the eNodeB checks the number of online VoIP subscribers
and IBLER and then determines whether to apply the TBS-based MCS selection function
to voice services. TBS is short for transport block size. If the function takes effect on
voice services, the eNodeB makes decisions based on the packet size during a voice call
to select a relatively low MCS while ensuring that the number of RBs remains
unchanged. In this way, HARQ retransmission and user delay are reduced.
l When this option is deselected, the eNodeB determines the MCS for voice services based
on the downlink CQI adjustment algorithm. For details about the downlink CQI
adjustment algorithm, see Scheduling Feature Parameter Description.
When dynamic scheduling is used for voice services, it is recommended that the
DlRetxTbsIndexAdjOptSwitch of the CellAlgoSwitch.CqiAdjAlgoSwitch parameter be
turned on to reduce the voice packet loss rate and improve voice user experience. For details
about this switch, see Scheduling Feature Parameter Description.
3.5.2 Power Control in Dynamic Scheduling

Power control policies for voice services in dynamic scheduling are the same as those for data
services. For details about voice service power control policies when dynamic scheduling is
used for voice services, see Power Control Feature Parameter Description.

eRAN
VoLTE Feature Parameter Description 4 Enhanced VoLTE Features
4 Enhanced VoLTE Features
Operators can enable features described in this chapter to improve VoLTE performance such
as capacity and coverage.

eRAN
4.1 Capacity Enhancement

The following features can be enabled to increase capacity for voice services:
l Semi-persistent scheduling and power control
When the capacity is low due to high PDCCH overheads, these features can be used to
reduce PDCCH overheads and therefore increase the maximum number of VoLTE users
or the throughput of data services (provided that the number of VoLTE users remains
unchanged).
l Uplink delay-based dynamic scheduling
When there are too many VoLTE users, this feature can be used to improve the
performance of cell edge users (CEUs) by sacrificing the performance of cell center
users (CCUs) and increase the proportion of satisfied VoLTE users.
l ROHC
By compressing the headers of voice packets, this feature reduces air interface overheads
and increase the maximum number of VoLTE users or the throughput of data services
(provided that the number of VoLTE users remains unchanged).
4.1.1 Semi-Persistent Scheduling and Power Control
4.1.1.1 Semi-Persistent Scheduling

This section describes the LOFD-001016 VoIP Semi-persistent Scheduling feature.
Introduction
When dynamic scheduling is used for voice services, time-frequency resource or MCS is
updated through the PDCCH every 20 ms. This consumes a large number of PDCCH
resources. Figure 4-1 shows the resource allocation for dynamic scheduling.
Figure 4-1 Resource allocation for dynamic scheduling

eRAN
Huawei introduces the VoLTE semi-persistent scheduling feature for small-packet services
that are periodically transmitted such as VoLTE. Before entering talk spurts, the eNodeB
allocates fixed resources to UEs through the PDCCH message. Before exiting talk spurts or
releasing resources, the UEs do not need to apply for resource allocation from the PDCCH
again, thereby saving PDCCH resources. Figure 4-2 shows the resource allocation for semi-
persistent scheduling.
After delivering the the PDCCH message, the eNodeB transmits voice packets in an interval
of 20 ms.
Figure 4-2 Resource allocation for semi-persistent scheduling
The eNodeB configures semi-persistent scheduling parameters for UEs supporting semi-
persistent scheduling in the RRC Connection Reconfiguration message during DRB setup for
QCI of 1. The eNodeB activates UL or DL semi-persistent scheduling for UEs when UEs
meet the UL or DL semi-persistent scheduling activation conditions. The eNodeB instructs
UEs to activate UL or DL semi-persistent scheduling through the PDCCH Order notification.
For details about the PDCCH Order format, see section 9.2 "PDCCH/EPDCCH validation for
semi-persistent scheduling" in 3GPP TS 36.213 V12.3.0.

eRAN
Effect Period
Figure 4-3 Semi-persistent scheduling effect period
In talk spurt, uplink or downlink semi-persistent scheduling takes effect when all the
following conditions are met:
l The following options are selected:
– The SpsSchSwitch option of the CELLALGOSWITCH.UlSchSwitch parameter
– The SpsSchSwitch option of the CELLALGOSWITCH.DlSchSwitch parameter.
l The UE supports semi-persistent scheduling.
l The UE performing voice services is in uplink or downlink talk spurts.
l The uplink or downlink for the UE has only one dedicated bearer for services with QCI
of 1. For the uplink, there is no data transmission on the data bearer.
l RLC segmentation is not performed in the uplink or downlink for the UE.
l When ROHC is enabled, the uplink or downlink ROHC is in the stable compression
state, that is, the size of the ROHC header is relatively stable.
eNodeBs use dynamic scheduling in the following scenarios during talk spurts:
l Transmission of large packets, such as channel-associated signaling or uncompressed
packets generated when the ROHC feature updates contexts
l Downlink semi-persistent retransmission
l Uplink semi-persistent adaptive retransmission
NOTE
When the UE uses semi-persistent scheduling, the highest MCS index is only 15.
Uplink Semi-Persistent Scheduling

During semi-persistent scheduling, the eNodeB determines the modulation and coding
scheme (MCS) and the number of PRBs based on the following items:
l Voice packet size (ROHC disabled) or size of compressed voice packets (ROHC
enabled)

eRAN
l Wideband signal to interference plus noise ratio (SINR)
After semi-persistent scheduling is activated, the UE periodically sends data and the eNodeB
periodically receives data using the semi-persistently allocated resources. In addition, the
eNodeB checks whether the MCS allocated in semi-persistent scheduling matches the current
channel status. If the MCS does not match the current channel status, the eNodeB activates
semi-persistent scheduling again.
After the eNodeB triggers a UE to enter uplink semi-persistent scheduling, the

logicalChannelSR-Mask-r9 IE in the RRC Reconfiguration message instructs the UE not to
send scheduling requests over the radio bearers for QCI of 1. This reduces UE power
consumption. The CellAlgoSwitch.SrMaskSwitch parameter controls this function. It is
recommended that both this function and uplink semi-persistent scheduling be enabled. This
function takes effect only on UEs that comply with 3GPP Release 9 or later.
When the number of empty packets received by the eNodeB in semi-persistent scheduling
exceeds the value of CellAlgoSwitch.SpsRelThd, the eNodeB automatically releases semi-
persistently allocated resources.
Downlink Semi-Persistent Scheduling

Downlink data transmitted in semi-persistent scheduling mode has a lower priority than
common control (such as broadcast and paging) information but a higher priority than UE-
specific control information and user-plane data. The eNodeB periodically sends data and the
UE periodically receives data using the semi-persistently allocated resources.
During semi-persistent scheduling, the eNodeB determines the MCS and the number of PRBs
based on the following items:
l Voice packet size (ROHC disabled) or size of compressed voice packets (ROHC
enabled)
l Wideband CQI
The UE and eNodeB then receive and send data on the allocated resources.
After semi-persistent scheduling is activated, the eNodeB checks whether the MCS allocated
in semi-persistent scheduling matches the current channel status. If the MCS does not match
the current channel status, the eNodeB activates semi-persistent scheduling again.
According to 3GPP TS 36.321 and 3GPP TS 36.331, the eNodeB reserves HARQ processes
for downlink semi-persistent scheduling while configuring semi-persistent scheduling for
UEs.
When the eNodeB configures semi-persistent scheduling for UEs, the PUCCH requires
available semi-persistent code channel for HARQ. Otherwise, the eNodeB does not configure
semi-persistent scheduling for UEs.
4.1.1.2 Power Control in Semi-Persistent Scheduling

This section describes voice service power control policies when semi-persistent scheduling is
used for VoLTE. For details about power control, see Power Control Feature Parameter
Description.

eRAN
Power Control in Uplink Semi-Persistent Scheduling

When semi-persistent scheduling is used for VoLTE in the uplink, closed-loop power control
for the physical uplink shared channel (PUSCH) can be enabled or disabled by setting the
CloseLoopSpsSwitch option of the CellAlgoSwitch.UlPcAlgoSwitch parameter.
l If the CloseLoopSpsSwitch option is selected, the eNodeB adjusts transmit power for
the PUSCH based on the measured IBLER of voice services.
l If the CloseLoopSpsSwitch option is deselected, the eNodeB uses open-loop (not
closed-loop) power control for the PUSCH.
Power Control in Downlink Semi-Persistent Scheduling

When semi-persistent scheduling is used for VoLTE in the downlink, power control for the
PDSCH can be enabled or disabled by setting the PdschSpsPcSwitch option of the
CellAlgoSwitch.DlPcAlgoSwitch parameter.
l If the PdschSpsPcSwitch option is selected, the eNodeB periodically adjusts the
PDSCH transmit power for UEs based on the measured IBLER.
l If the PdschSpsPcSwitch option is deselected, power control for the PDSCH in semi-
persistent scheduling is not used. Instead, the eNodeB transmit power is evenly shared
by each RB.
4.1.2 ROHC
This section describes how the optional feature LOFD-001017 RObust Header Compression
(ROHC) works for VoLTE. For details about this feature, see ROHC Feature Parameter
Description.
ROHC provides an efficient header compression mechanism for data packets transmitted on
radio links to solve the problems of high bit error rates (BERs) and long round trip time
(RTT). ROHC helps reduce header overheads, lower the packet loss rate, and shorten
response time.
In the current version, ROHC is used to compress the headers of only voice packets (QCI of 1
and PTT QCI services), as shown in Figure 4-4. ROHC reduces the packet size and physical
resource block (PRB) overheads. When PRBs are insufficient, ROHC helps increase system
capacity.
Figure 4-4 ROHC for VoLTE
After deploying VoLTE, operators can enable or disable ROHC by setting the
PdcpRohcPara.RohcSwitch parameter. ROHC is an extensible framework consisting of

eRAN
different profiles for data streams compliant with different protocols. Profiles define the
compression modes for streams with different types of protocol headers. Voice services use
profiles 0x0001 and 0x0002.
The ROHC compression efficiency varies with the ROHC operating mode and variations in
the dynamic part of packet headers at the application layer. A header can be compressed to a
size as small as 1 byte, which efficiently reduces the voice packet size.
4.2 Coverage Improvement

Operators can enable the following features to improve voice service coverage in poor
coverage scenarios:
l TTI Bundling
l ROHC
l Uplink RLC segmentation enhancement
4.2.1 TTI Bundling

This section describes the principles of the optional feature LOFD-001048 TTI Bundling and
how this feature works for VoLTE.
4.2.1.1 Overview
TTI bundling enables a data block to be transmitted in four consecutive TTIs, which are
bound together and treated as the same resource. Different HARQ redundancy versions of the
same data block are transmitted in different TTIs. TTI bundling makes full use of HARQ
combining gains and reduces the number of retransmissions and RTT.
When the UE's channel quality is poor and transmit power is limited, TTI bundling increases
the cell edge coverage of the PUSCH by about 1 dB. The gains produced by this feature can
be observed when voice quality is maintained at a certain level, for example, when the mean
opinion score (MOS) is 3.
The TtiBundlingSwitch option of the CellAlgoSwitch.UlSchSwitch parameter determines
whether to enable TTI bundling. When this option is selected, the eNodeB determines
whether to activate TTI bundling based on the channel quality. After activating TTI bundling,
the eNodeB determines the number of PRBs and selects an MCS based on the channel quality
and the amount of data to be transmitted.
According to section 8.6.1 "Modulation order and redundancy version determination" in
3GPP TS 36.213 V10.1.0, when TTI bundling is enabled, the resource allocation size is
restricted to a maximum of three PRBs and the modulation scheme must be QPSK. Therefore,
the selected MCS index cannot be greater than 10. After TTI bundling is enabled, the
maximum available TBS is as large as 504 bits. Voice services are delay-sensitive. If higher-
layer data is not transmitted within the specified delay budget, voice quality deteriorates. To
prevent this, TTI bundling is disabled when a G.711-defined high speech codec rate is used.
4.2.1.2 Principles
Entry into the TTI Bundling State

In eRAN8.1, the CellAlgoSwitch.TtiBundlingTriggerStrategy parameter is introduced.

eRAN
l When the TtiBundlingTriggerStrategy parameter is set to

SERVICE_VOIP(SERVICE_VOIP), TTI bundling applies to only VoLTE. Under this
parameter setting, the conditions for entering the TTI bundling state are as follows:
– The TtiBundlingSwitch of the eNodeB is turned on.
– The UE supports TTI bundling.
– The UE has only one QCI 1 dedicated bearer and stays in the talk spurts state. In
addition, the UE does not have data to transmit on the data bearer.
– The UL power of the UE is limited, and the number of PRBs is less than or equal to
3.
– The measured SINR is less than the target SINR for multiple consecutive times.
The number of consecutive times is specified by the
CellAlgoSwitch.StatisticNumThdForTtibTrig.
If the UE meets all these conditions, the eNodeB sends the UE an RRC Connection
Reconfiguration message, instructing the UE to enter the TTI bundling state.
l When the TtiBundlingTriggerStrategy parameter is set to
SERVICE_MULTIAPP(SERVICE_MULTIAPP), TTI bundling can apply to VoLTE
or a combination of VoLTE and data. Under this parameter setting, the conditions for
entering the TTI bundling state are as follows:
– The TtiBundlingSwitch of the eNodeB is turned on.
– The UE supports TTI bundling.
– The UE has a QCI 1 dedicated bearer.
– The UL power of the UE is limited, and the number of PRBs is less than or equal to
3.
– The measured SINR is less than the target SINR for multiple consecutive times.
The number of consecutive times is specified by the
CellAlgoSwitch.StatisticNumThdForTtibTrig.
If the UE meets all these conditions, the eNodeB sends the UE an RRC Connection
Reconfiguration message, instructing the UE to enter the TTI bundling state.
The processing in versions earlier than eRAN8.1 is the same as that when the
TtiBundlingTriggerStrategy parameter is set to SERVICE_VOIP(SERVICE_VOIP) in
eRAN8.1.
Data Block Transmission

For the UE in the TTI bundling state, the eNodeB determines the number of PRBs and MCS
based on channel quality and the amount of data to transmit. Then, the eNodeB transmits data
blocks.
As shown in Figure 4-5 , the UE transmits identical data within four consecutive TTIs in a
bundle and performs HARQ retransmission also within four TTIs in a bundle. The
retransmission operates in synchronous non-adaptive mode. Four uplink subframes in PHICH
carry one ACK/NACK message. The HARQ retransmission interval is changed from 8 TTIs
(Normal HARQ RTT) to 16 TTIs (Bundle HARQ RTT).
Take the transmission of a data block as an example. Assume that the UE transmits the data
block in a bundle of TTIs, among which the last TTI is numbered N. The eNodeB sends an
ACK or NACK as feedback to the UE in the (N + 4)th TTI. Based on the feedback, the UE
determines whether a retransmission is required. If it is required, the UE retransmits the data
block in the (N + 13)th through (N + 16)th TTIs.

eRAN
When the UE is in the TTI bundling state, the maximum number of uplink HARQ
retransmissions is specified by the CellAlgoSwitch.TtiBundlingHarqMaxTxNum parameter.
Figure 4-5 TTI bundling
In the TTI bundling state, the number of RLC segments of a voice packet cannot be greater
than the value of the CellAlgoSwitch.TtiBundlingRlcMaxSegNum parameter. The number is
4 in Figure 4-6.
Figure 4-6 Collaboration between TTI bundling and RLC segmentation
When the UE is located at the cell edge, RLC segmentation in collaboration with TTI
bundling produces fewer RLC segments than pure RLC segmentation, reducing PDCCH
overheads.
Exit from TTI Bundling

When the measured SINR is greater than the sum of the target SINR and the
CellAlgoSwitch.HystToExitTtiBundling parameter value for multiple consecutive times, the
eNodeB instructs the UE to exit the TTI bundling state through an RRC Connection
Reconfiguration message. The number of consecutive times is specified by the
StatisticNumThdForTtibExit parameter.
The eNodeB does not instruct the UE to exit the TTI bundling state even when the UE has
data to transmit on the default bearer, needs to set up a new dedicated bearer, or stops the
voice service (QCI 1). The eNodeB instructs the UE to exit the TTI bundling state when the
UE meets the exit conditions, experiences handover or service drop, or needs to reestablish a
new connection.
4.2.2 ROHC
This section describes how the optional feature LOFD-001017 RObust Header Compression
(ROHC) works for VoLTE. For details about this feature, see ROHC Feature Parameter
Description.

eRAN
ROHC can compress the RTP, UDP, or IP header of a voice packet, thereby reducing the size
of the entire packet. ROHC results in a higher probability of correctly transmitting voice
packets with fewer segments and enhances the edge coverage for voice services.
4.2.3 Uplink RLC Segmentation Enhancement

This section describes how uplink RLC segmentation enhancement works for VoLTE.
The number of Uplink RLC segments is dependent on the TBS determined by UL scheduling.
The smaller the TBS, the large the number of uplink RLC segments. When channel quality is
poor and UL power is limited, a small TBS results in a large number of uplink RLC segments,
which causes:
l Long delay of voice packets
l Uplink voice packet loss (because voice packets wait in the UE buffer so long that the
packet discard timer expires)
l Large overhead of RLC and MAC headers
l Large consumption of control channel elements (CCEs) and resource blocks (RBs) by
UL dynamic scheduling of VoLTE services
Uplink RLC segmentation enhancement restricts the TBS in UL dynamic scheduling to

control the number of uplink RLC segments for voice packets. This restriction improves voice
quality when channel quality is poor.
The CellAlgoSwitch.UlVoipRlcMaxSegNum parameter is introduced to control the

maximum number of uplink RLC segments for UEs not in the TTI bundling state.
l When the number of uplink RLC segments is less than or equal to the value of the
CellAlgoSwitch.UlVoipRlcMaxSegNum parameter, the number is not restricted.
l When the number of uplink RLC segments is greater than the value of the
CellAlgoSwitch.UlVoipRlcMaxSegNum parameter, the number is restricted. Based on
the voice packet size and the configured maximum number of RLC segments, a
minimum TBS is guaranteed in UL dynamic scheduling so that the number of uplink
RLC segments decreases to this maximum number.
This function takes effect when all the following conditions are met:
l The CellAlgoSwitch.UlVoipRlcMaxSegNum parameter is set to a none-zero value.

l The GLOBALPROCSWITCH.LcgProfile parameter is set to LCG_PROFILE_0 or
LCG_PROFILE_2.
This function does not take effect when one of the following conditions is met:
l The CellAlgoSwitch.UlVoipRlcMaxSegNum parameter is set to 0.

l The GLOBALPROCSWITCH.LcgProfile parameter is set to LCG_PROFILE_1.
l The UE enters the TTI bundling state.
NOTE
This function applies only to services with QCI of 1.

When the CellAlgoSwitch.UlVoipRlcMaxSegNum parameter is set to the recommended value, this
function increases the MOS of VoIP users who do not support TTI bundling by about 0.3 in uplink weak
coverage areas.

eRAN
4.3 Quality Improvement
4.3.1 Voice Characteristic Awareness Scheduling

This section describes LOFD-081229 Voice Characteristic Awareness Scheduling, involving
uplink delay-based dynamic scheduling, estimation of uplink VoLTE volume for dynamic
scheduling, and independent configuration for voice inactivity timer.
Uplink Delay-based Dynamic Scheduling

For uplink delay-based dynamic scheduling, the eNodeB prioritizes voice packets based on
their waiting times. Sorting scheduling priorities based on delay for voice services brings
balanced scheduling sequence. This helps improve voice quality. Specifically, voice quality
improves for UEs far from center with poor channel quality. This feature increases the user
satisfaction rate of UEs with voice services in scenarios where voice service load is high.
Figure 4-7 shows the difference before and after uplink delay-based dynamic scheduling is
enabled.
Figure 4-7 Difference before and after uplink delay-based dynamic scheduling is enabled.
A longer wait time indicates a higher scheduling priority. When the

CellAlgoSwitch.UlDelaySchStrategy parameter is set to VOIP_DELAYSCH(VoIP Service
Delay Scheduling), uplink delay-based dynamic scheduling for VoLTE is used.
Uplink VoLTE Volume Estimation for Dynamic Scheduling

The eNodeB can obtain the accurate downlink service volume but cannot obtain the accurate
uplink service volume.
Therefore, uplink VoLTE volume estimation for dynamic scheduling is introduced to allow
the eNodeB to perform the uplink estimation based on the VoLTE model and uplink
scheduling intervals so that scheduling can be completed in one time:
l During talk spurts, the eNodeB estimates the number of voice packets in the UE buffer
based on their uplink scheduling intervals and then calculates the volume of voice
packets based on the size of a voice packet.
l During silent periods, the eNodeB takes the size of a voice packet as the uplink VoLTE
volume for dynamic scheduling.
Uplink VoLTE volume estimation for dynamic scheduling makes the calculation of uplink
service volume more accurate and therefore shortens voice packet delays. This function can

eRAN
improve voice quality when the cell is heavily loaded and DRX is enabled. Figure 4-8 shows
the principles.
Figure 4-8 Uplink VoLTE Volume Estimation for Dynamic Scheduling
Uplink VoLTE volume estimation for dynamic scheduling is controlled by the

UlVoLTEDataSizeEstSwitch option of the CellAlgoSwitch.UlEnhencedVoipSchSw
parameter.
Independent Configurations for the UE Inactivity Timer for Voice Services

When a called UE does not answer the call, the calling UE is released after the UE inactivity
timer expires. This may interrupt the session.
l In dynamic DRX scenarios, the RrcConnStateTimer.UeInactivityTimerDynDrx
parameter specifies the length of the UE inactivity timer. The default and recommended
values of this parameter are large and therefore do not cause call setup failures in the
preceding scenario.
In other scenarios, with independent configuration for voice inactivity timer, the UEs can
distinguish voice and non-voice scenarios. That is, the length of the UE inactivity timer
can be independently configured to avoid the preceding negative impact. When the
CELLALGOSWITCH.UEInactiveTimerQCI1Switch parameter is set to ON(On), the
RrcConnStateTimer.UeInactiveTimerQci1 parameter takes effect. Otherwise, the
RrcConnStateTimer.UeInactiveTimerQci1 parameter does not take effect. It is
recommended that the value of the RrcConnStateTimer.UeInactiveTimerQci1
parameter be greater than the active connection release timer length when the called
party of the core network does not respond.
4.3.2 Uplink Compensation Scheduling

This section describes LBFD-081104 UL Compensation Scheduling.
Sending uplink data is dependent on the scheduling requests (SRs) reported by UEs. If an
eNodeB experiences missing SR detection, the eNodeB may not perform scheduling in a

eRAN
timely manner. This may extend the voice packet waiting delay or cause timeout-triggered
packet loss. Figure 4-9 shows the situation before uplink compensation scheduling is enabled.
Figure 4-9 Uplink compensation scheduling not enabled
Uplink compensation scheduling is a technique in which the eNodeB identifies voice users
and, for each voice user, measures the duration in which the user is not scheduled in the
uplink. If the duration reaches a threshold, the eNodeB sends a UL Grant to the UE to ensure
that uplink voice packets can be timely transmitted. This way, this feature shortens the waiting
time of voice packets and reduces the number of packets discarded because of the expiry of
PDCP Discard Timer. Figure 4-10 shows the situation after uplink compensation scheduling
is enabled.
Figure 4-10 Uplink compensation scheduling enabled
This feature is controlled by the UlVoipSchOptSwitch option of the

CellAlgoSwitch.UlEnhencedVoipSchSw parameter.

eRAN
4.3.3 Voice-Specific AMC

This section describes LBFD-081105 Voice-Specific AMC.
For details about the principles and engineering guidelines of adaptive modulation and coding
(AMC), mainly MCS selection for uplink dynamic scheduling, see Scheduling Feature
The eNodeB adjusts SINRs for UEs to be dynamically scheduled in the uplink based on the
configured uplink target IBLER and then preliminarily selects MCSs for the UEs.
To reduce the uplink VoLTE packet loss rate and VoLTE packet delay, users can set different
target uplink IBLER values for VoLTE and data services.
l The CellAlgoSwitch.SinrAdjustTargetIbler parameter specifies the target uplink IBLER
value for data services.
l The CellAlgoSwitch. SinrAdjTargetIblerforVoLTE parameter specifies the target uplink
IBLER value for VoLTE services. This parameter takes effect only to VoLTE UEs not in
the TTI bundling state.
Voice-specific AMC and uplink RLC segmentation enhancement can be enabled
simultaneously. Uplink RLC segmentation enhancement takes precedence if its requirements
are met.
4.4 Power Saving

This section describes how the basic feature LBFD-002017 DRX works for VoLTE.
As shown in Figure 4-11, with DRX enabled, UEs enter the sleep state when data is not
transmitted, saving UE power. DRX typically applies to services with consecutive small
packets that are transmitted periodically, for example, voice services. According to 3GPP TS
23.203 and section A.2.1.4 "System performance metrics" in 3GPP TS 36.814, a 50 to 80 ms
delay budget is reserved for services with QCI of 1 in the Uu interface and the interval of
sending voice frames is 20 ms. Therefore, the DRX cycle must be set to 20 ms or 40 ms,
considering the retransmission time. In this situation, setting DRX cycle to a short value for
voice services does not provide much gain. Therefore, it is recommended that the short DRX
cycle be disabled when configuring DRX parameter for services with QCI of 1.
Similar to the default bearer for a data service, the default bearer for a VoLTE service (that is,
the signaling bearer [QCI 5]) always exists as long as the UE is in RRC_CONNECTED
mode, regardless of whether the UE has a QCI 1 voice bearer. Therefore, it is recommended
that the DRX parameters for QCI 5 be set to the same values as those for a default bearer used
in a data service. In addition, as a long DRX cycle leads to a long delay for setting up a QCI 1
voice bearer, it is recommended that the long DRX cycle for QCI 5 be less than or equal to
320 ms to provide fast access experience for VoLTE users.
The DRX.DrxAlgSwitch parameter specifies whether to enable DRX.

eRAN
Figure 4-11 DRX working for VoLTE
Enabling DRX for QCI 1 can reduce the battery consumption on voice services, but at the
same time it affects voice quality, for example, the packet loss rate increases. For details, see
DRX and Signaling Feature Parameter Description.
NOTE
False detection of the PDCCH may cause voice packet loss, due to which there is a low probability of voice
quality deterioration. Preallocation can be used to reduce the impact of false detection. For details about how
DRX works with preallocation, see DRX and Signaling Control Feature Parameter Description.
4.5 Mobility Management
4.5.1 Overview
This section describes the mobility of voice services. It is recommended that coverage-based
intra-RAT and inter-RAT handovers for voice services be turned on by default to ensure the
continuity of voice services.
Voice and data service handovers are classified into intra-frequency, inter-frequency, and
inter-RAT handovers. Their handover procedures are the same. However, certain handover
parameters can be configured according to the QCI. When UEs set up bearers for different
QCIs during coverage-based, distance-based, and UL-quality-based handovers, the handover
parameters with high priority are used as the handover parameters. For details about
handovers caused by other reasons, see Intra-RAT Mobility Management in Connected Mode
Feature Parameter Description and Inter-RAT Mobility Management in Connected Mode
Feature Parameter Description. The QCI priority is specified by the
CellStandardQci.QciPriorityForHo parameter. A smaller value of this parameter indicates a
higher priority. If the QCI priority configurations (indicated by the
CellStandardQci.QciPriorityForHo parameter) are the same, the eNodeB selects handover
parameters for the UE depending on the QCI priority configurations in 3GPP specifications.
Handover parameter with high priority is used as the handover parameter of the UE. For
details, see section 6.1.7 "Standardized QoS characteristics" in 3GPP TS 23.203 V10.3.0.

eRAN
NOTE
VoLTE is generally deployed in existing LTE networks, which are data networks. Mobility parameters in
existing LTE networks have been optimized constantly and can satisfy the KPI requirements of data services.
The QoS requirements differ depending on voice and data services. It is recommended that inter-frequency or
inter-RAT mobility parameters separately configured for voice and data services. For data services, the inter-
frequency or inter-RAT mobility parameters optimized in the existing network are recommended. For voice
services, the default inter-frequency or inter-RAT mobility parameters are recommended. The preceding
recommendations minimize the impact on the KPIs of data services in future network optimization on VoLTE
services. For intra-frequency mobility, relative thresholds are used and can be separately configured for voice
and data services. However, separate configurations are not recommended.
Like the default bearer for a data service, the signaling bearer (QCI 5)for a VoLTE service always exists as
long as the UE is in RRC_CONNECTED mode. Therefore, mobility parameters for QCI 5 can be set to the
same values as those for the default bearer used in a data service.
4.5.2 Intra-Frequency Handover

This section describes the handover parameters that are set based on QCIs in different intra-
frequency handover scenarios. These parameters are as follows:
l IntraFreqHOGroup.IntraFreqHoA3Hyst
l IntraFreqHOGroup.IntraFreqHoA3Offset
l IntraFreqHOGroup.IntraFreqHoA3TimeToTrig
For details about intra-frequency handovers, see Intra-RAT Mobility Management in
Connected Mode Feature Parameter Description.
4.5.3 Inter-Frequency Handover

This section describes the handover parameters that are set based on QCIs in different inter-
frequency handover scenarios.
For details about intra-frequency handovers, see Intra-RAT Mobility Management in
Coverage-based Inter-Frequency Handover

The following handover parameters can be configured based on QCIs:
l InterFreqHoGroup.InterFreqHoA1A2Hyst
l InterFreqHoGroup.InterFreqHoA1A2TimeToTrig
l InterFreqHoGroup.InterFreqHoA1ThdRsrp
l InterFreqHoGroup.InterFreqHoA1ThdRsrq
l InterFreqHoGroup.InterFreqHoA4Hyst
l InterFreqHoGroup.InterFreqHoA4TimeToTrig
l InterFreqHoGroup.InterFreqHoA3Offset
l InterFreqHoGroup.A3InterFreqHoA1ThdRsrp
l InterFreqHoGroup.A3InterFreqHoA2ThdRsrp

eRAN
l InterFreqHoGroup.InterFreqHoA5Thd1Rsrp
l InterFreqHoGroup.InterFreqHoA5Thd1Rsrq
Service-based Inter-Frequency Handover

It is recommended that service-based inter-frequency handovers be used in inter-frequency
co-coverage scenarios.
l InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp
l InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrq
If operators require that service-based inter-frequency handovers be performed on voice

services, that is, services with QCI of 1 be preferentially set up on a certain frequency, the
following handover policies must be configured:
l Set the handover policy ServiceIfHoCfgGroup.InterFreqHoState of

ServiceIfDlEarfcnGrp.DlEarfcn to PERMIT_HO.
NOTE
When a UE initiates a voice service, the eNodeB delivers the A4 measurement configuration to the
UE, instructing the UE to measure the frequency identified by the
ServiceIfDlEarfcnGrp.DlEarfcn parameter.
l Set the CnOperatorStandardQci.Qci parameter to configure the mapping between the
inter-frequency handover frequency policy and services with a QCI of 1.
l Set the CellStandardQci.QciPriorityForHo parameter to configure the highest
handover priority for QCI 1.
l It is recommended that initial planning and configuration be performed on neighboring
cells on frequencies that carry only VoLTE services.
Distance-based Inter-Frequency Handover

UL-Quality-based Inter-Frequency Handover

Similar to coverage-based inter-frequency handover, UL-quality-based inter-frequency
handover uses certain parameters that can be specified based on QCIs. For details, see
Coverage-based Inter-Frequency Handover.
Frequency-Priority-based Inter-Frequency Handover

The following handover parameters related to event A1 and event A2 can be separately
configured based on QCIs:
l InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrp
l InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrq
l InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrp

eRAN
l InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrq
Similar to service-based inter-frequency handover, frequency-priority-based inter-frequency
handover uses certain A4-related parameters that can be specified based on QCIs. For details,
see Service-based Inter-Frequency Handover.
4.5.4 Inter-RAT Handover
4.5.4.1 Handover Type

This section describes the handover parameters that are set based on QCIs in different inter-
RAT handover scenarios.
For details about inter-RAT handovers, see Inter-RAT Mobility Management in Connected
Mode Feature Parameter Description.
Coverage-based Inter-RAT Handover

The following common inter-RAT handover parameters can be configured based on QCIs:
l InterRatHoCommGroup.InterRatHoA1A2Hyst
l InterRatHoCommGroup.InterRatHoA1A2TimeToTrig
l InterRatHoCommGroup.InterRatHoA1ThdRsrp
l InterRatHoCommGroup.InterRatHoA1ThdRsrq
l InterRatHoCommGroup.InterRatHoA2ThdRsrp
l InterRatHoCommGroup.InterRatHoA2ThdRsrq
The following handover parameters can be configured based on QCIs for each RAT.
Table 4-1 Parameters related to coverage-based inter-RAT handover

Target RAT Parameter ID
UTRAN l InterRatHoUtranGroup.InterRatHoUtranB1ThdEcn0
l InterRatHoUtranGroup.InterRatHoUtranB1ThdRscp
l InterRatHoUtranGroup.InterRatHoUtranB1Hyst
l InterRatHoUtranGroup.InterRatHoUtranB1TimeToTrig
l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0
l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRscp
GERAN l InterRatHoGeranGroup.InterRatHoGeranB1Hyst
l InterRatHoGeranGroup.InterRatHoGeranB1Thd
l InterRatHoGeranGroup.InterRatHoGeranB1TimeToTrig
l InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd
CDMA 1x l InterRatHoCdma1XrttGroup.InterRatHoCdmaB1Hyst
RTT l InterRatHoCdma1XrttGroup.InterRatHoCdmaB1ThdPs
l InterRatHoCdma1XrttGroup.InterRatHoCdmaB1TimeToTrig
l InterRatHoCdma1XrttGroup.LdSvBasedHoCdmaB1ThdPs

eRAN
Target RAT Parameter ID
CDMA l InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1Hyst
HRPD l InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1ThdPs
l InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1TimeToTrig
l InterRatHOCdmaHrpdGroup.LdSvBasedHoCdmaB1ThdPs
l InterRatHOCdmaHrpdGroup.Cdma2000HrpdB2Thd1Rsrp
l InterRatHOCdmaHrpdGroup.Cdma2000HrpdB2Thd1Rsrq
Service-based Inter-RAT Handover

With service-based inter-RAT handover, voice services are handed over from the E-UTRAN
to GERAN or UTRAN during the service setup phase.
If VoLTE has been deployed, the configurations of service-based inter-RAT handover must
meet either of the following conditions so that the eNodeB does not immediately trigger the
service-based inter-RAT handover procedure after the UE sets up voice services:
l The UtranServiceHoSwitch(UtranServiceHoSwitch) and
GeranServiceHoSwitch(GeranServiceHoSwitch) options of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter are deselected.
l The UtranServiceHoSwitch(UtranServiceHoSwitch) and
GeranServiceHoSwitch(GeranServiceHoSwitch) options of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter are selected, and the
ServiceIrHoCfgGroup.InterRatHoState parameter mapping QCI of 1 and QCI of 5 is
not set to MUST_HO.
Distance-based Inter-RAT Handover

The eNodeB supports only distance-based inter-RAT handovers to GERAN or UTRAN.
The following handover parameters can be configured based on QCIs for each RAT. These
parameters also apply to coverage-based inter-RAT handovers.
Table 4-2 Distance-based inter-RAT handover parameters

Target Parameter ID
RAT
UTRAN l InterRatHoUtranGroup.InterRatHoUtranB1ThdEcn0
l InterRatHoUtranGroup.InterRatHoUtranB1ThdRscp
l InterRatHoUtranGroup.InterRatHoUtranB1Hyst
l InterRatHoUtranGroup.InterRatHoUtranB1TimeToTrig
l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0
l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRscp

eRAN
Target Parameter ID
RAT
GERAN l InterRatHoGeranGroup.InterRatHoGeranB1Hyst
l InterRatHoGeranGroup.InterRatHoGeranB1Thd
l InterRatHoGeranGroup.InterRatHoGeranB1TimeToTrig
l InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd
UL-Quality-based Inter-RAT Handover

Similar to coverage-based inter-RAT handover, certain handover parameters for UL-quality-
based inter-RAT handover can be configured based on QCIs. For details, see Coverage-based
Inter-RAT Handover.
4.5.4.2 Handover Mode

The eNodeB determines whether to use SRVCC or PS handover for performing the preceding
inter-RAT handovers so that the CS or PS domain of the target RAT can carry voice services.
The eNodeB selects a handover mode based on conditions such as UE capability and whether
the target RAT can carry IMS-based voice services.
SRVCC
With SRVCC, the eNodeB hands over voice services from E-UTRAN to the CS domain of the
GERAN or UTRAN to ensure voice call continuity. For details about SRVCC, see SRVCC
PS Handover
With PS handover, the eNodeB hands over voice services from E-UTRAN to the PS domain
of the UTRAN to ensure voice call continuity.
If the UTRAN supports the IMS-based VoHSPA voice solution, voice services can be handed
over to VoHSPA of the UTRAN using inter-RAT PS handovers. In this situation, the
mechanism of inter-RAT PS handovers for voice services is the same as that for data services.
For details about PS handovers, see Inter-RAT Mobility Management in Connected Mode

eRAN
VoLTE Feature Parameter Description 5 Special Processing by Other Features
5 Special Processing by Other Features
ANR
After LOFD-002001 Automatic Neighbour Relation (ANR) or LOFD-002002 Inter-RAT
ANR are configured, the eNodeB filters out UEs performing voice services while selecting
UEs to perform fast ANR measurement.
l The eNodeB does not select the UEs with bearers of QCI 1 when selecting UEs that
newly access the network or are handed over to the cell.
l For UEs that are already selected for fast ANR measurement, the eNodeB uses a
measurement control policy depending on the value of the
GlobalProcSwitch.VoipWithGapMode parameter:
– When this parameter is set to ENABLE, the eNodeB does not delete the fast ANR
measurements if the bearer with a QCI of 1 is set up for the UE. However,
continuous measurement gaps may affect the voice quality of services with a QCI
of 1.
– When this parameter is set to DISABLE, the eNodeB sends an RRC Connection
Reconfiguration message to delete fast ANR measurements if the UE sets up bearer
with a QCI of 1.
l UEs read cell global identifications (CGIs) in sleep time during DRX. The sleep time
stops when a data packet arrives. This has an impact on the CGI reading success rate.
This success rate is even lower for VoLTE services, which are scheduled at a fixed
interval and encounter a higher probability that the sleep time stops. After a CGI is
acquired, the identified cell is automatically configured as a neighboring cell.
NOTE
Event-triggered ANR can be triggered by coverage-based measurements for handover or user-number-

based measurements for MLB. If coverage-based measurement for handover is enabled, gap-assisted
measurement is started even for voice users to avoid call drops. If user-number-based measurement for
MLB is enabled, MLB does not select voice users for load balancing.
When VoLTE is deployed, it is recommended that GlobalProcSwitch.VoipWithGapMode be set to
DISABLE to ensure the quality of voice services.
PCI Collision Detection and Self-Optimization

After the LOFD-002007 PCI Collision Detection & Self-Optimization feature and ANR-
based proactive PCI conflict detection are enabled, the eNodeB selects UEs without CQI 1
bearers for proactive PCI conflict detection. In addition, the eNodeB sends A3 and A4

eRAN
measurement configurations to the selected UEs, instructing the UEs to measure their serving
frequencies and neighboring E-UTRAN frequencies. For UEs that are already selected, the
eNodeB uses a measurement control policy depending on the value of the
GlobalProcSwitch.VoipWithGapMode parameter:
l When this parameter is set to ENABLE, the eNodeB does not delete the measurements
of the UE if the bearer of QCI of 1 is set up for the UE. However, continuous
measurement gaps may affect the voice quality of services with a QCI of 1.
l When this parameter is set to DISABLE, the eNodeB sends the RRC Reconfiguration
message to delete the measurement configuration if the UE sets up a bearer with a QCI
of 1.
NOTE

Carrier Aggregation
l If voice services are initiated for carrier aggregation (CA) UEs, voice services can be
scheduled only on PCells.
l If the SccBlindCfgSwitch of the eNodeBAlgoSwitch.CaAlgoSwitch parameter is turned
off, UEs that have originated voice services are not selected for CA.
l If the SccBlindCfgSwitch of the eNodeBAlgoSwitch.CaAlgoSwitch parameter is turned
on, UEs that have originated voice services can be selected for CA.
Periodic Measurement Reporting and GSM and LTE Buffer Zone Optimization
For periodic measurement reporting or GSM and LTE buffer zone optimization, the eNodeB
selects UEs for measurement based on the GlobalProcSwitch.VoipWithGapMode parameter
setting:
l When this parameter is set to ENABLE:

The eNodeB randomly selects UEs. When a UE performing voice services is selected,
continuous measurement gaps may affect the voice quality of the UE.
l When this parameter is set to DISABLE: If the UE has already initiated voice services,
the eNodeB does not select the UE for periodic inter-frequency or inter-RAT
measurement.
– The UE is selected for measurement decision until the UE releases voice services
and is selected for the second time.
– If the UE is not performing voice services, the eNodeB sends periodic inter-
frequency or inter-RAT measurement to the UE. If the UE initiates voice services
later, the eNodeB updates configurations to delete existing periodic inter-frequency
or inter-RAT measurement of the UE. The UE is selected for measurement decision
until the UE releases voice services and is selected for the second time.
NOTE

Mobility Load Balancing

l LOFD-001032 Intra-LTE Load Balancing

eRAN
The eNodeB transfers UEs based on the PRB usage. The eNodeB may transfer UEs
performing voice services for small-bandwidth cells. The voice quality of transferred
UEs may be affected.
l LOFD-070215 Intra-LTE User Number Load Balancing
For user-number-based intra-LTE load balancing, the eNodeB does not transfer UEs
performing voice services.
l LOFD-001045 Inter-RAT Load Sharing to GERAN and LOFD-001044 Inter-RAT Load
Sharing to UTRAN
During inter-RAT load balancing, the eNodeB selects the UEs to be transferred based on
PRB-usage and user number. The eNodeB may transfer UEs performing voice services.
The voice quality of transferred UEs may be affected.
PRB-based MLB is not recommended for VoLTE.
DL Non-GBR Packet Bundling

After the LOFD-001109 DL Non-GBR Packet Bundling feature is enabled, the scheduling
priority of voice services is no longer the highest priority. This feature is not recommended
for VoLTE when there are many voice users because this feature may slightly affect voice
quality.

eRAN
VoLTE Feature Parameter Description 6 Related Features
6 Related Features
This chapter describes the relationships between VoLTE-related features and other features.

eRAN
6.1 LOFD-001016 VoIP Semi-persistent Scheduling

Prerequisite Features
LBFD-002026 Uplink Power Control
During uplink semi-persistent scheduling, the MCS remains unchanged but channel
conditions vary. Consequently, the IBLER may not converge on a target value. To solve this
problem, closed-loop power control can be enabled to adjust UE transmit power for the
PUSCH.
Mutually Exclusive Features

None
Impacted Features
l LBFD-002017 DRX
If the value of the DrxParaGroup.LongDrxCycle parameter for QCI of 1 is set to a
value greater than the semi-persistent scheduling period (20 ms), the eNodeB does not
activate downlink semi-persistent scheduling.
l LOFD-001036 RAN Sharing with Common Carrier
Voice services have a high scheduling priority and are sensitive to scheduling delays.
Therefore, uplink and downlink semi-persistent scheduling does not consider the
configured proportions of PRBs that can be allocated to different operators.
l LBFD-002005 DL Asynchronous HARQ
The HARQ retransmission for DL semi-persistently scheduled data is performed by
using dynamic scheduling.
l LBFD-002006 Uplink Synchronization HARQ
When the activated retransmission for UL semi-persistent scheduling conflicts with
higher-priority scheduling, adaptive HARQ retransmission is used.
l LAOFD-001001 LTE-A Introduction
According to section 5.10 "Semi-Persistent Scheduling" in 3GPP TS 36.321, the semi-
persistent scheduling feature can be configured only in the PCell for CA UEs.
l LAOFD-0010014 DL 2x2 MIMO based on TM9
When TM9 UEs use SPS scheduling, the MIMO scheme for the UEs in PDSCH is
transmit diversity based on port7.
l Uplink delay-based dynamic scheduling
– Uplink VoIP semi-persistent scheduling and uplink delay-based dynamic scheduling
cannot take effect for the same UE at the same time.
can be enabled for the same cell at the same time. When the conditions for both
features are met, uplink VoIP semi-persistent scheduling takes precedence.
– LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentation
enhancement cannot take effect for the same UE at the same time.

eRAN

enhancement can be enabled for the same cell at the same time.
l TDLOFD-001007 High Speed Mobility
Semi-persistent scheduling is not suitable in high-speed movement scenarios because it
uses fixed MCSs and PRBs for data transmission and cannot well adapt to changes in
channel conditions.
l LBFD-081104 UL Compensation Scheduling
Uplink VoIP semi-persistent scheduling and uplink compensation scheduling cannot take
effect for the same UE at the same time.

None

None
Impacted Features
l LBFD-002017 DRX and LOFD-001105 Dynamic DRX
– If a UE is in the TTI bundling state, the eNodeB instructs the UE to enter DRX
mode only when the UE needs to perform ANR measurement.
– If a UE is in DRX mode, the eNodeB instructs the UE to exit DRX mode after
activating TTI bundling. An exception is that if the UE is performing ANR
measurement in DRX mode, the eNodeB does not instruct the UE to exit DRX
mode.
l LAOFD-001001 LTE-A Introduction
According to 3GPP TS 36.331, TTI bundling cannot be configured if a CA UE performs
data transmission in the uplink. After a CA UE enters the TTI bundling state, the
secondary serving cell (SCell) of this UE will be automatically deleted and CA is no
longer activated for UEs that are already in the TTI bundling state.
– Uplink RLC segmentation enhancement and TTI bundling can be enabled for the
same cell at the same time.
– Uplink RLC segmentation enhancement and TTI bundling cannot take effect for the
same UE at the same time.
l LOFD-001007 High Speed Mobility and LOFD-001008 Ultra High Speed Mobility
To instruct UEs to enter or exit the TTI bundling state, the eNodeB needs to send RRC
Connection Reconfiguration messages. When UEs are moving at high or ultra high
speed, their channel conditions change rapidly. As a result, the UEs frequently enter and
exit the TTI bundling state, which increases signaling load on the Uu interface, degrades
voice quality, and increase the probability of service drops. Therefore, TTI bundling is
not recommended in high- or ultra-high-movement scenarios.

eRAN
6.3 Uplink RLC Segmentation Enhancement

None

None
Impacted Features
enhancement can be enabled for the same cell at the same time.
enhancement cannot take effect for the same UE at the same time.
– Uplink RLC segmentation enhancement and TTI bundling can be enabled for the
same cell at the same time.
– Uplink RLC segmentation enhancement and TTI bundling cannot take effect for the
same UE at the same time.
l LBFD-081105 Voice-Specific AMC
The uplink IBLER of the voice user cannot converge to the target value when RLC
segmentation enhancement takes effect.
6.4 LOFD-081229 Voice Characteristic Awareness

Scheduling
l LBFD-002025 Basic Scheduling
l LOFD-00101502 Dynamic Scheduling

None
Impacted Features
cannot take effect for the same UE at the same time.
can be enabled for the same cell at the same time. When the conditions for both
features are met, uplink VoIP semi-persistent scheduling takes precedence.

eRAN
6.5 LBFD-081104 UL Compensation Scheduling


None
Impacted Features
LOFD-001016 VoIP Semi-persistent Scheduling
Uplink VoIP semi-persistent scheduling and uplink compensation scheduling cannot take
effect for the same UE at the same time.
6.6 LBFD-081105 Voice-Specific AMC

l LBFD-001006 AMC

None
Impacted Features
LOFD-001016 VoIP Semi-persistent Scheduling and LBFD-081105 Voice-Specific
AMC can be enabled for the same cell at the same time. However, voice-specific AMC
takes effect only for dynamic scheduling of VoLTE users.
LOFD-001048 TTI Bundling and LBFD-081105 Voice-Specific AMC can be enabled
for the same cell at the same time. However, voice-specific AMC applies only to VoLTE
users not in the TTI bundling state.
l RLC segmentation enhancement
The uplink IBLER of the voice user cannot converge to the target value when RLC
segmentation enhancement takes effect.
6.7 Other Features

This chapter describes other features related to VoLTE.

eRAN
Table 6-1 Other features

VoLTE-related Feature Description
LBFD-002023 Admission For details, see Admission and Congestion Control Feature
Control Parameter Description.
LBFD-002024 Congestion For details, see Admission and Congestion Control Feature
Control Parameter Description.
LOFD-00101502 Dynamic For details, see Scheduling Feature Parameter Description.

Scheduling
LBFD-002016 Dynamic This VoLTE-related feature is associated with LOFD-001016

Downlink Power VoIP Semi-persistent Scheduling. For details about the
Allocation impact on other features, see Power Control Feature
The downlink semi-persistent scheduling algorithm provides
the initial block error rate (IBLER) of downlink voice
services as an input to the downlink power control
algorithm. The IBLER is a prerequisite for PDSCH power
adjustment in semi-persistent scheduling mode.
LBFD-002026 Uplink This VoLTE-related feature is associated with LOFD-001016

Power Control VoIP Semi-persistent Scheduling. For details about the
impact on other features, see Power Control Feature
The uplink semi-persistent scheduling algorithm provides
the uplink IBLER as an input to the uplink power control
algorithm. The IBLER is a prerequisite for PUSCH power
adjustment in semi-persistent scheduling mode. If uplink
semi-persistent scheduling is enabled, it is recommended
that the CloseLoopSpsSwitch option of the
CellAlgoSwitch.UlPcAlgoSwitch parameter be selected to
ensure that the uplink IBLER converges on the target
IBLER.
LOFD-001017 RObust For details, see ROHC Feature Parameter Description.

Header Compression
(ROHC)

eRAN
VoLTE-related Feature Description
LBFD-002017 DRX The following are the relationships between DRX and TTI
bundling and between DRX and scheduling:
l If a UE is in the TTI bundling state, the eNodeB instructs
the UE to enter DRX mode only when the UE needs to
perform ANR measurement.
l If a UE is in DRX mode, the eNodeB instructs the UE to
exit DRX mode after activating TTI bundling. An
exception is that if the UE is performing ANR
measurement in DRX mode, the eNodeB does not
instruct the UE to exit DRX mode.
l When the long DRX cycle for QCI 1 is greater than the
semi-persistent scheduling interval (for example, always
20 ms for FDD), downlink semi-persistent scheduling
does not take effect.
l After DRX is enabled, preallocation does not take effect.
Preallocation decreases the probability of PDCCH false
detection, which may cause packet loss, and therefore
improves voice quality.
For more information, see DRX and Signaling Control
Intra-frequency handover For details, see Intra-RAT Mobility Management in

Inter-frequency handover For details, see Intra-RAT Mobility Management in

Inter-RAT handover For details, see Inter-RAT Mobility Management in

Connected Mode Feature Parameter Description and
SRVCC Feature Parameter Description.

eRAN
VoLTE Feature Parameter Description 7 Network Impact
7 Network Impact
This chapter describes the impact of the VoIP-related features on the network.

eRAN
7.1 LOFD-001016 VoIP Semi-persistent Scheduling

System Capacity
After semi-persistent scheduling is enabled, PDCCH resources do not hinder voice service
capacity because PDCCH resources are consumed only when semi-persistent scheduling is
initially activated or reactivated or when semi-persistently allocated resources are released.
Compared with dynamic scheduling, enabling semi-persistent scheduling increases the
number of supported voice service users by more than 30% in simulation case 1, according to
the simulation conditions and capacity evaluation method specified in an appendix of 3GPP
TS 36.814.
During semi-persistent scheduling, the MCS index cannot exceed 15. This restriction may
increase the number of RBs allocated to semi-persistently scheduled users near the cell center.
For example, when the coding rate is 23.85 kbit/s (without considering ROHC) and the MCS
index for voice users near the cell center is 26, two RBs are required in the uplink and one RB
in the downlink (dual-stream mode) when dynamic scheduling is enabled. Under the same
condition, semi-persistent scheduling requires three RBs in both the uplink and downlink due
to the MCS index restriction (the largest MCS index is 15). That is, compared with dynamic
scheduling, semi-persistent scheduling for voice users near the cell center consumes more RB
resources. Therefore, the amount of RB resource for data services decreases (compared with
that when semi-persistent scheduling is disabled), and the throughput of data services may
also decrease.
After downlink semi-persistent scheduling is enabled and voice services are set up, the
eNodeB reserves HARQ processes for downlink semi-persistent scheduling. Before the next
initial transmission in semi-persistent scheduling, the HARQ processes for downlink semi-
persistent scheduling may not be released. As a result, periodic data for semi-persistent
scheduling cannot be sent. The HARQ processes are reserved to avoid such situation. The
HARQ processes reserved for downlink semi-persistent scheduling cannot be used for
dynamic scheduling for other service type of the UE, such as data service. In combined
services where voice and data services coexist, the HARQ processes that can be used by data
services therefore decrease. Compared with the scenario where dynamic scheduling is used by
both voice and data services, the use of downlink semi-persistent scheduling for voice
services affects the throughput of data services, specifically, when the volume of the data
services is large (such as when full buffer service is performed). When there are multiple
users or a small amount of data volume, the impact of reserving HARQ processes is small
because the scheduling chances for UEs are discretely distributed or a few HARQ processes
are required for data services.
Network Performance
Fixed-position resource allocation is adopted after semi-persistent scheduling is activated.
Compared with dynamic scheduling, semi-persistent scheduling may increase the scheduling
wait time.

System Capacity
No impact.

eRAN
Network Performance
LOFD-001048 TTI bundling increases the cell edge coverage of PUSCH, improves MCS in
uplink weak-coverage areas, and reduces the packet loss rate. However, this feature increases
signaling overheads because the entry and exit of the TTI bundling state requires the
exchange of RRC messages. When the number of TTI bundling mode reconfiguration
messages (indicated by the counters L.Signal.Num.TtiBundling.Enter and
L.Signal.Num.TtiBundling.Exit) increases, the average board CPU usage (indicated by the
counter VS.BBUBoard.CPULoad.Mean (%)) slightly increases.
As defined in 3GPP protocols, TTI bundling uses a maximum of three PRBs and adopts
QPSK with the highest MCS order of 10. That is, after TTI bundling is enabled, the maximum
number of TBS that can be transmitted is 504 bits. This restricts the uplink throughput of TTI
bundling. The logical channel priority of signaling and voice services is higher than that of
data services, which means that UEs preferentially send signaling and voice services. As a
result, the uplink throughput of data services is further restricted.
7.3 Uplink RLC Segmentation Enhancement

System Capacity
No impact.
Network Performance
Uplink RLC segmentation enhancement can increase the mean opinion score (MOS)of
VoLTE users when the users are in a weak coverage area but not in the TTI bundling state.
However, uplink RLC segmentation enhancement raises the uplink MCS, IBLER and residual
BLER (RBLER).
7.4 LOFD-081229 Voice Characteristic Awareness

Scheduling
System Capacity
No impact.
Network Performance
Uplink VoLTE volume estimation for dynamic scheduling can shorten voice service delays,
reduce the uplink packet loss rate, and improve voice quality when a cell is heavily loaded
and DRX is enabled. However, this function increases RB overheads and lowers MCS
indexes allocated to voice users; when there are many voice users, this function also reduces
cell throughput.
Uplink delay-based dynamic scheduling can be used in heavy traffic scenarios to improve
voice quality in weak-coverage areas. However, this function prolongs SR-based scheduling,
which further:
l Prolongs processing time such as E-RAB setup time, RRC connection setup time, ping
delay, time of transition from idle mode to connected mode, and attach delay.

eRAN
l Slightly decreases cell throughput.

Independent configuration for voice inactivity timer has the following impacts on network
performance:
l If the value of the RrcConnStateTimer.UeInactiveTimerQci1 parameter is smaller than
that of the RrcConnStateTimer.UeInactiveTimer parameter, the online duration of
voice service UEs becomes short and voice service drop rate decreases when there is no
data transmission in the uplink and downlink while waiting for the callee to answer the
call.
l If the value of the RrcConnStateTimer.UeInactiveTimerQci1 parameter is greater than
that of the RrcConnStateTimer.UeInactiveTimer parameter, the online duration of
voice service UEs becomes long, RRC connection request number decreases, number of
normal releases decreases, and voice service drop rate increases.
7.5 LBFD-081104 UL Compensation Scheduling

System Capacity
No impact.
Network Performance
Uplink compensation scheduling can reduce the rate of uplink packet losses in heavy traffic
scenarios, shorten voice packet delays, and improve voice quality. However, this feature
increases RB and CCE overheads; when there are many voice users, this feature also reduces
cell throughput.
In addition, uplink compensation scheduling decreases the possibility that uplink control
information of voice users is transmitted over PUCCH and increases the possibility that
uplink control information of voice users is transmitted over PUSCH. This affects the
possibility that PDSCH ACK/NACK is detected as DTX and slightly increases VoLTE
downlink packet loss rate (indicated by L.Traffic.DL.PktUuLoss.Loss.QCI.1/
L.Traffic.DL.PktUuLoss.Tot.QCI.1).
7.6 LBFD-081105 Voice-Specific AMC

System Capacity
No impact.
Network Performance
l This feature affects voice quality in the following aspects:
– If the CellUlschAlgo.SinrAdjTargetIblerforVoLTE parameter is set to a smaller
value, the MCS indexes selected for uplink voice services are smaller. For voice
users in the cell center, the uplink QCI 1 packet loss rate may slightly decrease and
voice quality almost remains unchanged. For voice users not in the cell center, the
number of uplink RLC segments increases and the uplink QCI 1 packet loss rate
may increase in the case of heavy load; as a result, voice quality becomes worse and
voice capacity decreases.

eRAN
– If the CellUlschAlgo.SinrAdjTargetIblerforVoLTE parameter is set to a larger

value, the MCS indexes selected for uplink voice services are larger. In the uplink,
the IBLER, RBLER, and QCI 1 packet loss rate increases, and voice quality
becomes worse. In the downlink, the QCI 1 packet loss rate also increases and voice
quality also becomes worse because the demodulation performance deteriorates for
ACKs/NACKs and channel status information transmitted on the PUSCH.
l This feature may also affect cell throughput and data service throughput.
If the CellUlschAlgo.SinrAdjTargetIblerforVoLTE parameter is set to a smaller value,
the MCS indexes selected for uplink voice services are smaller and the number of
consumed RBs increases. When there are many voice users, cell throughput decreases.
7.7 Other Features

This chapter describes the impact of other features related to VoLTE on system capacity and
network performance.
Table 7-1 Impact of other VoLTE-related features on system capacity and network
performance
Feature Description
LBFD-002023 Admission Admission control maximizes system capacity while

Control providing users with satisfied QoS, which is indicated by the
voice service MOS.
LBFD-002024 Congestion Congestion control maximizes system capacity while

Control preferentially providing satisfied QoS for high-priority UEs.
The priority refers to the allocation/retention priority (ARP).
Congestion control ensures a high satisfaction rate of voice
service users in congested cells.
LOFD-00101502 Dynamic Voice packets are generally small. If semi-persistent

Scheduling scheduling is disabled, voice service capacity is mainly
subject to PDCCH resources. If a continuous increase in the
number of voice service users causes PDCCH resources to
become insufficient first, the cell capacity decreases.
LBFD-002016 Dynamic For details, see Power Control Feature Parameter

Downlink Power Description.
Allocation
LBFD-002026 Uplink For details, see Power Control Feature Parameter

Power Control Description.
LOFD-001017 RObust For details, see ROHC Feature Parameter Description.

Header Compression
(ROHC)

eRAN
Feature Description
LBFD-002017 DRX DRX extends voice service delay because it introduces the
sleep time. If DRX parameter settings are inappropriate,
voice service capacity will decrease or the packet loss rate
increases because voice services cannot be scheduled in real-
time. For details about the impact of DRX on network
performance, see DRX Feature Parameter Description.
Intra-frequency handover For details, see Intra-RAT Mobility Management in

Inter-frequency handover For details, see Intra-RAT Mobility Management in

Inter-RAT handover For details, see Inter-RAT Mobility Management in

Connected Mode Feature Parameter Description and
SRVCC Feature Parameter Description.

eRAN
VoLTE Feature Parameter Description 8 Voice Service Performance Evaluation
8 Voice Service Performance Evaluation
8.1 QoS Requirements

Section 6.1.7 in 3GPP TS 23.203 of Release 10 provides the QoS requirements of services
with standardized QCIs. Table 8-1 lists the QoS requirements of QCI 1 services.
Table 8-1 QoS requirements of QCI 1 services

Resource Type Priority Packet Delay Packet Error Typical Service
Budget (ms) Loss Rate
GBR 2 100 10-2 Voice service
l The preceding Packet Delay Budget indicates the threshold delay between UE and PDN
gateway (P-GW). The corresponding user satisfaction rate is 98%.
l The preceding Packet Error Loss Rate indicates the threshold proportion of SDUs that
are not successfully sent from the data link layer of the transmission end to the
corresponding upper layer of the receive end.
The packet delay budget, uplink and downlink Uu interface packet loss rate, and downlink
PDCP packet loss rates of QCI 1 services can be measured using counters. For details about
related counters, see 9.2.4.2 Voice QoS.
8.2 Quality Evaluation

The mean opinion score (MOS) is an important indicator for evaluating voice quality. MOS-
based evaluation involves subjective evaluation, objective evaluation, and measurement-based
evaluation.
8.2.1 Subjective Evaluation

MOS is a subjective measurement where listeners perceive raw speech materials and
processed degraded speech materials and then score speech quality.
Table 8-2 lists the MOS standards defined in ITU-T G.107.

eRAN
Table 8-2 MOS standards
MO Quality Level Auditory Distortion Extent Required Auditory

S Effort
5 Excellent Distortion not noticed Listening in a relaxed

manner
4 Good Distortion noticed, but not Listening with a little effort

unpleasant
3 Fair Distortion noticed, and Listening in an attentive

annoying manner
2 Poor Unpleasant but not annoying Listen with much effort
1 Bad Unpleasant and annoying Cannot understand the

contents
8.2.2 Objective Evaluation

Perceptual Evaluation of Speech Quality (PESQ), defined in ITU-T P862, is a mainstream
method of objectively evaluating AMR-NB speech quality. Perceptual Objective Listening
Quality Assessment (POLQA), defined in ITU-T P863, is the evolution of PESQ; POLQA
supports wider sampling scope and provides more accurate evaluation of AMR-WB or AMR-
NB speech quality. PESQ and POLQA are based on special tools, for example, Digital Speech
Level Analyzer (DSLA).
Objective evaluation is commonly used by operators to evaluate speech quality. However, it

requires the collaboration of drive tests. As it cannot monitor speech quality in real time, it is
generally used for tests in labs, network entry tests, and third-party evaluation of network
quality.
8.2.3 Measurement-based Evaluation
Overview
Using the third-party's drive test tools to evaluate speech quality is time and cost consuming
and cannot monitor speech quality in real time. Therefore, it is important for vendors to
develop their own measurement-based evaluation methods. Huawei uses a Voice Quality
Monitoring (VQM) algorithm to calculate the MOS scores of uplink and downlink voice
services on the Uu interface.
VQM is mainly used for network monitoring, network optimization, VIP guarantee, and user
complaint handling. VQM reduces the necessity of drive tests required for obtaining voice
quality.
VQM applies only to the AMR speech codec scenario. VQM is controlled by the
EnodebAlgoSwitch.VQMAlgoSwitch parameter, which is turned off by default. After this
parameter is turned on, the eNodeB automatically identifies whether the eNodeB supports
AMR speech codec. The eNodeB calculates only the MOS of voice services that use the
AMR speech codec scheme.

eRAN
VQM Principles
Figure 8-1 shows the VQM implementation process.
Figure 8-1 VQM implementation process
1. The eNodeB monitors counters for voice packets of QCI of 1, including the frame error
rate (FER) on the Uu interface, long frame error rate (LFER), and handover state. When
detecting that the delay variation for voice packets of QCI of 1 exceeds the
VQMALGO.ULDelayJitter parameter value, the eNodeB determines that a packet loss
occurs.
2. Then, the eNodeB inputs the monitoring results to the Huawei proprietary voice quality
indicator (VQI) model and estimates the MOS scores of uplink and downlink voice
services on the Uu interface at intervals of 2.5 seconds. The VQI model is based on the
algorithms specified in ITU-T P.863 and simulates an MOS score using mathematical
formulas.
– The eNodeB separately simulates the MOS scores of uplink and downlink voice
packets.
– The eNodeB separately simulates the MOS scores of voice packets coded at
different rates.
3. The MOS scores are saved in call history records (CHRs) and are used to collect the
statistics of cell-level voice quality counters and monitor user-level performance.
NOTE
The voice quality monitoring results including statistics about cell-level voice quality counters and
user-level performance monitoring results as well as CHRs do not include user privacy
information.

eRAN
Voice Quality Evaluation

The eNodeB evaluates voice quality based on the MOS provided by the VQM and voice
quality thresholds. In addition, the eNodeB collects the statistics of counters related to voice
quality, as listed in Table 8-3.
Table 8-3 Voice quality evaluation rules and related counters
MOS Scores Provided by the VQI Model Voice Quality Related Counters
Level
MOS > VQMAlgo.VqiExcellentThd Excellent For details, see Table

9-8.
VQMAlgo.VqiGoodThd < MOS ≤ Good For details, see Table

VQMAlgo.VqiExcellentThd 9-9.
VQMAlgo.VqiPoorThd < MOS ≤ Fair For details, see Table

VQMAlgo.VqiGoodThd 9-10.
VQMAlgo.VqiBadThd < MOS ≤ Poor For details, see Table

VQMAlgo.VqiPoorThd 9-11.
MOS ≤ VQMAlgo.VqiBadThd Bad For details, see Table

9-12.
Application Limitations
AMR coding rate is an important input for the VQI model. Currently, the VQM algorithm
cannot monitor the AMR coding rate in real time. If the AMR coding rate changed, the output
of the VQI model would be inaccurate. Up to now, it has not been found that the AMR coding
rate changes in any scenario.
In the following scenarios, the eNodeB cannot determine the AMR coding rate and therefore
does not use the VQI model.
l One RTP packet carries multiple AMR speech frames.

l One RTP packet carries multiple speech frames that are coded at different rates.
The IP headers need to be removed when the eNodeB identifies the coding rate. The IP
header length is different after the encryption. The IP header of a voice packet may
include an Authentication Header (AH) or (Encapsulation Security Payload (ESP) header
for encryption. The length of AHs is not fixed, and the latter part of ESP headers is
encrypted, and the latter part of ESP headers is encrypted.
8.3 Capacity Evaluation

The voice service capacity can be evaluated based on the number of users performing QCI 1
services. The related counters are listed below and described in 9.2.4.4 Voice Capacity.
l L.Traffic.ActiveUser.UL.QCI.1
l L.Traffic.ActiveUser.DL.QCI.1

eRAN
8.4 Performance Evaluation

The performance of voice services can be evaluated using the following KPIs, which are
described in 9.2.4.1 Voice KPIs
l E-RAB Setup Success Rate (VoIP)
l Call Drop Rate (VoIP)

eRAN
VoLTE Feature Parameter Description 9 Engineering Guidelines
9 Engineering Guidelines
9.1 Overview
The engineering guidelines of features or functions listed in Table 9-1 are not included in this
document.
Table 9-1 VoLTE-related functions and features

Features/Functions Engineering Guidelines
LBFD-002023 Admission Control For details about the engineering guidelines for this
feature, see Admission and Congestion Control
LBFD-002024 Congestion Control For details about the engineering guidelines for this
feature, see Admission and Congestion Control
LOFD-00101502 Dynamic For details about the engineering guidelines for this
Scheduling feature, see Scheduling Feature Parameter
Description.
Power control in dynamic scheduling For details about the engineering guidelines for
power control in dynamic scheduling, see Power
Control Feature Parameter Description.
QCI and RLC mode For details about the engineering guidelines for
QCI and RLC mode, see QoS Management Feature
LOFD-001017 RObust Header For details about the engineering guidelines for this
Compression (ROHC) feature, see ROHC Feature Parameter Description.
LOFD-001109 DL Non-GBR Packet For details about the engineering guidelines for this
Bundling feature, see Scheduling Feature Parameter
Description.

eRAN
Features/Functions Engineering Guidelines
Intra-frequency handover For details about the engineering guidelines for this
function, see Intra-RAT Mobility Management in
Connected Mode.
Inter-frequency handover For details about the engineering guidelines for this
function, see Intra-RAT Mobility Management in
Connected Mode.
Inter-RAT handover For details about the engineering guidelines for

SRVCC, see SRVCC Feature Parameter
Description.
For details about the engineering guidelines for PS
handover, see Inter-RAT Mobility Management in
Connected Mode.
LBFD-002017 DRX For details about the engineering guidelines for this
feature, see DRX and Signaling Control Feature
9.2 Basic Functions
9.2.1 When to Use Basic Functions

Users can determine whether to deploy IMS-based VoLTE services depending on whether
IMS is deployed, transmission delay, and voice service policies.
The E-UTRAN supports VoLTE after the IMS is deployed. However, VoLTE is not used in
the following scenarios because IMS-based VoLTE is not appropriate for these scenarios:
l Transmission delay is large.
l Voice services are not allowed on certain frequency bands.
You can turn off the ENodeBAlgoSwitch.EutranVoipSupportSwitch if the eNodeB works in
the preceding scenarios. Turning off this switch prevents UEs from initiating voice services
and prevents UEs performing voice services from handing over to the eNodeB. For details,
see 3.2.2 VoLTE-Prohibited Scenario.
NOTE
After the ENodeBAlgoSwitch.EutranVoipSupportSwitch is turned off, you also need to disable VoLTE
in the corresponding tracking areas on the MME.
In other scenarios, turn on the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch so that

the eNodeB supports IMS-based voice services.
In scenarios where E-UTRAN coverage is discontinuous, it is recommended that the SRVCC
function be enabled.
If the MME supports the UE Radio Capability Match REQUEST and UE Radio Capability
Match RESPONSE messages introduced in 3GPP Release 11, it is recommended that the
SupportS1UeCapMatchMsg option of the GlobalProcSwitch.ProtocolSupportSwitch

eRAN
parameter be selected on the eNodeB side. By doing this, the MME considers the VoLTE
mobility capability of the UE during the voice policy negotiation. In this manner, UEs that do
not support SRVCC do not adopt VoLTE as the voice policy, thereby ensuring voice
continuity.
It is recommended that the VQM function be enabled to monitor voice quality.
9.2.2 Required Information

None
9.2.3 Deployment
Operating Environment
l UEs must support VoLTE, and the EPC must support IMS.
l Operators have deployed the IMS.
Transmission Networking
VoLTE services have high requirements on end-to-end real-time delay. For example, when the
transmission delay between the eNodeB and EPC exceeds 20 ms, VoLTE is not appropriate
for the eNodeB.
For the requirements on transmission delay and jitter on S1 and X2 interfaces, see IP eRAN
Engineering Guide Feature Parameter Description.
License
None
9.2.3.2 Data Preparation

There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to set the eNodeB voice service switch.

eRAN
Parameter Parameter ID Data Source Setting Notes

Name
Eutran Voip ENodeBAlgoSwitc Network plan Set this parameter to ON(On) if

Support h.EutranVoipSupp (negotiation you plan to use the VoLTE voice
Switch ortSwitch not required) solution.
For details about the deployment
suggestion of the VoLTE voice
solution, see 9.2.1 When to Use
Basic Functions.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to
determine whether the eNodeB supports voice mobility.

Name
Protocol GlobalProcSwitch. Network plan If the MME supports the UE

Procedure ProtocolSupportS- (negotiation Radio Capability Match
Support witch not required) REQUEST and UE Radio
Switch Capability Match RESPONSE
messages introduced in 3GPP
Release 11, set this parameter to
SupportS1UeCapMatchMsg(Su
pportS1UeCapMatchMsg).
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to determine whether the eNodeB supports VQM.

Name
Voice quality ENodeBAlgoSwitc Network plan To monitor the voice quality, set
monitoring h.VQMAlgoSwitch (negotiation this parameter to
algo switch not required) VQM_ALGO_SWITCH_ON.
The following table describes the parameter that must be set in the RlcPdcpParaGroup MO
to configure the PDCP discard timer.

eRAN

Name
Discard timer RlcPdcpParaGrou Network plan If the voice service bearer

p.DiscardTimer (negotiation planning policy specified by
not required) operators is QCI 5 multiplexing
for carrying voice packets, it is
recommended that this parameter
for QCI of 5 be set to 150 ms.
Otherwise, set this parameter for
QCI of 5 to Infinity.
9.2.3.3 Precautions
None
9.2.3.4 Hardware Adjustment

None
9.2.3.5 Initial Configuration
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 9-2 in a summary data file, which also
contains other data for the new eNodeBs to be deployed.
Then, import the summary data file into the Configuration Management Express (CME) for
batch configuration.
For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide
for the eNodeB, which is available in the eNodeB product documentation. The summary data
file may be a scenario-specific file provided by the CME or a customized file, depending on
the following conditions:
l The MOs in Table 9-2 are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 9-2 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 9-2 Common data

MO Sheet in the Summary Parameter Group Remarks
Data File
ENodeBAlgoS ENodeBAlgoSwitch EutranVoipSupportSwitch User-

witch defined
template

eRAN

Data File
GlobalProcSwit GlobalProcSwitch ProtocolSupportSwitch User-

ch defined
template
ENodeBAlgoS ENodeBAlgoSwitch VQMAlgoSwitch User-

witch defined
template
RlcPdcpParaGr RlcPdcpParaGroup DiscardTimer User-

oup defined
template
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure.
Step 1 The procedure is as follows: After creating a planned data area, choose CME > Advanced >
Customize Summary Data File (U2000 client mode), or choose Advanced > Customize
Summary Data File (CME client mode), to customize a summary data file for batch
reconfiguration.
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 9-2 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME,
and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts
(U2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
----End
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the 9.4.3.2 Data Preparation section for a single
eNodeB. The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.

eRAN
Step 2 In area 1 shown in Figure 9-1, select the eNodeB to which the MOs belong.
Figure 9-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column.
Step 5 All parameters in this MO are displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
Using MML Commands

l Run the MOD ENODEBALGOSWITCH command to turn on the
EutranVoipSupportSwitch switch.
l Run the MOD GLOBALPROCSWITCH command and select
SupportS1UeCapMatchMsg.
l Run the MOD ENODEBALGOSWITCH command to turn on the VQMAlgoSwitch.
MML Command Examples

MOD ENODEBALGOSWITCH:EUTRANVOIPSUPPORTSWITCH=ON;
MOD GLOBALPROCSWITCH: ProtocolSupportSwitch=SupportS1UeCapMatchMsg-1;
MOD ENODEBALGOSWITCH:VQMALGOSWITCH=VQM_ALGO_SWITCH_ON;

eRAN
9.2.3.6 Activation Observation

To check whether a UE can perform voice services after the EutranVoipSupportSwitch
switch is turned on, perform the following steps:
Step 1 Run the LST ENodeBAlgoSwitch command to check whether the

EutranVoipSupportSwitch switch is turned on.
Step 2 Enable a UE to access a cell and perform voice services.
Step 3 View the E-RAB SETUP REQUEST and E-RAB SETUP RESPONSE messages for QCI 5
and QCI 1 in the S1 interface tracing task result on the U2000. Bearers for QCI of 5 and QCI
of 1 are successfully set up, as shown in Figure 9-2, Figure 9-3, Figure 9-4, and Figure 9-5.
Figure 9-2 E-RAB SETUP REQUEST (QCI5)
Figure 9-3 E-RAB SETUP RESPONSE (QCI5)

eRAN
Figure 9-4 E-RAB SETUP REQUEST (QCI1)
Figure 9-5 E-RAB SETUP RESPONSE (QCI1)
Step 4 Check whether the following counters indicate successful voice service setup.
Counter Counter Name Counter Description

ID
15267266 L.E- Number of successful E-RAB setups initiated by UEs

69 RAB.SuccEst.QC for services with the QCI of 1 in a cell
I.1
15267266 L.E- Number of successful E-RAB setups initiated by UEs

77 RAB.SuccEst.QC for services with the QCI of 5 in a cell
I.5
Step 5 View the "voice support match indicator" IE in the UE RADIO CAPABILITY MATCH
RESPONSE message in the S1 interface tracing task result on the U2000. If the value of the

eRAN
IE is supported or not supported, the eNodeB can query a UE's capability in supporting
VoLTE mobility and report the capability to the MME.
----End
9.2.3.7 Reconfiguration
N/A
9.2.3.8 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 9-3.
Table 9-3 Common data

Data File
ENodeBAlgo ENodeBAlgoSwitch EutranVoipSupportS- OFF(Off)

Switch witch
GlobalProcS GlobalProcSwitch ProtocolSupportSwitch Deselected

witch
ENodeBAlgo ENodeBAlgoSwitch VQMAlgoSwitch VQM_ALGO_S

Switch WITCH_OFF

On the CME, set parameters according to the MOs listed in the related tables in each scenario.
For detailed instructions, see Using the CME to Perform Single Configuration described
for feature activation.
Using MML Commands

l Run the MOD ENODEBALGOSWITCH command to turn off the
EutranVoipSupportSwitch switch.
l Run the MOD GLOBALPROCSWITCH command and clear
SupportS1UeCapMatchMsg.
l Run the MOD ENODEBALGOSWITCH command to turn off the VQMAlgoSwitch.

MOD ENODEBALGOSWITCH:EUTRANVOIPSUPPORTSWITCH=OFF;
MOD GLOBALPROCSWITCH: ProtocolSupportSwitch=SupportS1UeCapMatchMsg-0;
MOD ENODEBALGOSWITCH:VQMALGOSWITCH=VQM_ALGO_SWITCH_OFF;

eRAN
9.2.4 Performance Monitoring

After common parameters are deployed, or after both common parameters and the features
and functions in Table 9-1 are deployed, you can monitor voice service performance using the
following counters.
9.2.4.1 Voice KPIs
E-RAB Setup Success Rate (VoLTE)

Table 9-4 describes the counters used to monitor the E-RAB setup success rates of voice
services.
Table 9-4 Counters used to monitor the E-RAB setup success rates of voice services
Counter ID Counter Name Counter Description
1526726668 L.E-RAB.AttEst.QCI.1 Number of E-RAB setup attempts initiated

by UEs for services with the QCI of 1 in a
cell
1526726676 L.E-RAB.AttEst.QCI.5 Number of E-RAB setup attempts initiated

by UEs for services with the QCI of 5 in a
cell
1526726669 L.E-RAB.SuccEst.QCI.1 Number of successful E-RAB setups

initiated by UEs for services with the QCI
of 1 in a cell
1526726677 L.E-RAB.SuccEst.QCI.5 Number of successful E-RAB setups

initiated by UEs for services with the QCI
of 5 in a cell
1526727853 L.E- Number of E-RAB setup attempts initiated

RAB.AttEst.PLMN.QCI.1 by UEs of a specified operator for services
with the QCI of 1 in a cell
1526727861 L.E- Number of E-RAB setup attempts initiated

RAB.AttEst.PLMN.QCI.5 by UEs of a specified operator for services
1526727854 L.E- Number of successful E-RAB setups

RAB.SuccEst.PLMN.QCI.1 initiated by UEs of a specified operator for
services with the QCI of 1 in a cell
1526727862 L.E- Number of successful E-RAB setups

RAB.SuccEst.PLMN.QCI.5 initiated by UEs of a specified operator for
E-RAB (QCI 1) setup success rate = L.E-RAB.SuccEst.QCI.1/L.E-RAB.AttEst.QCI.1
E-RAB (QCI 5) setup success rate = L.E-RAB.SuccEst.QCI.5/L.E-RAB.AttEst.QCI.5

eRAN
E-RAB (QCI 1) setup success rate for a specific operator = L.E-RAB.SuccEst.PLMN.QCI.

1/L.E-RAB.AttEst.PLMN.QCI.1
E-RAB (QCI 5) setup success rate for a specific operator = L.E-RAB.SuccEst.PLMN.QCI.
5/L.E-RAB.AttEst.PLMN.QCI.5
Handover Success Rate (VoIP)

Table 9-5 describes the counters used to monitor the handover success rates of voice services.
Table 9-5 Counters used to monitor the handover success rates of voice services
1526729526 L.HHO.IntraeNB.IntraFre Number of intra-eNodeB intra-frequency

q.PrepAttOut.VoIP outgoing handover attempts for UEs
performing voice services in a cell
1526729527 L.HHO.IntraeNB.InterFre Number of intra-eNodeB inter-frequency

1526729535 L.HHO.IntereNB.IntraFre Number of inter-eNodeB intra-frequency

1526729536 L.HHO.IntereNB.InterFreq Number of inter-eNodeB inter-frequency

.PrepAttOut.VoIP outgoing handover attempts for UEs
1526729537 L.HHO.IntereNB.InterFdd Number of inter-eNodeB inter-duplex-

Tdd.PrepAttOut.VoIP mode outgoing handover attempts for UEs
1526729529 L.HHO.IntraeNB.IntraFre Number of intra-eNodeB intra-frequency

q.ExecAttOut.VoIP outgoing handover executions for UEs
1526729530 L.HHO.IntraeNB.InterFre Number of intra-eNodeB inter-frequency

1526729538 L.HHO.IntereNB.IntraFre Number of inter-eNodeB intra-frequency

1526729539 L.HHO.IntereNB.InterFreq Number of inter-eNodeB inter-frequency

.ExecAttOut.VoIP outgoing handover executions for UEs
1526729540 L.HHO.IntereNB.InterFdd Number of inter-eNodeB inter-duplex-

Tdd.ExecAttOut.VoIP mode outgoing handover executions for
UEs performing voice services in a cell

eRAN
1526729532 L.HHO.IntraeNB.IntraFre Number of successful intra-eNodeB intra-

q.ExecSuccOut.VoIP frequency outgoing handovers for UEs
1526729533 L.HHO.IntraeNB.InterFre Number of successful intra-eNodeB inter-

1526729541 L.HHO.IntereNB.IntraFre Number of successful inter-eNodeB intra-

1526729542 L.HHO.IntereNB.InterFreq Number of successful inter-eNodeB inter-

.ExecSuccOut.VoIP frequency outgoing handovers for UEs
1526729543 L.HHO.IntereNB.InterFdd Number of successful inter-eNodeB inter-

Tdd.ExecSuccOut.VoIP duplex-mode outgoing handovers for UEs
1526729528 L.HHO.IntraeNB.InterFdd Number of intra-eNodeB inter-duplex-

Tdd.PrepAttOut.VoIP mode outgoing handover attempts for UEs
1526729531 L.HHO.IntraeNB.InterFdd Number of intra-eNodeB inter-duplex-

Tdd.ExecAttOut.VoIP mode outgoing handover executions for
UEs performing voice services in a cell
1526729534 L.HHO.IntraeNB.InterFdd Number of successful intra-eNodeB inter-

Tdd.ExecSuccOut.VoIP duplex-mode outgoing handovers for UEs
Intra-frequency handover success rates of voice services =

(L.HHO.IntraeNB.IntraFreq.ExecSuccOut.VoIP +
L.HHO.IntereNB.IntraFreq.ExecSuccOut.VoIP)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut.VoIP +
L.HHO.IntereNB.IntraFreq.ExecAttOut.VoIP)
Inter-frequency handover success rates of voice services =
(L.HHO.IntraeNB.InterFreq.ExecSuccOut.VoIP +
L.HHO.IntereNB.InterFreq.ExecSuccOut.VoIP)/
(L.HHO.IntraeNB.InterFreq.ExecAttOut.VoIP +
L.HHO.IntereNB.InterFreq.ExecAttOut.VoIP)
Inter-mode handover success rates of voice services =
(L.HHO.IntraeNB.InterFddTdd.ExecSuccOut.VoIP +
L.HHO.IntereNB.InterFddTdd.ExecSuccOut.VoIP )/
(L.HHO.IntraeNB.InterFddTdd.ExecAttOut.VoIP +
L.HHO.IntereNB.InterFddTdd.ExecAttOut.VoIP)

eRAN
Call Drop Rate (VoLTE)

Table 9-6 describes the counters used to monitor the call drop rates of voice services.
Table 9-6 Counters used to monitor the call drop rates of voice services
ID
152672668 L.E- Number of abnormal E-RAB releases for services

6 RAB.AbnormRel.Q with the QCI of 1 in a cell
CI.1
152672669 L.E- Number of abnormal E-RAB releases for services

4 RAB.AbnormRel.Q with the QCI of 5 in a cell
CI.5
152672668 L.E- Number of normal E-RAB releases for services

7 RAB.NormRel.QCI. with the QCI of 1 in a cell
1
152672669 L.E- Number of normal E-RAB releases for services

5 RAB.NormRel.QCI. with the QCI of 5 in a cell
5
152672787 L.E- Number of abnormal releases of activated E-RABs

1 RAB.AbnormRel.P of a specified operator for services with the QCI of
LMN.QCI.1 1 in a cell
152672787 L.E- Number of abnormal releases of activated E-RABs

9 RAB.AbnormRel.P of a specified operator for services with the QCI of
LMN.QCI.5 5 in a cell
152672787 L.E- Number of normal E-RAB releases of a specified

2 RAB.NormRel.PLM operator for services with the QCI of 1 in a cell
N.QCI.1
152672788 L.E- Number of normal E-RAB releases of a specified

0 RAB.NormRel.PLM operator for services with the QCI of 5 in a cell
N.QCI.5
Call drop rate (QCI 1) = L.E-RAB.AbnormRel.QCI.1/(L.E-RAB.AbnormRel.QCI.1 +

L.E-RAB.NormRel.QCI.1)
Call drop rate (QCI 5) = L.E-RAB.AbnormRel.QCI.5/(L.E-RAB.AbnormRel.QCI.5 +
L.E-RAB.NormRel.QCI.5)
Call drop rate (QCI 1) for a specific operator = L.E-RAB.AbnormRel.PLMN.QCI.1/(L.E-
RAB.AbnormRel.PLMN.QCI.1 + L.E-RAB.NormRel.PLMN.QCI.1)
Call drop rate (QCI 5) for a specific operator = L.E-RAB.AbnormRel.PLMN.QCI.5/(L.E-
RAB.AbnormRel.PLMN.QCI.5 + L.E-RAB.NormRel.PLMN.QCI.5)

eRAN
9.2.4.2 Voice QoS
Packet Loss Rate

Table 9-7 describes the counters used to monitor the uplink and downlink packet loss rate on
the Uu interface and the downlink PDCP packet discard rate of voice services.
Table 9-7 Counters used to monitor the packet loss rate

ID
1526727 L.Traffic.UL.PktLoss.Los Number of discarded uplink traffic PDCP SDUs

961 s.QCI.1 for DRB services with the QCI of 1 in a cell
1526727 L.Traffic.UL.PktLoss.Tot Number of expected uplink traffic data packets

962 .QCI.1 for DRB services with the QCI of 1 in a cell
1526727 L.Traffic.DL.PktUuLoss. Number of discarded downlink traffic PDCP

934 Loss.QCI.1 SDUs for DRB services with the QCI of 1 in a
cell over the Uu interface
1526727 L.Traffic.DL.PktUuLoss. Number of transmitted downlink traffic PDCP

935 Tot.QCI.1 SDUs for DRB services with the QCI of 1 in a
cell over the Uu interface
1526726 L.PDCP.Tx.Disc.Trf.SDU Number of downlink traffic SDUs discarded by

833 .QCI.1 the PDCP layer for services with the QCI of 1 in
a cell
1526727 L.PDCP.Tx.TotRev.Trf.S Number of transmitted downlink traffic PDCP

889 DU.QCI.1 SDUs for services with the QCI of 1 in a cell
1526736 L.Traffic.UL.PktLoss.Los Total number of discarded uplink PDCP SDUs

684 s.PLMN.QCI.1 for traffic services with a QCI of 1 for a specific
operator in a cell
1526736 L.Traffic.UL.PktLoss.Tot Total number of expected uplink data packets for

686 .PLMN.QCI.1 DRB services with a QCI of 1 for a specific
operator in a cell
1526736 L.Traffic.DL.PktUuLoss. Total number of discarded downlink PDCP

737 Loss.PLMN.QCI.1 SDUs for traffic services with a QCI of 1 for a
specific operator in a cell
1526736 L.Traffic.DL.PktUuLoss. Total number of expected downlink data packets

739 Tot.PLMN.QCI.1 for DRB services with a QCI of 1 for a specific
operator in a cell
1526736 L.PDCP.Tx.Disc.Trf.SDU Number of downlink traffic SDUs discarded by

680 .PLMN.QCI.1 the PDCP layer for services with a QCI of 1 for
a specific operator in a cell
1526736 L.PDCP.Tx.TotRev.Trf.S Number of transmitted downlink traffic PDCP

682 DU.PLMN.QCI.1 SDUs for services with a QCI of 1 for a specific
operator in a cell

eRAN
UL packet discard rate on the Uu interface for QCI 1 = L.Traffic.UL.PktLoss.Loss.QCI.1 /

L.Traffic.UL.PktLoss.Tot.QCI.1
DL packet discard rate on the Uu interface for QCI 1 = L.Traffic.DL.PktUuLoss.Loss.QCI.
1 / L.Traffic.DL.PktUuLoss.Tot.QCI.1
DL PDCP packet discard rate = L.PDCP.Tx.Disc.Trf.SDU.QCI.1 /
(L.PDCP.Tx.Disc.Trf.SDU.QCI.1+L.PDCP.Tx.TotRev.Trf.SDU.QCI.1)
UL packet discard rate on the Uu interface for QCI 1 of a specific operator =
L.Traffic.UL.PktLoss.Loss.PLMN.QCI.1 / L.Traffic.UL.PktLoss.Tot.PLMN.QCI.1
DL packet discard rate on the Uu interface for QCI 1 of a specific operator =
L.Traffic.DL.PktUuLoss.Loss.PLMN.QCI.1 / L.Traffic.DL.PktUuLoss.Tot.PLMN.QCI.1
DL PDCP packet discard rate for a specific operator =
L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.1 / (L.PDCP.Tx.Disc.Trf.SDU.QCI.
1+L.PDCP.Tx.TotRev.Trf.SDU.PLMN.QCI.1)
9.2.4.3 Voice Quality

Table 9-8, Table 9-9, Table 9-10, Table 9-11, and Table 9-12 describe the counters used to
monitor the distribution of uplink and downlink voice service QoS.
Table 9-8 Counters with the voice quality being Excellent

1526728411 L.Voice.VQI.UL.Exc Number of times uplink voice quality is Excellent

ellent.Times
1526728416 L.Voice.VQI.DL.Exc Number of times downlink voice quality is

ellent.Times Excellent
1526732687 L.Voice.VQI.AMR Number of times uplink voice quality of AMR-

WB.UL.Excellent.Ti WB services is Excellent
mes
1526732692 L.Voice.VQI.AMR Number of times downlink voice quality of AMR-

WB.DL.Excellent.Ti WB services is Excellent
mes
1526736660 L.Voice.VQI.UL.Exc Number of times uplink voice quality is Excellent

ellent.Times.PLMN for a specific operator in a cell
1526736665 L.Voice.VQI.DL.Exc Number of times downlink voice quality is

ellent.Times.PLMN Excellent for a specific operator in a cell

WB.UL.Excellent.Ti WB services is Excellent for a specific operator in
mes.PLMN a cell

eRAN

WB.DL.Excellent.Ti WB services is Excellent for a specific operator in
mes.PLMN a cell
Table 9-9 Counters with the voice quality being Good

1526728412 L.Voice.VQI.UL.Go Number of times uplink voice quality is Good

od.Times
1526728417 L.Voice.VQI.DL.Go Number of times downlink voice quality is Good

od.Times

WB.UL.Good.Times WB services is Good

WB.DL.Good.Times WB services is Good
1526736661 L.Voice.VQI.UL.Go Number of times uplink voice quality is Good for

od.Times.PLMN a specific operator in a cell
1526736666 L.Voice.VQI.DL.Go Number of times downlink voice quality is Good

od.Times.PLMN for a specific operator in a cell

WB.UL.Good.Times WB services is Good for a specific operator in a
.PLMN cell

WB.DL.Good.Times WB services is Good for a specific operator in a
.PLMN cell
Table 9-10 Counters with the voice quality being Accept

1526728413 L.Voice.VQI.UL.Acc Number of times uplink voice quality is Accept

ept.Times
1526728418 L.Voice.VQI.DL.Acc Number of times downlink voice quality is Accept

ept.Times

WB.UL.Accept.Tim WB services is Accept
es

eRAN

WB.DL.Accept.Tim WB services is Accept
es
1526736662 L.Voice.VQI.UL.Acc Number of times uplink voice quality is Accept

ept.Times.PLMN for a specific operator in a cell
1526736667 L.Voice.VQI.DL.Acc Number of times downlink voice quality is Accept

ept.Times.PLMN for a specific operator in a cell

WB.UL.Accept.Tim WB services is Accept for a specific operator in a
es.PLMN cell

WB.DL.Accept.Tim WB services is Accept for a specific operator in a
es.PLMN cell
Table 9-11 Counters with the voice quality being Poor
1526728414 L.Voice.VQI.UL.Po Number of times uplink voice quality is Poor

or.Times
1526728419 L.Voice.VQI.DL.Po Number of times downlink voice quality is Poor

or.Times

WB.UL.Poor.Times WB services is Poor

WB.DL.Poor.Times WB services is Poor
1526732890 L.Voice.NormRel.U Number of normally released voice calls (poor

L.LowQuality uplink voice quality)
1526732891 L.Voice.NormRel.D Number of normally released voice calls (poor

L.LowQuality downlink voice quality)
1526736663 L.Voice.VQI.UL.Po Number of times uplink voice quality is Poor for a

or.Times.PLMN specific operator in a cell
1526736668 L.Voice.VQI.DL.Po Number of times downlink voice quality is Poor

or.Times.PLMN for a specific operator in a cell

WB.UL.Poor.Times. WB services is Poor for a specific operator in a
PLMN cell

WB.DL.Poor.Times. WB services is Poor for a specific operator in a
PLMN cell

eRAN
Table 9-12 Counters with the voice quality being Bad

1526728415 L.Voice.VQI.UL.Ba Number of times uplink voice quality is Bad

d.Times
1526728420 L.Voice.VQI.DL.Ba Number of times downlink voice quality is Bad

d.Times

WB.UL.Bad.Times WB services is Bad

WB.DL.Bad.Times WB services is Bad
1526732892 L.Voice.UL.Silent.N Number of times uplink voice call is silent

um
1526732893 L.Voice.DL.Silent.N Number of times downlink voice call is silent

um
1526736664 L.Voice.VQI.UL.Ba Number of times uplink voice quality is Bad for a

d.Times.PLMN specific operator in a cell
1526736669 L.Voice.VQI.DL.Ba Number of times downlink voice quality is Bad

d.Times.PLMN for a specific operator in a cell

WB.UL.Bad.Times. WB services is Bad for a specific operator in a cell
PLMN

WB.DL.Bad.Times. WB services is Bad for a specific operator in a cell
PLMN
9.2.4.4 Voice Capacity
Number of UEs with Voice Services

Table 9-13 describes the counters used to monitor the number of UEs with voice services.
Table 9-13 Counters used to monitor the number of UEs with voice services
1526728456 L.Traffic.ActiveUser.DL.QCI.1 Number of activated UEs

with the QCI of 1 in the
downlink buffer

eRAN
1526728446 L.Traffic.ActiveUser.UL.QCI.1 Number of activated UEs

with the QCI of 1 in the
uplink buffer
1526730601 L.Traffic.ActiveUser.DL.QCI.1.Max Maximum number of

activated UEs with the QCI
of 1 in the downlink buffer
1526730611 L.Traffic.ActiveUser.UL.QCI.1.Max Maximum number of

activated UEs with the QCI
of 1 in the uplink buffer
1526732721 L.Traffic.User.VoIP.Avg Average number of VoIP

UEs in a cell
1526732722 L.Traffic.User.VoIP.Max Maximum number of VoIP

UEs in a cell
1526736692 L.Traffic.User.VoIP.Avg.PLMN Average number of VoIP

UEs of a specific operator in
a cell
1526736693 L.Traffic.User.VoIP.Max.PLMN Maximum number of VoIP

UEs of a specific operator in
a cell
Number of PRBs Used by Voice Services

Table 9-14 describes the counters used to monitor the average number of PRBs occupied by
voice services.
Table 9-14 Counters used to monitor the average number of PRBs occupied by voice services
1526730883 L.ChMeas.PRB. Average number of PRBs used by DRBs on the

DL.DrbUsed.Avg PDSCH for downlink VoIP services
.VoIP
1526730884 L.ChMeas.PRB. Average number of PRBs used by DRBs on the

UL.DrbUsed.Avg PUSCH for uplink VoIP services
.VoIP
Throughput
Table 9-15 and Table 9-16 describe the counters used to monitor the number of PDCCH
CCEs used by voice services and total uplink/downlink traffic volume of voice services.
Based on these counters, you can calculate the average uplink/downlink throughput of voice
services.

eRAN
Table 9-15 Counters used to monitor the number of PDCCH CCEs used by voice services
1526736735 L.ChMeas.CCE.ULUsed. Number of PDCCH CCEs used for uplink

VoIP VoIP services
1526736736 L.ChMeas.CCE.DLUsed. Number of PDCCH CCEs used for

VoIP downlink VoIP services
Table 9-16 Counters used to monitor the total uplink/downlink traffic volume of voice
services
1526726776 L.Thrp.bits.UL.QCI.1 Uplink traffic volume for PDCP PDUs of

1526726803 L.Thrp.bits.DL.QCI.1 Downlink traffic volume for PDCP SDUs

of services with the QCI of 1 in a cell
1526726777 L.Thrp.Time.UL.QCI.1 Receive duration of uplink PDCP PDUs for

1526726804 L.Thrp.Time.DL.QCI.1 Transmit duration of downlink PDCP SDUs

for services with the QCI of 1 in a cell
1526727849 L.Thrp.bits.UL.PLMN.Q Uplink traffic volume for PDCP PDUs of

CI.1 services with the QCI of 1 in a cell
1526727850 L.Thrp.Time.UL.PLMN. Receive duration of uplink PDCP PDUs for

QCI.1 services with the QCI of 1 in a cell
1526728050 L.Thrp.bits.DL.PLMN.Q Downlink traffic volume for PDCP SDUs

CI.1 of services with the QCI of 1 in a cell
1526728051 L.Thrp.Time.DL.PLMN. Transmit duration of downlink PDCP SDUs

QCI.1 for services with the QCI of 1 in a cell
Average uplink throughput of services with a QCI of 1 = L.Thrp.bits.UL.QCI.1 /

L.Thrp.Time.UL.QCI.1
Average downlink throughput of services with a QCI of 1 = L.Thrp.bits.DL.QCI.1 /
L.Thrp.Time.DL.QCI.1
Average uplink throughput of services with a QCI of 1 for a specific operator =
L.Thrp.bits.UL.PLMN.QCI.1 / L.Thrp.Time.UL.PLMN.QCI.1
Average downlink throughput of services with a QCI of 1 for a specific operator =
L.Thrp.bits.DL.PLMN.QCI.1/ L.Thrp.Time.DL.PLMN.QCI.1
9.2.5 Parameter Optimization

N/A

eRAN
If voice services cannot get through after VoLTE is deployed, troubleshoot as follows:
1. Check whether the RRC connection procedure is normal.
2. Check whether the attach procedure is normal.
3. Check whether VoLTE is normally registered in the IMS.
4. Check whether the VoLTE call request procedure is normal.
If the results of steps 1 and 2 are abnormal, the problem is caused by the eRAN instead of
VoLTE. In this case, contact Huawei technical support.
If the results of steps 3 and 4 are abnormal, check for parameter settings on the eRAN side.
Specifically, check the following key parameters:
Whether RLCPDCPPARAGROUP.DiscardTimer is set to DiscardTimer_Infinity and
eNodeBAlgoSwitch.EutranVoipSupportSwitch is set to ON.
l If the parameter settings are incorrect, modify the parameter settings and perform the
verification again.
l If the parameter settings are incorrect, verify the following counters to check the packet
loss rate for QCI of 5:
– If packet loss for QCI of 5 occurs, contact Huawei technical support.
– Otherwise, the VoLTE fault is not caused by the eNodeB. In this case, troubleshoot
the IMS, EPC, or transport network.
Counter Name Counter Description
L.Traffic.UL.PktLoss.Loss. Number of uplink PDCP SDUs discarded for

QCI.5 services carried on DRBs with a QCI of 5 in a cell
L.Traffic.UL.PktLoss.Tot.Q Number of expected uplink PDCP SDUs for

CI.5 services carried on DRBs with a QCI of 5 in a cell
L.Traffic.DL.PktUuLoss.Lo Number of downlink PDCP SDUs discarded for

ss.QCI.5 services carried on DRBs with a QCI of 5 in a cell
over the Uu interface
L.Traffic.DL.PktUuLoss.To Number of downlink PDCP SDUs transmitted for

t.QCI.5 services carried on DRBs with a QCI of 5 in a cell
over the Uu interface
9.3 Semi-Persistent Scheduling
9.3.1 When to Use Semi-Persistent Scheduling and Deploy Power

Control
Semi-Persistent Scheduling
This feature is recommended to save cell CCE resources when the number of simultaneously
active subscribers is greater than or equal to 10 and the PDCCH CCE usage exceeds 70%.

eRAN
Semi-persistent scheduling uses fixed MCS and PRBs to transmit data during talk spurts
instead of updating MCS and PRBs at each TTI. This brings gains and reduces required
PDCCH resources. Therefore, semi-persistent scheduling is recommended in scenarios with
low-speed or where channel conditions change slowly. In high-speed or ultra-high speed cells,
UEs move fast and channel conditions change significantly. Therefore, semi-persistent
scheduling is not recommended in such scenarios.
Cells working at a bandwidth of 1.4 MHz have only six PRBs. When the UE uses semi-
persistent scheduling, the highest MCS index is only 15. This means that cell center users
(CCUs) and users near the cell center consume more PRBs, which wastes PRB resources.
Therefore, uplink and downlink semi-persistent scheduling and power control in uplink and
downlink semi-persistent scheduling are not recommended in cells working at a bandwidth of
1.4 MHz.
Power Control in Semi-Persistent Scheduling

When uplink semi-persistent scheduling is enabled, power control for uplink semi-persistent
scheduling must be enabled so that uplink IBLER converges on the target value.
The PDSCH transmit power is evenly allocated among RBs. Adjusting the PDSCH transmit
power only when performing VoIP service cannot bring gains. Therefore, it is recommended
that power control in downlink semi-persistent scheduling be disabled. When this type of
power control is disabled, fixed PDSCH power allocation is used for UEs that are scheduled
in a semi-persistent manner.

None
9.3.3 Deployment of Semi-Persistent Scheduling
UEs must support VoLTE, semi-persistent scheduling, and closed-loop power control in semi-
persistent scheduling. The EPC must support IMS.
N/A
License
The operator has purchased the license for this feature, and activated the license.

eRAN
Feature ID Feature Name Model License NE Sales Unit

Control Item
LOFD-0010 VoIP Semi- LT1S00V VoIP Semi- eNodeB per RRC

16 persistent OIP00 Persistent Connected
Scheduling Scheduling User
(FDD)

operator
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
set uplink and downlink semi-persistent scheduling for voice services.
Parameter Name Parameter ID Data Description

Source
Uplink schedule CellAlgoSwitch Network SpsSchSwitch(SpsSchSwitch)

switch .UlSchSwitch plan of this parameter specifies
(negotiatio whether to enable or disable
n not uplink semi-persistent scheduling
required) for voice services. To enable this
feature, select the
SpsSchSwitch(SpsSchSwitch)
option.
Set this parameter by referring to
9.3.1 When to Use Semi-
Persistent Scheduling and
Deploy Power Control.
DL schedule switch CellAlgoSwitch Network SpsSchSwitch(SpsSchSwitch)

.DlSchSwitch plan of this parameter specifies
(negotiatio whether to enable or disable
n not downlink semi-persistent
required) scheduling for voice services. To
enable this feature, select the
SpsSchSwitch(SpsSchSwitch)
option.

eRAN
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
set power control in uplink and downlink semi-persistent scheduling for voice services.
Paramet Parameter ID Data Source Description

er Name
Uplink CellAlgoSwitch. Network plan The CloseLoopSpsSwitch option

power UlPcAlgoSwitch (negotiation not of this parameter specifies
control required) whether to enable or disable
algorithm power control in uplink semi-
switch persistent scheduling for voice
services. To enable this feature,
select the CloseLoopSpsSwitch
option.
Downlink CellAlgoSwitch. Network plan The PdschSpsPcSwitch option of

power DlPcAlgoSwitch (negotiation not this parameter specifies whether
control required) to enable or disable power control
algorithm in downlink semi-persistent
switch scheduling for voice services. To
enable this feature, select the
PdschSpsPcSwitch option.
9.3.3.3 Precautions
If UL semi-persistent scheduling is enabled, it is recommended that CloseLoopSpsSwitch be
turned on to enable closed-loop power control for the PUSCH to ensure the convergence of
uplink IBLER. If downlink semi-persistent scheduling is enabled, turn off the
PdschSpsPcSwitch to disable PDSCH power control in semi-persistent scheduling mode.

None
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the
eNodeB, which is available in the eNodeB product documentation.

eRAN
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 9-17 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the
file.
parameters.
Table 9-17 Parameters related to semi-persistent scheduling

Data File
CellAlgoSwitch CELLALGOSWITCH LocalCellID, UlSchSwitch, User-

UlPcAlgoSwitch, defined
DlSchSwitch template

multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press
F1 when a CME window is active, and select Managing the CME > CME Guidelines >
LTE Application Management > eNodeB Related Operations > Customizing a Summary
Data File for Batch eNodeB Configuration.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB
data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts. For
detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End

eRAN

On the CME, set the parameters listed in 9.3.3.2 Data Preparation for a single eNodeB. The
procedure is as follows:
window.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
----End
Using MML Commands

l Uplink Semi-Persistent Scheduling
Run the MOD CELLALGOSWITCH command to turn on the uplink semi-persistent
scheduling switch.
l Power Control in Uplink Semi-Persistent Scheduling
Run the MOD CELLALGOSWITCH command with the PUSCH semi-persistent
scheduling closed-loop power control switch turned on.

eRAN
l Downlink Semi-Persistent Scheduling

Run the MOD CELLALGOSWITCH command turn on the downlink semi-persistent
scheduling switch.
l Power Control in Downlink Semi-Persistent Scheduling
Run the MOD CELLALGOSWITCH command turn on the switch of closed-loop
power control in downlink semi-persistent scheduling mode.

MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SpsSchSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=SpsSchSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch=CloseLoopSpsSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PdschSpsPcSwitch-0;
Uplink Semi-Persistent Scheduling

To verify uplink semi-persistent scheduling for voice services, perform the following steps:
Step 1 Run the LST CELLALGOSWITCH command to check whether uplink semi-persistent
scheduling has been activated.
LST CELLALGOSWITCH: LocalCellId=0;
Step 2 After the UE accesses the cell, use the UE to perform uplink voice services.
Step 3 Start a task on the U2000 client to monitor MCS-specific scheduling statistics.
1. On the U2000, choose Monitor > Signaling Trace > Signaling Trace Management.
2. In the left pane of the Signaling Trace Management window, choose User
Performance Monitoring > MCS Count Monitoring. Set the tracing duration, to-be-
traced MMEc (MME ID), and mTMSI(UE TMSI).
3. Check the MCS-specific scheduling statistics, as shown in Figure 9-7. If the uplink
MCS indexes are less than or equal to 15 and the number of uplink scheduling times is
about 50, uplink semi-persistent scheduling is activated for the UE. (If the UE is not far
from the eNodeB, the number of uplink scheduling times is about 50. If the UE is far
from the eNodeB, the number is greater than 50 due to packet segmentation).
Figure 9-7 Uplink MCS-specific scheduling statistics
4. In the left pane of the Signaling Trace Management window, choose Cell
Performance Monitoring >Scheduled Users Statistic Monitoring. Set the tracing
duration, to-be-traced NE information, and cell ID.

eRAN
5. On the U2000, check Total SPS ULSCH Users and Total SPS DLSCH Users, as
shown in Figure 9-8.
If the value of Total SPS ULSCH Users is greater than 0, UL semi-persistent scheduling
is activated for the UE. If the value of Total SPS DLSCH Users is greater than 0, DL
semi-persistent scheduling is activated for the UE.
Figure 9-8 Example of statistics about scheduled UEs
6. Use the following counters to check the status of uplink semi-persistent scheduling.
Counter ID Counter Counter Description
Name
1526728562 L.Sps.UL.Er Number of times of failed uplink semi-persistent

rNum scheduling transmission in a cell
1526728494 L.Sps.UL.Sc Number of times of uplink semi-persistent

hNum scheduling in a cell
----End
Downlink Semi-Persistent Scheduling

To verify downlink semi-persistent scheduling for voice services, perform the following steps:
Step 1 Run the LST CELLALGOSWITCH command to check whether downlink semi-persistent
scheduling has been activated.
LST CELLALGOSWITCH: LocalCellId=0;
Step 2 After the UE accesses the cell, use the UE to perform downlink voice services.
2. In the left pane of the displayed window, choose User Performance Monitoring >
MCS Count Monitoring. Set the tracing duration, to-be-traced MMEc (MME ID), and
mTMSI(UE TMSI).
3. Check the MCS-specific scheduling statistics, as shown in Figure 9-9. If the downlink
MCS indexes are less than or equal to 15 and the number of downlink scheduling times
is about 50, downlink semi-persistent scheduling has been performed for the UE.

eRAN
Figure 9-9 Downlink MCS-specific scheduling statistics
4. Use the following counters to check the status of downlink semi-persistent scheduling.
1526728563 L.Sps.DL.ErrNum Number of times of failed downlink

semi-persistent scheduling
transmission in a cell
1526728495 L.Sps.DL.SchNum Number of times of downlink semi-

persistent scheduling in a cell
----End
Power Control in Uplink Semi-Persistent Scheduling

To check whether the IBLER values can converge when closed-loop power control in PUSCH
semi-persistent scheduling is enabled, perform the following steps:
Step 1 Run the LST CELLALGOSWITCH command to check whether closed-loop power control
in PUSCH semi-persistent scheduling is enabled.
Step 2 After the UE accesses the cell, use the UE to perform uplink voice services.
Step 3 Start an IBLER monitoring task on the U2000 client to monitor IBLER values.
2. In the left pane of the displayed window, choose User Performance Monitoring >
BLER Monitoring. Set the tracing duration and MMEc (MME ID).
3. Check on the U2000 client whether the IBLER values converge, as shown in Figure
9-10. If the Uplink IBLER(Permillage) values are less than 100 (that is, the IBLER
values are less than 10%), the IBLER values converge. If the UE is close to the eNodeB,
the IBLER values are relatively small. If the UE is far from the eNodeB, the IBLER
values are relatively large. In the two cases, the IBLER values do not converge.

eRAN
Figure 9-10 Uplink IBLER monitoring results
----End
Power Control in Downlink Semi-Persistent Scheduling

Step 1 Run the LST CELLALGOSWITCH command to check whether power control in downlink
semi-persistent scheduling is enabled.
Step 2 If it is not enabled, run the following command to disable it:

----End
N/A

Table 9-18 Parameters related to semi-persistent scheduling

Data File
CellAlgoSwitch CELLALGOSWITCH LocalCellID, UlSchSwitch, User-

UlPcAlgoSwitch, defined
sheet
DlSchSwitch

eRAN

Using MML Commands

l Uplink Semi-Persistent Scheduling
Run the MOD CELLALGOSWITCH command with the uplink semi-persistent
scheduling switch turned off.
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SpsSchSwitch-0;
MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch=CloseLoopSpsSwitch-0;
l Downlink Semi-Persistent Scheduling

Run the MOD CELLALGOSWITCH command with the downlink semi-persistent
scheduling switch turned off.
MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=SpsSchSwitch-0;

Semi-persistent scheduling reduces PDCCH consumption, increases voice service capacity,
but slightly deteriorates voice service quality.
You can compare counters in the following table given the same number of UEs in a cell, UE
location, and traffic model. If the values for these counters decrease after semi-persistent
scheduling is enabled, PDCCH consumption is reduced.
1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH CCEs used for

uplink DCI
1526728305 L.ChMeas.CCE.DLUsed Number of PDCCH CCEs used for

downlink DCI
For details about monitoring, see 9.2.4.4 Voice Capacity and 9.2.4.3 Voice Quality.
Power control in semi-persistent scheduling impacts the voice quality of voice service users.
For details, see 9.2.4.3 Voice Quality.
NOTE
Power control in semi-persistent scheduling must work with semi-persistent scheduling.

N/A

eRAN
If the result of L.Sps.UL.ErrNum/L.Sps.UL.SchNum is relatively high (greater than 10%),
check whether the CloseLoopSpsSwitch option of the
CELLALGOSWITCH.UlPcAlgoSwitch parameter is selected:
l If the option is deselected, select this option.

l If the option is selected, contact Huawei technical support.
9.4 TTI Bundling
9.4.1 When to Deploy TTI Bundling

It is recommended that TTI bundling be enabled to improve the coverage of cell edges and in
scenarios where indoor voice services are served by outdoor sites. This function is dependent
on UEs. Therefore, a compatibility test is required before enabling this feature.
The RRC Connection Reconfiguration message instructs UEs to enter or exit the TTI
bundling state. UE channel conditions change significantly in high speed or ultra high speed
scenarios. As a result, UEs frequently enter and exit the TTI bundling state, thereby increasing
signaling load on the Uu interface, degrading voice quality, and increasing the risk of call
drops. Therefore, it is recommended that TTI bundling be disabled in high speed or ultra high
speed cells.
Cells working at a bandwidth of 1.4 MHz have only six PRBs. TTI bundling consumes
resources in the time domain. Therefore, it is recommended that TTI bundling be disabled in
cells working at a bandwidth of 1.4 MHz.

None
9.4.3 Deployment of TTI Bundling
UEs must support VoLTE and TTI bundling, and the EPC must support IMS-based voice
services.
According to 3GPP specifications, TTI bundling is supported only by cells with subframe
configuration 0, 1, or 6.
License

eRAN
Feature ID Feature Model License NE Sales Unit

Name Control
Item
LOFD-00104 TTI Bundling LT1S00TT TTI eNodeB per Cell

8 IB00 Bundling
(FDD)

operator
The following table describes the parameter that must be set in the CellAlgoSwitch and
CellUlschAlgo MOs to set TTI bundling.

Name
Uplink CellAlgoSwitch.UlSch Network plan The

schedule Switch (negotiation TtiBundlingSwitch(TtiBun
switch not required) dlingSwitch) option of this
parameter specifies whether
to enable TTI bundling.
l In common scenarios,
deselect this option.
l When the UE's channel
quality is poor and
transmit power is limited,
select this option.
TTI Bundling CellAlgoSwitch.TtiBu Network plan This parameter specifies a

Trigger ndlingTriggerStrategy (negotiation TTI bundling trigger policy.
Strategy not required) l If TTI bundling applies
only to VoLTE services,
set this parameter to
SERVICE_VOIP(SERV
ICE_VOIP).
l If TTI bundling applies to
VoLTE or a combination
of VoLTE and data, set
this parameter to
SERVICE_MULTIAPP(
SERVICE_MULTIAPP)
.

eRAN

Name
Statistic Num CellAlgoSwitch.Statist Network plan This parameter specifies a

Threshold for icNumThdForTtibTrig (negotiation threshold number of
TTIB Trigger not required) consecutive times that the
measured SINR is less than
the target SINR. When the
actual number reaches this
threshold number, the
eNodeB instructs the UE to
enter the TTI bundling state.
The default parameter value
is recommended.
Statistic Num CellAlgoSwitch.Statist Network plan This parameter specifies a

Threshold for icNumThdForTtibExit (negotiation threshold number of
TTIB Exit not required) consecutive times that the
measured SINR is greater
than the sum of the target
SINR and the
CellAlgoSwitch.HystToExit
TtiBundling parameter value.
When the actual number
reaches this threshold
number, the eNodeB instructs
the UE to exit the TTI
bundling state. The default
value is recommended.
Hysteresis to CellAlgoSwitch.HystT Network plan This parameter specifies an

Exit TTI oExitTtiBundling (negotiation SINR threshold for exiting
Bundling not required) the TTI bundling state. This
threshold is equal to the sum
of the SINR threshold for
entering the TTI bundling
state and the
CellAlgoSwitch.HystToExit
TtiBundling parameter value.
The default value is
recommended.
TTIB Max CellAlgoSwitch.TtiBu Network plan This parameter specifies the

Number of ndlingRlcMaxSeg- (negotiation maximum number of uplink
RLC Num not required) RLC segments for UEs in the
Segments TTI bundling state. The
default value is
recommended.

eRAN

Name
TTIB Max CellAlgoSwitch.TtiBu Network plan This parameter specifies the

Number of ndlingHarqMaxTx- (negotiation maximum number of HARQ
HARQ Num not required) transmissions for UEs in the
Transmissions TTI bundling state. The
default value is
recommended.
9.4.3.3 Precautions
None

None
into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in
Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB
product documentation.
l The managed objects (MOs) in Table 9-19 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the
file.
parameters.
Table 9-19 Parameters related to TTI bundling

MO Sheet in the Summary Parameter Group Remark
Data File s
CellAlgoSwitch CELLALGOSWITCH LocalCellID, UlSchSwitch User-

defined
template

eRAN
MO Sheet in the Summary Parameter Group Remark

Data File s
CellUlschAlgo CELLULSCHALGO LocalCellID, User-

TtiBundlingTriggerStrategy, defined
StatisticNumThdForTtibTrig, template
StatisticNumThdForTtibExit,
HystToExitTtiBundling,
TtiBundlingRlcMaxSegNum,
TtiBundlingHarqMaxTxNum

----End

window.

eRAN
----End
Using MML Commands

Step 1 Run the MOD CELLALGOSWITCH command to activate TTI bundling.
Step 2 (Optional) Run the MOD CellULSCHALGO command and set parameters in 9.4.3.2 Data
Preparation as required.
----End

MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=TtiBundlingSwitch-1;

To verify TTI bundling for UEs far from the eNodeB, perform the following steps:
Step 1 Run the LST CELLALGOSWITCH command to check whether TTI bundling has been
activated.

eRAN
Step 2 Start a Uu tracing task on the U2000 client. Select test cells when creating the task.
Step 3 Enable a UE to access a cell and perform UL VoIP services.
Step 4 Enable the UE to be far from the eNodeB until the RRC_CONN_RECFG and
RRC_CONN_RECFG_CMP messages are present in the Uu tracing result. Check the IEs
mac-MainConfig > ul-SCH-Config > ttiBundling in the RRC_CONN_RECFG message. The
value TRUE (as shown in Figure 9-12) indicates that TTI bundling has been activated for UL
VoIP.
Figure 9-12 RRC_CONN_RECFG message (indicating that TTI bundling has been activated)
Step 5 Enable the UE to be close to the eNodeB. Check the IEs mac-MainConfig > ul-SCH-Config >
ttiBundling in the RRC_CONN_RECFG message. The value FALSE (as shown in Figure
9-13) indicates that TTI bundling has been deactivated for UL VoIP.

eRAN
Figure 9-13 RRC_CONN_RECFG message (indicating that TTI bundling has been
deactivated)
Step 6 Use the following counters to check the status of TTI bundling. TTI bundling is enabled if the
values of these counters are not 0.
1526728496 L.Traffic.User.TtiBundling. Average number of UEs for which TTI

Avg bundling is enabled in a cell
1526728911 L.Signal.Num.TtiBundling. Number of messages that trigger the

Enter entering of the TTI bundling mode
1526728912 L.Signal.Num.TtiBundling. Number of messages that trigger the

Exit exiting of the TTI bundling mode
----End
N/A


eRAN
Table 9-20 Parameters related to TTI bundling

MO Sheet in the Summary Parameter Group Setti
Data File ng
Note
s
CellAlgoSwitch CellAlgoSwitch LocalCellID, UlSchSwitch User-

define
d
sheet
CellUlschAlgo CellUlschAlgo LocalCellID, User-

TtiBundlingTriggerStrategy, define
StatisticNumThdForTtib- d
Trig, StatisticNumThdForT- sheet
tibExit, HystToExitTtiBun-
dling, TtiBundlingRlcMax-
SegNum, TtiBundlingHarq-
MaxTxNum

Using MML Commands

Run the MOD CELLALGOSWITCH command to deactivate TTI bundling.

MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=TtiBundlingSwitch-0;

TTI bundling improves uplink coverage for voice service users or improves uplink packet loss
rate.
For details, see 9.2.4.3 Voice Quality.

N/A
N/A
9.5 UL RLC Segmentation Enhancement

eRAN
9.5.1 When to Use Uplink RLC Segmentation Enhancement

It is recommended that this feature be enabled for VoLTE to improve the cell edge coverage
of the PUSCH.

None
9.5.3 Deployment
The EPC must support IMS-based voice services.
N/A
License
N/A

operator
The following table describes the parameters that must be set in the CellUlschAlgo MO for
UEs supporting the uplink RLC segmentation enhancement function.

eRAN

Name
Uplink Voip CellUlschAlgo.UlVoip Network plan This parameter determines

Rlc Maximum RlcMaxSegNum (negotiation whether to enable the uplink
Segmentation not required) RLC segmentation
Number enhancement feature for
VoLTE services on UEs not in
the TTI bundling state and
specifies the maximum
number of uplink RLC
segments.
l If this parameter is set to
0, this feature is disabled.
l If this parameter is set to a
non-zero value X, this
feature is enabled and the
maximum number of
uplink RLC segments in
the non-TTI-bundling
state is X.
9.5.3.3 Precautions
None

None
parameters.

eRAN
Table 9-21 Parameters related to UL RLC segmentation enhancement
MO Sheet in the Summary Parameter Group Remar

Data File ks
CELLULSCH CELLULSCHALGO LocalCellID, User-

ALGO UlVoipRlcMaxSegNum defined
templat
e

----End

window.

eRAN
----End
Using MML Commands

Run the MOD CELLULSCHALGO command with the Uplink Voip Rlc Maximum
Segmentation Number parameter set to the recommended value of the corresponding RAT.

MOD CELLULSCHALGO: LocalCellId=0, UlVoipRlcMaxSegNum=20;

After uplink RLC segmentation enhancement is activated with the Uplink Voip Rlc
Maximum Segmentation Number parameter set to a non-zero value, the MCS index should
be increased for a UE at the cell edge to control the number of uplink RLC segments. To
verify this, perform the following steps:
Step 1 Run the LST CELLULSCHALGO command to check whether the Uplink Voip Rlc
Maximum Segmentation Number parameter is set to 0. If it is set to 0, go to Step 2. If it is
set to a non-zero value, run the following command to change it to 0 (x represents the local
cell ID):

eRAN
Step 2 Use a UE that does not support TTI bundling to access the cell. Initiate a UL VoLTE service
on the UE.
1. Choose Monitor > Signaling Trace > Signaling Trace Management.
2. In the left navigation tree in the Signaling Trace Management tab page, choose User
Performance Monitoring > MCS Count Monitoring. Set the monitoring duration and
to-be-traced MMEc (MME ID), and mTMSI (UE TMSI).
3. Observe MCS-specific uplink scheduling statistics, including the number of scheduling
times and the number of RBs. Move the UE to the cell edge, where channel quality is
poor. That is, move the UE until the monitoring result indicates that the MCS with an
index of 0 is selected and a maximum of three RBs are allocated by uplink scheduling of
the UE.
Step 4 Run the MOD CELLULSCHALGO command with the Uplink Voip Rlc Maximum
Segmentation Number parameter set to a non-zero value.
NOTE
To ensure satisfactory voice quality, you are advised to set the Uplink Voip Rlc Maximum
Segmentation Number parameter to its recommended value. However, to facilitate this verification,
you can set this parameter to a smaller non-zero value so that the selected MCS index increases
noticeably.
Step 5 On the U2000 client, observe the MCS-specific uplink scheduling statistics. If the MCS index
is greater than 0 but the number of RBs is still less than or equal to 3, the eNodeB has
increased the MCS index to restrict the number of uplink RLC segments. (The smaller the
value of CellAlgoSwitch.UlVoipRlcMaxSegNum, the larger the MCS index.)
Step 6 On a live network, you can also check the packet loss rate of uplink voice services and the
proportion of uplink low-order MCSs for the PUSCH (for example, MCS index 0 or 1). If
both of them decrease, RLC segmentation enhancement has taken effect.
1526727412 L.ChMeas.PUSCH.MCS.0 Number of times that MCS

to 1526727443 to L.ChMeas.PUSCH.MCS.31 indexes 0 to 31 are used for
PUSCH scheduling
1526727961 L.Traffic.UL.PktLoss.Loss.QCI. Number of uplink PDCP

1 SDUs discarded for services
carried on DRBs with QCIs
of 1 in a cell
1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1 Number of expected uplink

PDCP SDUs for services
of 1 in a cell
----End
N/A

eRAN

Table 9-22 Parameters related to UL RLC segmentation enhancement
MO Sheet in the Summary Parameter Group Rem

Data File arks

UlVoipRlcMaxSegNum defin
ed
templ
ate

Using MML Commands

Run the MOD CELLULSCHALGO command with the Uplink Voip Rlc Maximum
Segmentation Number parameter set to 0.


UL RLC segmentation enhancement improves UL packet loss rate of VoLTE services.
Monitor the performance of this feature through the following counters.
ID Name Description
1526727961 L.Traffic.UL.PktLoss.L Total number of discarded uplink PDCP SDUs

oss.QCI.1 for DRB services with the QCI of 1 in a cell
1526727962 L.Traffic.UL.PktLoss.To Total number of expected uplink data packets

t.QCI.1 for DRB services with the QCI of 1 in a cell

eRAN

N/A
N/A
9.6 Voice Characteristic Awareness Scheduling
9.6.1 When to Use Voice Characteristic Awareness Scheduling

This feature is recommended when VoLTE has been deployed and the performance of VoLTE
needs to be preferentially ensured.

None
9.6.3 Deployment
N/A
License
Feature ID Feature Model License Control NE Sales Unit

Name Item
LOFD-08122 Voice LT1S0 Voice Characteristic eNodeB per Cell

9 Characteristic 0VCA Awareness
Awareness S00 Scheduling(FDD)
Scheduling

operator

eRAN
The following table describes the parameter that must be set in the CELLULSCHALGO to
configure Voice Characteristic Awareness Scheduling for a cell.
Parameter ID Data Source Setting Notes
CELLULSCHALGO.UlDe Network plan This parameter specifies a policy

laySchStrategy (negotiation not for uplink delay-based dynamic
required) scheduling. If this parameter is set
to NO_DELAYSCH, uplink delay-
based dynamic scheduling is
disabled. If this parameter is set to
VOIP_DELAYSCH, uplink delay-
based dynamic scheduling for VoIP
is enabled. The eNodeB adjusts
scheduling priorities based on VoIP
packet delays during uplink
dynamic scheduling, thereby
increasing the MOS and VoIP
capacity when the cell is heavily
loaded.
CELLULSCHALGO.UlEn Network plan The UlVoLTEDataSizeEstSwitch

hencedVoipSchSw (negotiation not option of the
required) CELLULSCHALGO.UlEnhence
dVoipSchSw parameter specifies
whether to enable uplink VoLTE
volume estimation for dynamic
scheduling. This estimation
function shortens VoLTE packet
delays, reduces the packet loss rate,
and improves voice quality.

eRAN
Parameter ID Data Source Setting Notes
eNBCellRsvdPara.RsvdSw Network plan l When the RsvdSwPara3_bit1

Para3 (negotiation not option of the
required) eNBCellRsvdPara.RsvdSwPar
a3 parameter is selected and the
data scheduling wait time is the
same, the SR scheduling
priority for UEs with QCI of 1
is higher than that for UEs
without QCI of 1.
l When the RsvdSwPara3_bit1
option of the
eNBCellRsvdPara.RsvdSwPar
a3 parameter is deselected, the
eNodeB sorts the priorities of
scheduling triggered by SR and
BSR of VoLTE services. A
longer scheduling wait time
indicates a higher scheduling
priority.
9.6.3.3 Precautions
None

None
parameters.

eRAN
Table 9-23 Parameters related to voice characteristic awareness scheduling

Data File ks
CellUlschAlgo CellUlschAlgo LocalCellId, User-

UlDelaySchStrategy defined
templat
e

UlEnhencedVoipSchSw, defined
UlVoLTEDataSizeEstSwitch, templat
e

----End

window.

eRAN
----End
Using MML Commands

Step 1 Run the MOD CELLULSCHALGO command to enable uplink delay-based dynamic
scheduling.
Step 2 Run the MOD CELLULSCHALGO command to enable uplink VoLTE volume estimation
for dynamic scheduling.
----End

MOD CELLULSCHALGO: LocalCellId=0, UlDelaySchStrategy=VOIP_DELAYSCH;
MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoLTEDataSizeEstSwitch-1;

eRAN

Step 1 On the U2000 client, start performance monitoring tasks for counters listed in Table 9-24.
Step 2 On the U2000 client, check the the number of CCEs allocated for uplink QCI 1 services and
the duration of receiving uplink QCI 1 data at the PDCP layer before and after the feature is
enabled. If both of them increase, uplink VoLTE volume estimation for dynamic scheduling
has been activated. In addition, check the proportion of VQIs that indicate poor or bad voice
quality. If the proportion decreases, uplink delay-based dynamic scheduling have been
activated.
Table 9-24 Counters for monitoring Voice Characteristic Awareness Scheduling
1526736735 L.ChMeas.CCE.ULUsed.VoIP Number of PDCCH CCEs allocated

to uplink VoIP
1526726777 L.Thrp.Time.UL.QCI.1 Duration of receiving uplink PDCP

PDUs for services with QCIs of 1 in
a cell
1526728411 L.Voice.VQI.UL.Excellent.Time Number of times uplink voice

s quality is Excellent
1526728412 L.Voice.VQI.UL.Good.Times Number of times uplink voice

quality is Good
1526728413 L.Voice.VQI.UL.Accept.Times Number of times uplink voice

quality is Accept
1526728414 L.Voice.VQI.UL.Poor.Times Number of times uplink voice

quality is Poor
1526728415 L.Voice.VQI.UL.Bad.Times Number of times uplink voice

quality is Bad
----End
N/A


eRAN
Table 9-25 Parameters related to voice characteristic awareness scheduling

Data File arks

UlDelaySchStrategy defin
ed
templ
ate

UlEnhencedVoipSchSw defin
ed
templ
ate

Using MML Commands

Run the MOD CELLULSCHALGO command to disable uplink delay-based dynamic
scheduling.
Run the MOD CELLULSCHALGO command to disable uplink VoLTE volume estimation
for dynamic scheduling.
Run the MOD CELLULSCHALGO command with the uplink VoIP delay scheduling switch
turned off.

MOD CELLULSCHALGO: LocalCellId=0, UlDelaySchStrategy=NO_DELAYSCH;
MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoLTEDataSizeEstSwitch-0;

After voice characteristic awareness scheduling is enabled, you can use the following counters
to monitor whether the uplink VoLTE packet loss rate decreases.

ID
1526727961 L.Traffic.UL.PktLoss.L Number of uplink PDCP SDUs discarded for

oss.QCI.1 services carried on DRBs with QCIs of 1 in a
cell

eRAN

ID
1526727962 L.Traffic.UL.PktLoss.T Number of expected uplink PDCP SDUs for

ot.QCI.1 services carried on DRBs with QCIs of 1 in a
cell

N/A
N/A
9.7 Uplink Compensation Scheduling
9.7.1 When to Use Uplink Compensation Scheduling

If VoLTE has been deployed, it is recommended that uplink compensation scheduling be
enabled to reduce the number of uplink VoLTE packet losses in heavy traffic scenarios.

None
9.7.3 Deployment
N/A
License
N/A

operator

eRAN
The following table describes the parameters that must be set in the CellUlschAlgo MO to
enable or disable uplink compensation scheduling for a cell.

Name
Uplink CellUlschAlgo.UlEnh Network plan The UlVoipSchOptSwitch

Enhanced encedVoipSchSw (negotiation option of the
Voip Schedule not required) CellUlschAlgo.UlEnhenced
Switch VoipSchSw parameter
specifies whether to enable
uplink compensation
scheduling.
l When this switch is turned
off, the function does not
take effect.
l When this switch is turned
on, uplink dynamic
scheduling is triggered if
the scheduling interval
exceeds a threshold. The
scheduling interval is a
period during which a
VoLTE user is not
dynamically scheduled in
the uplink. In this way,
VoLTE users can be
timely scheduled in the
uplink and the number of
PDCP packet losses due to
discard timer expiry can
be reduced even in heavy
traffic scenarios.
9.7.3.3 Precautions
None

None

eRAN
parameters.
Table 9-26 Parameters related to uplink compensation scheduling

Data File ks

UlEnhencedVoipSchSw.UlV defined
oipSchOptSwitch templat
e


eRAN
----End

window.
----End

eRAN
Using MML Commands

Run the MOD CELLULSCHALGO command to enable uplink compensation scheduling.

MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoipSchOptSwitch-1;

Step 1 Run the LST CELLULSCHALGO command to check whether the UlVoipSchOptSwitch is
turned off. If the switch is turned on, run the following command to turn it off. If the switch
has been turned off, go to Step 2.
Step 2 After the UE accesses the cell, use the UE to originate uplink voice services.
Step 3 On the U2000 client, use the counters listed in Table 9-27 to monitor the performance.
Step 4 Run the MOD CELLULSCHALGO command to turn on the UlVoipSchOptSwitch.
Step 5 On the U2000 client, check the values of L.ChMeas.CCE.ULUsed.VoIP and

L.ChMeas.CCE.ULUsed.VoIP; if these values increase, this feature has been activated. In
addition, check the uplink VoIP packet loss rate (calculated based on
L.Traffic.UL.PktLoss.Loss.QCI.1 and L.Traffic.UL.PktLoss.Loss.QCI.1) to see the effect of
this feature.
Table 9-27 Counters
1526736735 L.ChMeas.CCE.ULUsed.VoIP Number of PDCCH CCEs

allocated to uplink VoIP
1526726777 L.Thrp.Time.UL.QCI.1 Receive duration of uplink

PDCP PDUs for services
1526727961 L.Traffic.UL.PktLoss.Loss.QCI.1 Number of uplink PDCP

SDUs discarded for services
of 1 in a cell
1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1 Number of expected uplink

PDCP SDUs for services
of 1 in a cell
----End
N/A

eRAN

Table 9-28 Parameters related to uplink compensation scheduling

Data File ks

UlEnhencedVoipSchSw.Ul defined
VoipSchOptSwitch templat
e

Using MML Commands

Run the MOD CELLULSCHALGO command to disable uplink compensation scheduling.


After uplink compensation scheduling is enabled, you can use the following counters to
monitor whether the uplink VoLTE packet loss rate decreases.

ID

cell

cell

eRAN

N/A
N/A
9.8 Voice-Specific AMC
9.8.1 When to Use Voice-Specific AMC

If VoLTE has been deployed, it is recommended that voice-specific AMC be used.
You are advised to configure this feature based on the number of VoLTE users and capacity
policies. For example, if the number of online VoLTE users is small and VoLTE performance
needs to be preferentially ensured, it is recommended that a small target IBLER be configured
for VoLTE users.

None
9.8.3 Deployment
N/A
License
None

operator
The following table describes the parameter that must be set in the CELLULSCHALGO to
configure Voice-Specific AMC for a cell.

eRAN

Name
SINR CellAlgoSwitch.SinrA Network plan This parameter specifies a

Adjustment djTargetIblerfor- (negotiation target IBLER for adjusting
Target IBLER VoLTE not required) the SINRs used in dynamic
for VoLTE scheduling of VoLTE users
not in the TTI bundling state.
It is recommended that this
parameter be set to a value
less than or equal to 10% in
light-traffic scenarios and to
10% in heavy-traffic
scenarios.
9.8.3.3 Precautions
None

None
parameters.

eRAN
Table 9-29 Parameters related to voice-specific AMC

Data File ks
CELLULSCH CELLULSCHALGO LocalCellID, User-

ALGO SinrAdjTargetIblerforVoLTE defined
templat
e

----End

window.

eRAN
----End
Using MML Commands

Run the MOD CELLULSCHALGO to set a target IBLER for adjusting VoLTE SINRs.

MOD CELLULSCHALGO: LocalCellId=0, SinrAdjTargetIblerforVoLTE=3;

Step 1 Run the LST CELLULSCHALGO command to check whether the value of SINR target
IBLER adjustment is 10. If the value is not 10, run the following command to change it. If
the value is 10, go to Step 2.
Step 2 After the UE accesses the cell, use the UE to originate uplink voice services.
Step 3 On the U2000 client, start performance monitoring tasks for counters listed in Table 9-30.
Step 4 Run the MOD CELLULSCHALGO command to set the target IBLER for VoLTE SINR
adjustment to a value rather than 10.

eRAN
NOTE
To ensure voice performance, you are advised to set the target IBLER to the recommended value. To
facilitate activation observation, you can also set it to a smaller non-zero value so that a more obvious
IBLER decrease can be seen.
Step 5 On the U2000 client, check the values of the counters listed in Table 9-30. If the uplink
IBLER of QCI 1 services (calculated using the following formula) converges on the target
IBLER, this feature has been activated.
Table 9-30 Counters

1526737730 L.Traffic.UL.SCH.QPSK.ErrT Number of erroneously

B.Ibler.QCI.1 transmitted QCI 1 service TBs
on the UL-SCH during the
initial transmission in QPSK
modulation mode
1526737731 L.Traffic.UL.SCH. Number of erroneously

16QAM.ErrTB.Ibler.QCI.1 transmitted QCI 1 service TBs
initial transmission in 16
Quadrature Amplitude
Modulation (16QAM)
modulation mode
1526737732 L.Traffic.UL.SCH. Number of erroneously

64QAM.ErrTB.Ibler.QCI.1 transmitted QCI 1 service TBs
initial transmission in 64QAM
modulation mode
1526737724 L.Traffic.UL.SCH.QPSK.TB.Q Number of initially transmitted

CI.1 QCI 1 service TBs on the UL-
SCH in QPSK modulation
mode
1526737725 L.Traffic.UL.SCH. Number of initially transmitted

16QAM.TB.QCI.1 QCI 1 service TBs on the UL-
SCH in 16QAM modulation
mode
1526737726 L.Traffic.UL.SCH. Number of initially transmitted

64QAM.TB.QCI.1 QCI 1 service TBs on the UL-
SCH in 64QAM modulation
mode
----End

eRAN
N/A

Table 9-31 Parameters related to voice-specific AMC

Data File arks

SinrAdjTargetIblerforVoLTE defin
ed
templ
ate

Using MML Commands

Run the MOD CELLULSCHALGO command to set the target IBLER for VoLTE SINR
adjustment to 10.


After voice-specific AMC is enabled, you can use the following counters to monitor whether
the uplink VoLTE packet loss rate decreases.

ID

cell

eRAN

ID

cell

N/A
N/A

eRAN
VoLTE Feature Parameter Description 10 Parameters
10 Parameters
Table 10-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
VQMAl VqiExce MOD None None Meaning: Indicates the voice quality indicator (VQI)
go llentThd VQMA threshold above which the voice quality is considered
LGO as excellent.
LST GUI Value Range: 0~500
VQMA Unit: None
LGO
Actual Value Range: 0~5, step:0.01
Default Value: 400
VQMAl VqiPoor MOD None None Meaning: Indicates the voice quality indicator (VQI)
go Thd VQMA threshold for determining the voice quality is poor. If
LGO the VQI evaluation value is greater than the
LST VqiBadThd parameter value and less than or equal to
VQMA the VqiPoorThd parameter value, the voice quality is
LGO considered as poor. If the VQI evaluation value is less
than or equal to the VqiGoodThd parameter value and
greater than the VqiPoorThd parameter value, the
voice quality is considered as accepted.
GUI Value Range: 0~500
Unit: None
Default Value: 200

eRAN

nd
VQMAl VqiGoo MOD None None Meaning: Indicates the voice quality indicator (VQI)
go dThd VQMA threshold for determining the voice quality is good. If
LGO the VQI evaluation value is greater than the
LST VqiGoodThd parameter value and less than or equal
VQMA to the VqiExcellentThd parameter value, the voice
LGO quality is considered as good. If the VQI evaluation
value is less than or equal to the VqiGoodThd
parameter value and greater than the VqiPoorThd
parameter value, the voice quality is considered as
accepted.
Unit: None
Default Value: 300
VQMAl VqiBad MOD None None Meaning: Indicates the voice quality indicator (VQI)
go Thd VQMA threshold equal to or below which the voice quality is
LGO considered as bad.
VQMA Unit: None
LGO
Default Value: 100

eRAN

nd
GlobalP VoipWit MOD LOFD-0 Automat Meaning:

rocSwitc hGapMo GLOBA 02001 / ic Indicates whether VoIP UEs are allowed to enter the
h de LPROC TDLOF Neighbo periodical measurement gap and whether they can exit
SWITC D-00200 ur the gap if VoIP services are initiated during the gap. A
H 1 Relation VoIP UE can enter the periodical measurement gap
LST LOFD-0 (ANR) during GSM and LTE buffer zone optimization or
GLOBA 02002 / Inter- periodic inter-frequency/RAT measurements in cell
LPROC TDLOF RAT tracing. If a UE enters the measurement gap and then
SWITC D-00200 ANR VoIP services are initiated for this UE, fast ANR,
H 2 PCI active PCI conflict detection, GSM and LTE buffer
LOFD-0 Collisio zone optimization, or periodic inter-frequency/RAT
02007 / n measurements in cell tracing can trigger the UE's
TDLOF Detectio exiting from the gap.
D-00200 n& If this parameter is set to ENBALE, VoIP UEs are
7 Self- allowed to enter the periodic measurement gap during
MRFD- Optimiz GSM and LTE buffer zone optimization and periodic
231808 ation inter-frequency/RAT measurement in cell tracing. The
GSM parameter setting does not affect the entering of the
and LTE gap during fast ANR and active PCI conflict detection
Buffer for VoIP UEs.
Zone
Optimiz If this parameter is set to DISABLE, VoIP UEs are
ation(LT prohibited to enter the periodic measurement gap and
E) the UEs entering the gap and initiating VoIP services
cannot exit the gap.
GUI Value Range: DISABLE(disable),
ENABLE(enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: ENABLE(enable)

eRAN

nd
CellUlsc TtiBund MOD LOFD-0 TTI Meaning:

hAlgo lingTrig CELLU 01048 Bundlin Indicates the policy of triggering transmission time
gerStrat LSCHA g interval (TTI) bundling when TtiBundlingSwitch of
egy LGO the UlSchSwitch parameter is on.
LST
CELLU If this parameter is set to SERVICE_VOIP, the
LSCHA eNodeB triggers TTI bundling for UEs running only
LGO VoIP services in the uplink.
If this parameter is set to SERVICE_MULTIAPP, the
eNodeB triggers TTI bundling for all UEs running
VoIP services, including UEs running only VoIP
services and UEs running both VoIP services and data
services in the uplink.
GUI Value Range:
SERVICE_VOIP(SERVICE_VOIP),
SERVICE_MULTIAPP(SERVICE_MULTIAPP)
Unit: None
Actual Value Range: SERVICE_VOIP,
SERVICE_MULTIAPP
Default Value: SERVICE_VOIP(SERVICE_VOIP)
CellUlsc Statistic MOD LOFD-0 TTI Meaning: Indicates the threshold of channel quality
hAlgo NumTh CELLU 01048 Bundlin statistic times during which the channel quality of a
dForTtib LSCHA g UE consistently meets conditions for entering
Trig LGO transmission time interval (TTI) bundling. Before a
LST UE enters TTI bundling, the eNodeB performs
CELLU statistic on the channel quality of the UE at the
LSCHA interval of 20 ms or longer. If the number of statistic
LGO times during which the channel quality of the UE
consistently meets conditions for entering TTI
bundling is greater than this parameter value, the UE
enters TTI bundling. This parameter helps delay the
time for entering TTI bundling and decrease the
probability of unnecessary TTI bundling entering
caused by wireless signal fluctuation. This parameter
applies only to LTE FDD networks.
GUI Value Range: N5_TTIB_ENTER(5),
N10_TTIB_ENTER(10), N15_TTIB_ENTER(15),
N20_TTIB_ENTER(20)
Unit: None
Actual Value Range: N5_TTIB_ENTER,
N10_TTIB_ENTER, N15_TTIB_ENTER,
N20_TTIB_ENTER
Default Value: N10_TTIB_ENTER(10)

eRAN

nd
CellUlsc Statistic MOD LOFD-0 TTI Meaning: Indicates the threshold of channel quality
hAlgo NumTh CELLU 01048 Bundlin statistic times during which the channel quality of a
dForTtib LSCHA g UE consistently meets conditions for exiting from
Exit LGO transmission time interval (TTI) bundling. Before a
LST UE exits from TTI bundling, the eNodeB performs
CELLU statistic on the channel quality of the UE at the
LSCHA interval of 20 ms or longer. If the number of statistic
LGO times during which the channel quality of the UE
consistently meets conditions for exiting from TTI
bundling is greater than this parameter value, the UE
exits TTI bundling. This parameter helps delay the
time for UEs to exit from TTI bundling and decrease
the probability of unnecessary exit from TTI bundling
caused by wireless signal fluctuation. This parameter
applies only to LTE FDD networks.
GUI Value Range: N10_TTIB_EXIT(10),
N20_TTIB_EXIT(20), N40_TTIB_EXIT(40),
N80_TTIB_EXIT(80)
Unit: None
Actual Value Range: N10_TTIB_EXIT,
N20_TTIB_EXIT, N40_TTIB_EXIT,
N80_TTIB_EXIT
Default Value: N20_TTIB_EXIT(20)
CellUlsc HystToE MOD LOFD-0 TTI Meaning: Indicates the hysteresis of the signal to
hAlgo xitTtiBu CELLU 01048 Bundlin interference plus noise ratio (SINR) threshold for
ndling LSCHA g exiting from transmission time interval (TTI) bundling
LGO against the SINR threshold for entering TTI bundling.
LST The hysteresis decreases the probability of
CELLU unnecessary exit from TTI bundling caused by
LSCHA wireless signal fluctuation. This parameter applies
LGO only to LTE FDD networks.
Unit: None
Actual Value Range: 3~6
Default Value: 5

eRAN

nd
CellUlsc TtiBund MOD LOFD-0 TTI Meaning: Indicates whether to apply upper limit
hAlgo lingRlc CELLU 01048 Bundlin control on service data unit (SDU) segmentation at the
MaxSeg LSCHA g radio link control (RLC) layer in the uplink for
Num LGO services scheduled in transmission time interval (TTI)
LST bundling mode and the maximum SDU segments at
CELLU the RLC layer. If this parameter is set to 0, the upper
LSCHA limit control on SDU segmentation at the RLC layer is
LGO disabled in the uplink for services scheduled in TTI
bundling mode. If this parameter is set to a non-zero
value X, upper limit control on SDU segmentation at
the RLC layer is enabled and a maximum of X SDU
segments that can be divided for services in uplink
dynamic scheduling in TTI bundling mode. This
parameter applies only to LTE FDD networks.
Unit: None
Default Value: 4
CellUlsc TtiBund MOD LOFD-0 TTI Meaning: Indicates the maximum transmission times
hAlgo lingHarq CELLU 01048 / Bundlin of hybrid automatic repeat requests (HARQs) based
MaxTx LSCHA TDLOF g on transmission time interval (TTI) in the uplink. For
Num LGO D-00104 details, see 3GPP TS 36.331.
LST 8 GUI Value Range: n4(4), n8(8), n12(12), n16(16),
CELLU n20(20), n24(24), n28(28)
LSCHA Unit: None
LGO
Actual Value Range: n4, n8, n12, n16, n20, n24, n28
Default Value: n16(16)

eRAN

nd
CellUlsc UlDelay MOD LOFD-0 Dynami Meaning: Indicates whether to enable delay-based
hAlgo SchStrat CELLU 0101502 c dynamic scheduling prioritization for VoIP services. If
egy LSCHA / Scheduli this parameter is set to NO_DELAYSCH, delay-based
LGO TDLOF ng dynamic scheduling prioritization for VoIP services is
LST D-00101 disabled. If this parameter is set to
CELLU 502 VOIP_DELAYSCH, delay-based dynamic scheduling
LSCHA prioritization for VoIP services is enabled. Scheduling
LGO priorities are dynamically adjusted based on VoIP
packet delays during uplink dynamic scheduling,
thereby increasing the mean opinion score (MOS) and
system capacity for VoIP services when the cell is
heavily loaded with VoIP services.
GUI Value Range: NO_DELAYSCH(No Delay
Scheduling), VOIP_DELAYSCH(VoIP Service Delay
Scheduling)
Unit: None
Actual Value Range: NO_DELAYSCH,
VOIP_DELAYSCH
Default Value: NO_DELAYSCH(No Delay
Scheduling)

eRAN

nd
CellUlsc UlEnhen MOD LOFD-0 Voice Meaning:

hAlgo cedVoip CELLU 81229 Characte Indicates whether to enable uplink pre-scheduling,
SchSw LSCHA ristic include UlVoipPreAllocationSwtich(Bit0),
LGO Awarene UlVoipDelaySchSwitch(Bit1),
LST ss UlVoIPLoadBasedSchSwitch(Bit2),
CELLU Scheduli UlVoipSchOptSwitch(Bit3), and
LSCHA ng UlVoLTEDataSizeEstSwitch(Bit4).
LGO
UlVoipPreAllocationSwtich: This switch controls
whether to schedule VoIP UEs during talk spurts when
the number of online UEs exceeds 50 in a cell. If this
switch is off, voice preallocation is not performed. If
this switch is on, voice preallocation is performed.
This switch applies only to LTE FDD networks.
UlVoipDelaySchSwitch: This switch controls whether
to schedule VoIP UEs based on delays when there are
a large number of VoIP UEs and these UEs are evenly
distributed. If this switch is turned off, delay-based
scheduling is not performed. If this switch is turned
on, the scheduling priorities are calculated based on
delays. This switch applies only to LTE TDD
networks.
UlVoIPLoadBasedSchSwitch: Indicates whether to
enable adaptive selection of VoIP scheduling mode
based on the cell load. There are two scheduling
modes: dynamic scheduling and semi-persistent
scheduling. If this switch is off, adaptive selection of
dynamic and semi-persistent scheduling cannot be
performed for UEs running voice services based on
the cell load. If this switch is off, dynamic and semi-
persistent scheduling can be adaptively selected for
UEs running voice services based on the cell load.
This switch applies only to LTE TDD cells.
UlVoipSchOptSwitch: Indicates whether to enable
scheduling optimization for VoIP services in the
uplink. If this option is deselected, this function is
disabled. If this option is selected, an uplink dynamic
scheduling is triggered for VoIP UEs adopting uplink
dynamic scheduling when the scheduling interval is
greater than the uplink scheduling interval threshold
for VoIP UEs. This ensures timely uplink scheduling
on voice services even when SR missing detection
occurs, thereby avoiding packet loss caused by the
expiration of the PDCP packet discarding timer.
UlVoLTEDataSizeEstSwitch: Indicates whether to
enable the estimation of traffic volume dynamically

eRAN

nd
scheduled for VoLTE services in the uplink.If this

option is deselected, this function is disabled. If this
option is selected, the eNodeB estimates the uplink
traffic volume that is dynamically scheduled for
VoLTE services, which shortens the VoLTE packet
delay, reduces the packet loss rate, improves the voice
service quality.
GUI Value Range: UlVoipPreAllocationSw-
tich(UlVoipPreAllocationSwtich), UlVoipDelaySchS-
witch(UlVoipDelaySchSwitch),
UlVoIPLoadBasedSchS-
witch(UlVoIPLoadBasedSchSwitch),
UlVoipSchOptSwitch(UlVoipSchOptSwitch),
UlVoLTEDataSizeEstSwitch(UlVoLTEDataSizeEstS-
witch)
Unit: None
Actual Value Range: UlVoipPreAllocationSwtich,
UlVoipDelaySchSwitch, UlVoIPLoadBasedSchS-
witch, UlVoipSchOptSwitch, UlVoLTEDataSizeEstS-
witch
Default Value: UlVoipPreAllocationSwtich:Off,
UlVoipDelaySchSwitch:Off, UlVoIPLoadBasedSchS-
witch:Off, UlVoipSchOptSwitch:Off,
UlVoLTEDataSizeEstSwitch:Off
CellUlsc SinrAdj MOD LBFD-0 Voice- Meaning: Indicates the target IBLER in the SINR
hAlgo TargetIb CELLU 81105 Specific calibration algorithm used for dynamic scheduling of
lerforVo LSCHA AMC voice users in non-TTI-bundling mode. A larger value
LTE LGO of this parameter results in a larger SINR adjustment
LST and a higher MCS to be selected.
CELLU GUI Value Range: 1~99
LSCHA Unit: None
LGO
Actual Value Range: 0.01~0.99,0.01
Default Value: 10
ENodeB EutranV MOD None None Meaning: Indicates whether the VoIP services are
AlgoSwi oipSupp ENODE enabled in the E-UTRAN cell. This parameter is used
tch ortSwitc BALGO for determining whether the establishment, handover
h SWITC in, admission, and reestablishment of VoIP services is
H allowed.
LST GUI Value Range: OFF(Off), ON(On)
ENODE Unit: None
BALGO
SWITC Actual Value Range: OFF, ON
H Default Value: ON(On)

eRAN

nd
GlobalP Protocol MOD None None Meaning: Indicates whether the eNodeB supports
rocSwitc Support GLOBA some protocol-defined procedures.
h Switch LPROC SupportS1UeCapMatchMsg(SupportS1UeCapMatch
SWITC Msg): If this option is selected, the eNodeB can
H process and respond to the UE RADIO CAPABILITY
LST MATCH REQUEST message over the S1 interface.
GLOBA For details about the message, see 3GPP TS 36.413. If
LPROC the option is deselected, the eNodeB cannot process
SWITC the UE RADIO CAPABILITY MATCH REQUEST
H message and responds with an error indication
message.
GUI Value Range:
SupportS1UeCapMatchMsg(SupportS1UeCapMatch
Msg)
Unit: None
Actual Value Range: SupportS1UeCapMatchMsg
Default Value: SupportS1UeCapMatchMsg:Off

eRAN

nd
ENodeB HoAlgo MOD LBFD-0 Coverag Meaning: Indicates whether to enable handover
AlgoSwi Switch ENODE 0201801 e Based algorithms. The switches are described as follows:
tch BALGO / Intra- IntraFreqCoverHoSwitch: If this switch is on,
SWITC TDLBF frequenc coverage-based intra-frequency handovers are enabled
H D-00201 y to ensure service continuity. If this switch is off,
LST 801 Handov coverage-based intra-frequency handovers are
ENODE LBFD-0 er disabled. InterFreqCoverHoSwitch: If this switch is
BALGO 0201802 Distance on, coverage-based inter-frequency handovers are
SWITC / Based enabled to ensure service continuity. If this switch is
H TDLBF Inter- off, coverage-based inter-frequency handovers are
D-00201 frequenc disabled. UtranCsfbSwitch: If this switch is on, CSFB
802 y to UTRAN is enabled and UEs can fall back to
Handov UTRAN. If this switch is off, CSFB to UTRAN is
LBFD-0 disabled. GeranCsfbSwitch: If this switch is on, CSFB
er
0201804 to GERAN is enabled and UEs can fall back to
/ Service
GERAN. If this switch is off, CSFB to GERAN is
TDLBF Based
disabled. Cdma1xRttCsfbSwitch: If this switch is on,
D-00201 Inter-
CSFB to CDMA2000 1xRTT is enabled and UEs can
804 frequenc
fall back to CDMA2000 1xRTT. If this switch is off,
y
LBFD-0 CSFB to CDMA2000 1xRTT is disabled.
Handov
0201805 UtranServiceHoSwitch: If this switch is on, service-
er
/ based handovers to UTRAN are enabled and UEs
TDLBF CS running a specific type of services can be handed over
D-00201 Fallback to UTRAN. If this switch is off, service-based
805 to handovers to UTRAN are disabled.
UTRAN GeranServiceHoSwitch: If this switch is on, service-
LOFD-0
CS based handovers to GERAN are enabled and UEs
01033 /
Fallback running a specific type of services can be handed over
TDLOF
to to GERAN. If this switch is off, service-based
D-00103
GERAN handovers to GERAN are disabled.
3
CS CdmaHrpdServiceHoSwitch: If this switch is on,
LOFD-0 Fallback service-based handovers to CDMA2000 HRPD cells
01034 / to are enabled and UEs running a specific type of
TDLOF CDMA2 services can be handed over to CDMA2000 HRPD
D-00103 000 cells. If this switch is off, service-based handovers to
4 1xRTT CDMA2000 HRPD cells are disabled.This parameter
LOFD-0 is unavailable in this version.
Flash
01035 / Cdma1xRttServiceHoSwitch: If this switch is on,
CS
TDLOF service-based handovers to CDMA2000 1xRTT are
Fallback
D-00103 enabled and UEs running a specific type of services
to
5 can be handed over to CDMA2000 1xRTT. If this
UTRAN
switch is off, service-based handovers to CDMA2000
LOFD-0 Flash 1xRTT are disabled.This parameter is unavailable in
01052 / CS this version. UlQualityInterRATHoSwitch: If this
TDLOF Fallback switch is on, UL-quality-based inter-RAT handovers
D-00105 to are enabled and UEs can be handed over to inter-RAT
2 GERAN cells to ensure service continuity when the UL signal
LOFD-0 CS quality is poor. If this switch is off, UL-quality-based
01053 / Fallback

eRAN

nd
TDLOF Steering inter-RAT handovers are disabled.

D-00105 to InterPlmnHoSwitch: If this switch is on, inter-PLMN
3 UTRAN handovers are enabled and UEs can be handed over to
LOFD-0 CS cells in other PLMNs. If this switch is off, inter-
01088 / Fallback PLMN handovers are disabled. UtranFlashCsfbS-
TDLOF Steering witch: This switch takes effect only when
D-00108 to UtranCsfbSwitch is on. If UtranFlashCsfbSwitch is
8 GERAN on, flash CSFB to UTRAN is enabled and the eNodeB
sends system information of candidate target UTRAN
LOFD-0 Enhance
cells to UEs during redirections. If UtranFlashCsfbS-
01089 / d CS
witch is off, flash CSFB to UTRAN is disabled.
TDLOF Fallback
GeranFlashCsfbSwitch: This switch takes effect only
D-00108 to
when GeranCsfbSwitch is on. If GeranFlashCsfbS-
9 CDMA2
witch is on, flash CSFB to GERAN is enabled and the
000
LOFD-0 eNodeB sends system information of candidate target
1xRTT
01090 / GERAN cells to UEs during redirections. If
TDLOF PS Inter- GeranFlashCsfbSwitch is off, flash CSFB to GERAN
D-00109 RAT is disabled. ServiceBasedInterFreqHoSwitch: If this
0 Mobility switch is on, service-based inter-frequency handovers
between are enabled and UEs running a specific type of
LOFD-0
E- services can be handed over to inter-frequency cells. If
01019 /
UTRAN this switch is off, service-based inter-frequency
TDLOF
and handovers are disabled. UlQualityInterFreqHoSwitch:
D-00101
UTRAN If this switch is on, UL-quality-based inter-frequency
9
PS Inter- handovers are enabled and UEs can be handed over to
LOFD-0 inter-frequency cells to ensure service continuity when
RAT
01020 / the UL signal quality is poor. If this switch is off, UL-
Mobility
TDLOF quality-based inter-frequency handovers are disabled.
between
D-00102 CsfbAdaptiveBlindHoSwitch: This switch takes effect
E-
0 only when BlindHoSwitch is on. If
UTRAN
LOFD-0 and CsfbAdaptiveBlindHoSwitch is on, adaptive blind
01043 / GERAN handovers for CSFB are enabled and appropriate
TDLOF handover mechanisms are selected for UEs based on
Service
D-00104 their locations. If CsfbAdaptiveBlindHoSwitch is off,
based
3 adaptive blind handovers for CSFB are disabled.
inter-
LOFD-0 RAT UtranCsfbSteeringSwitch: If this switch is on, CSFB
01046 / handove steering to UTRAN is enabled and CSFB policies for
TDLOF r to UEs in idle mode can be configured. If this switch is
D-00104 UTRAN off, CSFB steering to UTRAN is disabled.
6 GeranCsfbSteeringSwitch: If this switch is on, CSFB
Service steering to GERAN is enabled and CSFB policies for
LOFD-0 based UEs in idle mode can be configured. If this switch is
01072 / inter- off, CSFB steering to GERAN is disabled.
TDLOF RAT CSFBLoadInfoSwitch: If this switch is on, load-based
D-00107 handove CSFB is enabled and a target cell for CSFB is selected
2 r to based on loads of candidate target cells. If this switch
LOFD-0 GERAN is off, load-based CSFB is disabled.
01073 / Distance Cdma1XrttEcsfbSwitch: If this switch is on, eCSFB to
TDLOF based

eRAN

nd
D-00107 inter- CDMA2000 1xRTT is enabled and UEs can fall back
3 RAT to CDMA2000 1xRTT through handovers. If this
TDLBF handove switch is off, eCSFB to CDMA2000 1xRTT is
D-00201 r to disabled. EmcBlindHoA1Switch: If this switch is on,
8 UTRAN blind handover event A1 measurements are enabled. If
Distance a blind handover event measurement conflicts with a
TDLOF handover procedure, an emergency blind handover
D-00102 based
inter- can be triggered after the handover procedure is
2 complete. If this switch is off, blind handover event
RAT
TDLOF A1 measurements are disabled. If a blind handover
handove
D-07022 event measurement conflicts with a handover
r to
8 procedure, an emergency blind handover cannot be
GERAN
LOFD-0 triggered. EmcInterFreqBlindHoSwitch: If this switch
Mobility is on, the eNodeB preferentially performs an inter-
81283 /
Manage frequency blind handover when an emergency blind
TDLOF
ment handover is triggered. If this switch is off, the eNodeB
D-08120
3 Coverag only performs an inter-RAT blind handover when an
e Based emergency blind handover is triggered. EPlmnSwitch:
LOFD-0 Indicates whether handovers to neighboring cells
70202 / Inter-
frequenc under the equivalent PLMNs (EPLMNs) are allowed.
TDLOF When inter-PLMN handovers are allowed, handovers
D-07020 y
Handov to neighboring cells under the EPLMNs are allowed if
2 this switch is on, and not allowed if this switch is off.
er
TDLOF The EPLMNs are delivered by the MME to the UE.
D-08122 SRVCC ServiceReqInterFreqHoSwitch: If this switch is on,
3 to service request-based inter-frequency handovers are
UTRAN enabled and UEs using a specific type of services can
Service- be handed over to inter-frequency cells. If this switch
Request is off, service request-based inter-frequency handovers
Based are disabled. This option applies only to LTE TDD
Inter- networks. VoipHoControlSwitch: Indicates whether
frequenc the eNodeB filters out target cells that do not support
y VoIP services when processing intra-RAT handovers
Handov for VoIP services. The eNodeB filters out such target
er cells in the preceding scenario only when this switch
Ultra- is on. UtranUltraFlashCsfbSwitch: In this switch is on,
Flash ultra-flash CSFB to UTRAN is enabled and UEs can
CSFB to fall back to UTRAN based on the ultra-flash CSFB
GERAN procedure. If this switch is off, ultra-flash CSFB to
UTRAN is disabled. GeranUltraFlashCsfbSwitch: In
Ultra- this switch is on, ultra-flash CSFB to GERAN is
Flash enabled and UEs can fall back to GERAN based on
CSFB to the ultra-flash CSFB procedure. If this switch is off,
UTRAN ultra-flash CSFB to GERAN is disabled.
Ultra- GUI Value Range: IntraFreqCoverHoS-
Flash witch(IntraFreqCoverHoSwitch), InterFreqCoverHoS-
CSFB to witch(InterFreqCoverHoSwitch),
UTRAN UtranCsfbSwitch(UtranCsfbSwitch),

eRAN

nd
GeranCsfbSwitch(GeranCsfbSwitch),
Cdma1xRttCsfbSwitch(Cdma20001xRttCsfbSwitch),
UtranServiceHoSwitch(UtranServiceHoSwitch),
GeranServiceHoSwitch(GeranServiceHoSwitch),
CdmaHrpdServiceHoS-
witch(Cdma2000HrpdServiceHoSwitch),
Cdma1xRttServiceHoSwitch(Cdma20001xRttService
HoSwitch), UlQualityInterRATHoS-
witch(UlQualityInterRATHoSwitch),
InterPlmnHoSwitch(InterPlmnHoSwitch),
UtranFlashCsfbSwitch(UtranFlashCsfbSwitch),
GeranFlashCsfbSwitch(GeranFlashCsfbSwitch),
ServiceBasedInterFreqHoSwitch(ServiceBasedInter-
FreqHoSwitch), UlQualityInterFreqHoS-
witch(UlQualityInterFreqHoSwitch),
CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlind-
HoSwitch), UtranCsfbSteeringS-
witch(UtranCsfbSteeringSwitch),
GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch),
CSFBLoadInfoSwitch(CSFBLoadInfoSwitch),
Cdma1XrttEcsfbSwitch(Cdma1XrttEcsfbSwitch),
EmcBlindHoA1Switch(EmcBlindHoA1Switch),
EmcInterFreqBlindHoSwitch(EmcInterFreqBlind-
HoSwitch), EPlmnSwitch(EPlmnSwitch),
ServiceReqInterFreqHoSwitch(ServiceReqInterFreq-
HoSwitch),
VoipHoControlSwitch(VoipHoControlSwitch),
UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbS-
witch), GeranUltraFlashCsfbS-
witch(GeranUltraFlashCsfbSwitch)
Unit: None
Actual Value Range: IntraFreqCoverHoSwitch,
InterFreqCoverHoSwitch, UtranCsfbSwitch,
GeranCsfbSwitch, Cdma1xRttCsfbSwitch,
UtranServiceHoSwitch, GeranServiceHoSwitch,
CdmaHrpdServiceHoSwitch,
Cdma1xRttServiceHoSwitch, UlQualityInterRA-
THoSwitch, InterPlmnHoSwitch, UtranFlashCsfbS-
witch, GeranFlashCsfbSwitch, ServiceBasedInter-
FreqHoSwitch, UlQualityInterFreqHoSwitch,
CsfbAdaptiveBlindHoSwitch, UtranCsfbSteeringS-
witch, GeranCsfbSteeringSwitch,
CSFBLoadInfoSwitch, Cdma1XrttEcsfbSwitch,
EmcBlindHoA1Switch, EmcInterFreqBlindHoSwitch,
EPlmnSwitch, ServiceReqInterFreqHoSwitch,
VoipHoControlSwitch, UtranUltraFlashCsfbSwitch,
GeranUltraFlashCsfbSwitch

eRAN

nd
Default Value: IntraFreqCoverHoSwitch:On,
InterFreqCoverHoSwitch:On, UtranCsfbSwitch:Off,
GeranCsfbSwitch:Off, Cdma1xRttCsfbSwitch:Off,
UtranServiceHoSwitch:Off, GeranServiceHoS-
witch:Off, CdmaHrpdServiceHoSwitch:Off,
Cdma1xRttServiceHoSwitch:Off, UlQualityInterRA-
THoSwitch:Off, InterPlmnHoSwitch:Off,
UtranFlashCsfbSwitch:Off, GeranFlashCsfbS-
witch:Off, ServiceBasedInterFreqHoSwitch:Off,
UlQualityInterFreqHoSwitch:Off,
CsfbAdaptiveBlindHoSwitch:Off,
UtranCsfbSteeringSwitch:Off, GeranCsfbSteeringS-
witch:Off, CSFBLoadInfoSwitch:Off,
Cdma1XrttEcsfbSwitch:Off,
EmcBlindHoA1Switch:Off, EmcInterFreqBlindHoS-
witch:Off, EPlmnSwitch:Off, ServiceReqInterFreq-
HoSwitch:Off, VoipHoControlSwitch:Off,
UtranUltraFlashCsfbSwitch:Off,
GeranUltraFlashCsfbSwitch:Off
ENodeB S1Msg MOD LBFD-0 RRC Meaning: Indicates the timer governing the period that
ConnSta Waiting ENODE 02007 / Connect the eNodeB waits for a response message from the
teTimer TimerQ BCONN TDLBF ion MME when the UE are running services with the QCI
ci1 STATET D-00200 Manage of 1. If the timer expires, the eNodeB initiates a UE
IMER 7 ment context release over the S1 interface.
ENODE Unit: s
BCONN
STATET Actual Value Range: 1~200
IMER Default Value: 20
ENodeB X2Mess MOD LOFD-0 RRC Meaning: Indicates the timer governing the period the
ConnSta ageWaiti ENODE 02007 / Connect local eNodeB waits for a response message from the
teTimer ngTimer BCONN TDLOF ion peer eNodeB when the UE is running services with
Qci1 STATET D-00200 Manage the QCI of 1. If the timer expires, the eNodeB
IMER 7 ment processes the same as the timer specified by the
LST X2MessageWaitingTimer parameter expires.
ENODE GUI Value Range: 1~200
BCONN Unit: s
STATET
IMER Actual Value Range: 1~200
Default Value: 20

eRAN

nd
ENodeB UuMess MOD LBFD-0 RRC Meaning: Indicates the timer governing the period the
ConnSta ageWaiti ENODE 02007 / Connect eNodeB waits for a response message from a UE
teTimer ngTimer BCONN TDLBF ion when the UE is running services with the QCI of 1. If
Qci1 STATET D-00200 Manage the timer expires, the eNodeB initiates a UE context
IMER 7 ment release over the S1 interface.
ENODE Unit: s
BCONN
STATET Actual Value Range: 1~200
IMER Default Value: 35
RrcCon UeInacti MOD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity
nStateTi veTimer RRCCO 02007 / Connect timer for UEs that are running services of QCI 1. If
mer Qci1 NNSTA TDLBF ion the eNodeB detects that a UE has neither received nor
TETIM D-00200 Manage sent data for a duration exceeding the value of this
ER 7 ment parameter, the eNodeB releases the RRC connection
LST for the UE. If this parameter is set to 0, the UE
RRCCO inactivity timer is not used. This timer takes effect
NNSTA during the setup of bearers with a QCI of 1. During a
TETIM handover or RRC connection reestablishment to a new
ER cell, the eNodeB determines whether the timer takes
effect based on whether the UE is running services
with a QCI of 1. If yes, the timer takes effect;
otherwise, the timer does not take effect.
Unit: s
Default Value: 20
CellStan TrafficR MOD LBFD-0 Radio Meaning: Indicates the waiting duration for the
dardQci elDelay CELLS 02008 / Bearer eNodeB to release services with a specific QCI after
TANDA TDLBF Manage the eNodeB detects that the radio link is abnormal.
RDQCI D-00200 ment When the eNodeB detects that the radio link is
LST 8 abnormal, the eNodeB waits for the UE to initiate an
CELLS RRC connection reestablishment procedure to restore
TANDA services. If the waiting duration times out, the eNodeB
RDQCI releases the services.
Unit: ms
Default Value: 30000

eRAN

nd
RlcPdcp RlcMod ADD LBFD-0 Radio Meaning: Indicates the RLC transmission mode. Only
ParaGro e RLCPD 02008 / Bearer the AM and UM modes are available.
up CPPAR TDLBF Manage GUI Value Range: RlcMode_AM(Acknowledge
AGROU D-00200 ment Mode), RlcMode_UM(Un-acknowledge Mode)
P 8
Unit: None
MOD
RLCPD Actual Value Range: RlcMode_AM, RlcMode_UM
CPPAR Default Value: RlcMode_AM(Acknowledge Mode)
AGROU
P
LST
RLCPD
CPPAR
AGROU
P

eRAN

nd
CellAlg RacAlgo MOD LBFD-0 Admissi Meaning:

oSwitch Switch CELLA 02023 / on Indicates whether to enable the admission and load
LGOSW TDLBF Control control algorithms.
ITCH D-00202 Congesti
LST 3 on DlSwitch: Indicates whether to enable the algorithm
CELLA LBFD-0 Control of downlink admission control based on the
LGOSW 02024 / satisfaction rate. If this switch is on, the algorithm is
Radio/ enabled. If this switch is off, the algorithm is disabled.
ITCH TDLBF transport
D-00202 During the calculation of the QoS satisfaction rate of
resource services with different QCIs, the satisfaction
4 pre- estimation method used dedicatedly for VoIP services
LOFD-0 emption is implemented on services with the QCI of 1. If a
0102901 service with the QCI of 1 is not a VoIP service, the
satisfaction rate calculated using this method is lower
than the actual value, which affects the admission of
GBR services. Therefore, if not all the services with
the QCI of 1 are VoIP services, it is recommended that
this switch be off.
UlSwitch: Indicates whether to enable the algorithm
of uplink admission control based on the satisfaction
rate. If this switch is on, the algorithm is enabled. If
this switch is off, the algorithm is disabled. During the
calculation of the QoS satisfaction rate of services
with different QCIs, the satisfaction estimation
method used dedicated for VoIP services is
implemented on services with the QCI of 1. If a
service with the QCI of 1 is not a VoIP service, the
than the actual value, which affects the admission of
GBR services. Therefore, if not all the services with
the QCI of 1 are VoIP services, it is recommended that
this switch be off.
DlPredictSwitch: Indicates whether to enable the
algorithm of downlink admission control based on
prediction. If this switch is on, the algorithm is
enabled. If this switch is off, the algorithm is disabled.
UlPredictSwitch: Indicates whether to enable the
algorithm of uplink admission control based on
prediction. If this switch is on, the algorithm is
enabled. If this switch is off, the algorithm is disabled.
GbrUsageSwitch: Indicates whether to enable the
check on the number of PRBs used by GBR services.
If this switch is on, the number of PRBs used by
existing GBR services is checked before a new GBR
service can be admitted. If this switch is off, the
number of PRBs used by existing GBR services is not

eRAN

nd
checked during admission evaluation of new GBR

services
DlLdcSwitch: Indicates whether to implement load
control in the downlink of a cell. If this switch is on,
the system checks for congestion in the downlink of
the cell. If the downlink is congested, load control is
performed. If this switch is off, the system does not
check for congestion in the downlink of the cell and
the congestion cannot be relieved. During the
calculation of the QoS satisfaction rate of services
with different QCIs, the satisfaction estimation
method used dedicated for VoIP services is
implemented on services with the QCI of 1. If a
service with the QCI of 1 is not a VoIP service, the
than the actual value, which affects the cell load
control. Therefore, if not all the services with the QCI
of 1 are VoIP services, it is recommended that this
switch be off.
UlLdcSwitch: Indicates whether to implement load
control in the uplink of a cell. If this switch is on, the
system checks for congestion in the uplink of the cell.
If the uplink is congested, load control is performed. If
this switch is off, the system does not check for
congestion in the uplink of the cell and the congestion
cannot be relieved. During the calculation of the QoS
satisfaction rate of services with different QCIs, the
satisfaction estimation method used dedicated for
VoIP services is implemented on services with the
QCI of 1. If a service with the QCI of 1 is not a VoIP
service, the satisfaction rate calculated using this
method is lower than the actual value, which affects
the cell load control. Therefore, if not all the services
with the QCI of 1 are VoIP services, it is
recommended that this switch be off.
RelDrbSwitch: Indicates whether low-priority services
can be released in the case of congestion. If this
switch is on, low-priority services can be released. If
this switch is off, low-priority services cannot be
released.
PreemptionSwitch: Indicates whether to enable the
preemption control algorithm. If this switch is on,
preemption can be used when the admission of high-
priority services fails. If this switch is off, only
emergency calls can be admitted to the system when
resources are insufficient.

eRAN

nd
GUI Value Range: DlSwitch(dlCacSwitch),

UlSwitch(ulCacSwitch),
DlPredictSwitch(dlCacPredictSwitch),
UlPredictSwitch(ulCacPredictSwitch),
GbrUsageSwitch(GbrUsedPRbCheckSwitch),
DlLdcSwitch(dlLdcSwitch),
UlLdcSwitch(ulLdcSwitch),
RelDrbSwitch(LdcDrbRelSwitch),
PreemptionSwitch(PreemptionSwitch)
Unit: None
Actual Value Range: DlSwitch, UlSwitch,
DlPredictSwitch, UlPredictSwitch, GbrUsageSwitch,
DlLdcSwitch, UlLdcSwitch, RelDrbSwitch,
PreemptionSwitch
Default Value: DlSwitch:Off, UlSwitch:Off,
DlPredictSwitch:Off, UlPredictSwitch:Off,
GbrUsageSwitch:Off, DlLdcSwitch:Off,
UlLdcSwitch:Off, RelDrbSwitch:Off,
PreemptionSwitch:Off
CellRac Qci1Co MOD LBFD-0 Congesti Meaning:

Thd ngThd CELLR 02024 / on Indicates the congestion threshold for services with
ACTHD TDLBF Control QCI of 1. This threshold applies to both UL and DL.
LST D-00202
CELLR 4 If the satisfaction rate of services with QCI of 1 in the
ACTHD cell becomes lower than this threshold, the services
with QCI of 1 enter the congested state.
If the satisfaction rate of services with QCI of 1 in the
cell becomes higher than the sum of this threshold and
the congestion relief offset, the services with QCI of 1
leave the congested state.
Unit: %
Default Value: 65

eRAN

nd
CellUlsc UlschStr MOD LBFD-0 Basic Meaning: Indicates the UL scheduling policy, which
hAlgo ategy CELLU 02025 / Scheduli determines the scheduling priority order in which UEs
LSCHA TDLBF ng are arranged in UL. There are four UL scheduling
LGO D-00202 Dynami strategies: MAX C/I, proportional fair (PF), round
LST 5 c Robin (RR), and enhanced proportional fair (EPF).
CELLU TDLOF Scheduli The MAX C/I policy schedules UEs in descending
LSCHA D-00101 ng order of average signal to interference plus noise ratio
LGO 5 (SINR). The PF policy schedules UEs in ascending
Enhance order of ratio of the data rate to the SINR. The RR
TDLOF d policy schedules each UE in sequence, and therefore
D-00101 Scheduli each UE has an equal opportunity to be scheduled.
502 ng The EPF policy schedules UEs in ascending order of
priority. In EPF, the priority of an UE is calculated
based on the following factors: the data rate, average
SINR, QoS-satisfying data rate for each service, and
service differentiation requirements of the UE. The
MAX C/I, PF, and RR policies are basic UL
scheduling policies and supported by the eNodeB by
default, whereas the EPF policy is intended for
commercial use.
GUI Value Range: ULSCH_STRATEGY_EPF(EPF),
ULSCH_STRATEGY_MAX_CI(MAX_CI),
ULSCH_STRATEGY_PF(PF),
ULSCH_STRATEGY_RR(RR)
Unit: None
Actual Value Range: ULSCH_STRATEGY_EPF,
ULSCH_STRATEGY_MAX_CI,
ULSCH_STRATEGY_PF, ULSCH_STRATEGY_RR
Default Value: ULSCH_STRATEGY_EPF(EPF)

eRAN

nd
CellAlg UlSchS MOD LOFD-0 VoIP Meaning:

oSwitch witch CELLA 01016 / Semi- This parameter indicates the switches related to uplink
LGOSW TDLOF persisten (UL) scheduling in the cell. The switches are used to
ITCH D-00101 t enable or disable specific UL scheduling functions.
LST 6 Scheduli
CELLA LOFD-0 ng SpsSchSwitch: Indicates the switch used to enable or
LGOSW 01048 / TTI disable semi-persistent scheduling during talk spurts
ITCH TDLOF Bundlin of VoIP services. If this switch is on, semi-persistent
D-00104 g scheduling is applied during talk spurts of VoIP
8 services. If this switch is off, dynamic scheduling is
Dynami applied during talk spurts of VoIP services.
LOFD-0 c
0101502 Scheduli SinrAdjustSwitch: Indicates whether to adjust the
/ ng measured signal to interference plus noise ratio
TDLOF Basic (SINR) based on ACK/NACK in UL hybrid automatic
D-00101 Scheduli repeat request (HARQ) processes.
502 ngTDL PreAllocationSwitch: Indicates whether to enable
TDLBF OFD-07 preallocation in the uplink. When this switch is on: (1)
D-00202 0224:Sc If SmartPreAllocationSwitch is off and a UE is in the
5 heduling discontinuous reception (DRX) state, preallocation is
LBFD-0 Based disabled for the UE in the uplink; (2) If
70102 / on Max SmartPreAllocationSwitch is off and the UE is not in
TDLBF Bit Rate the DRX state, preallocation is enabled for the UE in
D-07010 MBR>G the uplink; (3) If SmartPreAllocationSwitch is on and
2 BR the SmartPreAllocationDuration parameter value is
LOFD-0 Configu greater than 0, smart preallocation is enabled for the
01002 ration UE in the uplink; (4) If SmartPreAllocationSwitch is
UL 2x2 on and the SmartPreAllocationDuration parameter
LOFD-0 value is 0, preallocation is disabled for the UE in the
01058 MU-
MIMO uplink. If this switch is off, preallocation is disabled
LBFD-0 for the UE in the uplink. If bearer-level preallocation
01006 UL 2x4 or bearer-level smart preallocation is enabled for a UE
MU- with a QCI class, cell-level preallocation and cell-
MIMO level smart preallocation do not apply to UEs with the
AMC QCI.
UlVmimoSwitch: Indicates whether to enable multi-
user MIMO (MU-MIMO) in the UL. If this switch is
on, the eNodeB performs MU-MIMO pairing among
UEs based on related principles. UEs forming a pair
transmit data using the same time-frequency
resources, which improves system throughput and
spectral efficiency.
TtiBundlingSwitch: Indicates whether to enable
transmission time interval (TTI) bundling. If TTI
bundling is enabled, more transmission opportunities
are available to UEs within the delay budget for VoIP

eRAN

nd
services on the Uu interface, thereby improving uplink

coverage.
ImIcSwitch: Indicates whether to enable the
intermodulation interference (IM) cancellation for
UEs. When data is transmitted in both uplink and
downlink, two IM components are generated
symmetrically beside the Direct Current (DC)
subcarrier on the downlink receive channel due to
interference from uplink radio signals. If this switch is
on, IM component elimination is performed on UEs.
If this switch is off, IM component elimination is not
performed on UEs. This switch applies only to FDD
cells working in frequency band 20.
SmartPreAllocationSwitch: Indicates whether to
enable uplink smart preallocation when preallocation
is enabled (by turning on PreAllocationSwitch). If
both PreAllocationSwitch and SmartPreAllocationS-
witch are on and SmartPreAllocationDuration is set to
a value greater than 0, uplink smart preallocation is
enabled; otherwise, uplink smart preallocation is
disabled.
PuschDtxSwitch: Indicates whether the eNodeB uses
the physical uplink shared channel (PUSCH)
discontinuous transmission (DTX) detection result
during UL scheduling. In an LTE FDD cell, if this
switch is on, based on the PUSCH DTX detection
result, the eNodeB determines whether to perform
adaptive retransmission during UL scheduling and
also adjusts the control channel element (CCE)
aggregation level of the physical downlink control
channel (PDCCH) carrying downlink control
information (DCI) format 0. If an FDD cell is
established on an LBBPc, this switch takes effect only
when the cell uses less than four RX antennas and
normal cyclic prefix (CP) in the uplink and the
SrsCfgInd parameter in the SRSCfg MO is set to
BOOLEAN_TRUE. Note that the LBBPc does not
support PUSCH DTX detection for UEs with MU-
MIMO applied. In an LTE TDD cell, this switch takes
effect only when the cell is configured with subframe
configuration 2 or 5. After this switch takes effect, the
eNodeB adjusts the CCE aggregation level based on
the PUSCH DTX detection results. Note that LTE
TDD cells established on LBBPc boards do not
support PUSCH DTX detection.
UlIblerAdjustSwitch: Indicates whether to enable the
uplink initial block error rate (IBLER) adjustment

eRAN

nd
algorithm. If this switch is on, IBLER convergence

target is adjusted to increase the cell edge throughput.
When this switch is on, the recommended
configuration of parameter DopMeasLevel in MO
CellUlschAlgo is CLASS_1.
UlEnhancedFssSwitch: Indicates whether to enable
uplink load-based enhanced frequency selection. This
switch applies only to FDD cells.
UlIicsAlgoSwitch: Indicates whether to enable the UL
IICS algorithm. If this switch is on, interference can
be reduced based on accurate detection of user
attributes and resource scheduling coordination,
thereby increasing the cell edge throughput. This
switch applies only to LTE TDD networks.
UlEnhancedSrSchSwitch: Indicates whether uplink re-
scheduling is performed only when the On Duration
timer for the DRX long cycle starts. Uplink re-
scheduling is required if the number of HARQ
retransmissions for a scheduling request (SR) reaches
the maximum value but the scheduling still fails. If
this switch is on, uplink re-scheduling is performed
only when the On Duration timer for the DRX long
cycle starts. If this switch is off, uplink re-scheduling
is performed immediately when the number of HARQ
retransmissions for SR reaches the maximum value
but the scheduling still fails. It is recommended that
the switch be turned on in live networks.
SchedulerCtrlPowerSwitch: Indicates whether the
uplink scheduler performs scheduling without
considering power control restrictions. If this switch is
on, the uplink scheduler performs scheduling without
considering power control restrictions, which ensures
full utilization of the transmit power for all UEs. If
this switch is off, the uplink scheduler considers
power control restrictions while performing
scheduling, which prevents full utilization of the
transmit power for UEs at far or medium distances
from the cell center.
UlMinGbrSwitch: Indicates whether to enable uplink
minimum guaranteed bit rate (GBR). If this switch is
on, the minimum GBR of non-GBR services is
ensured by increasing the scheduling priority of UEs
whose non-GBR service rates are lower than the
minimum GBR of GBR services.
UlMbrCtrlSwitch: Indicates whether to enable uplink
scheduling based on the maximum bit rate (MBR) and

eRAN

nd
guaranteed bit rate (GBR) on the GBR bearer. If this

switch is on, the eNodeB performs uplink scheduling
on GBR bearers based on the MBR and GBR. If this
switch is off, the eNodeB performs uplink scheduling
on GBR bearers based only on the GBR.
MbrUlSchSwitch: Indicates whether the eNodeB
performs uplink scheduling based on MBR. If this
switch is on, the eNodeB prioritizes UEs based on the
MBRs during uplink scheduling. This parameter
applies only to LTE TDD cells.
UeAmbrUlSchSwitch: Indicates whether the eNodeB
performs uplink scheduling based on the aggregate
maximum bit rate (AMBR) of UEs. If this switch is
on, the eNodeB prioritizes UEs based on the AMBRs
during uplink scheduling. This parameter applies only
to LTE TDD cells.
UlEnhancedDopplerSwitch: Indicates whether to
enable enhanced uplink scheduling based on mobility
speed. If this switch is on, enhanced uplink scheduling
based on mobility speed is enabled. If this switch is
on, the eNodeB determines whether a UE is a low-
mobility UE based on the Doppler measurement in the
physical layer, and then improves uplink frequency
selective scheduling performance for low-mobility
UEs. If this switch is off, enhanced uplink scheduling
based on mobility speed is disabled. This switch takes
effect only when the UlEnhancedDopplerSwitch
parameter is set to CLASS_1. This switch does not
take effect on cells established on an LBBPc.
UlRaUserSchOptSw: Indicates whether the eNodeB
raises the scheduling priority of UEs sending uplink
access signaling, including MSG5 and the RRC
Connection Reconfiguration Complete message. If
this switch is on, the eNodeB raises the scheduling
priority of UEs sending uplink access signaling. If this
switch is off, the eNodeB does not raise the
scheduling priority of UEs sending uplink access
signaling.
UlLast2RetransSchOptSwitch: Indicates whether to
enable optimization on the scheduling policy for the
last two retransmissions. If this switch is on,
optimization on the scheduling policy for the last two
retransmissions is enabled. If the UE transmit power is
not limited, adaptive retransmission is used and the
number of RBs increases in the last two
retransmissions to increase the receive success rate of

eRAN

nd
the last two retransmissions and decrease uplink

RBLER. If this switch is off, optimization on the
scheduling policy for the last two retransmissions is
disabled. This switch does not apply to LTE TDD
cells.
UlInterfFssSwitch: Indicates whether to enable
interference-based uplink frequency-selective
scheduling. This switch applies only to LTE FDD
networks.
UlSmallRBSpectralEffOptSw: Indicates whether to
enable spectral efficiency optimization on uplink
small RBs. If this switch is on, the optimization is
enabled, thereby ensuring that the transmission block
size calculated based on optimized spectral efficiency
is not less than the traffic volume needs to be
scheduled. If this switch is off, the optimization is
disabled.
PuschUsePucchRbSwitch: Indicates whether PUCCH
RBs can be occupied by the PUSCH. In scenarios
with a single user, if this switch is on, PUCCH RBs
can be occupied by the PUSCH. If this switch is off,
PUCCH RBs cannot be occupied by the PUSCH. In
scenarios with multiple users, PUCCH RBs cannot be
occupied by the PUSCH no matter whether this switch
is on or off.
PuschDtxSchOptSwitch: If this switch is on, the
eNodeB determines whether to perform adaptive
retransmission during UL scheduling based on the
PUSCH DTX detection result. This switch takes effect
only when subframe configuration 2 or 5 is used. If a
TDD cell is established on an LBBPc, PUSCH DTX
detection is not supported. This switch applies only to
LTE TDD cells.
PrachRbReuseSwitch:If this switch is on, the PUSCH
and PRACH transmissions can use the same resource.
If this switch is off, the PUSCH and PRACH
transmissions cannot use the same resource. This
switch applies only to LTE TDD cells.
ULFSSAlgoswitch:If this switch is off, uplink
frequency-selective scheduling is disabled. If this
switch is on, uplink frequency-selective scheduling is
enabled. This switch is invalid if the HighSpeedFlag
parameter in the Cell MO is set to
HIGH_SPEED(High speed cell flag) or

eRAN

nd
ULTRA_HIGH_SPEED(Ultra high speed cell flag),

that is, uplink frequency-selective scheduling is
disabled in high speed and ultra high speed mobility
conditions. This switch applies only to LTE TDD
cells.
SrSchDataAdptSw: Indicates whether to enable data
volume adaption in SR scheduling. Data volume
adaption in SR scheduling is enabled only when this
option is selected.
UlFssUserThdStSwitch: UlFssUserThdStSwitch:
Indicates whether to enable the optimization policy on
the UE number threshold for frequency selective
scheduling. The optimization policy is enabled only
when this option is selected.
GUI Value Range: SpsSchSwitch(SpsSchSwitch),
SinrAdjustSwitch(SinrAdjustSwitch),
PreAllocationSwitch(PreAllocationSwitch),
UlVmimoSwitch(UlVmimoSwitch),
TtiBundlingSwitch(TtiBundlingSwitch),
ImIcSwitch(ImIcSwitch), SmartPreAllocationS-
witch(SmartPreAllocationSwitch),
PuschDtxSwitch(PuschDtxSwitch),
UlIblerAdjustSwitch(UlIblerAdjustSwitch),
UlEnhancedFssSwitch(UlEnhancedFssSwitch),
UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch),
SchedulerCtrlPowerSwitch(SchedulerCtrlPowerS-
witch), UlIicsAlgoSwitch(UlIicsAlgoSwitch),
UlMinGbrSwitch(UlMinGbrSwitch),
UlMbrCtrlSwitch(UlMbrCtrlSwitch),
MbrUlSchSwitch(MbrUlSchSwitch),
UeAmbrUlSchSwitch(UeAmbrUlSchSwitch),
UlEnhancedDopplerSwitch(UlEnhancedDopplerS-
witch), UlRaUserSchOptSw(UlRaUserSchOptSw),
UlLast2RetransSchOptSwitch(UlLast2RetransSchOpt
Switch), UlInterfFssSwitch(UlInterfFssSwitch),
UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEf-
ficiencyOptSw), PuschUsePucchRbS-
witch(PuschUsePucchRbSwitch), PuschDtxSchOptS-
witch(PuschDtxSchOptSwitch),
ULFSSAlgoSwitch(ULFSSAlgoSwitch),
PrachRbReuseSwitch(PrachRbReuseSwitch),
SrSchDataAdptSw(SrSchDataAdptSw),
UlFssUserThdStSwitch(UlFssUserThdStSwitch)
Unit: None
Actual Value Range: SpsSchSwitch,
SinrAdjustSwitch, PreAllocationSwitch,
UlVmimoSwitch, TtiBundlingSwitch, ImIcSwitch,

eRAN

nd
SmartPreAllocationSwitch, PuschDtxSwitch,
UlIblerAdjustSwitch, UlEnhancedFssSwitch,
UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch,
UlIicsAlgoSwitch, UlMinGbrSwitch,
UlMbrCtrlSwitch, MbrUlSchSwitch,
UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch,
UlRaUserSchOptSw, UlLast2RetransSchOptSwitch,
UlInterfFssSwitch, UlSmallRBSpectralEffOptSw,
PuschUsePucchRbSwitch, PuschDtxSchOptSwitch,
ULFSSAlgoSwitch, PrachRbReuseSwitch,
SrSchDataAdptSw, UlFssUserThdStSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
ImIcSwitch:Off, SmartPreAllocationSwitch:Off,
PuschDtxSwitch:On, UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On, UlEnhancedSrSchS-
witch:Off, SchedulerCtrlPowerSwitch:Off,
UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off, UlEnhancedDopplerS-
witch:Off, UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:Off,
UlInterfFssSwitch:Off, UlSmallRBSpectralEf-
fOptSw:Off, PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off

eRAN

nd
CellAlg DlSchS MOD LOFD-0 VoIP Meaning:

oSwitch witch CELLA 01016 / Semi- Indicates the switches related to downlink scheduling
LGOSW TDLOF persisten in the cell.
ITCH D-00101 t
LST 6 Scheduli FreqSelSwitch: Indicates whether to enable frequency
CELLA LOFD-0 ng selective scheduling. If this switch is on, data is
LGOSW 0101502 Dynami transmitted on the frequency band in good signal
ITCH / c quality.
TDLOF Scheduli ServiceDiffSwitch: Indicates whether to enable
D-00101 ng service differentiation. If this switch is on, service
502 DL differentiation is applied. If this switch is off, service
LOFD-0 Non- differentiation is not applied.
01109 / GBR
TDLOF Packet SpsSchSwitch: Indicates whether to enable semi-
D-00110 Bundlin persistent scheduling during talk spurts of VoIP
9 g services. If this switch is on, semi-persistent
scheduling is applied during talk spurts of VoIP
LOFD-0 Symbol services. If this switch is off, dynamic scheduling is
01070 / Power applied during talk spurts of VoIP services.
TDLOF Saving
D-00107 Scheduli MBSFNShutDownSwitch: Indicates whether to
0 ng enable Multimedia Broadcast multicast service Single
TDLOF Based Frequency Network (MBSFN) subframe shutdown. If
D-07022 on Max this switch is on, MBSFN subframe shutdown is
4 Bit Rate applied. If this switch is off, MBSFN subframe
shutdown is not applied. This switch is valid only
LBFD-0 Basic when SymbolShutdownSwitch is on. If the MBSFN
02025 / Scheduli shutdown switch is on, the setting of the switch for
TDLBF ng mapping SIBs to SI messages becomes invalid. The
D-00202 Support latter can be specified by the SiMapSwitch parameter
5 of in the CellSiMap MO. If the MBSFN subframe
LBFD-0 aperiodi shutdown switch is off, the setting of the switch for
02031 / c CQI mapping SIBs to SI messages becomes valid. MBSFN
TDLBF reports subframe shutdown applies only to LTE-only base
D-00203 MBR>G stations.
1 BR NonGbrBundlingSwitch: Indicates whether to enable
LBFD-0 Configu downlink non-GBR packet bundling. If this switch is
70102 / ration on, delay of non-GBR services can be controlled in
TDLBF Enhance non-congestion scenarios. If this switch is off, delay of
D-07010 d DL non-GBR services cannot be controlled.
2 Frequen
LBFD-0 cy EnAperiodicCqiRptSwitch: Indicates whether to
60202 Selectiv enable enhanced aperiodic channel quality indicator
e (CQI) reporting. If this switch is on, the eNodeB
triggers aperiodic CQI reporting for a UE based on
downlink services of the UE and the interval at which
the UE sends periodic CQI reports. If this switch is
off, UEs under non-frequency selective scheduling do
not trigger aperiodic CQI reporting based on downlink

eRAN

nd
services and triggers an aperiodic CQI reporting if no

valid periodic CQI reports are sent in eight
consecutive periodic CQI reporting periods.
DlMbrCtrlSwitch: Indicates whether to enable
downlink scheduling based on the maximum bit rate
(MBR) and guaranteed bit rate (GBR) on the GBR
bearer. If this switch is on, the eNodeB performs
downlink scheduling on GBR bearers based on the
MBR and GBR. If this switch is off, the eNodeB
performs downlink scheduling on GBR bearers based
on the GBR only.
MbrDlSchSwitch: Indicates whether the eNodeB
performs downlink scheduling based on MBR. If this
switch is on, the eNodeB determines priorities of UEs
based on the MBR in downlink scheduling. This
parameter applies only to LTE TDD cells.
UeAmbrDlSchSwitch: Indicates whether the eNodeB
performs downlink scheduling based on the aggregate
maximum bit rate (AMBR) of UEs. If this switch is
on, the eNodeB determines priorities of UEs based on
the AMBR of UEs in downlink scheduling. This
EpfEnhancedSwitch: Indicates whether to enable
enhanced proportional fair (EPF) for downlink
scheduling. EPF for downlink scheduling is enabled
only when this switch is on.
AperiodicCqiTrigOptSwitch: Indicates whether to
trigger aperiodic CQI optimization. If this switch is
on, a UE performing initial access triggers aperiodic
CQI reporting based on related triggering conditions
after the DLMAC instance has been established for
200 ms and the eNodeB receives MSG5. Consider that
aperiodic CQI reporting is triggered by invalid CQI
reports in eight consecutive CQI reporting periods. If
cyclic redundancy check (CRC) on aperiodic CQI
reports fails, aperiodic CQI reporting is not repeatedly
triggered when DRX is enabled; or aperiodic CQI
reporting is triggered after eight TTIs when DRX is
disabled. If this switch is off, a UE performing initial
access triggers aperiodic CQI reporting based on
related triggering conditions after the DLMAC
instance has been established for 200 ms. Consider
that aperiodic CQI reporting is triggered by invalid
CQI reports in eight consecutive CQI reporting
periods. If CRC on aperiodic CQI reports fails,

eRAN

nd
aperiodic CQI reporting is triggered after eight TTIs

regardless of the DRX status.
VoipTbsBasedMcsSelSwitch: Indicates whether the
modulation and coding scheme (MCS) index is
selected based on the transport block size (TBS) in
downlink scheduling for VoIP services. If this switch
is on, the MCS index is selected based on the TBS in
downlink scheduling for VoIP services. If this switch
is off, the MCS index is not selected based on the TBS
in downlink scheduling for VoIP services.
UeSigMcsEnhanceSwitch: Indicates whether to
enable or disable the optimized MCS algorithm for
UE signaling. The optimized MCS algorithm for UE
signaling takes effect after this switch is on. This
PagingInterfRandSwitch: Indicates whether to enable
or disable interference randomizing for paging
messages. If this switch is on, interference
randomizing is enabled for paging messages. This
switch is valid only in TDD mode.
DlSingleUsrMcsOptSwitch: Indicates conditions for
lowering the modulation and coding scheme (MCS)
for a single UE. When this switch is on, the MCS can
be lowered for a UE if the UE is the only UE to be
scheduled in a transmission time interval (TTI). When
this switch is off, the MCS can be lowered for a UE if
there are only 10 percent of TTIs having UEs to
schedule in each sparse packet determination period
and the UE is the only UE to be scheduled in each
TTI.
SubframeSchDiffSwitch: Indicates whether subframes
3 and 8 perform scheduling based on increased
number of uplink scheduling UEs when subframe
configuration type 2 is used. If this switch is on,
subframes 3 and 8 perform scheduling based on
increased number of uplink scheduling UEs when
subframe configuration type 2 is used. If this switch is
off, subframes 3 and 8 perform scheduling based on
the policy that other downlink subframes adopt when
subframe configuration type 2 is used. This switch is
dedicated to LTE TDD cells.
TailPackagePriSchSwitch: Indicates the switch that
controls the scheduling of downlink connected tail
packages in the bearer. If this switch is on, the
connected tail package is scheduled preferentially in

eRAN

nd
the next TTI, which reduces the delay and increases

the transmission rate. If this switch is off, the
scheduling strategy of the connected tail package is
the same as other downlink subframes. This switch is
dedicated to LTE TDD cells.
FreqSelJudgeIgnorDopplerSwitch: Indicates whether
Doppler determination conditions are considered
during channel frequency selective scheduling
determination. Doppler determination conditions are
considered only when this option is deselected. This
option applies only to LTE FDD.
SIB1InterfRandSwitch: Indicates whether to enable
SIB1 interference randomizing. If this switch is on,
interference randomizing is enabled for SIB1. This
switch applies only to LTE TDD cells.
GUI Value Range: FreqSelSwitch(FreqSelSwitch),
ServiceDiffSwitch(ServiceDiffSwitch),
SpsSchSwitch(SpsSchSwitch),
MBSFNShutDownSwitch(MBSFNShutDownSwitch),
NonGbrBundlingSwitch(NonGbrBundlingSwitch),
EnAperiodicCqiRptSwitch(EnAperiodicCqiRptS-
witch), DlMbrCtrlSwitch(DlMbrCtrlSwitch),
MbrDlSchSwitch(MbrDlSchSwitch),
UeAmbrDlSchSwitch(UeAmbrDlSchSwitch),
EpfEnhancedSwitch(EpfEnhancedSwitch),
AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptS-
witch), VoipTbsBasedMcsSelS-
witch(VoipTbsBasedMcsSelSwitch),
PagingInterfRandSwitch(PagingInterfRandSwitch),
DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptS-
witch), SubframeSchDiffSwitch(SubframeSchDiffS-
witch), TailPackagePriSchS-
witch(TailPackagePriSchSwitch),
UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch),
FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnor-
DopplerSwitch),
SIB1InterfRandSwitch(SIB1InterfRandSwitch)
Unit: None
Actual Value Range: FreqSelSwitch,
ServiceDiffSwitch, SpsSchSwitch,
MBSFNShutDownSwitch, NonGbrBundlingSwitch,
EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch,
MbrDlSchSwitch, UeAmbrDlSchSwitch,
EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch,
VoipTbsBasedMcsSelSwitch, PagingInterfRand-
Switch, DlSingleUsrMcsOptSwitch,
SubframeSchDiffSwitch, TailPackagePriSchSwitch,

eRAN

nd
UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDop-
plerSwitch, SIB1InterfRandSwitch
Default Value: FreqSelSwitch:Off,
ServiceDiffSwitch:Off, SpsSchSwitch:Off,
MBSFNShutDownSwitch:Off, NonGbrBundlingS-
witch:Off, EnAperiodicCqiRptSwitch:Off,
DlMbrCtrlSwitch:Off, MbrDlSchSwitch:Off,
UeAmbrDlSchSwitch:Off, EpfEnhancedSwitch:Off,
AperiodicCqiTrigOptSwitch:Off, VoipTbsBasedMcs-
SelSwitch:Off, PagingInterfRandSwitch:Off,
DlSingleUsrMcsOptSwitch:Off, SubframeSchDiffS-
witch:Off, TailPackagePriSchSwitch:Off,
UeSigMcsEnhanceSwitch:Off, FreqSelJudgeIgnor-
DopplerSwitch:Off, SIB1InterfRandSwitch:On

eRAN

nd
CellAlg CqiAdj MOD LOFD-0 CQI Meaning:

oSwitch AlgoSwi CELLA 0101501 Adjustm CqiAdjAlgoSwitch: Indicates whether to allow the
tch LGOSW / ent eNodeB to adjust the UE-reported CQI based on the
ITCH TDLOF Dynami initial block error rate (IBLER).
LST D-00101 c
CELLA 501 Scheduli If this switch is On, the CQI adjustment algorithm is
LGOSW LOFD-0 ng enabled. In this case, the eNodeB adjusts the UE-
ITCH 0101502 reported CQI based on the IBLER.
/ If this switch is off, the CQI adjustment algorithm is
TDLOF disabled. In this case, the eNodeB does not adjust the
D-00101 UE-reported CQI based on the IBLER.
502
StepVarySwitch: Indicates whether to enable the
variable-step-based adjustment algorithm.
If this switch is On, the variable-step-based
adjustment algorithm is enabled to accelerate the
convergence of IBLER. In this case, rapid adjustment
at large steps is applied if there is a relatively large
difference between the measured IBLER and target
IBLER; fine-tuning at small steps is applied if the
measured IBLER approaches the target IBLER.
If this switch is off, the adjustment is performed at a
fixed step.
DlVarIBLERtargetSwitch: Indicates whether to enable
downlink target IBLER adaption.
If this switch is On, the downlink target IBLER is
adjusted based on the size of transport blocks (TBs) to
improve the spectral efficiency.
If this switch is off, the target IBLER is determined
based on the setting of DlEnVarIblerTargetSwitch.
TddBundlingCqiAdjOptSwitch: Indicates whether to
use optimized CQI adjustment algorithm in ACK
bundling mode.
If this switch is On, the optimized CQI adjustment
algorithm is used.
If this switch is off, the optimized CQI adjustment
algorithm cannot be used.
TddMultiplexingCqiAdjOptSwitch: Indicates whether
to use the optimized CQI adjustment algorithm in
ACK multiplexing mode.
If this switch is On, the optimized CQI adjustment
algorithm is used.

eRAN

nd
If this switch is off, the optimized CQI adjustment

algorithm cannot be used.
AdaptiveStepVarySwitch: Indicates whether to enable
adaptive step change in CQI adjustment.
If this switch is On, significant changes in the signal
quality can be detected, and the CQI adjustment is
performed at a large step, accelerating the IBLER
convergence.
If this switch is off, the CQI adjustment is performed
at a fixed step.
DlCqiAdjDeltaOptSwitch: Indicates whether to enable
optimization on downlink CQI adjustment. If this
switch is off, the CQI adjustment is calculated based
on the following formula: CQI adjustment = (Number
of ACKs for initial transmissions x CQI adjustment
per ACK + Number of NACKs for initial
transmissions x CQI adjustment per NACK)/(Number
of NACKs for initial transmissions + Number of
ACKs for initial transmissions). If this switch is On,
the CQI adjustment is calculated based on the
following formula: CQI adjustment = Number of
ACKs for initial transmissions x CQI adjustment per
ACK + Number of NACKs for initial transmissions x
CQI adjustment per NACK).
DlEnVarIblerTargetSwitch: Indicates whether to
enable enhanced downlink target IBLER adaption. If
this switch is On, the downlink target IBLER is
adaptively adjusted based on CQI fluctuation and TB
size. If this switch is off, the downlink target IBLER
policy is controlled by DlVarIBLERtargetSwitch. This
switch applies only to FDD cells.
DlRetxTbsIndexAdjOptSwitch: Indicates whether to
enable transport block size (TBS) index adjustment
optimization in retransmissions.
If this switch is On, TBS index adjustment
optimization in retransmissions is enabled. The TBS
index is lowered for the scheduling of the last two
retransmissions, and the TBS index is determined
based on the CQI adjustment for the scheduling of
other retransmissions. If this switch is off, TBS index
adjustment optimization in retransmissions is
disabled. The TBS index is determined based on the
CQI adjustment for the scheduling of all
retransmissions.

eRAN

nd
CfiConvertOptSwitch: Indicates whether to enable

CFI calculation optimization. If this switch is turned
on, new CFI calculation tables for normal and special
subframes are used to ensure more accurate MCS
selection in normal and special subframes and
facilitate IBLER convergence to the target value. If
this switch is turned off, the original CFI calculation
tables for normal and special subframes are used. This
switch applies only to LTE TDD networks.
BundlingOptThdSwitch: Indicates whether to adjust
the MCS index threshold for enabling the optimized
CQI adjustment algorithm in TDD bundling mode. If
this switch is turned on, the lower MCS index
threshold for enabling the optimized CQI adjustment
algorithm in TDD bundling mode is changed from
MCS index 6 to MCS index 0. If this switch is turned
off, the lower MCS index threshold for enabling the
optimized CQI adjustment algorithm in TDD bundling
mode is MCS index 6. This switch applies only to
LTE TDD networks.
GUI Value Range:
CqiAdjAlgoSwitch(CqiAdjAlgoSwitch),
StepVarySwitch(StepVarySwitch),
DlVarIBLERtargetSwitch(DlVarIBLERtargetSwitch),
TddBundlingCqiAdjOptSwitch(TddBundlingCqiAd-
jOptSwitch), TddMultiplexingCqiAdjOptS-
witch(TddMultiplexingCqiAdjOptSwitch),
AdaptiveStepVarySwitch(AdaptiveStepVarySwitch),
DlCqiAdjDeltaOptSwitch(DlCqiAdjDeltaOptSwitch),
DlEnVarIblerTargetSwitch(DlEnVarIblerTargetS-
witch), DlRetxTbsIndexAdjOptS-
witch(DlRetxTbsIndexAdjOptSwitch),
CfiConvertOptSwitch(CfiConvertOptSwitch),
BundlingOptThdSwitch(BundlingOptThdSwitch)
Unit: None
Actual Value Range: CqiAdjAlgoSwitch,
StepVarySwitch, DlVarIBLERtargetSwitch,
TddBundlingCqiAdjOptSwitch, TddMultiplexingC-
qiAdjOptSwitch, AdaptiveStepVarySwitch,
DlCqiAdjDeltaOptSwitch, DlEnVarIblerTargetSwitch,
DlRetxTbsIndexAdjOptSwitch,
CfiConvertOptSwitch, BundlingOptThdSwitch
Default Value: CqiAdjAlgoSwitch:On,
StepVarySwitch:Off, DlVarIBLERtargetSwitch:Off,
TddBundlingCqiAdjOptSwitch:Off,
TddMultiplexingCqiAdjOptSwitch:Off,
AdaptiveStepVarySwitch:Off, DlCqiAdjDeltaOptS-

eRAN

nd
witch:Off, DlEnVarIblerTargetSwitch:Off,
DlRetxTbsIndexAdjOptSwitch:Off,
CfiConvertOptSwitch:Off,
BundlingOptThdSwitch:Off
CellUlsc SrMask MOD LOFD-0 VoIP Meaning: Indicates whether to enable scheduling
hAlgo Switch CELLU 01016 / Semi- request (SR) masking in logical channels for UEs
LSCHA TDLOF persisten complying with 3GPP Release 9 or later when the
LGO D-00101 t SpsSchSwitch option under the UlSchSwitch
LST 6 Scheduli parameter is selected. If this parameter is set to
CELLU ng ON(On), SR masking in logical channels is enabled. If
LSCHA this parameter is set to OFF(Off), SR masking in
LGO logical channels is disabled.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellUlsc SpsRelT MOD LOFD-0 Dynami Meaning: Indicates the threshold for the number of
hAlgo hd CELLU 0101502 c consecutive zero-payload packets received by the
LSCHA / Scheduli eNodeB. After receiving consecutive zero-payload
LGO TDLOF ng packets of a number that is equal to the value of this
LST D-00101 parameter, the eNodeB performs implicit release of
CELLU 502 semi-persistent resources.
LSCHA GUI Value Range: 2~3
LGO Unit: None
Default Value: 2

eRAN

nd
CellAlg UlPcAlg MOD LBFD-0 Broadca Meaning:

oSwitch oSwitch CELLA 02009 / st of Indicates the switches used to enable or disable power
LGOSW TDLBF system control for the PUSCH or PUCCH.
ITCH D-00200 informat CloseLoopSpsSwitch: Indicates whether to enable
LST 9 ion closed-loop power control for the PUSCH in semi-
CELLA LBFD-0 Uplink persistent scheduling mode. If this switch is on, TPC
LGOSW 02026 / Power commands are adjusted based on correctness of the
ITCH TDLBF Control received initial-transmission packets to decrease the
D-00202 PUCCH IBLER. InnerLoopPuschSwitch: Indicates whether to
6 Outer enable inner-loop power control for the PUSCH in
LBFD-0 Loop dynamic scheduling mode. Inner-loop power control
81101 / Power for the PUSCH in dynamic scheduling mode is
TDLBF Control enabled only when this switch is on.
D-08110 PhSinrTarUpdateSwitch: None. InnerLoopPucchS-
4 witch: Indicates whether to enable inner-loop power
control for the PUCCH. Inner-loop power control for
the PUCCH is enabled only when this switch is on.
OiSinrTarUpdateSwitch: None. PowerSavingSwitch:
None. CloseLoopOptPUSCHSwitch: Indicates
whether to enable the optimization on closed-loop
power control for the PUSCH in dynamic scheduling
mode. This parameter applies only to LTE TDD cells.
PucchPcDtxSinrSwitch: Indicates whether the
eNodeB processes the measured uplink SINR in the
DTX state when the PUCCH DTX is detected. If this
switch is off, the eNodeB does not process the
measured uplink SINR in the DTX state when the
PUCCH DTX is detected. If this switch is on, the
eNodeB processes the measured uplink SINR even
when PUCCH DTX is detected, generates power
control commands based on the SINR, and delivers
the power control commands to UEs.
PuschIoTCtrlSwitch: Indicates whether to enable
interference control in closed-loop power control for
the PUSCH in dynamic scheduling mode. Interference
control in closed-loop power control for the PUSCH
in dynamic scheduling mode is enabled only when
this switch is on. SrsPcSwitch: Indicates whether to
enable SRS power control adjustment. SRS power
control adjustment is enabled only when this switch is
on. This switch applies only to LTE TDD.
NearPointUeOptPUSCHSwitch: Indicates whether to
apply optimized closed-loop power control for the
PUSCH to UEs near the cell center. The optimization
helps UEs near the cell center to avoid unnecessary
power lowering due to inter-RAT or abrupt
interference. If this switch is on, optimized closed-
loop power control for the PUSCH is applied to UEs

eRAN

nd
near the cell center. If this switch is off, optimized

closed-loop power control for the PUSCH is not
applied to UEs near the cell center. This switch
applies only to LTE FDD cells. PuschRsrpHighThd-
Switch: Indicates whether closed-loop power control
for the PUSCH limits the maximum value of RSRP. If
this switch is off, closed-loop power control for the
PUSCH does not limit the maximum value of RSRP.
If this switch is on, the maximum value of RSRP
cannot exceed the RSRP value specified by the
PuschRsrpHighThd parameter in the CellAlgoSwitch
in this version. This switch applies only to LTE FDD
cells. OuterLoopPucchSwitch: Indicates whether to
enable outer-loop PUCCH power control. Outer-loop
PUCCH power control is enabled only when this
switch is on.This option does not apply to cells
established on LBBPc boards.
GroupPCForPucchSwitch: Indicates whether to enable
group power control for the PUCCH in dynamic
scheduling mode. This switch applies only to LTE
TDD cells in which UEs must support group power
control for the PUCCH.
GUI Value Range:
CloseLoopSpsSwitch(CloseLoopSpsSwitch),
InnerLoopPuschSwitch(InnerLoopPuschSwitch),
PhSinrTarUpdateSwitch(PhSinrTarUpdateSwitch),
InnerLoopPucchSwitch(InnerLoopPucchSwitch),
OiSinrTarUpdateSwitch(OiSinrTarUpdateSwitch),
PowerSavingSwitch(PowerSavingSwitch),
CloseLoopOptPUSCHS-
witch(CloseLoopOptPUSCHSwitch),
PucchPcDtxSinrSwitch(PucchPcDtxSinrSwitch),
PuschIoTCtrlSwitch(PuschIoTCtrlSwitch),
SrsPcSwitch(SrsPcSwitch),
NearPointUeOptPUSCHS-
witch(NearPointUeOptPUSCHSwitch),
PuschRsrpHighThdSwitch(PuschRsrpHighThd-
Switch), OuterLoopPucchSwitch(OuterLoopPucchS-
witch), GroupPCForPucchS-
witch(GroupPCForPucchSwitch)
Unit: None
Actual Value Range: CloseLoopSpsSwitch,
InnerLoopPuschSwitch, PhSinrTarUpdateSwitch,
InnerLoopPucchSwitch, OiSinrTarUpdateSwitch,
PowerSavingSwitch, CloseLoopOptPUSCHSwitch,
PucchPcDtxSinrSwitch, PuschIoTCtrlSwitch,
SrsPcSwitch, NearPointUeOptPUSCHSwitch,

eRAN

nd
PuschRsrpHighThdSwitch, OuterLoopPucchSwitch,
GroupPCForPucchSwitch
Default Value: CloseLoopSpsSwitch:Off,
InnerLoopPuschSwitch:On, PhSinrTarUpdateS-
witch:Off, InnerLoopPucchSwitch:On,
OiSinrTarUpdateSwitch:Off, PowerSavingSwitch:Off,
CloseLoopOptPUSCHSwitch:Off, PucchPcDtxSinrS-
witch:Off, PuschIoTCtrlSwitch:Off, SrsPcSwitch:On,
NearPointUeOptPUSCHSwitch:Off,
PuschRsrpHighThdSwitch:Off, OuterLoopPucchS-
witch:Off, GroupPCForPucchSwitch:Off

eRAN

nd
CellAlg DlPcAlg MOD LBFD-0 Physical Meaning:

oSwitch oSwitch CELLA 02003 / Channel Indicates the switches used to enable or disable power
LGOSW TDLBF Manage control for PDSCH, PDCCH, and PHICH.
ITCH D-00200 ment
LST 3 Broadca PdschSpsPcSwitch: Indicates the switch for power
CELLA LBFD-0 st of control during semi-persistent scheduling on the
LGOSW 02009 / system PDSCH. If the switch is off, power is allocated evenly
ITCH TDLBF informat during semi-persistent scheduling on the PDSCH. If
D-00200 ion the switch is on, power control is applied during semi-
9 persistent scheduling on the PDSCH, ensuring
Dynami communication quality (indicated by IBLER) of VoIP
LBFD-0 c services in the QPSK modulation scheme.
02016 / Downlin
TDLBF k Power PhichInnerLoopPcSwitch: Indicates the switch for
D-00201 Allocati PHICH inner-loop power control. If the switch is off,
6 on only the initial transmit power for the PHICH is set. If
the switch is on, the eNodeB controls the physical
channel transmit power to enable the receive SINR to
converge to the target SINR.
PdcchPcSwitch: Indicates the switch for PDCCH
power control. If the switch is off, power is allocated
evenly to PDCCH. If the switch is on, power allocated
to PDCCH is adjusted dynamically.
EDlMaxTXPwrSwitch: Indicates the switch for
enhanced maximum TX power of the cell. If this
switch is off, the maximum TX power of the cell is
determined by the reference signal (RS) power and the
scaling factor indexes Pa and Pb. If this switch is on,
the maximum TX power of the cell can be increased
to improve the RB usage in the cell. This switch has
no impact on the TDD 20M, TDD 15HMz and 10M
cell.
BFModeUserPwrSwitch: Specifies whether to turn on
the UE power optimization switch in BF mode. If the
BFModeUserPwrSwitch check box is cleared, BF UEs
adopt the existing power allocation principle. If the
BFModeUserPwrSwitch check box is selected, the
eNodeB increases the BF UE power based on the
configured power headroom. This switch applies only
to LTE TDD networks.
SigPowerIncreaseSwitch: Indicates the switch
controlling signaling power improvement. If this
switch is off, the signaling is transmitted using the
original power during network entry. If this switch is
on, the PDSCH transmit power increases when
scheduling is performed for downlink retransmission

eRAN

nd
of signaling during network entry. This switch applies

only to LTE TDD networks.
GUI Value Range: PdschSpsPcSwitch,
PhichInnerLoopPcSwitch, PdcchPcSwitch,
EDlMaxTXPwrSwitch, BFModeUserPwrSwitch,
SigPowerIncreaseSwitch
Unit: None
Actual Value Range: PdschSpsPcSwitch,
PhichInnerLoopPcSwitch, PdcchPcSwitch,
EDlMaxTXPwrSwitch, BFModeUserPwrSwitch,
SigPowerIncreaseSwitch
Default Value: PdschSpsPcSwitch:Off,
PhichInnerLoopPcSwitch:Off, PdcchPcSwitch:On,
EDlMaxTXPwrSwitch:Off,
BFModeUserPwrSwitch:Off, SigPowerIncreaseS-
witch:Off
PdcpRo RohcSw MOD LOFD-0 RObust Meaning:

hcPara itch PDCPR 01017 / Header Indicates whether to enable ROHC.
OHCPA TDLOF Compre
RA D-00101 ssion Set this parameter to ON if the eNodeB is expected to
LST 7 (ROHC) support VoIP or video services.
PDCPR GUI Value Range: OFF(Off), ON(On)
OHCPA Unit: None
RA

eRAN

nd
CellUlsc UlVoipR MOD LOFD-0 Dynami Meaning:

hAlgo lcMaxSe CELLU 0101502 c Indicates whether to apply upper limit control on
gNum LSCHA / Scheduli service data unit (SDU) segmentation at the radio link
LGO TDLOF ng control (RLC) layer in the uplink for VoIP services
LST D-00101 scheduled in non-TTI bundling mode and the
CELLU 502 maximum SDU segments at the RLC layer.
LSCHA
LGO If this parameter is set to 0, the upper limit control on
SDU segmentation at the RLC layer is disabled in the
uplink for VoIP services scheduled in non-TTI
bundling mode.
If this parameter is set to a non-zero value X, upper
limit control on SDU segmentation at the RLC layer is
enabled and a maximum of X SDU segments that can
be divided for VoIP services in uplink dynamic
scheduling in non-TTI bundling mode.
Unit: None
Default Value: 0

eRAN

nd
GlobalP LcgProfi MOD LBFD-0 Basic Meaning:

rocSwitc le GLOBA 02025 / Scheduli Indicates the logical channel group configuration.
h LPROC TDLBF ng
SWITC D-00202 Dynami Currently, three logical channel group profiles are
H 5 c available. If this parameter is set to
LST LOFD-0 Scheduli LCG_PROFILE_0, the control-plane services (SRB1,
GLOBA 0101502 ng SRB2, and bearers with a QCI of 5), VoIP services
LPROC / (bearers with a QCI of 1), GBR services, and non-
SWITC TDLOF GBR services are assigned logical channel groups 0,
H D-00101 1, 2, and 3, respectively.
502 If this parameter is set to LCG_PROFILE_1, the
control-plane services, VoIP services, GBR services,
high-priority non-GBR services, and low-priority non-
GBR services are assigned logical channel groups 0,
1, 2, and 3, respectively.
If this parameter is set to LCG_PROFILE_2, the
control-plane services, VoIP services, high-priority
non-GBR services, and low-priority non-GBR
services are assigned logical channel groups 0, 1, 2, 3,
respectively. In addition, services with a QCI of 2 to 4
are also assigned logical channel group 1. If this
parameter is set to LCG_PROFILE_2, VoIP services
must be carried by bearers with a QCI of 1 and bearers
with a QCI of 2 to 4 are not used. The parameter value
LCG_PROFILE_2 does not apply to LTE TDD.
GUI Value Range: LCG_PROFILE_0,
LCG_PROFILE_1, LCG_PROFILE_2
Unit: None
Actual Value Range: LCG_PROFILE_0,
LCG_PROFILE_1, LCG_PROFILE_2
Default Value: LCG_PROFILE_0
Drx DrxAlg MOD LBFD-0 DRX Meaning: Indicates the DRX switch. The setting of
Switch DRX 02017 / this parameter has no effect on dynamic DRX. DRX
LST TDLBF applies to a CA UE only when this parameter is set to
DRX D-00201 ON(On) on both eNodeBs to which the PCell and
7 SCell of the CA UE belong.
GUI Value Range: OFF(Off), ON(On)
Unit: None

eRAN

nd
CellStan QciPrior MOD LBFD-0 Coverag Meaning: Indicates the QCI priority used by each
dardQci ityForH CELLS 0201801 e Based QCI-based handover algorithm. A larger value of this
o TANDA LBFD-0 Intra- parameter indicates a lower priority. This parameter
RDQCI 0201802 frequenc applies to handover parameter selection based on QCI
LST y priorities, target frequency selection in service-based
LBFD-0 Handov inter-frequency handovers, and inter-RAT handover
CELLS 0201804
TANDA er policy selection. For a service that involves all the
RDQCI LBFD-0 Coverag preceding selection, the setting of this parameter
0201805 e Based determines the handover parameter, target frequency,
LOFD-0 Inter- and handover policy corresponding to a QCI.
01072 frequenc GUI Value Range: 1~9
LOFD-0 y Unit: None
01073 Handov
er Actual Value Range: 1~9
Distance Default Value: 9

Based
Inter-
frequenc
y
Handov
er
Service
Based
Inter-
frequenc
y
Handov
er
Distance
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
GERAN

eRAN

nd
IntraFre IntraFre ADD LBFD-0 Coverag Meaning: Indicates the hysteresis for intra-frequency
qHoGro qHoA3 INTRA 0201801 e Based handover event A3. This parameter decreases frequent
up Hyst FREQH / Intra- event triggering due to radio signal fluctuations and
OGROU TDLBF frequenc reduces the probability of handover decision errors
P D-00201 y and ping-pong handovers. A larger value of this
MOD 801 Handov parameter results in a lower probability. The
INTRA er hysteresis for event inter-frequency handover event
FREQH A3 is the same as the value of this parameter. For
OGROU details, see 3GPP TS 36.331.
P GUI Value Range: 0~30
LST Unit: 0.5dB
INTRA Actual Value Range: 0~15
FREQH
OGROU Default Value: 2
P
IntraFre IntraFre ADD LBFD-0 Coverag Meaning: Indicates the offset for event A3. If the
qHoGro qHoA3 INTRA 0201801 e Based parameter is set to a large value, an intra-frequency
up Offset FREQH / Intra- handover is performed only when the signal quality of
OGROU TDLBF frequenc the neighboring cell is significantly better than that of
P D-00201 y the serving cell and other triggering conditions are
MOD 801 Handov met. For details, see 3GPP TS 36.331.
INTRA er GUI Value Range: -30~30
FREQH Unit: 0.5dB
OGROU
P Actual Value Range: -15~15
LST Default Value: 2

INTRA
FREQH
OGROU
P

eRAN

nd
IntraFre IntraFre ADD LBFD-0 Coverag Meaning:

qHoGro qHoA3T INTRA 0201801 e Based Indicates the time-to-trigger for intra-frequency
up imeToTr FREQH / Intra- handover event A3.
ig OGROU TDLBF frequenc
P D-00201 y When the UE detects that the signal quality in the
MOD 801 Handov serving cell and that in at least one neighboring cell
INTRA er meet the entering condition, it does not immediately
FREQH send a measurement report to the eNodeB. Instead, the
OGROU UE sends a report only when the signal quality meets
P the entering condition throughout the time-to-trigger.
LST This parameter helps decrease the number of

INTRA occasionally triggered event reports, the average
FREQH number of handovers, and the number of incorrect
OGROU handovers, preventing unnecessary handovers. The
P time-to-trigger for inter-frequency handover event A3
is the same as the value of this parameter.
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Default Value: 320ms
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the hysteresis of event A1/A2 for
qHoGro qHoA1 INTERF 0201802 e Based triggering inter-frequency measurement. This
up A2Hyst REQHO / Inter- parameter is used to prevent frequent triggering of
GROUP TDLBF frequenc event evaluation caused by radio signal fluctuation. In
MOD D-00201 y this way, the probability of ping-pong handovers or
INTERF 802 Handov handover decision errors is reduced. A larger value of
REQHO er this parameter results in a lower probability.
GROUP GUI Value Range: 0~30
LST Unit: 0.5dB
INTERF
REQHO
GROUP Default Value: 2

eRAN

nd
InterFre InterFre ADD LBFD-0 Coverag Meaning:

qHoGro qHoA1 INTERF 0201802 e Based Indicates the time-to-trigger of event A1/A2 for
up A2Time REQHO / Inter- triggering inter-frequency measurement.
ToTrig GROUP TDLBF frequenc
MOD D-00201 y When detecting that the signal quality in the serving
INTERF 802 Handov cell meets the entering condition, the UE does not
REQHO er send a measurement report to the eNodeB
GROUP immediately. Instead, the UE sends a report only when
the signal quality continuously meets the entering
LST condition during the time-to-trigger. This parameter
INTERF helps decrease the number of occasionally triggered
REQHO event reports, the average number of handovers, and
GROUP the number of wrong handovers. In summary, it helps
prevent unnecessary handovers.
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms

qHoGro qHoA1T INTERF 0201802 e Based Indicates the RSRP threshold for event A1 related to
up hdRsrp REQHO / Inter- event-A4/A5-triggered inter-frequency handover.
GROUP TDLBF frequenc
MOD D-00201 y When the measured RSRP value exceeds this
INTERF 802 Handov threshold, a measurement report will be sent.
REQHO er GUI Value Range: -140~-43
GROUP Unit: dBm
LST Actual Value Range: -140~-43
INTERF
REQHO Default Value: -105
GROUP

eRAN

nd

qHoGro qHoA1T INTERF 0201802 e Based Indicates the RSRQ threshold for event A1 related to
up hdRsrq REQHO / Inter- event-A4/A5-triggered inter-frequency handover.
MOD D-00201 y When the measured RSRQ value exceeds this
GROUP Unit: 0.5dB
INTERF
GROUP

qHoGro qHoA2T INTERF 0201802 e Based Indicates the RSRP threshold for event A2 related to
up hdRsrp REQHO / Inter- event-A4/A5-triggered inter-frequency handover.
MOD D-00201 y When the measured RSRP value is lower than this
GROUP Unit: dBm
INTERF
GROUP

qHoGro qHoA2T INTERF 0201802 e Based Indicates the RSRQ threshold for event A2 related to
up hdRsrq REQHO / Inter- event-A4/A5-triggered inter-frequency handover.
MOD D-00201 y When the measured RSRQ value is lower than this
GROUP Unit: 0.5dB
INTERF
GROUP

eRAN

nd
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the hysteresis for event A4. This
qHoGro qHoA4 INTERF 0201802 e Based parameter is used to prevent frequent triggering of
up Hyst REQHO / Inter- event evaluation caused by radio signal fluctuation. In
GROUP TDLBF frequenc this way, the probability of ping-pong handovers or
MOD D-00201 y handover decision errors is reduced. A larger value of
INTERF 802 Handov this parameter results in a lower probability.
REQHO LBFD-0 er GUI Value Range: 0~30
GROUP 0201804 Distance Unit: 0.5dB
LST / Based
TDLBF Inter- Actual Value Range: 0~15
INTERF
REQHO D-00201 frequenc Default Value: 2
GROUP 804 y
LBFD-0 Handov
0201805 er
/ Service
TDLBF Based
D-00201 Inter-
805 frequenc
y
Handov
er
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the RSRP threshold for event A4
qHoGro qHoA4T INTERF 0201802 e Based related to coverage-based inter-frequency handover.
up hdRsrp REQHO / Inter- When the measured RSRP value exceeds this
GROUP TDLBF frequenc threshold, event A4 is reported. The value of this
MOD D-00201 y parameter is also used as the RSRP threshold for event
INTERF 802 Handov A4 related to distance-based, UL-power-based, or
REQHO LBFD-0 er SPID-based inter-frequency handover back to the
GROUP 0201804 Distance HPLMN.
LST / Based GUI Value Range: -140~-43
INTERF TDLBF Inter- Unit: dBm
REQHO D-00201 frequenc
804 y Actual Value Range: -140~-43
GROUP
Handov Default Value: -105
er

eRAN

nd
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the RSRQ threshold for event A4
qHoGro qHoA4T INTERF 0201802 e Based related to coverage-based inter-frequency handover.
up hdRsrq REQHO / Inter- When the measured RSRQ value exceeds this
GROUP TDLBF frequenc threshold, event A4 is reported. The value of this
MOD D-00201 y parameter is also used as the RSRQ threshold for
INTERF 802 Handov event A4 related to distance-based, UL-power-based,
REQHO LBFD-0 er or SPID-based inter-frequency handover back to the
GROUP 0201804 Distance HPLMN.
LST / Based GUI Value Range: -40~-6
INTERF TDLBF Inter- Unit: 0.5dB
REQHO D-00201 frequenc
804 y Actual Value Range: -20~-3
GROUP
Handov Default Value: -20
er

qHoGro qHoA4T INTERF 0201802 e Based Indicates the time-to-trigger for event A4 for the inter-
up imeToTr REQHO / Inter- frequency handover. When detecting that the signal
ig GROUP TDLBF frequenc quality in at least one neighboring cell meets the
MOD D-00201 y entering condition, the UE does not send a
INTERF 802 Handov measurement report to the eNodeB immediately.
REQHO LBFD-0 er Instead, the UE sends a report only when the signal
GROUP 0201804 Distance quality continuously meets the entering condition
LST / Based during the time-to-trigger.
INTERF TDLBF Inter-
D-00201 frequenc This parameter helps decrease the number of
REQHO occasionally triggered event reports, the average
GROUP 804 y
Handov number of handovers, and the number of wrong
LBFD-0 handovers. In summary, it helps prevent unnecessary
0201805 er
handovers.
/ Service
TDLBF Based GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
D-00201 Inter- 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
805 frequenc 1024ms, 1280ms, 2560ms, 5120ms
y Unit: ms
Handov Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
er 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms

eRAN

nd
InterFre InterFre ADD LBFD-0 Coverag Meaning: Indicates the offset for event A3 associated
qHoGro qHoA3 INTERF 0201802 e Based with inter-frequency handover. This parameter
up Offset REQHO / Inter- determines the border between the serving cell and the
GROUP TDLBF frequenc neighboring cell. If the parameter is set to a large
MOD D-00201 y value, an inter-frequency handover is performed only
INTERF 802 Handov when the signal quality of the neighboring cell is
REQHO er significantly better than that of the serving cell and
GROUP other triggering conditions are met. For details, see
3GPP TS 36.331.
LST
INTERF GUI Value Range: -30~30
REQHO Unit: 0.5dB
GROUP Actual Value Range: -15~15
Default Value: 2
InterFre A3Inter ADD LBFD-0 Coverag Meaning: Indicates the RSRP threshold for event A1
qHoGro FreqHo INTERF 0201802 e Based related to event-A3-triggered inter-frequency
up A1ThdR REQHO / Inter- handover. When the measured RSRP value exceeds
srp GROUP TDLBF frequenc this threshold, a measurement report will be sent.
MOD D-00201 y GUI Value Range: -140~-43
INTERF 802 Handov
er Unit: dBm
REQHO
GROUP Actual Value Range: -140~-43
LST Default Value: -95

INTERF
REQHO
GROUP
InterFre A3Inter ADD LBFD-0 Coverag Meaning: Indicates the RSRP threshold for event A2
qHoGro FreqHo INTERF 0201802 e Based related to event-A3-triggerd inter-frequency handover.
up A2ThdR REQHO / Inter- When the measured RSRP value is lower than this
srp GROUP TDLBF frequenc threshold, a measurement report will be sent.
MOD D-00201 y GUI Value Range: -140~-43
INTERF 802 Handov
er Unit: dBm
REQHO

INTERF
REQHO
GROUP

eRAN

nd

qHoGro qHoA5T INTERF 0201802 e Based Indicates the RSRP threshold 1 in the serving cell of
up hd1Rsrp REQHO / Inter- event A5 for triggering inter-frequency handovers.
MOD D-00201 y When the measured RSRP in the serving cell is
INTERF 802 Handov smaller than the value of this parameter and the RSRP
REQHO er or RSRQ in the neighboring cell is higher than the
GROUP value of InterFreqHoA4ThdRsrp or
InterFreqHoA4ThdRsrq, the UE reports event A5.
LST
INTERF GUI Value Range: -140~-43
REQHO Unit: dBm
Default Value: -109

qHoGro qHoA5T INTERF 0201802 e Based Indicates the RSRQ threshold 1 in the serving cell of
up hd1Rsrq REQHO / Inter- event A5 for triggering inter-frequency handovers.
MOD D-00201 y When the measured RSRQ in the serving cell is
INTERF 802 Handov smaller than the value of this parameter and the RSRP
REQHO er or RSRQ in the neighboring cell is higher than the
GROUP value of InterFreqHoA4ThdRsrp or
InterFreqHoA4ThdRsrq, the UE reports event A5.
LST
INTERF GUI Value Range: -40~-6
REQHO Unit: 0.5dB
Default Value: -24
InterFre InterFre ADD LBFD-0 Service Meaning: Indicates the RSRP threshold for event A4
qHoGro qLoadB INTERF 0201805 Based related to load-based inter-frequency handover. When
up asedHo REQHO / Inter- the measured RSRP value exceeds this threshold,
A4ThdR GROUP TDLBF frequenc event A4 is reported. The value of this parameter is
srp MOD D-00201 y also used as the RSRP threshold for event A4 related
INTERF 805 Handov to frequency-priority-based handover, service-based
REQHO er inter-frequency handover, inter-frequency handover of
GROUP low-speed UEs, or redirection of high-speed UEs.
LST GUI Value Range: -140~-43
INTERF Unit: dBm
REQHO Actual Value Range: -140~-43
GROUP
Default Value: -103

eRAN

nd
InterFre InterFre ADD LBFD-0 Service Meaning: Indicates the RSRQ threshold for event A4
qHoGro qLoadB INTERF 0201805 Based related to load-based inter-frequency handover. When
up asedHo REQHO / Inter- the measured RSRQ value exceeds this threshold,
A4ThdR GROUP TDLBF frequenc event A4 is reported. The value of this parameter is
srq MOD D-00201 y also used as the RSRQ threshold for event A4 related
INTERF 805 Handov to frequency-priority-based, service-based inter-
REQHO er frequency handover, inter-frequency handover of low-
GROUP speed UEs, or redirection of high-speed UEs.
INTERF Unit: 0.5dB
REQHO Actual Value Range: -20~-3
GROUP
Default Value: -18
InterFre FreqPriI ADD None None Meaning: Indicates the RSRP threshold for frequency-
qHoGro nterFreq INTERF priority-based inter-frequency measurement event A1.
up HoA1Th REQHO When the measured RSRP value exceeds this
dRsrp GROUP threshold, an event A1 report will be sent.
MOD GUI Value Range: -140~-43
INTERF Unit: dBm
REQHO

INTERF
REQHO
GROUP
InterFre FreqPriI ADD None None Meaning:

qHoGro nterFreq INTERF Indicates the RSRQ threshold for frequency-priority-
up HoA1Th REQHO based inter-frequency measurement event A1.
dRsrq GROUP
MOD When the measured RSRQ value exceeds this
INTERF threshold, an event A1 report will be sent.
REQHO GUI Value Range: -40~-6
GROUP Unit: 0.5dB
INTERF
GROUP

eRAN

nd

qHoGro nterFreq INTERF Indicates the RSRP threshold for frequency-priority-
up HoA2Th REQHO based inter-frequency measurement event A2.
dRsrp GROUP
MOD If the measured RSRP value is less than this threshold,
INTERF an event A2 report will be sent.
GROUP Unit: dBm
INTERF
GROUP

qHoGro nterFreq INTERF Indicates the RSRQ threshold for inter-frequency
up HoA2Th REQHO measurement event A2.
dRsrq GROUP
MOD When the measured RSRQ value is below this
INTERF threshold, a measurement report will be sent.
GROUP Unit: 0.5dB
INTERF
GROUP

eRAN

nd
InterRat InterRat ADD LOFD-0 PS Inter- Meaning: Indicates the hysteresis of event A1/A2 for
HoCom HoA1A INTER 01019 / RAT triggering inter-RAT measurement. This parameter is
mGroup 2Hyst RATHO TDLOF Mobility used to prevent frequent triggering of event evaluation
COMM D-00101 between caused by radio signal fluctuation. In this way, the
GROUP 9 E- probability of ping-pong handovers or handover
MOD LOFD-0 UTRAN decision errors is reduced. A larger value of this
INTER 01020 / and parameter results in a lower probability.
RATHO TDLOF UTRAN GUI Value Range: 0~30
COMM D-00102 PS Inter- Unit: 0.5dB
GROUP 0 RAT
Mobility Actual Value Range: 0~15
LST LOFD-0
INTER 01021 / between Default Value: 2
RATHO TDLOF E-
COMM D-00102 UTRAN
GROUP 1 and
GERAN
TDLOF
D-00102 PS Inter-
2 RAT
Mobility
TDLOF between
D-00102 E-
3 UTRAN
and
CDMA2
000
SRVCC
to
UTRAN
SRVCC
to
GERAN

eRAN

nd
InterRat InterRat ADD LOFD-0 PS Inter- Meaning:

HoCom HoA1A INTER 01019 / RAT Indicates the time-to-trigger of event A1/A2 for
mGroup 2TimeT RATHO TDLOF Mobility triggering inter-RAT measurement.
oTrig COMM D-00101 between
GROUP 9 E- When detecting that the signal quality in the serving
MOD LOFD-0 UTRAN cell meets the entering condition, the UE does not
INTER 01020 / and send a measurement report to the eNodeB
RATHO TDLOF UTRAN immediately. Instead, the UE sends a report only when
COMM D-00102 PS Inter- the signal quality continuously meets the entering
GROUP 0 RAT condition during the time-to-trigger.
LST LOFD-0 Mobility This parameter helps decrease the number of

INTER 01021 / between occasionally triggered event reports, the average
RATHO TDLOF E- number of handovers, and the number of wrong
COMM D-00102 UTRAN handovers. In summary, it helps prevent unnecessary
GROUP 1 and handovers.
GERAN
TDLOF GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
D-00102 PS Inter- 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
2 RAT 1024ms, 1280ms, 2560ms, 5120ms
Mobility
TDLOF between Unit: ms
D-00102 E- Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
3 UTRAN 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
and 1024ms, 1280ms, 2560ms, 5120ms
CDMA2 Default Value: 640ms
000
SRVCC
to
UTRAN
SRVCC
to
GERAN

eRAN

nd
InterRat InterRat ADD LOFD-0 PS Inter- Meaning: Indicates the RSRP threshold for inter-RAT
HoCom HoA1Th INTER 01019 / RAT measurement event A1. When the measured RSRP
mGroup dRsrp RATHO TDLOF Mobility value of the serving cell exceeds this threshold, an
COMM D-00101 between event A1 report will be sent.
GROUP 9 E- GUI Value Range: -140~-43
MOD LOFD-0 UTRAN
and Unit: dBm
INTER 01020 /
RATHO TDLOF UTRAN Actual Value Range: -140~-43
COMM D-00102 PS Inter- Default Value: -111
GROUP 0 RAT
LST LOFD-0 Mobility
INTER 01021 / between
RATHO TDLOF E-
COMM D-00102 UTRAN
GROUP 1 and
GERAN
TDLOF
D-00102 PS Inter-
2 RAT
Mobility
TDLOF between
D-00102 E-
3 UTRAN
and
CDMA2
000
SRVCC
to
UTRAN
SRVCC
to
GERAN

eRAN

nd

HoCom HoA1Th INTER 01019 / RAT Indicates the RSRQ threshold for inter-RAT
mGroup dRsrq RATHO TDLOF Mobility measurement event A1.
COMM D-00101 between
GROUP 9 E- When the measured RSRQ value of the serving cell
MOD LOFD-0 UTRAN exceeds this threshold, an event A1 report will be sent.
INTER 01020 / and GUI Value Range: -40~-6
RATHO TDLOF UTRAN
Unit: 0.5dB
COMM D-00102 PS Inter-
GROUP 0 RAT Actual Value Range: -20~-3
LST LOFD-0 Mobility Default Value: -20

INTER 01021 / between
RATHO TDLOF E-
COMM D-00102 UTRAN
GROUP 1 and
GERAN
TDLOF
D-00102 PS Inter-
2 RAT
Mobility
TDLOF between
D-00102 E-
3 UTRAN
and
CDMA2
000
SRVCC
to
UTRAN
SRVCC
to
GERAN

eRAN

nd

HoCom HoA2Th INTER 01019 / RAT Indicates the RSRP threshold for inter-RAT
mGroup dRsrp RATHO TDLOF Mobility measurement event A2.
GROUP 9 E- When the measured RSRP value of the serving cell is
MOD LOFD-0 UTRAN below this threshold, an event A2 report will be sent.
INTER 01020 / and If you need to change the parameter value, you are
RATHO TDLOF UTRAN advised to set this parameter to a value greater than
COMM D-00102 PS Inter- the value of the BlindHoA1A2ThdRsrp parameter in
GROUP 0 RAT the CellHoParaCfg MO.
LST LOFD-0 Mobility GUI Value Range: -140~-43

INTER 01021 / between Unit: dBm
RATHO TDLOF E-
UTRAN Actual Value Range: -140~-43
COMM D-00102
GROUP 1 and Default Value: -115
GERAN
TDLOF
D-00102 PS Inter-
2 RAT
Mobility
TDLOF between
D-00102 E-
3 UTRAN
and
CDMA2
000
SRVCC
to
UTRAN
SRVCC
to
GERAN

eRAN

nd

HoCom HoA2Th INTER 01019 / RAT Indicates the RSRQ threshold for inter-RAT
mGroup dRsrq RATHO TDLOF Mobility measurement event A2.
GROUP 9 E- When the measured RSRQ value of the serving cell is
MOD LOFD-0 UTRAN below this threshold, an event A2 report will be sent.
INTER 01020 / and If you need to change the parameter value, you are
RATHO TDLOF UTRAN advised to set this parameter to a value greater than
COMM D-00102 PS Inter- the value of the BlindHoA1A2ThdRsrq parameter in
GROUP 0 RAT the CellHoParaCfg MO.
LST LOFD-0 Mobility GUI Value Range: -40~-6

INTER 01021 / between Unit: 0.5dB
RATHO TDLOF E-
UTRAN Actual Value Range: -20~-3
COMM D-00102
GROUP 1 and Default Value: -24
GERAN
TDLOF
D-00102 PS Inter-
2 RAT
Mobility
TDLOF between
D-00102 E-
3 UTRAN
and
CDMA2
000
SRVCC
to
UTRAN
SRVCC
to
GERAN

eRAN

nd
InterRat InterRat ADD LOFD-0 PS Inter- Meaning: Indicates the Ec/N0 threshold for event B1
HoUtran HoUtran INTER 01019 / RAT related to coverage-based inter-RAT handover to
Group B1ThdE RATHO TDLOF Mobility UTRAN. This parameter specifies the requirement for
cn0 UTRAN D-00101 between Ec/N0 of the target UTRAN cell. For a cell with large
GROUP 9 E- signal fading variance, set this parameter to a large
MOD TDLOF UTRAN value to prevent unnecessary handovers. For a cell
INTER D-00102 and with small signal fading variance, set this parameter to
RATHO 2 UTRAN a small value to ensure timely handovers. A large
UTRAN SRVCC value of this parameter results in a low probability of
GROUP to handover to the UTRAN cell, and a small value leads
UTRAN to a high probability. When the measurement value
LST exceeds this threshold, a measurement report will be
INTER sent.
RATHO
UTRAN GUI Value Range: -48~0
GROUP Unit: 0.5dB
Actual Value Range: -24~0
Default Value: -24

HoUtran HoUtran INTER 01019 / RAT Indicates the RSCP threshold for event B1 related to
Group B1ThdR RATHO TDLOF Mobility coverage-based inter-RAT handover to UTRAN.
scp UTRAN D-00101 between
GROUP 9 E- This parameter specifies the requirement for RSCP of
MOD TDLOF UTRAN the target UTRAN cell.
INTER D-00102 and
UTRAN When the measurement value exceeds this threshold, a
RATHO 2 measurement report will be sent.
UTRAN SRVCC
GROUP to GUI Value Range: -120~-25
LST UTRAN Unit: dBm

INTER Actual Value Range: -120~-25
RATHO Default Value: -103
UTRAN
GROUP

eRAN

nd
InterRat InterRat ADD LOFD-0 PS Inter- Meaning: Indicates the hysteresis for event B1 related
HoUtran HoUtran INTER 01019 / RAT to inter-RAT handover to UTRAN. This parameter is
Group B1Hyst RATHO TDLOF Mobility used to prevent frequent triggering of event evaluation
UTRAN D-00101 between caused by radio signal fluctuation. In this way, the
MOD TDLOF UTRAN decision errors is reduced. A larger value of this
INTER D-00102 and parameter results in a lower probability of ping-pong
RATHO 2 UTRAN handovers or handover decision errors.
UTRAN SRVCC GUI Value Range: 0~30
GROUP to Unit: 0.5dB
LST UTRAN
INTER
RATHO Default Value: 0
UTRAN
GROUP

HoUtran HoUtran INTER 01019 / RAT Indicates the time-to-trigger for event B1 related to
Group B1Time RATHO TDLOF Mobility inter-RAT handover to UTRAN. When detecting that
ToTrig UTRAN D-00101 between the signal quality in at least one neighboring cell
GROUP 9 E- meets the entering condition, the UE does not send a
MOD TDLOF UTRAN measurement report to the eNodeB immediately.
INTER D-00102 and Instead, the UE sends a report only when the signal
RATHO 2 UTRAN quality continuously meets the entering condition
UTRAN SRVCC during the time-to-trigger.
GROUP to
UTRAN This parameter helps decrease the number of
LST occasionally triggered event reports, the average
INTER number of handovers and the number of wrong
RATHO handovers, preventing unnecessary handovers.
UTRAN
GROUP GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms

eRAN

nd
InterRat LdSvBa ADD LOFD-0 Service Meaning:

HoUtran sedHoUt INTER 01043 based Indicates the Ec/N0 threshold for event B1 related to
Group ranB1Th RATHO TDLOF inter- load- or service-based inter-RAT handover to
dEcn0 UTRAN D-00102 RAT UTRAN.
GROUP 2 handove
MOD r to This parameter specifies the requirement for Ec/N0 of
INTER UTRAN the target UTRAN cell. When the measurement value
RATHO SRVCC exceeds this threshold, a measurement report may be
UTRAN to sent. For a cell with large signal fading variance, set
GROUP UTRAN this parameter to a large value to prevent unnecessary
handovers. For a cell with small signal fading
LST variance, set this parameter to a small value to ensure
INTER timely handovers.
RATHO
UTRAN GUI Value Range: -48~0
GROUP Unit: 0.5dB
Actual Value Range: -24~0
Default Value: -18

HoUtran sedHoUt INTER 01043 based Indicates the RSCP threshold for event B1 related to
Group ranB1Th RATHO TDLOF inter- load- or service-based inter-RAT handover to
dRscp UTRAN D-00102 RAT UTRAN.
GROUP 2 handove
MOD r to This parameter specifies the requirement for RSCP of
INTER UTRAN the target UTRAN cell.
RATHO SRVCC
UTRAN to When the measurement value exceeds this threshold, a
GROUP UTRAN measurement report will be sent.
INTER Unit: dBm
RATHO
Actual Value Range: -120~-25
UTRAN
GROUP Default Value: -101

eRAN

nd
HoGera HoGera INTER 01020 / RAT to inter-RAT handover to GERAN. This parameter is
nGroup nB1Hyst RATHO TDLOF Mobility used to prevent frequent triggering of event evaluation
GERAN D-00102 between caused by radio signal fluctuation. In this way, the
MOD TDLOF UTRAN decision errors is reduced. A larger value of this
INTER D-00102 and parameter results in a lower probability of ping-pong
RATHO 3 GERAN handovers or handover decision errors.
GERAN SRVCC GUI Value Range: 0~30
GROUP to Unit: 0.5dB
LST GERAN
INTER
RATHO Default Value: 2
GERAN
GROUP

HoGera HoGera INTER 01020 / RAT Indicates the RSSI threshold for event B1 related to
nGroup nB1Thd RATHO TDLOF Mobility coverage-based inter-RAT handover to GERAN.
GERAN D-00102 between
GROUP 0 E- A UE sends a measurement report related to event B1
MOD UTRAN to the eNodeB when the RSSI in at least one GERAN
INTER and cell exceeds this threshold and other triggering
RATHO GERAN conditions are met. For details, see 3GPP TS 36.331.
GERAN GUI Value Range: -110~-48
GROUP Unit: dBm
INTER
RATHO Default Value: -100
GERAN
GROUP

eRAN

nd

HoGera HoGera INTER 01020 / RAT Indicates the time-to-trigger for event B1 related to
nGroup nB1Tim RATHO TDLOF Mobility inter-RAT handover to GERAN. When detecting that
eToTrig GERAN D-00102 between the signal quality in at least one neighboring cell
GROUP 0 E- meets the entering condition, the UE does not send a
MOD TDLOF UTRAN measurement report to the eNodeB immediately.
INTER D-00102 and Instead, the UE sends a report only when the signal
RATHO 3 GERAN quality continuously meets the entering condition
GERAN SRVCC during the time-to-trigger.
GROUP to
GERAN This parameter helps decrease the number of
LST occasionally triggered event reports, the average
INTER number of handovers and the number of wrong
RATHO handovers, preventing unnecessary handovers.
GERAN
GROUP GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms

HoGera sedHoG INTER 01046 / based Indicates the RSSI threshold for event B1 related to
nGroup eranB1T RATHO TDLOF inter- load- or service-based inter-RAT handover to
hd GERAN D-00104 RAT GERAN.
GROUP 6 handove
MOD r to When the measured RSSI value exceeds this
INTER GERAN threshold, a measurement report will be sent.
RATHO GUI Value Range: -110~-48
GERAN Unit: dBm
GROUP
Actual Value Range: -110~-48
LST
INTER Default Value: -98
RATHO
GERAN
GROUP

eRAN

nd
InterRat InterRat ADD LOFD-0 Enhance Meaning: Indicates the hysteresis for event B1 for
HoCdm HoCdm INTER 01090 / d CS inter-RAT handover to CDMA2000 1xRTT. This
a1xRttG aB1Hyst RATHO TDLOF Fallback parameter is used to prevent frequent triggering of
roup CDMA1 D-00109 to event evaluation caused by radio signal fluctuation. In
XRTTG 0 CDMA2 this way, the probability of ping-pong handovers or
ROUP 000 handover decision errors is reduced. A larger value of
MOD 1xRTT this parameter results in a lower probability of ping-
INTER pong handovers or handover decision errors.
RATHO GUI Value Range: 0~30
CDMA1 Unit: 0.5dB
XRTTG
ROUP Actual Value Range: 0~15

INTER
RATHO
CDMA1
XRTTG
ROUP
InterRat InterRat ADD None None Meaning: Indicates the pilot strength threshold for
HoCdm HoCdm INTER event B1 related to coverage-based inter-RAT
a1xRttG aB1Thd RATHO handover to CDMA2000 1xRTT. When the
roup Ps CDMA1 measurement value exceeds this threshold, a
XRTTG measurement report will be sent.
ROUP GUI Value Range: -63~0
MOD Unit: 0.5dB
INTER
RATHO Actual Value Range: -31.5~0
CDMA1 Default Value: -28
XRTTG
ROUP
LST
INTER
RATHO
CDMA1
XRTTG
ROUP

eRAN

nd
InterRat InterRat ADD LOFD-0 Enhance Meaning:

HoCdm HoCdm INTER 01090 / d CS Indicates the time-to-trigger for event B1 related to
a1xRttG aB1Tim RATHO TDLOF Fallback inter-RAT handover to CDMA2000 1xRTT.
roup eToTrig CDMA1 D-00109 to
XRTTG 0 CDMA2 When detecting that the signal quality in at least one
ROUP 000 neighboring cell meets the entering condition, the UE
MOD 1xRTT does not send a measurement report to the eNodeB
INTER immediately. Instead, the UE sends a report only when
RATHO the signal quality continuously meets the entering
CDMA1 condition during the time-to-trigger.
XRTTG This parameter helps decrease the number of
ROUP occasionally triggered event reports, the average
LST number of handovers and the number of wrong
INTER handovers, preventing unnecessary handovers.
RATHO GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
CDMA1 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
XRTTG 1024ms, 1280ms, 2560ms, 5120ms
ROUP
Unit: None
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
InterRat LdSvBa ADD LOFD-0 PS Inter- Meaning:

HoCdm sedHoC INTER 01021 / RAT Indicates the pilot strength threshold for event B1
a1xRttG dmaB1T RATHO TDLOF Mobility related to load- or service-based inter-RAT handover
roup hdPs CDMA1 D-00102 between to CDMA2000 1xRTT.
XRTTG 1 E-
ROUP UTRAN When the measurement value exceeds this threshold, a
MOD and measurement report will be sent.
INTER CDMA2 GUI Value Range: -63~0
RATHO 000
Unit: 0.5dB
CDMA1
XRTTG Actual Value Range: -31.5~0
ROUP Default Value: -24
LST
INTER
RATHO
CDMA1
XRTTG
ROUP

eRAN

nd
HoCdm HoCdm INTER 01021 / RAT to inter-RAT handover to CDMA2000 HRPD. This
aHrpdGr aB1Hyst RATHO TDLOF Mobility parameter is used to prevent frequent triggering of
oup CDMA D-00102 between event evaluation caused by radio signal fluctuation. In
HRPDG 1 E- this way, the probability of ping-pong handovers or
ROUP UTRAN handover decision errors is reduced. A larger value of
MOD and this parameter results in a lower probability of ping-
INTER CDMA2 pong handovers or handover decision errors.
RATHO 000 GUI Value Range: 0~30
CDMA Unit: 0.5dB
HRPDG
ROUP Actual Value Range: 0~15

INTER
RATHO
CDMA
HRPDG
ROUP

HoCdm HoCdm INTER 01021 / RAT Indicates the pilot strength threshold for event B1
aHrpdGr aB1Thd RATHO TDLOF Mobility related to load- or service-based inter-RAT handover
oup Ps CDMA D-00102 between to CDMA2000 HRPD.
HRPDG 1 E-
ROUP UTRAN When the measurement value exceeds this threshold, a
MOD and measurement report will be sent.
INTER CDMA2 GUI Value Range: -63~0
RATHO 000
Unit: 0.5dB
CDMA
HRPDG Actual Value Range: -31.5~0
LST
INTER
RATHO
CDMA
HRPDG
ROUP

eRAN

nd

HoCdm HoCdm INTER 01021 / RAT Indicates the time-to-trigger for event B1 related to
aHrpdGr aB1Tim RATHO TDLOF Mobility inter-RAT handover to CDMA2000 HRPD.
oup eToTrig CDMA D-00102 between
HRPDG 1 E- When detecting that the signal quality in at least one
ROUP UTRAN neighboring cell meets the entering condition, the UE
MOD and does not send a measurement report to the eNodeB
INTER CDMA2 immediately. Instead, the UE sends a report only when
RATHO 000 the signal quality continuously meets the entering
CDMA condition during the time-to-trigger.
HRPDG This parameter helps decrease the number of
ROUP occasionally triggered event reports, the average
LST number of handovers and the number of wrong
INTER handovers, preventing unnecessary handovers.
RATHO GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
CDMA 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
HRPDG 1024ms, 1280ms, 2560ms, 5120ms
ROUP
Unit: ms
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
InterRat LdSvBa ADD LOFD-0 CS Meaning:

HoCdm sedHoC INTER 01035 / Fallback Indicates the pilot strength threshold for event B1
aHrpdGr dmaB1T RATHO TDLOF to related to load- or service-based inter-RAT handover
oup hdPs CDMA D-00103 CDMA2 to CDMA2000 HRPD.
HRPDG 5 000
ROUP 1xRTT When the measurement value exceeds this threshold, a
MOD measurement report will be sent.
INTER GUI Value Range: -63~0
RATHO Unit: 0.5dB
CDMA
HRPDG Actual Value Range: -31.5~0
LST
INTER
RATHO
CDMA
HRPDG
ROUP

eRAN

nd
InterRat Cdma20 ADD LOFD-0 PS Inter- Meaning: Indicates the B2 RSRP threshold 1 used
HoCdm 00Hrpd INTER 01021 / RAT during optimized handovers from E-UTRAN to
aHrpdGr B2Thd1 RATHO TDLOF Mobility CDMA2000 eHRPD.
oup Rsrp CDMA D-00102 between GUI Value Range: -140~-43
HRPDG 1 E-
ROUP UTRAN Unit: dBm
MOD and Actual Value Range: -140~-43

INTER CDMA2 Default Value: -113
RATHO 000
CDMA
HRPDG
ROUP
LST
INTER
RATHO
CDMA
HRPDG
ROUP
InterRat Cdma20 ADD LOFD-0 PS Inter- Meaning: Indicates the B2 RSRQ threshold 1 used
HoCdm 00Hrpd INTER 01021 / RAT during optimized handovers from E-UTRAN to
aHrpdGr B2Thd1 RATHO TDLOF Mobility CDMA2000 eHRPD.
oup Rsrq CDMA D-00102 between GUI Value Range: -40~-6
HRPDG 1 E-
ROUP UTRAN Unit: 0.5dB
MOD and Actual Value Range: -20~-3

INTER CDMA2 Default Value: -14
RATHO 000
CDMA
HRPDG
ROUP
LST
INTER
RATHO
CDMA
HRPDG
ROUP

eRAN

nd
ENodeB CaAlgo MOD LAOFD Intra- Meaning:

AlgoSwi Switch ENODE -001001 Band Indicates whether to enable carrier aggregation (CA).
tch BALGO 01 Carrier The switches are described as follows:
SWITC LAOFD Aggrega
H tion for PdcchOverlapSrchSpcSwitch: Indicates whether CA
-001001 UEs regard the overlapping PDCCH candidates of the
LST 02 Downlin
k 2CC common search space and UE-specific search space,
ENODE
LAOFD in which are transmitted by the primary serving cell
BALGO
-001002 20MHz (PCell), as PDCCH candidates of the common or UE-
SWITC
01 / specific search space. If this switch is On and if a CA
H Inter-
TDLAO UE supports cross-carrier scheduling and is assigned a
Band
FD-001 carrier indicator field (CIF), the CA UE determines
Carrier
002 that the overlapping PDCCH candidates belong to the
Aggrega
LAOFD common search space; otherwise, the CA UE
tion for
-001002 determines that the overlapping PDCCH candidates
Downlin
02 / belong to the UE-specific search space. If this switch
k 2CC
TDLAO is Off, the CA UE always determines that the
in
FD-001 overlapping PDCCH candidates belong to the
20MHz
00102 common search space.
Carrier
LAOFD Aggrega CaCapbFiltSwitch: Indicates how the eNodeB
-070201 tion for performs CA after a CA UE reports the combination
/ Downlin of frequency bands. If the UECapabilityInformation
TDLAO k 2CC message reported by a UE does not contain the IE
FD-070 in supportedBandwidthCombinationSet, the eNodeB
201 40MHz performs CA as follows: If this option is Off, the
eNodeB configures a secondary component carrier
LAOFD Support (SCC) for the UE using the default value of the IE
-070202 of UE supportedBandwidthCombinationSet defined in 3GPP
TDLAO Categor specifications. If this option is On, the eNodeB does
FD-001 y6 not configure an SCC for the UE.
00111 Flexible
PccAnchorSwitch: Indicates whether to enable the
CA
LAOFD anchor function of the primary component carrier
from
-080202 (PCC). This switch is not subject to the setting of
Multiple
LAOFD FreqCfgSwitch of the CaAlgoSwitch parameter. The
Carriers
-080201 anchor function of the PCC is enabled only when this
Inter- switch is On.
LBFD-0 eNodeB
0201805 CA SccBlindCfgSwitch: Indicates whether a secondary
/ based on serving cell (SCell) can be blindly configured. If this
TDLBF Coordin switch is On, the eNodeB configures a candidate
D-00201 ated SCell as an SCell for a CA UE without A4
805 BBU measurements. If this switch is Off, the eNodeB
delivers A4 measurement configurations for
LOFD-0 Intra-
measuring the frequency of a candidate SCell before
0105401 band
configuring the candidate SCell as an SCell for the
/ Carrier
CA UE.
TDLOF Aggrega
D-00105 tion for FreqCfgSwitch: Indicates whether to configure CA
401 Downlin based on frequencies or CA groups. If this switch is

eRAN

nd
k 2CC On, CA can be configured based on frequencies. If

in this switch is Off, CA can be configured based on CA
30MHz groups.
Carrier SccA2RmvSwitch: Indicates whether to deliver A2
Aggrega measurement configurations for measuring a
tion for secondary component carrier (SCC) after the SCC is
Uplink configured. This option is not subject to the setting of
2CC the FreqCfgSwitch option of the CaAlgoSwitch
Inter- parameter. If FreqCfgSwitch is Off and
eNodeB SccBlindCfgSwitch is On, the setting of
CA SccA2RmvSwitch does not take effect. The eNodeB
based on delivers A2 measurement configurations for
relaxed measuring an SCC after the SCC is configured only
backhau when SccA2RmvSwitch is On.
l
CaTrafficTriggerSwitch: Indicates whether to add and
Service remove an SCC based on the traffic volume of a CA
Based UE after the UE accesses the network. This switch is
Inter- not subject to the settings of FreqCfgSwitch. If the
frequenc CarrierMgtSwitch parameter is set to Off and
y CaTrafficTriggerSwitch is On, an added SCC cannot
Handov be removed based on the traffic volume of a CA UE.
er
HoWithSccCfgSwitch: Indicates whether an SCC can
Camp &
be configured for a CA UE during a handover. It is
Handov
recommended that the SccA2RmvSwitch option of the
er Based
CaAlgoSwitch parameter be selected when the
on SPID
HoWithSccCfgSwitch option of the same parameter is
selected. If the SccA2RmvSwitch option is deselected,
UEs cannot report the signals of neighboring cells that
operate on the frequencies of their SCell, affecting
SCell configuration in handovers. This switch is not
subject to the setting of FreqCfgSwitch of the
CaAlgoSwitch parameter. If this switch is On, the
source cell sends SCC information to the target cell
during the handover and the SCC is configured for the
CA UE. If this switch is Off, the source cell does not
send SCC information to the target cell during the
handover.
SccModA6Switch: Indicates whether the eNodeB
delivers event A6 measurement configurations to a
CA UE after configuring an SCC for the UE. The
eNodeB delivers event A6 measurement
configurations to a CA UE after configuring an SCC
for the UE only when the switch is On.
GbrAmbrJudgeSwitch: Indicates whether to check the
GBR or AMBR when an SCell is to be activated for
downlink CA. If this switch is On, the bit rate of the

eRAN

nd
bearer or aggregate bit rate of the CA UE is checked

when an SCell is to be activated. An SCell can be
activated if the bit rate has not reached the GBR or the
aggregate bit rate of the UE has not reached the
AMBR. If this switch is Off, neither the bit rate of the
bearer nor the aggregate bit rate of the CA UE is
checked when an SCell is to be activated.
MtaAlgSwitch: Indicates whether multiple timing
advances (MTAs) are supported in uplink CA
scenarios. This parameter applies only to LTE FDD. If
this switch is On, MTAs are supported. If the reported
UE capabilities indicate that the UE supports MTAs in
the uplink, uplink timing is performed on the UE
based on multiple timing advance groups (TAGs) in
uplink CA scenarios. If the UE does not support
MTAs in the uplink, uplink timing is performed on the
UE based on a single TAG in uplink CA scenarios. If
this switch is Off, MTAs are not supported in uplink
CA scenarios, and uplink timing is performed on UEs
based on a single TAG. You are advised to set this
switch to On in inter-eNodeB CA scenarios and
scenarios where RRUs are installed remotely.
RelaxedBackhaulCaSwitch: Indicates whether to
enable inter-eNodeB downlink CA based on relaxed
backhaul. Inter-eNodeB CA based on relaxed
backhaul is enabled only when this switch is On.
AdpCaSwitch: Indicates whether to allow adaptive
frequency-based CA configuration. If this switch is
On, in frequency-based configuration mode, the
eNodeB can configure SCells in a blind manner based
on preconfigured CA group information. If this switch
is Off, blind SCell configuration is not allowed in
frequency-based CA configuration mode.
CaHoControlSwitch: Indicates whether CA UEs can
be handed over to non-macro cells during unnecessary
intra-RAT handovers. If this switch is On, CA UEs
cannot be handed over to non-macro cells during
unnecessary intra-RAT handovers. If this switch is
Off, CA UEs can be handed over to non-macro cells
during unnecessary intra-RAT handovers.
DistributeCloudbbCaSwitch: Indicates whether to
enable CA based on distributed Cloud BB. CA based
on distributed Cloud BB applies to cells served by the
eNodeB only when this switch is On.
SccSmartCfgSwitch: Indicates whether to enable
smart SCC selection. The eNodeB considers the load

eRAN

nd
status indicators of candidate SCells when configuring

the SCell only when this switch is On.
IdleModePccAnchorSwitch: Indicates whether to

enable the anchor function of the primary component
carrier (PCC) for UEs in idle mode. If this option is
selected, this function is enabled. If this option is
deselected, this function is disabled.
FreqPriBasedHoCaFiltSwitch: Indicates whether the

eNodeB filters out CA UEs when delivering
measurement configuration for frequency-priority-
based handovers. CA UEs are filtered out only if this
option is selected.
CaSccSuspendSwitch: Indicates whether the eNodeB

stops scheduling carrier aggregation (CA) UEs in their
secondary serving cells (SCells) when the channel
quality for the CA UEs is poor. If this option is
selected, the eNodeB stops scheduling CA UEs when
the channel quality for the CA UEs is worse than that
indicated by the SccDeactCqiThd parameter value in
single-codeword transmission. The eNodeB resumes
scheduling CA UEs in their SCells when the channel
quality for the CA UEs is better than that indicated by
the SccDeactCqiThd parameter value plus 2 in single-
codeword transmission.
GUI Value Range: PdcchOverlapSrchSpcS-
witch(PdcchOverlapSrchSpcSwitch),
CaCapbFiltSwitch(CaCapbFiltSwitch),
PccAnchorSwitch(PccAnchorSwitch),
SccBlindCfgSwitch(SccBlindCfgSwitch),
FreqCfgSwitch(FreqCfgSwitch),
SccA2RmvSwitch(SccA2RmvSwitch),
CaTrafficTriggerSwitch(CaTrafficTriggerSwitch),
HoWithSccCfgSwitch(HoWithSccCfgSwitch),
SccModA6Switch(SccModA6Switch),
GbrAmbrJudgeSwitch(GbrAmbrJudgeSwitch),
MtaAlgSwitch(MtaAlgSwitch), RelaxedBackhaul-
CaSwitch(RelaxedBackhaulCaSwitch),
AdpCaSwitch(AdpCaSwitch),
CaHoControlSwitch(CaHoControlSwitch),
DistributeCloudbbCaSwitch(DistributeCloudbbCaS-
witch), SccSmartCfgSwitch(SccSmartCfgSwitch),
IdleModePccAnchorSwitch(IdleModePccAnchorS-
witch), FreqPriBasedHoCaFiltS-
witch(FreqPriBasedHoCaFiltSwitch),
CaSccSuspendSwitch(CaSccSuspendSwitch)
Unit: None

eRAN

nd
Actual Value Range: PdcchOverlapSrchSpcSwitch,

CaCapbFiltSwitch, PccAnchorSwitch,
SccBlindCfgSwitch, FreqCfgSwitch,
SccA2RmvSwitch, CaTrafficTriggerSwitch,
HoWithSccCfgSwitch, SccModA6Switch,
GbrAmbrJudgeSwitch, MtaAlgSwitch,
RelaxedBackhaulCaSwitch, AdpCaSwitch,
CaHoControlSwitch, DistributeCloudbbCaSwitch,
SccSmartCfgSwitch, IdleModePccAnchorSwitch,
FreqPriBasedHoCaFiltSwitch, CaSccSuspendSwitch
Default Value: PdcchOverlapSrchSpcSwitch:On,
CaCapbFiltSwitch:Off, PccAnchorSwitch:Off,
SccBlindCfgSwitch:Off, FreqCfgSwitch:Off,
SccA2RmvSwitch:On, CaTrafficTriggerSwitch:Off,
HoWithSccCfgSwitch:Off, SccModA6Switch:Off,
GbrAmbrJudgeSwitch:On, MtaAlgSwitch:Off,
RelaxedBackhaulCaSwitch:Off, AdpCaSwitch:Off,
CaHoControlSwitch:Off, DistributeCloudbbCaS-
witch:Off, SccSmartCfgSwitch:Off,
IdleModePccAnchorSwitch:Off, FreqPriBasedHoCa-
FiltSwitch:Off, CaSccSuspendSwitch:Off

eRAN

nd
DrxPara LongDr ADD LBFD-0 DRX Meaning: Indicates the length of the long DRX cycle.
Group xCycle DRXPA 02017 / Because of the impact of the SRS bandwidth and TA
RAGRO TDLBF period specified by the TimeAlignmentTimer
UP D-00201 parameter, the actual value of this parameter assigned
MOD 7 to a UE may be less than the configured value. In
DRXPA addition, the configured value will be rounded down
RAGRO to an integral multiple of 10. Therefore, you are
UP advised to configure this parameter to a value that is
an integral multiple of 10. If users hope that the value
LST actually assigned to a UE is equal to or greater than 80
DRXPA ms, set the TimeAlignmentTimer parameter to a value
RAGRO equal to or greater than 10240 ms. If the
UP TimingAdvCmdOptSwitch parameter is set to ON, it
is recommended that the LongDrxCycle parameter be
set to a value smaller than or equal to 320 ms.
Otherwise, the uplink time alignment performance of
UEs is affected. If the TimingAdvCmdOptSwitch
parameter is set to ON, it is recommended that the
TimeAlignmentTimer parameter be set to sf10240. A
smaller value of the TimeAlignmentTimer parameter,
such as sf5120, increases the probability that UEs in
DRX mode become uplink asynchronized. The length
of the long DRX cycle must be smaller than the length
of the PDCP packet discarding timer for the
corresponding QCI. Otherwise, packet loss occurs
during a ping operation or low-traffic service.
GUI Value Range: SF10(10 subframes), SF20(20
subframes), SF32(32 subframes), SF40(40
subframes)
Unit: subframe
Actual Value Range: SF10, SF20, SF32, SF40, SF64,
SF80, SF128, SF160, SF256, SF320, SF512, SF640,
SF1024, SF1280, SF2048, SF2560
Default Value: SF40(40 subframes)

eRAN

nd
RrcCon UeInacti MOD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity
nStateTi veTimer RRCCO 02007 / Connect timer for UEs that are running non-QCI1 services. If
mer NNSTA TDLBF ion the eNodeB detects that a UE has neither received nor
TETIM D-00200 Manage sent data for a duration exceeding the value of this
ER 7 ment parameter, the eNodeB releases the RRC connection
LST for the UE. If this parameter is set to 0, the UE
RRCCO inactivity timer is not used. If the parameter setting is
NNSTA changed, the change applies to UEs that newly access
TETIM the network.
ER GUI Value Range: 0~3600
Unit: s
Default Value: 20
ENodeB VQMAl MOD None None Meaning: Indicates the switch used to enable or
AlgoSwi goSwitc ENODE disable the voice quality monitoring algorithm.
tch h BALGO GUI Value Range:
SWITC VQM_ALGO_SWITCH_OFF(Disable),
H VQM_ALGO_SWITCH_ON(Enable)
LST Unit: None
ENODE
BALGO Actual Value Range: VQM_ALGO_SWITCH_OFF,
SWITC VQM_ALGO_SWITCH_ON
H Default Value:
VQM_ALGO_SWITCH_OFF(Disable)
VQMAl ULDela MOD None None Meaning: Indicates the maximum UL voice packet
go yJitter VQMA delay variation allowed on the Uu interface. If the
LGO actual delay variation of a UL voice packet exceeds
LST this limit, this packet is regarded as lost during the
VQMA evaluation of voice quality indicator (VQI). The delay
LGO variation is measured at the eNodeB PDCP layer.
Unit: ms
Default Value: 100

eRAN

nd
RlcPdcp Discard ADD LBFD-0 Radio Meaning: Indicates the length of the PDCP discard
ParaGro Timer RLCPD 02008 / Bearer timer.
up CPPAR TDLBF Manage GUI Value Range: DiscardTimer_50(50),
AGROU D-00200 ment DiscardTimer_100(100), DiscardTimer_150(150),
P 8 DiscardTimer_300(300), DiscardTimer_500(500),
MOD DiscardTimer_750(750), DiscardTimer_1500(1500),
RLCPD DiscardTimer_Infinity(infinity)
CPPAR
Unit: ms
AGROU
P Actual Value Range: DiscardTimer_50,
DiscardTimer_100, DiscardTimer_150,
LST
RLCPD
CPPAR
DiscardTimer_Infinity
AGROU
P Default Value: DiscardTimer_Infinity(infinity)

eRAN
VoLTE Feature Parameter Description 11 Counters
11 Counters
Table 11-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526726668 L.E- Number of E-RAB Multi-mode: None Radio Bearer

RAB.AttEst.QCI.1 setup attempts GSM: None Management
initiated by UEs for Radio Bearer
services with the UMTS: None
Management
QCI of 1 in a cell LTE:
LBFD-002008
TDLBFD-002008
1526726669 L.E- Number of Multi-mode: None Radio Bearer

RAB.SuccEst.QCI. successful E-RAB GSM: None Management
1 setups initiated by Radio Bearer
UEs for services UMTS: None
Management
with the QCI of 1 in LTE:
a cell LBFD-002008
TDLBFD-002008

RAB.AttEst.QCI.5 setup attempts GSM: None Management
initiated by UEs for Radio Bearer
Management
QCI of 5 in a cell LTE:
LBFD-002008
TDLBFD-002008

RAB.SuccEst.QCI. successful E-RAB GSM: None Management
5 setups initiated by Radio Bearer
Management
a cell LBFD-002008
TDLBFD-002008

eRAN

Description

RAB.AbnormRel.Q abnormal releases GSM: None Management
CI.1 of activated E- Radio Bearer
RABs for services UMTS: None
Management
a cell LBFD-002008
TDLBFD-002008
1526726687 L.E- Number of normal Multi-mode: None Radio Bearer

RAB.NormRel.QCI E-RAB releases for GSM: None Management
.1 services with the Radio Bearer
QCI of 1 in a cell UMTS: None
Management
LTE:
LBFD-002008
TDLBFD-002008

RAB.AbnormRel.Q abnormal releases GSM: None Management
CI.5 of activated E- Radio Bearer
Management
a cell LBFD-002008
TDLBFD-002008

RAB.NormRel.QCI E-RAB releases for GSM: None Management
.5 services with the Radio Bearer
Management
LTE:
LBFD-002008
TDLBFD-002008
1526726776 L.Thrp.bits.UL.QCI Uplink traffic Multi-mode: None Radio Bearer

.1 volume for PDCP GSM: None Management
PDUs of services Radio Bearer
with the QCI of 1 in UMTS: None
Management
a cell LTE:
LBFD-002008 Basic Scheduling
TDLBFD-002008 Basic Scheduling
LBFD-002025
TDLBFD-002025

eRAN

Description
1526726777 L.Thrp.Time.UL.Q Receive duration of Multi-mode: None Radio Bearer

CI.1 uplink PDCP PDUs GSM: None Management
for services with the Radio Bearer
Management
LTE:
LBFD-002025
TDLBFD-002025
1526726803 L.Thrp.bits.DL.QCI Downlink traffic Multi-mode: None Radio Bearer

.1 volume for PDCP GSM: None Management
SDUs of services Radio Bearer
Management
a cell LTE:
LBFD-002025
TDLBFD-002025
1526726804 L.Thrp.Time.DL.Q Transmit duration Multi-mode: None Radio Bearer

CI.1 of downlink PDCP GSM: None Management
SDUs for services Radio Bearer
Management
a cell LTE:
LBFD-002025
TDLBFD-002025
1526726833 L.PDCP.Tx.Disc.Tr Number of Multi-mode: None Radio Bearer

f.SDU.QCI.1 downlink PDCP GSM: None Management
SDUs discarded for Radio Bearer
services carried on UMTS: None
Management
DRBs with a QCI LTE:
of 1 in a cell LBFD-002008 Basic Scheduling
LBFD-002025
TDLBFD-002025

eRAN

Description
1526727412 L.ChMeas.PUSCH. Number of times Multi-mode: None Basic Scheduling

MCS.0 MCS index 0 is GSM: None Modulation: DL/UL
scheduled on the QPSK, DL/UL
PUSCH UMTS: None
16QAM, DL
LTE: 64QAM
LBFD-002025
Basic Scheduling
LBFD-001005
Modulation: DL/UL
TDLBFD-002025 QPSK, DL/UL
TDLBFD-001005 16QAM, DL
64QAM
1526727443 L.ChMeas.PUSCH. Number of times Multi-mode: None Basic Scheduling

MCS.31 MCS index 31 is GSM: None Basic Scheduling
scheduled on the
PUSCH UMTS: None Modulation: DL/UL
QPSK, DL/UL
LTE:
16QAM, DL
LBFD-002025
64QAM
TDLBFD-002025 Modulation: DL/UL
LBFD-001005 QPSK, DL/UL
16QAM, DL
TDLBFD-001005
64QAM
LOFD-001006
UL 64QAM
TDLOFD-001006 UL 64QAM
1526727849 L.Thrp.bits.UL.PL Total traffic volume Multi-mode: None Radio Bearer

MN.QCI.1 of uplink PDCP GSM: None Management
PDUs of QCI-1 RAN Sharing with
services UMTS: None
Common Carrier
LTE:
LBFD-002008 RAN Sharing with
Dedicated Carrier
LOFD-001036
Basic Scheduling
LOFD-001037
Radio Bearer
LBFD-002025 Management
TDLBFD-002008 RAN Sharing with
TDLOFD-001036 Common Carrier
TDLOFD-001037 RAN Sharing with
TDLBFD-002025 Dedicated Carrier
LOFD-070206 Basic Scheduling
Hybrid RAN
Sharing

eRAN

Description
1526727850 L.Thrp.Time.UL.PL Duration for Multi-mode: None Radio Bearer

MN.QCI.1 receiving uplink GSM: None Management
PDCP SDUs of RAN Sharing with
QCI-1 services UMTS: None
Common Carrier
LTE:
Dedicated Carrier
LOFD-001036
Basic Scheduling
LOFD-001037
Radio Bearer
Hybrid RAN
Sharing

RAB.AttEst.PLMN. setup attempts GSM: None Management
QCI.1 initiated by UEs for Radio Bearer
Management
QCI of 1for a LTE:
specific operator in LBFD-002008 RAN Sharing with
a cell Common Carrier
TDLBFD-002008
RAN Sharing with
LOFD-001036 Dedicated Carrier
LOFD-001037 RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

RAB.SuccEst.PLM successful E-RAB GSM: None Management
N.QCI.1 setups initiated by Radio Bearer
Management
with the QCI of 1 LTE:
for a specific LBFD-002008 RAN Sharing with
operator in a cell Common Carrier
TDLBFD-002008
RAN Sharing with
Hybrid RAN
Sharing

RAB.AttEst.PLMN. setup attempts GSM: None Management
QCI.5 initiated by UEs for Radio Bearer
Management
QCI of 5 for a LTE:
specific operator in LBFD-002008 RAN Sharing with
TDLBFD-002008
RAN Sharing with
Hybrid RAN
Sharing

RAB.SuccEst.PLM successful E-RAB GSM: None Management
N.QCI.5 setups initiated by Radio Bearer
Management
TDLBFD-002008
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

RAB.AbnormRel.P abnormal releases GSM: None Management
LMN.QCI.1 of activated E- Radio Bearer
Management
TDLBFD-002008
RAN Sharing with
Hybrid RAN
Sharing

RAB.NormRel.PL E-RAB releases for GSM: None Management
MN.QCI.1 services with the Radio Bearer
QCI of 1 for a UMTS: None
Management
specific operator in LTE:
a cell LBFD-002008 RAN Sharing with
Common Carrier
TDLBFD-002008
RAN Sharing with
Hybrid RAN
Sharing

RAB.AbnormRel.P abnormal releases GSM: None Management
LMN.QCI.5 of activated E- Radio Bearer
Management
TDLBFD-002008
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

RAB.NormRel.PL E-RAB releases for GSM: None Management
MN.QCI.5 services with the Radio Bearer
QCI of 5 for a UMTS: None
Management
a cell LBFD-002008 RAN Sharing with
Common Carrier
TDLBFD-002008
RAN Sharing with
Hybrid RAN
Sharing
1526727889 L.PDCP.Tx.TotRev. Number of Multi-mode: None Radio Bearer

Trf.SDU.QCI.1 downlink PDCP GSM: None Management
SDUs transmitted Radio Bearer
for services carried UMTS: None
Management
on DRBs with a LTE:
QCI of 1 in a cell LBFD-002008 Basic Scheduling
LBFD-002025
TDLBFD-002025
1526727934 L.Traffic.DL.PktUu Number of Multi-mode: None Radio Bearer

Loss.Loss.QCI.1 downlink PDCP GSM: None Management
SDUs discarded for Radio Bearer
Management
of 1 in a cell over LBFD-002008 Basic Scheduling
the Uu interface TDLBFD-002008 Basic Scheduling
LBFD-002025
TDLBFD-002025
1526727935 L.Traffic.DL.PktUu Number of Multi-mode: None Radio Bearer

Loss.Tot.QCI.1 downlink PDCP GSM: None Management
SDUs transmitted Radio Bearer
for services carried UMTS: None
Management
on DRBs with a LTE:
QCI of 1 in a cell LBFD-002008 Basic Scheduling
over the Uu TDLBFD-002008 Basic Scheduling
interface
LBFD-002025
TDLBFD-002025

eRAN

Description
1526727961 L.Traffic.UL.PktLo Number of uplink Multi-mode: None Radio Bearer

ss.Loss.QCI.1 PDCP SDUs GSM: None Management
discarded for Radio Bearer
Management
LBFD-002025
TDLBFD-002025
1526727962 L.Traffic.UL.PktLo Number of Multi-mode: None Radio Bearer

ss.Tot.QCI.1 expected uplink GSM: None Management
PDCP SDUs for Radio Bearer
Management
LBFD-002025
TDLBFD-002025
1526728050 L.Thrp.bits.DL.PL Total traffic volume Multi-mode: None Radio Bearer

MN.QCI.1 of downlink PDCP GSM: None Management
PDUs of QCI-1 RAN Sharing with
services UMTS: None
Common Carrier
LTE:
Dedicated Carrier
LOFD-001036
Basic Scheduling
LOFD-001037
Radio Bearer
Hybrid RAN
Sharing

eRAN

Description
1526728051 L.Thrp.Time.DL.PL Duration for Multi-mode: None Radio Bearer

MN.QCI.1 transmitting GSM: None Management
downlink PDCP RAN Sharing with
SDUs of QCI-1 UMTS: None
Common Carrier
services LTE:
Dedicated Carrier
LOFD-001036
Basic Scheduling
LOFD-001037
Radio Bearer
Hybrid RAN
Sharing
1526728304 L.ChMeas.CCE.UL Number of PDCCH Multi-mode: None Physical Channel

Used CCEs used for GSM: None Management
uplink DCI in a Physical Channel
measurement period UMTS: None
Management
LTE:
LBFD-002003
TDLBFD-002003
1526728305 L.ChMeas.CCE.DL Number of PDCCH Multi-mode: None Physical Channel

Used CCEs used for GSM: None Management
downlink DCI in a Physical Channel
measurement period UMTS: None
Management
LTE:
LBFD-002003
TDLBFD-002003
1526728411 L.Voice.VQI.UL.Ex Number of times Multi-mode: None Performance

cellent.Times uplink voice quality GSM: None Management
is Excellent
UMTS: None
LTE:
LBFD-004008
1526728412 L.Voice.VQI.UL.G Number of times Multi-mode: None Performance

ood.Times uplink voice quality GSM: None Management
is Good
UMTS: None
LTE:
LBFD-004008

eRAN

Description
1526728413 L.Voice.VQI.UL.Ac Number of times Multi-mode: None Performance

cept.Times uplink voice quality GSM: None Management
is Accept
UMTS: None
LTE:
LBFD-004008
1526728414 L.Voice.VQI.UL.Po Number of times Multi-mode: None Performance

or.Times uplink voice quality GSM: None Management
is Poor
UMTS: None
LTE:
LBFD-004008
1526728415 L.Voice.VQI.UL.Ba Number of times Multi-mode: None Performance

d.Times uplink voice quality GSM: None Management
is Bad
UMTS: None
LTE:
LBFD-004008
1526728416 L.Voice.VQI.DL.Ex Number of times Multi-mode: None Performance

cellent.Times downlink voice GSM: None Management
quality is Excellent
UMTS: None
LTE:
LBFD-004008
1526728417 L.Voice.VQI.DL.G Number of times Multi-mode: None Performance

ood.Times downlink voice GSM: None Management
quality is Good
UMTS: None
LTE:
LBFD-004008
1526728418 L.Voice.VQI.DL.Ac Number of times Multi-mode: None Performance

cept.Times downlink voice GSM: None Management
quality is Accept
UMTS: None
LTE:
LBFD-004008
1526728419 L.Voice.VQI.DL.Po Number of times Multi-mode: None Performance

or.Times downlink voice GSM: None Management
quality is Poor
UMTS: None
LTE:
LBFD-004008

eRAN

Description
1526728420 L.Voice.VQI.DL.Ba Number of times Multi-mode: None Performance

d.Times downlink voice GSM: None Management
quality is Bad
UMTS: None
LTE:
LBFD-004008
1526728446 L.Traffic.ActiveUse Number of Multi-mode: None RRC Connection

r.UL.QCI.1 activated UEs with GSM: None Management
the QCI of 1 in the RRC Connection
uplink buffer UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526728456 L.Traffic.ActiveUse Number of Multi-mode: None RRC Connection

r.DL.QCI.1 activated UEs with GSM: None Management
the QCI of 1 in the RRC Connection
downlink buffer UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526728494 L.Sps.UL.SchNum Number of uplink Multi-mode: None VoIP Semi-

semi-persistent GSM: None persistent
scheduling times in Scheduling
a cell UMTS: None
VoIP Semi-
LTE: persistent
LOFD-001016 Scheduling
TDLOFD-001016
1526728495 L.Sps.DL.SchNum Number of Multi-mode: None VoIP Semi-

downlink semi- GSM: None persistent
scheduling times in UMTS: None
VoIP Semi-
a cell LTE: persistent
LOFD-001016 Scheduling
TDLOFD-001016
1526728496 L.Traffic.User.TtiB Average number of Multi-mode: None TTI Bundling

undling.Avg UEs on which TTI GSM: None TTI Bundling
bundling takes
effect in a cell UMTS: None
LTE:
LOFD-001048
TDLOFD-001048

eRAN

Description
1526728562 L.Sps.UL.ErrNum Number of failed Multi-mode: None VoIP Semi-

uplink semi- GSM: None persistent
scheduling UMTS: None
VoIP Semi-
transmissions in a LTE: persistent
cell LOFD-001016 Scheduling
TDLOFD-001016
1526728563 L.Sps.DL.ErrNum Number of failed Multi-mode: None VoIP Semi-

downlink semi- GSM: None persistent
scheduling UMTS: None
VoIP Semi-
transmission in a LTE: persistent
cell LOFD-001016 Scheduling
TDLOFD-001016
1526728911 L.Signal.Num.TtiB Number of Multi-mode: None TTI Bundling

undling.Enter messages sent for GSM: None TTI Bundling
instructing UEs to
enter TTI bundling UMTS: None
mode LTE:
LOFD-001048
TDLOFD-001048
1526728912 L.Signal.Num.TtiB Number of Multi-mode: None TTI Bundling

undling.Exit messages sent for GSM: None TTI Bundling
instructing UEs to
exit TTI bundling UMTS: None
mode LTE:
LOFD-001048
TDLOFD-001048
1526729526 L.HHO.IntraeNB.In Number of intra- Multi-mode: None Coverage Based

traFreq.PrepAttOut. eNodeB intra- GSM: None Intra-frequency
VoIP frequency outgoing Handover
handover attempts UMTS: None
Coverage Based
for UEs performing LTE: Intra-frequency
voice services in a LBFD-00201801 Handover
cell TDLBFD-0020180
1

terFreq.PrepAttOut. eNodeB inter- GSM: None Inter-frequency
Coverage Based
for UEs performing LTE: Inter-frequency
cell TDLBFD-0020180
2

eRAN

Description

terFddTdd.PrepAtt eNodeB inter- GSM: None Inter-frequency
Out.VoIP duplex-mode Handover
outgoing handover UMTS: None
Coverage Based
attempts for UEs LTE: Inter-frequency
performing voice LBFD-00201802 Handover
services in a cell TDLBFD-0020180
2

traFreq.ExecAttOut eNodeB intra- GSM: None Intra-frequency
.VoIP frequency outgoing Handover
handover UMTS: None
Coverage Based
executions for UEs LTE: Intra-frequency
1

terFreq.ExecAttOut eNodeB inter- GSM: None Inter-frequency
handover UMTS: None
Coverage Based
executions for UEs LTE: Inter-frequency
2

terFddTdd.ExecAtt eNodeB inter- GSM: None Inter-frequency
Coverage Based
2
1526729532 L.HHO.IntraeNB.In Number of Multi-mode: None Coverage Based

traFreq.ExecSuccO successful intra- GSM: None Intra-frequency
ut.VoIP eNodeB intra- Handover
frequency outgoing UMTS: None
Coverage Based
handovers for UEs LTE: Intra-frequency
1

eRAN

Description

terFreq.ExecSuccO successful intra- GSM: None Inter-frequency
ut.VoIP eNodeB inter- Handover
Coverage Based
handovers for UEs LTE: Inter-frequency
2

terFddTdd.ExecSuc successful intra- GSM: None Inter-frequency
cOut.VoIP eNodeB inter- Handover
duplex-mode UMTS: None
Coverage Based
outgoing handovers LTE: Inter-frequency
for UEs performing LBFD-00201802 Handover
voice services in a TDLBFD-0020180
cell 2
1526729535 L.HHO.IntereNB.In Number of inter- Multi-mode: None Coverage Based

traFreq.PrepAttOut. eNodeB intra- GSM: None Intra-frequency
Coverage Based
for UEs performing LTE: Intra-frequency
cell TDLBFD-0020180
1

terFreq.PrepAttOut. eNodeB inter- GSM: None Inter-frequency
Coverage Based
for UEs performing LTE: Inter-frequency
cell TDLBFD-0020180
2

terFddTdd.PrepAtt eNodeB inter- GSM: None Inter-frequency
Coverage Based
attempts for UEs LTE: Inter-frequency
2

eRAN

Description

traFreq.ExecAttOut eNodeB intra- GSM: None Intra-frequency
handover UMTS: None
Coverage Based
executions for UEs LTE: Intra-frequency
1

terFreq.ExecAttOut eNodeB inter- GSM: None Inter-frequency
handover UMTS: None
Coverage Based
2

terFddTdd.ExecAtt eNodeB inter- GSM: None Inter-frequency
Coverage Based
2
1526729541 L.HHO.IntereNB.In Number of Multi-mode: None Coverage Based

traFreq.ExecSuccO successful inter- GSM: None Intra-frequency
ut.VoIP eNodeB intra- Handover
Coverage Based
handovers for UEs LTE: Intra-frequency
1

terFreq.ExecSuccO successful inter- GSM: None Inter-frequency
ut.VoIP eNodeB inter- Handover
Coverage Based
handovers for UEs LTE: Inter-frequency
2

eRAN

Description

terFddTdd.ExecSuc successful inter- GSM: None Inter-frequency
cOut.VoIP eNodeB inter- Handover
duplex-mode UMTS: None
Coverage Based
outgoing handovers LTE: Inter-frequency
for UEs performing LBFD-00201802 Handover
voice services in a TDLBFD-0020180
cell 2
1526730601 L.Traffic.ActiveUse Maximum number Multi-mode: None RRC Connection

r.DL.QCI.1.Max of activated UEs GSM: None Management
with the QCI of 1 in RRC Connection
the downlink buffer UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526730611 L.Traffic.ActiveUse Maximum number Multi-mode: None RRC Connection

r.UL.QCI.1.Max of activated UEs GSM: None Management
with the QCI of 1 in RRC Connection
the uplink buffer UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526730883 L.ChMeas.PRB.DL Average number of Multi-mode: None Basic Scheduling

.DrbUsed.Avg.VoIP PRBs used by GSM: None Basic Scheduling
DRBs on the
PDSCH for UMTS: None Adaptive SFN/
downlink VoIP LTE: SDMA
services LBFD-002025
TDLBFD-002025
LOFD-070205
1526730884 L.ChMeas.PRB.UL Average number of Multi-mode: None Basic Scheduling

.DrbUsed.Avg.VoIP PRBs used by GSM: None Basic Scheduling
DRBs on the
PUSCH for uplink UMTS: None Adaptive SFN/
VoIP services LTE: SDMA
LBFD-002025
TDLBFD-002025
LOFD-070205
1526732687 L.Voice.VQI.AMR Number of times Multi-mode: None Performance

WB.UL.Excellent.T uplink voice quality GSM: None Management
imes of AMR-WB
services is UMTS: None
Excellent LTE:
LBFD-004008

eRAN

Description

WB.UL.Good.Time uplink voice quality GSM: None Management
s of AMR-WB
services is Good UMTS: None
LTE:
LBFD-004008

WB.UL.Accept.Ti uplink voice quality GSM: None Management
mes of AMR-WB
services is Accept UMTS: None
LTE:
LBFD-004008

WB.UL.Poor.Times uplink voice quality GSM: None Management
of AMR-WB
services is Poor UMTS: None
LTE:
LBFD-004008

WB.UL.Bad.Times uplink voice quality GSM: None Management
of AMR-WB
services is Bad UMTS: None
LTE:
LBFD-004008

WB.DL.Excellent.T downlink voice GSM: None Management
imes quality of AMR-
WB services is UMTS: None
Excellent LTE:
LBFD-004008

WB.DL.Good.Time downlink voice GSM: None Management
s quality of AMR-
Good LTE:
LBFD-004008

WB.DL.Accept.Ti downlink voice GSM: None Management
mes quality of AMR-
Accept LTE:
LBFD-004008

eRAN

Description

WB.DL.Poor.Times downlink voice GSM: None Management
quality of AMR-
WB services is Poor UMTS: None
LTE:
LBFD-004008

WB.DL.Bad.Times downlink voice GSM: None Management
quality of AMR-
WB services is Bad UMTS: None
LTE:
LBFD-004008
1526732721 L.Traffic.User.VoIP. Average number of Multi-mode: None RRC Connection

Avg VoIP UEs in a cell GSM: None Management
UMTS: None RRC Connection
Management
LTE:
LBFD-002007
TDLBFD-002007
1526732722 L.Traffic.User.VoIP. Maximum number Multi-mode: None RRC Connection

Max of VoIP UEs in a GSM: None Management
cell RRC Connection
UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526732890 L.Voice.NormRel.U Number of normal Multi-mode: None Performance

L.LowQuality voice call releases GSM: None Management
in the cell (poor
uplink voice UMTS: None
quality) LTE:
LBFD-004008
1526732891 L.Voice.NormRel.D Number of normal Multi-mode: None Performance

L.LowQuality voice call releases GSM: None Management
in the cell (poor
downlink voice UMTS: None
quality) LTE:
LBFD-004008
1526732892 L.Voice.UL.Silent. Number of times Multi-mode: None Performance

Num that a UE GSM: None Management
experiences uplink
voice mute in the UMTS: None
cell LTE:
LBFD-004008

eRAN

Description
1526732893 L.Voice.DL.Silent. Number of times Multi-mode: None Performance

Num that a UE GSM: None Management
experiences
downlink voice UMTS: None
mute in the cell LTE:
LBFD-004008
1526736660 L.Voice.VQI.UL.Ex Number of times Multi-mode: None Performance

cellent.Times.PLM uplink voice quality GSM: None Management
N is Excellent for a RAN Sharing with
specific operator in UMTS: None
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
TDLOFD-001036 Dedicated Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
1526736661 L.Voice.VQI.UL.G Number of times Multi-mode: None Performance

ood.Times.PLMN uplink voice quality GSM: None Management
is Good for a RAN Sharing with
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
1526736662 L.Voice.VQI.UL.Ac Number of times Multi-mode: None Performance

cept.Times.PLMN uplink voice quality GSM: None Management
is Accept for a RAN Sharing with
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

eRAN

Description
1526736663 L.Voice.VQI.UL.Po Number of times Multi-mode: None Performance

or.Times.PLMN uplink voice quality GSM: None Management
is Poor for a RAN Sharing with
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
1526736664 L.Voice.VQI.UL.Ba Number of times Multi-mode: None Performance

d.Times.PLMN uplink voice quality GSM: None Management
is Bad for a specific RAN Sharing with
operator in a cell UMTS: None
Common Carrier
LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
1526736665 L.Voice.VQI.DL.Ex Number of times Multi-mode: None Performance

cellent.Times.PLM downlink voice GSM: None Management
N quality is Excellent RAN Sharing with
for a specific UMTS: None
Common Carrier
operator in a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

eRAN

Description
1526736666 L.Voice.VQI.DL.G Number of times Multi-mode: None Performance

ood.Times.PLMN downlink voice GSM: None Management
quality is Good for RAN Sharing with
a specific operator UMTS: None
Common Carrier
in a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
1526736667 L.Voice.VQI.DL.Ac Number of times Multi-mode: None Performance

cept.Times.PLMN downlink voice GSM: None Management
quality is Accept RAN Sharing with
for a specific UMTS: None
Common Carrier
operator in a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
1526736668 L.Voice.VQI.DL.Po Number of times Multi-mode: None Performance

or.Times.PLMN downlink voice GSM: None Management
quality is Poor for a RAN Sharing with
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

eRAN

Description
1526736669 L.Voice.VQI.DL.Ba Number of times Multi-mode: None Performance

d.Times.PLMN downlink voice GSM: None Management
quality is Bad for a RAN Sharing with
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

WB.UL.Excellent.T uplink voice quality GSM: None Management
imes.PLMN of AMR-WB RAN Sharing with
services is UMTS: None
Common Carrier
Excellent for a LTE:
specific operator in RAN Sharing with
LBFD-004008
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

WB.UL.Good.Time uplink voice quality GSM: None Management
s.PLMN of AMR-WB RAN Sharing with
services is Good for UMTS: None
Common Carrier
a specific operator LTE:
in a cell RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

eRAN

Description

WB.UL.Accept.Ti uplink voice quality GSM: None Management
mes.PLMN of AMR-WB RAN Sharing with
services is Accept UMTS: None
Common Carrier
for a specific LTE:
operator in a cell RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

WB.UL.Poor.Times uplink voice quality GSM: None Management
.PLMN of AMR-WB RAN Sharing with
services is Poor for UMTS: None
Common Carrier
a specific operator LTE:
in a cell RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

WB.UL.Bad.Times. uplink voice quality GSM: None Management
PLMN of AMR-WB RAN Sharing with
services is Bad for a UMTS: None
Common Carrier
a cell RAN Sharing with
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

eRAN

Description

WB.DL.Excellent.T downlink voice GSM: None Management
imes.PLMN quality of AMR- RAN Sharing with
Common Carrier
Excellent for a LTE:
LBFD-004008
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

WB.DL.Good.Time downlink voice GSM: None Management
s.PLMN quality of AMR- RAN Sharing with
Common Carrier
Good for a specific LTE:
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

WB.DL.Accept.Ti downlink voice GSM: None Management
mes.PLMN quality of AMR- RAN Sharing with
Common Carrier
Accept for a LTE:
LBFD-004008
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

eRAN

Description

WB.DL.Poor.Times downlink voice GSM: None Management
.PLMN quality of AMR- RAN Sharing with
WB services is Poor UMTS: None
Common Carrier
for a specific LTE:
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing

WB.DL.Bad.Times. downlink voice GSM: None Management
PLMN quality of AMR- RAN Sharing with
WB services is Bad UMTS: None
Common Carrier
for a specific LTE:
LBFD-004008
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
1526736680 L.PDCP.Tx.Disc.Tr Number of Multi-mode: None Radio Bearer

f.SDU.PLMN.QCI. downlink traffic GSM: None Management
1 SDUs discarded by Radio Bearer
the PDCP layer for UMTS: None
Management
services with a QCI LTE:
of 1 for a specific LBFD-002008 Basic Scheduling
operator in a cell TDLBFD-002008 Basic Scheduling
Common Carrier
TDLBFD-002025
RAN Sharing with
LOFD-001036 Common Carrier
Hybrid RAN
Sharing

eRAN

Description
1526736682 L.PDCP.Tx.TotRev. Number of Multi-mode: None Radio Bearer

Trf.SDU.PLMN.Q transmitted GSM: None Management
CI.1 downlink traffic Radio Bearer
PDCP SDUs for UMTS: None
Management
services with a QCI LTE:
of 1 for a specific LBFD-002008 Basic Scheduling
operator in a cell TDLBFD-002008 Basic Scheduling
Common Carrier
TDLBFD-002025
RAN Sharing with
Hybrid RAN
Sharing
1526736684 L.Traffic.UL.PktLo Total number of Multi-mode: None Radio Bearer

ss.Loss.PLMN.QCI discarded uplink GSM: None Management
.1 PDCP SDUs for Radio Bearer
traffic services with UMTS: None
Management
a QCI of 1 for a LTE:
specific operator in LBFD-002008 Basic Scheduling
a cell TDLBFD-002008 Basic Scheduling
Common Carrier
TDLBFD-002025
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description
1526736686 L.Traffic.UL.PktLo Total number of Multi-mode: None Radio Bearer

ss.Tot.PLMN.QCI.1 expected uplink GSM: None Management
data packets for Radio Bearer
DRB services with UMTS: None
Management
Common Carrier
TDLBFD-002025
RAN Sharing with
Hybrid RAN
Sharing
1526736692 L.Traffic.User.VoIP. Average number of Multi-mode: None RRC Connection

Avg.PLMN VoIP UEs of a GSM: None Management
specific operator in RRC Connection
a cell UMTS: None
Management
LTE:
Common Carrier
TDLBFD-002007
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description
1526736693 L.Traffic.User.VoIP. Maximum number Multi-mode: None RRC Connection

Max.PLMN of VoIP UEs of a GSM: None Management
specific operator in RRC Connection
a cell UMTS: None
Management
LTE:
Common Carrier
TDLBFD-002007
RAN Sharing with
Hybrid RAN
Sharing
1526736735 L.ChMeas.CCE.UL Number of PDCCH Multi-mode: None Physical Channel

Used.VoIP CCEs used for GSM: None Management
uplink VoIP Physical Channel
services UMTS: None
Management
LTE:
LBFD-002003
TDLBFD-002003
1526736736 L.ChMeas.CCE.DL Number of PDCCH Multi-mode: None Physical Channel

Used.VoIP CCEs used for GSM: None Management
downlink VoIP Physical Channel
services UMTS: None
Management
LTE:
LBFD-002003
TDLBFD-002003

eRAN

Description
1526736737 L.Traffic.DL.PktUu Total number of Multi-mode: None Radio Bearer

Loss.Loss.PLMN.Q discarded downlink GSM: None Management
CI.1 PDCP SDUs for Radio Bearer
traffic services with UMTS: None
Management
Common Carrier
TDLBFD-002025
RAN Sharing with
Hybrid RAN
Sharing
1526736739 L.Traffic.DL.PktUu Total number of Multi-mode: None Radio Bearer

Loss.Tot.PLMN.QC expected downlink GSM: None Management
I.1 data packets for Radio Bearer
DRB services with UMTS: None
Management
Common Carrier
TDLBFD-002025
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description
1526737724 L.Traffic.UL.SCH. Number of QCI-1 Multi-mode: None Transport Channel

QPSK.TB.QCI.1 Service TBs GSM: None Management
initially transmitted Modulation: DL/UL
on the uplink SCH UMTS: None
QPSK, DL/UL
in QPSK LTE: 16QAM, DL
modulation mode LBFD-002002 64QAM
LBFD-001005 Transport Channel
TDLBFD-002002 Management
QPSK, DL/UL
16QAM, DL
64QAM

16QAM.TB.QCI.1 Service TBs GSM: None Management
initially transmitted Modulation: DL/UL
QPSK, DL/UL
in 16QAM LTE: 16QAM, DL
modulation mode LBFD-002002 64QAM
LBFD-001005 Transport Channel
TDLBFD-002002 Management
QPSK, DL/UL
16QAM, DL
64QAM

64QAM.TB.QCI.1 Service TBs GSM: None Management
initially transmitted UL 64QAM
in 64QAM LTE: Transport Channel
modulation mode LBFD-002002 Management
LOFD-001006 UL 64QAM
TDLBFD-002002
TDLOFD-001006

QPSK.ErrTB.Ibler. Service TBs with GSM: None Management
QCI.1 initial transmission Transport Channel
failures on the UMTS: None
Management
uplink SCH in LTE:
QPSK modulation LBFD-002002
mode TDLBFD-002002

eRAN

Description

16QAM.ErrTB.Ible Service TBs with GSM: None Management
r.QCI.1 initial transmission Transport Channel
Management
uplink SCH in LTE:
16QAM modulation LBFD-002002
mode TDLBFD-002002

64QAM.ErrTB.Ible Service TBs with GSM: None Management
r.QCI.1 initial transmission Transport Channel
Management
uplink SCH in LTE:
64QAM modulation LBFD-002002
mode TDLBFD-002002

eRAN
VoLTE Feature Parameter Description 12 Glossary
12 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
VoLTE Feature Parameter Description 13 Reference Documents
13 Reference Documents
1. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
2. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC)"
3. 3GPP TS 23.203, "Policy and charging control architecture"
4. 3GPP TS 36.814, "Further Advancements for E-UTRA Physical Layer Aspects"
5. 3GPP TS 36.321, "Medium Access Control (MAC) protocol specification"
6. ITU-T G.107, "The E-model: a computational model for use in transmission planning"
7. ROHC Feature Parameter Description
8. Scheduling Feature Parameter Description
9. DRX and Signaling Control Feature Parameter Description
10. Admission and Congestion Control Feature Parameter Description
11. Power Control Feature Parameter Description
12. Intra-RAT Mobility Management in Connected Mode Feature Parameter Description
13. Inter-RAT Mobility Management in Connected Mode Feature Parameter Description
14. QoS Management Feature Parameter Description


Volteeran8 161124091619

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Volteeran8 161124091619

Diunggah oleh

Hak Cipta:

Format Tersedia

eRAN

VoLTE Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2015-06-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

3 Basic VoLTE Functions...............................................................................................................14

4 Enhanced VoLTE Features......................................................................................................... 28

Issue 03 (2015-06-30) Huawei Proprietary and Confidential ii

4.1.1.2 Power Control in Semi-Persistent Scheduling........................................................................................................32

5 Special Processing by Other Features......................................................................................48

8 Voice Service Performance Evaluation................................................................................... 64

Issue 03 (2015-06-30) Huawei Proprietary and Confidential iii

8.2.2 Objective Evaluation................................................................................................................................................. 65

Issue 03 (2015-06-30) Huawei Proprietary and Confidential iv

9.4.2 Required Information.............................................................................................................................................. 101

Issue 03 (2015-06-30) Huawei Proprietary and Confidential v

9.6.6 Troubleshooting....................................................................................................................................................... 123

Issue 03 (2015-06-30) Huawei Proprietary and Confidential vi

1 About This Document

eNodeB Type Model

Macro 3900 series eNodeB

Micro base BTS3202E

LampSite DBS3900 LampSite

Issue 03 (2015-06-30) Huawei Proprietary and Confidential 1

1.2 Intended Audience

1.3 Change History

Change Change Description Parameter Affected

Feature None None Macro, micro,

Editorial Revised the following sections: None -

Issue 03 (2015-06-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Affected

Feature Changed the optional feature Voice- None Macro, micro,

Editorial Revised the following sections: None -

Change Change Description Parameter Affected

Feature Modified the LOFD-081229 Voice Added the Macro, micro,

Editorial Added network impact descriptions. None -

eRAN8.1 Draft A (2015-01-15)

Issue 03 (2015-06-30) Huawei Proprietary and Confidential 3

Change Change Description Parameter Affected

Feature Modified the voice quality Added the Macro, micro,

Added policy control for Added the Macro, micro,

Added the descriptions of the None Macro, micro,

Modified the relationship between None Macro, micro,

Issue 03 (2015-06-30) Huawei Proprietary and Confidential 4

Change Change Description Parameter Affected

Modified the functions of TTI Added the Macro, micro,

Added LOFD-081229 Voice l Added the Macro, micro,

Issue 03 (2015-06-30) Huawei Proprietary and Confidential 5

Change Change Description Parameter Affected

Added LBFD-081104 UL Added the Macro, micro,

Added LOFD-081230 Voice- Added the Macro, micro,

Editorial Modified the document structure to None -

Added 8.2.2 Objective Evaluation. None -

Added counters to measure handover None -

Added 4.3.1 Voice Characteristic None -

1.4 Differences Between eNodeB Types

Feature ID Feature Name Suppor Supported Supported by

LOFD-001016 VoIP Semi-persistent Yes Yes Yes

LOFD-001048 TTI Bundling Yes Yes Yes

Issue 03 (2015-06-30) Huawei Proprietary and Confidential 6

Feature ID Feature Name Suppor Supported Supported by