Vo lte(eran8.1 03)

VoLTE Feature ParameterDescription

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 writtenconsent 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 respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 orrepresentations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: support@huawei.com

Contents

1 About This Document.................................................................................................................. 11.1 Scope.............................................................................................................................................................................. 11.2 Intended Audience..........................................................................................................................................................21.3 Change History............................................................................................................................................................... 21.4 Differences Between eNodeB Types.............................................................................................................................. 6

2 Overview......................................................................................................................................... 82.1 Background.....................................................................................................................................................................82.2 Introduction.................................................................................................................................................................... 92.3 Benefits.........................................................................................................................................................................102.4 Architecture.................................................................................................................................................................. 10

3 Basic VoLTE Functions...............................................................................................................143.1 Speech Codec Scheme and Traffic Model....................................................................................................................153.2 VoLTE Voice Policy Selection......................................................................................................................................163.2.1 Common Scenarios....................................................................................................................................................163.2.1.1 General Principles for Voice Policy Selection........................................................................................................163.2.1.2 VoLTE Mobility Capability Decision..................................................................................................................... 183.2.2 VoLTE-Prohibited Scenario.......................................................................................................................................193.3 Radio Bearer Management........................................................................................................................................... 213.3.1 Radio Bearer Setup....................................................................................................................................................213.3.2 Radio Bearer QoS Management................................................................................................................................ 233.4 Admission and Congestion Control..............................................................................................................................243.4.1 Overview................................................................................................................................................................... 243.4.2 Load Monitoring........................................................................................................................................................243.4.3 Admission Control.....................................................................................................................................................253.4.4 Congestion Control....................................................................................................................................................253.5 Dynamic Scheduling and Power Control..................................................................................................................... 263.5.1 Dynamic Scheduling..................................................................................................................................................263.5.2 Power Control in Dynamic Scheduling..................................................................................................................... 27

4 Enhanced VoLTE Features.........................................................................................................284.1 Capacity Enhancement................................................................................................................................................. 294.1.1 Semi-Persistent Scheduling and Power Control........................................................................................................294.1.1.1 Semi-Persistent Scheduling.................................................................................................................................... 29

eRANVoLTE Feature Parameter Description Contents

4.1.1.2 Power Control in Semi-Persistent Scheduling........................................................................................................324.1.2 ROHC........................................................................................................................................................................ 334.2 Coverage Improvement................................................................................................................................................ 344.2.1 TTI Bundling............................................................................................................................................................. 344.2.1.1 Overview................................................................................................................................................................ 344.2.1.2 Principles................................................................................................................................................................ 344.2.2 ROHC........................................................................................................................................................................ 364.2.3 Uplink RLC Segmentation Enhancement..................................................................................................................374.3 Quality Improvement....................................................................................................................................................384.3.1 Voice Characteristic Awareness Scheduling..............................................................................................................384.3.2 Uplink Compensation Scheduling............................................................................................................................. 394.3.3 Voice-Specific AMC..................................................................................................................................................414.4 Power Saving................................................................................................................................................................414.5 Mobility Management.................................................................................................................................................. 424.5.1 Overview................................................................................................................................................................... 424.5.2 Intra-Frequency Handover.........................................................................................................................................434.5.3 Inter-Frequency Handover.........................................................................................................................................434.5.4 Inter-RAT Handover.................................................................................................................................................. 454.5.4.1 Handover Type........................................................................................................................................................454.5.4.2 Handover Mode...................................................................................................................................................... 47

5 Special Processing by Other Features......................................................................................48

6 Related Features...........................................................................................................................516.1 LOFD-001016 VoIP Semi-persistent Scheduling.........................................................................................................526.2 LOFD-001048 TTI Bundling....................................................................................................................................... 536.3 Uplink RLC Segmentation Enhancement.....................................................................................................................546.4 LOFD-081229 Voice Characteristic Awareness Scheduling........................................................................................ 546.5 LBFD-081104 UL Compensation Scheduling............................................................................................................. 556.6 LBFD-081105 Voice-Specific AMC............................................................................................................................ 556.7 Other Features...............................................................................................................................................................55

7 Network Impact........................................................................................................................... 587.1 LOFD-001016 VoIP Semi-persistent Scheduling.........................................................................................................597.2 LOFD-001048 TTI Bundling....................................................................................................................................... 597.3 Uplink RLC Segmentation Enhancement.....................................................................................................................607.4 LOFD-081229 Voice Characteristic Awareness Scheduling........................................................................................ 607.5 LBFD-081104 UL Compensation Scheduling............................................................................................................. 617.6 LBFD-081105 Voice-Specific AMC............................................................................................................................ 617.7 Other Features...............................................................................................................................................................62

8 Voice Service Performance Evaluation................................................................................... 648.1 QoS Requirements........................................................................................................................................................648.2 Quality Evaluation........................................................................................................................................................648.2.1 Subjective Evaluation................................................................................................................................................ 64

8.2.2 Objective Evaluation................................................................................................................................................. 658.2.3 Measurement-based Evaluation.................................................................................................................................658.3 Capacity Evaluation......................................................................................................................................................678.4 Performance Evaluation............................................................................................................................................... 68

9 Engineering Guidelines............................................................................................................. 699.1 Overview...................................................................................................................................................................... 699.2 Basic Functions.............................................................................................................................................................709.2.1 When to Use Basic Functions....................................................................................................................................709.2.2 Required Information................................................................................................................................................ 719.2.3 Deployment............................................................................................................................................................... 719.2.3.1 Requirements.......................................................................................................................................................... 719.2.3.2 Data Preparation..................................................................................................................................................... 719.2.3.3 Precautions..............................................................................................................................................................739.2.3.4 Hardware Adjustment.............................................................................................................................................739.2.3.5 Initial Configuration............................................................................................................................................... 739.2.3.6 Activation Observation...........................................................................................................................................769.2.3.7 Reconfiguration...................................................................................................................................................... 789.2.3.8 Deactivation............................................................................................................................................................789.2.4 Performance Monitoring............................................................................................................................................799.2.4.1 Voice KPIs.............................................................................................................................................................. 799.2.4.2 Voice QoS............................................................................................................................................................... 839.2.4.3 Voice Quality.......................................................................................................................................................... 849.2.4.4 Voice Capacity........................................................................................................................................................ 879.2.5 Parameter Optimization.............................................................................................................................................899.2.6 Troubleshooting......................................................................................................................................................... 909.3 Semi-Persistent Scheduling.......................................................................................................................................... 909.3.1 When to Use Semi-Persistent Scheduling and Deploy Power Control..................................................................... 909.3.2 Required Information................................................................................................................................................ 919.3.3 Deployment of Semi-Persistent Scheduling.............................................................................................................. 919.3.3.1 Requirements.......................................................................................................................................................... 919.3.3.2 Data Preparation..................................................................................................................................................... 929.3.3.3 Precautions..............................................................................................................................................................939.3.3.4 Hardware Adjustment.............................................................................................................................................939.3.3.5 Initial Configuration............................................................................................................................................... 939.3.3.6 Activation Observation...........................................................................................................................................969.3.3.7 Reconfiguration...................................................................................................................................................... 999.3.3.8 Deactivation............................................................................................................................................................999.3.4 Performance Monitoring..........................................................................................................................................1009.3.5 Parameter Optimization...........................................................................................................................................1009.3.6 Troubleshooting....................................................................................................................................................... 1019.4 TTI Bundling.............................................................................................................................................................. 1019.4.1 When to Deploy TTI Bundling................................................................................................................................101

9.4.2 Required Information.............................................................................................................................................. 1019.4.3 Deployment of TTI Bundling.................................................................................................................................. 1019.4.3.1 Requirements........................................................................................................................................................ 1019.4.3.2 Data Preparation................................................................................................................................................... 1029.4.3.3 Precautions............................................................................................................................................................1049.4.3.4 Hardware Adjustment...........................................................................................................................................1049.4.3.5 Initial Configuration............................................................................................................................................. 1049.4.3.6 Activation Observation.........................................................................................................................................1069.4.3.7 Reconfiguration.................................................................................................................................................... 1089.4.3.8 Deactivation..........................................................................................................................................................1089.4.4 Performance Monitoring..........................................................................................................................................1099.4.5 Parameter Optimization...........................................................................................................................................1099.4.6 Troubleshooting....................................................................................................................................................... 1099.5 UL RLC Segmentation Enhancement........................................................................................................................ 1099.5.1 When to Use Uplink RLC Segmentation Enhancement..........................................................................................1109.5.2 Required Information...............................................................................................................................................1109.5.3 Deployment..............................................................................................................................................................1109.5.3.1 Requirements........................................................................................................................................................ 1109.5.3.2 Data Preparation................................................................................................................................................... 1109.5.3.3 Precautions............................................................................................................................................................1119.5.3.4 Hardware Adjustment........................................................................................................................................... 1119.5.3.5 Initial Configuration..............................................................................................................................................1119.5.3.6 Activation Observation......................................................................................................................................... 1139.5.3.7 Reconfiguration.................................................................................................................................................... 1149.5.3.8 Deactivation.......................................................................................................................................................... 1159.5.4 Performance Monitoring..........................................................................................................................................1159.5.5 Parameter Optimization........................................................................................................................................... 1169.5.6 Troubleshooting....................................................................................................................................................... 1169.6 Voice Characteristic Awareness Scheduling............................................................................................................... 1169.6.1 When to Use Voice Characteristic Awareness Scheduling...................................................................................... 1169.6.2 Required Information...............................................................................................................................................1169.6.3 Deployment..............................................................................................................................................................1169.6.3.1 Requirements........................................................................................................................................................ 1169.6.3.2 Data Preparation................................................................................................................................................... 1169.6.3.3 Precautions............................................................................................................................................................1189.6.3.4 Hardware Adjustment........................................................................................................................................... 1189.6.3.5 Initial Configuration............................................................................................................................................. 1189.6.3.6 Activation Observation.........................................................................................................................................1219.6.3.7 Reconfiguration.................................................................................................................................................... 1219.6.3.8 Deactivation..........................................................................................................................................................1219.6.4 Performance Monitoring..........................................................................................................................................1229.6.5 Parameter Optimization...........................................................................................................................................123

9.6.6 Troubleshooting....................................................................................................................................................... 1239.7 Uplink Compensation Scheduling.............................................................................................................................. 1239.7.1 When to Use Uplink Compensation Scheduling..................................................................................................... 1239.7.2 Required Information.............................................................................................................................................. 1239.7.3 Deployment............................................................................................................................................................. 1239.7.3.1 Requirements........................................................................................................................................................ 1239.7.3.2 Data Preparation................................................................................................................................................... 1239.7.3.3 Precautions............................................................................................................................................................1249.7.3.4 Hardware Adjustment...........................................................................................................................................1249.7.3.5 Initial Configuration............................................................................................................................................. 1259.7.3.6 Activation Observation.........................................................................................................................................1279.7.3.7 Reconfiguration.................................................................................................................................................... 1279.7.3.8 Deactivation..........................................................................................................................................................1289.7.4 Performance Monitoring..........................................................................................................................................1289.7.5 Parameter Optimization...........................................................................................................................................1299.7.6 Troubleshooting....................................................................................................................................................... 1299.8 Voice-Specific AMC...................................................................................................................................................1299.8.1 When to Use Voice-Specific AMC..........................................................................................................................1299.8.2 Required Information.............................................................................................................................................. 1299.8.3 Deployment............................................................................................................................................................. 1299.8.3.1 Requirements........................................................................................................................................................ 1299.8.3.2 Data Preparation................................................................................................................................................... 1299.8.3.3 Precautions............................................................................................................................................................1309.8.3.4 Hardware Adjustment...........................................................................................................................................1309.8.3.5 Initial Configuration............................................................................................................................................. 1309.8.3.6 Activation Observation.........................................................................................................................................1329.8.3.7 Reconfiguration.................................................................................................................................................... 1349.8.3.8 Deactivation..........................................................................................................................................................1349.8.4 Performance Monitoring..........................................................................................................................................1349.8.5 Parameter Optimization...........................................................................................................................................1359.8.6 Troubleshooting....................................................................................................................................................... 135

10 Parameters.................................................................................................................................136

11 Counters.................................................................................................................................... 215

12 Glossary.....................................................................................................................................247

13 Reference Documents............................................................................................................. 248

1 About This Document

1.1 ScopeThis document describes Voice over LTE (VoLTE), including its technical principles, relatedfeatures, network impact, and engineering guidelines. VoLTE is based on IP multimediasubsystem (IMS).

This document covers the following features:

l LOFD-001016 VoIP Semi-persistent Schedulingl LOFD-001048 TTI Bundlingl LOFD-081229 Voice Characteristic Awareness Schedulingl LBFD-081104 UL Compensation Schedulingl LBFD-081105 Voice-Specific AMC

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro basestation

BTS3202E

LampSite DBS3900 LampSite

Any managed objects (MOs), parameters, alarms, or counters described herein correspond tothe software release delivered with this document. Any future updates will be described in theproduct 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.

eRANVoLTE Feature Parameter Description 1 About This Document

1.2 Intended AudienceThis document is intended for personnel who:

l Need to understand the features described hereinl Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes:

l Feature changeChanges in features and parameters of a specified version as well as the affected entities

l Editorial changeChanges in wording or addition of information and any related parameters affected byeditorial changes. Editorial change does not specify the affected entities.

eRAN8.1 03 (2015-06-30)This issue includes the following changes.

ChangeType

Change Description ParameterChange

AffectedEntity

Featurechange

None None Macro, micro,and LampSiteeNodeBs

Editorialchange

Revised the following sections:4.1.1 Semi-Persistent Schedulingand Power Control4.3.1 Voice CharacteristicAwareness Scheduling4.3.2 Uplink CompensationScheduling

None -

eRAN8.1 02 (2015-04-30)This issue includes the following changes.

ChangeType

AffectedEntity

Featurechange

Changed the optional feature Voice-Specific AMC to a basic feature, andchanged the feature ID fromLOFD-081230 to LBFD-081105.

None Macro, micro,and LampSiteeNodeBs

Editorialchange

Revised the following sections:3.2.1.2 VoLTE Mobility CapabilityDecision3.2.2 VoLTE-Prohibited Scenario9.2.3.1 Requirements9.2.6 Troubleshooting

None -

eRAN8.1 01 (2015-03-23)

This issue includes the following changes.

ChangeType

AffectedEntity

Featurechange

Modified the LOFD-081229 VoiceCharacteristic Awareness Schedulingfeature to add independentconfigurations for the UE inactivitytimer for voice services. For details,see the following sections:2.4 Architecture4.3.1 Voice CharacteristicAwareness Scheduling7.4 LOFD-081229 VoiceCharacteristic AwarenessScheduling

Added thefollowingparameter:CELLALGOSWITCH.UEInactiveTimerQCI1Switch

Macro, micro,and LampSiteeNodeBs

Editorialchange

Added network impact descriptions.For details, see the followingsections:7.1 LOFD-001016 VoIP Semi-persistent Scheduling7.2 LOFD-001048 TTI Bundling

None -

eRAN8.1 Draft A (2015-01-15)

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

ChangeType

AffectedEntity

Featurechange

Modified the voice qualitymonitoring mechanism as follows:l The voice quality threshold

becomes configurable.l The downlink voice quality

evaluation is changed from E-Model to VQI-Model.

For details, see 8.2.3 Measurement-based Evaluation.

Added thefollowingparameters:l VQMAlgo.

VqiExcellentThd

l VQMAlgo.VqiPoorThd

l VQMAlgo.VqiGoodThd

l VQMAlgo.VqiBadThd

Added policy control formeasurements (such as ANRmeasurement) by UEs performingvoice services.For details, see 5 Special Processingby Other Features.

Added theGlobalProcSwitch.VoipWithGapModeparameter.

Added the descriptions of therelationship between LOFD-001016VoIP Semi-persistent Scheduling andLAOFD-0010014 DL 2x2 MIMObased on TM9. For details, see 4.1.1Semi-Persistent Scheduling andPower Control.

Modified the relationship betweenLOFD-001048 TTI Bundling andLAOFD-001001 LTE-AIntroduction. For details, see 4.2.1TTI Bundling.

ChangeType

AffectedEntity

Modified the functions of TTIbundling:l Enabled the configuration of

applicable services of TTIbundling. The applicable servicesinclude VoLTE or a combinationof VoLTE and data.

l Added five key parameters toTTI bundling.

For details, see 4.2.1 TTI Bundling.

Added thefollowingparameter:l CellAlgoSw

itch.TtiBundlingTriggerStrategy

l CellAlgoSwitch.StatisticNumThdForTtibTrig

l CellAlgoSwitch.StatisticNumThdForTtibExit

l CellAlgoSwitch.HystToExitTtiBundling

l CellAlgoSwitch.TtiBundlingRlcMaxSegNum

l CellAlgoSwitch.TtiBundlingHarqMaxTxNum

Added LOFD-081229 VoiceCharacteristic AwarenessScheduling. For details, see 4.3.1Voice Characteristic AwarenessScheduling and 9.6 VoiceCharacteristic AwarenessScheduling.

l Added theCellAlgoSwitch.UlDelaySchStrategy parameter.

l Added theUlVoLTEDataSizeEstSwitch optionto theCellAlgoSwitch.UlEnhencedVoipSchSwparameter.

ChangeType

AffectedEntity

Added LBFD-081104 ULCompensation Scheduling. Fordetails, see 4.3.2 UplinkCompensation Scheduling and 9.7Uplink Compensation Scheduling.

Added theUlVoipSchOptSwitch optionto theCellAlgoSwitch.UlEnhencedVoipSchSwparameter.

Added LOFD-081230 Voice-Specific AMC. For details, see 4.3.3Voice-Specific AMC and 9.8 Voice-Specific AMC.

Added theCellAlgoSwitch.SinrAdjTargetIblerforVoLTEparameter.

Editorialchange

Modified the document structure toenhance readability.

None -

Added 8.2.2 Objective Evaluation. None -

Added counters to measure handoversuccess rates for VoLTE services.For details, see 9.2.4.1 Voice KPIs.

None -

Added 4.3.1 Voice CharacteristicAwareness Scheduling, whichincorporates the description ofuplink delay-based dynamicscheduling.

None -

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 followingtable lists the differences of VoIP-related features between eNodeB types. For details aboutother features and functions, see the corresponding feature parameter descriptions.

Feature ID Feature Name Supported byMacroeNodeBs

Supportedby MicroeNodeBs

Supported byLampSiteeNodeBs

LOFD-001016 VoIP Semi-persistentScheduling

Yes Yes Yes

LOFD-001048 TTI Bundling Yes Yes Yes

Feature ID Feature Name Supported byMacroeNodeBs

Supportedby MicroeNodeBs

Supported byLampSiteeNodeBs

LOFD-081229 Voice CharacteristicAwareness Scheduling

Yes Yes Yes

LBFD-081105 UL CompensationScheduling

Yes Yes Yes

LBFD-081105 Voice-Specific AMC Yes Yes Yes

Function Implementation in Macro, Micro, and LampSite eNodeBsFunction Difference

High speedmobility

Micro and LampSite eNodeBs do not support high speed mobility. Thedynamic scheduling policies for high speed mobility described hereinapply only to macro eNodeBs. For details, see 3.5.1 DynamicScheduling.

1.4 MHzbandwidth

Micro and LampSite eNodeBs do not support 1.4 MHz bandwidth. Thedynamic scheduling policies for 1.4 MHz bandwidth described hereinapply only to macro eNodeBs. For details, see 3.5.1 DynamicScheduling.

2 Overview

2.1 BackgroundThe 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 andGERAN or UTRAN. Dual-standby UEs automatically select GERAN or UTRAN toperform 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 toprovide voice services for LTE users if the IMS is not yet deployed. Figure 2-1 showsthe 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 MMEinstructs the UE to fall back to the legacy CS domain of the GERAN or UTRAN before

eRANVoLTE Feature Parameter Description 2 Overview

the UE performs the service. For details about CSFB, see CS Fallback FeatureParameter Description.

l Voice solution based on IMSThis 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 anLTE 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 andtheir voice services may be discontinued. Huawei uses the following methods to ensurevoice 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 singleradio voice call continuity (SRVCC). For details about SRVCC, see SRVCC FeatureParameter Description.

– If the PS domain of the UTRAN/GERAN supports VoIP services, VoIP services arehanded over to the UTRAN/GERAN through PS handovers. For details about PShandovers, see Inter-RAT Mobility Management in Connected Mode FeatureParameter Description.

Figure 2-2 Voice solution based on IMS

2.2 IntroductionVoLTE 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 voiceservices directly.

Emergency services are not described in this document. For details about emergency services,see Emergency Call Feature Parameter Description.

2.3 BenefitsVoLTE provides UEs in the E-UTRAN with voice services, without the need of falling backto 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 forSystem 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 networkgateway

IP multimedia subsystem (IMS) includes multiple network elements (NEs). These NEsperform voice session control and multimedia negotiation between the calling and called UEs.

Function Architecture

Table 2-1 describes the basic functions of VoLTE.

Table 2-1 Basic VoLTE functions

Function Description

Speech codec schemeand traffic model

During a VoLTE call, the UEs negotiate a speech codec schemewith the IMS. The commonly used codec scheme is AdaptiveMultirate (AMR). For details about its voice traffic model, see3.1 Speech Codec Scheme and Traffic Model.

VoLTE voice policyselection

During the attach procedure, the UE negotiates with the MMEand selects VoLTE as the voice policy. For details about voicepolicy selection, see 3.2 VoLTE Voice Policy Selection.

Radio bearermanagement

Radio bearers with QoS class identifiers (QCIs) of 1 and 5 areset up between the calling and called UEs to carryconversational voice and signaling, respectively. For detailsabout radio bearer management, see 3.3 Radio BearerManagement.

Admission andcongestion control

The eNodeB performs admission and congestion control forconversational voice (QCI 1) and signaling (QCI 5). For detailsabout admission and congestion control, see 3.4 Admissionand Congestion Control.

Dynamic scheduling andpower control

By default, the eNodeB performs dynamic scheduling and usespower control policies that are suitable for dynamic scheduling.For details about dynamic scheduling and power control, see3.5 Dynamic Scheduling and Power Control.

UEs can perform VoLTE services after the preceding functions are enabled. Table 2-2describes the features that help improve VoLTE performance such as capacity, coverage, andvoice quality.

Table 2-2 Enhanced VoLTE features/functions

Category Feature/FunctionName

Description

Capacityenhancement

Semi-persistentscheduling and powercontrol

The eNodeB performs semi-persistentscheduling and uses suitable power controlpolicies for UEs during talk spurts.This feature applies only to voice services. Fordetails about semi-persistent scheduling andpower control, see 4.1.1 Semi-PersistentScheduling and Power Control.The eNodeB performs dynamic scheduling anduses suitable power control policies for UEs atvoice service setup and during silent periods.

Description

Robust headercompression (ROHC)

ROHC compresses the headers of voice packetsto reduce air interface overheads.This feature applies only to voice services. Fordetails about how ROHC works for VoLTE, see4.1.2 ROHC.

Coverageimprovement

Transmission timeinterval (TTI) bundling

Multiple TTIs are bound together for UEs withpoor signal quality to transmit the same data.This increases the once-off transmissionsuccess rate.This feature applies only to uplink voiceservices. For details, see 4.2.1 TTI Bundling.

Robust headercompression (ROHC)

ROHC compresses the headers of voice packetsto reduce air interface overheads and increasethe once-off transmission success rate.This feature applies only to voice services. Fordetails about how ROHC works for VoLTE, see4.2.2 ROHC.

Uplink RLC segmentationenhancement

This feature restricts the transport block size(TBS) in UL dynamic scheduling to control thenumber of uplink RLC segments for VoLTEpackets. This restriction improves voice qualitywhen channel quality is poor. For details aboutthis feature, see 4.2.3 Uplink RLCSegmentation Enhancement.

QualityImprovement

Voice characteristicawareness scheduling

During uplink dynamic scheduling, the eNodeBadjusts the scheduling priorities of UEs basedon their waiting time and estimates the voicevolume to be dynamically scheduled in theuplink. An independent inactivity timer isconfigured for voice services. The purpose is toimprove voice quality, decrease the servicedrop rate, and increase the proportion ofsatisfied voice service users.This feature applies only to voice services. Fordetails about how UL delay-based dynamicscheduling, UL VoLTE volume estimation fordynamic scheduling, and independentconfiguration for voice inactivity timer workfor VoLTE, see 4.3.1 Voice CharacteristicAwareness Scheduling.

Description

Uplink compensationscheduling

For each voice user, the eNodeB measures theduration in which the user is not scheduled inthe uplink. If the duration reaches a threshold,the eNodeB performs uplink compensationscheduling for the UE. The purpose is to ensurethat uplink voice packets can be timelytransmitted, shorten their waiting time, andreduce the number of packets discardedbecause of the expiry of PDCP Discard Timer.This feature applies only to voice services. Fordetails, see 4.3.2 Uplink CompensationScheduling.

Voice-specific AMC The eNodeB sets a target IBLER for uplinkvoice services.This feature applies only to voice services. Fordetails, see 4.3.3 Voice-Specific AMC.

Powersaving

Discontinuous reception(DRX)

With DRX, UEs enter the sleep state when datais not transmitted, saving UE power.For details about how DRX works for VoLTE,see 4.4 Power Saving.

Mobilitymanagement

Intra-frequency handover The eNodeB performs intra-frequency, inter-frequency, or inter-RAT handovers to transferUEs performing voice services to appropriateneighboring cells to maintain voice continuity.For details about how mobility managementworks for VoLTE, see 4.5 MobilityManagement.

Inter-frequency handover

Inter-RAT handover

Voice service performance can be evaluated on various dimensions. For details about voiceservice performance evaluation, see 8 Voice Service Performance Evaluation.

3 Basic VoLTE Functions

The ENodeBAlgoSwitch.EutranVoipSupportSwitch parameter specifies whether to enableVoLTE.

l When this parameter is set to ON(On) on an eNodeB, this eNodeB supports VoLTE andallows the establishment, access, incoming handover, and reestablishment of thededicated bearer with a QCI of 1.

l When this parameter is set to OFF(Off)) on an eNodeB, this eNodeB does not supportVoLTE and does not allow the establishment, access, incoming handover, andreestablishment of the dedicated bearer with a QCI of 1.

eRANVoLTE Feature Parameter Description 3 Basic VoLTE Functions

3.1 Speech Codec Scheme and Traffic ModelThe speech codec scheme is classified into AMR and G.7 series. VoLTE uses the AMR-basedspeech codec scheme.

Adaptive Multi Rate (AMR) is an audio data compression scheme optimized for speechcoding and is now widely used in GERAN and UTRAN. AMR is classified into adaptivemultirate 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.4kbit/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.

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 forVoLTE services. Whether AMR-WB or AMR-NB is used is negotiated between the UEs andthe IMS.

Figure 3-1 Voice traffic model

There are two VoLTE traffic states:

l Talk spurtsDuring talk spurts, the uplink of UEs transmits voice packets or the downlink of UEsreceives voice packets. Voice packets are transmitted at intervals of 20 ms, and thepacket size is determined by the speech coding rate.

l Silent periodDuring silent periods, the UE transmits silence insertion descriptor (SID) frames orreceives SID frames at intervals of 160 ms. For different AMR speech codec rates, theSID 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.

l The interval between neighboring voice frames is different from the interval betweenSID frames.

The eNodeB distinguishes between voice frames and SID frames based on the precedingdifferences.

G.7 Series

The widely used G.7 series standards include G.711, G.729, and G.726.

l G.711G.711, also known as pulse code modulation (PCM), is primarily used in fixed-linetelephony. It supports a coding rate of 64 kbit/s.

l G.729G.729, known for the high voice quality and low delay, is widely used in variousdomains of data communications. It supports a coding rate of 8 kbit/s.

l G.726G.726 supports coding rates of 16 kbit/s to 40 kbit/s. The most commonly used rate is 32kbit/s. In actual application, voice packets are sent at intervals of 20 ms.

3.2 VoLTE Voice Policy SelectionUE 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 asVoLTE-prohibited scenario.

This section describes voice policy selection for UEs in common and VoLTE-prohibitedscenarios.

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 policybased on the UE capability and configuration on the MME side. The MME then sends the UEthe voice policy contained in the Attach Accept and TAU Accept messages. During voicepolicy 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 UEregistration:– CS Voice only

That is, CSFB.– IMS PS Voice only

That is, VoLTE.

– Prefer CS Voice with IMS PS Voice as secondaryThat is, CSFB takes precedence over VoLTE.For details about the voice policy negotiation procedures between the UE and MMEwhen this policy is used, see Annex A.2 in 3GPP TS 23.221 V9.4.0.

– Prefer IMS PS Voice with CS Voice as secondaryThat is, VoLTE takes precedence over CSFB.Figure 3-2 and Figure 3-3 show the voice policy negotiation procedures betweenthe UE and MME when this policy is used. For details about the voice servicepolicy negotiation, see Annex A.2 in 3GPP TS 23.221 V9.4.0.

Figure 3-2 Procedures for voice policy selection (non-combined attach)

Figure 3-3 Procedures for voice policy selection (combined attach)

3GPP Release 11 introduced VoLTE mobility capability decision, which further helps theMME 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 Requestmessage 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, theeNodeB sends a UE Capability Enquiry message to the UE.

3. The UE reports its radio capability through the UE Capability Information message. Fordetails, see section 5.6.3 "UE Capability Transfer" in 3GPP TS 36.331 R10.

4. If the eNodeB determines that the UE can ensure mobility after the UE performs VoLTEservices, the eNodeB replies the MME with the decision result through the UE RadioCapability Match Response message.

The SupportS1UeCapMatchMsg option of the GlobalProcSwitch.ProtocolSupportSwitchparameter 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 UEmeets 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 ofUTRAN-FDD to the CS domain of GERAN.

– The UE supports the PS domain of UTRAN-TDD (VoHSPA), SRVCC from the PSdomain to the CS domain of UTRAN-TDD, and SRVCC from the PS domain ofUTRAN-TDD to the CS domain of GERAN.

l When the SupportS1UeCapMatchMsg option is deselected, the eNodeB does notperform VoLTE mobility capability decision. In this case, the eNodeB replies ERRORINDICATION when receiving the UE RADIO CAPABILTY MATCH REQUESTmessage. If the UE uses VoLTE but does not support SRVCC, VoLTE mobility cannot beensured.

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 Setupmessage.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 theVoLTE mobility cannot be ensured.

l If the eNodeB is not informed of the MME's SRVCC capability, for example, the UE RADIOCAPABILTY MATCH REQUEST message arrives at the eNodeB earlier than the Initial UE ContextSetup message, the eNodeB does not consider the MME's capability while determining UE voiceservice continuity.

3.2.2 VoLTE-Prohibited ScenarioThe 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 thesescenarios:

l Transmission delay is large.Voice services have high requirements on end-to-end delay. Figure 3-5 shows therelationship between end-to-end delay and perceived voice quality, as per ITU-TRecommendation G.114. As shown in the figure, the end-to-end delay threshold toachieve very satisfied user experience is 200 ms, and that to achieve satisfied userexperience is 275 ms. That is, VoLTE users become dissatisfied on voice quality whenthe end-to-end delay exceeds 275 ms. The recommended packet delay budget for the Uuinterface 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 theEPC and eNodeB is 20 ms. If the transmission delay between the EPC and eNodeB isgreater than 20 ms, voice quality may not be guaranteed after VoLTE is deployed on theeNodeB.

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 notserve 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 settingdedicated TAIs on the MME, areas in such scenarios use CSFB instead of VoLTE. During theAttach and tracking area update (TAU), UEs negotiate or re-negotiate with the MME aboutvoice policies. Voice policy negotiation between the UE and the MME is transparent to theeNodeB.

You can turn off the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch for eNodeBswith dedicated TAIs working in the preceding scenarios. For eNodeBs with non-dedicatedTAIs, you can select the VoipHoControlSwitch option of theENodeBAlgoSwitch.HoAlgoSwitch parameter and configure the VoLTE handover blacklistin the EutranVoipHoBlkList MO. This prevents UEs performing voice services fromhanding over to these eNodeBs or reestablished on the eNodeBs.

After the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch is turned off and VoLTE isdisabled for a specific tracking area on the MME, the statistics about VoLTE-related KPIssuch 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 areacode (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.

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;

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 inthe VoLTE handover blacklist (specified by the EutranVoipHoBlkList MO) depending on the settingsof the VoipHoControlSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter.

According to current 3GPP specifications, voice policies can be configured only on a TAC basis on theMME. ENODEBALGOSWITCH.EutranVoipSupportSwitch andENODEBALGOSWITCH.HoAlgoSwitch.VoipHoControlSwitch parameters for the eNodeB are usedto 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 VoLTEhandovers, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.

When the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch is turned on, dedicated bearer forservices with QCI of 1 can be set up for the eNodeB. When this switch is turned off, dedicated bearer forservices with QCI of 1 is not allowed to be set up for the eNodeB.

3.3 Radio Bearer Management

3.3.1 Radio Bearer SetupFrom 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-6shows the process of setting up a voice session between the calling and called UEs.

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 andan 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 signalingexchange between the UE and the IMS.

3. After the QCI 5 radio bearer is set up, the calling UE and the IMS perform SessionInitiation Protocol (SIP) negotiation on the speech codec scheme, IP address, portnumber, called UE's information, and other information.

4. In the EPS bearer establishment (QCI 1) procedure, a QCI 1 radio bearer is set up tocarry voice packets.

If VoLTE is determined as the voice solution for a UE according to negotiation with the MME, a QCI 5radio bearer is set up when the UE enters RRC_CONNECTED mode, irrespective of whether the UE isperforming a voice service or not.

When ENodeBAlgoSwitch.EutranVoipSupportSwitch is set to OFF(Off), the eNodeB cannot set upQCI 1 radio bearers (the eNodeB sends to the EPC a message containing the cause value "Not supportedQCI 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 precedingprocedures.

eNodeBs provide the following QCI 1-specific timer settings:ENodeBConnStateTimer.S1MsgWaitingTimerQci1,ENodeBConnStateTimer.X2MessageWaitingTimerQci1,ENodeBConnStateTimer.UuMessageWaitingTimerQci1,RrcConnStateTimer.UeInactiveTimerQci1, and CellStandardQci.TrafficRelDelay. For details aboutthese parameters, see Connection Management Feature Parameter Description.

3.3.2 Radio Bearer QoS ManagementRadio bearer QoS management for voice services complies with the Policy and ChargingControl 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 thedynamic PCC rule as follows:

1. The IMS (P-CSCF) sends QCI information to the PCRF over the Rx interface.

2. Based on the received QCI information and subscription information, the PCRFgenerates a QoS rule (including the following key QoS parameters: QCI, ARP, GBR, andMBR) 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, andeNodeB to set up EPS bearers. Services of different QoS requirements are carried byradio bearers with different QCIs. According to 3GPP specifications, the QCIs forconversational voice, conversational video, and IMS signaling are 1, 2, and 5,respectively. Table 3-1 lists their QoS parameters. QoS parameters are set inStandardQci MOs, and the Radio Link Control (RLC) modes for setting upconversational voice, conversational video, and IMS signaling E-RABs are specified bythe RlcPdcpParaGroup.RlcMode parameter. For details, see 3GPP 23.203.

Table 3-1 QoS parameters for conversational voice, conversational video, and IMSsignaling

ResourceType

Priority

Delay Packet LossRate

Service Type

1 GBR 2 100 ms 10-2 Conversationalvoice

2 GBR 4 150 ms 10-3 Conversationalvideo

5 Non-GBR 1 100 ms 10-6 IMS signaling

A smaller priority value indicates a higher priority.

For details about QCIs and RLC modes, see QoS Management Feature ParameterDescription.

3.4 Admission and Congestion Control

3.4.1 OverviewThis section describes how the basic features LBFD-002023 Admission Control andLBFD-002024 Congestion Control work for VoLTE. For details about the two features, seeAdmission 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 MonitoringLoad monitoring provides decision references for admission and congestion control. TheeNodeB 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 thisway, the eNodeB can know the current status of a cell.

Conversational Voice (QCI 1)

For the method of calculating the QoS satisfaction rate of QCI 1, see Admission andCongestion 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 ControlAdmission control determines whether to admit a GBR service (new service or handoverservice) based on the cell load reported by the load monitoring module. The cell load isrepresented by the PRB usage, QoS satisfaction rates of GBR services, and resourceinsufficiency indicators. For details, see Admission and Congestion Control FeatureParameter Description.

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

Admission control for non-GBR services (QCI 5) is not based on load. If SRS and PUCCHresources are successfully allocated, non-GBR services (QCI 5) are directly admitted.

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 afterSRS resources are successfully allocated.

Even if the PreemptionSwitch option under the CellAlgoSwitch.RacAlgoSwitch parameteris selected, IMS signaling (QCI 5) cannot be preempted.

3.4.4 Congestion ControlWhen the network is congested, the eNodeB preferentially releases low-priority GBR servicesto free up resources for other services. For details, see Admission and Congestion ControlFeature Parameter Description.

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

3.5 Dynamic Scheduling and Power Control

3.5.1 Dynamic SchedulingThis section describes how the optional feature LOFD-00101502 Dynamic Scheduling worksfor 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 scheduleroptimizes the handling of voice service priorities to ensure voice service QoS. When VoLTEis deployed, it is recommended that the enhanced proportional fair (EPF) scheduling policy beused 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 downlinkby default.

For details about dynamic scheduling for voice services, see Scheduling Feature ParameterDescription.

Uplink Dynamic Scheduling

When uplink dynamic scheduling uses the enhanced proportional fair (EPF) algorithm, thepriority of conversational voice (QCI 1) is lower than the priorities of data retransmitted usingHARQ, signaling radio bearer 1 (SRB1), SRB2, and IMS signaling (QCI 5), but higher thanthe priorities of other initially transmitted data.

It is recommended that the UlLast2RetransSchOptSwitch option of theCELLALGOSWITCH.UlSchSwitch parameter be selected when dynamic scheduling isused and there are voice services. Selecting this option decreases the packet loss rate of voiceservices and improves user experience on voice services.

Uplink voice preallocation is introduced to reduce the delay of voice services. When thenumber of UEs in a cell exceeds 50, the eNodeB preallocates uplink resources only to UEsperforming voice services. When the number of UEs in a cell is less than or equal to 50, theeNodeB retains the existing uplink preallocation or uplink smart preallocation mechanism forall UEs. For details, see Scheduling Feature Parameter Description. Uplink voicepreallocation is controlled by the UlVoipPreAllocationSwtich option of theCellAlgoSwitch.UlEnhencedVoipSchSw parameter.

Downlink Dynamic Scheduling

When dynamic scheduling is used, the scheduling priority is related to whether theLOFD-001109 DL Non-GBR Packet Bundling feature is enabled:

l If the LOFD-001109 DL Non-GBR Packet Bundling feature is not enabled: When theEPF 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

messages, IMS signaling (QCI of 5), HARQ retransmission data, and RLC AM statusreport. However, the priority for scheduling voice packets (QCI of 1) is higher than thatfor scheduling initial transmission data.

l If the LOFD-001109 DL Non-GBR Packet Bundling feature is enabled: The priority forscheduling voice packets (QCI of 1) is no longer higher than that for scheduling initialtransmission data. Instead, the eNodeB sorts overall priorities.

When dynamic scheduling is used, the MCS selection policy depends on the value for theVoipTbsBasedMcsSelSwitch option of the CellAlgoSwitch.DlSchSwitch parameter.

l When this option is selected, the eNodeB checks the number of online VoIP subscribersand IBLER and then determines whether to apply the TBS-based MCS selection functionto voice services. TBS is short for transport block size. If the function takes effect onvoice services, the eNodeB makes decisions based on the packet size during a voice callto select a relatively low MCS while ensuring that the number of RBs remainsunchanged. In this way, HARQ retransmission and user delay are reduced.

l When this option is deselected, the eNodeB determines the MCS for voice services basedon the downlink CQI adjustment algorithm. For details about the downlink CQIadjustment algorithm, see Scheduling Feature Parameter Description.

When dynamic scheduling is used for voice services, it is recommended that theDlRetxTbsIndexAdjOptSwitch of the CellAlgoSwitch.CqiAdjAlgoSwitch parameter beturned on to reduce the voice packet loss rate and improve voice user experience. For detailsabout this switch, see Scheduling Feature Parameter Description.

3.5.2 Power Control in Dynamic SchedulingPower control policies for voice services in dynamic scheduling are the same as those for dataservices. For details about voice service power control policies when dynamic scheduling isused for voice services, see Power Control Feature Parameter Description.

4 Enhanced VoLTE Features

Operators can enable features described in this chapter to improve VoLTE performance suchas capacity and coverage.

eRANVoLTE Feature Parameter Description 4 Enhanced VoLTE Features

4.1 Capacity EnhancementThe following features can be enabled to increase capacity for voice services:

l Semi-persistent scheduling and power controlWhen the capacity is low due to high PDCCH overheads, these features can be used toreduce PDCCH overheads and therefore increase the maximum number of VoLTE usersor the throughput of data services (provided that the number of VoLTE users remainsunchanged).

l Uplink delay-based dynamic schedulingWhen there are too many VoLTE users, this feature can be used to improve theperformance of cell edge users (CEUs) by sacrificing the performance of cell centerusers (CCUs) and increase the proportion of satisfied VoLTE users.

l ROHCBy compressing the headers of voice packets, this feature reduces air interface overheadsand 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 SchedulingThis section describes the LOFD-001016 VoIP Semi-persistent Scheduling feature.

IntroductionWhen dynamic scheduling is used for voice services, time-frequency resource or MCS isupdated through the PDCCH every 20 ms. This consumes a large number of PDCCHresources. Figure 4-1 shows the resource allocation for dynamic scheduling.

Figure 4-1 Resource allocation for dynamic scheduling

Huawei introduces the VoLTE semi-persistent scheduling feature for small-packet servicesthat are periodically transmitted such as VoLTE. Before entering talk spurts, the eNodeBallocates fixed resources to UEs through the PDCCH message. Before exiting talk spurts orreleasing resources, the UEs do not need to apply for resource allocation from the PDCCHagain, 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 intervalof 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 forQCI of 1. The eNodeB activates UL or DL semi-persistent scheduling for UEs when UEsmeet the UL or DL semi-persistent scheduling activation conditions. The eNodeB instructsUEs 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 forsemi-persistent scheduling" in 3GPP TS 36.213 V12.3.0.

Effect Period

Figure 4-3 Semi-persistent scheduling effect period

In talk spurt, uplink or downlink semi-persistent scheduling takes effect when all thefollowing 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 contextsl Downlink semi-persistent retransmissionl Uplink semi-persistent adaptive retransmission

When the UE uses semi-persistent scheduling, the highest MCS index is only 15.

Uplink Semi-Persistent SchedulingDuring semi-persistent scheduling, the eNodeB determines the modulation and codingscheme (MCS) and the number of PRBs based on the following items:

l Voice packet size (ROHC disabled) or size of compressed voice packets (ROHCenabled)

l Wideband signal to interference plus noise ratio (SINR)

After semi-persistent scheduling is activated, the UE periodically sends data and the eNodeBperiodically receives data using the semi-persistently allocated resources. In addition, theeNodeB checks whether the MCS allocated in semi-persistent scheduling matches the currentchannel status. If the MCS does not match the current channel status, the eNodeB activatessemi-persistent scheduling again.

After the eNodeB triggers a UE to enter uplink semi-persistent scheduling, thelogicalChannelSR-Mask-r9 IE in the RRC Reconfiguration message instructs the UE not tosend scheduling requests over the radio bearers for QCI of 1. This reduces UE powerconsumption. The CellAlgoSwitch.SrMaskSwitch parameter controls this function. It isrecommended that both this function and uplink semi-persistent scheduling be enabled. Thisfunction 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 schedulingexceeds 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 thancommon 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 theUE periodically receives data using the semi-persistently allocated resources.

During semi-persistent scheduling, the eNodeB determines the MCS and the number of PRBsbased on the following items:

l Voice packet size (ROHC disabled) or size of compressed voice packets (ROHCenabled)

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 allocatedin semi-persistent scheduling matches the current channel status. If the MCS does not matchthe 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 processesfor downlink semi-persistent scheduling while configuring semi-persistent scheduling forUEs.

When the eNodeB configures semi-persistent scheduling for UEs, the PUCCH requiresavailable semi-persistent code channel for HARQ. Otherwise, the eNodeB does not configuresemi-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 isused for VoLTE. For details about power control, see Power Control Feature ParameterDescription.

Power Control in Uplink Semi-Persistent SchedulingWhen semi-persistent scheduling is used for VoLTE in the uplink, closed-loop power controlfor the physical uplink shared channel (PUSCH) can be enabled or disabled by setting theCloseLoopSpsSwitch option of the CellAlgoSwitch.UlPcAlgoSwitch parameter.

l If the CloseLoopSpsSwitch option is selected, the eNodeB adjusts transmit power forthe PUSCH based on the measured IBLER of voice services.

l If the CloseLoopSpsSwitch option is deselected, the eNodeB uses open-loop (notclosed-loop) power control for the PUSCH.

Power Control in Downlink Semi-Persistent SchedulingWhen semi-persistent scheduling is used for VoLTE in the downlink, power control for thePDSCH can be enabled or disabled by setting the PdschSpsPcSwitch option of theCellAlgoSwitch.DlPcAlgoSwitch parameter.

l If the PdschSpsPcSwitch option is selected, the eNodeB periodically adjusts thePDSCH 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 sharedby each RB.

4.1.2 ROHCThis section describes how the optional feature LOFD-001017 RObust Header Compression(ROHC) works for VoLTE. For details about this feature, see ROHC Feature ParameterDescription.

ROHC provides an efficient header compression mechanism for data packets transmitted onradio 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 shortenresponse time.

In the current version, ROHC is used to compress the headers of only voice packets (QCI of 1and PTT QCI services), as shown in Figure 4-4. ROHC reduces the packet size and physicalresource block (PRB) overheads. When PRBs are insufficient, ROHC helps increase systemcapacity.

Figure 4-4 ROHC for VoLTE

After deploying VoLTE, operators can enable or disable ROHC by setting thePdcpRohcPara.RohcSwitch parameter. ROHC is an extensible framework consisting of

different profiles for data streams compliant with different protocols. Profiles define thecompression modes for streams with different types of protocol headers. Voice services useprofiles 0x0001 and 0x0002.

The ROHC compression efficiency varies with the ROHC operating mode and variations inthe dynamic part of packet headers at the application layer. A header can be compressed to asize as small as 1 byte, which efficiently reduces the voice packet size.

4.2 Coverage ImprovementOperators can enable the following features to improve voice service coverage in poorcoverage scenarios:

l TTI Bundlingl ROHCl Uplink RLC segmentation enhancement

4.2.1 TTI BundlingThis section describes the principles of the optional feature LOFD-001048 TTI Bundling andhow this feature works for VoLTE.

4.2.1.1 OverviewTTI bundling enables a data block to be transmitted in four consecutive TTIs, which arebound together and treated as the same resource. Different HARQ redundancy versions of thesame data block are transmitted in different TTIs. TTI bundling makes full use of HARQcombining gains and reduces the number of retransmissions and RTT.

When the UE's channel quality is poor and transmit power is limited, TTI bundling increasesthe cell edge coverage of the PUSCH by about 1 dB. The gains produced by this feature canbe observed when voice quality is maintained at a certain level, for example, when the meanopinion score (MOS) is 3.

The TtiBundlingSwitch option of the CellAlgoSwitch.UlSchSwitch parameter determineswhether to enable TTI bundling. When this option is selected, the eNodeB determineswhether 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 qualityand the amount of data to be transmitted.

According to section 8.6.1 "Modulation order and redundancy version determination" in3GPP TS 36.213 V10.1.0, when TTI bundling is enabled, the resource allocation size isrestricted 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, themaximum 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. Toprevent 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 StateIn eRAN8.1, the CellAlgoSwitch.TtiBundlingTriggerStrategy parameter is introduced.

l When the TtiBundlingTriggerStrategy parameter is set toSERVICE_VOIP(SERVICE_VOIP), TTI bundling applies to only VoLTE. Under thisparameter 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 theCellAlgoSwitch.StatisticNumThdForTtibTrig.

If the UE meets all these conditions, the eNodeB sends the UE an RRC ConnectionReconfiguration message, instructing the UE to enter the TTI bundling state.

l When the TtiBundlingTriggerStrategy parameter is set toSERVICE_MULTIAPP(SERVICE_MULTIAPP), TTI bundling can apply to VoLTEor a combination of VoLTE and data. Under this parameter setting, the conditions forentering 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 theCellAlgoSwitch.StatisticNumThdForTtibTrig.

If the UE meets all these conditions, the eNodeB sends the UE an RRC ConnectionReconfiguration message, instructing the UE to enter the TTI bundling state.

The processing in versions earlier than eRAN8.1 is the same as that when theTtiBundlingTriggerStrategy parameter is set to SERVICE_VOIP(SERVICE_VOIP) ineRAN8.1.

Data Block TransmissionFor the UE in the TTI bundling state, the eNodeB determines the number of PRBs and MCSbased on channel quality and the amount of data to transmit. Then, the eNodeB transmits datablocks.

As shown in Figure 4-5 , the UE transmits identical data within four consecutive TTIs in abundle and performs HARQ retransmission also within four TTIs in a bundle. Theretransmission operates in synchronous non-adaptive mode. Four uplink subframes in PHICHcarry 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 datablock in a bundle of TTIs, among which the last TTI is numbered N. The eNodeB sends anACK or NACK as feedback to the UE in the (N + 4)th TTI. Based on the feedback, the UEdetermines whether a retransmission is required. If it is required, the UE retransmits the datablock in the (N + 13)th through (N + 16)th TTIs.

When the UE is in the TTI bundling state, the maximum number of uplink HARQretransmissions 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 greaterthan the value of the CellAlgoSwitch.TtiBundlingRlcMaxSegNum parameter. The number is4 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 TTIbundling produces fewer RLC segments than pure RLC segmentation, reducing PDCCHoverheads.

Exit from TTI BundlingWhen the measured SINR is greater than the sum of the target SINR and theCellAlgoSwitch.HystToExitTtiBundling parameter value for multiple consecutive times, theeNodeB instructs the UE to exit the TTI bundling state through an RRC ConnectionReconfiguration message. The number of consecutive times is specified by theStatisticNumThdForTtibExit parameter.

The eNodeB does not instruct the UE to exit the TTI bundling state even when the UE hasdata to transmit on the default bearer, needs to set up a new dedicated bearer, or stops thevoice service (QCI 1). The eNodeB instructs the UE to exit the TTI bundling state when theUE meets the exit conditions, experiences handover or service drop, or needs to reestablish anew connection.

4.2.2 ROHCThis section describes how the optional feature LOFD-001017 RObust Header Compression(ROHC) works for VoLTE. For details about this feature, see ROHC Feature ParameterDescription.

ROHC can compress the RTP, UDP, or IP header of a voice packet, thereby reducing the sizeof the entire packet. ROHC results in a higher probability of correctly transmitting voicepackets with fewer segments and enhances the edge coverage for voice services.

4.2.3 Uplink RLC Segmentation EnhancementThis 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 ispoor 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 thepacket discard timer expires)

l Large overhead of RLC and MAC headers

l Large consumption of control channel elements (CCEs) and resource blocks (RBs) byUL dynamic scheduling of VoLTE services

Uplink RLC segmentation enhancement restricts the TBS in UL dynamic scheduling tocontrol the number of uplink RLC segments for voice packets. This restriction improves voicequality when channel quality is poor.

The CellAlgoSwitch.UlVoipRlcMaxSegNum parameter is introduced to control themaximum 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 theCellAlgoSwitch.UlVoipRlcMaxSegNum parameter, the number is not restricted.

l When the number of uplink RLC segments is greater than the value of theCellAlgoSwitch.UlVoipRlcMaxSegNum parameter, the number is restricted. Based onthe voice packet size and the configured maximum number of RLC segments, aminimum TBS is guaranteed in UL dynamic scheduling so that the number of uplinkRLC 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 orLCG_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.

This function applies only to services with QCI of 1.

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

4.3 Quality Improvement

4.3.1 Voice Characteristic Awareness SchedulingThis section describes LOFD-081229 Voice Characteristic Awareness Scheduling, involvinguplink delay-based dynamic scheduling, estimation of uplink VoLTE volume for dynamicscheduling, and independent configuration for voice inactivity timer.

Uplink Delay-based Dynamic SchedulingFor uplink delay-based dynamic scheduling, the eNodeB prioritizes voice packets based ontheir waiting times. Sorting scheduling priorities based on delay for voice services bringsbalanced scheduling sequence. This helps improve voice quality. Specifically, voice qualityimproves for UEs far from center with poor channel quality. This feature increases the usersatisfaction 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 isenabled.

Figure 4-7 Difference before and after uplink delay-based dynamic scheduling is enabled.

A longer wait time indicates a higher scheduling priority. When theCellAlgoSwitch.UlDelaySchStrategy parameter is set to VOIP_DELAYSCH(VoIP ServiceDelay Scheduling), uplink delay-based dynamic scheduling for VoLTE is used.

Uplink VoLTE Volume Estimation for Dynamic SchedulingThe eNodeB can obtain the accurate downlink service volume but cannot obtain the accurateuplink service volume.

Therefore, uplink VoLTE volume estimation for dynamic scheduling is introduced to allowthe eNodeB to perform the uplink estimation based on the VoLTE model and uplinkscheduling 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 bufferbased on their uplink scheduling intervals and then calculates the volume of voicepackets based on the size of a voice packet.

l During silent periods, the eNodeB takes the size of a voice packet as the uplink VoLTEvolume for dynamic scheduling.

Uplink VoLTE volume estimation for dynamic scheduling makes the calculation of uplinkservice volume more accurate and therefore shortens voice packet delays. This function can

improve voice quality when the cell is heavily loaded and DRX is enabled. Figure 4-8 showsthe principles.

Figure 4-8 Uplink VoLTE Volume Estimation for Dynamic Scheduling

Uplink VoLTE volume estimation for dynamic scheduling is controlled by theUlVoLTEDataSizeEstSwitch option of the CellAlgoSwitch.UlEnhencedVoipSchSwparameter.

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 inactivitytimer expires. This may interrupt the session.

l In dynamic DRX scenarios, the RrcConnStateTimer.UeInactivityTimerDynDrxparameter specifies the length of the UE inactivity timer. The default and recommendedvalues of this parameter are large and therefore do not cause call setup failures in thepreceding scenario.In other scenarios, with independent configuration for voice inactivity timer, the UEs candistinguish voice and non-voice scenarios. That is, the length of the UE inactivity timercan be independently configured to avoid the preceding negative impact. When theCELLALGOSWITCH.UEInactiveTimerQCI1Switch parameter is set to ON(On), theRrcConnStateTimer.UeInactiveTimerQci1 parameter takes effect. Otherwise, theRrcConnStateTimer.UeInactiveTimerQci1 parameter does not take effect. It isrecommended that the value of the RrcConnStateTimer.UeInactiveTimerQci1parameter be greater than the active connection release timer length when the calledparty of the core network does not respond.

4.3.2 Uplink Compensation SchedulingThis section describes LBFD-081104 UL Compensation Scheduling.

Sending uplink data is dependent on the scheduling requests (SRs) reported by UEs. If aneNodeB experiences missing SR detection, the eNodeB may not perform scheduling in a

timely manner. This may extend the voice packet waiting delay or cause timeout-triggeredpacket 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 usersand, for each voice user, measures the duration in which the user is not scheduled in theuplink. If the duration reaches a threshold, the eNodeB sends a UL Grant to the UE to ensurethat uplink voice packets can be timely transmitted. This way, this feature shortens the waitingtime of voice packets and reduces the number of packets discarded because of the expiry ofPDCP Discard Timer. Figure 4-10 shows the situation after uplink compensation schedulingis enabled.

Figure 4-10 Uplink compensation scheduling enabled

This feature is controlled by the UlVoipSchOptSwitch option of theCellAlgoSwitch.UlEnhencedVoipSchSw parameter.

4.3.3 Voice-Specific AMCThis 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 FeatureParameter Description.

The eNodeB adjusts SINRs for UEs to be dynamically scheduled in the uplink based on theconfigured 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 differenttarget uplink IBLER values for VoLTE and data services.

l The CellAlgoSwitch.SinrAdjustTargetIbler parameter specifies the target uplink IBLERvalue for data services.

l The CellAlgoSwitch. SinrAdjTargetIblerforVoLTE parameter specifies the target uplinkIBLER value for VoLTE services. This parameter takes effect only to VoLTE UEs not inthe TTI bundling state.

Voice-specific AMC and uplink RLC segmentation enhancement can be enabledsimultaneously. Uplink RLC segmentation enhancement takes precedence if its requirementsare met.

4.4 Power SavingThis 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 nottransmitted, saving UE power. DRX typically applies to services with consecutive smallpackets that are transmitted periodically, for example, voice services. According to 3GPP TS23.203 and section A.2.1.4 "System performance metrics" in 3GPP TS 36.814, a 50 to 80 msdelay budget is reserved for services with QCI of 1 in the Uu interface and the interval ofsending 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 forvoice services does not provide much gain. Therefore, it is recommended that the short DRXcycle 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_CONNECTEDmode, regardless of whether the UE has a QCI 1 voice bearer. Therefore, it is recommendedthat the DRX parameters for QCI 5 be set to the same values as those for a default bearer usedin a data service. In addition, as a long DRX cycle leads to a long delay for setting up a QCI 1voice bearer, it is recommended that the long DRX cycle for QCI 5 be less than or equal to320 ms to provide fast access experience for VoLTE users.

The DRX.DrxAlgSwitch parameter specifies whether to enable DRX.

Figure 4-11 DRX working for VoLTE

Enabling DRX for QCI 1 can reduce the battery consumption on voice services, but at thesame time it affects voice quality, for example, the packet loss rate increases. For details, seeDRX and Signaling Feature Parameter Description.

False detection of the PDCCH may cause voice packet loss, due to which there is a low probability of voicequality deterioration. Preallocation can be used to reduce the impact of false detection. For details about howDRX works with preallocation, see DRX and Signaling Control Feature Parameter Description.

4.5 Mobility Management

4.5.1 OverviewThis section describes the mobility of voice services. It is recommended that coverage-basedintra-RAT and inter-RAT handovers for voice services be turned on by default to ensure thecontinuity of voice services.

Voice and data service handovers are classified into intra-frequency, inter-frequency, andinter-RAT handovers. Their handover procedures are the same. However, certain handoverparameters can be configured according to the QCI. When UEs set up bearers for differentQCIs during coverage-based, distance-based, and UL-quality-based handovers, the handoverparameters with high priority are used as the handover parameters. For details abouthandovers caused by other reasons, see Intra-RAT Mobility Management in Connected ModeFeature Parameter Description and Inter-RAT Mobility Management in Connected ModeFeature Parameter Description. The QCI priority is specified by theCellStandardQci.QciPriorityForHo parameter. A smaller value of this parameter indicates ahigher priority. If the QCI priority configurations (indicated by theCellStandardQci.QciPriorityForHo parameter) are the same, the eNodeB selects handoverparameters 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. Fordetails, see section 6.1.7 "Standardized QoS characteristics" in 3GPP TS 23.203 V10.3.0.

VoLTE is generally deployed in existing LTE networks, which are data networks. Mobility parameters inexisting 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 orinter-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 voiceservices, the default inter-frequency or inter-RAT mobility parameters are recommended. The precedingrecommendations minimize the impact on the KPIs of data services in future network optimization on VoLTEservices. For intra-frequency mobility, relative thresholds are used and can be separately configured for voiceand 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 aslong as the UE is in RRC_CONNECTED mode. Therefore, mobility parameters for QCI 5 can be set to thesame values as those for the default bearer used in a data service.

4.5.2 Intra-Frequency HandoverThis section describes the handover parameters that are set based on QCIs in different intra-frequency handover scenarios. These parameters are as follows:

l IntraFreqHOGroup.IntraFreqHoA3Hystl IntraFreqHOGroup.IntraFreqHoA3Offsetl IntraFreqHOGroup.IntraFreqHoA3TimeToTrig

For details about intra-frequency handovers, see Intra-RAT Mobility Management inConnected Mode Feature Parameter Description.

4.5.3 Inter-Frequency HandoverThis 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 inConnected Mode Feature Parameter Description.

Coverage-based Inter-Frequency Handover

The following handover parameters can be configured based on QCIs:

l InterFreqHoGroup.InterFreqHoA1A2Hystl InterFreqHoGroup.InterFreqHoA1A2TimeToTrigl InterFreqHoGroup.InterFreqHoA1ThdRsrpl InterFreqHoGroup.InterFreqHoA1ThdRsrql InterFreqHoGroup.InterFreqHoA2ThdRsrpl InterFreqHoGroup.InterFreqHoA2ThdRsrql InterFreqHoGroup.InterFreqHoA4Hystl InterFreqHoGroup.InterFreqHoA4ThdRsrpl InterFreqHoGroup.InterFreqHoA4ThdRsrql InterFreqHoGroup.InterFreqHoA4TimeToTrigl InterFreqHoGroup.InterFreqHoA3Offsetl InterFreqHoGroup.A3InterFreqHoA1ThdRsrpl InterFreqHoGroup.A3InterFreqHoA2ThdRsrp

l InterFreqHoGroup.InterFreqHoA5Thd1Rsrpl InterFreqHoGroup.InterFreqHoA5Thd1Rsrq

Service-based Inter-Frequency Handover

It is recommended that service-based inter-frequency handovers be used in inter-frequencyco-coverage scenarios.

l InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrpl InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrq

If operators require that service-based inter-frequency handovers be performed on voiceservices, that is, services with QCI of 1 be preferentially set up on a certain frequency, thefollowing handover policies must be configured:

l Set the handover policy ServiceIfHoCfgGroup.InterFreqHoState ofServiceIfDlEarfcnGrp.DlEarfcn to PERMIT_HO.

When a UE initiates a voice service, the eNodeB delivers the A4 measurement configuration to theUE, instructing the UE to measure the frequency identified by theServiceIfDlEarfcnGrp.DlEarfcn parameter.

l Set the CnOperatorStandardQci.Qci parameter to configure the mapping between theinter-frequency handover frequency policy and services with a QCI of 1.

l Set the CellStandardQci.QciPriorityForHo parameter to configure the highesthandover priority for QCI 1.

l It is recommended that initial planning and configuration be performed on neighboringcells on frequencies that carry only VoLTE services.

Distance-based Inter-Frequency Handover

l InterFreqHoGroup.InterFreqHoA4ThdRsrpl InterFreqHoGroup.InterFreqHoA4ThdRsrq

UL-Quality-based Inter-Frequency Handover

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

Frequency-Priority-based Inter-Frequency Handover

The following handover parameters related to event A1 and event A2 can be separatelyconfigured based on QCIs:

l InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrpl InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrql InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrp

l InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrq

Similar to service-based inter-frequency handover, frequency-priority-based inter-frequencyhandover 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 ConnectedMode Feature Parameter Description.

Coverage-based Inter-RAT Handover

The following common inter-RAT handover parameters can be configured based on QCIs:

l InterRatHoCommGroup.InterRatHoA1A2Hystl InterRatHoCommGroup.InterRatHoA1A2TimeToTrigl InterRatHoCommGroup.InterRatHoA1ThdRsrpl InterRatHoCommGroup.InterRatHoA1ThdRsrql InterRatHoCommGroup.InterRatHoA2ThdRsrpl 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.InterRatHoUtranB1ThdEcn0l InterRatHoUtranGroup.InterRatHoUtranB1ThdRscpl InterRatHoUtranGroup.InterRatHoUtranB1Hystl InterRatHoUtranGroup.InterRatHoUtranB1TimeToTrigl InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRscp

GERAN l InterRatHoGeranGroup.InterRatHoGeranB1Hystl InterRatHoGeranGroup.InterRatHoGeranB1Thdl InterRatHoGeranGroup.InterRatHoGeranB1TimeToTrigl InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd

CDMA 1xRTT

l InterRatHoCdma1XrttGroup.InterRatHoCdmaB1Hystl InterRatHoCdma1XrttGroup.InterRatHoCdmaB1ThdPsl InterRatHoCdma1XrttGroup.InterRatHoCdmaB1TimeToTrigl InterRatHoCdma1XrttGroup.LdSvBasedHoCdmaB1ThdPs

Target RAT Parameter ID

CDMAHRPD

l InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1Hystl InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1ThdPsl InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1TimeToTrigl InterRatHOCdmaHrpdGroup.LdSvBasedHoCdmaB1ThdPsl InterRatHOCdmaHrpdGroup.Cdma2000HrpdB2Thd1Rsrpl InterRatHOCdmaHrpdGroup.Cdma2000HrpdB2Thd1Rsrq

Service-based Inter-RAT HandoverWith service-based inter-RAT handover, voice services are handed over from the E-UTRANto GERAN or UTRAN during the service setup phase.

If VoLTE has been deployed, the configurations of service-based inter-RAT handover mustmeet either of the following conditions so that the eNodeB does not immediately trigger theservice-based inter-RAT handover procedure after the UE sets up voice services:

l The UtranServiceHoSwitch(UtranServiceHoSwitch) andGeranServiceHoSwitch(GeranServiceHoSwitch) options of theENodeBAlgoSwitch.HoAlgoSwitch parameter are deselected.

l The UtranServiceHoSwitch(UtranServiceHoSwitch) andGeranServiceHoSwitch(GeranServiceHoSwitch) options of theENodeBAlgoSwitch.HoAlgoSwitch parameter are selected, and theServiceIrHoCfgGroup.InterRatHoState parameter mapping QCI of 1 and QCI of 5 isnot set to MUST_HO.

Distance-based Inter-RAT HandoverThe 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. Theseparameters also apply to coverage-based inter-RAT handovers.

Table 4-2 Distance-based inter-RAT handover parameters

TargetRAT

Parameter ID

UTRAN l InterRatHoUtranGroup.InterRatHoUtranB1ThdEcn0l InterRatHoUtranGroup.InterRatHoUtranB1ThdRscpl InterRatHoUtranGroup.InterRatHoUtranB1Hystl InterRatHoUtranGroup.InterRatHoUtranB1TimeToTrigl InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRscp

TargetRAT

Parameter ID

GERAN l InterRatHoGeranGroup.InterRatHoGeranB1Hystl InterRatHoGeranGroup.InterRatHoGeranB1Thdl InterRatHoGeranGroup.InterRatHoGeranB1TimeToTrigl InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd

UL-Quality-based Inter-RAT HandoverSimilar 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-basedInter-RAT Handover.

4.5.4.2 Handover ModeThe eNodeB determines whether to use SRVCC or PS handover for performing the precedinginter-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 whetherthe target RAT can carry IMS-based voice services.

SRVCCWith SRVCC, the eNodeB hands over voice services from E-UTRAN to the CS domain of theGERAN or UTRAN to ensure voice call continuity. For details about SRVCC, see SRVCCFeature Parameter Description.

PS HandoverWith PS handover, the eNodeB hands over voice services from E-UTRAN to the PS domainof the UTRAN to ensure voice call continuity.

If the UTRAN supports the IMS-based VoHSPA voice solution, voice services can be handedover to VoHSPA of the UTRAN using inter-RAT PS handovers. In this situation, themechanism 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 ModeFeature Parameter Description.

5 Special Processing by Other Features

After LOFD-002001 Automatic Neighbour Relation (ANR) or LOFD-002002 Inter-RATANR are configured, the eNodeB filters out UEs performing voice services while selectingUEs to perform fast ANR measurement.

l The eNodeB does not select the UEs with bearers of QCI 1 when selecting UEs thatnewly access the network or are handed over to the cell.

l For UEs that are already selected for fast ANR measurement, the eNodeB uses ameasurement control policy depending on the value of theGlobalProcSwitch.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 QCIof 1.

– When this parameter is set to DISABLE, the eNodeB sends an RRC ConnectionReconfiguration message to delete fast ANR measurements if the UE sets up bearerwith a QCI of 1.

l UEs read cell global identifications (CGIs) in sleep time during DRX. The sleep timestops 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 fixedinterval and encounter a higher probability that the sleep time stops. After a CGI isacquired, the identified cell is automatically configured as a neighboring cell.

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-assistedmeasurement is started even for voice users to avoid call drops. If user-number-based measurement forMLB is enabled, MLB does not select voice users for load balancing.

When VoLTE is deployed, it is recommended that GlobalProcSwitch.VoipWithGapMode be set toDISABLE 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 1bearers for proactive PCI conflict detection. In addition, the eNodeB sends A3 and A4

eRANVoLTE Feature Parameter Description 5 Special Processing by Other Features

measurement configurations to the selected UEs, instructing the UEs to measure their servingfrequencies and neighboring E-UTRAN frequencies. For UEs that are already selected, theeNodeB uses a measurement control policy depending on the value of theGlobalProcSwitch.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, continuousmeasurement 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 Reconfigurationmessage to delete the measurement configuration if the UE sets up a bearer with a QCIof 1.

Carrier Aggregationl 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 eNodeBselects UEs for measurement based on the GlobalProcSwitch.VoipWithGapMode parametersetting:

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-RATmeasurement.– 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 serviceslater, the eNodeB updates configurations to delete existing periodic inter-frequencyor inter-RAT measurement of the UE. The UE is selected for measurement decisionuntil the UE releases voice services and is selected for the second time.

Mobility Load Balancingl LOFD-001032 Intra-LTE Load Balancing

The eNodeB transfers UEs based on the PRB usage. The eNodeB may transfer UEsperforming voice services for small-bandwidth cells. The voice quality of transferredUEs may be affected.

l LOFD-070215 Intra-LTE User Number Load BalancingFor user-number-based intra-LTE load balancing, the eNodeB does not transfer UEsperforming voice services.

l LOFD-001045 Inter-RAT Load Sharing to GERAN and LOFD-001044 Inter-RAT LoadSharing to UTRANDuring inter-RAT load balancing, the eNodeB selects the UEs to be transferred based onPRB-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 BundlingAfter the LOFD-001109 DL Non-GBR Packet Bundling feature is enabled, the schedulingpriority of voice services is no longer the highest priority. This feature is not recommendedfor VoLTE when there are many voice users because this feature may slightly affect voicequality.

6 Related Features

This chapter describes the relationships between VoLTE-related features and other features.

eRANVoLTE Feature Parameter Description 6 Related Features

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 channelconditions vary. Consequently, the IBLER may not converge on a target value. To solve thisproblem, closed-loop power control can be enabled to adjust UE transmit power for thePUSCH.

Mutually Exclusive Features

Impacted Featuresl LBFD-002017 DRX

If the value of the DrxParaGroup.LongDrxCycle parameter for QCI of 1 is set to avalue greater than the semi-persistent scheduling period (20 ms), the eNodeB does notactivate downlink semi-persistent scheduling.

l LOFD-001036 RAN Sharing with Common CarrierVoice services have a high scheduling priority and are sensitive to scheduling delays.Therefore, uplink and downlink semi-persistent scheduling does not consider theconfigured proportions of PRBs that can be allocated to different operators.

l LBFD-002005 DL Asynchronous HARQThe HARQ retransmission for DL semi-persistently scheduled data is performed byusing dynamic scheduling.

l LBFD-002006 Uplink Synchronization HARQWhen the activated retransmission for UL semi-persistent scheduling conflicts withhigher-priority scheduling, adaptive HARQ retransmission is used.

l LAOFD-001001 LTE-A IntroductionAccording 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 TM9When TM9 UEs use SPS scheduling, the MIMO scheme for the UEs in PDSCH istransmit 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.– Uplink VoIP semi-persistent scheduling and uplink delay-based dynamic scheduling

can be enabled for the same cell at the same time. When the conditions for bothfeatures are met, uplink VoIP semi-persistent scheduling takes precedence.

l Uplink RLC segmentation enhancement– LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentation

enhancement cannot take effect for the same UE at the same time.

– LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentationenhancement 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 ituses fixed MCSs and PRBs for data transmission and cannot well adapt to changes inchannel conditions.

l LBFD-081104 UL Compensation Scheduling

Uplink VoIP semi-persistent scheduling and uplink compensation scheduling cannot takeeffect for the same UE at the same time.

6.2 LOFD-001048 TTI Bundling

Impacted Featuresl LBFD-002017 DRX and LOFD-001105 Dynamic DRX

– If a UE is in the TTI bundling state, the eNodeB instructs the UE to enter DRXmode 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 afteractivating TTI bundling. An exception is that if the UE is performing ANRmeasurement in DRX mode, the eNodeB does not instruct the UE to exit DRXmode.

l LAOFD-001001 LTE-A Introduction

According to 3GPP TS 36.331, TTI bundling cannot be configured if a CA UE performsdata transmission in the uplink. After a CA UE enters the TTI bundling state, thesecondary serving cell (SCell) of this UE will be automatically deleted and CA is nolonger activated for UEs that are already in the TTI bundling state.

l Uplink RLC segmentation enhancement

– Uplink RLC segmentation enhancement and TTI bundling can be enabled for thesame cell at the same time.

– Uplink RLC segmentation enhancement and TTI bundling cannot take effect for thesame 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 RRCConnection Reconfiguration messages. When UEs are moving at high or ultra highspeed, their channel conditions change rapidly. As a result, the UEs frequently enter andexit the TTI bundling state, which increases signaling load on the Uu interface, degradesvoice quality, and increase the probability of service drops. Therefore, TTI bundling isnot recommended in high- or ultra-high-movement scenarios.

6.3 Uplink RLC Segmentation Enhancement

Impacted Featuresl LOFD-001016 VoIP Semi-persistent Scheduling

– LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentationenhancement can be enabled for the same cell at the same time.

– LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentationenhancement cannot take effect for the same UE at the same time.

l LOFD-001048 TTI Bundling– 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 RLCsegmentation enhancement takes effect.

6.4 LOFD-081229 Voice Characteristic AwarenessScheduling

Prerequisite Featuresl LBFD-002025 Basic Schedulingl LOFD-00101502 Dynamic Scheduling

– Uplink VoIP semi-persistent scheduling and uplink delay-based dynamic schedulingcannot take effect for the same UE at the same time.

– Uplink VoIP semi-persistent scheduling and uplink delay-based dynamic schedulingcan be enabled for the same cell at the same time. When the conditions for bothfeatures are met, uplink VoIP semi-persistent scheduling takes precedence.

6.5 LBFD-081104 UL Compensation Scheduling

Prerequisite Featuresl LBFD-002025 Basic Schedulingl LOFD-00101502 Dynamic Scheduling

Impacted Features

LOFD-001016 VoIP Semi-persistent Scheduling

Uplink VoIP semi-persistent scheduling and uplink compensation scheduling cannot takeeffect for the same UE at the same time.

6.6 LBFD-081105 Voice-Specific AMC

Prerequisite Featuresl LBFD-001006 AMCl LBFD-002025 Basic Schedulingl LOFD-00101502 Dynamic Scheduling

LOFD-001016 VoIP Semi-persistent Scheduling and LBFD-081105 Voice-SpecificAMC can be enabled for the same cell at the same time. However, voice-specific AMCtakes effect only for dynamic scheduling of VoLTE users.

l LOFD-001048 TTI BundlingLOFD-001048 TTI Bundling and LBFD-081105 Voice-Specific AMC can be enabledfor the same cell at the same time. However, voice-specific AMC applies only to VoLTEusers not in the TTI bundling state.

l RLC segmentation enhancementThe uplink IBLER of the voice user cannot converge to the target value when RLCsegmentation enhancement takes effect.

6.7 Other FeaturesThis chapter describes other features related to VoLTE.

Table 6-1 Other features

VoLTE-related Feature Description

LBFD-002023 AdmissionControl

For details, see Admission and Congestion Control FeatureParameter Description.

LBFD-002024 CongestionControl

For details, see Admission and Congestion Control FeatureParameter Description.

LOFD-00101502 DynamicScheduling

For details, see Scheduling Feature Parameter Description.

LBFD-002016 DynamicDownlink PowerAllocation

This VoLTE-related feature is associated with LOFD-001016VoIP Semi-persistent Scheduling. For details about theimpact on other features, see Power Control FeatureParameter Description.The downlink semi-persistent scheduling algorithm providesthe initial block error rate (IBLER) of downlink voiceservices as an input to the downlink power controlalgorithm. The IBLER is a prerequisite for PDSCH poweradjustment in semi-persistent scheduling mode.

LBFD-002026 UplinkPower Control

This VoLTE-related feature is associated with LOFD-001016VoIP Semi-persistent Scheduling. For details about theimpact on other features, see Power Control FeatureParameter Description.The uplink semi-persistent scheduling algorithm providesthe uplink IBLER as an input to the uplink power controlalgorithm. The IBLER is a prerequisite for PUSCH poweradjustment in semi-persistent scheduling mode. If uplinksemi-persistent scheduling is enabled, it is recommendedthat the CloseLoopSpsSwitch option of theCellAlgoSwitch.UlPcAlgoSwitch parameter be selected toensure that the uplink IBLER converges on the targetIBLER.

LOFD-001017 RObustHeader Compression(ROHC)

For details, see ROHC Feature Parameter Description.

VoLTE-related Feature Description

LBFD-002017 DRX The following are the relationships between DRX and TTIbundling 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 toperform ANR measurement.

l If a UE is in DRX mode, the eNodeB instructs the UE toexit DRX mode after activating TTI bundling. Anexception is that if the UE is performing ANRmeasurement in DRX mode, the eNodeB does notinstruct the UE to exit DRX mode.

l When the long DRX cycle for QCI 1 is greater than thesemi-persistent scheduling interval (for example, always20 ms for FDD), downlink semi-persistent schedulingdoes not take effect.

l After DRX is enabled, preallocation does not take effect.Preallocation decreases the probability of PDCCH falsedetection, which may cause packet loss, and thereforeimproves voice quality.

For more information, see DRX and Signaling ControlFeature Parameter Description.

Intra-frequency handover For details, see Intra-RAT Mobility Management inConnected Mode Feature Parameter Description.

Inter-frequency handover For details, see Intra-RAT Mobility Management inConnected Mode Feature Parameter Description.

Inter-RAT handover For details, see Inter-RAT Mobility Management inConnected Mode Feature Parameter Description andSRVCC Feature Parameter Description.

7 Network Impact

This chapter describes the impact of the VoIP-related features on the network.

eRANVoLTE Feature Parameter Description 7 Network Impact

7.1 LOFD-001016 VoIP Semi-persistent Scheduling

System CapacityAfter semi-persistent scheduling is enabled, PDCCH resources do not hinder voice servicecapacity because PDCCH resources are consumed only when semi-persistent scheduling isinitially activated or reactivated or when semi-persistently allocated resources are released.Compared with dynamic scheduling, enabling semi-persistent scheduling increases thenumber of supported voice service users by more than 30% in simulation case 1, according tothe simulation conditions and capacity evaluation method specified in an appendix of 3GPPTS 36.814.

During semi-persistent scheduling, the MCS index cannot exceed 15. This restriction mayincrease 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 MCSindex for voice users near the cell center is 26, two RBs are required in the uplink and one RBin the downlink (dual-stream mode) when dynamic scheduling is enabled. Under the samecondition, semi-persistent scheduling requires three RBs in both the uplink and downlink dueto the MCS index restriction (the largest MCS index is 15). That is, compared with dynamicscheduling, semi-persistent scheduling for voice users near the cell center consumes more RBresources. Therefore, the amount of RB resource for data services decreases (compared withthat when semi-persistent scheduling is disabled), and the throughput of data services mayalso decrease.

After downlink semi-persistent scheduling is enabled and voice services are set up, theeNodeB reserves HARQ processes for downlink semi-persistent scheduling. Before the nextinitial transmission in semi-persistent scheduling, the HARQ processes for downlink semi-persistent scheduling may not be released. As a result, periodic data for semi-persistentscheduling cannot be sent. The HARQ processes are reserved to avoid such situation. TheHARQ processes reserved for downlink semi-persistent scheduling cannot be used fordynamic scheduling for other service type of the UE, such as data service. In combinedservices where voice and data services coexist, the HARQ processes that can be used by dataservices therefore decrease. Compared with the scenario where dynamic scheduling is used byboth voice and data services, the use of downlink semi-persistent scheduling for voiceservices affects the throughput of data services, specifically, when the volume of the dataservices is large (such as when full buffer service is performed). When there are multipleusers or a small amount of data volume, the impact of reserving HARQ processes is smallbecause the scheduling chances for UEs are discretely distributed or a few HARQ processesare required for data services.

Network PerformanceFixed-position resource allocation is adopted after semi-persistent scheduling is activated.Compared with dynamic scheduling, semi-persistent scheduling may increase the schedulingwait time.

7.2 LOFD-001048 TTI Bundling

System CapacityNo impact.

Network PerformanceLOFD-001048 TTI bundling increases the cell edge coverage of PUSCH, improves MCS inuplink weak-coverage areas, and reduces the packet loss rate. However, this feature increasessignaling overheads because the entry and exit of the TTI bundling state requires theexchange of RRC messages. When the number of TTI bundling mode reconfigurationmessages (indicated by the counters L.Signal.Num.TtiBundling.Enter andL.Signal.Num.TtiBundling.Exit) increases, the average board CPU usage (indicated by thecounter VS.BBUBoard.CPULoad.Mean (%)) slightly increases.

As defined in 3GPP protocols, TTI bundling uses a maximum of three PRBs and adoptsQPSK with the highest MCS order of 10. That is, after TTI bundling is enabled, the maximumnumber of TBS that can be transmitted is 504 bits. This restricts the uplink throughput of TTIbundling. The logical channel priority of signaling and voice services is higher than that ofdata services, which means that UEs preferentially send signaling and voice services. As aresult, the uplink throughput of data services is further restricted.

7.3 Uplink RLC Segmentation Enhancement

Network PerformanceUplink RLC segmentation enhancement can increase the mean opinion score (MOS)ofVoLTE 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 residualBLER (RBLER).

7.4 LOFD-081229 Voice Characteristic AwarenessScheduling

Network PerformanceUplink 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 loadedand DRX is enabled. However, this function increases RB overheads and lowers MCSindexes allocated to voice users; when there are many voice users, this function also reducescell throughput.

Uplink delay-based dynamic scheduling can be used in heavy traffic scenarios to improvevoice 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, pingdelay, time of transition from idle mode to connected mode, and attach delay.

l Slightly decreases cell throughput.

Independent configuration for voice inactivity timer has the following impacts on networkperformance:

l If the value of the RrcConnStateTimer.UeInactiveTimerQci1 parameter is smaller thanthat of the RrcConnStateTimer.UeInactiveTimer parameter, the online duration ofvoice service UEs becomes short and voice service drop rate decreases when there is nodata transmission in the uplink and downlink while waiting for the callee to answer thecall.

l If the value of the RrcConnStateTimer.UeInactiveTimerQci1 parameter is greater thanthat of the RrcConnStateTimer.UeInactiveTimer parameter, the online duration ofvoice service UEs becomes long, RRC connection request number decreases, number ofnormal 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 trafficscenarios, shorten voice packet delays, and improve voice quality. However, this featureincreases RB and CCE overheads; when there are many voice users, this feature also reducescell throughput.

In addition, uplink compensation scheduling decreases the possibility that uplink controlinformation of voice users is transmitted over PUCCH and increases the possibility thatuplink control information of voice users is transmitted over PUSCH. This affects thepossibility that PDSCH ACK/NACK is detected as DTX and slightly increases VoLTEdownlink 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 Performancel This feature affects voice quality in the following aspects:

– If the CellUlschAlgo.SinrAdjTargetIblerforVoLTE parameter is set to a smallervalue, the MCS indexes selected for uplink voice services are smaller. For voiceusers in the cell center, the uplink QCI 1 packet loss rate may slightly decrease andvoice quality almost remains unchanged. For voice users not in the cell center, thenumber of uplink RLC segments increases and the uplink QCI 1 packet loss ratemay increase in the case of heavy load; as a result, voice quality becomes worse andvoice capacity decreases.

– If the CellUlschAlgo.SinrAdjTargetIblerforVoLTE parameter is set to a largervalue, 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 qualitybecomes worse. In the downlink, the QCI 1 packet loss rate also increases and voicequality also becomes worse because the demodulation performance deteriorates forACKs/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 ofconsumed RBs increases. When there are many voice users, cell throughput decreases.

7.7 Other FeaturesThis chapter describes the impact of other features related to VoLTE on system capacity andnetwork performance.

Table 7-1 Impact of other VoLTE-related features on system capacity and networkperformance

Feature Description

LBFD-002023 AdmissionControl

Admission control maximizes system capacity whileproviding users with satisfied QoS, which is indicated by thevoice service MOS.

LBFD-002024 CongestionControl

Congestion control maximizes system capacity whilepreferentially providing satisfied QoS for high-priority UEs.The priority refers to the allocation/retention priority (ARP).Congestion control ensures a high satisfaction rate of voiceservice users in congested cells.

Voice packets are generally small. If semi-persistentscheduling is disabled, voice service capacity is mainlysubject to PDCCH resources. If a continuous increase in thenumber of voice service users causes PDCCH resources tobecome insufficient first, the cell capacity decreases.

LBFD-002016 DynamicDownlink PowerAllocation

For details, see Power Control Feature ParameterDescription.

LBFD-002026 UplinkPower Control

For details, see Power Control Feature ParameterDescription.

LOFD-001017 RObustHeader Compression(ROHC)

For details, see ROHC Feature Parameter Description.

Feature Description

LBFD-002017 DRX DRX extends voice service delay because it introduces thesleep time. If DRX parameter settings are inappropriate,voice service capacity will decrease or the packet loss rateincreases because voice services cannot be scheduled in real-time. For details about the impact of DRX on networkperformance, see DRX Feature Parameter Description.

Intra-frequency handover For details, see Intra-RAT Mobility Management inConnected Mode Feature Parameter Description.

Inter-frequency handover For details, see Intra-RAT Mobility Management inConnected Mode Feature Parameter Description.

Inter-RAT handover For details, see Inter-RAT Mobility Management inConnected Mode Feature Parameter Description andSRVCC Feature Parameter Description.

8 Voice Service Performance Evaluation

8.1 QoS RequirementsSection 6.1.7 in 3GPP TS 23.203 of Release 10 provides the QoS requirements of serviceswith 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 DelayBudget (ms)

Packet ErrorLoss Rate

Typical Service

GBR 2 100 10-2 Voice service

l The preceding Packet Delay Budget indicates the threshold delay between UE and PDNgateway (P-GW). The corresponding user satisfaction rate is 98%.

l The preceding Packet Error Loss Rate indicates the threshold proportion of SDUs thatare not successfully sent from the data link layer of the transmission end to thecorresponding upper layer of the receive end.

The packet delay budget, uplink and downlink Uu interface packet loss rate, and downlinkPDCP packet loss rates of QCI 1 services can be measured using counters. For details aboutrelated counters, see 9.2.4.2 Voice QoS.

8.2 Quality EvaluationThe mean opinion score (MOS) is an important indicator for evaluating voice quality. MOS-based evaluation involves subjective evaluation, objective evaluation, and measurement-basedevaluation.

8.2.1 Subjective EvaluationMOS is a subjective measurement where listeners perceive raw speech materials andprocessed degraded speech materials and then score speech quality.

Table 8-2 lists the MOS standards defined in ITU-T G.107.

eRANVoLTE Feature Parameter Description 8 Voice Service Performance Evaluation

Table 8-2 MOS standards

Quality Level Auditory Distortion Extent Required AuditoryEffort

5 Excellent Distortion not noticed Listening in a relaxedmanner

4 Good Distortion noticed, but notunpleasant

Listening with a little effort

3 Fair Distortion noticed, andannoying

Listening in an attentivemanner

2 Poor Unpleasant but not annoying Listen with much effort

1 Bad Unpleasant and annoying Cannot understand thecontents

8.2.2 Objective EvaluationPerceptual Evaluation of Speech Quality (PESQ), defined in ITU-T P862, is a mainstreammethod of objectively evaluating AMR-NB speech quality. Perceptual Objective ListeningQuality Assessment (POLQA), defined in ITU-T P863, is the evolution of PESQ; POLQAsupports 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 SpeechLevel Analyzer (DSLA).

Objective evaluation is commonly used by operators to evaluate speech quality. However, itrequires the collaboration of drive tests. As it cannot monitor speech quality in real time, it isgenerally used for tests in labs, network entry tests, and third-party evaluation of networkquality.

8.2.3 Measurement-based Evaluation

Overview

Using the third-party's drive test tools to evaluate speech quality is time and cost consumingand cannot monitor speech quality in real time. Therefore, it is important for vendors todevelop their own measurement-based evaluation methods. Huawei uses a Voice QualityMonitoring (VQM) algorithm to calculate the MOS scores of uplink and downlink voiceservices on the Uu interface.

VQM is mainly used for network monitoring, network optimization, VIP guarantee, and usercomplaint handling. VQM reduces the necessity of drive tests required for obtaining voicequality.

VQM applies only to the AMR speech codec scenario. VQM is controlled by theEnodebAlgoSwitch.VQMAlgoSwitch parameter, which is turned off by default. After thisparameter is turned on, the eNodeB automatically identifies whether the eNodeB supportsAMR speech codec. The eNodeB calculates only the MOS of voice services that use theAMR speech codec scheme.

VQM PrinciplesFigure 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 errorrate (FER) on the Uu interface, long frame error rate (LFER), and handover state. Whendetecting that the delay variation for voice packets of QCI of 1 exceeds theVQMALGO.ULDelayJitter parameter value, the eNodeB determines that a packet lossoccurs.

2. Then, the eNodeB inputs the monitoring results to the Huawei proprietary voice qualityindicator (VQI) model and estimates the MOS scores of uplink and downlink voiceservices on the Uu interface at intervals of 2.5 seconds. The VQI model is based on thealgorithms specified in ITU-T P.863 and simulates an MOS score using mathematicalformulas.– 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.

The voice quality monitoring results including statistics about cell-level voice quality counters anduser-level performance monitoring results as well as CHRs do not include user privacyinformation.

Voice Quality Evaluation

The eNodeB evaluates voice quality based on the MOS provided by the VQM and voicequality thresholds. In addition, the eNodeB collects the statistics of counters related to voicequality, as listed in Table 8-3.

Table 8-3 Voice quality evaluation rules and related counters

MOS Scores Provided by the VQI Model Voice QualityLevel

Related Counters

MOS > VQMAlgo.VqiExcellentThd Excellent For details, see Table9-8.

VQMAlgo.VqiGoodThd < MOS ≤VQMAlgo.VqiExcellentThd

Good For details, see Table9-9.

VQMAlgo.VqiPoorThd < MOS ≤VQMAlgo.VqiGoodThd

Fair For details, see Table9-10.

VQMAlgo.VqiBadThd < MOS ≤VQMAlgo.VqiPoorThd

Poor For details, see Table9-11.

MOS ≤ VQMAlgo.VqiBadThd Bad For details, see Table9-12.

Application Limitations

AMR coding rate is an important input for the VQI model. Currently, the VQM algorithmcannot monitor the AMR coding rate in real time. If the AMR coding rate changed, the outputof the VQI model would be inaccurate. Up to now, it has not been found that the AMR codingrate changes in any scenario.

In the following scenarios, the eNodeB cannot determine the AMR coding rate and thereforedoes 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 IPheader length is different after the encryption. The IP header of a voice packet mayinclude an Authentication Header (AH) or (Encapsulation Security Payload (ESP) headerfor encryption. The length of AHs is not fixed, and the latter part of ESP headers isencrypted, and the latter part of ESP headers is encrypted.

8.3 Capacity EvaluationThe voice service capacity can be evaluated based on the number of users performing QCI 1services. The related counters are listed below and described in 9.2.4.4 Voice Capacity.

l L.Traffic.ActiveUser.UL.QCI.1l L.Traffic.ActiveUser.DL.QCI.1

8.4 Performance EvaluationThe performance of voice services can be evaluated using the following KPIs, which aredescribed in 9.2.4.1 Voice KPIs

l E-RAB Setup Success Rate (VoIP)l Call Drop Rate (VoIP)

9 Engineering Guidelines

9.1 OverviewThe engineering guidelines of features or functions listed in Table 9-1 are not included in thisdocument.

Table 9-1 VoLTE-related functions and features

Features/Functions Engineering Guidelines

LBFD-002023 Admission Control For details about the engineering guidelines for thisfeature, see Admission and Congestion ControlFeature Parameter Description.

LBFD-002024 Congestion Control For details about the engineering guidelines for thisfeature, see Admission and Congestion ControlFeature Parameter Description.

For details about the engineering guidelines for thisfeature, see Scheduling Feature ParameterDescription.

Power control in dynamic scheduling For details about the engineering guidelines forpower control in dynamic scheduling, see PowerControl Feature Parameter Description.

QCI and RLC mode For details about the engineering guidelines forQCI and RLC mode, see QoS Management FeatureParameter Description.

LOFD-001017 RObust HeaderCompression (ROHC)

For details about the engineering guidelines for thisfeature, see ROHC Feature Parameter Description.

LOFD-001109 DL Non-GBR PacketBundling

For details about the engineering guidelines for thisfeature, see Scheduling Feature ParameterDescription.

eRANVoLTE Feature Parameter Description 9 Engineering Guidelines

Features/Functions Engineering Guidelines

Intra-frequency handover For details about the engineering guidelines for thisfunction, see Intra-RAT Mobility Management inConnected Mode.

Inter-frequency handover For details about the engineering guidelines for thisfunction, see Intra-RAT Mobility Management inConnected Mode.

Inter-RAT handover For details about the engineering guidelines forSRVCC, see SRVCC Feature ParameterDescription.For details about the engineering guidelines for PShandover, see Inter-RAT Mobility Management inConnected Mode.

LBFD-002017 DRX For details about the engineering guidelines for thisfeature, see DRX and Signaling Control FeatureParameter Description.

9.2 Basic Functions

9.2.1 When to Use Basic FunctionsUsers can determine whether to deploy IMS-based VoLTE services depending on whetherIMS is deployed, transmission delay, and voice service policies.

The E-UTRAN supports VoLTE after the IMS is deployed. However, VoLTE is not used inthe 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 inthe preceding scenarios. Turning off this switch prevents UEs from initiating voice servicesand prevents UEs performing voice services from handing over to the eNodeB. For details,see 3.2.2 VoLTE-Prohibited Scenario.

After the ENodeBAlgoSwitch.EutranVoipSupportSwitch is turned off, you also need to disable VoLTEin the corresponding tracking areas on the MME.

In other scenarios, turn on the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch so thatthe eNodeB supports IMS-based voice services.

In scenarios where E-UTRAN coverage is discontinuous, it is recommended that the SRVCCfunction be enabled.

If the MME supports the UE Radio Capability Match REQUEST and UE Radio CapabilityMatch RESPONSE messages introduced in 3GPP Release 11, it is recommended that theSupportS1UeCapMatchMsg option of the GlobalProcSwitch.ProtocolSupportSwitch

parameter be selected on the eNodeB side. By doing this, the MME considers the VoLTEmobility capability of the UE during the voice policy negotiation. In this manner, UEs that donot support SRVCC do not adopt VoLTE as the voice policy, thereby ensuring voicecontinuity.

It is recommended that the VQM function be enabled to monitor voice quality.

9.2.2 Required InformationNone

9.2.3 Deployment

9.2.3.1 Requirements

Operating Environmentl UEs must support VoLTE, and the EPC must support IMS.l Operators have deployed the IMS.

Transmission NetworkingVoLTE services have high requirements on end-to-end real-time delay. For example, when thetransmission delay between the eNodeB and EPC exceeds 20 ms, VoLTE is not appropriatefor the eNodeB.

For the requirements on transmission delay and jitter on S1 and X2 interfaces, see IP eRANEngineering Guide Feature Parameter Description.

LicenseNone

9.2.3.2 Data PreparationThere are three types of data sources:

l Network plan (negotiation not required): parameter values planned and set by theoperator

l Network plan (negotiation required): parameter values planned by the operator andnegotiated 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 MOto set the eNodeB voice service switch.

ParameterName

Parameter ID Data Source Setting Notes

Eutran VoipSupportSwitch

ENodeBAlgoSwitch.EutranVoipSupportSwitch

Network plan(negotiationnot required)

Set this parameter to ON(On) ifyou plan to use the VoLTE voicesolution.For details about the deploymentsuggestion of the VoLTE voicesolution, see 9.2.1 When to UseBasic Functions.

The following table describes the parameter that must be set in the GlobalProcSwitch MO todetermine whether the eNodeB supports voice mobility.

ParameterName

ProtocolProcedureSupportSwitch

GlobalProcSwitch.ProtocolSupportS-witch

If the MME supports the UERadio Capability MatchREQUEST and UE RadioCapability Match RESPONSEmessages introduced in 3GPPRelease 11, set this parameter toSupportS1UeCapMatchMsg(SupportS1UeCapMatchMsg).

The following table describes the parameter that must be set in the ENodeBAlgoSwitch MOto determine whether the eNodeB supports VQM.

ParameterName

Voice qualitymonitoringalgo switch

ENodeBAlgoSwitch.VQMAlgoSwitch

To monitor the voice quality, setthis parameter toVQM_ALGO_SWITCH_ON.

The following table describes the parameter that must be set in the RlcPdcpParaGroup MOto configure the PDCP discard timer.

ParameterName

Discard timer RlcPdcpParaGroup.DiscardTimer

If the voice service bearerplanning policy specified byoperators is QCI 5 multiplexingfor carrying voice packets, it isrecommended that this parameterfor QCI of 5 be set to 150 ms.Otherwise, set this parameter forQCI of 5 to Infinity.

9.2.3.3 Precautions

9.2.3.4 Hardware Adjustment

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 alsocontains other data for the new eNodeBs to be deployed.

Then, import the summary data file into the Configuration Management Express (CME) forbatch configuration.

For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guidefor the eNodeB, which is available in the eNodeB product documentation. The summary datafile may be a scenario-specific file provided by the CME or a customized file, depending onthe following conditions:

l The MOs in Table 9-2 are contained in a scenario-specific summary data file. In thissituation, 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. Inthis situation, customize a summary data file to include the MOs before you can set theparameters.

Table 9-2 Common data

MO Sheet in the SummaryData File

Parameter Group Remarks

ENodeBAlgoSwitch

ENodeBAlgoSwitch EutranVoipSupportSwitch User-definedtemplate

GlobalProcSwitch

GlobalProcSwitch ProtocolSupportSwitch User-definedtemplate

ENodeBAlgoSwitch

ENodeBAlgoSwitch VQMAlgoSwitch User-definedtemplate

RlcPdcpParaGroup

RlcPdcpParaGroup DiscardTimer User-definedtemplate

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, formultiple 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 > CustomizeSummary Data File (CME client mode), to customize a summary data file for batchreconfiguration.

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 ConfigurationData (U2000 client mode), or choose LTE Application > Export Data > Export Base StationBulk Configuration Data (CME client mode), to export the eNodeB data stored on the CMEinto 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 ConfigurationData (U2000 client mode), or choose LTE Application > Import Data > Import Base StationBulk 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 IncrementalScripts (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 singleeNodeB. The procedure is as follows:

Step 1 In the planned data area, click Base Station in the upper left corner of the configurationwindow.

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 chooseArea Management > Planned Area > Export Incremental Scripts (CME client mode), toexport and activate the incremental scripts.

----End

Using MML Commandsl Run the MOD ENODEBALGOSWITCH command to turn on the

EutranVoipSupportSwitch switch.

l Run the MOD GLOBALPROCSWITCH command and selectSupportS1UeCapMatchMsg.

l Run the MOD ENODEBALGOSWITCH command to turn on the VQMAlgoSwitch.

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

9.2.3.6 Activation ObservationTo check whether a UE can perform voice services after the EutranVoipSupportSwitchswitch is turned on, perform the following steps:

Step 1 Run the LST ENodeBAlgoSwitch command to check whether theEutranVoipSupportSwitch 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 5and QCI 1 in the S1 interface tracing task result on the U2000. Bearers for QCI of 5 and QCIof 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)

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.

CounterID

Counter Name Counter Description

1526726669

L.E-RAB.SuccEst.QCI.1

Number of successful E-RAB setups initiated by UEsfor services with the QCI of 1 in a cell

1526726677

L.E-RAB.SuccEst.QCI.5

Number of successful E-RAB setups initiated by UEsfor services with the QCI of 5 in a cell

Step 5 View the "voice support match indicator" IE in the UE RADIO CAPABILITY MATCHRESPONSE message in the S1 interface tracing task result on the U2000. If the value of the

IE is supported or not supported, the eNodeB can query a UE's capability in supportingVoLTE mobility and report the capability to the MME.

----End

9.2.3.7 Reconfiguration

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 oneNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure for feature deactivation is similar to that forfeature activation described in Using the CME to Perform Batch Configuration forExisting eNodeBs. In the procedure, modify parameters according to Table 9-3.

Table 9-3 Common data

ENodeBAlgoSwitch

ENodeBAlgoSwitch EutranVoipSupportS-witch

OFF(Off)

GlobalProcSwitch

GlobalProcSwitch ProtocolSupportSwitch Deselected

ENodeBAlgoSwitch

ENodeBAlgoSwitch VQMAlgoSwitch VQM_ALGO_SWITCH_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 describedfor feature activation.

Using MML Commandsl 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.

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

9.2.4 Performance MonitoringAfter common parameters are deployed, or after both common parameters and the featuresand functions in Table 9-1 are deployed, you can monitor voice service performance using thefollowing 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 voiceservices.

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 initiatedby UEs for services with the QCI of 1 in acell

1526726676 L.E-RAB.AttEst.QCI.5 Number of E-RAB setup attempts initiatedby UEs for services with the QCI of 5 in acell

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

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

1526727853 L.E-RAB.AttEst.PLMN.QCI.1

Number of E-RAB setup attempts initiatedby UEs of a specified operator for serviceswith the QCI of 1 in a cell

Number of E-RAB setup attempts initiatedby UEs of a specified operator for serviceswith the QCI of 5 in a cell

1526727854 L.E-RAB.SuccEst.PLMN.QCI.1

Number of successful E-RAB setupsinitiated by UEs of a specified operator forservices with the QCI of 1 in a cell

Number of successful E-RAB setupsinitiated by UEs of a specified operator forservices with the QCI of 5 in a cell

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

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.IntraFreq.PrepAttOut.VoIP

Number of intra-eNodeB intra-frequencyoutgoing handover attempts for UEsperforming voice services in a cell

1526729527 L.HHO.IntraeNB.InterFreq.PrepAttOut.VoIP

Number of intra-eNodeB inter-frequencyoutgoing handover attempts for UEsperforming voice services in a cell

1526729535 L.HHO.IntereNB.IntraFreq.PrepAttOut.VoIP

Number of inter-eNodeB intra-frequencyoutgoing handover attempts for UEsperforming voice services in a cell

1526729536 L.HHO.IntereNB.InterFreq.PrepAttOut.VoIP

Number of inter-eNodeB inter-frequencyoutgoing handover attempts for UEsperforming voice services in a cell

1526729537 L.HHO.IntereNB.InterFddTdd.PrepAttOut.VoIP

Number of inter-eNodeB inter-duplex-mode outgoing handover attempts for UEsperforming voice services in a cell

1526729529 L.HHO.IntraeNB.IntraFreq.ExecAttOut.VoIP

Number of intra-eNodeB intra-frequencyoutgoing handover executions for UEsperforming voice services in a cell

1526729530 L.HHO.IntraeNB.InterFreq.ExecAttOut.VoIP

Number of intra-eNodeB inter-frequencyoutgoing handover executions for UEsperforming voice services in a cell

1526729538 L.HHO.IntereNB.IntraFreq.ExecAttOut.VoIP

Number of inter-eNodeB intra-frequencyoutgoing handover executions for UEsperforming voice services in a cell

1526729539 L.HHO.IntereNB.InterFreq.ExecAttOut.VoIP

Number of inter-eNodeB inter-frequencyoutgoing handover executions for UEsperforming voice services in a cell

1526729540 L.HHO.IntereNB.InterFddTdd.ExecAttOut.VoIP

Number of inter-eNodeB inter-duplex-mode outgoing handover executions forUEs performing voice services in a cell

1526729532 L.HHO.IntraeNB.IntraFreq.ExecSuccOut.VoIP

Number of successful intra-eNodeB intra-frequency outgoing handovers for UEsperforming voice services in a cell

1526729533 L.HHO.IntraeNB.InterFreq.ExecSuccOut.VoIP

Number of successful intra-eNodeB inter-frequency outgoing handovers for UEsperforming voice services in a cell

1526729541 L.HHO.IntereNB.IntraFreq.ExecSuccOut.VoIP

Number of successful inter-eNodeB intra-frequency outgoing handovers for UEsperforming voice services in a cell

1526729542 L.HHO.IntereNB.InterFreq.ExecSuccOut.VoIP

Number of successful inter-eNodeB inter-frequency outgoing handovers for UEsperforming voice services in a cell

1526729543 L.HHO.IntereNB.InterFddTdd.ExecSuccOut.VoIP

Number of successful inter-eNodeB inter-duplex-mode outgoing handovers for UEsperforming voice services in a cell

1526729528 L.HHO.IntraeNB.InterFddTdd.PrepAttOut.VoIP

Number of intra-eNodeB inter-duplex-mode outgoing handover attempts for UEsperforming voice services in a cell

1526729531 L.HHO.IntraeNB.InterFddTdd.ExecAttOut.VoIP

Number of intra-eNodeB inter-duplex-mode outgoing handover executions forUEs performing voice services in a cell

1526729534 L.HHO.IntraeNB.InterFddTdd.ExecSuccOut.VoIP

Number of successful intra-eNodeB inter-duplex-mode outgoing handovers for UEsperforming voice services in a cell

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)

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

CounterID

1526726686

L.E-RAB.AbnormRel.QCI.1

Number of abnormal E-RAB releases for serviceswith the QCI of 1 in a cell

1526726694

L.E-RAB.AbnormRel.QCI.5

Number of abnormal E-RAB releases for serviceswith the QCI of 5 in a cell

1526726687

L.E-RAB.NormRel.QCI.1

Number of normal E-RAB releases for serviceswith the QCI of 1 in a cell

1526726695

L.E-RAB.NormRel.QCI.5

Number of normal E-RAB releases for serviceswith the QCI of 5 in a cell

1526727871

L.E-RAB.AbnormRel.PLMN.QCI.1

Number of abnormal releases of activated E-RABsof a specified operator for services with the QCI of1 in a cell

1526727879

L.E-RAB.AbnormRel.PLMN.QCI.5

Number of abnormal releases of activated E-RABsof a specified operator for services with the QCI of5 in a cell

1526727872

L.E-RAB.NormRel.PLMN.QCI.1

Number of normal E-RAB releases of a specifiedoperator for services with the QCI of 1 in a cell

1526727880

L.E-RAB.NormRel.PLMN.QCI.5

Number of normal E-RAB releases of a specifiedoperator for services with the QCI of 5 in a cell

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)

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 onthe Uu interface and the downlink PDCP packet discard rate of voice services.

Table 9-7 Counters used to monitor the packet loss rate

CounterID

1526727961

L.Traffic.UL.PktLoss.Loss.QCI.1

Number of discarded uplink traffic PDCP SDUsfor DRB services with the QCI of 1 in a cell

1526727962

L.Traffic.UL.PktLoss.Tot.QCI.1

Number of expected uplink traffic data packetsfor DRB services with the QCI of 1 in a cell

1526727934

L.Traffic.DL.PktUuLoss.Loss.QCI.1

Number of discarded downlink traffic PDCPSDUs for DRB services with the QCI of 1 in acell over the Uu interface

1526727935

L.Traffic.DL.PktUuLoss.Tot.QCI.1

Number of transmitted downlink traffic PDCPSDUs for DRB services with the QCI of 1 in acell over the Uu interface

1526726833

L.PDCP.Tx.Disc.Trf.SDU.QCI.1

Number of downlink traffic SDUs discarded bythe PDCP layer for services with the QCI of 1 ina cell

1526727889

L.PDCP.Tx.TotRev.Trf.SDU.QCI.1

Number of transmitted downlink traffic PDCPSDUs for services with the QCI of 1 in a cell

1526736684

L.Traffic.UL.PktLoss.Loss.PLMN.QCI.1

Total number of discarded uplink PDCP SDUsfor traffic services with a QCI of 1 for a specificoperator in a cell

1526736686

L.Traffic.UL.PktLoss.Tot.PLMN.QCI.1

Total number of expected uplink data packets forDRB services with a QCI of 1 for a specificoperator in a cell

1526736737

L.Traffic.DL.PktUuLoss.Loss.PLMN.QCI.1

Total number of discarded downlink PDCPSDUs for traffic services with a QCI of 1 for aspecific operator in a cell

1526736739

L.Traffic.DL.PktUuLoss.Tot.PLMN.QCI.1

Total number of expected downlink data packetsfor DRB services with a QCI of 1 for a specificoperator in a cell

1526736680

L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.1

Number of downlink traffic SDUs discarded bythe PDCP layer for services with a QCI of 1 fora specific operator in a cell

1526736682

L.PDCP.Tx.TotRev.Trf.SDU.PLMN.QCI.1

Number of transmitted downlink traffic PDCPSDUs for services with a QCI of 1 for a specificoperator in a cell

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 QualityTable 9-8, Table 9-9, Table 9-10, Table 9-11, and Table 9-12 describe the counters used tomonitor the distribution of uplink and downlink voice service QoS.

Table 9-8 Counters with the voice quality being Excellent

1526728411 L.Voice.VQI.UL.Excellent.Times

Number of times uplink voice quality is Excellent

1526728416 L.Voice.VQI.DL.Excellent.Times

Number of times downlink voice quality isExcellent

1526732687 L.Voice.VQI.AMRWB.UL.Excellent.Times

Number of times uplink voice quality of AMR-WB services is Excellent

1526732692 L.Voice.VQI.AMRWB.DL.Excellent.Times

Number of times downlink voice quality of AMR-WB services is Excellent

1526736660 L.Voice.VQI.UL.Excellent.Times.PLMN

Number of times uplink voice quality is Excellentfor a specific operator in a cell

1526736665 L.Voice.VQI.DL.Excellent.Times.PLMN

Number of times downlink voice quality isExcellent for a specific operator in a cell

1526736670 L.Voice.VQI.AMRWB.UL.Excellent.Times.PLMN

Number of times uplink voice quality of AMR-WB services is Excellent for a specific operator ina cell

1526736675 L.Voice.VQI.AMRWB.DL.Excellent.Times.PLMN

Number of times downlink voice quality of AMR-WB services is Excellent for a specific operator ina cell

Table 9-9 Counters with the voice quality being Good

1526728412 L.Voice.VQI.UL.Good.Times

Number of times uplink voice quality is Good

1526728417 L.Voice.VQI.DL.Good.Times

Number of times downlink voice quality is Good

1526732688 L.Voice.VQI.AMRWB.UL.Good.Times

Number of times uplink voice quality of AMR-WB services is Good

1526732693 L.Voice.VQI.AMRWB.DL.Good.Times

Number of times downlink voice quality of AMR-WB services is Good

1526736661 L.Voice.VQI.UL.Good.Times.PLMN

Number of times uplink voice quality is Good fora specific operator in a cell

1526736666 L.Voice.VQI.DL.Good.Times.PLMN

Number of times downlink voice quality is Goodfor a specific operator in a cell

1526736671 L.Voice.VQI.AMRWB.UL.Good.Times.PLMN

Number of times uplink voice quality of AMR-WB services is Good for a specific operator in acell

1526736676 L.Voice.VQI.AMRWB.DL.Good.Times.PLMN

Number of times downlink voice quality of AMR-WB services is Good for a specific operator in acell

Table 9-10 Counters with the voice quality being Accept

1526728413 L.Voice.VQI.UL.Accept.Times

Number of times uplink voice quality is Accept

1526728418 L.Voice.VQI.DL.Accept.Times

Number of times downlink voice quality is Accept

1526732689 L.Voice.VQI.AMRWB.UL.Accept.Times

Number of times uplink voice quality of AMR-WB services is Accept

1526732694 L.Voice.VQI.AMRWB.DL.Accept.Times

Number of times downlink voice quality of AMR-WB services is Accept

1526736662 L.Voice.VQI.UL.Accept.Times.PLMN

Number of times uplink voice quality is Acceptfor a specific operator in a cell

1526736667 L.Voice.VQI.DL.Accept.Times.PLMN

Number of times downlink voice quality is Acceptfor a specific operator in a cell

1526736672 L.Voice.VQI.AMRWB.UL.Accept.Times.PLMN

Number of times uplink voice quality of AMR-WB services is Accept for a specific operator in acell

1526736677 L.Voice.VQI.AMRWB.DL.Accept.Times.PLMN

Number of times downlink voice quality of AMR-WB services is Accept for a specific operator in acell

Table 9-11 Counters with the voice quality being Poor

1526728414 L.Voice.VQI.UL.Poor.Times

Number of times uplink voice quality is Poor

1526728419 L.Voice.VQI.DL.Poor.Times

Number of times downlink voice quality is Poor

1526732690 L.Voice.VQI.AMRWB.UL.Poor.Times

Number of times uplink voice quality of AMR-WB services is Poor

1526732695 L.Voice.VQI.AMRWB.DL.Poor.Times

Number of times downlink voice quality of AMR-WB services is Poor

1526732890 L.Voice.NormRel.UL.LowQuality

Number of normally released voice calls (pooruplink voice quality)

1526732891 L.Voice.NormRel.DL.LowQuality

Number of normally released voice calls (poordownlink voice quality)

1526736663 L.Voice.VQI.UL.Poor.Times.PLMN

Number of times uplink voice quality is Poor for aspecific operator in a cell

1526736668 L.Voice.VQI.DL.Poor.Times.PLMN

Number of times downlink voice quality is Poorfor a specific operator in a cell

1526736673 L.Voice.VQI.AMRWB.UL.Poor.Times.PLMN

Number of times uplink voice quality of AMR-WB services is Poor for a specific operator in acell

1526736678 L.Voice.VQI.AMRWB.DL.Poor.Times.PLMN

Number of times downlink voice quality of AMR-WB services is Poor for a specific operator in acell

Table 9-12 Counters with the voice quality being Bad

1526728415 L.Voice.VQI.UL.Bad.Times

Number of times uplink voice quality is Bad

1526728420 L.Voice.VQI.DL.Bad.Times

Number of times downlink voice quality is Bad

1526732691 L.Voice.VQI.AMRWB.UL.Bad.Times

Number of times uplink voice quality of AMR-WB services is Bad

1526732696 L.Voice.VQI.AMRWB.DL.Bad.Times

Number of times downlink voice quality of AMR-WB services is Bad

1526732892 L.Voice.UL.Silent.Num

Number of times uplink voice call is silent

1526732893 L.Voice.DL.Silent.Num

Number of times downlink voice call is silent

1526736664 L.Voice.VQI.UL.Bad.Times.PLMN

Number of times uplink voice quality is Bad for aspecific operator in a cell

1526736669 L.Voice.VQI.DL.Bad.Times.PLMN

Number of times downlink voice quality is Badfor a specific operator in a cell

1526736674 L.Voice.VQI.AMRWB.UL.Bad.Times.PLMN

Number of times uplink voice quality of AMR-WB services is Bad for a specific operator in a cell

1526736679 L.Voice.VQI.AMRWB.DL.Bad.Times.PLMN

Number of times downlink voice quality of AMR-WB services is Bad for a specific operator in a cell

9.2.4.4 Voice Capacity

Number of UEs with Voice ServicesTable 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 UEswith the QCI of 1 in thedownlink buffer

1526728446 L.Traffic.ActiveUser.UL.QCI.1 Number of activated UEswith the QCI of 1 in theuplink buffer

1526730601 L.Traffic.ActiveUser.DL.QCI.1.Max Maximum number ofactivated UEs with the QCIof 1 in the downlink buffer

1526730611 L.Traffic.ActiveUser.UL.QCI.1.Max Maximum number ofactivated UEs with the QCIof 1 in the uplink buffer

1526732721 L.Traffic.User.VoIP.Avg Average number of VoIPUEs in a cell

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

1526736692 L.Traffic.User.VoIP.Avg.PLMN Average number of VoIPUEs of a specific operator ina cell

1526736693 L.Traffic.User.VoIP.Max.PLMN Maximum number of VoIPUEs of a specific operator ina cell

Number of PRBs Used by Voice Services

Table 9-14 describes the counters used to monitor the average number of PRBs occupied byvoice services.

Table 9-14 Counters used to monitor the average number of PRBs occupied by voice services

1526730883 L.ChMeas.PRB.DL.DrbUsed.Avg.VoIP

Average number of PRBs used by DRBs on thePDSCH for downlink VoIP services

1526730884 L.ChMeas.PRB.UL.DrbUsed.Avg.VoIP

Average number of PRBs used by DRBs on thePUSCH for uplink VoIP services

Throughput

Table 9-15 and Table 9-16 describe the counters used to monitor the number of PDCCHCCEs 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 voiceservices.

Table 9-15 Counters used to monitor the number of PDCCH CCEs used by voice services

1526736735 L.ChMeas.CCE.ULUsed.VoIP

Number of PDCCH CCEs used for uplinkVoIP services

1526736736 L.ChMeas.CCE.DLUsed.VoIP

Number of PDCCH CCEs used fordownlink VoIP services

Table 9-16 Counters used to monitor the total uplink/downlink traffic volume of voiceservices

1526726776 L.Thrp.bits.UL.QCI.1 Uplink traffic volume for PDCP PDUs ofservices with the QCI of 1 in a cell

1526726803 L.Thrp.bits.DL.QCI.1 Downlink traffic volume for PDCP SDUsof services with the QCI of 1 in a cell

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

1526726804 L.Thrp.Time.DL.QCI.1 Transmit duration of downlink PDCP SDUsfor services with the QCI of 1 in a cell

1526727849 L.Thrp.bits.UL.PLMN.QCI.1

Uplink traffic volume for PDCP PDUs ofservices with the QCI of 1 in a cell

1526727850 L.Thrp.Time.UL.PLMN.QCI.1

Receive duration of uplink PDCP PDUs forservices with the QCI of 1 in a cell

1526728050 L.Thrp.bits.DL.PLMN.QCI.1

Downlink traffic volume for PDCP SDUsof services with the QCI of 1 in a cell

1526728051 L.Thrp.Time.DL.PLMN.QCI.1

Transmit duration of downlink PDCP SDUsfor 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 OptimizationN/A

9.2.6 TroubleshootingIf 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 ofVoLTE. 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 andeNodeBAlgoSwitch.EutranVoipSupportSwitch is set to ON.

l If the parameter settings are incorrect, modify the parameter settings and perform theverification again.

l If the parameter settings are incorrect, verify the following counters to check the packetloss 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.

L.Traffic.UL.PktLoss.Loss.QCI.5

Number of uplink PDCP SDUs discarded forservices carried on DRBs with a QCI of 5 in a cell

L.Traffic.UL.PktLoss.Tot.QCI.5

Number of expected uplink PDCP SDUs forservices carried on DRBs with a QCI of 5 in a cell

L.Traffic.DL.PktUuLoss.Loss.QCI.5

Number of downlink PDCP SDUs discarded forservices carried on DRBs with a QCI of 5 in a cellover the Uu interface

L.Traffic.DL.PktUuLoss.Tot.QCI.5

Number of downlink PDCP SDUs transmitted forservices carried on DRBs with a QCI of 5 in a cellover the Uu interface

9.3 Semi-Persistent Scheduling

9.3.1 When to Use Semi-Persistent Scheduling and Deploy PowerControl

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

Semi-persistent scheduling uses fixed MCS and PRBs to transmit data during talk spurtsinstead of updating MCS and PRBs at each TTI. This brings gains and reduces requiredPDCCH resources. Therefore, semi-persistent scheduling is recommended in scenarios withlow-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-persistentscheduling 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 anddownlink semi-persistent scheduling are not recommended in cells working at a bandwidth of1.4 MHz.

Power Control in Semi-Persistent SchedulingWhen uplink semi-persistent scheduling is enabled, power control for uplink semi-persistentscheduling must be enabled so that uplink IBLER converges on the target value.

The PDSCH transmit power is evenly allocated among RBs. Adjusting the PDSCH transmitpower only when performing VoIP service cannot bring gains. Therefore, it is recommendedthat power control in downlink semi-persistent scheduling be disabled. When this type ofpower control is disabled, fixed PDSCH power allocation is used for UEs that are scheduledin a semi-persistent manner.

9.3.3 Deployment of Semi-Persistent Scheduling

Operating EnvironmentUEs must support VoLTE, semi-persistent scheduling, and closed-loop power control in semi-persistent scheduling. The EPC must support IMS.

Transmission NetworkingN/A

LicenseThe operator has purchased the license for this feature, and activated the license.

Feature ID Feature Name Model LicenseControl Item

NE Sales Unit

LOFD-001016

VoIP Semi-persistentScheduling

LT1S00VOIP00

VoIP Semi-PersistentScheduling(FDD)

eNodeB per RRCConnectedUser

9.3.3.2 Data Preparation

There are three types of data sources:

The following table describes the parameters that must be set in the CellAlgoSwitch MO toset uplink and downlink semi-persistent scheduling for voice services.

Parameter Name Parameter ID DataSource

Description

Uplink scheduleswitch

CellAlgoSwitch.UlSchSwitch

Networkplan(negotiation notrequired)

SpsSchSwitch(SpsSchSwitch)of this parameter specifieswhether to enable or disableuplink semi-persistent schedulingfor voice services. To enable thisfeature, select theSpsSchSwitch(SpsSchSwitch)option.Set this parameter by referring to9.3.1 When to Use Semi-Persistent Scheduling andDeploy Power Control.

DL schedule switch CellAlgoSwitch.DlSchSwitch

Networkplan(negotiation notrequired)

SpsSchSwitch(SpsSchSwitch)of this parameter specifieswhether to enable or disabledownlink semi-persistentscheduling for voice services. Toenable this feature, select theSpsSchSwitch(SpsSchSwitch)option.Set this parameter by referring to9.3.1 When to Use Semi-Persistent Scheduling andDeploy Power Control.

The following table describes the parameters that must be set in the CellAlgoSwitch MO toset power control in uplink and downlink semi-persistent scheduling for voice services.

Parameter Name

Parameter ID Data Source Description

Uplinkpowercontrolalgorithmswitch

CellAlgoSwitch.UlPcAlgoSwitch

Network plan(negotiation notrequired)

The CloseLoopSpsSwitch optionof this parameter specifieswhether to enable or disablepower control in uplink semi-persistent scheduling for voiceservices. To enable this feature,select the CloseLoopSpsSwitchoption.Set this parameter by referring to9.3.1 When to Use Semi-Persistent Scheduling andDeploy Power Control.

Downlinkpowercontrolalgorithmswitch

CellAlgoSwitch.DlPcAlgoSwitch

The PdschSpsPcSwitch option ofthis parameter specifies whetherto enable or disable power controlin downlink semi-persistentscheduling for voice services. Toenable this feature, select thePdschSpsPcSwitch option.Set this parameter by referring to9.3.1 When to Use Semi-Persistent Scheduling andDeploy Power Control.

9.3.3.3 PrecautionsIf UL semi-persistent scheduling is enabled, it is recommended that CloseLoopSpsSwitch beturned on to enable closed-loop power control for the PUSCH to ensure the convergence ofuplink IBLER. If downlink semi-persistent scheduling is enabled, turn off thePdschSpsPcSwitch to disable PDSCH power control in semi-persistent scheduling mode.

9.3.3.4 Hardware AdjustmentNone

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBsEnter the values of the parameters listed in Table 9-17 in a summary data file, which alsocontains other data for the new eNodeBs to be deployed. Then, import the summary data fileinto the Configuration Management Express (CME) for batch configuration. For detailedinstructions, see "Creating eNodeBs in Batches" in the initial configuration guide for theeNodeB, which is available in the eNodeB product documentation.

The summary data file may be a scenario-specific file provided by the CME or a customizedfile, depending on the following conditions:

l The managed objects (MOs) in Table 9-17 are contained in a scenario-specific summarydata file. In this situation, set the parameters in the MOs, and then verify and save thefile.

Table 9-17 Parameters related to semi-persistent scheduling

CellAlgoSwitch CELLALGOSWITCH LocalCellID, UlSchSwitch,UlPcAlgoSwitch,DlSchSwitch

User-definedtemplate

Batch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, formultiple 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 theCME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, pressF1 when a CME window is active, and select Managing the CME > CME Guidelines >LTE Application Management > eNodeB Related Operations > Customizing a SummaryData File for Batch eNodeB Configuration.

Step 2 Choose CME > LTE Application > Export Data > Export Base Station BulkConfiguration Data (U2000 client mode), or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeBdata 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 notesprovided in section "Data Preparation" and close the file.

Step 4 Choose CME > LTE Application > Import Data > Import Base Station BulkConfiguration Data (U2000 client mode), or choose LTE Application > Import Data >Import Base Station Bulk Configuration Data (CME client mode), to import the summarydata file into the CME, and then start the data verification.

Step 5 After data verification is complete, choose CME > Planned Area > Export IncrementalScripts (U2000 client mode), or choose Area Management > Planned Area > ExportIncremental Scripts (CME client mode), to export and activate the incremental scripts. Fordetailed operations, see Managing the CME > CME Guidelines > Script File Management> Exporting Incremental Scripts from a Planned Data Area in the CME online help.

----End

On the CME, set the parameters listed in 9.3.3.2 Data Preparation for a single eNodeB. Theprocedure is as follows:

Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO aredisplayed in area 4.

Step 5 Set the parameters in area 4 or 5.

----End

Using MML Commandsl Uplink Semi-Persistent Scheduling

Run the MOD CELLALGOSWITCH command to turn on the uplink semi-persistentscheduling switch.

l Power Control in Uplink Semi-Persistent SchedulingRun the MOD CELLALGOSWITCH command with the PUSCH semi-persistentscheduling closed-loop power control switch turned on.

l Downlink Semi-Persistent SchedulingRun the MOD CELLALGOSWITCH command turn on the downlink semi-persistentscheduling switch.

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

MML Command ExamplesMOD 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;

9.3.3.6 Activation Observation

Uplink Semi-Persistent SchedulingTo verify uplink semi-persistent scheduling for voice services, perform the following steps:

Step 1 Run the LST CELLALGOSWITCH command to check whether uplink semi-persistentscheduling 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 uplinkMCS indexes are less than or equal to 15 and the number of uplink scheduling times isabout 50, uplink semi-persistent scheduling is activated for the UE. (If the UE is not farfrom the eNodeB, the number of uplink scheduling times is about 50. If the UE is farfrom 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 CellPerformance Monitoring >Scheduled Users Statistic Monitoring. Set the tracingduration, to-be-traced NE information, and cell ID.

5. On the U2000, check Total SPS ULSCH Users and Total SPS DLSCH Users, asshown in Figure 9-8.If the value of Total SPS ULSCH Users is greater than 0, UL semi-persistent schedulingis activated for the UE. If the value of Total SPS DLSCH Users is greater than 0, DLsemi-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 CounterName

Counter Description

1526728562 L.Sps.UL.ErrNum

Number of times of failed uplink semi-persistentscheduling transmission in a cell

1526728494 L.Sps.UL.SchNum

Number of times of uplink semi-persistentscheduling in a cell

----End

Downlink Semi-Persistent SchedulingTo verify downlink semi-persistent scheduling for voice services, perform the following steps:

Step 1 Run the LST CELLALGOSWITCH command to check whether downlink semi-persistentscheduling has been activated.LST CELLALGOSWITCH: LocalCellId=0;

Step 2 After the UE accesses the cell, use the UE to perform downlink voice services.

1. On the U2000, choose Monitor > Signaling Trace > Signaling Trace Management.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), andmTMSI(UE TMSI).

3. Check the MCS-specific scheduling statistics, as shown in Figure 9-9. If the downlinkMCS indexes are less than or equal to 15 and the number of downlink scheduling timesis about 50, downlink semi-persistent scheduling has been performed for the UE.

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 downlinksemi-persistent schedulingtransmission 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 SchedulingTo check whether the IBLER values can converge when closed-loop power control in PUSCHsemi-persistent scheduling is enabled, perform the following steps:

Step 1 Run the LST CELLALGOSWITCH command to check whether closed-loop power controlin 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.

1. On the U2000, choose Monitor > Signaling Trace > Signaling Trace Management.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 IBLERvalues 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 IBLERvalues are relatively large. In the two cases, the IBLER values do not converge.

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 downlinksemi-persistent scheduling is enabled.

Step 2 If it is not enabled, run the following command to disable it:MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PdschSpsPcSwitch-0;

----End

Table 9-18 Parameters related to semi-persistent scheduling

CellAlgoSwitch CELLALGOSWITCH LocalCellID, UlSchSwitch,UlPcAlgoSwitch,DlSchSwitch

User-definedsheet

Using the CME to Perform Single ConfigurationOn 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 describedfor feature activation.

Using MML Commandsl Uplink Semi-Persistent Scheduling

Run the MOD CELLALGOSWITCH command with the uplink semi-persistentscheduling switch turned off.MML Command ExamplesMOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SpsSchSwitch-0;MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch=CloseLoopSpsSwitch-0;

l Downlink Semi-Persistent SchedulingRun the MOD CELLALGOSWITCH command with the downlink semi-persistentscheduling switch turned off.MML Command ExamplesMOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=SpsSchSwitch-0;MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PdschSpsPcSwitch-0;

9.3.4 Performance MonitoringSemi-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, UElocation, and traffic model. If the values for these counters decrease after semi-persistentscheduling is enabled, PDCCH consumption is reduced.

1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH CCEs used foruplink DCI

1526728305 L.ChMeas.CCE.DLUsed Number of PDCCH CCEs used fordownlink 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.

Power control in semi-persistent scheduling must work with semi-persistent scheduling.

9.3.6 TroubleshootingIf the result of L.Sps.UL.ErrNum/L.Sps.UL.SchNum is relatively high (greater than 10%),check whether the CloseLoopSpsSwitch option of theCELLALGOSWITCH.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 BundlingIt is recommended that TTI bundling be enabled to improve the coverage of cell edges and inscenarios where indoor voice services are served by outdoor sites. This function is dependenton UEs. Therefore, a compatibility test is required before enabling this feature.

The RRC Connection Reconfiguration message instructs UEs to enter or exit the TTIbundling state. UE channel conditions change significantly in high speed or ultra high speedscenarios. As a result, UEs frequently enter and exit the TTI bundling state, thereby increasingsignaling load on the Uu interface, degrading voice quality, and increasing the risk of calldrops. Therefore, it is recommended that TTI bundling be disabled in high speed or ultra highspeed cells.

Cells working at a bandwidth of 1.4 MHz have only six PRBs. TTI bundling consumesresources in the time domain. Therefore, it is recommended that TTI bundling be disabled incells working at a bandwidth of 1.4 MHz.

9.4.3 Deployment of TTI Bundling

Operating Environment

UEs must support VoLTE and TTI bundling, and the EPC must support IMS-based voiceservices.

Transmission Networking

According to 3GPP specifications, TTI bundling is supported only by cells with subframeconfiguration 0, 1, or 6.

License

The operator has purchased the license for this feature, and activated the license.

Feature ID FeatureName

Model LicenseControlItem

NE Sales Unit

LOFD-001048

TTI Bundling LT1S00TTIB00

TTIBundling(FDD)

eNodeB per Cell

9.4.3.2 Data Preparation

There are three types of data sources:

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

ParameterName

Uplinkscheduleswitch

CellAlgoSwitch.UlSchSwitch

TheTtiBundlingSwitch(TtiBundlingSwitch) option of thisparameter specifies whetherto enable TTI bundling.l In common scenarios,

deselect this option.l When the UE's channel

quality is poor andtransmit power is limited,select this option.

TTI BundlingTriggerStrategy

CellAlgoSwitch.TtiBundlingTriggerStrategy

This parameter specifies aTTI bundling trigger policy.l If TTI bundling applies

only to VoLTE services,set this parameter toSERVICE_VOIP(SERVICE_VOIP).

l If TTI bundling applies toVoLTE or a combinationof VoLTE and data, setthis parameter toSERVICE_MULTIAPP(SERVICE_MULTIAPP).

ParameterName

Statistic NumThreshold forTTIB Trigger

CellAlgoSwitch.StatisticNumThdForTtibTrig

This parameter specifies athreshold number ofconsecutive times that themeasured SINR is less thanthe target SINR. When theactual number reaches thisthreshold number, theeNodeB instructs the UE toenter the TTI bundling state.The default parameter valueis recommended.

Statistic NumThreshold forTTIB Exit

CellAlgoSwitch.StatisticNumThdForTtibExit

This parameter specifies athreshold number ofconsecutive times that themeasured SINR is greaterthan the sum of the targetSINR and theCellAlgoSwitch.HystToExitTtiBundling parameter value.When the actual numberreaches this thresholdnumber, the eNodeB instructsthe UE to exit the TTIbundling state. The defaultvalue is recommended.

Hysteresis toExit TTIBundling

CellAlgoSwitch.HystToExitTtiBundling

This parameter specifies anSINR threshold for exitingthe TTI bundling state. Thisthreshold is equal to the sumof the SINR threshold forentering the TTI bundlingstate and theCellAlgoSwitch.HystToExitTtiBundling parameter value.The default value isrecommended.

TTIB MaxNumber ofRLCSegments

CellAlgoSwitch.TtiBundlingRlcMaxSeg-Num

This parameter specifies themaximum number of uplinkRLC segments for UEs in theTTI bundling state. Thedefault value isrecommended.

ParameterName

TTIB MaxNumber ofHARQTransmissions

CellAlgoSwitch.TtiBundlingHarqMaxTx-Num

This parameter specifies themaximum number of HARQtransmissions for UEs in theTTI bundling state. Thedefault value isrecommended.

9.4.3.3 PrecautionsNone

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBsEnter the values of the parameters listed in Table 9-19 in a summary data file, which alsocontains other data for the new eNodeBs to be deployed. Then, import the summary data fileinto the CME for batch configuration. For detailed instructions, see "Creating eNodeBs inBatches" in the initial configuration guide for the eNodeB, which is available in the eNodeBproduct documentation.

l The managed objects (MOs) in Table 9-19 are contained in a scenario-specific summarydata file. In this situation, set the parameters in the MOs, and then verify and save thefile.

Table 9-19 Parameters related to TTI bundling

CellAlgoSwitch CELLALGOSWITCH LocalCellID, UlSchSwitch User-definedtemplate

CellUlschAlgo CELLULSCHALGO LocalCellID,TtiBundlingTriggerStrategy,StatisticNumThdForTtibTrig,StatisticNumThdForTtibExit,HystToExitTtiBundling,TtiBundlingRlcMaxSegNum,TtiBundlingHarqMaxTxNum

----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 DataPreparation as required.

----End

MML Command ExamplesMOD 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 beenactivated.

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 andRRC_CONN_RECFG_CMP messages are present in the Uu tracing result. Check the IEsmac-MainConfig > ul-SCH-Config > ttiBundling in the RRC_CONN_RECFG message. Thevalue TRUE (as shown in Figure 9-12) indicates that TTI bundling has been activated for ULVoIP.

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 Figure9-13) indicates that TTI bundling has been deactivated for UL VoIP.

Figure 9-13 RRC_CONN_RECFG message (indicating that TTI bundling has beendeactivated)

Step 6 Use the following counters to check the status of TTI bundling. TTI bundling is enabled if thevalues of these counters are not 0.

1526728496 L.Traffic.User.TtiBundling.Avg

Average number of UEs for which TTIbundling is enabled in a cell

1526728911 L.Signal.Num.TtiBundling.Enter

Number of messages that trigger theentering of the TTI bundling mode

1526728912 L.Signal.Num.TtiBundling.Exit

Number of messages that trigger theexiting of the TTI bundling mode

----End

Table 9-20 Parameters related to TTI bundling

Parameter Group SettingNotes

CellAlgoSwitch CellAlgoSwitch LocalCellID, UlSchSwitch User-definedsheet

CellUlschAlgo CellUlschAlgo LocalCellID,TtiBundlingTriggerStrategy,StatisticNumThdForTtib-Trig, StatisticNumThdForT-tibExit, HystToExitTtiBun-dling, TtiBundlingRlcMax-SegNum, TtiBundlingHarq-MaxTxNum

User-definedsheet

Using MML Commands

Run the MOD CELLALGOSWITCH command to deactivate TTI bundling.

MML Command ExamplesMOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=TtiBundlingSwitch-0;

9.4.4 Performance MonitoringTTI bundling improves uplink coverage for voice service users or improves uplink packet lossrate.

For details, see 9.2.4.3 Voice Quality.

9.4.6 TroubleshootingN/A

9.5 UL RLC Segmentation Enhancement

9.5.1 When to Use Uplink RLC Segmentation EnhancementIt is recommended that this feature be enabled for VoLTE to improve the cell edge coverageof the PUSCH.

9.5.3 Deployment

Operating EnvironmentThe EPC must support IMS-based voice services.

LicenseN/A

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

ParameterName

Uplink VoipRlc MaximumSegmentationNumber

CellUlschAlgo.UlVoipRlcMaxSegNum

This parameter determineswhether to enable the uplinkRLC segmentationenhancement feature forVoLTE services on UEs not inthe TTI bundling state andspecifies the maximumnumber of uplink RLCsegments.l If this parameter is set to

0, this feature is disabled.l If this parameter is set to a

non-zero value X, thisfeature is enabled and themaximum number ofuplink RLC segments inthe non-TTI-bundlingstate is X.

9.5.3.3 Precautions

Enter the values of the parameters listed in Table 9-21 in a summary data file, which alsocontains other data for the new eNodeBs to be deployed. Then, import the summary data fileinto the CME for batch configuration. For detailed instructions, see "Creating eNodeBs inBatches" in the initial configuration guide for the eNodeB, which is available in the eNodeBproduct documentation.

Table 9-21 Parameters related to UL RLC segmentation enhancement

CELLULSCHALGO

CELLULSCHALGO LocalCellID,UlVoipRlcMaxSegNum

----End

Using MML CommandsRun the MOD CELLULSCHALGO command with the Uplink Voip Rlc MaximumSegmentation Number parameter set to the recommended value of the corresponding RAT.

MML Command ExamplesMOD CELLULSCHALGO: LocalCellId=0, UlVoipRlcMaxSegNum=20;

9.5.3.6 Activation ObservationAfter uplink RLC segmentation enhancement is activated with the Uplink Voip RlcMaximum Segmentation Number parameter set to a non-zero value, the MCS index shouldbe increased for a UE at the cell edge to control the number of uplink RLC segments. Toverify this, perform the following steps:

Step 1 Run the LST CELLULSCHALGO command to check whether the Uplink Voip RlcMaximum Segmentation Number parameter is set to 0. If it is set to 0, go to Step 2. If it isset to a non-zero value, run the following command to change it to 0 (x represents the localcell ID):

MOD CELLULSCHALGO: LocalCellId=0, UlVoipRlcMaxSegNum=0;

Step 2 Use a UE that does not support TTI bundling to access the cell. Initiate a UL VoLTE serviceon 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 andto-be-traced MMEc (MME ID), and mTMSI (UE TMSI).

3. Observe MCS-specific uplink scheduling statistics, including the number of schedulingtimes and the number of RBs. Move the UE to the cell edge, where channel quality ispoor. That is, move the UE until the monitoring result indicates that the MCS with anindex of 0 is selected and a maximum of three RBs are allocated by uplink scheduling ofthe UE.

Step 4 Run the MOD CELLULSCHALGO command with the Uplink Voip Rlc MaximumSegmentation Number parameter set to a non-zero value.

To ensure satisfactory voice quality, you are advised to set the Uplink Voip Rlc MaximumSegmentation 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 increasesnoticeably.

Step 5 On the U2000 client, observe the MCS-specific uplink scheduling statistics. If the MCS indexis greater than 0 but the number of RBs is still less than or equal to 3, the eNodeB hasincreased the MCS index to restrict the number of uplink RLC segments. (The smaller thevalue 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 theproportion of uplink low-order MCSs for the PUSCH (for example, MCS index 0 or 1). Ifboth of them decrease, RLC segmentation enhancement has taken effect.

1526727412to 1526727443

L.ChMeas.PUSCH.MCS.0to L.ChMeas.PUSCH.MCS.31

Number of times that MCSindexes 0 to 31 are used forPUSCH scheduling

1526727961 L.Traffic.UL.PktLoss.Loss.QCI.1

Number of uplink PDCPSDUs discarded for servicescarried on DRBs with QCIsof 1 in a cell

1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1 Number of expected uplinkPDCP SDUs for servicescarried on DRBs with QCIsof 1 in a cell

----End

9.5.3.7 ReconfigurationN/A

Table 9-22 Parameters related to UL RLC segmentation enhancement

CellUlschAlgo CELLULSCHALGO LocalCellID,UlVoipRlcMaxSegNum

Using MML Commands

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

MML Command ExamplesMOD CELLULSCHALGO: LocalCellId=0, UlVoipRlcMaxSegNum=0;

9.5.4 Performance MonitoringUL RLC segmentation enhancement improves UL packet loss rate of VoLTE services.Monitor the performance of this feature through the following counters.

ID Name Description

Total number of discarded uplink PDCP SDUsfor DRB services with the QCI of 1 in a cell

1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1

Total number of expected uplink data packetsfor DRB services with the QCI of 1 in a cell

9.6 Voice Characteristic Awareness Scheduling

9.6.1 When to Use Voice Characteristic Awareness SchedulingThis feature is recommended when VoLTE has been deployed and the performance of VoLTEneeds to be preferentially ensured.

9.6.3 Deployment

LicenseThe operator has purchased the license for this feature, and activated the license.

Feature ID FeatureName

Model License ControlItem

NE Sales Unit

LOFD-081229

VoiceCharacteristicAwarenessScheduling

LT1S00VCAS00

Voice CharacteristicAwarenessScheduling(FDD)

eNodeB per Cell

The following table describes the parameter that must be set in the CELLULSCHALGO toconfigure Voice Characteristic Awareness Scheduling for a cell.

CELLULSCHALGO.UlDelaySchStrategy

This parameter specifies a policyfor uplink delay-based dynamicscheduling. If this parameter is setto NO_DELAYSCH, uplink delay-based dynamic scheduling isdisabled. If this parameter is set toVOIP_DELAYSCH, uplink delay-based dynamic scheduling for VoIPis enabled. The eNodeB adjustsscheduling priorities based on VoIPpacket delays during uplinkdynamic scheduling, therebyincreasing the MOS and VoIPcapacity when the cell is heavilyloaded.

CELLULSCHALGO.UlEnhencedVoipSchSw

The UlVoLTEDataSizeEstSwitchoption of theCELLULSCHALGO.UlEnhencedVoipSchSw parameter specifieswhether to enable uplink VoLTEvolume estimation for dynamicscheduling. This estimationfunction shortens VoLTE packetdelays, reduces the packet loss rate,and improves voice quality.

eNBCellRsvdPara.RsvdSwPara3

l When the RsvdSwPara3_bit1option of theeNBCellRsvdPara.RsvdSwPara3 parameter is selected and thedata scheduling wait time is thesame, the SR schedulingpriority for UEs with QCI of 1is higher than that for UEswithout QCI of 1.

l When the RsvdSwPara3_bit1option of theeNBCellRsvdPara.RsvdSwPara3 parameter is deselected, theeNodeB sorts the priorities ofscheduling triggered by SR andBSR of VoLTE services. Alonger scheduling wait timeindicates a higher schedulingpriority.

9.6.3.3 Precautions

Table 9-23 Parameters related to voice characteristic awareness scheduling

CellUlschAlgo CellUlschAlgo LocalCellId,UlDelaySchStrategy

CellUlschAlgo CellUlschAlgo LocalCellID,UlEnhencedVoipSchSw,UlVoLTEDataSizeEstSwitch,

Using the CME to Perform Batch Configuration for Existing eNodeBsBatch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, formultiple eNodeBs in a single procedure. The procedure is as follows:

----End

Using the CME to Perform Single ConfigurationOn the CME, set the parameters listed in 9.6.3.2 Data Preparation for a single eNodeB. Theprocedure is as follows:

----End

Using MML Commands

Step 1 Run the MOD CELLULSCHALGO command to enable uplink delay-based dynamicscheduling.

Step 2 Run the MOD CELLULSCHALGO command to enable uplink VoLTE volume estimationfor dynamic scheduling.

----End

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

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 andthe duration of receiving uplink QCI 1 data at the PDCP layer before and after the feature isenabled. If both of them increase, uplink VoLTE volume estimation for dynamic schedulinghas been activated. In addition, check the proportion of VQIs that indicate poor or bad voicequality. If the proportion decreases, uplink delay-based dynamic scheduling have beenactivated.

Table 9-24 Counters for monitoring Voice Characteristic Awareness Scheduling

1526736735 L.ChMeas.CCE.ULUsed.VoIP Number of PDCCH CCEs allocatedto uplink VoIP

1526726777 L.Thrp.Time.UL.QCI.1 Duration of receiving uplink PDCPPDUs for services with QCIs of 1 ina cell

Number of times uplink voicequality is Excellent

1526728412 L.Voice.VQI.UL.Good.Times Number of times uplink voicequality is Good

1526728413 L.Voice.VQI.UL.Accept.Times Number of times uplink voicequality is Accept

1526728414 L.Voice.VQI.UL.Poor.Times Number of times uplink voicequality is Poor

1526728415 L.Voice.VQI.UL.Bad.Times Number of times uplink voicequality is Bad

----End

Table 9-25 Parameters related to voice characteristic awareness scheduling

CellUlschAlgo CellUlschAlgo LocalCellID,UlDelaySchStrategy

CellUlschAlgo CellUlschAlgo LocalCellID,UlEnhencedVoipSchSw

Using MML Commands

Run the MOD CELLULSCHALGO command to disable uplink delay-based dynamicscheduling.

Run the MOD CELLULSCHALGO command to disable uplink VoLTE volume estimationfor dynamic scheduling.

Run the MOD CELLULSCHALGO command with the uplink VoIP delay scheduling switchturned off.

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

9.6.4 Performance MonitoringAfter voice characteristic awareness scheduling is enabled, you can use the following countersto monitor whether the uplink VoLTE packet loss rate decreases.

CounterID

Number of uplink PDCP SDUs discarded forservices carried on DRBs with QCIs of 1 in acell

CounterID

Number of expected uplink PDCP SDUs forservices carried on DRBs with QCIs of 1 in acell

9.7 Uplink Compensation Scheduling

9.7.1 When to Use Uplink Compensation SchedulingIf VoLTE has been deployed, it is recommended that uplink compensation scheduling beenabled to reduce the number of uplink VoLTE packet losses in heavy traffic scenarios.

9.7.3 Deployment

LicenseN/A

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

ParameterName

UplinkEnhancedVoip ScheduleSwitch

CellUlschAlgo.UlEnhencedVoipSchSw

The UlVoipSchOptSwitchoption of theCellUlschAlgo.UlEnhencedVoipSchSw parameterspecifies whether to enableuplink compensationscheduling.l When this switch is turned

off, the function does nottake effect.

l When this switch is turnedon, uplink dynamicscheduling is triggered ifthe scheduling intervalexceeds a threshold. Thescheduling interval is aperiod during which aVoLTE user is notdynamically scheduled inthe uplink. In this way,VoLTE users can betimely scheduled in theuplink and the number ofPDCP packet losses due todiscard timer expiry canbe reduced even in heavytraffic scenarios.

Table 9-26 Parameters related to uplink compensation scheduling

CellUlschAlgo CELLULSCHALGO LocalCellID,UlEnhencedVoipSchSw.UlVoipSchOptSwitch

----End

Using MML Commands

Run the MOD CELLULSCHALGO command to enable uplink compensation scheduling.

MML Command ExamplesMOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoipSchOptSwitch-1;

Step 1 Run the LST CELLULSCHALGO command to check whether the UlVoipSchOptSwitch isturned off. If the switch is turned on, run the following command to turn it off. If the switchhas been turned off, go to Step 2.MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoipSchOptSwitch-0;

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 andL.ChMeas.CCE.ULUsed.VoIP; if these values increase, this feature has been activated. Inaddition, check the uplink VoIP packet loss rate (calculated based onL.Traffic.UL.PktLoss.Loss.QCI.1 and L.Traffic.UL.PktLoss.Loss.QCI.1) to see the effect ofthis feature.

Table 9-27 Counters

1526736735 L.ChMeas.CCE.ULUsed.VoIP Number of PDCCH CCEsallocated to uplink VoIP

1526726777 L.Thrp.Time.UL.QCI.1 Receive duration of uplinkPDCP PDUs for serviceswith the QCI of 1 in a cell

1526727961 L.Traffic.UL.PktLoss.Loss.QCI.1 Number of uplink PDCPSDUs discarded for servicescarried on DRBs with QCIsof 1 in a cell

1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1 Number of expected uplinkPDCP SDUs for servicescarried on DRBs with QCIsof 1 in a cell

----End

Table 9-28 Parameters related to uplink compensation scheduling

CellUlschAlgo CellUlschAlgo LocalCellID,UlEnhencedVoipSchSw.UlVoipSchOptSwitch

Using MML Commands

Run the MOD CELLULSCHALGO command to disable uplink compensation scheduling.

MML Command ExamplesMOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoipSchOptSwitch-0;

9.7.4 Performance MonitoringAfter uplink compensation scheduling is enabled, you can use the following counters tomonitor whether the uplink VoLTE packet loss rate decreases.

CounterID

9.8 Voice-Specific AMC

9.8.1 When to Use Voice-Specific AMCIf 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 capacitypolicies. For example, if the number of online VoLTE users is small and VoLTE performanceneeds to be preferentially ensured, it is recommended that a small target IBLER be configuredfor VoLTE users.

9.8.3 Deployment

LicenseNone

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

ParameterName

SINRAdjustmentTarget IBLERfor VoLTE

CellAlgoSwitch.SinrAdjTargetIblerfor-VoLTE

This parameter specifies atarget IBLER for adjustingthe SINRs used in dynamicscheduling of VoLTE usersnot in the TTI bundling state.It is recommended that thisparameter be set to a valueless than or equal to 10% inlight-traffic scenarios and to10% in heavy-trafficscenarios.

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBsEnter the values of the parameters listed in Table 9-29 in a summary data file, which alsocontains other data for the new eNodeBs to be deployed. Then, import the summary data fileinto the CME for batch configuration. For detailed instructions, see "Creating eNodeBs inBatches" in the initial configuration guide for the eNodeB, which is available in the eNodeBproduct documentation.

Table 9-29 Parameters related to voice-specific AMC

CELLULSCHALGO

CELLULSCHALGO LocalCellID,SinrAdjTargetIblerforVoLTE

----End

Using MML CommandsRun the MOD CELLULSCHALGO to set a target IBLER for adjusting VoLTE SINRs.

MML Command ExamplesMOD CELLULSCHALGO: LocalCellId=0, SinrAdjTargetIblerforVoLTE=3;

Step 1 Run the LST CELLULSCHALGO command to check whether the value of SINR targetIBLER adjustment is 10. If the value is not 10, run the following command to change it. Ifthe value is 10, go to Step 2.MOD CELLULSCHALGO: LocalCellId=0, SinrAdjTargetIblerforVoLTE=10;

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 SINRadjustment to a value rather than 10.

To ensure voice performance, you are advised to set the target IBLER to the recommended value. Tofacilitate activation observation, you can also set it to a smaller non-zero value so that a more obviousIBLER decrease can be seen.

Step 5 On the U2000 client, check the values of the counters listed in Table 9-30. If the uplinkIBLER of QCI 1 services (calculated using the following formula) converges on the targetIBLER, this feature has been activated.

Table 9-30 Counters

1526737730 L.Traffic.UL.SCH.QPSK.ErrTB.Ibler.QCI.1

Number of erroneouslytransmitted QCI 1 service TBson the UL-SCH during theinitial transmission in QPSKmodulation mode

1526737731 L.Traffic.UL.SCH.16QAM.ErrTB.Ibler.QCI.1

Number of erroneouslytransmitted QCI 1 service TBson the UL-SCH during theinitial transmission in 16Quadrature AmplitudeModulation (16QAM)modulation mode

Number of erroneouslytransmitted QCI 1 service TBson the UL-SCH during theinitial transmission in 64QAMmodulation mode

1526737724 L.Traffic.UL.SCH.QPSK.TB.QCI.1

Number of initially transmittedQCI 1 service TBs on the UL-SCH in QPSK modulationmode

1526737725 L.Traffic.UL.SCH.16QAM.TB.QCI.1

Number of initially transmittedQCI 1 service TBs on the UL-SCH in 16QAM modulationmode

Number of initially transmittedQCI 1 service TBs on the UL-SCH in 64QAM modulationmode

----End

Table 9-31 Parameters related to voice-specific AMC

CellUlschAlgo CellUlschAlgo LocalCellID,SinrAdjTargetIblerforVoLTE

Using MML Commands

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

MML Command ExamplesMOD CELLULSCHALGO: LocalCellId=0, SinrAdjTargetIblerforVoLTE=10;

9.8.4 Performance MonitoringAfter voice-specific AMC is enabled, you can use the following counters to monitor whetherthe uplink VoLTE packet loss rate decreases.

CounterID

10 Parameters

Table 10-1 Parameters

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

VQMAlgo

VqiExcellentThd

MODVQMALGOLSTVQMALGO

None None Meaning: Indicates the voice quality indicator (VQI)threshold above which the voice quality is consideredas excellent.GUI Value Range: 0~500Unit: NoneActual Value Range: 0~5, step:0.01Default Value: 400

VQMAlgo

VqiPoorThd

None None Meaning: Indicates the voice quality indicator (VQI)threshold for determining the voice quality is poor. Ifthe VQI evaluation value is greater than theVqiBadThd parameter value and less than or equal tothe VqiPoorThd parameter value, the voice quality isconsidered as poor. If the VQI evaluation value is lessthan or equal to the VqiGoodThd parameter value andgreater than the VqiPoorThd parameter value, thevoice quality is considered as accepted.GUI Value Range: 0~500Unit: NoneActual Value Range: 0~5, step:0.01Default Value: 200

eRANVoLTE Feature Parameter Description 10 Parameters

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

VQMAlgo

VqiGoodThd

None None Meaning: Indicates the voice quality indicator (VQI)threshold for determining the voice quality is good. Ifthe VQI evaluation value is greater than theVqiGoodThd parameter value and less than or equalto the VqiExcellentThd parameter value, the voicequality is considered as good. If the VQI evaluationvalue is less than or equal to the VqiGoodThdparameter value and greater than the VqiPoorThdparameter value, the voice quality is considered asaccepted.GUI Value Range: 0~500Unit: NoneActual Value Range: 0~5, step:0.01Default Value: 300

VQMAlgo

VqiBadThd

None None Meaning: Indicates the voice quality indicator (VQI)threshold equal to or below which the voice quality isconsidered as bad.GUI Value Range: 0~500Unit: NoneActual Value Range: 0~5, step:0.01Default Value: 100

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

GlobalProcSwitch

VoipWithGapMode

MODGLOBALPROCSWITCHLSTGLOBALPROCSWITCH

LOFD-002001 /TDLOFD-002001LOFD-002002 /TDLOFD-002002LOFD-002007 /TDLOFD-002007MRFD-231808

AutomaticNeighbourRelation(ANR)Inter-RATANRPCICollisionDetection &Self-OptimizationGSMand LTEBufferZoneOptimization(LTE)

Meaning:Indicates whether VoIP UEs are allowed to enter theperiodical measurement gap and whether they can exitthe gap if VoIP services are initiated during the gap. AVoIP UE can enter the periodical measurement gapduring GSM and LTE buffer zone optimization orperiodic inter-frequency/RAT measurements in celltracing. If a UE enters the measurement gap and thenVoIP services are initiated for this UE, fast ANR,active PCI conflict detection, GSM and LTE bufferzone optimization, or periodic inter-frequency/RATmeasurements in cell tracing can trigger the UE'sexiting from the gap.

If this parameter is set to ENBALE, VoIP UEs areallowed to enter the periodic measurement gap duringGSM and LTE buffer zone optimization and periodicinter-frequency/RAT measurement in cell tracing. Theparameter setting does not affect the entering of thegap during fast ANR and active PCI conflict detectionfor VoIP UEs.

If this parameter is set to DISABLE, VoIP UEs areprohibited to enter the periodic measurement gap andthe UEs entering the gap and initiating VoIP servicescannot exit the gap.GUI Value Range: DISABLE(disable),ENABLE(enable)Unit: NoneActual Value Range: DISABLE, ENABLEDefault Value: ENABLE(enable)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUlschAlgo

TtiBundlingTriggerStrategy

MODCELLULSCHALGOLSTCELLULSCHALGO

LOFD-001048

TTIBundling

Meaning:Indicates the policy of triggering transmission timeinterval (TTI) bundling when TtiBundlingSwitch ofthe UlSchSwitch parameter is on.

If this parameter is set to SERVICE_VOIP, theeNodeB triggers TTI bundling for UEs running onlyVoIP services in the uplink.

If this parameter is set to SERVICE_MULTIAPP, theeNodeB triggers TTI bundling for all UEs runningVoIP services, including UEs running only VoIPservices and UEs running both VoIP services and dataservices in the uplink.GUI Value Range:SERVICE_VOIP(SERVICE_VOIP),SERVICE_MULTIAPP(SERVICE_MULTIAPP)Unit: NoneActual Value Range: SERVICE_VOIP,SERVICE_MULTIAPPDefault Value: SERVICE_VOIP(SERVICE_VOIP)

CellUlschAlgo

StatisticNumThdForTtibTrig

LOFD-001048

TTIBundling

Meaning: Indicates the threshold of channel qualitystatistic times during which the channel quality of aUE consistently meets conditions for enteringtransmission time interval (TTI) bundling. Before aUE enters TTI bundling, the eNodeB performsstatistic on the channel quality of the UE at theinterval of 20 ms or longer. If the number of statistictimes during which the channel quality of the UEconsistently meets conditions for entering TTIbundling is greater than this parameter value, the UEenters TTI bundling. This parameter helps delay thetime for entering TTI bundling and decrease theprobability of unnecessary TTI bundling enteringcaused by wireless signal fluctuation. This parameterapplies 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: NoneActual Value Range: N5_TTIB_ENTER,N10_TTIB_ENTER, N15_TTIB_ENTER,N20_TTIB_ENTERDefault Value: N10_TTIB_ENTER(10)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUlschAlgo

StatisticNumThdForTtibExit

LOFD-001048

TTIBundling

Meaning: Indicates the threshold of channel qualitystatistic times during which the channel quality of aUE consistently meets conditions for exiting fromtransmission time interval (TTI) bundling. Before aUE exits from TTI bundling, the eNodeB performsstatistic on the channel quality of the UE at theinterval of 20 ms or longer. If the number of statistictimes during which the channel quality of the UEconsistently meets conditions for exiting from TTIbundling is greater than this parameter value, the UEexits TTI bundling. This parameter helps delay thetime for UEs to exit from TTI bundling and decreasethe probability of unnecessary exit from TTI bundlingcaused by wireless signal fluctuation. This parameterapplies 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: NoneActual Value Range: N10_TTIB_EXIT,N20_TTIB_EXIT, N40_TTIB_EXIT,N80_TTIB_EXITDefault Value: N20_TTIB_EXIT(20)

CellUlschAlgo

HystToExitTtiBundling

LOFD-001048

TTIBundling

Meaning: Indicates the hysteresis of the signal tointerference plus noise ratio (SINR) threshold forexiting from transmission time interval (TTI) bundlingagainst the SINR threshold for entering TTI bundling.The hysteresis decreases the probability ofunnecessary exit from TTI bundling caused bywireless signal fluctuation. This parameter appliesonly to LTE FDD networks.GUI Value Range: 3~6Unit: NoneActual Value Range: 3~6Default Value: 5

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUlschAlgo

TtiBundlingRlcMaxSegNum

LOFD-001048

TTIBundling

Meaning: Indicates whether to apply upper limitcontrol on service data unit (SDU) segmentation at theradio link control (RLC) layer in the uplink forservices scheduled in transmission time interval (TTI)bundling mode and the maximum SDU segments atthe RLC layer. If this parameter is set to 0, the upperlimit control on SDU segmentation at the RLC layer isdisabled in the uplink for services scheduled in TTIbundling mode. If this parameter is set to a non-zerovalue X, upper limit control on SDU segmentation atthe RLC layer is enabled and a maximum of X SDUsegments that can be divided for services in uplinkdynamic scheduling in TTI bundling mode. Thisparameter applies only to LTE FDD networks.GUI Value Range: 0~7Unit: NoneActual Value Range: 0~7Default Value: 4

CellUlschAlgo

TtiBundlingHarqMaxTxNum

LOFD-001048 /TDLOFD-001048

TTIBundling

Meaning: Indicates the maximum transmission timesof hybrid automatic repeat requests (HARQs) basedon transmission time interval (TTI) in the uplink. Fordetails, see 3GPP TS 36.331.GUI Value Range: n4(4), n8(8), n12(12), n16(16),n20(20), n24(24), n28(28)Unit: NoneActual Value Range: n4, n8, n12, n16, n20, n24, n28Default Value: n16(16)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUlschAlgo

UlDelaySchStrategy

LOFD-00101502/TDLOFD-00101502

DynamicScheduling

Meaning: Indicates whether to enable delay-baseddynamic scheduling prioritization for VoIP services. Ifthis parameter is set to NO_DELAYSCH, delay-baseddynamic scheduling prioritization for VoIP services isdisabled. If this parameter is set toVOIP_DELAYSCH, delay-based dynamic schedulingprioritization for VoIP services is enabled. Schedulingpriorities are dynamically adjusted based on VoIPpacket delays during uplink dynamic scheduling,thereby increasing the mean opinion score (MOS) andsystem capacity for VoIP services when the cell isheavily loaded with VoIP services.GUI Value Range: NO_DELAYSCH(No DelayScheduling), VOIP_DELAYSCH(VoIP Service DelayScheduling)Unit: NoneActual Value Range: NO_DELAYSCH,VOIP_DELAYSCHDefault Value: NO_DELAYSCH(No DelayScheduling)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUlschAlgo

UlEnhencedVoipSchSw

LOFD-081229

VoiceCharacteristicAwarenessScheduling

Meaning:Indicates whether to enable uplink pre-scheduling,include UlVoipPreAllocationSwtich(Bit0),UlVoipDelaySchSwitch(Bit1),UlVoIPLoadBasedSchSwitch(Bit2),UlVoipSchOptSwitch(Bit3), andUlVoLTEDataSizeEstSwitch(Bit4).

UlVoipPreAllocationSwtich: This switch controlswhether to schedule VoIP UEs during talk spurts whenthe number of online UEs exceeds 50 in a cell. If thisswitch is off, voice preallocation is not performed. Ifthis switch is on, voice preallocation is performed.This switch applies only to LTE FDD networks.

UlVoipDelaySchSwitch: This switch controls whetherto schedule VoIP UEs based on delays when there area large number of VoIP UEs and these UEs are evenlydistributed. If this switch is turned off, delay-basedscheduling is not performed. If this switch is turnedon, the scheduling priorities are calculated based ondelays. This switch applies only to LTE TDDnetworks.

UlVoIPLoadBasedSchSwitch: Indicates whether toenable adaptive selection of VoIP scheduling modebased on the cell load. There are two schedulingmodes: dynamic scheduling and semi-persistentscheduling. If this switch is off, adaptive selection ofdynamic and semi-persistent scheduling cannot beperformed for UEs running voice services based onthe cell load. If this switch is off, dynamic and semi-persistent scheduling can be adaptively selected forUEs running voice services based on the cell load.This switch applies only to LTE TDD cells.

UlVoipSchOptSwitch: Indicates whether to enablescheduling optimization for VoIP services in theuplink. If this option is deselected, this function isdisabled. If this option is selected, an uplink dynamicscheduling is triggered for VoIP UEs adopting uplinkdynamic scheduling when the scheduling interval isgreater than the uplink scheduling interval thresholdfor VoIP UEs. This ensures timely uplink schedulingon voice services even when SR missing detectionoccurs, thereby avoiding packet loss caused by theexpiration of the PDCP packet discarding timer.

UlVoLTEDataSizeEstSwitch: Indicates whether toenable the estimation of traffic volume dynamically

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

scheduled for VoLTE services in the uplink.If thisoption is deselected, this function is disabled. If thisoption is selected, the eNodeB estimates the uplinktraffic volume that is dynamically scheduled forVoLTE services, which shortens the VoLTE packetdelay, reduces the packet loss rate, improves the voiceservice quality.GUI Value Range: UlVoipPreAllocationSw-tich(UlVoipPreAllocationSwtich), UlVoipDelaySchS-witch(UlVoipDelaySchSwitch),UlVoIPLoadBasedSchS-witch(UlVoIPLoadBasedSchSwitch),UlVoipSchOptSwitch(UlVoipSchOptSwitch),UlVoLTEDataSizeEstSwitch(UlVoLTEDataSizeEstS-witch)Unit: NoneActual Value Range: UlVoipPreAllocationSwtich,UlVoipDelaySchSwitch, UlVoIPLoadBasedSchS-witch, UlVoipSchOptSwitch, UlVoLTEDataSizeEstS-witchDefault Value: UlVoipPreAllocationSwtich:Off,UlVoipDelaySchSwitch:Off, UlVoIPLoadBasedSchS-witch:Off, UlVoipSchOptSwitch:Off,UlVoLTEDataSizeEstSwitch:Off

CellUlschAlgo

SinrAdjTargetIblerforVoLTE

LBFD-081105

Voice-SpecificAMC

Meaning: Indicates the target IBLER in the SINRcalibration algorithm used for dynamic scheduling ofvoice users in non-TTI-bundling mode. A larger valueof this parameter results in a larger SINR adjustmentand a higher MCS to be selected.GUI Value Range: 1~99Unit: NoneActual Value Range: 0.01~0.99,0.01Default Value: 10

ENodeBAlgoSwitch

EutranVoipSupportSwitch

MODENODEBALGOSWITCHLSTENODEBALGOSWITCH

None None Meaning: Indicates whether the VoIP services areenabled in the E-UTRAN cell. This parameter is usedfor determining whether the establishment, handoverin, admission, and reestablishment of VoIP services isallowed.GUI Value Range: OFF(Off), ON(On)Unit: NoneActual Value Range: OFF, ONDefault Value: ON(On)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

GlobalProcSwitch

ProtocolSupportSwitch

None None Meaning: Indicates whether the eNodeB supportssome protocol-defined procedures.SupportS1UeCapMatchMsg(SupportS1UeCapMatchMsg): If this option is selected, the eNodeB canprocess and respond to the UE RADIO CAPABILITYMATCH REQUEST message over the S1 interface.For details about the message, see 3GPP TS 36.413. Ifthe option is deselected, the eNodeB cannot processthe UE RADIO CAPABILITY MATCH REQUESTmessage and responds with an error indicationmessage.GUI Value Range:SupportS1UeCapMatchMsg(SupportS1UeCapMatchMsg)Unit: NoneActual Value Range: SupportS1UeCapMatchMsgDefault Value: SupportS1UeCapMatchMsg:Off

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

ENodeBAlgoSwitch

HoAlgoSwitch

LBFD-00201801/TDLBFD-00201801LBFD-00201802/TDLBFD-00201802LBFD-00201804/TDLBFD-00201804LBFD-00201805/TDLBFD-00201805LOFD-001033 /TDLOFD-001033LOFD-001034 /TDLOFD-001034LOFD-001035 /TDLOFD-001035LOFD-001052 /TDLOFD-001052LOFD-001053 /

Coverage BasedIntra-frequencyHandoverDistanceBasedInter-frequencyHandoverServiceBasedInter-frequencyHandoverCSFallbacktoUTRANCSFallbacktoGERANCSFallbacktoCDMA20001xRTTFlashCSFallbacktoUTRANFlashCSFallbacktoGERANCSFallback

Meaning: Indicates whether to enable handoveralgorithms. The switches are described as follows:IntraFreqCoverHoSwitch: If this switch is on,coverage-based intra-frequency handovers are enabledto ensure service continuity. If this switch is off,coverage-based intra-frequency handovers aredisabled. InterFreqCoverHoSwitch: If this switch ison, coverage-based inter-frequency handovers areenabled to ensure service continuity. If this switch isoff, coverage-based inter-frequency handovers aredisabled. UtranCsfbSwitch: If this switch is on, CSFBto UTRAN is enabled and UEs can fall back toUTRAN. If this switch is off, CSFB to UTRAN isdisabled. GeranCsfbSwitch: If this switch is on, CSFBto GERAN is enabled and UEs can fall back toGERAN. If this switch is off, CSFB to GERAN isdisabled. Cdma1xRttCsfbSwitch: If this switch is on,CSFB to CDMA2000 1xRTT is enabled and UEs canfall back to CDMA2000 1xRTT. If this switch is off,CSFB to CDMA2000 1xRTT is disabled.UtranServiceHoSwitch: If this switch is on, service-based handovers to UTRAN are enabled and UEsrunning a specific type of services can be handed overto UTRAN. If this switch is off, service-basedhandovers to UTRAN are disabled.GeranServiceHoSwitch: If this switch is on, service-based handovers to GERAN are enabled and UEsrunning a specific type of services can be handed overto GERAN. If this switch is off, service-basedhandovers to GERAN are disabled.CdmaHrpdServiceHoSwitch: If this switch is on,service-based handovers to CDMA2000 HRPD cellsare enabled and UEs running a specific type ofservices can be handed over to CDMA2000 HRPDcells. If this switch is off, service-based handovers toCDMA2000 HRPD cells are disabled.This parameteris unavailable in this version.Cdma1xRttServiceHoSwitch: If this switch is on,service-based handovers to CDMA2000 1xRTT areenabled and UEs running a specific type of servicescan be handed over to CDMA2000 1xRTT. If thisswitch is off, service-based handovers to CDMA20001xRTT are disabled.This parameter is unavailable inthis version. UlQualityInterRATHoSwitch: If thisswitch is on, UL-quality-based inter-RAT handoversare enabled and UEs can be handed over to inter-RATcells to ensure service continuity when the UL signalquality is poor. If this switch is off, UL-quality-based

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TDLOFD-001053LOFD-001088 /TDLOFD-001088LOFD-001089 /TDLOFD-001089LOFD-001090 /TDLOFD-001090LOFD-001019 /TDLOFD-001019LOFD-001020 /TDLOFD-001020LOFD-001043 /TDLOFD-001043LOFD-001046 /TDLOFD-001046LOFD-001072 /TDLOFD-001072LOFD-001073 /TDLOF

SteeringtoUTRANCSFallbackSteeringtoGERANEnhanced CSFallbacktoCDMA20001xRTTPS Inter-RATMobilitybetweenE-UTRANandUTRANPS Inter-RATMobilitybetweenE-UTRANandGERANServicebasedinter-RAThandover toUTRANServicebasedinter-RAThandover toGERANDistancebased

inter-RAT handovers are disabled.InterPlmnHoSwitch: If this switch is on, inter-PLMNhandovers are enabled and UEs can be handed over tocells in other PLMNs. If this switch is off, inter-PLMN handovers are disabled. UtranFlashCsfbS-witch: This switch takes effect only whenUtranCsfbSwitch is on. If UtranFlashCsfbSwitch ison, flash CSFB to UTRAN is enabled and the eNodeBsends system information of candidate target UTRANcells to UEs during redirections. If UtranFlashCsfbS-witch is off, flash CSFB to UTRAN is disabled.GeranFlashCsfbSwitch: This switch takes effect onlywhen GeranCsfbSwitch is on. If GeranFlashCsfbS-witch is on, flash CSFB to GERAN is enabled and theeNodeB sends system information of candidate targetGERAN cells to UEs during redirections. IfGeranFlashCsfbSwitch is off, flash CSFB to GERANis disabled. ServiceBasedInterFreqHoSwitch: If thisswitch is on, service-based inter-frequency handoversare enabled and UEs running a specific type ofservices can be handed over to inter-frequency cells. Ifthis switch is off, service-based inter-frequencyhandovers are disabled. UlQualityInterFreqHoSwitch:If this switch is on, UL-quality-based inter-frequencyhandovers are enabled and UEs can be handed over tointer-frequency cells to ensure service continuity whenthe UL signal quality is poor. If this switch is off, UL-quality-based inter-frequency handovers are disabled.CsfbAdaptiveBlindHoSwitch: This switch takes effectonly when BlindHoSwitch is on. IfCsfbAdaptiveBlindHoSwitch is on, adaptive blindhandovers for CSFB are enabled and appropriatehandover mechanisms are selected for UEs based ontheir locations. If CsfbAdaptiveBlindHoSwitch is off,adaptive blind handovers for CSFB are disabled.UtranCsfbSteeringSwitch: If this switch is on, CSFBsteering to UTRAN is enabled and CSFB policies forUEs in idle mode can be configured. If this switch isoff, CSFB steering to UTRAN is disabled.GeranCsfbSteeringSwitch: If this switch is on, CSFBsteering to GERAN is enabled and CSFB policies forUEs in idle mode can be configured. If this switch isoff, CSFB steering to GERAN is disabled.CSFBLoadInfoSwitch: If this switch is on, load-basedCSFB is enabled and a target cell for CSFB is selectedbased on loads of candidate target cells. If this switchis off, load-based CSFB is disabled.Cdma1XrttEcsfbSwitch: If this switch is on, eCSFB to

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

D-001073TDLBFD-002018TDLOFD-001022TDLOFD-070228LOFD-081283 /TDLOFD-081203LOFD-070202 /TDLOFD-070202TDLOFD-081223

inter-RAThandover toUTRAN

Distancebasedinter-RAThandover toGERAN

MobilityManagement

Coverage BasedInter-frequencyHandover

SRVCCtoUTRAN

Service-RequestBasedInter-frequencyHandover

Ultra-FlashCSFB toGERAN

Ultra-FlashCSFB toUTRAN

CDMA2000 1xRTT is enabled and UEs can fall backto CDMA2000 1xRTT through handovers. If thisswitch is off, eCSFB to CDMA2000 1xRTT isdisabled. EmcBlindHoA1Switch: If this switch is on,blind handover event A1 measurements are enabled. Ifa blind handover event measurement conflicts with ahandover procedure, an emergency blind handovercan be triggered after the handover procedure iscomplete. If this switch is off, blind handover eventA1 measurements are disabled. If a blind handoverevent measurement conflicts with a handoverprocedure, an emergency blind handover cannot betriggered. EmcInterFreqBlindHoSwitch: If this switchis on, the eNodeB preferentially performs an inter-frequency blind handover when an emergency blindhandover is triggered. If this switch is off, the eNodeBonly performs an inter-RAT blind handover when anemergency blind handover is triggered. EPlmnSwitch:Indicates whether handovers to neighboring cellsunder the equivalent PLMNs (EPLMNs) are allowed.When inter-PLMN handovers are allowed, handoversto neighboring cells under the EPLMNs are allowed ifthis switch is on, and not allowed if this switch is off.The EPLMNs are delivered by the MME to the UE.ServiceReqInterFreqHoSwitch: If this switch is on,service request-based inter-frequency handovers areenabled and UEs using a specific type of services canbe handed over to inter-frequency cells. If this switchis off, service request-based inter-frequency handoversare disabled. This option applies only to LTE TDDnetworks. VoipHoControlSwitch: Indicates whetherthe eNodeB filters out target cells that do not supportVoIP services when processing intra-RAT handoversfor VoIP services. The eNodeB filters out such targetcells in the preceding scenario only when this switchis on. UtranUltraFlashCsfbSwitch: In this switch is on,ultra-flash CSFB to UTRAN is enabled and UEs canfall back to UTRAN based on the ultra-flash CSFBprocedure. If this switch is off, ultra-flash CSFB toUTRAN is disabled. GeranUltraFlashCsfbSwitch: Inthis switch is on, ultra-flash CSFB to GERAN isenabled and UEs can fall back to GERAN based onthe ultra-flash CSFB procedure. If this switch is off,ultra-flash CSFB to GERAN is disabled.GUI Value Range: IntraFreqCoverHoS-witch(IntraFreqCoverHoSwitch), InterFreqCoverHoS-witch(InterFreqCoverHoSwitch),UtranCsfbSwitch(UtranCsfbSwitch),

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

GeranCsfbSwitch(GeranCsfbSwitch),Cdma1xRttCsfbSwitch(Cdma20001xRttCsfbSwitch),UtranServiceHoSwitch(UtranServiceHoSwitch),GeranServiceHoSwitch(GeranServiceHoSwitch),CdmaHrpdServiceHoS-witch(Cdma2000HrpdServiceHoSwitch),Cdma1xRttServiceHoSwitch(Cdma20001xRttServiceHoSwitch), 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: NoneActual 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

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

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

ENodeBConnStateTimer

S1MsgWaitingTimerQci1

MODENODEBCONNSTATETIMERLSTENODEBCONNSTATETIMER

LBFD-002007 /TDLBFD-002007

RRCConnectionManagement

Meaning: Indicates the timer governing the period thatthe eNodeB waits for a response message from theMME when the UE are running services with the QCIof 1. If the timer expires, the eNodeB initiates a UEcontext release over the S1 interface.GUI Value Range: 1~200Unit: sActual Value Range: 1~200Default Value: 20

X2MessageWaitingTimerQci1

LOFD-002007 /TDLOFD-002007

Meaning: Indicates the timer governing the period thelocal eNodeB waits for a response message from thepeer eNodeB when the UE is running services withthe QCI of 1. If the timer expires, the eNodeBprocesses the same as the timer specified by theX2MessageWaitingTimer parameter expires.GUI Value Range: 1~200Unit: sActual Value Range: 1~200Default Value: 20

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

UuMessageWaitingTimerQci1

LBFD-002007 /TDLBFD-002007

Meaning: Indicates the timer governing the period theeNodeB waits for a response message from a UEwhen the UE is running services with the QCI of 1. Ifthe timer expires, the eNodeB initiates a UE contextrelease over the S1 interface.GUI Value Range: 1~200Unit: sActual Value Range: 1~200Default Value: 35

RrcConnStateTimer

UeInactiveTimerQci1

MODRRCCONNSTATETIMERLSTRRCCONNSTATETIMER

LBFD-002007 /TDLBFD-002007

Meaning: Indicates the length of the UE inactivitytimer for UEs that are running services of QCI 1. Ifthe eNodeB detects that a UE has neither received norsent data for a duration exceeding the value of thisparameter, the eNodeB releases the RRC connectionfor the UE. If this parameter is set to 0, the UEinactivity timer is not used. This timer takes effectduring the setup of bearers with a QCI of 1. During ahandover or RRC connection reestablishment to a newcell, the eNodeB determines whether the timer takeseffect based on whether the UE is running serviceswith a QCI of 1. If yes, the timer takes effect;otherwise, the timer does not take effect.GUI Value Range: 0~3600Unit: sActual Value Range: 0~3600Default Value: 20

CellStandardQci

TrafficRelDelay

MODCELLSTANDARDQCILSTCELLSTANDARDQCI

LBFD-002008 /TDLBFD-002008

RadioBearerManagement

Meaning: Indicates the waiting duration for theeNodeB to release services with a specific QCI afterthe eNodeB detects that the radio link is abnormal.When the eNodeB detects that the radio link isabnormal, the eNodeB waits for the UE to initiate anRRC connection reestablishment procedure to restoreservices. If the waiting duration times out, the eNodeBreleases the services.GUI Value Range: 0~65000Unit: msActual Value Range: 0~65000Default Value: 30000

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RlcPdcpParaGroup

RlcMode

ADDRLCPDCPPARAGROUPMODRLCPDCPPARAGROUPLSTRLCPDCPPARAGROUP

LBFD-002008 /TDLBFD-002008

Meaning: Indicates the RLC transmission mode. Onlythe AM and UM modes are available.GUI Value Range: RlcMode_AM(AcknowledgeMode), RlcMode_UM(Un-acknowledge Mode)Unit: NoneActual Value Range: RlcMode_AM, RlcMode_UMDefault Value: RlcMode_AM(Acknowledge Mode)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellAlgoSwitch

RacAlgoSwitch

MODCELLALGOSWITCHLSTCELLALGOSWITCH

LBFD-002023 /TDLBFD-002023LBFD-002024 /TDLBFD-002024LOFD-00102901

AdmissionControlCongestionControlRadio/transportresourcepre-emption

Meaning:Indicates whether to enable the admission and loadcontrol algorithms.

DlSwitch: Indicates whether to enable the algorithmof downlink admission control based on thesatisfaction rate. If this switch is on, the algorithm isenabled. If this switch is off, the algorithm is disabled.During the calculation of the QoS satisfaction rate ofservices with different QCIs, the satisfactionestimation method used dedicatedly for VoIP servicesis implemented on services with the QCI of 1. If aservice with the QCI of 1 is not a VoIP service, thesatisfaction rate calculated using this method is lowerthan the actual value, which affects the admission ofGBR services. Therefore, if not all the services withthe QCI of 1 are VoIP services, it is recommended thatthis switch be off.

UlSwitch: Indicates whether to enable the algorithmof uplink admission control based on the satisfactionrate. If this switch is on, the algorithm is enabled. Ifthis switch is off, the algorithm is disabled. During thecalculation of the QoS satisfaction rate of serviceswith different QCIs, the satisfaction estimationmethod used dedicated for VoIP services isimplemented on services with the QCI of 1. If aservice with the QCI of 1 is not a VoIP service, thesatisfaction rate calculated using this method is lowerthan the actual value, which affects the admission ofGBR services. Therefore, if not all the services withthe QCI of 1 are VoIP services, it is recommended thatthis switch be off.

DlPredictSwitch: Indicates whether to enable thealgorithm of downlink admission control based onprediction. If this switch is on, the algorithm isenabled. If this switch is off, the algorithm is disabled.

UlPredictSwitch: Indicates whether to enable thealgorithm of uplink admission control based onprediction. If this switch is on, the algorithm isenabled. If this switch is off, the algorithm is disabled.

GbrUsageSwitch: Indicates whether to enable thecheck on the number of PRBs used by GBR services.If this switch is on, the number of PRBs used byexisting GBR services is checked before a new GBRservice can be admitted. If this switch is off, thenumber of PRBs used by existing GBR services is not

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

checked during admission evaluation of new GBRservices

DlLdcSwitch: Indicates whether to implement loadcontrol in the downlink of a cell. If this switch is on,the system checks for congestion in the downlink ofthe cell. If the downlink is congested, load control isperformed. If this switch is off, the system does notcheck for congestion in the downlink of the cell andthe congestion cannot be relieved. During thecalculation of the QoS satisfaction rate of serviceswith different QCIs, the satisfaction estimationmethod used dedicated for VoIP services isimplemented on services with the QCI of 1. If aservice with the QCI of 1 is not a VoIP service, thesatisfaction rate calculated using this method is lowerthan the actual value, which affects the cell loadcontrol. Therefore, if not all the services with the QCIof 1 are VoIP services, it is recommended that thisswitch be off.

UlLdcSwitch: Indicates whether to implement loadcontrol in the uplink of a cell. If this switch is on, thesystem checks for congestion in the uplink of the cell.If the uplink is congested, load control is performed. Ifthis switch is off, the system does not check forcongestion in the uplink of the cell and the congestioncannot be relieved. During the calculation of the QoSsatisfaction rate of services with different QCIs, thesatisfaction estimation method used dedicated forVoIP services is implemented on services with theQCI of 1. If a service with the QCI of 1 is not a VoIPservice, the satisfaction rate calculated using thismethod is lower than the actual value, which affectsthe cell load control. Therefore, if not all the serviceswith the QCI of 1 are VoIP services, it isrecommended that this switch be off.

RelDrbSwitch: Indicates whether low-priority servicescan be released in the case of congestion. If thisswitch is on, low-priority services can be released. Ifthis switch is off, low-priority services cannot bereleased.

PreemptionSwitch: Indicates whether to enable thepreemption control algorithm. If this switch is on,preemption can be used when the admission of high-priority services fails. If this switch is off, onlyemergency calls can be admitted to the system whenresources are insufficient.

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

GUI Value Range: DlSwitch(dlCacSwitch),UlSwitch(ulCacSwitch),DlPredictSwitch(dlCacPredictSwitch),UlPredictSwitch(ulCacPredictSwitch),GbrUsageSwitch(GbrUsedPRbCheckSwitch),DlLdcSwitch(dlLdcSwitch),UlLdcSwitch(ulLdcSwitch),RelDrbSwitch(LdcDrbRelSwitch),PreemptionSwitch(PreemptionSwitch)Unit: NoneActual Value Range: DlSwitch, UlSwitch,DlPredictSwitch, UlPredictSwitch, GbrUsageSwitch,DlLdcSwitch, UlLdcSwitch, RelDrbSwitch,PreemptionSwitchDefault Value: DlSwitch:Off, UlSwitch:Off,DlPredictSwitch:Off, UlPredictSwitch:Off,GbrUsageSwitch:Off, DlLdcSwitch:Off,UlLdcSwitch:Off, RelDrbSwitch:Off,PreemptionSwitch:Off

CellRacThd

Qci1CongThd

MODCELLRACTHDLSTCELLRACTHD

LBFD-002024 /TDLBFD-002024

CongestionControl

Meaning:Indicates the congestion threshold for services withQCI of 1. This threshold applies to both UL and DL.

If the satisfaction rate of services with QCI of 1 in thecell becomes lower than this threshold, the serviceswith QCI of 1 enter the congested state.

If the satisfaction rate of services with QCI of 1 in thecell becomes higher than the sum of this threshold andthe congestion relief offset, the services with QCI of 1leave the congested state.GUI Value Range: 0~99Unit: %Actual Value Range: 0~99Default Value: 65

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUlschAlgo

UlschStrategy

LBFD-002025 /TDLBFD-002025TDLOFD-001015TDLOFD-00101502

BasicSchedulingDynamicSchedulingEnhancedScheduling

Meaning: Indicates the UL scheduling policy, whichdetermines the scheduling priority order in which UEsare arranged in UL. There are four UL schedulingstrategies: MAX C/I, proportional fair (PF), roundRobin (RR), and enhanced proportional fair (EPF).The MAX C/I policy schedules UEs in descendingorder of average signal to interference plus noise ratio(SINR). The PF policy schedules UEs in ascendingorder of ratio of the data rate to the SINR. The RRpolicy schedules each UE in sequence, and thereforeeach UE has an equal opportunity to be scheduled.The EPF policy schedules UEs in ascending order ofpriority. In EPF, the priority of an UE is calculatedbased on the following factors: the data rate, averageSINR, QoS-satisfying data rate for each service, andservice differentiation requirements of the UE. TheMAX C/I, PF, and RR policies are basic ULscheduling policies and supported by the eNodeB bydefault, whereas the EPF policy is intended forcommercial use.GUI Value Range: ULSCH_STRATEGY_EPF(EPF),ULSCH_STRATEGY_MAX_CI(MAX_CI),ULSCH_STRATEGY_PF(PF),ULSCH_STRATEGY_RR(RR)Unit: NoneActual Value Range: ULSCH_STRATEGY_EPF,ULSCH_STRATEGY_MAX_CI,ULSCH_STRATEGY_PF, ULSCH_STRATEGY_RRDefault Value: ULSCH_STRATEGY_EPF(EPF)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellAlgoSwitch

UlSchSwitch

LOFD-001016 /TDLOFD-001016LOFD-001048 /TDLOFD-001048LOFD-00101502/TDLOFD-00101502TDLBFD-002025LBFD-070102 /TDLBFD-070102LOFD-001002LOFD-001058LBFD-001006

VoIPSemi-persistentSchedulingTTIBundlingDynamicSchedulingBasicSchedulingTDLOFD-070224:SchedulingBasedon MaxBit RateMBR>GBRConfigurationUL 2x2MU-MIMOUL 2x4MU-MIMOAMC

Meaning:This parameter indicates the switches related to uplink(UL) scheduling in the cell. The switches are used toenable or disable specific UL scheduling functions.

SpsSchSwitch: Indicates the switch used to enable ordisable semi-persistent scheduling during talk spurtsof VoIP services. If this switch is on, semi-persistentscheduling is applied during talk spurts of VoIPservices. If this switch is off, dynamic scheduling isapplied during talk spurts of VoIP services.

SinrAdjustSwitch: Indicates whether to adjust themeasured signal to interference plus noise ratio(SINR) based on ACK/NACK in UL hybrid automaticrepeat request (HARQ) processes.

PreAllocationSwitch: Indicates whether to enablepreallocation in the uplink. When this switch is on: (1)If SmartPreAllocationSwitch is off and a UE is in thediscontinuous reception (DRX) state, preallocation isdisabled for the UE in the uplink; (2) IfSmartPreAllocationSwitch is off and the UE is not inthe DRX state, preallocation is enabled for the UE inthe uplink; (3) If SmartPreAllocationSwitch is on andthe SmartPreAllocationDuration parameter value isgreater than 0, smart preallocation is enabled for theUE in the uplink; (4) If SmartPreAllocationSwitch ison and the SmartPreAllocationDuration parametervalue is 0, preallocation is disabled for the UE in theuplink. If this switch is off, preallocation is disabledfor the UE in the uplink. If bearer-level preallocationor bearer-level smart preallocation is enabled for a UEwith a QCI class, cell-level preallocation and cell-level smart preallocation do not apply to UEs with theQCI.

UlVmimoSwitch: Indicates whether to enable multi-user MIMO (MU-MIMO) in the UL. If this switch ison, the eNodeB performs MU-MIMO pairing amongUEs based on related principles. UEs forming a pairtransmit data using the same time-frequencyresources, which improves system throughput andspectral efficiency.

TtiBundlingSwitch: Indicates whether to enabletransmission time interval (TTI) bundling. If TTIbundling is enabled, more transmission opportunitiesare available to UEs within the delay budget for VoIP

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

services on the Uu interface, thereby improving uplinkcoverage.

ImIcSwitch: Indicates whether to enable theintermodulation interference (IM) cancellation forUEs. When data is transmitted in both uplink anddownlink, two IM components are generatedsymmetrically beside the Direct Current (DC)subcarrier on the downlink receive channel due tointerference from uplink radio signals. If this switch ison, IM component elimination is performed on UEs.If this switch is off, IM component elimination is notperformed on UEs. This switch applies only to FDDcells working in frequency band 20.

SmartPreAllocationSwitch: Indicates whether toenable uplink smart preallocation when preallocationis enabled (by turning on PreAllocationSwitch). Ifboth PreAllocationSwitch and SmartPreAllocationS-witch are on and SmartPreAllocationDuration is set toa value greater than 0, uplink smart preallocation isenabled; otherwise, uplink smart preallocation isdisabled.

PuschDtxSwitch: Indicates whether the eNodeB usesthe physical uplink shared channel (PUSCH)discontinuous transmission (DTX) detection resultduring UL scheduling. In an LTE FDD cell, if thisswitch is on, based on the PUSCH DTX detectionresult, the eNodeB determines whether to performadaptive retransmission during UL scheduling andalso adjusts the control channel element (CCE)aggregation level of the physical downlink controlchannel (PDCCH) carrying downlink controlinformation (DCI) format 0. If an FDD cell isestablished on an LBBPc, this switch takes effect onlywhen the cell uses less than four RX antennas andnormal cyclic prefix (CP) in the uplink and theSrsCfgInd parameter in the SRSCfg MO is set toBOOLEAN_TRUE. Note that the LBBPc does notsupport PUSCH DTX detection for UEs with MU-MIMO applied. In an LTE TDD cell, this switch takeseffect only when the cell is configured with subframeconfiguration 2 or 5. After this switch takes effect, theeNodeB adjusts the CCE aggregation level based onthe PUSCH DTX detection results. Note that LTETDD cells established on LBBPc boards do notsupport PUSCH DTX detection.

UlIblerAdjustSwitch: Indicates whether to enable theuplink initial block error rate (IBLER) adjustment

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

algorithm. If this switch is on, IBLER convergencetarget is adjusted to increase the cell edge throughput.When this switch is on, the recommendedconfiguration of parameter DopMeasLevel in MOCellUlschAlgo is CLASS_1.

UlEnhancedFssSwitch: Indicates whether to enableuplink load-based enhanced frequency selection. Thisswitch applies only to FDD cells.

UlIicsAlgoSwitch: Indicates whether to enable the ULIICS algorithm. If this switch is on, interference canbe reduced based on accurate detection of userattributes and resource scheduling coordination,thereby increasing the cell edge throughput. Thisswitch applies only to LTE TDD networks.

UlEnhancedSrSchSwitch: Indicates whether uplink re-scheduling is performed only when the On Durationtimer for the DRX long cycle starts. Uplink re-scheduling is required if the number of HARQretransmissions for a scheduling request (SR) reachesthe maximum value but the scheduling still fails. Ifthis switch is on, uplink re-scheduling is performedonly when the On Duration timer for the DRX longcycle starts. If this switch is off, uplink re-schedulingis performed immediately when the number of HARQretransmissions for SR reaches the maximum valuebut the scheduling still fails. It is recommended thatthe switch be turned on in live networks.

SchedulerCtrlPowerSwitch: Indicates whether theuplink scheduler performs scheduling withoutconsidering power control restrictions. If this switch ison, the uplink scheduler performs scheduling withoutconsidering power control restrictions, which ensuresfull utilization of the transmit power for all UEs. Ifthis switch is off, the uplink scheduler considerspower control restrictions while performingscheduling, which prevents full utilization of thetransmit power for UEs at far or medium distancesfrom the cell center.

UlMinGbrSwitch: Indicates whether to enable uplinkminimum guaranteed bit rate (GBR). If this switch ison, the minimum GBR of non-GBR services isensured by increasing the scheduling priority of UEswhose non-GBR service rates are lower than theminimum GBR of GBR services.

UlMbrCtrlSwitch: Indicates whether to enable uplinkscheduling based on the maximum bit rate (MBR) and

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

guaranteed bit rate (GBR) on the GBR bearer. If thisswitch is on, the eNodeB performs uplink schedulingon GBR bearers based on the MBR and GBR. If thisswitch is off, the eNodeB performs uplink schedulingon GBR bearers based only on the GBR.

MbrUlSchSwitch: Indicates whether the eNodeBperforms uplink scheduling based on MBR. If thisswitch is on, the eNodeB prioritizes UEs based on theMBRs during uplink scheduling. This parameterapplies only to LTE TDD cells.

UeAmbrUlSchSwitch: Indicates whether the eNodeBperforms uplink scheduling based on the aggregatemaximum bit rate (AMBR) of UEs. If this switch ison, the eNodeB prioritizes UEs based on the AMBRsduring uplink scheduling. This parameter applies onlyto LTE TDD cells.

UlEnhancedDopplerSwitch: Indicates whether toenable enhanced uplink scheduling based on mobilityspeed. If this switch is on, enhanced uplink schedulingbased on mobility speed is enabled. If this switch ison, the eNodeB determines whether a UE is a low-mobility UE based on the Doppler measurement in thephysical layer, and then improves uplink frequencyselective scheduling performance for low-mobilityUEs. If this switch is off, enhanced uplink schedulingbased on mobility speed is disabled. This switch takeseffect only when the UlEnhancedDopplerSwitchparameter is set to CLASS_1. This switch does nottake effect on cells established on an LBBPc.

UlRaUserSchOptSw: Indicates whether the eNodeBraises the scheduling priority of UEs sending uplinkaccess signaling, including MSG5 and the RRCConnection Reconfiguration Complete message. Ifthis switch is on, the eNodeB raises the schedulingpriority of UEs sending uplink access signaling. If thisswitch is off, the eNodeB does not raise thescheduling priority of UEs sending uplink accesssignaling.

UlLast2RetransSchOptSwitch: Indicates whether toenable optimization on the scheduling policy for thelast two retransmissions. If this switch is on,optimization on the scheduling policy for the last tworetransmissions is enabled. If the UE transmit power isnot limited, adaptive retransmission is used and thenumber of RBs increases in the last tworetransmissions to increase the receive success rate of

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

the last two retransmissions and decrease uplinkRBLER. If this switch is off, optimization on thescheduling policy for the last two retransmissions isdisabled. This switch does not apply to LTE TDDcells.

UlInterfFssSwitch: Indicates whether to enableinterference-based uplink frequency-selectivescheduling. This switch applies only to LTE FDDnetworks.

UlSmallRBSpectralEffOptSw: Indicates whether toenable spectral efficiency optimization on uplinksmall RBs. If this switch is on, the optimization isenabled, thereby ensuring that the transmission blocksize calculated based on optimized spectral efficiencyis not less than the traffic volume needs to bescheduled. If this switch is off, the optimization isdisabled.

PuschUsePucchRbSwitch: Indicates whether PUCCHRBs can be occupied by the PUSCH. In scenarioswith a single user, if this switch is on, PUCCH RBscan be occupied by the PUSCH. If this switch is off,PUCCH RBs cannot be occupied by the PUSCH. Inscenarios with multiple users, PUCCH RBs cannot beoccupied by the PUSCH no matter whether this switchis on or off.

PuschDtxSchOptSwitch: If this switch is on, theeNodeB determines whether to perform adaptiveretransmission during UL scheduling based on thePUSCH DTX detection result. This switch takes effectonly when subframe configuration 2 or 5 is used. If aTDD cell is established on an LBBPc, PUSCH DTXdetection is not supported. This switch applies only toLTE TDD cells.

PrachRbReuseSwitch:If this switch is on, the PUSCHand PRACH transmissions can use the same resource.

If this switch is off, the PUSCH and PRACHtransmissions cannot use the same resource. Thisswitch applies only to LTE TDD cells.

ULFSSAlgoswitch:If this switch is off, uplinkfrequency-selective scheduling is disabled. If thisswitch is on, uplink frequency-selective scheduling isenabled. This switch is invalid if the HighSpeedFlagparameter in the Cell MO is set toHIGH_SPEED(High speed cell flag) or

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

ULTRA_HIGH_SPEED(Ultra high speed cell flag),that is, uplink frequency-selective scheduling isdisabled in high speed and ultra high speed mobilityconditions. This switch applies only to LTE TDDcells.

SrSchDataAdptSw: Indicates whether to enable datavolume adaption in SR scheduling. Data volumeadaption in SR scheduling is enabled only when thisoption is selected.

UlFssUserThdStSwitch: UlFssUserThdStSwitch:Indicates whether to enable the optimization policy onthe UE number threshold for frequency selectivescheduling. The optimization policy is enabled onlywhen 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(UlLast2RetransSchOptSwitch), UlInterfFssSwitch(UlInterfFssSwitch),UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEf-ficiencyOptSw), PuschUsePucchRbS-witch(PuschUsePucchRbSwitch), PuschDtxSchOptS-witch(PuschDtxSchOptSwitch),ULFSSAlgoSwitch(ULFSSAlgoSwitch),PrachRbReuseSwitch(PrachRbReuseSwitch),SrSchDataAdptSw(SrSchDataAdptSw),UlFssUserThdStSwitch(UlFssUserThdStSwitch)Unit: NoneActual Value Range: SpsSchSwitch,SinrAdjustSwitch, PreAllocationSwitch,UlVmimoSwitch, TtiBundlingSwitch, ImIcSwitch,

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

SmartPreAllocationSwitch, PuschDtxSwitch,UlIblerAdjustSwitch, UlEnhancedFssSwitch,UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch,UlIicsAlgoSwitch, UlMinGbrSwitch,UlMbrCtrlSwitch, MbrUlSchSwitch,UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch,UlRaUserSchOptSw, UlLast2RetransSchOptSwitch,UlInterfFssSwitch, UlSmallRBSpectralEffOptSw,PuschUsePucchRbSwitch, PuschDtxSchOptSwitch,ULFSSAlgoSwitch, PrachRbReuseSwitch,SrSchDataAdptSw, UlFssUserThdStSwitchDefault 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

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellAlgoSwitch

DlSchSwitch

LOFD-001016 /TDLOFD-001016LOFD-00101502/TDLOFD-00101502LOFD-001109 /TDLOFD-001109LOFD-001070 /TDLOFD-001070TDLOFD-070224LBFD-002025 /TDLBFD-002025LBFD-002031 /TDLBFD-002031LBFD-070102 /TDLBFD-070102LBFD-060202

VoIPSemi-persistentSchedulingDynamicSchedulingDLNon-GBRPacketBundlingSymbolPowerSavingSchedulingBasedon MaxBit RateBasicSchedulingSupportofaperiodic CQIreportsMBR>GBRConfigurationEnhanced DLFrequencySelective

Meaning:Indicates the switches related to downlink schedulingin the cell.

FreqSelSwitch: Indicates whether to enable frequencyselective scheduling. If this switch is on, data istransmitted on the frequency band in good signalquality.

ServiceDiffSwitch: Indicates whether to enableservice differentiation. If this switch is on, servicedifferentiation is applied. If this switch is off, servicedifferentiation is not applied.

SpsSchSwitch: Indicates whether to enable semi-persistent scheduling during talk spurts of VoIPservices. If this switch is on, semi-persistentscheduling is applied during talk spurts of VoIPservices. If this switch is off, dynamic scheduling isapplied during talk spurts of VoIP services.

MBSFNShutDownSwitch: Indicates whether toenable Multimedia Broadcast multicast service SingleFrequency Network (MBSFN) subframe shutdown. Ifthis switch is on, MBSFN subframe shutdown isapplied. If this switch is off, MBSFN subframeshutdown is not applied. This switch is valid onlywhen SymbolShutdownSwitch is on. If the MBSFNshutdown switch is on, the setting of the switch formapping SIBs to SI messages becomes invalid. Thelatter can be specified by the SiMapSwitch parameterin the CellSiMap MO. If the MBSFN subframeshutdown switch is off, the setting of the switch formapping SIBs to SI messages becomes valid. MBSFNsubframe shutdown applies only to LTE-only basestations.

NonGbrBundlingSwitch: Indicates whether to enabledownlink non-GBR packet bundling. If this switch ison, delay of non-GBR services can be controlled innon-congestion scenarios. If this switch is off, delay ofnon-GBR services cannot be controlled.

EnAperiodicCqiRptSwitch: Indicates whether toenable enhanced aperiodic channel quality indicator(CQI) reporting. If this switch is on, the eNodeBtriggers aperiodic CQI reporting for a UE based ondownlink services of the UE and the interval at whichthe UE sends periodic CQI reports. If this switch isoff, UEs under non-frequency selective scheduling donot trigger aperiodic CQI reporting based on downlink

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

services and triggers an aperiodic CQI reporting if novalid periodic CQI reports are sent in eightconsecutive periodic CQI reporting periods.

DlMbrCtrlSwitch: Indicates whether to enabledownlink scheduling based on the maximum bit rate(MBR) and guaranteed bit rate (GBR) on the GBRbearer. If this switch is on, the eNodeB performsdownlink scheduling on GBR bearers based on theMBR and GBR. If this switch is off, the eNodeBperforms downlink scheduling on GBR bearers basedon the GBR only.

MbrDlSchSwitch: Indicates whether the eNodeBperforms downlink scheduling based on MBR. If thisswitch is on, the eNodeB determines priorities of UEsbased on the MBR in downlink scheduling. Thisparameter applies only to LTE TDD cells.

UeAmbrDlSchSwitch: Indicates whether the eNodeBperforms downlink scheduling based on the aggregatemaximum bit rate (AMBR) of UEs. If this switch ison, the eNodeB determines priorities of UEs based onthe AMBR of UEs in downlink scheduling. Thisparameter applies only to LTE TDD cells.

EpfEnhancedSwitch: Indicates whether to enableenhanced proportional fair (EPF) for downlinkscheduling. EPF for downlink scheduling is enabledonly when this switch is on.

AperiodicCqiTrigOptSwitch: Indicates whether totrigger aperiodic CQI optimization. If this switch ison, a UE performing initial access triggers aperiodicCQI reporting based on related triggering conditionsafter the DLMAC instance has been established for200 ms and the eNodeB receives MSG5. Consider thataperiodic CQI reporting is triggered by invalid CQIreports in eight consecutive CQI reporting periods. Ifcyclic redundancy check (CRC) on aperiodic CQIreports fails, aperiodic CQI reporting is not repeatedlytriggered when DRX is enabled; or aperiodic CQIreporting is triggered after eight TTIs when DRX isdisabled. If this switch is off, a UE performing initialaccess triggers aperiodic CQI reporting based onrelated triggering conditions after the DLMACinstance has been established for 200 ms. Considerthat aperiodic CQI reporting is triggered by invalidCQI reports in eight consecutive CQI reportingperiods. If CRC on aperiodic CQI reports fails,

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

aperiodic CQI reporting is triggered after eight TTIsregardless of the DRX status.

VoipTbsBasedMcsSelSwitch: Indicates whether themodulation and coding scheme (MCS) index isselected based on the transport block size (TBS) indownlink scheduling for VoIP services. If this switchis on, the MCS index is selected based on the TBS indownlink scheduling for VoIP services. If this switchis off, the MCS index is not selected based on the TBSin downlink scheduling for VoIP services.

UeSigMcsEnhanceSwitch: Indicates whether toenable or disable the optimized MCS algorithm forUE signaling. The optimized MCS algorithm for UEsignaling takes effect after this switch is on. Thisparameter applies only to LTE TDD cells.

PagingInterfRandSwitch: Indicates whether to enableor disable interference randomizing for pagingmessages. If this switch is on, interferencerandomizing is enabled for paging messages. Thisswitch is valid only in TDD mode.

DlSingleUsrMcsOptSwitch: Indicates conditions forlowering the modulation and coding scheme (MCS)for a single UE. When this switch is on, the MCS canbe lowered for a UE if the UE is the only UE to bescheduled in a transmission time interval (TTI). Whenthis switch is off, the MCS can be lowered for a UE ifthere are only 10 percent of TTIs having UEs toschedule in each sparse packet determination periodand the UE is the only UE to be scheduled in eachTTI.

SubframeSchDiffSwitch: Indicates whether subframes3 and 8 perform scheduling based on increasednumber of uplink scheduling UEs when subframeconfiguration type 2 is used. If this switch is on,subframes 3 and 8 perform scheduling based onincreased number of uplink scheduling UEs whensubframe configuration type 2 is used. If this switch isoff, subframes 3 and 8 perform scheduling based onthe policy that other downlink subframes adopt whensubframe configuration type 2 is used. This switch isdedicated to LTE TDD cells.

TailPackagePriSchSwitch: Indicates the switch thatcontrols the scheduling of downlink connected tailpackages in the bearer. If this switch is on, theconnected tail package is scheduled preferentially in

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

the next TTI, which reduces the delay and increasesthe transmission rate. If this switch is off, thescheduling strategy of the connected tail package isthe same as other downlink subframes. This switch isdedicated to LTE TDD cells.

FreqSelJudgeIgnorDopplerSwitch: Indicates whetherDoppler determination conditions are consideredduring channel frequency selective schedulingdetermination. Doppler determination conditions areconsidered only when this option is deselected. Thisoption applies only to LTE FDD.

SIB1InterfRandSwitch: Indicates whether to enableSIB1 interference randomizing. If this switch is on,interference randomizing is enabled for SIB1. Thisswitch 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: NoneActual Value Range: FreqSelSwitch,ServiceDiffSwitch, SpsSchSwitch,MBSFNShutDownSwitch, NonGbrBundlingSwitch,EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch,MbrDlSchSwitch, UeAmbrDlSchSwitch,EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch,VoipTbsBasedMcsSelSwitch, PagingInterfRand-Switch, DlSingleUsrMcsOptSwitch,SubframeSchDiffSwitch, TailPackagePriSchSwitch,

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDop-plerSwitch, SIB1InterfRandSwitchDefault 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

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellAlgoSwitch

CqiAdjAlgoSwitch

LOFD-00101501/TDLOFD-00101501LOFD-00101502/TDLOFD-00101502

CQIAdjustmentDynamicScheduling

Meaning:CqiAdjAlgoSwitch: Indicates whether to allow theeNodeB to adjust the UE-reported CQI based on theinitial block error rate (IBLER).

If this switch is On, the CQI adjustment algorithm isenabled. In this case, the eNodeB adjusts the UE-reported CQI based on the IBLER.

If this switch is off, the CQI adjustment algorithm isdisabled. In this case, the eNodeB does not adjust theUE-reported CQI based on the IBLER.

StepVarySwitch: Indicates whether to enable thevariable-step-based adjustment algorithm.

If this switch is On, the variable-step-basedadjustment algorithm is enabled to accelerate theconvergence of IBLER. In this case, rapid adjustmentat large steps is applied if there is a relatively largedifference between the measured IBLER and targetIBLER; fine-tuning at small steps is applied if themeasured IBLER approaches the target IBLER.

If this switch is off, the adjustment is performed at afixed step.

DlVarIBLERtargetSwitch: Indicates whether to enabledownlink target IBLER adaption.

If this switch is On, the downlink target IBLER isadjusted based on the size of transport blocks (TBs) toimprove the spectral efficiency.

If this switch is off, the target IBLER is determinedbased on the setting of DlEnVarIblerTargetSwitch.

TddBundlingCqiAdjOptSwitch: Indicates whether touse optimized CQI adjustment algorithm in ACKbundling mode.

If this switch is On, the optimized CQI adjustmentalgorithm is used.

If this switch is off, the optimized CQI adjustmentalgorithm cannot be used.

TddMultiplexingCqiAdjOptSwitch: Indicates whetherto use the optimized CQI adjustment algorithm inACK multiplexing mode.

If this switch is On, the optimized CQI adjustmentalgorithm is used.

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

If this switch is off, the optimized CQI adjustmentalgorithm cannot be used.

AdaptiveStepVarySwitch: Indicates whether to enableadaptive step change in CQI adjustment.

If this switch is On, significant changes in the signalquality can be detected, and the CQI adjustment isperformed at a large step, accelerating the IBLERconvergence.

If this switch is off, the CQI adjustment is performedat a fixed step.

DlCqiAdjDeltaOptSwitch: Indicates whether to enableoptimization on downlink CQI adjustment. If thisswitch is off, the CQI adjustment is calculated basedon the following formula: CQI adjustment = (Numberof ACKs for initial transmissions x CQI adjustmentper ACK + Number of NACKs for initialtransmissions x CQI adjustment per NACK)/(Numberof NACKs for initial transmissions + Number ofACKs for initial transmissions). If this switch is On,the CQI adjustment is calculated based on thefollowing formula: CQI adjustment = Number ofACKs for initial transmissions x CQI adjustment perACK + Number of NACKs for initial transmissions xCQI adjustment per NACK).

DlEnVarIblerTargetSwitch: Indicates whether toenable enhanced downlink target IBLER adaption. Ifthis switch is On, the downlink target IBLER isadaptively adjusted based on CQI fluctuation and TBsize. If this switch is off, the downlink target IBLERpolicy is controlled by DlVarIBLERtargetSwitch. Thisswitch applies only to FDD cells.

DlRetxTbsIndexAdjOptSwitch: Indicates whether toenable transport block size (TBS) index adjustmentoptimization in retransmissions.

If this switch is On, TBS index adjustmentoptimization in retransmissions is enabled. The TBSindex is lowered for the scheduling of the last tworetransmissions, and the TBS index is determinedbased on the CQI adjustment for the scheduling ofother retransmissions. If this switch is off, TBS indexadjustment optimization in retransmissions isdisabled. The TBS index is determined based on theCQI adjustment for the scheduling of allretransmissions.

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CfiConvertOptSwitch: Indicates whether to enableCFI calculation optimization. If this switch is turnedon, new CFI calculation tables for normal and specialsubframes are used to ensure more accurate MCSselection in normal and special subframes andfacilitate IBLER convergence to the target value. Ifthis switch is turned off, the original CFI calculationtables for normal and special subframes are used. Thisswitch applies only to LTE TDD networks.

BundlingOptThdSwitch: Indicates whether to adjustthe MCS index threshold for enabling the optimizedCQI adjustment algorithm in TDD bundling mode. Ifthis switch is turned on, the lower MCS indexthreshold for enabling the optimized CQI adjustmentalgorithm in TDD bundling mode is changed fromMCS index 6 to MCS index 0. If this switch is turnedoff, the lower MCS index threshold for enabling theoptimized CQI adjustment algorithm in TDD bundlingmode is MCS index 6. This switch applies only toLTE 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: NoneActual Value Range: CqiAdjAlgoSwitch,StepVarySwitch, DlVarIBLERtargetSwitch,TddBundlingCqiAdjOptSwitch, TddMultiplexingC-qiAdjOptSwitch, AdaptiveStepVarySwitch,DlCqiAdjDeltaOptSwitch, DlEnVarIblerTargetSwitch,DlRetxTbsIndexAdjOptSwitch,CfiConvertOptSwitch, BundlingOptThdSwitchDefault Value: CqiAdjAlgoSwitch:On,StepVarySwitch:Off, DlVarIBLERtargetSwitch:Off,TddBundlingCqiAdjOptSwitch:Off,TddMultiplexingCqiAdjOptSwitch:Off,AdaptiveStepVarySwitch:Off, DlCqiAdjDeltaOptS-

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

witch:Off, DlEnVarIblerTargetSwitch:Off,DlRetxTbsIndexAdjOptSwitch:Off,CfiConvertOptSwitch:Off,BundlingOptThdSwitch:Off

CellUlschAlgo

SrMaskSwitch

LOFD-001016 /TDLOFD-001016

VoIPSemi-persistentScheduling

Meaning: Indicates whether to enable schedulingrequest (SR) masking in logical channels for UEscomplying with 3GPP Release 9 or later when theSpsSchSwitch option under the UlSchSwitchparameter is selected. If this parameter is set toON(On), SR masking in logical channels is enabled. Ifthis parameter is set to OFF(Off), SR masking inlogical channels is disabled.GUI Value Range: OFF(Off), ON(On)Unit: NoneActual Value Range: OFF, ONDefault Value: OFF(Off)

CellUlschAlgo

SpsRelThd

LOFD-00101502/TDLOFD-00101502

DynamicScheduling

Meaning: Indicates the threshold for the number ofconsecutive zero-payload packets received by theeNodeB. After receiving consecutive zero-payloadpackets of a number that is equal to the value of thisparameter, the eNodeB performs implicit release ofsemi-persistent resources.GUI Value Range: 2~3Unit: NoneActual Value Range: 2~3Default Value: 2

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellAlgoSwitch

UlPcAlgoSwitch

LBFD-002009 /TDLBFD-002009LBFD-002026 /TDLBFD-002026LBFD-081101 /TDLBFD-081104

Broadcast ofsysteminformationUplinkPowerControlPUCCHOuterLoopPowerControl

Meaning:Indicates the switches used to enable or disable powercontrol for the PUSCH or PUCCH.CloseLoopSpsSwitch: Indicates whether to enableclosed-loop power control for the PUSCH in semi-persistent scheduling mode. If this switch is on, TPCcommands are adjusted based on correctness of thereceived initial-transmission packets to decrease theIBLER. InnerLoopPuschSwitch: Indicates whether toenable inner-loop power control for the PUSCH indynamic scheduling mode. Inner-loop power controlfor the PUSCH in dynamic scheduling mode isenabled only when this switch is on.PhSinrTarUpdateSwitch: None. InnerLoopPucchS-witch: Indicates whether to enable inner-loop powercontrol for the PUCCH. Inner-loop power control forthe PUCCH is enabled only when this switch is on.OiSinrTarUpdateSwitch: None. PowerSavingSwitch:None. CloseLoopOptPUSCHSwitch: Indicateswhether to enable the optimization on closed-looppower control for the PUSCH in dynamic schedulingmode. This parameter applies only to LTE TDD cells.PucchPcDtxSinrSwitch: Indicates whether theeNodeB processes the measured uplink SINR in theDTX state when the PUCCH DTX is detected. If thisswitch is off, the eNodeB does not process themeasured uplink SINR in the DTX state when thePUCCH DTX is detected. If this switch is on, theeNodeB processes the measured uplink SINR evenwhen PUCCH DTX is detected, generates powercontrol commands based on the SINR, and deliversthe power control commands to UEs.PuschIoTCtrlSwitch: Indicates whether to enableinterference control in closed-loop power control forthe PUSCH in dynamic scheduling mode. Interferencecontrol in closed-loop power control for the PUSCHin dynamic scheduling mode is enabled only whenthis switch is on. SrsPcSwitch: Indicates whether toenable SRS power control adjustment. SRS powercontrol adjustment is enabled only when this switch ison. This switch applies only to LTE TDD.NearPointUeOptPUSCHSwitch: Indicates whether toapply optimized closed-loop power control for thePUSCH to UEs near the cell center. The optimizationhelps UEs near the cell center to avoid unnecessarypower lowering due to inter-RAT or abruptinterference. If this switch is on, optimized closed-loop power control for the PUSCH is applied to UEs

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

near the cell center. If this switch is off, optimizedclosed-loop power control for the PUSCH is notapplied to UEs near the cell center. This switchapplies only to LTE FDD cells. PuschRsrpHighThd-Switch: Indicates whether closed-loop power controlfor the PUSCH limits the maximum value of RSRP. Ifthis switch is off, closed-loop power control for thePUSCH does not limit the maximum value of RSRP.If this switch is on, the maximum value of RSRPcannot exceed the RSRP value specified by thePuschRsrpHighThd parameter in the CellAlgoSwitchin this version. This switch applies only to LTE FDDcells. OuterLoopPucchSwitch: Indicates whether toenable outer-loop PUCCH power control. Outer-loopPUCCH power control is enabled only when thisswitch is on.This option does not apply to cellsestablished on LBBPc boards.

GroupPCForPucchSwitch: Indicates whether to enablegroup power control for the PUCCH in dynamicscheduling mode. This switch applies only to LTETDD cells in which UEs must support group powercontrol 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: NoneActual Value Range: CloseLoopSpsSwitch,InnerLoopPuschSwitch, PhSinrTarUpdateSwitch,InnerLoopPucchSwitch, OiSinrTarUpdateSwitch,PowerSavingSwitch, CloseLoopOptPUSCHSwitch,PucchPcDtxSinrSwitch, PuschIoTCtrlSwitch,SrsPcSwitch, NearPointUeOptPUSCHSwitch,

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

PuschRsrpHighThdSwitch, OuterLoopPucchSwitch,GroupPCForPucchSwitchDefault 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

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellAlgoSwitch

DlPcAlgoSwitch

LBFD-002003 /TDLBFD-002003LBFD-002009 /TDLBFD-002009LBFD-002016 /TDLBFD-002016

PhysicalChannelManagementBroadcast ofsysteminformationDynamicDownlink PowerAllocation

Meaning:Indicates the switches used to enable or disable powercontrol for PDSCH, PDCCH, and PHICH.

PdschSpsPcSwitch: Indicates the switch for powercontrol during semi-persistent scheduling on thePDSCH. If the switch is off, power is allocated evenlyduring semi-persistent scheduling on the PDSCH. Ifthe switch is on, power control is applied during semi-persistent scheduling on the PDSCH, ensuringcommunication quality (indicated by IBLER) of VoIPservices in the QPSK modulation scheme.

PhichInnerLoopPcSwitch: Indicates the switch forPHICH inner-loop power control. If the switch is off,only the initial transmit power for the PHICH is set. Ifthe switch is on, the eNodeB controls the physicalchannel transmit power to enable the receive SINR toconverge to the target SINR.

PdcchPcSwitch: Indicates the switch for PDCCHpower control. If the switch is off, power is allocatedevenly to PDCCH. If the switch is on, power allocatedto PDCCH is adjusted dynamically.

EDlMaxTXPwrSwitch: Indicates the switch forenhanced maximum TX power of the cell. If thisswitch is off, the maximum TX power of the cell isdetermined by the reference signal (RS) power and thescaling factor indexes Pa and Pb. If this switch is on,the maximum TX power of the cell can be increasedto improve the RB usage in the cell. This switch hasno impact on the TDD 20M, TDD 15HMz and 10Mcell.

BFModeUserPwrSwitch: Specifies whether to turn onthe UE power optimization switch in BF mode. If theBFModeUserPwrSwitch check box is cleared, BF UEsadopt the existing power allocation principle. If theBFModeUserPwrSwitch check box is selected, theeNodeB increases the BF UE power based on theconfigured power headroom. This switch applies onlyto LTE TDD networks.

SigPowerIncreaseSwitch: Indicates the switchcontrolling signaling power improvement. If thisswitch is off, the signaling is transmitted using theoriginal power during network entry. If this switch ison, the PDSCH transmit power increases whenscheduling is performed for downlink retransmission

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

of signaling during network entry. This switch appliesonly to LTE TDD networks.GUI Value Range: PdschSpsPcSwitch,PhichInnerLoopPcSwitch, PdcchPcSwitch,EDlMaxTXPwrSwitch, BFModeUserPwrSwitch,SigPowerIncreaseSwitchUnit: NoneActual Value Range: PdschSpsPcSwitch,PhichInnerLoopPcSwitch, PdcchPcSwitch,EDlMaxTXPwrSwitch, BFModeUserPwrSwitch,SigPowerIncreaseSwitchDefault Value: PdschSpsPcSwitch:Off,PhichInnerLoopPcSwitch:Off, PdcchPcSwitch:On,EDlMaxTXPwrSwitch:Off,BFModeUserPwrSwitch:Off, SigPowerIncreaseS-witch:Off

PdcpRohcPara

RohcSwitch

MODPDCPROHCPARALSTPDCPROHCPARA

LOFD-001017 /TDLOFD-001017

RObustHeaderCompression(ROHC)

Meaning:Indicates whether to enable ROHC.

Set this parameter to ON if the eNodeB is expected tosupport VoIP or video services.GUI Value Range: OFF(Off), ON(On)Unit: NoneActual Value Range: OFF, ONDefault Value: OFF(Off)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUlschAlgo

UlVoipRlcMaxSegNum

LOFD-00101502/TDLOFD-00101502

DynamicScheduling

Meaning:Indicates whether to apply upper limit control onservice data unit (SDU) segmentation at the radio linkcontrol (RLC) layer in the uplink for VoIP servicesscheduled in non-TTI bundling mode and themaximum SDU segments at the RLC layer.

If this parameter is set to 0, the upper limit control onSDU segmentation at the RLC layer is disabled in theuplink for VoIP services scheduled in non-TTIbundling mode.

If this parameter is set to a non-zero value X, upperlimit control on SDU segmentation at the RLC layer isenabled and a maximum of X SDU segments that canbe divided for VoIP services in uplink dynamicscheduling in non-TTI bundling mode.GUI Value Range: 0~20Unit: NoneActual Value Range: 0~20Default Value: 0

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

GlobalProcSwitch

LcgProfile

LBFD-002025 /TDLBFD-002025LOFD-00101502/TDLOFD-00101502

BasicSchedulingDynamicScheduling

Meaning:Indicates the logical channel group configuration.

Currently, three logical channel group profiles areavailable. If this parameter is set toLCG_PROFILE_0, the control-plane services (SRB1,SRB2, and bearers with a QCI of 5), VoIP services(bearers with a QCI of 1), GBR services, and non-GBR services are assigned logical channel groups 0,1, 2, and 3, respectively.

If this parameter is set to LCG_PROFILE_1, thecontrol-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, thecontrol-plane services, VoIP services, high-prioritynon-GBR services, and low-priority non-GBRservices are assigned logical channel groups 0, 1, 2, 3,respectively. In addition, services with a QCI of 2 to 4are also assigned logical channel group 1. If thisparameter is set to LCG_PROFILE_2, VoIP servicesmust be carried by bearers with a QCI of 1 and bearerswith a QCI of 2 to 4 are not used. The parameter valueLCG_PROFILE_2 does not apply to LTE TDD.GUI Value Range: LCG_PROFILE_0,LCG_PROFILE_1, LCG_PROFILE_2Unit: NoneActual Value Range: LCG_PROFILE_0,LCG_PROFILE_1, LCG_PROFILE_2Default Value: LCG_PROFILE_0

Drx DrxAlgSwitch

MODDRXLSTDRX

LBFD-002017 /TDLBFD-002017

DRX Meaning: Indicates the DRX switch. The setting ofthis parameter has no effect on dynamic DRX. DRXapplies to a CA UE only when this parameter is set toON(On) on both eNodeBs to which the PCell andSCell of the CA UE belong.GUI Value Range: OFF(Off), ON(On)Unit: NoneActual Value Range: OFF, ONDefault Value: OFF(Off)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellStandardQci

QciPriorityForHo

MODCELLSTANDARDQCILSTCELLSTANDARDQCI

LBFD-00201801LBFD-00201802LBFD-00201804LBFD-00201805LOFD-001072LOFD-001073

Coverage BasedIntra-frequencyHandoverCoverage BasedInter-frequencyHandoverDistanceBasedInter-frequencyHandoverServiceBasedInter-frequencyHandoverDistancebasedInter-RAThandover toUTRANDistancebasedInter-RAThandover toGERAN

Meaning: Indicates the QCI priority used by eachQCI-based handover algorithm. A larger value of thisparameter indicates a lower priority. This parameterapplies to handover parameter selection based on QCIpriorities, target frequency selection in service-basedinter-frequency handovers, and inter-RAT handoverpolicy selection. For a service that involves all thepreceding selection, the setting of this parameterdetermines the handover parameter, target frequency,and handover policy corresponding to a QCI.GUI Value Range: 1~9Unit: NoneActual Value Range: 1~9Default Value: 9

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

IntraFreqHoGroup

IntraFreqHoA3Hyst

ADDINTRAFREQHOGROUPMODINTRAFREQHOGROUPLSTINTRAFREQHOGROUP

LBFD-00201801/TDLBFD-00201801

Coverage BasedIntra-frequencyHandover

Meaning: Indicates the hysteresis for intra-frequencyhandover event A3. This parameter decreases frequentevent triggering due to radio signal fluctuations andreduces the probability of handover decision errorsand ping-pong handovers. A larger value of thisparameter results in a lower probability. Thehysteresis for event inter-frequency handover eventA3 is the same as the value of this parameter. Fordetails, see 3GPP TS 36.331.GUI Value Range: 0~30Unit: 0.5dBActual Value Range: 0~15Default Value: 2

IntraFreqHoGroup

IntraFreqHoA3Offset

LBFD-00201801/TDLBFD-00201801

Meaning: Indicates the offset for event A3. If theparameter is set to a large value, an intra-frequencyhandover is performed only when the signal quality ofthe neighboring cell is significantly better than that ofthe serving cell and other triggering conditions aremet. For details, see 3GPP TS 36.331.GUI Value Range: -30~30Unit: 0.5dBActual Value Range: -15~15Default Value: 2

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

IntraFreqHoGroup

IntraFreqHoA3TimeToTrig

LBFD-00201801/TDLBFD-00201801

Meaning:Indicates the time-to-trigger for intra-frequencyhandover event A3.

When the UE detects that the signal quality in theserving cell and that in at least one neighboring cellmeet the entering condition, it does not immediatelysend a measurement report to the eNodeB. Instead, theUE sends a report only when the signal quality meetsthe entering condition throughout the time-to-trigger.

This parameter helps decrease the number ofoccasionally triggered event reports, the averagenumber of handovers, and the number of incorrecthandovers, preventing unnecessary handovers. Thetime-to-trigger for inter-frequency handover event A3is 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, 5120msUnit: msActual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msDefault Value: 320ms

InterFreqHoGroup

InterFreqHoA1A2Hyst

ADDINTERFREQHOGROUPMODINTERFREQHOGROUPLSTINTERFREQHOGROUP

LBFD-00201802/TDLBFD-00201802

Meaning: Indicates the hysteresis of event A1/A2 fortriggering inter-frequency measurement. Thisparameter is used to prevent frequent triggering ofevent evaluation caused by radio signal fluctuation. Inthis way, the probability of ping-pong handovers orhandover decision errors is reduced. A larger value ofthis parameter results in a lower probability.

GUI Value Range: 0~30

Unit: 0.5dB

Actual Value Range: 0~15

Default Value: 2

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

InterFreqHoA1A2TimeToTrig

LBFD-00201802/TDLBFD-00201802

Meaning:Indicates the time-to-trigger of event A1/A2 fortriggering inter-frequency measurement.

When detecting that the signal quality in the servingcell meets the entering condition, the UE does notsend a measurement report to the eNodeBimmediately. Instead, the UE sends a report only whenthe signal quality continuously meets the enteringcondition during the time-to-trigger. This parameterhelps decrease the number of occasionally triggeredevent reports, the average number of handovers, andthe number of wrong handovers. In summary, it helpsprevent unnecessary handovers.GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msUnit: msActual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msDefault Value: 640ms

InterFreqHoGroup

InterFreqHoA1ThdRsrp

LBFD-00201802/TDLBFD-00201802

Meaning:Indicates the RSRP threshold for event A1 related toevent-A4/A5-triggered inter-frequency handover.

When the measured RSRP value exceeds thisthreshold, a measurement report will be sent.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -105

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

InterFreqHoA1ThdRsrq

LBFD-00201802/TDLBFD-00201802

Meaning:Indicates the RSRQ threshold for event A1 related toevent-A4/A5-triggered inter-frequency handover.

When the measured RSRQ value exceeds thisthreshold, a measurement report will be sent.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -20

InterFreqHoGroup

LBFD-00201802/TDLBFD-00201802

Meaning:Indicates the RSRP threshold for event A2 related toevent-A4/A5-triggered inter-frequency handover.

When the measured RSRP value is lower than thisthreshold, a measurement report will be sent.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -109

InterFreqHoGroup

LBFD-00201802/TDLBFD-00201802

Meaning:Indicates the RSRQ threshold for event A2 related toevent-A4/A5-triggered inter-frequency handover.

When the measured RSRQ value is lower than thisthreshold, a measurement report will be sent.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -24

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

InterFreqHoA4Hyst

LBFD-00201802/TDLBFD-00201802LBFD-00201804/TDLBFD-00201804LBFD-00201805/TDLBFD-00201805

Coverage BasedInter-frequencyHandoverDistanceBasedInter-frequencyHandoverServiceBasedInter-frequencyHandover

Meaning: Indicates the hysteresis for event A4. Thisparameter is used to prevent frequent triggering ofevent evaluation caused by radio signal fluctuation. Inthis way, the probability of ping-pong handovers orhandover decision errors is reduced. A larger value ofthis parameter results in a lower probability.GUI Value Range: 0~30Unit: 0.5dBActual Value Range: 0~15Default Value: 2

InterFreqHoGroup

LBFD-00201802/TDLBFD-00201802LBFD-00201804/TDLBFD-00201804

Coverage BasedInter-frequencyHandoverDistanceBasedInter-frequencyHandover

Meaning: Indicates the RSRP threshold for event A4related to coverage-based inter-frequency handover.When the measured RSRP value exceeds thisthreshold, event A4 is reported. The value of thisparameter is also used as the RSRP threshold for eventA4 related to distance-based, UL-power-based, orSPID-based inter-frequency handover back to theHPLMN.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -105

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

LBFD-00201802/TDLBFD-00201802LBFD-00201804/TDLBFD-00201804

Coverage BasedInter-frequencyHandoverDistanceBasedInter-frequencyHandover

Meaning: Indicates the RSRQ threshold for event A4related to coverage-based inter-frequency handover.When the measured RSRQ value exceeds thisthreshold, event A4 is reported. The value of thisparameter is also used as the RSRQ threshold forevent A4 related to distance-based, UL-power-based,or SPID-based inter-frequency handover back to theHPLMN.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -20

InterFreqHoGroup

InterFreqHoA4TimeToTrig

LBFD-00201802/TDLBFD-00201802LBFD-00201804/TDLBFD-00201804LBFD-00201805/TDLBFD-00201805

Coverage BasedInter-frequencyHandoverDistanceBasedInter-frequencyHandoverServiceBasedInter-frequencyHandover

Meaning:Indicates the time-to-trigger for event A4 for the inter-frequency handover. When detecting that the signalquality in at least one neighboring cell meets theentering condition, the UE does not send ameasurement report to the eNodeB immediately.Instead, the UE sends a report only when the signalquality continuously meets the entering conditionduring the time-to-trigger.

This parameter helps decrease the number ofoccasionally triggered event reports, the averagenumber of handovers, and the number of wronghandovers. In summary, it helps prevent unnecessaryhandovers.GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msUnit: msActual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msDefault Value: 640ms

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

InterFreqHoA3Offset

LBFD-00201802/TDLBFD-00201802

Meaning: Indicates the offset for event A3 associatedwith inter-frequency handover. This parameterdetermines the border between the serving cell and theneighboring cell. If the parameter is set to a largevalue, an inter-frequency handover is performed onlywhen the signal quality of the neighboring cell issignificantly better than that of the serving cell andother triggering conditions are met. For details, see3GPP TS 36.331.GUI Value Range: -30~30Unit: 0.5dBActual Value Range: -15~15Default Value: 2

InterFreqHoGroup

A3InterFreqHoA1ThdRsrp

LBFD-00201802/TDLBFD-00201802

Meaning: Indicates the RSRP threshold for event A1related to event-A3-triggered inter-frequencyhandover. When the measured RSRP value exceedsthis threshold, a measurement report will be sent.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -95

InterFreqHoGroup

A3InterFreqHoA2ThdRsrp

LBFD-00201802/TDLBFD-00201802

Meaning: Indicates the RSRP threshold for event A2related to event-A3-triggerd inter-frequency handover.When the measured RSRP value is lower than thisthreshold, a measurement report will be sent.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -99

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

InterFreqHoA5Thd1Rsrp

LBFD-00201802/TDLBFD-00201802

Meaning:Indicates the RSRP threshold 1 in the serving cell ofevent A5 for triggering inter-frequency handovers.

When the measured RSRP in the serving cell issmaller than the value of this parameter and the RSRPor RSRQ in the neighboring cell is higher than thevalue of InterFreqHoA4ThdRsrp orInterFreqHoA4ThdRsrq, the UE reports event A5.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -109

InterFreqHoGroup

InterFreqHoA5Thd1Rsrq

LBFD-00201802/TDLBFD-00201802

Meaning:Indicates the RSRQ threshold 1 in the serving cell ofevent A5 for triggering inter-frequency handovers.

When the measured RSRQ in the serving cell issmaller than the value of this parameter and the RSRPor RSRQ in the neighboring cell is higher than thevalue of InterFreqHoA4ThdRsrp orInterFreqHoA4ThdRsrq, the UE reports event A5.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -24

InterFreqHoGroup

InterFreqLoadBasedHoA4ThdRsrp

LBFD-00201805/TDLBFD-00201805

ServiceBasedInter-frequencyHandover

Meaning: Indicates the RSRP threshold for event A4related to load-based inter-frequency handover. Whenthe measured RSRP value exceeds this threshold,event A4 is reported. The value of this parameter isalso used as the RSRP threshold for event A4 relatedto frequency-priority-based handover, service-basedinter-frequency handover, inter-frequency handover oflow-speed UEs, or redirection of high-speed UEs.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -103

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

InterFreqLoadBasedHoA4ThdRsrq

LBFD-00201805/TDLBFD-00201805

ServiceBasedInter-frequencyHandover

Meaning: Indicates the RSRQ threshold for event A4related to load-based inter-frequency handover. Whenthe measured RSRQ value exceeds this threshold,event A4 is reported. The value of this parameter isalso used as the RSRQ threshold for event A4 relatedto frequency-priority-based, service-based inter-frequency handover, inter-frequency handover of low-speed UEs, or redirection of high-speed UEs.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -18

InterFreqHoGroup

FreqPriInterFreqHoA1ThdRsrp

None None Meaning: Indicates the RSRP threshold for frequency-priority-based inter-frequency measurement event A1.When the measured RSRP value exceeds thisthreshold, an event A1 report will be sent.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -85

InterFreqHoGroup

FreqPriInterFreqHoA1ThdRsrq

None None Meaning:Indicates the RSRQ threshold for frequency-priority-based inter-frequency measurement event A1.

When the measured RSRQ value exceeds thisthreshold, an event A1 report will be sent.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -16

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterFreqHoGroup

FreqPriInterFreqHoA2ThdRsrp

None None Meaning:Indicates the RSRP threshold for frequency-priority-based inter-frequency measurement event A2.

If the measured RSRP value is less than this threshold,an event A2 report will be sent.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -87

InterFreqHoGroup

FreqPriInterFreqHoA2ThdRsrq

None None Meaning:Indicates the RSRQ threshold for inter-frequencymeasurement event A2.

When the measured RSRQ value is below thisthreshold, a measurement report will be sent.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -20

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCommGroup

InterRatHoA1A2Hyst

ADDINTERRATHOCOMMGROUPMODINTERRATHOCOMMGROUPLSTINTERRATHOCOMMGROUP

LOFD-001019 /TDLOFD-001019LOFD-001020 /TDLOFD-001020LOFD-001021 /TDLOFD-001021TDLOFD-001022TDLOFD-001023

PS Inter-RATMobilitybetweenE-UTRANandUTRANPS Inter-RATMobilitybetweenE-UTRANandGERANPS Inter-RATMobilitybetweenE-UTRANandCDMA2000SRVCCtoUTRANSRVCCtoGERAN

Meaning: Indicates the hysteresis of event A1/A2 fortriggering inter-RAT measurement. This parameter isused to prevent frequent triggering of event evaluationcaused by radio signal fluctuation. In this way, theprobability of ping-pong handovers or handoverdecision errors is reduced. A larger value of thisparameter results in a lower probability.GUI Value Range: 0~30Unit: 0.5dBActual Value Range: 0~15Default Value: 2

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCommGroup

InterRatHoA1A2TimeToTrig

Meaning:Indicates the time-to-trigger of event A1/A2 fortriggering inter-RAT measurement.

When detecting that the signal quality in the servingcell meets the entering condition, the UE does notsend a measurement report to the eNodeBimmediately. Instead, the UE sends a report only whenthe signal quality continuously meets the enteringcondition during the time-to-trigger.

This parameter helps decrease the number ofoccasionally triggered event reports, the averagenumber of handovers, and the number of wronghandovers. In summary, it helps prevent unnecessaryhandovers.GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msUnit: msActual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msDefault Value: 640ms

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCommGroup

InterRatHoA1ThdRsrp

Meaning: Indicates the RSRP threshold for inter-RATmeasurement event A1. When the measured RSRPvalue of the serving cell exceeds this threshold, anevent A1 report will be sent.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -111

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCommGroup

InterRatHoA1ThdRsrq

Meaning:Indicates the RSRQ threshold for inter-RATmeasurement event A1.

When the measured RSRQ value of the serving cellexceeds this threshold, an event A1 report will be sent.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -20

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCommGroup

InterRatHoA2ThdRsrp

Meaning:Indicates the RSRP threshold for inter-RATmeasurement event A2.

When the measured RSRP value of the serving cell isbelow this threshold, an event A2 report will be sent.If you need to change the parameter value, you areadvised to set this parameter to a value greater thanthe value of the BlindHoA1A2ThdRsrp parameter inthe CellHoParaCfg MO.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -115

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCommGroup

InterRatHoA2ThdRsrq

Meaning:Indicates the RSRQ threshold for inter-RATmeasurement event A2.

When the measured RSRQ value of the serving cell isbelow this threshold, an event A2 report will be sent.If you need to change the parameter value, you areadvised to set this parameter to a value greater thanthe value of the BlindHoA1A2ThdRsrq parameter inthe CellHoParaCfg MO.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -24

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoUtranGroup

InterRatHoUtranB1ThdEcn0

ADDINTERRATHOUTRANGROUPMODINTERRATHOUTRANGROUPLSTINTERRATHOUTRANGROUP

LOFD-001019 /TDLOFD-001019TDLOFD-001022

PS Inter-RATMobilitybetweenE-UTRANandUTRANSRVCCtoUTRAN

Meaning: Indicates the Ec/N0 threshold for event B1related to coverage-based inter-RAT handover toUTRAN. This parameter specifies the requirement forEc/N0 of the target UTRAN cell. For a cell with largesignal fading variance, set this parameter to a largevalue to prevent unnecessary handovers. For a cellwith small signal fading variance, set this parameter toa small value to ensure timely handovers. A largevalue of this parameter results in a low probability ofhandover to the UTRAN cell, and a small value leadsto a high probability. When the measurement valueexceeds this threshold, a measurement report will besent.GUI Value Range: -48~0Unit: 0.5dBActual Value Range: -24~0Default Value: -24

InterRatHoUtranB1ThdRscp

Meaning:Indicates the RSCP threshold for event B1 related tocoverage-based inter-RAT handover to UTRAN.

This parameter specifies the requirement for RSCP ofthe target UTRAN cell.

When the measurement value exceeds this threshold, ameasurement report will be sent.GUI Value Range: -120~-25Unit: dBmActual Value Range: -120~-25Default Value: -103

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoUtranB1Hyst

Meaning: Indicates the hysteresis for event B1 relatedto inter-RAT handover to UTRAN. This parameter isused to prevent frequent triggering of event evaluationcaused by radio signal fluctuation. In this way, theprobability of ping-pong handovers or handoverdecision errors is reduced. A larger value of thisparameter results in a lower probability of ping-ponghandovers or handover decision errors.GUI Value Range: 0~30Unit: 0.5dBActual Value Range: 0~15Default Value: 0

InterRatHoUtranB1TimeToTrig

Meaning:Indicates the time-to-trigger for event B1 related tointer-RAT handover to UTRAN. When detecting thatthe signal quality in at least one neighboring cellmeets the entering condition, the UE does not send ameasurement report to the eNodeB immediately.Instead, the UE sends a report only when the signalquality continuously meets the entering conditionduring the time-to-trigger.

This parameter helps decrease the number ofoccasionally triggered event reports, the averagenumber of handovers and the number of wronghandovers, preventing unnecessary handovers.GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msUnit: msActual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msDefault Value: 320ms

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LdSvBasedHoUtranB1ThdEcn0

LOFD-001043TDLOFD-001022

Servicebasedinter-RAThandover toUTRANSRVCCtoUTRAN

Meaning:Indicates the Ec/N0 threshold for event B1 related toload- or service-based inter-RAT handover toUTRAN.

This parameter specifies the requirement for Ec/N0 ofthe target UTRAN cell. When the measurement valueexceeds this threshold, a measurement report may besent. For a cell with large signal fading variance, setthis parameter to a large value to prevent unnecessaryhandovers. For a cell with small signal fadingvariance, set this parameter to a small value to ensuretimely handovers.GUI Value Range: -48~0Unit: 0.5dBActual Value Range: -24~0Default Value: -18

LdSvBasedHoUtranB1ThdRscp

LOFD-001043TDLOFD-001022

Servicebasedinter-RAThandover toUTRANSRVCCtoUTRAN

Meaning:

Indicates the RSCP threshold for event B1 related toload- or service-based inter-RAT handover toUTRAN.

This parameter specifies the requirement for RSCP ofthe target UTRAN cell.

When the measurement value exceeds this threshold, ameasurement report will be sent.

GUI Value Range: -120~-25

Unit: dBm

Actual Value Range: -120~-25

Default Value: -101

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoGeranGroup

InterRatHoGeranB1Hyst

ADDINTERRATHOGERANGROUPMODINTERRATHOGERANGROUPLSTINTERRATHOGERANGROUP

PS Inter-RATMobilitybetweenE-UTRANandGERANSRVCCtoGERAN

Meaning: Indicates the hysteresis for event B1 relatedto inter-RAT handover to GERAN. This parameter isused to prevent frequent triggering of event evaluationcaused by radio signal fluctuation. In this way, theprobability of ping-pong handovers or handoverdecision errors is reduced. A larger value of thisparameter results in a lower probability of ping-ponghandovers or handover decision errors.GUI Value Range: 0~30Unit: 0.5dBActual Value Range: 0~15Default Value: 2

InterRatHoGeranB1Thd

LOFD-001020 /TDLOFD-001020

PS Inter-RATMobilitybetweenE-UTRANandGERAN

Meaning:Indicates the RSSI threshold for event B1 related tocoverage-based inter-RAT handover to GERAN.

A UE sends a measurement report related to event B1to the eNodeB when the RSSI in at least one GERANcell exceeds this threshold and other triggeringconditions are met. For details, see 3GPP TS 36.331.GUI Value Range: -110~-48Unit: dBmActual Value Range: -110~-48Default Value: -100

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoGeranB1TimeToTrig

PS Inter-RATMobilitybetweenE-UTRANandGERANSRVCCtoGERAN

Meaning:Indicates the time-to-trigger for event B1 related tointer-RAT handover to GERAN. When detecting thatthe signal quality in at least one neighboring cellmeets the entering condition, the UE does not send ameasurement report to the eNodeB immediately.Instead, the UE sends a report only when the signalquality continuously meets the entering conditionduring the time-to-trigger.

LdSvBasedHoGeranB1Thd

LOFD-001046 /TDLOFD-001046

Servicebasedinter-RAThandover toGERAN

Meaning:Indicates the RSSI threshold for event B1 related toload- or service-based inter-RAT handover toGERAN.

When the measured RSSI value exceeds thisthreshold, a measurement report will be sent.GUI Value Range: -110~-48Unit: dBmActual Value Range: -110~-48Default Value: -98

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCdma1xRttGroup

InterRatHoCdmaB1Hyst

ADDINTERRATHOCDMA1XRTTGROUPMODINTERRATHOCDMA1XRTTGROUPLSTINTERRATHOCDMA1XRTTGROUP

LOFD-001090 /TDLOFD-001090

Enhanced CSFallbacktoCDMA20001xRTT

Meaning: Indicates the hysteresis for event B1 forinter-RAT handover to CDMA2000 1xRTT. Thisparameter is used to prevent frequent triggering ofevent evaluation caused by radio signal fluctuation. Inthis way, the probability of ping-pong handovers orhandover decision errors is reduced. A larger value ofthis parameter results in a lower probability of ping-pong handovers or handover decision errors.GUI Value Range: 0~30Unit: 0.5dBActual Value Range: 0~15Default Value: 2

InterRatHoCdmaB1ThdPs

None None Meaning: Indicates the pilot strength threshold forevent B1 related to coverage-based inter-RAThandover to CDMA2000 1xRTT. When themeasurement value exceeds this threshold, ameasurement report will be sent.GUI Value Range: -63~0Unit: 0.5dBActual Value Range: -31.5~0Default Value: -28

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCdmaB1TimeToTrig

LOFD-001090 /TDLOFD-001090

Enhanced CSFallbacktoCDMA20001xRTT

Meaning:Indicates the time-to-trigger for event B1 related tointer-RAT handover to CDMA2000 1xRTT.

When detecting that the signal quality in at least oneneighboring cell meets the entering condition, the UEdoes not send a measurement report to the eNodeBimmediately. Instead, the UE sends a report only whenthe signal quality continuously meets the enteringcondition during the time-to-trigger.

This parameter helps decrease the number ofoccasionally triggered event reports, the averagenumber of handovers and the number of wronghandovers, preventing unnecessary handovers.GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msUnit: NoneActual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,1024ms, 1280ms, 2560ms, 5120msDefault Value: 640ms

LdSvBasedHoCdmaB1ThdPs

LOFD-001021 /TDLOFD-001021

PS Inter-RATMobilitybetweenE-UTRANandCDMA2000

Meaning:Indicates the pilot strength threshold for event B1related to load- or service-based inter-RAT handoverto CDMA2000 1xRTT.

When the measurement value exceeds this threshold, ameasurement report will be sent.GUI Value Range: -63~0Unit: 0.5dBActual Value Range: -31.5~0Default Value: -24

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCdmaHrpdGroup

InterRatHoCdmaB1Hyst

ADDINTERRATHOCDMAHRPDGROUPMODINTERRATHOCDMAHRPDGROUPLSTINTERRATHOCDMAHRPDGROUP

LOFD-001021 /TDLOFD-001021

Meaning: Indicates the hysteresis for event B1 relatedto inter-RAT handover to CDMA2000 HRPD. Thisparameter is used to prevent frequent triggering ofevent evaluation caused by radio signal fluctuation. Inthis way, the probability of ping-pong handovers orhandover decision errors is reduced. A larger value ofthis parameter results in a lower probability of ping-pong handovers or handover decision errors.GUI Value Range: 0~30Unit: 0.5dBActual Value Range: 0~15Default Value: 2

InterRatHoCdmaB1ThdPs

LOFD-001021 /TDLOFD-001021

Meaning:Indicates the pilot strength threshold for event B1related to load- or service-based inter-RAT handoverto CDMA2000 HRPD.

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

InterRatHoCdmaB1TimeToTrig

LOFD-001021 /TDLOFD-001021

Meaning:Indicates the time-to-trigger for event B1 related tointer-RAT handover to CDMA2000 HRPD.

When detecting that the signal quality in at least oneneighboring cell meets the entering condition, the UEdoes not send a measurement report to the eNodeBimmediately. Instead, the UE sends a report only whenthe signal quality continuously meets the enteringcondition during the time-to-trigger.

LdSvBasedHoCdmaB1ThdPs

LOFD-001035 /TDLOFD-001035

CSFallbacktoCDMA20001xRTT

Meaning:Indicates the pilot strength threshold for event B1related to load- or service-based inter-RAT handoverto CDMA2000 HRPD.

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Cdma2000HrpdB2Thd1Rsrp

LOFD-001021 /TDLOFD-001021

Meaning: Indicates the B2 RSRP threshold 1 usedduring optimized handovers from E-UTRAN toCDMA2000 eHRPD.GUI Value Range: -140~-43Unit: dBmActual Value Range: -140~-43Default Value: -113

Cdma2000HrpdB2Thd1Rsrq

LOFD-001021 /TDLOFD-001021

Meaning: Indicates the B2 RSRQ threshold 1 usedduring optimized handovers from E-UTRAN toCDMA2000 eHRPD.GUI Value Range: -40~-6Unit: 0.5dBActual Value Range: -20~-3Default Value: -14

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

ENodeBAlgoSwitch

CaAlgoSwitch

LAOFD-00100101

LAOFD-00100102

LAOFD-00100201 /TDLAOFD-001002

LAOFD-00100202 /TDLAOFD-00100102

LAOFD-070201/TDLAOFD-070201

LAOFD-070202

TDLAOFD-00100111

LAOFD-080202

LAOFD-080201

LBFD-00201805/TDLBFD-00201805

LOFD-00105401/TDLOFD-00105401

Intra-BandCarrierAggregation forDownlink 2CCin20MHzInter-BandCarrierAggregation forDownlink 2CCin20MHzCarrierAggregation forDownlink 2CCin40MHzSupportof UECategory 6FlexibleCAfromMultipleCarriersInter-eNodeBCAbased onCoordinatedBBUIntra-bandCarrierAggregation forDownlin

Meaning:Indicates whether to enable carrier aggregation (CA).The switches are described as follows:

PdcchOverlapSrchSpcSwitch: Indicates whether CAUEs regard the overlapping PDCCH candidates of thecommon search space and UE-specific search space,which are transmitted by the primary serving cell(PCell), as PDCCH candidates of the common or UE-specific search space. If this switch is On and if a CAUE supports cross-carrier scheduling and is assigned acarrier indicator field (CIF), the CA UE determinesthat the overlapping PDCCH candidates belong to thecommon search space; otherwise, the CA UEdetermines that the overlapping PDCCH candidatesbelong to the UE-specific search space. If this switchis Off, the CA UE always determines that theoverlapping PDCCH candidates belong to thecommon search space.

CaCapbFiltSwitch: Indicates how the eNodeBperforms CA after a CA UE reports the combinationof frequency bands. If the UECapabilityInformationmessage reported by a UE does not contain the IEsupportedBandwidthCombinationSet, the eNodeBperforms CA as follows: If this option is Off, theeNodeB configures a secondary component carrier(SCC) for the UE using the default value of the IEsupportedBandwidthCombinationSet defined in 3GPPspecifications. If this option is On, the eNodeB doesnot configure an SCC for the UE.

PccAnchorSwitch: Indicates whether to enable theanchor function of the primary component carrier(PCC). This switch is not subject to the setting ofFreqCfgSwitch of the CaAlgoSwitch parameter. Theanchor function of the PCC is enabled only when thisswitch is On.

SccBlindCfgSwitch: Indicates whether a secondaryserving cell (SCell) can be blindly configured. If thisswitch is On, the eNodeB configures a candidateSCell as an SCell for a CA UE without A4measurements. If this switch is Off, the eNodeBdelivers A4 measurement configurations formeasuring the frequency of a candidate SCell beforeconfiguring the candidate SCell as an SCell for theCA UE.

FreqCfgSwitch: Indicates whether to configure CAbased on frequencies or CA groups. If this switch is

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

k 2CCin30MHzCarrierAggregation forUplink2CCInter-eNodeBCAbased onrelaxedbackhaulServiceBasedInter-frequencyHandoverCamp &Handover Basedon SPID

On, CA can be configured based on frequencies. Ifthis switch is Off, CA can be configured based on CAgroups.

SccA2RmvSwitch: Indicates whether to deliver A2measurement configurations for measuring asecondary component carrier (SCC) after the SCC isconfigured. This option is not subject to the setting ofthe FreqCfgSwitch option of the CaAlgoSwitchparameter. If FreqCfgSwitch is Off andSccBlindCfgSwitch is On, the setting ofSccA2RmvSwitch does not take effect. The eNodeBdelivers A2 measurement configurations formeasuring an SCC after the SCC is configured onlywhen SccA2RmvSwitch is On.

CaTrafficTriggerSwitch: Indicates whether to add andremove an SCC based on the traffic volume of a CAUE after the UE accesses the network. This switch isnot subject to the settings of FreqCfgSwitch. If theCarrierMgtSwitch parameter is set to Off andCaTrafficTriggerSwitch is On, an added SCC cannotbe removed based on the traffic volume of a CA UE.

HoWithSccCfgSwitch: Indicates whether an SCC canbe configured for a CA UE during a handover. It isrecommended that the SccA2RmvSwitch option of theCaAlgoSwitch parameter be selected when theHoWithSccCfgSwitch option of the same parameter isselected. If the SccA2RmvSwitch option is deselected,UEs cannot report the signals of neighboring cells thatoperate on the frequencies of their SCell, affectingSCell configuration in handovers. This switch is notsubject to the setting of FreqCfgSwitch of theCaAlgoSwitch parameter. If this switch is On, thesource cell sends SCC information to the target cellduring the handover and the SCC is configured for theCA UE. If this switch is Off, the source cell does notsend SCC information to the target cell during thehandover.

SccModA6Switch: Indicates whether the eNodeBdelivers event A6 measurement configurations to aCA UE after configuring an SCC for the UE. TheeNodeB delivers event A6 measurementconfigurations to a CA UE after configuring an SCCfor the UE only when the switch is On.

GbrAmbrJudgeSwitch: Indicates whether to check theGBR or AMBR when an SCell is to be activated fordownlink CA. If this switch is On, the bit rate of the

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

bearer or aggregate bit rate of the CA UE is checkedwhen an SCell is to be activated. An SCell can beactivated if the bit rate has not reached the GBR or theaggregate bit rate of the UE has not reached theAMBR. If this switch is Off, neither the bit rate of thebearer nor the aggregate bit rate of the CA UE ischecked when an SCell is to be activated.

MtaAlgSwitch: Indicates whether multiple timingadvances (MTAs) are supported in uplink CAscenarios. This parameter applies only to LTE FDD. Ifthis switch is On, MTAs are supported. If the reportedUE capabilities indicate that the UE supports MTAs inthe uplink, uplink timing is performed on the UEbased on multiple timing advance groups (TAGs) inuplink CA scenarios. If the UE does not supportMTAs in the uplink, uplink timing is performed on theUE based on a single TAG in uplink CA scenarios. Ifthis switch is Off, MTAs are not supported in uplinkCA scenarios, and uplink timing is performed on UEsbased on a single TAG. You are advised to set thisswitch to On in inter-eNodeB CA scenarios andscenarios where RRUs are installed remotely.

RelaxedBackhaulCaSwitch: Indicates whether toenable inter-eNodeB downlink CA based on relaxedbackhaul. Inter-eNodeB CA based on relaxedbackhaul is enabled only when this switch is On.

AdpCaSwitch: Indicates whether to allow adaptivefrequency-based CA configuration. If this switch isOn, in frequency-based configuration mode, theeNodeB can configure SCells in a blind manner basedon preconfigured CA group information. If this switchis Off, blind SCell configuration is not allowed infrequency-based CA configuration mode.

CaHoControlSwitch: Indicates whether CA UEs canbe handed over to non-macro cells during unnecessaryintra-RAT handovers. If this switch is On, CA UEscannot be handed over to non-macro cells duringunnecessary intra-RAT handovers. If this switch isOff, CA UEs can be handed over to non-macro cellsduring unnecessary intra-RAT handovers.

DistributeCloudbbCaSwitch: Indicates whether toenable CA based on distributed Cloud BB. CA basedon distributed Cloud BB applies to cells served by theeNodeB only when this switch is On.

SccSmartCfgSwitch: Indicates whether to enablesmart SCC selection. The eNodeB considers the load

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

status indicators of candidate SCells when configuringthe SCell only when this switch is On.

IdleModePccAnchorSwitch: Indicates whether toenable the anchor function of the primary componentcarrier (PCC) for UEs in idle mode. If this option isselected, this function is enabled. If this option isdeselected, this function is disabled.

FreqPriBasedHoCaFiltSwitch: Indicates whether theeNodeB filters out CA UEs when deliveringmeasurement configuration for frequency-priority-based handovers. CA UEs are filtered out only if thisoption is selected.

CaSccSuspendSwitch: Indicates whether the eNodeBstops scheduling carrier aggregation (CA) UEs in theirsecondary serving cells (SCells) when the channelquality for the CA UEs is poor. If this option isselected, the eNodeB stops scheduling CA UEs whenthe channel quality for the CA UEs is worse than thatindicated by the SccDeactCqiThd parameter value insingle-codeword transmission. The eNodeB resumesscheduling CA UEs in their SCells when the channelquality for the CA UEs is better than that indicated bythe 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

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Actual Value Range: PdcchOverlapSrchSpcSwitch,CaCapbFiltSwitch, PccAnchorSwitch,SccBlindCfgSwitch, FreqCfgSwitch,SccA2RmvSwitch, CaTrafficTriggerSwitch,HoWithSccCfgSwitch, SccModA6Switch,GbrAmbrJudgeSwitch, MtaAlgSwitch,RelaxedBackhaulCaSwitch, AdpCaSwitch,CaHoControlSwitch, DistributeCloudbbCaSwitch,SccSmartCfgSwitch, IdleModePccAnchorSwitch,FreqPriBasedHoCaFiltSwitch, CaSccSuspendSwitchDefault 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

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

DrxParaGroup

LongDrxCycle

ADDDRXPARAGROUPMODDRXPARAGROUPLSTDRXPARAGROUP

LBFD-002017 /TDLBFD-002017

DRX Meaning: Indicates the length of the long DRX cycle.Because of the impact of the SRS bandwidth and TAperiod specified by the TimeAlignmentTimerparameter, the actual value of this parameter assignedto a UE may be less than the configured value. Inaddition, the configured value will be rounded downto an integral multiple of 10. Therefore, you areadvised to configure this parameter to a value that isan integral multiple of 10. If users hope that the valueactually assigned to a UE is equal to or greater than 80ms, set the TimeAlignmentTimer parameter to a valueequal to or greater than 10240 ms. If theTimingAdvCmdOptSwitch parameter is set to ON, itis recommended that the LongDrxCycle parameter beset to a value smaller than or equal to 320 ms.Otherwise, the uplink time alignment performance ofUEs is affected. If the TimingAdvCmdOptSwitchparameter is set to ON, it is recommended that theTimeAlignmentTimer parameter be set to sf10240. Asmaller value of the TimeAlignmentTimer parameter,such as sf5120, increases the probability that UEs inDRX mode become uplink asynchronized. The lengthof the long DRX cycle must be smaller than the lengthof the PDCP packet discarding timer for thecorresponding QCI. Otherwise, packet loss occursduring a ping operation or low-traffic service.GUI Value Range: SF10(10 subframes), SF20(20subframes), SF32(32 subframes), SF40(40subframes), SF64(64 subframes), SF80(80subframes), SF128(128 subframes), SF160(160subframes), SF256(256 subframes), SF320(320subframes), SF512(512 subframes), SF640(640subframes), SF1024(1024 subframes), SF1280(1280subframes), SF2048(2048 subframes), SF2560(2560subframes)Unit: subframeActual Value Range: SF10, SF20, SF32, SF40, SF64,SF80, SF128, SF160, SF256, SF320, SF512, SF640,SF1024, SF1280, SF2048, SF2560Default Value: SF40(40 subframes)

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RrcConnStateTimer

UeInactiveTimer

MODRRCCONNSTATETIMERLSTRRCCONNSTATETIMER

LBFD-002007 /TDLBFD-002007

Meaning: Indicates the length of the UE inactivitytimer for UEs that are running non-QCI1 services. Ifthe eNodeB detects that a UE has neither received norsent data for a duration exceeding the value of thisparameter, the eNodeB releases the RRC connectionfor the UE. If this parameter is set to 0, the UEinactivity timer is not used. If the parameter setting ischanged, the change applies to UEs that newly accessthe network.GUI Value Range: 0~3600Unit: sActual Value Range: 0~3600Default Value: 20

ENodeBAlgoSwitch

VQMAlgoSwitch

None None Meaning: Indicates the switch used to enable ordisable the voice quality monitoring algorithm.GUI Value Range:VQM_ALGO_SWITCH_OFF(Disable),VQM_ALGO_SWITCH_ON(Enable)Unit: NoneActual Value Range: VQM_ALGO_SWITCH_OFF,VQM_ALGO_SWITCH_ONDefault Value:VQM_ALGO_SWITCH_OFF(Disable)

VQMAlgo

ULDelayJitter

None None Meaning: Indicates the maximum UL voice packetdelay variation allowed on the Uu interface. If theactual delay variation of a UL voice packet exceedsthis limit, this packet is regarded as lost during theevaluation of voice quality indicator (VQI). The delayvariation is measured at the eNodeB PDCP layer.GUI Value Range: 1~255Unit: msActual Value Range: 1~255Default Value: 100

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RlcPdcpParaGroup

DiscardTimer

ADDRLCPDCPPARAGROUPMODRLCPDCPPARAGROUPLSTRLCPDCPPARAGROUP

LBFD-002008 /TDLBFD-002008

Meaning: Indicates the length of the PDCP discardtimer.

GUI Value Range: DiscardTimer_50(50),DiscardTimer_100(100), DiscardTimer_150(150),DiscardTimer_300(300), DiscardTimer_500(500),DiscardTimer_750(750), DiscardTimer_1500(1500),DiscardTimer_Infinity(infinity)

Unit: ms

Actual Value Range: DiscardTimer_50,DiscardTimer_100, DiscardTimer_150,DiscardTimer_300, DiscardTimer_500,DiscardTimer_750, DiscardTimer_1500,DiscardTimer_Infinity

Default Value: DiscardTimer_Infinity(infinity)

11 Counters

Table 11-1 Counters

Counter ID Counter Name CounterDescription

Feature ID Feature Name

1526726668 L.E-RAB.AttEst.QCI.1

Number of E-RABsetup attemptsinitiated by UEs forservices with theQCI of 1 in a cell

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002008TDLBFD-002008

Radio BearerManagementRadio BearerManagement

1526726669 L.E-RAB.SuccEst.QCI.1

Number ofsuccessful E-RABsetups initiated byUEs for serviceswith the QCI of 1 ina cell

1526726676 L.E-RAB.AttEst.QCI.5

Number of E-RABsetup attemptsinitiated by UEs forservices with theQCI of 5 in a cell

1526726677 L.E-RAB.SuccEst.QCI.5

Number ofsuccessful E-RABsetups initiated byUEs for serviceswith the QCI of 5 ina cell

eRANVoLTE Feature Parameter Description 11 Counters

1526726686 L.E-RAB.AbnormRel.QCI.1

Number ofabnormal releasesof activated E-RABs for serviceswith the QCI of 1 ina cell

1526726687 L.E-RAB.NormRel.QCI.1

Number of normalE-RAB releases forservices with theQCI of 1 in a cell

1526726694 L.E-RAB.AbnormRel.QCI.5

Number ofabnormal releasesof activated E-RABs for serviceswith the QCI of 5 ina cell

1526726695 L.E-RAB.NormRel.QCI.5

Number of normalE-RAB releases forservices with theQCI of 5 in a cell

1526726776 L.Thrp.bits.UL.QCI.1

Uplink trafficvolume for PDCPPDUs of serviceswith the QCI of 1 ina cell

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002008TDLBFD-002008LBFD-002025TDLBFD-002025

Radio BearerManagementRadio BearerManagementBasic SchedulingBasic Scheduling

1526726777 L.Thrp.Time.UL.QCI.1

Receive duration ofuplink PDCP PDUsfor services with theQCI of 1 in a cell

1526726803 L.Thrp.bits.DL.QCI.1

Downlink trafficvolume for PDCPSDUs of serviceswith the QCI of 1 ina cell

1526726804 L.Thrp.Time.DL.QCI.1

Transmit durationof downlink PDCPSDUs for serviceswith the QCI of 1 ina cell

1526726833 L.PDCP.Tx.Disc.Trf.SDU.QCI.1

Number ofdownlink PDCPSDUs discarded forservices carried onDRBs with a QCIof 1 in a cell

1526727412 L.ChMeas.PUSCH.MCS.0

Number of timesMCS index 0 isscheduled on thePUSCH

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002025LBFD-001005TDLBFD-002025TDLBFD-001005

Basic SchedulingModulation: DL/ULQPSK, DL/UL16QAM, DL64QAMBasic SchedulingModulation: DL/ULQPSK, DL/UL16QAM, DL64QAM

1526727443 L.ChMeas.PUSCH.MCS.31

Number of timesMCS index 31 isscheduled on thePUSCH

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-002025

TDLBFD-002025

LBFD-001005

TDLBFD-001005

LOFD-001006

TDLOFD-001006

Basic SchedulingBasic SchedulingModulation: DL/ULQPSK, DL/UL16QAM, DL64QAMModulation: DL/ULQPSK, DL/UL16QAM, DL64QAMUL 64QAMUL 64QAM

1526727849 L.Thrp.bits.UL.PLMN.QCI.1

Total traffic volumeof uplink PDCPPDUs of QCI-1services

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002008LOFD-001036LOFD-001037LBFD-002025TDLBFD-002008TDLOFD-001036TDLOFD-001037TDLBFD-002025LOFD-070206

Radio BearerManagementRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierBasic SchedulingRadio BearerManagementRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierBasic SchedulingHybrid RANSharing

1526727850 L.Thrp.Time.UL.PLMN.QCI.1

Duration forreceiving uplinkPDCP SDUs ofQCI-1 services

Number of E-RABsetup attemptsinitiated by UEs forservices with theQCI of 1for aspecific operator ina cell

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002008TDLBFD-002008LOFD-001036LOFD-001037TDLOFD-001036TDLOFD-001037LOFD-070206

Radio BearerManagementRadio BearerManagementRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierHybrid RANSharing

Number ofsuccessful E-RABsetups initiated byUEs for serviceswith the QCI of 1for a specificoperator in a cell

Number of E-RABsetup attemptsinitiated by UEs forservices with theQCI of 5 for aspecific operator ina cell

Number ofsuccessful E-RABsetups initiated byUEs for serviceswith the QCI of 5for a specificoperator in a cell

1526727871 L.E-RAB.AbnormRel.PLMN.QCI.1

Number ofabnormal releasesof activated E-RABs for serviceswith the QCI of 1for a specificoperator in a cell

1526727872 L.E-RAB.NormRel.PLMN.QCI.1

Number of normalE-RAB releases forservices with theQCI of 1 for aspecific operator ina cell

1526727879 L.E-RAB.AbnormRel.PLMN.QCI.5

Number ofabnormal releasesof activated E-RABs for serviceswith the QCI of 5for a specificoperator in a cell

1526727880 L.E-RAB.NormRel.PLMN.QCI.5

Number of normalE-RAB releases forservices with theQCI of 5 for aspecific operator ina cell

1526727889 L.PDCP.Tx.TotRev.Trf.SDU.QCI.1

Number ofdownlink PDCPSDUs transmittedfor services carriedon DRBs with aQCI of 1 in a cell

1526727934 L.Traffic.DL.PktUuLoss.Loss.QCI.1

Number ofdownlink PDCPSDUs discarded forservices carried onDRBs with a QCIof 1 in a cell overthe Uu interface

1526727935 L.Traffic.DL.PktUuLoss.Tot.QCI.1

Number ofdownlink PDCPSDUs transmittedfor services carriedon DRBs with aQCI of 1 in a cellover the Uuinterface

Number of uplinkPDCP SDUsdiscarded forservices carried onDRBs with a QCIof 1 in a cell

Number ofexpected uplinkPDCP SDUs forservices carried onDRBs with a QCIof 1 in a cell

1526728050 L.Thrp.bits.DL.PLMN.QCI.1

Total traffic volumeof downlink PDCPPDUs of QCI-1services

1526728051 L.Thrp.Time.DL.PLMN.QCI.1

Duration fortransmittingdownlink PDCPSDUs of QCI-1services

1526728304 L.ChMeas.CCE.ULUsed

Number of PDCCHCCEs used foruplink DCI in ameasurement period

Physical ChannelManagementPhysical ChannelManagement

1526728305 L.ChMeas.CCE.DLUsed

Number of PDCCHCCEs used fordownlink DCI in ameasurement period

Number of timesuplink voice qualityis Excellent

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-004008

PerformanceManagement

1526728412 L.Voice.VQI.UL.Good.Times

Number of timesuplink voice qualityis Good

1526728413 L.Voice.VQI.UL.Accept.Times

Number of timesuplink voice qualityis Accept

1526728414 L.Voice.VQI.UL.Poor.Times

Number of timesuplink voice qualityis Poor

1526728415 L.Voice.VQI.UL.Bad.Times

Number of timesuplink voice qualityis Bad

1526728416 L.Voice.VQI.DL.Excellent.Times

Number of timesdownlink voicequality is Excellent

1526728417 L.Voice.VQI.DL.Good.Times

Number of timesdownlink voicequality is Good

1526728418 L.Voice.VQI.DL.Accept.Times

Number of timesdownlink voicequality is Accept

1526728419 L.Voice.VQI.DL.Poor.Times

Number of timesdownlink voicequality is Poor

1526728420 L.Voice.VQI.DL.Bad.Times

Number of timesdownlink voicequality is Bad

1526728446 L.Traffic.ActiveUser.UL.QCI.1

Number ofactivated UEs withthe QCI of 1 in theuplink buffer

RRC ConnectionManagementRRC ConnectionManagement

1526728456 L.Traffic.ActiveUser.DL.QCI.1

Number ofactivated UEs withthe QCI of 1 in thedownlink buffer

1526728494 L.Sps.UL.SchNum Number of uplinksemi-persistentscheduling times ina cell

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LOFD-001016TDLOFD-001016

VoIP Semi-persistentSchedulingVoIP Semi-persistentScheduling

1526728495 L.Sps.DL.SchNum Number ofdownlink semi-persistentscheduling times ina cell

1526728496 L.Traffic.User.TtiBundling.Avg

Average number ofUEs on which TTIbundling takeseffect in a cell

TTI BundlingTTI Bundling

1526728562 L.Sps.UL.ErrNum Number of faileduplink semi-persistentschedulingtransmissions in acell

1526728563 L.Sps.DL.ErrNum Number of faileddownlink semi-persistentschedulingtransmission in acell

1526728911 L.Signal.Num.TtiBundling.Enter

Number ofmessages sent forinstructing UEs toenter TTI bundlingmode

1526728912 L.Signal.Num.TtiBundling.Exit

Number ofmessages sent forinstructing UEs toexit TTI bundlingmode

1526729526 L.HHO.IntraeNB.IntraFreq.PrepAttOut.VoIP

Number of intra-eNodeB intra-frequency outgoinghandover attemptsfor UEs performingvoice services in acell

Coverage BasedIntra-frequencyHandoverCoverage BasedIntra-frequencyHandover

1526729527 L.HHO.IntraeNB.InterFreq.PrepAttOut.VoIP

Number of intra-eNodeB inter-frequency outgoinghandover attemptsfor UEs performingvoice services in acell

Coverage BasedInter-frequencyHandoverCoverage BasedInter-frequencyHandover

1526729528 L.HHO.IntraeNB.InterFddTdd.PrepAttOut.VoIP

Number of intra-eNodeB inter-duplex-modeoutgoing handoverattempts for UEsperforming voiceservices in a cell

1526729529 L.HHO.IntraeNB.IntraFreq.ExecAttOut.VoIP

Number of intra-eNodeB intra-frequency outgoinghandoverexecutions for UEsperforming voiceservices in a cell

1526729530 L.HHO.IntraeNB.InterFreq.ExecAttOut.VoIP

Number of intra-eNodeB inter-frequency outgoinghandoverexecutions for UEsperforming voiceservices in a cell

1526729531 L.HHO.IntraeNB.InterFddTdd.ExecAttOut.VoIP

Number of intra-eNodeB inter-duplex-modeoutgoing handoverexecutions for UEsperforming voiceservices in a cell

1526729532 L.HHO.IntraeNB.IntraFreq.ExecSuccOut.VoIP

Number ofsuccessful intra-eNodeB intra-frequency outgoinghandovers for UEsperforming voiceservices in a cell

1526729533 L.HHO.IntraeNB.InterFreq.ExecSuccOut.VoIP

Number ofsuccessful intra-eNodeB inter-frequency outgoinghandovers for UEsperforming voiceservices in a cell

1526729534 L.HHO.IntraeNB.InterFddTdd.ExecSuccOut.VoIP

Number ofsuccessful intra-eNodeB inter-duplex-modeoutgoing handoversfor UEs performingvoice services in acell

1526729535 L.HHO.IntereNB.IntraFreq.PrepAttOut.VoIP

Number of inter-eNodeB intra-frequency outgoinghandover attemptsfor UEs performingvoice services in acell

1526729536 L.HHO.IntereNB.InterFreq.PrepAttOut.VoIP

Number of inter-eNodeB inter-frequency outgoinghandover attemptsfor UEs performingvoice services in acell

1526729537 L.HHO.IntereNB.InterFddTdd.PrepAttOut.VoIP

Number of inter-eNodeB inter-duplex-modeoutgoing handoverattempts for UEsperforming voiceservices in a cell

1526729538 L.HHO.IntereNB.IntraFreq.ExecAttOut.VoIP

Number of inter-eNodeB intra-frequency outgoinghandoverexecutions for UEsperforming voiceservices in a cell

1526729539 L.HHO.IntereNB.InterFreq.ExecAttOut.VoIP

Number of inter-eNodeB inter-frequency outgoinghandoverexecutions for UEsperforming voiceservices in a cell

1526729540 L.HHO.IntereNB.InterFddTdd.ExecAttOut.VoIP

Number of inter-eNodeB inter-duplex-modeoutgoing handoverexecutions for UEsperforming voiceservices in a cell

1526729541 L.HHO.IntereNB.IntraFreq.ExecSuccOut.VoIP

Number ofsuccessful inter-eNodeB intra-frequency outgoinghandovers for UEsperforming voiceservices in a cell

1526729542 L.HHO.IntereNB.InterFreq.ExecSuccOut.VoIP

Number ofsuccessful inter-eNodeB inter-frequency outgoinghandovers for UEsperforming voiceservices in a cell

1526729543 L.HHO.IntereNB.InterFddTdd.ExecSuccOut.VoIP

Number ofsuccessful inter-eNodeB inter-duplex-modeoutgoing handoversfor UEs performingvoice services in acell

1526730601 L.Traffic.ActiveUser.DL.QCI.1.Max

Maximum numberof activated UEswith the QCI of 1 inthe downlink buffer

1526730611 L.Traffic.ActiveUser.UL.QCI.1.Max

Maximum numberof activated UEswith the QCI of 1 inthe uplink buffer

1526730883 L.ChMeas.PRB.DL.DrbUsed.Avg.VoIP

Average number ofPRBs used byDRBs on thePDSCH fordownlink VoIPservices

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002025TDLBFD-002025LOFD-070205

Basic SchedulingBasic SchedulingAdaptive SFN/SDMA

1526730884 L.ChMeas.PRB.UL.DrbUsed.Avg.VoIP

Average number ofPRBs used byDRBs on thePUSCH for uplinkVoIP services

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002025TDLBFD-002025LOFD-070205

Basic SchedulingBasic SchedulingAdaptive SFN/SDMA

1526732687 L.Voice.VQI.AMRWB.UL.Excellent.Times

Number of timesuplink voice qualityof AMR-WBservices isExcellent

1526732688 L.Voice.VQI.AMRWB.UL.Good.Times

Number of timesuplink voice qualityof AMR-WBservices is Good

1526732689 L.Voice.VQI.AMRWB.UL.Accept.Times

Number of timesuplink voice qualityof AMR-WBservices is Accept

1526732690 L.Voice.VQI.AMRWB.UL.Poor.Times

Number of timesuplink voice qualityof AMR-WBservices is Poor

1526732691 L.Voice.VQI.AMRWB.UL.Bad.Times

Number of timesuplink voice qualityof AMR-WBservices is Bad

1526732692 L.Voice.VQI.AMRWB.DL.Excellent.Times

Number of timesdownlink voicequality of AMR-WB services isExcellent

1526732693 L.Voice.VQI.AMRWB.DL.Good.Times

Number of timesdownlink voicequality of AMR-WB services isGood

1526732694 L.Voice.VQI.AMRWB.DL.Accept.Times

Number of timesdownlink voicequality of AMR-WB services isAccept

1526732695 L.Voice.VQI.AMRWB.DL.Poor.Times

Number of timesdownlink voicequality of AMR-WB services is Poor

1526732696 L.Voice.VQI.AMRWB.DL.Bad.Times

Number of timesdownlink voicequality of AMR-WB services is Bad

1526732721 L.Traffic.User.VoIP.Avg

Average number ofVoIP UEs in a cell

1526732722 L.Traffic.User.VoIP.Max

Maximum numberof VoIP UEs in acell

1526732890 L.Voice.NormRel.UL.LowQuality

Number of normalvoice call releasesin the cell (pooruplink voicequality)

1526732891 L.Voice.NormRel.DL.LowQuality

Number of normalvoice call releasesin the cell (poordownlink voicequality)

1526732892 L.Voice.UL.Silent.Num

Number of timesthat a UEexperiences uplinkvoice mute in thecell

1526732893 L.Voice.DL.Silent.Num

Number of timesthat a UEexperiencesdownlink voicemute in the cell

1526736660 L.Voice.VQI.UL.Excellent.Times.PLMN

Number of timesuplink voice qualityis Excellent for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

PerformanceManagementRAN Sharing withCommon CarrierRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierRAN Sharing withDedicated CarrierHybrid RANSharing

1526736661 L.Voice.VQI.UL.Good.Times.PLMN

Number of timesuplink voice qualityis Good for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736662 L.Voice.VQI.UL.Accept.Times.PLMN

Number of timesuplink voice qualityis Accept for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736663 L.Voice.VQI.UL.Poor.Times.PLMN

Number of timesuplink voice qualityis Poor for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736664 L.Voice.VQI.UL.Bad.Times.PLMN

Number of timesuplink voice qualityis Bad for a specificoperator in a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736665 L.Voice.VQI.DL.Excellent.Times.PLMN

Number of timesdownlink voicequality is Excellentfor a specificoperator in a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736666 L.Voice.VQI.DL.Good.Times.PLMN

Number of timesdownlink voicequality is Good fora specific operatorin a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736667 L.Voice.VQI.DL.Accept.Times.PLMN

Number of timesdownlink voicequality is Acceptfor a specificoperator in a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736668 L.Voice.VQI.DL.Poor.Times.PLMN

Number of timesdownlink voicequality is Poor for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736669 L.Voice.VQI.DL.Bad.Times.PLMN

Number of timesdownlink voicequality is Bad for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736670 L.Voice.VQI.AMRWB.UL.Excellent.Times.PLMN

Number of timesuplink voice qualityof AMR-WBservices isExcellent for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736671 L.Voice.VQI.AMRWB.UL.Good.Times.PLMN

Number of timesuplink voice qualityof AMR-WBservices is Good fora specific operatorin a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736672 L.Voice.VQI.AMRWB.UL.Accept.Times.PLMN

Number of timesuplink voice qualityof AMR-WBservices is Acceptfor a specificoperator in a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736673 L.Voice.VQI.AMRWB.UL.Poor.Times.PLMN

Number of timesuplink voice qualityof AMR-WBservices is Poor fora specific operatorin a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736674 L.Voice.VQI.AMRWB.UL.Bad.Times.PLMN

Number of timesuplink voice qualityof AMR-WBservices is Bad for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736675 L.Voice.VQI.AMRWB.DL.Excellent.Times.PLMN

Number of timesdownlink voicequality of AMR-WB services isExcellent for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736676 L.Voice.VQI.AMRWB.DL.Good.Times.PLMN

Number of timesdownlink voicequality of AMR-WB services isGood for a specificoperator in a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736677 L.Voice.VQI.AMRWB.DL.Accept.Times.PLMN

Number of timesdownlink voicequality of AMR-WB services isAccept for aspecific operator ina cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736678 L.Voice.VQI.AMRWB.DL.Poor.Times.PLMN

Number of timesdownlink voicequality of AMR-WB services is Poorfor a specificoperator in a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736679 L.Voice.VQI.AMRWB.DL.Bad.Times.PLMN

Number of timesdownlink voicequality of AMR-WB services is Badfor a specificoperator in a cell

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-004008

LOFD-001036

TDLOFD-001036

LOFD-001037

TDLOFD-001037

LOFD-070206

1526736680 L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.1

Number ofdownlink trafficSDUs discarded bythe PDCP layer forservices with a QCIof 1 for a specificoperator in a cell

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002008TDLBFD-002008LBFD-002025TDLBFD-002025LOFD-001036TDLOFD-001036LOFD-001037TDLOFD-001037LOFD-070206

Radio BearerManagementRadio BearerManagementBasic SchedulingBasic SchedulingRAN Sharing withCommon CarrierRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierRAN Sharing withDedicated CarrierHybrid RANSharing

1526736682 L.PDCP.Tx.TotRev.Trf.SDU.PLMN.QCI.1

Number oftransmitteddownlink trafficPDCP SDUs forservices with a QCIof 1 for a specificoperator in a cell

1526736684 L.Traffic.UL.PktLoss.Loss.PLMN.QCI.1

Total number ofdiscarded uplinkPDCP SDUs fortraffic services witha QCI of 1 for aspecific operator ina cell

1526736686 L.Traffic.UL.PktLoss.Tot.PLMN.QCI.1

Total number ofexpected uplinkdata packets forDRB services witha QCI of 1 for aspecific operator ina cell

1526736692 L.Traffic.User.VoIP.Avg.PLMN

Average number ofVoIP UEs of aspecific operator ina cell

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002007TDLBFD-002007LOFD-001036TDLOFD-001036LOFD-001037TDLOFD-001037LOFD-070206

RRC ConnectionManagementRRC ConnectionManagementRAN Sharing withCommon CarrierRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierRAN Sharing withDedicated CarrierHybrid RANSharing

1526736693 L.Traffic.User.VoIP.Max.PLMN

Maximum numberof VoIP UEs of aspecific operator ina cell

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002007TDLBFD-002007LOFD-001036TDLOFD-001036LOFD-001037TDLOFD-001037LOFD-070206

RRC ConnectionManagementRRC ConnectionManagementRAN Sharing withCommon CarrierRAN Sharing withCommon CarrierRAN Sharing withDedicated CarrierRAN Sharing withDedicated CarrierHybrid RANSharing

1526736735 L.ChMeas.CCE.ULUsed.VoIP

Number of PDCCHCCEs used foruplink VoIPservices

1526736736 L.ChMeas.CCE.DLUsed.VoIP

Number of PDCCHCCEs used fordownlink VoIPservices

1526736737 L.Traffic.DL.PktUuLoss.Loss.PLMN.QCI.1

Total number ofdiscarded downlinkPDCP SDUs fortraffic services witha QCI of 1 for aspecific operator ina cell

1526736739 L.Traffic.DL.PktUuLoss.Tot.PLMN.QCI.1

Total number ofexpected downlinkdata packets forDRB services witha QCI of 1 for aspecific operator ina cell

1526737724 L.Traffic.UL.SCH.QPSK.TB.QCI.1

Number of QCI-1Service TBsinitially transmittedon the uplink SCHin QPSKmodulation mode

Transport ChannelManagementModulation: DL/ULQPSK, DL/UL16QAM, DL64QAMTransport ChannelManagementModulation: DL/ULQPSK, DL/UL16QAM, DL64QAM

Number of QCI-1Service TBsinitially transmittedon the uplink SCHin 16QAMmodulation mode

Transport ChannelManagementModulation: DL/ULQPSK, DL/UL16QAM, DL64QAMTransport ChannelManagementModulation: DL/ULQPSK, DL/UL16QAM, DL64QAM

Number of QCI-1Service TBsinitially transmittedon the uplink SCHin 64QAMmodulation mode

Multi-mode: NoneGSM: NoneUMTS: NoneLTE:LBFD-002002LOFD-001006TDLBFD-002002TDLOFD-001006

Transport ChannelManagementUL 64QAMTransport ChannelManagementUL 64QAM

1526737730 L.Traffic.UL.SCH.QPSK.ErrTB.Ibler.QCI.1

Number of QCI-1Service TBs withinitial transmissionfailures on theuplink SCH inQPSK modulationmode

Transport ChannelManagementTransport ChannelManagement

Number of QCI-1Service TBs withinitial transmissionfailures on theuplink SCH in16QAM modulationmode

Number of QCI-1Service TBs withinitial transmissionfailures on theuplink SCH in64QAM modulationmode

12 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRANVoLTE Feature Parameter Description 12 Glossary

13 Reference Documents

1. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for EvolvedUniversal 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 Description8. Scheduling Feature Parameter Description9. DRX and Signaling Control Feature Parameter Description10. Admission and Congestion Control Feature Parameter Description11. Power Control Feature Parameter Description12. Intra-RAT Mobility Management in Connected Mode Feature Parameter Description13. Inter-RAT Mobility Management in Connected Mode Feature Parameter Description14. QoS Management Feature Parameter Description

eRANVoLTE Feature Parameter Description 13 Reference Documents

Vo lte(eran8.1 03)

Mobile

03 - LTEND - LTE MIMO

03. LTE Air Interface_p

4G LTE: The Fastest, Most Advanced 4G Network in Americaitmf.uga.edu/minutes/2011-03-03/verizon_presentation.pdf · 4G LTE TECHNICAL BENEFITS OVERVIEW ... WiMAX is an evolution of

TR 129 949 - V13.3.0 - Universal Mobile Telecommunications System (UMTS); LTE… · 2016-01-20 · ETSI TR 1 Universal Mobile Tel Study on technical aspe with Voice over LTE (Vo an

Cisco 4G LTE Software Configuration Guide · Cisco 4G LTE Software Configuration Guide First Published: 2012-03-16 Last Modified: 2017-12-22 Cisco 4G LTE Software Configuration

8 the path to voice over lte - vo lte

Vo lezing ict in de gezondheidszorg, 03-02-2017

intelligent Converged network consolIdating Radio and ...icirrus-5gnet.eu/wp-content/uploads/2017/03/D3.3-20161221-FINAL... · LTE Long Term Evolution LTE-A LTE-Advanced MAC Media

Nacional de Vigilancia de Medicamentos y Alimentos — INVIMA RESOLUCION No. 2015020068 DE 22 de Mayo ... vo. Bo 500-03-1604 vo Bo. 500-03-76 vo. Bo. 500

03 - LTE Dimensioning Guidelines - Outdoor Link Budget - FDD - Ed2.9 - Internal

03 LTE Radio Parameters System Info v20

LTE in Mining - 3D-P3d-p.com/wp-content/uploads/2018/03/Performance-of-LTE-in-Mining-White... · LTE client, again removing that traffic from the asymmetrical LTE links. • Finally,

APCO Emerging Technology Forum P SAFETY …Dec 03, 2013 · •PTT over LTE (Push-to-talk over LTE) –GSMA •VoLTE (Voice over LTE) •Lessons Learned –Public safety LTE is a

03 ZTE%27s LTE Mobile Backhaul Solution

3.VO Der Krieg und die conditio humana Vorlage-07.06homepage.univie.ac.at/.../3.-VO-Der-Krieg-und-die-conditio-humana.pdf · 3. VO Der Krieg und die conditio humana (27. 05. & 03

130879103 LTE eRAN3 0 Handover Fault Diagnosis ISSUE 1 03

MAGRABAR® · 2020. 7. 24. · MAGRABAR ® 4000 Vegetable Oil Liquid 0® % VO VO VO VO VO VO VO VO MAGRABAR ® 4010 Vegetable Oil Liquid 0 % VO VO VO VO VO VO VO VO CI = Certified

03 RA41333EN40GLA2 LTE Capacity Areas

vo) (sax, f l) (per c) 03-5237-gggg 06-6213-2954 TEL 03-5553 … · 2017-04-19 · vo) (sax, f l) (per c) 03-5237-gggg 06-6213-2954 TEL 03-5553-2563 The Japan Foundation

LTE Bitstream Verification Application Note · 2019-03-24 · The FSx together with options -K100 (EUTRA/LTE FDD DL Measurements), -K102 (EUTRA/LTE DL MIMO Measurements), -K104 (EUTRA/LTE