February 20, 2017 | Author: Muhammad Abdur Razzaqe | Category: N/A
eRAN
VoLTE Feature Parameter Description Issue
03
Date
2015-06-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd. Address:
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website:
http://www.huawei.com
Email:
[email protected]
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
i
eRAN VoLTE Feature Parameter Description
Contents
Contents 1 About This Document.................................................................................................................. 1 1.1 Scope.............................................................................................................................................................................. 1 1.2 Intended Audience.......................................................................................................................................................... 2 1.3 Change History............................................................................................................................................................... 2 1.4 Differences Between eNodeB Types.............................................................................................................................. 6
2 Overview......................................................................................................................................... 8 2.1 Background.....................................................................................................................................................................8 2.2 Introduction.................................................................................................................................................................... 9 2.3 Benefits......................................................................................................................................................................... 10 2.4 Architecture.................................................................................................................................................................. 10
3 Basic VoLTE Functions...............................................................................................................14 3.1 Speech Codec Scheme and Traffic Model....................................................................................................................15 3.2 VoLTE Voice Policy Selection......................................................................................................................................16 3.2.1 Common Scenarios....................................................................................................................................................16 3.2.1.1 General Principles for Voice Policy Selection........................................................................................................16 3.2.1.2 VoLTE Mobility Capability Decision..................................................................................................................... 18 3.2.2 VoLTE-Prohibited Scenario....................................................................................................................................... 19 3.3 Radio Bearer Management........................................................................................................................................... 21 3.3.1 Radio Bearer Setup.................................................................................................................................................... 21 3.3.2 Radio Bearer QoS Management................................................................................................................................ 23 3.4 Admission and Congestion Control..............................................................................................................................24 3.4.1 Overview................................................................................................................................................................... 24 3.4.2 Load Monitoring........................................................................................................................................................24 3.4.3 Admission Control.....................................................................................................................................................25 3.4.4 Congestion Control....................................................................................................................................................25 3.5 Dynamic Scheduling and Power Control..................................................................................................................... 26 3.5.1 Dynamic Scheduling..................................................................................................................................................26 3.5.2 Power Control in Dynamic Scheduling..................................................................................................................... 27
4 Enhanced VoLTE Features......................................................................................................... 28 4.1 Capacity Enhancement................................................................................................................................................. 29 4.1.1 Semi-Persistent Scheduling and Power Control........................................................................................................ 29 4.1.1.1 Semi-Persistent Scheduling.................................................................................................................................... 29 Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
ii
eRAN VoLTE Feature Parameter Description
Contents
4.1.1.2 Power Control in Semi-Persistent Scheduling........................................................................................................32 4.1.2 ROHC........................................................................................................................................................................ 33 4.2 Coverage Improvement................................................................................................................................................ 34 4.2.1 TTI Bundling............................................................................................................................................................. 34 4.2.1.1 Overview................................................................................................................................................................ 34 4.2.1.2 Principles................................................................................................................................................................ 34 4.2.2 ROHC........................................................................................................................................................................ 36 4.2.3 Uplink RLC Segmentation Enhancement..................................................................................................................37 4.3 Quality Improvement....................................................................................................................................................38 4.3.1 Voice Characteristic Awareness Scheduling..............................................................................................................38 4.3.2 Uplink Compensation Scheduling............................................................................................................................. 39 4.3.3 Voice-Specific AMC..................................................................................................................................................41 4.4 Power Saving................................................................................................................................................................ 41 4.5 Mobility Management.................................................................................................................................................. 42 4.5.1 Overview................................................................................................................................................................... 42 4.5.2 Intra-Frequency Handover.........................................................................................................................................43 4.5.3 Inter-Frequency Handover.........................................................................................................................................43 4.5.4 Inter-RAT Handover.................................................................................................................................................. 45 4.5.4.1 Handover Type........................................................................................................................................................45 4.5.4.2 Handover Mode...................................................................................................................................................... 47
5 Special Processing by Other Features......................................................................................48 6 Related Features...........................................................................................................................51 6.1 LOFD-001016 VoIP Semi-persistent Scheduling.........................................................................................................52 6.2 LOFD-001048 TTI Bundling....................................................................................................................................... 53 6.3 Uplink RLC Segmentation Enhancement.....................................................................................................................54 6.4 LOFD-081229 Voice Characteristic Awareness Scheduling........................................................................................ 54 6.5 LBFD-081104 UL Compensation Scheduling............................................................................................................. 55 6.6 LBFD-081105 Voice-Specific AMC............................................................................................................................ 55 6.7 Other Features...............................................................................................................................................................55
7 Network Impact........................................................................................................................... 58 7.1 LOFD-001016 VoIP Semi-persistent Scheduling.........................................................................................................59 7.2 LOFD-001048 TTI Bundling....................................................................................................................................... 59 7.3 Uplink RLC Segmentation Enhancement.....................................................................................................................60 7.4 LOFD-081229 Voice Characteristic Awareness Scheduling........................................................................................ 60 7.5 LBFD-081104 UL Compensation Scheduling............................................................................................................. 61 7.6 LBFD-081105 Voice-Specific AMC............................................................................................................................ 61 7.7 Other Features...............................................................................................................................................................62
8 Voice Service Performance Evaluation................................................................................... 64 8.1 QoS Requirements........................................................................................................................................................ 64 8.2 Quality Evaluation........................................................................................................................................................ 64 8.2.1 Subjective Evaluation................................................................................................................................................ 64 Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iii
eRAN VoLTE Feature Parameter Description
Contents
8.2.2 Objective Evaluation................................................................................................................................................. 65 8.2.3 Measurement-based Evaluation.................................................................................................................................65 8.3 Capacity Evaluation......................................................................................................................................................67 8.4 Performance Evaluation............................................................................................................................................... 68
9 Engineering Guidelines............................................................................................................. 69 9.1 Overview...................................................................................................................................................................... 69 9.2 Basic Functions.............................................................................................................................................................70 9.2.1 When to Use Basic Functions....................................................................................................................................70 9.2.2 Required Information................................................................................................................................................ 71 9.2.3 Deployment............................................................................................................................................................... 71 9.2.3.1 Requirements.......................................................................................................................................................... 71 9.2.3.2 Data Preparation..................................................................................................................................................... 71 9.2.3.3 Precautions..............................................................................................................................................................73 9.2.3.4 Hardware Adjustment.............................................................................................................................................73 9.2.3.5 Initial Configuration............................................................................................................................................... 73 9.2.3.6 Activation Observation...........................................................................................................................................76 9.2.3.7 Reconfiguration...................................................................................................................................................... 78 9.2.3.8 Deactivation............................................................................................................................................................78 9.2.4 Performance Monitoring............................................................................................................................................79 9.2.4.1 Voice KPIs.............................................................................................................................................................. 79 9.2.4.2 Voice QoS............................................................................................................................................................... 83 9.2.4.3 Voice Quality.......................................................................................................................................................... 84 9.2.4.4 Voice Capacity........................................................................................................................................................ 87 9.2.5 Parameter Optimization............................................................................................................................................. 89 9.2.6 Troubleshooting......................................................................................................................................................... 90 9.3 Semi-Persistent Scheduling.......................................................................................................................................... 90 9.3.1 When to Use Semi-Persistent Scheduling and Deploy Power Control..................................................................... 90 9.3.2 Required Information................................................................................................................................................ 91 9.3.3 Deployment of Semi-Persistent Scheduling.............................................................................................................. 91 9.3.3.1 Requirements.......................................................................................................................................................... 91 9.3.3.2 Data Preparation..................................................................................................................................................... 92 9.3.3.3 Precautions..............................................................................................................................................................93 9.3.3.4 Hardware Adjustment.............................................................................................................................................93 9.3.3.5 Initial Configuration............................................................................................................................................... 93 9.3.3.6 Activation Observation...........................................................................................................................................96 9.3.3.7 Reconfiguration...................................................................................................................................................... 99 9.3.3.8 Deactivation............................................................................................................................................................99 9.3.4 Performance Monitoring..........................................................................................................................................100 9.3.5 Parameter Optimization........................................................................................................................................... 100 9.3.6 Troubleshooting....................................................................................................................................................... 101 9.4 TTI Bundling.............................................................................................................................................................. 101 9.4.1 When to Deploy TTI Bundling................................................................................................................................101 Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iv
eRAN VoLTE Feature Parameter Description
Contents
9.4.2 Required Information.............................................................................................................................................. 101 9.4.3 Deployment of TTI Bundling.................................................................................................................................. 101 9.4.3.1 Requirements........................................................................................................................................................ 101 9.4.3.2 Data Preparation................................................................................................................................................... 102 9.4.3.3 Precautions............................................................................................................................................................104 9.4.3.4 Hardware Adjustment...........................................................................................................................................104 9.4.3.5 Initial Configuration............................................................................................................................................. 104 9.4.3.6 Activation Observation.........................................................................................................................................106 9.4.3.7 Reconfiguration.................................................................................................................................................... 108 9.4.3.8 Deactivation..........................................................................................................................................................108 9.4.4 Performance Monitoring..........................................................................................................................................109 9.4.5 Parameter Optimization........................................................................................................................................... 109 9.4.6 Troubleshooting....................................................................................................................................................... 109 9.5 UL RLC Segmentation Enhancement........................................................................................................................ 109 9.5.1 When to Use Uplink RLC Segmentation Enhancement..........................................................................................110 9.5.2 Required Information...............................................................................................................................................110 9.5.3 Deployment..............................................................................................................................................................110 9.5.3.1 Requirements........................................................................................................................................................ 110 9.5.3.2 Data Preparation................................................................................................................................................... 110 9.5.3.3 Precautions............................................................................................................................................................111 9.5.3.4 Hardware Adjustment........................................................................................................................................... 111 9.5.3.5 Initial Configuration..............................................................................................................................................111 9.5.3.6 Activation Observation......................................................................................................................................... 113 9.5.3.7 Reconfiguration.................................................................................................................................................... 114 9.5.3.8 Deactivation.......................................................................................................................................................... 115 9.5.4 Performance Monitoring..........................................................................................................................................115 9.5.5 Parameter Optimization........................................................................................................................................... 116 9.5.6 Troubleshooting....................................................................................................................................................... 116 9.6 Voice Characteristic Awareness Scheduling............................................................................................................... 116 9.6.1 When to Use Voice Characteristic Awareness Scheduling...................................................................................... 116 9.6.2 Required Information...............................................................................................................................................116 9.6.3 Deployment..............................................................................................................................................................116 9.6.3.1 Requirements........................................................................................................................................................ 116 9.6.3.2 Data Preparation................................................................................................................................................... 116 9.6.3.3 Precautions............................................................................................................................................................118 9.6.3.4 Hardware Adjustment........................................................................................................................................... 118 9.6.3.5 Initial Configuration............................................................................................................................................. 118 9.6.3.6 Activation Observation.........................................................................................................................................121 9.6.3.7 Reconfiguration.................................................................................................................................................... 121 9.6.3.8 Deactivation..........................................................................................................................................................121 9.6.4 Performance Monitoring..........................................................................................................................................122 9.6.5 Parameter Optimization........................................................................................................................................... 123 Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
v
eRAN VoLTE Feature Parameter Description
Contents
9.6.6 Troubleshooting....................................................................................................................................................... 123 9.7 Uplink Compensation Scheduling.............................................................................................................................. 123 9.7.1 When to Use Uplink Compensation Scheduling..................................................................................................... 123 9.7.2 Required Information.............................................................................................................................................. 123 9.7.3 Deployment............................................................................................................................................................. 123 9.7.3.1 Requirements........................................................................................................................................................ 123 9.7.3.2 Data Preparation................................................................................................................................................... 123 9.7.3.3 Precautions............................................................................................................................................................124 9.7.3.4 Hardware Adjustment...........................................................................................................................................124 9.7.3.5 Initial Configuration............................................................................................................................................. 125 9.7.3.6 Activation Observation.........................................................................................................................................127 9.7.3.7 Reconfiguration.................................................................................................................................................... 127 9.7.3.8 Deactivation..........................................................................................................................................................128 9.7.4 Performance Monitoring..........................................................................................................................................128 9.7.5 Parameter Optimization........................................................................................................................................... 129 9.7.6 Troubleshooting....................................................................................................................................................... 129 9.8 Voice-Specific AMC...................................................................................................................................................129 9.8.1 When to Use Voice-Specific AMC..........................................................................................................................129 9.8.2 Required Information.............................................................................................................................................. 129 9.8.3 Deployment............................................................................................................................................................. 129 9.8.3.1 Requirements........................................................................................................................................................ 129 9.8.3.2 Data Preparation................................................................................................................................................... 129 9.8.3.3 Precautions............................................................................................................................................................130 9.8.3.4 Hardware Adjustment...........................................................................................................................................130 9.8.3.5 Initial Configuration............................................................................................................................................. 130 9.8.3.6 Activation Observation.........................................................................................................................................132 9.8.3.7 Reconfiguration.................................................................................................................................................... 134 9.8.3.8 Deactivation..........................................................................................................................................................134 9.8.4 Performance Monitoring..........................................................................................................................................134 9.8.5 Parameter Optimization........................................................................................................................................... 135 9.8.6 Troubleshooting....................................................................................................................................................... 135
10 Parameters................................................................................................................................. 136 11 Counters.................................................................................................................................... 217 12 Glossary..................................................................................................................................... 249 13 Reference Documents............................................................................................................. 250
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
vi
eRAN VoLTE Feature Parameter Description
1 About This Document
1
About This Document
1.1 Scope This document describes Voice over LTE (VoLTE), including its technical principles, related features, network impact, and engineering guidelines. VoLTE is based on IP multimedia subsystem (IMS). This document covers the following features: l
LOFD-001016 VoIP Semi-persistent Scheduling
l
LOFD-001048 TTI Bundling
l
LOFD-081229 Voice Characteristic Awareness Scheduling
l
LBFD-081104 UL Compensation Scheduling
l
LBFD-081105 Voice-Specific AMC
This document applies to the following types of eNodeBs. eNodeB Type
Model
Macro
3900 series eNodeB
Micro base station
BTS3202E
LampSite
DBS3900 LampSite
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this document. Any future updates will be described in the product documentation delivered with future software releases. This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
1
eRAN VoLTE Feature Parameter Description
1 About This Document
1.2 Intended Audience This document is intended for personnel who: l
Need to understand the features described herein
l
Work with Huawei products
1.3 Change History This section provides information about the changes in different document versions. There are two types of changes: l
Feature change Changes in features and parameters of a specified version as well as the affected entities
l
Editorial change Changes in wording or addition of information and any related parameters affected by editorial changes. Editorial change does not specify the affected entities.
eRAN8.1 03 (2015-06-30) This issue includes the following changes. Change Type
Change Description
Parameter Change
Affected Entity
Feature change
None
None
Macro, micro, and LampSite eNodeBs
Editorial change
Revised the following sections:
None
-
4.1.1 Semi-Persistent Scheduling and Power Control 4.3.1 Voice Characteristic Awareness Scheduling 4.3.2 Uplink Compensation Scheduling
eRAN8.1 02 (2015-04-30) This issue includes the following changes.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
2
eRAN VoLTE Feature Parameter Description
1 About This Document
Change Type
Change Description
Parameter Change
Affected Entity
Feature change
Changed the optional feature VoiceSpecific AMC to a basic feature, and changed the feature ID from LOFD-081230 to LBFD-081105.
None
Macro, micro, and LampSite eNodeBs
Editorial change
Revised the following sections:
None
-
3.2.1.2 VoLTE Mobility Capability Decision 3.2.2 VoLTE-Prohibited Scenario 9.2.3.1 Requirements 9.2.6 Troubleshooting
eRAN8.1 01 (2015-03-23) This issue includes the following changes. Change Type
Change Description
Parameter Change
Affected Entity
Feature change
Modified the LOFD-081229 Voice Characteristic Awareness Scheduling feature to add independent configurations for the UE inactivity timer for voice services. For details, see the following sections:
Added the following parameter:
Macro, micro, and LampSite eNodeBs
2.4 Architecture
CELLALGOS WITCH.UEIn activeTimerQC I1Switch
4.3.1 Voice Characteristic Awareness Scheduling 7.4 LOFD-081229 Voice Characteristic Awareness Scheduling Editorial change
Added network impact descriptions. For details, see the following sections:
None
-
7.1 LOFD-001016 VoIP Semipersistent Scheduling 7.2 LOFD-001048 TTI Bundling
eRAN8.1 Draft A (2015-01-15) Compared with Issue 05 (2014-11-13) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
3
eRAN VoLTE Feature Parameter Description
1 About This Document
Change Type
Change Description
Parameter Change
Affected Entity
Feature change
Modified the voice quality monitoring mechanism as follows:
Added the following parameters:
Macro, micro, and LampSite eNodeBs
l The voice quality threshold becomes configurable. l The downlink voice quality evaluation is changed from EModel to VQI-Model. For details, see 8.2.3 Measurementbased Evaluation.
l VQMAlgo. VqiExcellen tThd l VQMAlgo. VqiPoorThd l VQMAlgo. VqiGoodTh d l VQMAlgo. VqiBadThd
Added policy control for measurements (such as ANR measurement) by UEs performing voice services.
Added the GlobalProcSwi tch.VoipWithG apMode parameter.
Macro, micro, and LampSite eNodeBs
Added the descriptions of the relationship between LOFD-001016 VoIP Semi-persistent Scheduling and LAOFD-0010014 DL 2x2 MIMO based on TM9. For details, see 4.1.1 Semi-Persistent Scheduling and Power Control.
None
Macro, micro, and LampSite eNodeBs
Modified the relationship between LOFD-001048 TTI Bundling and LAOFD-001001 LTE-A Introduction. For details, see 4.2.1 TTI Bundling.
None
Macro, micro, and LampSite eNodeBs
For details, see 5 Special Processing by Other Features.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
4
eRAN VoLTE Feature Parameter Description
Change Type
1 About This Document
Change Description
Parameter Change
Affected Entity
Modified the functions of TTI bundling:
Added the following parameters:
Macro, micro, and LampSite eNodeBs
l Enabled the configuration of applicable services of TTI bundling. The applicable services include VoLTE or a combination of VoLTE and data. l Added five key parameters to TTI bundling. For details, see 4.2.1 TTI Bundling.
l CellUlschAl go.TtiBundl ingTriggerS trategy l CellUlschAl go.Statistic NumThdFo rTtibTrig l CellUlschAl go.Statistic NumThdFo rTtibExit l CellUlschAl go.HystToE xitTtiBundli ng l CellUlschAl go.TtiBundl ingRlcMax SegNum l CellUlschAl go.TtiBundl ingHarqMa xTxNum
Added LOFD-081229 Voice Characteristic Awareness Scheduling. For details, see 4.3.1 Voice Characteristic Awareness Scheduling and 9.6 Voice Characteristic Awareness Scheduling.
Issue 03 (2015-06-30)
l Added the CELLULS CHALGO. UlDelaySch Strategy parameter.
Macro, micro, and LampSite eNodeBs
l Added the UlVoLTED ataSizeEstS witch option to the CELLULS CHALGO. UlEnhence dVoipSchSw parameter.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
5
eRAN VoLTE Feature Parameter Description
Change Type
Editorial change
1 About This Document
Change Description
Parameter Change
Affected Entity
Added LBFD-081104 UL Compensation Scheduling. For details, see 4.3.2 Uplink Compensation Scheduling and 9.7 Uplink Compensation Scheduling.
Added the UlVoipSchOpt Switch option to the CELLULSCH ALGO.UlEnhe ncedVoipSchS w parameter.
Macro, micro, and LampSite eNodeBs
Added LOFD-081230 VoiceSpecific AMC. For details, see 4.3.3 Voice-Specific AMC and 9.8 VoiceSpecific AMC.
Added the CELLULSCH ALGO.SinrAdj TargetIblerfor VoLTE parameter.
Macro, micro, and LampSite eNodeBs
Modified the document structure to enhance readability.
None
-
Added 8.2.2 Objective Evaluation.
None
-
Added counters to measure handover success rates for VoLTE services. For details, see 9.2.4.1 Voice KPIs.
None
-
Added 4.3.1 Voice Characteristic Awareness Scheduling, which incorporates the description of uplink delay-based dynamic scheduling.
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 following table lists the differences of VoIP-related features between eNodeB types. For details about other features and functions, see the corresponding feature parameter descriptions.
Issue 03 (2015-06-30)
Feature ID
Feature Name
Suppor ted by Macro eNode Bs
Supported by Micro eNodeBs
Supported by LampSite eNodeBs
LOFD-001016
VoIP Semi-persistent Scheduling
Yes
Yes
Yes
LOFD-001048
TTI Bundling
Yes
Yes
Yes
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
6
eRAN VoLTE Feature Parameter Description
1 About This Document
Feature ID
Feature Name
Suppor ted by Macro eNode Bs
Supported by Micro eNodeBs
Supported by LampSite eNodeBs
LOFD-081229
Voice Characteristic Awareness Scheduling
Yes
Yes
Yes
LBFD-081105
UL Compensation Scheduling
Yes
Yes
Yes
LBFD-081105
Voice-Specific AMC
Yes
Yes
Yes
Function Implementation in Macro, Micro, and LampSite eNodeBs
Issue 03 (2015-06-30)
Function
Difference
High speed mobility
Micro and LampSite eNodeBs do not support high speed mobility. The dynamic scheduling policies for high speed mobility described herein apply only to macro eNodeBs. For details, see 3.5.1 Dynamic Scheduling.
1.4 MHz bandwidth
Micro and LampSite eNodeBs do not support 1.4 MHz bandwidth. The dynamic scheduling policies for 1.4 MHz bandwidth described herein apply only to macro eNodeBs. For details, see 3.5.1 Dynamic Scheduling.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
7
eRAN VoLTE Feature Parameter Description
2 Overview
2
Overview
2.1 Background The LTE voice solution is as follows: l
Voice solution based on dual-standby UEs A dual-standby UE is capable of receiving or sending signals in both E-UTRAN and GERAN or UTRAN. Dual-standby UEs automatically select GERAN or UTRAN to perform voice services and select E-UTRAN to perform data services. That is, the EUTRAN provides dual-standby UEs with only data services.
l
Voice solution based on CSFB In the initial phase of LTE network deployment, CSFB is a transitional solution to provide voice services for LTE users if the IMS is not yet deployed. Figure 2-1 shows the voice solution based on CSFB. Figure 2-1 Voice solution based on CSFB
With the CSFB solution, when a UE initiates a CS service in the E-UTRAN, the MME instructs the UE to fall back to the legacy CS domain of the GERAN or UTRAN before Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
8
eRAN VoLTE Feature Parameter Description
2 Overview
the UE performs the service. For details about CSFB, see CS Fallback Feature Parameter Description. l
Voice solution based on the IMS This solution is used in the mature stage of the LTE network when the IMS is deployed, as shown in Figure 2-2. With this solution, UEs can directly perform voice services in an LTE network. This solution is also termed as the Voice over LTE (VoLTE) solution. When LTE coverage has not been complete, UEs may move out of LTE coverage and their voice services may be discontinued. Huawei uses the following methods to ensure voice service continuity: –
VoIP services are handed over to the CS domain of the UTRAN/GERAN through single radio voice call continuity (SRVCC). For details about SRVCC, see SRVCC Feature Parameter Description.
–
VoIP services are handed over to the UTRAN/GERAN through PS handovers. For details about PS handovers, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
Figure 2-2 Voice solution based on IMS
2.2 Introduction VoLTE is the voice service supported by the IP transmission network between calling/called UEs in the E-UTRAN and the IMS. That is, with VoLTE, calling/called UEs in the LTE network can perform voice services directly. Emergency services are not described in this document. For details about emergency services, see Emergency Call Feature Parameter Description.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
9
eRAN VoLTE Feature Parameter Description
2 Overview
2.3 Benefits VoLTE provides UEs in the E-UTRAN with voice services, without the need of falling back to GERAN or UTRAN. VoLTE features the following characteristics: l
Higher spectral efficiency
l
Better user experience, such as lower access delay and better voice quality
2.4 Architecture Network Architecture Figure 2-3 illustrates the LTE/SAE architecture in non-roaming scenarios. SAE is short for System Architecture Evolution. For details about the architectures in roaming and nonroaming scenarios, see section 4.2 "Architecture reference model" in 3GPP TS 23.401. Figure 2-3 LTE/SAE architecture in non-roaming scenarios
MME: mobility management entity
S-GW: serving gateway
SGSN: serving GPRS support node
HSS: home subscriber server
PCRF: policy and charging rule function
PDN Gateway: packet data network gateway
IP multimedia subsystem (IMS) includes multiple network elements (NEs). These NEs perform voice session control and multimedia negotiation between the calling and called UEs.
Function Architecture Table 2-1 describes the basic functions of VoLTE.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
10
eRAN VoLTE Feature Parameter Description
2 Overview
Table 2-1 Basic VoLTE functions Function
Description
Speech codec scheme and traffic model
During a VoLTE call, the UEs negotiate a speech codec scheme, while the IMS may or may not take part in the negotiation. The commonly used codec scheme is Adaptive Multirate (AMR). For details about its voice traffic model, see 3.1 Speech Codec Scheme and Traffic Model.
VoLTE voice policy selection
During the attach procedure, the UE negotiates with the MME and selects VoLTE as the voice policy. For details about voice policy selection, see 3.2 VoLTE Voice Policy Selection.
Radio bearer management
Radio bearers with QoS class identifiers (QCIs) of 1 and 5 are set up between the calling and called UEs to carry conversational voice and signaling, respectively. For details about radio bearer management, see 3.3 Radio Bearer Management.
Admission and congestion control
The eNodeB performs admission and congestion control for conversational voice (QCI 1) and signaling (QCI 5). For details about admission and congestion control, see 3.4 Admission and Congestion Control.
Dynamic scheduling and power control
By default, the eNodeB performs dynamic scheduling and uses power control policies that are suitable for dynamic scheduling. For details about dynamic scheduling and power control, see 3.5 Dynamic Scheduling and Power Control.
UEs can perform VoLTE services after the preceding functions are enabled. Table 2-2 describes the features that help improve VoLTE performance such as capacity, coverage, and voice quality. Table 2-2 Enhanced VoLTE features/functions Category
Feature/Function Name
Description
Capacity enhanceme nt
Semi-persistent scheduling and power control
The eNodeB performs semi-persistent scheduling and uses suitable power control policies for UEs during talk spurts. This feature applies only to voice services. For details about semi-persistent scheduling and power control, see 4.1.1 Semi-Persistent Scheduling and Power Control. The eNodeB performs dynamic scheduling and uses suitable power control policies for UEs at voice service setup and during silent periods.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
11
eRAN VoLTE Feature Parameter Description
Category
2 Overview
Feature/Function Name
Description
Robust header compression (ROHC)
ROHC compresses the headers of voice packets to reduce air interface overheads. This feature applies only to voice services. For details about how ROHC works for VoLTE, see 4.1.2 ROHC.
Coverage improveme nt
Transmission time interval (TTI) bundling
Multiple TTIs are bound together for UEs with poor signal quality to transmit the same data. This increases the once-off transmission success rate. This feature applies only to uplink voice services. For details, see 4.2.1 TTI Bundling.
Robust header compression (ROHC)
ROHC compresses the headers of voice packets to reduce air interface overheads and increase the once-off transmission success rate. This feature applies only to voice services. For details about how ROHC works for VoLTE, see 4.2.2 ROHC.
Quality Improveme nt
Uplink RLC segmentation enhancement
This feature restricts the transport block size (TBS) in UL dynamic scheduling to control the number of uplink RLC segments for VoLTE packets. This restriction improves voice quality when channel quality is poor. For details about this feature, see 4.2.3 Uplink RLC Segmentation Enhancement.
Voice characteristic awareness scheduling
During uplink dynamic scheduling, the eNodeB adjusts the scheduling priorities of UEs based on their waiting time and estimates the voice volume to be dynamically scheduled in the uplink. An independent inactivity timer is configured for voice services. The purpose is to improve voice quality, decrease the service drop rate, and increase the proportion of satisfied voice service users. This feature applies only to voice services. For details about how UL delay-based dynamic scheduling, UL VoLTE volume estimation for dynamic scheduling, and independent configuration for voice inactivity timer work for VoLTE, see 4.3.1 Voice Characteristic Awareness Scheduling.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
12
eRAN VoLTE Feature Parameter Description
Category
2 Overview
Feature/Function Name
Description
Uplink compensation scheduling
For each voice user, the eNodeB measures the duration in which the user is not scheduled in the uplink. If the duration reaches a threshold, the eNodeB performs uplink compensation scheduling for the UE. The purpose is to ensure that uplink voice packets can be timely transmitted, shorten their waiting time, and reduce the number of packets discarded because of the expiry of PDCP Discard Timer. This feature applies only to voice services. For details, see 4.3.2 Uplink Compensation Scheduling.
Voice-specific AMC
The eNodeB sets a target IBLER for uplink voice services. This feature applies only to voice services. For details, see 4.3.3 Voice-Specific AMC.
Power saving
Discontinuous reception (DRX)
With DRX, UEs enter the sleep state when data is not transmitted, saving UE power. For details about how DRX works for VoLTE, see 4.4 Power Saving.
Mobility managemen t
Intra-frequency handover Inter-frequency handover Inter-RAT handover
The eNodeB performs intra-frequency, interfrequency, or inter-RAT handovers to transfer UEs performing voice services to appropriate neighboring cells to maintain voice continuity. For details about how mobility management works for VoLTE, see 4.5 Mobility Management.
Voice service performance can be evaluated on various dimensions. For details about voice service performance evaluation, see 8 Voice Service Performance Evaluation.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
13
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
3
Basic VoLTE Functions
The ENodeBAlgoSwitch.EutranVoipSupportSwitch parameter specifies whether to enable VoLTE. l
When this parameter is set to ON(On) on an eNodeB, this eNodeB supports VoLTE and allows the establishment, access, incoming handover, and reestablishment of the dedicated bearer with a QCI of 1.
l
When this parameter is set to OFF(Off)) on an eNodeB, this eNodeB does not support VoLTE and does not allow the establishment, access, incoming handover, and reestablishment of the dedicated bearer with a QCI of 1.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
14
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
3.1 Speech Codec Scheme and Traffic Model The speech codec scheme is classified into AMR and G.7 series. VoLTE uses the AMR-based speech codec scheme.
AMR AMR is an audio data compression scheme optimized for speech coding and is now widely used in GERAN and UTRAN. AMR is classified into adaptive multirate wideband (AMRWB) and adaptive multirate narrowband (AMR-NB). l
AMR-NB has eight speech coding rates. They are 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s.
l
AMR-WB has nine speech coding rates.They are 23.85 kbit/s, 23.05 kbit/s, 19.85 kbit/s, 18.25 kbit/s, 15.85 kbit/s, 14.25 kbit/s, 12.65 kbit/s, 8.85 kbit/s, and 6.6 kbit/s. NOTE
AMR-NB herein corresponds to AMR in the protocol.
Figure 3-1 shows the voice service traffic model when AMR is used as the codec scheme for VoLTE services. The AMR codec scheme to be used is negotiated between UEs, with the IMS involved. The eNodeB is transparent in the AMR codec scheme negotiation. Figure 3-1 Voice traffic model
There are two VoLTE traffic states: l
Talk spurts During talk spurts, the uplink of UEs transmits voice packets or the downlink of UEs receives voice packets. Voice packets are transmitted at intervals of 20 ms, and the packet size is determined by the speech coding rate.
l
Silent period During silent periods, the UE transmits silence insertion descriptor (SID) frames or receives SID frames at intervals of 160 ms. For different AMR speech codec rates, the SID frame sizes are all 56 bits.
The differences between talk spurts and silent period are as follows: l Issue 03 (2015-06-30)
The size of voice frames is greater than the size of SID frames. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
15
eRAN VoLTE Feature Parameter Description
l
3 Basic VoLTE Functions
The interval between neighboring voice frames is different from the interval between SID frames.
The eNodeB distinguishes between voice frames and SID frames based on the preceding differences.
G.7 Series The widely used G.7 series standards include G.711, G.729, and G.726. l
G.711 G.711, also known as pulse code modulation (PCM), is primarily used in fixed-line telephony. It supports a coding rate of 64 kbit/s.
l
G.729 G.729, known for the high voice quality and low delay, is widely used in various domains of data communications. It supports a coding rate of 8 kbit/s.
l
G.726 G.726 supports coding rates of 16 kbit/s to 40 kbit/s. The most commonly used rate is 32 kbit/s. In actual application, voice packets are sent at intervals of 20 ms.
3.2 VoLTE Voice Policy Selection UE capability and configurations on the MME determine whether a UE uses VoLTE. However, VoLTE may be inappropriate for certain sites or regions. This case is termed as VoLTE-prohibited scenario. This section describes voice policy selection for UEs in common and VoLTE-prohibited scenarios.
3.2.1 Common Scenarios 3.2.1.1 General Principles for Voice Policy Selection During the UE attach and tracking area update (TAU) period, the MME selects a voice policy based on the UE capability and configuration on the MME side. The MME then sends the UE the voice policy contained in the Attach Accept and TAU Accept messages. During voice policy selection, the MME selects a voice policy based on the following principles: l
If the UE supports only CSFB, the corresponding voice policy is CS Voice only.
l
If the UE supports only VoLTE, the corresponding voice policy is IMS PS Voice only, that is, VoLTE.
l
If the UE supports both CSFB and VoLTE, the voice policy used before negotiation with the MME is one of the following voice policies specified by operators during UE registration: –
CS Voice only That is, CSFB.
–
IMS PS Voice only That is, VoLTE.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
16
eRAN VoLTE Feature Parameter Description
–
3 Basic VoLTE Functions
Prefer CS Voice with IMS PS Voice as secondary That is, CSFB takes precedence over VoLTE. For details about the voice policy negotiation procedures between the UE and MME when this policy is used, see Annex A.2 in 3GPP TS 23.221 V9.4.0.
–
Prefer IMS PS Voice with CS Voice as secondary That is, VoLTE takes precedence over CSFB. Figure 3-2 and Figure 3-3 show the voice policy negotiation procedures between the UE and MME when this policy is used. For details about the voice service policy negotiation, see Annex A.2 in 3GPP TS 23.221 V9.4.0. Figure 3-2 Procedures for voice policy selection (non-combined attach)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
17
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
Figure 3-3 Procedures for voice policy selection (combined attach)
3GPP Release 11 introduced VoLTE mobility capability decision, which further helps the MME in selecting a VoLTE policy.
3.2.1.2 VoLTE Mobility Capability Decision Figure 3-4 Signaling procedure of VoLTE mobility capability decision
1.
During the UE attach period, the MME sends the UE Radio Capability Match Request message to the eNodeB to query whether the UE has the VoLTE mobility capability.
2.
If the eNodeB does not receive the UE radio capability message from the UE, the eNodeB sends a UE Capability Enquiry message to the UE.
3.
The UE reports its radio capability through the UE Capability Information message.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
18
eRAN VoLTE Feature Parameter Description
4.
3 Basic VoLTE Functions
If the eNodeB determines that the UE can ensure mobility after the UE performs VoLTE services, the eNodeB replies the MME with the decision result through the UE Radio Capability Match Response message. Based on the reply, the MME then selects a voice policy for UEs as follows: –
If mobility can be ensured, VoLTE is used.
–
If mobility cannot be ensured, CSFB is used.
The SupportS1UeCapMatchMsg option of the GlobalProcSwitch.ProtocolSupportSwitch parameter specifies whether the eNodeB supports the VoLTE mobility decision. l
l
When the SupportS1UeCapMatchMsg(SupportS1UeCapMatchMsg) option is selected, the UE can ensure mobility after the performing VoLTE services if the UE meets any of the following conditions: –
The UE supports UTRAN and SRVCC from E-UTRAN to UTRAN.
–
The UE supports GERAN and SRVCC from E-UTRAN to GERAN.
–
The UE supports the PS domain of UTRAN-FDD (VoHSPA), SRVCC from the PS domain to the CS domain of UTRAN-FDD, and SRVCC from the PS domain of UTRAN-FDD to the CS domain of GERAN.
–
The UE supports the PS domain of UTRAN-TDD (VoHSPA), SRVCC from the PS domain to the CS domain of UTRAN-TDD, and SRVCC from the PS domain of UTRAN-TDD to the CS domain of GERAN.
When the SupportS1UeCapMatchMsg option is deselected, the eNodeB does not perform VoLTE mobility capability decision. In this case, the eNodeB replies ERROR INDICATION when receiving the UE RADIO CAPABILTY MATCH REQUEST message. NOTE
The UE RADIO CAPABILTY MATCH REQUEST message is introduced in 3GPP Release 11. The MME informs the eNodeB of the MME's SRVCC capability in the Initial UE Context Setup message. l After the eNodeB obtains the MME's SRVCC capability, it also considers the MME's capability while determining the preceding conditions. Otherwise, the eNodeB replies to the eNodeB that the VoLTE mobility cannot be ensured. l If the eNodeB is not informed of the MME's SRVCC capability, for example, the UE RADIO CAPABILTY MATCH REQUEST message arrives at the eNodeB earlier than the Initial UE Context Setup message, the eNodeB does not consider the MME's capability while determining UE voice service continuity.
3.2.2 VoLTE-Prohibited Scenario The E-UTRAN supports VoLTE after the IMS is deployed. However, a non-VoLTE solution (such as CSFB) is used in the following scenarios because VoLTE is not appropriate for these scenarios: l
Transmission delay is large. Voice services have high requirements on end-to-end delay. Figure 3-5 shows the relationship between end-to-end delay and perceived voice quality, as per ITU-T Recommendation G.114. As shown in the figure, the end-to-end delay threshold to achieve very satisfied user experience is 200 ms, and that to achieve satisfied user experience is 275 ms. That is, VoLTE users become dissatisfied on voice quality when the end-to-end delay exceeds 275 ms. The recommended packet delay budget for the Uu interface is 80 ms, as per Table 6.1.7: Standardized QCI characteristics in section 6.1.7.2 "Standardized QCI characteristics" of 3GPP TS 23.203. The delay budget between the
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
19
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
EPC and eNodeB is 20 ms. If the transmission delay between the EPC and eNodeB is greater than 20 ms, voice quality may not be guaranteed after VoLTE is deployed on the eNodeB. Figure 3-5 Relationship between delay and voice quality
l
Voice services are not allowed on certain frequency bands. Certain operators expect that some frequency bands such as LTE TDD bands do not serve voice service but serve only data services.
MMEs are required in the preceding scenarios to prohibit VoLTE in certain areas. Operators can allocate dedicated tracking area identities (TAIs) to regions. After setting dedicated TAIs on the MME, areas in such scenarios use CSFB instead of VoLTE. During the Attach and tracking area update (TAU), UEs negotiate or re-negotiate with the MME about voice policies. Voice policy negotiation between the UE and the MME is transparent to the eNodeB. You can turn off the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch for eNodeBs with dedicated TAIs working in the preceding scenarios. For eNodeBs with non-dedicated TAIs, you can select the VoipHoControlSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter and configure the VoLTE handover blacklist in the EutranVoipHoBlkList MO. This prevents UEs performing voice services from handing over to these eNodeBs or reestablished on the eNodeBs. After the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch is turned off and VoLTE is disabled for a specific tracking area on the MME, the statistics about VoLTE-related KPIs such as E-RAB Setup Success Rate (VoIP) become 0. The following is an example. The MCC and MNC of a network are 001 and 02, respectively. In this network, tracking area code (TAC) 1 corresponds to eNodeB A, and the other TACs correspond to eNodeBs B to Z. CSFB is to be used in the area that is labeled TAC 1. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
20
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
The configurations are as follows: 1. 2.
On the MME, configure CSFB for TAC1. On eNodeB A, run the following command: MOD ENODEBALGOSWITCH:EutranVoipSupportSwitch=OFF;
3.
(Optional) On eNodeBs B to Z, perform the following command: MOD ENODEBALGOSWITCH:EutranVoipSupportSwitch=ON;
4.
On eNodeBs B to Z, run the following command: MOD ENODEBALGOSWITCH:HoAlgoSwitch=VoipHoControlSwitch-1;
5.
On eNodeBs B to Z, run the following command: ADD EUTRANVOIPHOBLKLIST: Mcc="001", Mnc="02", Tac=TAC1; NOTE
In the preceding VoLTE-prohibited scenarios, when a UE performing voice services triggers an intraRAT intra-frequency or inter-frequency handover, the eNodeB determines whether to filter out cells in the VoLTE handover blacklist (specified by the EutranVoipHoBlkList MO) depending on the settings of the VoipHoControlSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter. According to current 3GPP specifications, voice policies can be configured only on a TAC basis on the MME. The eNodeB's ENODEBALGOSWITCH.EutranVoipSupportSwitch and ENODEBALGOSWITCH.HoAlgoSwitch.VoipHoControlSwitch are used to support the configuration of TAC-based voice policies on the MME side. For details about the VoLTE handover blacklist and target cell selection procedures for VoLTE handovers, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description. When the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch is turned on, dedicated bearer for services with QCI of 1 can be set up for the eNodeB. When this switch is turned off, dedicated bearer for services with QCI of 1 is not allowed to be set up for the eNodeB.
3.3 Radio Bearer Management 3.3.1 Radio Bearer Setup From the perspective of eNodeBs, voice session setup includes the following procedures: RRC connection setup, QCI 5 radio bearer setup, and QCI 1 radio bearer setup. Figure 3-6 shows the process of setting up a voice session between the calling and called UEs.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
21
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
Figure 3-6 Voice session setup process
The process is as follows: 1.
In the RRC connection setup procedure, a radio connection is set up between a UE and an eNodeB so that the UE can send service requests and data packets to upper-layer NEs.
2.
In the EPS bearer setup (QCI 5) procedure, a QCI 5 radio bearer is set up for signaling exchange between the UE and the IMS.
3.
After the QCI 5 radio bearer is set up, the calling UE and the IMS perform Session Initiation Protocol (SIP) negotiation on the speech codec scheme, IP address, port number, called UE's information, and other information.
4.
In the EPS bearer establishment (QCI 1) procedure, a QCI 1 radio bearer is set up to carry voice packets.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
22
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
NOTE
If VoLTE is determined as the voice solution for a UE according to negotiation with the MME, a QCI 5 radio bearer is set up when the UE enters RRC_CONNECTED mode, irrespective of whether the UE is performing a voice service or not. When ENodeBAlgoSwitch.EutranVoipSupportSwitch is set to OFF(Off), the eNodeB cannot set up QCI 1 radio bearers but can set up QCI 5 radio bearers. If the UE initiates a conversational video service, a radio bearer (QCI 2) is also set up in the preceding procedures. eNodeBs provide the following QCI 1-specific timer settings: ENodeBConnStateTimer.S1MsgWaitingTimerQci1, ENodeBConnStateTimer.X2MessageWaitingTimerQci1, ENodeBConnStateTimer.UuMessageWaitingTimerQci1, RrcConnStateTimer.UeInactiveTimerQci1, and CellStandardQci.TrafficRelDelay. For details about these parameters, see Connection Management Feature Parameter Description.
3.3.2 Radio Bearer QoS Management Radio bearer QoS management for voice services complies with the Policy and Charging Control architecture defined in 3GPP specifications. Figure 3-7 shows the architecture of radio bearer QoS management for voice services. Figure 3-7 Architecture of radio bearer QoS management
The dedicated bearers for voice services perform QoS parameter control based on the dynamic PCC rule as follows: 1.
The IMS (P-CSCF) sends QCI information to the PCRF over the Rx interface.
2.
Based on the received QCI information and subscription information, the PCRF generates a QoS rule (including key QoS parameters, QCI, ARP, GBR, and MBR) and sends the rule to the P-GW over the Gx interface.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
23
eRAN VoLTE Feature Parameter Description
3.
3 Basic VoLTE Functions
Based on the QoS rule sent from the PCRF, the P-GW instructs the S-GW, MME, and eNodeB to set up EPS bearers. Services of different QoS requirements are carried by radio bearers with different QCIs. According to 3GPP specifications, the QCIs for conversational voice, conversational video, and IMS signaling are 1, 2, and 5, respectively. Table 3-1 lists their QoS parameters. QoS parameters are set in StandardQci MOs, and the Radio Link Control (RLC) modes for setting up conversational voice, conversational video, and IMS signaling E-RABs are specified by the RlcPdcpParaGroup.RlcMode parameter. Table 3-1 QoS parameters for conversational voice, conversational video, and IMS signaling QC I
Resource Type
Priorit y
Delay
Packet Loss Rate
Service Type
1
GBR
2
100 ms
10-2
Conversational voice
2
GBR
4
150 ms
10-3
Conversational video
5
Non-GBR
1
100 ms
10-6
IMS signaling
NOTE
A smaller priority value indicates a higher priority.
For details about QCI and RLC mode, see QoS Management Feature Parameter Description.
3.4 Admission and Congestion Control 3.4.1 Overview This section describes how the basic features LBFD-002023 Admission Control and LBFD-002024 Congestion Control work for VoLTE. For details about the two features, see Admission and Congestion Control Feature Parameter Description. The eNodeB performs admission and congestion control for conversational voice (QCI of 1) and IMS signaling (QCI of 5) separately.
3.4.2 Load Monitoring Load monitoring provides decision references for admission and congestion control. The eNodeB monitors various resources in a cell to obtain the usage of physical resource blocks (PRBs), QoS satisfaction rates of GBR services, and resource insufficiency indicators. In this way, the eNodeB can know the current status of a cell.
Conversational Voice (QCI 1) The QoS satisfaction rates for QCI 1 are calculated as follows: Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
24
eRAN VoLTE Feature Parameter Description
l
3 Basic VoLTE Functions
Downlink QoS satisfaction rate Downlink QoS satisfaction rate for QCI 1 services = Sum of downlink QoS satisfaction rates of all VoIP services in the cell/Number of VoIP services in the cell
l
Uplink QoS satisfaction rate Uplink QoS satisfaction rate for QCI 1 services = Sum of uplink QoS satisfaction rates of all VoIP services in the cell/Number of VoIP services in the cell
IMS Signaling (QCI 5) QCI 5 indicates non-GBR services. There is no need to calculate their QoS satisfaction rates.
3.4.3 Admission Control Admission control determines whether to admit a GBR service (new service or handover service) based on the cell load reported by the load monitoring module. The cell load is represented by the PRB usage, QoS satisfaction rates of GBR services, and resource insufficiency indicators. For details, see Admission and Congestion Control Feature Parameter Description.
Conversational Voice (QCI 1) The admission control of GBR services with a QCI of 1is performed based on load-based decisions.
IMS Signaling (QCI 5) Admission control for non-GBR services (QCI 5) is not based on load. If SRS and PUCCH resources are successfully allocated, admits non-GBR services (QCI 5) are directly admitted. NOTE
The allocation of SRS resources needs to be considered during admission control of non-GBR services (QCI 5) only when the eNodeB is configured with the LBBPc. The services can be admitted only after SRS resources are successfully allocated.
The eNodeB directly admits non-GBR services without evaluating the QoS satisfaction rate. When PreemptionSwitch under the CellAlgoSwitch.RacAlgoSwitch parameter is turned on, IMS signaling (QCI 5) cannot be preempted.
3.4.4 Congestion Control When the network is congested, the eNodeB preferentially releases low-priority GBR services to free up resources for other services. For details, see Admission and Congestion Control Feature Parameter Description.
Conversational Voice (QCI 1) The eNodeB monitors PRB usage and QoS satisfaction rate to evaluate load status. When the eNodeB determines that a cell is congested, the eNodeB rejects service access requests and triggers congestion control to decrease load. The congestion threshold is specified the CellRacThd.Qci1CongThd parameter. For details about how to set this parameter, see Admission and Congestion Control Feature Parameter Description. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
25
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
IMS Signaling (QCI 5) N/A
3.5 Dynamic Scheduling and Power Control 3.5.1 Dynamic Scheduling This section describes how the optional feature LOFD-00101502 Dynamic Scheduling works for VoLTE. For details about the principles and engineering guidelines of dynamic scheduling, see Scheduling Feature Parameter Description.
Overview Voice services have demanding requirements on delay. Therefore, the Huawei scheduler optimizes the handling of voice service priorities to ensure voice service QoS. When VoLTE is deployed, it is recommended that the enhanced proportional fair (EPF) scheduling policy be used in the uplink and downlink. That is: l
The CELLULSCHALGO.UlschStrategy parameter is set to ULSCH_STRATEGY_EPF.
l
The CELLDLSCHALGO.DlschStrategy parameter is set to DLSCH_PRI_TYPE_EPF.
On commercial LTE networks, the EPF scheduling policy is used in the uplink and downlink by default. For details about dynamic scheduling for voice services, see Scheduling Feature Parameter Description.
Uplink Dynamic Scheduling When uplink dynamic scheduling uses the enhanced proportional fair (EPF) algorithm, the priority of conversational voice (QCI 1) is lower than the priorities of data retransmitted using HARQ, signaling radio bearer 1 (SRB1), SRB2, and IMS signaling (QCI 5), but higher than the priorities of other initially transmitted data. It is recommended that the UlLast2RetransSchOptSwitch option of the CellAlgoSwitch.UlSchSwitch parameter be selected when dynamic scheduling is used and there are voice services. Selecting this option decreases the packet loss rate of voice services and improves the user experience on voice services. Uplink voice preallocation is introduced to reduce the delay of voice services. When the number of UEs in a cell exceeds 50, the eNodeB can preallocate available uplink resources to only UEs performing voice services. When the number of UEs in a cell is less than or equal to 50, the eNodeB retains the existing uplink preallocation or uplink smart preallocation mechanism. For details, see Scheduling Feature Parameter Description. Uplink voice preallocation is controlled by the UlVoipPreAllocationSwtich option of the CELLULSCHALGO.UlEnhencedVoipSchSw parameter.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
26
eRAN VoLTE Feature Parameter Description
3 Basic VoLTE Functions
Downlink Dynamic Scheduling When dynamic scheduling is used, the scheduling priority is related to whether the LOFD-001109 DL Non-GBR Packet Bundling feature is enabled: l
If the LOFD-001109 DL Non-GBR Packet Bundling feature is not enabled: When the EPF downlink scheduling algorithm is used, the priority for scheduling voice packets (QCI of 1) is lower than that for scheduling common control messages, user-level control messages, IMS signaling (QCI of 5), HARQ retransmission data, and RLC AM status report. However, the priority for scheduling voice packets (QCI of 1) is higher than that for scheduling initial transmission data.
l
If the LOFD-001109 DL Non-GBR Packet Bundling feature is enabled: The priority for scheduling voice packets (QCI of 1) is no longer higher than that for scheduling initial transmission data. Instead, the eNodeB sorts overall priorities.
When dynamic scheduling is used, the modulation and coding scheme (MCS) selection policy is related to the value for the VoipTbsBasedMcsSelSwitch option of the CellAlgoSwitch.DlSchSwitch parameter. l
When this option is selected, the eNodeB checks the number of online subscribers and IBLER and then determines whether to apply the TBS-based MCS selection function to voice services. TBS is short for transport block size. HARQ retransmission and user delay are reduced if the function takes effect on voice services.
l
When this option is deselected, the eNodeB determines the MCS for voice services based on the downlink CQI adjustment algorithm. For details about the downlink CQI adjustment algorithm, see Scheduling Feature Parameter Description.
When dynamic scheduling is used for voice service, it is recommended that the DlRetxTbsIndexAdjOptSwitch of the CELLALGOSWITCH.CqiAdjAlgoSwitch parameter be turned on to reduce the voice packet loss rate and improve voice user experience. For details about this switch, see Scheduling Feature Parameter Description.
3.5.2 Power Control in Dynamic Scheduling Power control policies for voice services in dynamic scheduling are the same as those for data services. For details about voice service power control policies when dynamic scheduling is used for voice services, see Power Control Feature Parameter Description.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
27
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
4
Enhanced VoLTE Features
Operators can enable features described in this chapter to improve VoLTE performance such as capacity and coverage.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
28
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
4.1 Capacity Enhancement The following features can be enabled to increase capacity for voice services: l
Semi-persistent scheduling and power control When the capacity is low due to high PDCCH overheads, these features can be used to reduce PDCCH overheads and therefore increase the maximum number of VoLTE users or the throughput of data services (provided that the number of VoLTE users remains unchanged).
l
Uplink delay-based dynamic scheduling When there are too many VoLTE users, this feature can be used to improve the performance of cell edge users (CEUs) by sacrificing the performance of cell center users (CCUs) and increase the proportion of satisfied VoLTE users.
l
ROHC By compressing the headers of voice packets, this feature reduces air interface overheads and increase the maximum number of VoLTE users or the throughput of data services (provided that the number of VoLTE users remains unchanged).
4.1.1 Semi-Persistent Scheduling and Power Control 4.1.1.1 Semi-Persistent Scheduling This section describes the LOFD-001016 VoIP Semi-persistent Scheduling feature.
Introduction When dynamic scheduling is used for voice services, time-frequency resource or MCS is updated through the PDCCH every 20 ms. This consumes a large number of PDCCH resources. Figure 4-1 shows the resource allocation for dynamic scheduling. Figure 4-1 Resource allocation for dynamic scheduling
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
29
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
Huawei introduces the VoLTE semi-persistent scheduling feature for small-packet services that are periodically transmitted such as VoLTE. Before entering talk spurts, the eNodeB allocates fixed resources to UEs through the PDCCH message. Before exiting talk spurts or releasing resources, the UEs do not need to apply for resource allocation from the PDCCH again, thereby saving PDCCH resources. Figure 4-2 shows the resource allocation for semipersistent scheduling. Figure 4-2 Resource allocation for semi-persistent scheduling
The eNodeB configures semi-persistent scheduling parameters for UEs supporting semipersistent scheduling in the RRC Connection Reconfiguration message during DRB setup for QCI of 1. The eNodeB activates UL or DL semi-persistent scheduling for UEs when UEs meet the UL or DL semi-persistent scheduling activation conditions. The eNodeB instructs UEs to activate UL or DL semi-persistent scheduling through the PDCCH Order notification. For details about the PDCCH Order format, see section 9.2 "PDCCH/EPDCCH validation for semi-persistent scheduling" in 3GPP TS 36.213 V12.3.0. The semi-persistent scheduling interval is 20 ms and applies only to services with QCI of 1 and PTT QCI services.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
30
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
Effect Period Figure 4-3 Semi-persistent scheduling effect period
The VoLTE voice status is classified into instantaneous state, talk spurt, and silent period. In talk spurt, uplink or downlink semi-persistent scheduling takes effect when all the following conditions are met: l
The following options are selected: –
The SpsSchSwitch option of the CELLALGOSWITCH.UlSchSwitch parameter
–
The SpsSchSwitch option of the CELLALGOSWITCH.DlSchSwitch parameter.
l
The UE supports semi-persistent scheduling.
l
The UE performing voice services is in uplink or downlink talk spurts.
l
The uplink or downlink for the UE has only one dedicated bearer for services with QCI of 1. For the uplink, there is no data transmission on the default 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 to supplement semi-persistent scheduling during talk spurts: l
Transmission of large packets, such as channel-associated signaling or uncompressed packets generated when the ROHC feature updates contexts
l
Downlink semi-persistent retransmission
l
Uplink semi-persistent adaptive retransmission NOTE
When the UE uses semi-persistent scheduling, the highest MCS index is only 15.
Uplink Semi-Persistent Scheduling During semi-persistent scheduling, the eNodeB determines the modulation and coding scheme (MCS) and the number of PRBs based on the following items: Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
31
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
l
Voice packet size (ROHC disabled) or size of compressed voice packets (ROHC enabled)
l
Wideband signal to interference plus noise ratio (SINR)
After semi-persistent scheduling is activated, the UE periodically sends data and the eNodeB periodically receives data using the semi-persistently allocated resources. In addition, the eNodeB checks whether the MCS allocated in semi-persistent scheduling matches the current channel status. If the MCS does not match the current channel status, the eNodeB activates semi-persistent scheduling again. After the eNodeB triggers a UE to enter uplink semi-persistent scheduling, the logicalChannelSR-Mask-r9 IE in the RRC Reconfiguration message instructs the UE not to send scheduling requests over the radio bearers for QCI of 1. This reduces UE power consumption. The CellULSchAlgo.SrMaskSwitch parameter controls this function. It is recommended that both this function and uplink semi-persistent scheduling be enabled. This function takes effect only on UEs that comply with 3GPP Release 9 or later. When the number of empty packets received by the eNodeB in semi-persistent scheduling exceeds the value of CellUlschAlgo.SpsRelThd, the eNodeB automatically releases semipersistently allocated resources.
Downlink Semi-Persistent Scheduling Downlink data transmitted in semi-persistent scheduling mode has a lower priority than common control (such as broadcast and paging) information but a higher priority than UEspecific control information and user-plane data. The eNodeB periodically sends data and the UE periodically receives data using the semi-persistently allocated resources. During semi-persistent scheduling, the eNodeB determines the MCS and the number of PRBs based on the following items: l
Voice packet size (ROHC disabled) or size of compressed voice packets (ROHC enabled)
l
Wideband CQI
The UE and eNodeB then receive and send data on the allocated resources. After semi-persistent scheduling is activated, the eNodeB checks whether the MCS allocated in semi-persistent scheduling matches the current channel status. If the MCS does not match the current channel status, the eNodeB activates semi-persistent scheduling again. According to 3GPP TS 36.321 and 3GPP TS 36.331, the eNodeB reserves HARQ processes for downlink semi-persistent scheduling while configuring semi-persistent scheduling for UEs. When the eNodeB configures semi-persistent scheduling for UEs, the PUCCH requires available semi-persistent code channel. Otherwise, the eNodeB does not configure semipersistent scheduling for UEs.
4.1.1.2 Power Control in Semi-Persistent Scheduling This section describes voice service power control policies when semi-persistent scheduling is used for VoLTE. For details about power control, see Power Control Feature Parameter Description. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
32
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
Power Control in Uplink Semi-Persistent Scheduling When semi-persistent scheduling is used for VoLTE in the uplink, closed-loop power control for the physical uplink shared channel (PUSCH) can be enabled or disabled by setting the CloseLoopSpsSwitch option of the CellAlgoSwitch.UlPcAlgoSwitch parameter. l
If the CloseLoopSpsSwitch option is selected, the eNodeB adjusts transmit power for the PUSCH based on the measured IBLER of voice services.
l
If the CloseLoopSpsSwitch option is deselected, the eNodeB uses open-loop (not closed-loop) power control for the PUSCH.
Power Control in Downlink Semi-Persistent Scheduling When semi-persistent scheduling is used for VoLTE in the downlink, power control for the PDSCH can be enabled or disabled by setting the PdschSpsPcSwitch option of the CellAlgoSwitch.DlPcAlgoSwitch parameter. l
If the PdschSpsPcSwitch option is selected, the eNodeB periodically adjusts the PDSCH transmit power for UEs based on the measured IBLER.
l
If the PdschSpsPcSwitch option is deselected, power control for the PDSCH in semipersistent scheduling is not used. Instead, the eNodeB transmit power is evenly shared by each RB.
4.1.2 ROHC This section describes how the optional feature LOFD-001017 RObust Header Compression (ROHC) works for VoLTE. For details about this feature, see ROHC Feature Parameter Description. ROHC provides an efficient header compression mechanism for data packets transmitted on radio links to solve the problems of high bit error rates (BERs) and long round trip time (RTT). ROHC helps reduce header overheads, lower the packet loss rate, and shorten response time. In the current version, ROHC is used to compress the headers of only voice packets (QCI of 1 and PTT QCI services), as shown in Figure 4-4. ROHC reduces the packet size and physical resource block (PRB) overheads. When PRBs are insufficient, ROHC helps increase system capacity. Figure 4-4 ROHC for VoLTE
After deploying VoLTE, operators can enable or disable ROHC by setting the PdcpRohcPara.RohcSwitch parameter. ROHC is an extensible framework consisting of Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
33
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
different profiles for data streams compliant with different protocols. Profiles define the compression modes for streams with different types of protocol headers. Voice services use profiles 0x0001 and 0x0002. The ROHC compression efficiency varies with the ROHC operating mode and variations in the dynamic part of packet headers at the application layer. A header can be compressed to a size as small as 1 byte, which efficiently reduces the voice packet size.
4.2 Coverage Improvement Operators can enable the following features to improve voice service coverage in poor coverage scenarios: l
TTI Bundling
l
ROHC
l
Uplink RLC segmentation enhancement
4.2.1 TTI Bundling This section describes the principles of the optional feature LOFD-001048 TTI Bundling and how this feature works for VoLTE.
4.2.1.1 Overview TTI bundling enables a data block to be transmitted in four consecutive TTIs, which are bound together and treated as the same resource. Different HARQ redundancy versions of the same data block are transmitted in different TTIs. TTI bundling makes full use of HARQ combining gains and reduces the number of retransmissions and RTT. When the UE's channel quality is poor and transmit power is limited, TTI bundling increases the cell edge coverage of the PUSCH by about 1 dB. The gains produced by this feature can be observed when voice quality is maintained at a certain level, for example, when the mean opinion score (MOS) is 3. The TtiBundlingSwitch option of the CellAlgoSwitch.UlSchSwitch parameter controls whether to enable TTI bundling. When this option is selected, the eNodeB determines whether to activate TTI bundling based on the channel quality. After activating TTI bundling, the eNodeB determines the number of PRBs and selects an MCS based on the channel quality and the amount of data to be transmitted. According to section 8.6.1 "Modulation order and redundancy version determination" in 3GPP TS 36.213 V10.1.0, when TTI bundling is enabled, the resource allocation size is restricted to a maximum of three PRBs and the modulation scheme must be QPSK. Therefore, the selected MCS index cannot be greater than 10. After TTI bundling is enabled, the maximum available TBS is as large as 504 bits. Voice services are delay-sensitive. If higherlayer data is not transmitted within the specified delay budget, voice quality deteriorates. To prevent this, TTI bundling is disabled when a G.711-defined high speech codec rate is used.
4.2.1.2 Principles Entry into the TTI Bundling State In eRAN8.1, the CELLULSCHALGO.TtiBundlingTriggerStrategy parameter is introduced. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
34
eRAN VoLTE Feature Parameter Description
l
4 Enhanced VoLTE Features
When the TtiBundlingTriggerStrategy parameter is set to SERVICE_VOIP(SERVICE_VOIP), TTI bundling applies to only VoLTE. Under this parameter setting, the conditions for entering the TTI bundling state are as follows: –
The TtiBundlingSwitch of the eNodeB is turned on.
–
The UE supports TTI bundling.
–
The UE has only one QCI 1 dedicated bearer and stays in the talk spurts state. In addition, the UE does not have data to transmit on the default bearer.
–
The UL power of the UE is limited, and the number of PRBs is less than or equal to 3.
–
The measured SINR is less than the target SINR for multiple consecutive times. The number of consecutive times is specified by the CellUlschAlgo.StatisticNumThdForTtibTrig.
If the UE meets all these conditions, the eNodeB sends the UE an RRC Connection Reconfiguration message, instructing the UE to enter the TTI bundling state. l
When the TtiBundlingTriggerStrategy parameter is set to SERVICE_MULTIAPP(SERVICE_MULTIAPP), TTI bundling can apply to VoLTE or a combination of VoLTE and data. Under this parameter setting, the conditions for entering the TTI bundling state are as follows: –
The TtiBundlingSwitch of the eNodeB is turned on.
–
The UE supports TTI bundling.
–
The UE has a QCI 1 dedicated bearer.
–
The UL power of the UE is limited, and the number of PRBs is less than or equal to 3.
–
The measured SINR is less than the target SINR for multiple consecutive times. The number of consecutive times is specified by the CellUlschAlgo.StatisticNumThdForTtibTrig.
If the UE meets all these conditions, the eNodeB sends the UE an RRC Connection Reconfiguration message, instructing the UE to enter the TTI bundling state. The processing in versions earlier than eRAN8.1 is the same as that when the TtiBundlingTriggerStrategy parameter is set to SERVICE_VOIP(SERVICE_VOIP) in eRAN8.1.
Data Block Transmission For the UE in the TTI bundling state, the eNodeB determines the number of PRBs and MCS based on channel quality and the amount of data to transmit. Then, the eNodeB transmits data blocks. As shown in Figure 4-5 , the UE transmits identical data within four consecutive TTIs in a bundle and performs HARQ retransmission also within four TTIs in a bundle. The retransmission operates in synchronous non-adaptive mode. The HARQ retransmission interval is changed from 8 TTIs (Normal HARQ RTT) to 16 TTIs (Bundle HARQ RTT). Take the transmission of a data block as an example. Assume that the UE transmits the data block in a bundle of TTIs, among which the last TTI is numbered N. The eNodeB sends an ACK or NACK as feedback to the UE in the (N + 4)th TTI. Based on the feedback, the UE determines whether a retransmission is required. If it is required, the UE retransmits the data block in the (N + 13)th through (N + 16)th TTIs. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
35
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
When the UE is in the TTI bundling state, the maximum number of uplink HARQ retransmissions is specified by the CellUlschAlgo.TtiBundlingHarqMaxTxNum parameter. Figure 4-5 TTI bundling
In the TTI bundling state, the number of RLC segments of a voice packet cannot be greater than the value specified by the CellUlschAlgo.TtiBundlingRlcMaxSegNum. The number is 4 in Figure 4-6. Figure 4-6 Collaboration between TTI bundling and RLC segmentation
When the UE is located at the cell edge, RLC segmentation in collaboration with TTI bundling produces fewer RLC segments than pure RLC segmentation, reducing PDCCH overheads.
Exit from TTI Bundling When the measured SINR is greater than the sum of the target SINR and the CellUlschAlgo.HystToExitTtiBundling parameter value for multiple consecutive times, the eNodeB instructs the UE to exit the TTI bundling state through an RRC Connection Reconfiguration message. The number of consecutive times is specified by the StatisticNumThdForTtibExit parameter. The eNodeB does not instruct the UE to exit the TTI bundling state even when the UE has data to transmit on the default bearer, needs to set up a new dedicated bearer, or stops the voice service (QCI 1). The eNodeB instructs the UE to exit the TTI bundling state when the UE meets the exit conditions, experiences handover or service drop, or needs to reestablish a new connection.
4.2.2 ROHC This section describes how the optional feature LOFD-001017 RObust Header Compression (ROHC) works for VoLTE. For details about this feature, see ROHC Feature Parameter Description. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
36
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
ROHC can compress the RTP, UDP, or IP header of a voice packet, thereby reducing the size of the entire packet. ROHC results in a higher probability of correctly transmitting voice packets with fewer segments and enhances the edge coverage for voice services.
4.2.3 Uplink RLC Segmentation Enhancement This section describes how uplink RLC segmentation enhancement works for VoLTE. The number of Uplink RLC segments is dependent on the TBS determined by UL scheduling. The smaller the TBS, the large the number of uplink RLC segments. When channel quality is poor and UL power is limited, a small TBS results in a large number of uplink RLC segments, which causes: l
Long delay of voice packets
l
Uplink voice packet loss (because voice packets wait in the UE buffer so long that the packet discard timer expires)
l
Large overhead of RLC and MAC headers
l
Large consumption of control channel elements (CCEs) and resource blocks (RBs) by UL dynamic scheduling of VoLTE services
Uplink RLC segmentation enhancement restricts the TBS in UL dynamic scheduling to control the number of uplink RLC segments for voice packets. This restriction improves voice quality when channel quality is poor. The CELLULSCHALGO.UlVoipRlcMaxSegNum is introduced to control the maximum number of uplink RLC segments for UEs not in the TTI bundling state. l
When the number of uplink RLC segments is less than or equal to the CELLULSCHALGO.UlVoipRlcMaxSegNum parameter value, the number is not restricted.
l
When the number of uplink RLC segments is greater than the CELLULSCHALGO.UlVoipRlcMaxSegNum parameter value, the number is restricted. Based on the voice packet size and the configured maximum number of RLC segments, a minimum TBS is guaranteed in UL dynamic scheduling so that the number of uplink RLC segments decreases to this maximum number.
This function takes effect when all the following conditions are met: l
The CELLULSCHALGO.UlVoipRlcMaxSegNum parameter is set to a none-zero value.
l
The GLOBALPROCSWITCH.LcgProfile parameter is set to LCG_PROFILE_0 or LCG_PROFILE_2.
This function does not take effect when one of the following conditions is met: l
The CELLULSCHALGO.UlVoipRlcMaxSegNum parameter is set to 0.
l
The GLOBALPROCSWITCH.LcgProfile parameter is set to LCG_PROFILE_1.
l
The UE enters the TTI bundling state. NOTE
This function applies only to services with QCI of 1. When the CELLULSCHALGO.UlVoipRlcMaxSegNum parameter is set to the recommended value, this function increases the MOS of VoIP users who do not support TTI bundling by about 0.3 in uplink weak-coverage areas.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
37
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
4.3 Quality Improvement 4.3.1 Voice Characteristic Awareness Scheduling This section describes LOFD-081229 Voice Characteristic Awareness Scheduling, involving uplink delay-based dynamic scheduling, estimation of uplink VoLTE volume for dynamic scheduling, and independent configuration for voice inactivity timer.
Uplink Delay-based Dynamic Scheduling For uplink delay-based dynamic scheduling, the eNodeB prioritizes voice packets based on their waiting times. Sorting scheduling priorities based on delay for voice services brings balanced scheduling sequence. This helps improve voice quality. Specifically, voice quality improves for UEs far from center with poor channel quality. This feature increases the user satisfaction rate of UEs with voice services in scenarios where voice service load is high. Figure 4-7 shows the difference before and after uplink delay-based dynamic scheduling is enabled. Figure 4-7 Difference before and after uplink delay-based dynamic scheduling is enabled.
A longer wait time indicates a higher scheduling priority. When the CELLULSCHALGO.UlDelaySchStrategy parameter is set to VOIP_DELAYSCH(VoIP Service Delay Scheduling), uplink delay-based dynamic scheduling for VoLTE is used.
Uplink VoLTE Volume Estimation for Dynamic Scheduling The eNodeB can obtain the accurate downlink service volume but cannot obtain the accurate uplink service volume. Therefore, uplink VoLTE volume estimation for dynamic scheduling is introduced to allow the eNodeB to perform the uplink estimation based on the VoLTE model and uplink scheduling intervals so that scheduling can be completed in one time: l
During talk spurts, the eNodeB estimates the number of voice packets in the UE buffer based on their uplink scheduling intervals and then calculates the volume of voice packets based on the size of a voice packet.
l
During silent periods, the eNodeB takes the size of a voice packet as the uplink VoLTE volume for dynamic scheduling.
Uplink VoLTE volume estimation for dynamic scheduling makes the calculation of uplink service volume more accurate and therefore shortens voice packet delays. This function can Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
38
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
improve voice quality when the cell is heavily loaded and DRX is enabled. Figure 4-8 shows the principles. Figure 4-8 Uplink VoLTE Volume Estimation for Dynamic Scheduling
Uplink VoLTE volume estimation for dynamic scheduling is controlled by the UlVoLTEDataSizeEstSwitch option of the CELLULSCHALGO.UlEnhencedVoipSchSw parameter.
Independent Configurations for the UE Inactivity Timer for Voice Services When a called UE does not answer the call, the calling UE is released after the UE inactivity timer expires. This may interrupt the session. l
In dynamic DRX scenarios, the RrcConnStateTimer.UeInactivityTimerDynDrx parameter specifies the length of the UE inactivity timer. The default and recommended values of this parameter are large and therefore do not cause call setup failures in the preceding scenario. In other scenarios, with independent configuration for voice inactivity timer, the UEs can distinguish voice and non-voice scenarios. That is, the length of the UE inactivity timer can be independently configured to avoid the preceding negative impact. When the CELLALGOSWITCH.UEInactiveTimerQCI1Switch parameter is set to ON(On), the RrcConnStateTimer.UeInactiveTimerQci1 parameter takes effect. Otherwise, the RrcConnStateTimer.UeInactiveTimerQci1 parameter does not take effect. It is recommended that the value of the RrcConnStateTimer.UeInactiveTimerQci1 parameter be greater than the active connection release timer length when the called party of the core network does not respond.
4.3.2 Uplink Compensation Scheduling This section describes LBFD-081104 UL Compensation Scheduling. Sending uplink data is dependent on the scheduling requests (SRs) reported by UEs. If an eNodeB experiences missing SR detection, the eNodeB may not perform scheduling in a Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
39
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
timely manner. This may extend the voice packet waiting delay or cause timeout-triggered packet loss. Figure 4-9 shows the situation before uplink compensation scheduling is enabled. Figure 4-9 Uplink compensation scheduling not enabled
Uplink compensation scheduling is a technique in which the eNodeB identifies voice users and, for each voice user, measures the duration in which the user is not scheduled in the uplink. If the duration reaches a threshold, the eNodeB sends a UL Grant to the UE to ensure that uplink voice packets can be timely transmitted. This way, this feature shortens the waiting time of voice packets and reduces the number of packets discarded because of the expiry of PDCP Discard Timer. Figure 4-10 shows the situation after uplink compensation scheduling is enabled. Figure 4-10 Uplink compensation scheduling enabled
This feature is controlled by the UlVoipSchOptSwitch option of the CELLULSCHALGO.UlEnhencedVoipSchSw parameter.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
40
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
4.3.3 Voice-Specific AMC This section describes LBFD-081105 Voice-Specific AMC. For details about the principles and engineering guidelines of adaptive modulation and coding (AMC), mainly MCS selection for uplink dynamic scheduling, see Scheduling Feature Parameter Description. The eNodeB adjusts SINRs for UEs to be dynamically scheduled in the uplink based on the configured uplink target IBLER and then preliminarily selects MCSs for the UEs. To reduce the uplink VoLTE packet loss rate and VoLTE packet delay, users can set different target uplink IBLER values for VoLTE and data services. l
The CellUlschAlgo.SinrAdjustTargetIbler parameter specifies the target uplink IBLER value for data services.
l
The CellUlschAlgo. SinrAdjTargetIblerforVoLTE parameter specifies the target uplink IBLER value for VoLTE services. This parameter takes effect only to VoLTE UEs not in the TTI bundling state.
Voice-specific AMC and uplink RLC segmentation enhancement can be enabled simultaneously. Uplink RLC segmentation enhancement takes precedence if its requirements are met.
4.4 Power Saving This section describes how the basic feature LBFD-002017 DRX works for VoLTE. As shown in Figure 4-11, with DRX enabled, UEs enter the sleep state when data is not transmitted, saving UE power. DRX typically applies to services with consecutive small packets that are transmitted periodically, for example, voice services. According to 3GPP TS 23.203 and section A.2.1.4 "System performance metrics" in 3GPP TS 36.814, a 50 to 80 ms delay budget is reserved for services with QCI of 1 in the Uu interface and the send interval for voice frames is 20 ms. Therefore, the DRX cycle must be set to 20 ms or 40 ms, considering the retransmission time. In this situation, setting DRX cycle to a short value for voice services does not provide much gain. Therefore, it is recommended that the short DRX cycle be disabled when configuring DRX parameter for services with QCI of 1. Similar to the default bearer for a data service, the default bearer for a VoLTE service (that is, the signaling bearer [QCI 5]) always exists as long as the UE is in RRC_CONNECTED mode, regardless of whether the UE has a QCI 1 voice bearer. Therefore, it is recommended that the DRX parameters for QCI 5 be set to the same values as those for a default bearer used in a data service. In addition, as a long DRX cycle leads to a long delay for setting up a QCI 1 voice bearer, it is recommended that the long DRX cycle for QCI 5 be less than or equal to 320 ms to provide fast access experience for VoLTE users. The DRX.DrxAlgSwitch parameter specifies whether to enable DRX.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
41
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
Figure 4-11 DRX working for VoLTE
Enabling DRX for QCI 1 can reduce the battery consumption on voice services, but at the same time it affects voice quality, for example, the packet loss rate increases. For details, see DRX and Signaling Feature Parameter Description. NOTE
False detection of the PDCCH may cause voice packet loss, due to which there is a low probability of voice quality deterioration. Preallocation can be used to reduce the impact of false detection. For details about how DRX works with preallocation, see DRX and Signaling Control Feature Parameter Description.
4.5 Mobility Management 4.5.1 Overview This section describes the mobility of voice services. It is recommended that coverage-based intra-RAT and inter-RAT handovers for voice services be turned on by default to ensure the continuity of voice services. Voice and data service handovers are classified into intra-frequency, inter-frequency, and inter-RAT handovers. Their handover procedures are the same. However, certain handover parameters can be configured according to the QCI. When UEs set up bearers for different QCIs during coverage-based, distance-based, and UL-quality-based handovers, the handover parameters with high priority are used as the handover parameters. For details about handovers caused by other reasons, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description and Inter-RAT Mobility Management in Connected Mode Feature Parameter Description. The QCI priority is specified by the CellStandardQci.QciPriorityForHo parameter. A smaller value of this parameter indicates a higher priority. If the QCI priority configurations (indicated by the CellStandardQci.QciPriorityForHo parameter) are the same, the eNodeB selects handover parameters for the UE depending on the QCI priority configurations in 3GPP specifications. Handover parameter with high priority is used as the handover parameter of the UE. For details, see section 6.1.7 "Standardized QoS characteristics" in 3GPP TS 23.203 V10.3.0.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
42
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
NOTE
VoLTE is generally deployed in existing LTE networks, which are data networks. Mobility parameters in existing LTE networks have been optimized constantly and can satisfy the KPI requirements of data services. The QoS requirements differ depending on voice and data services. It is recommended that inter-frequency or inter-RAT mobility parameters separately configured for voice and data services. For data services, the interfrequency or inter-RAT mobility parameters optimized in the existing network are recommended. For voice services, the default inter-frequency or inter-RAT mobility parameters are recommended. The preceding recommendations minimize the impact on the KPIs of data services in future network optimization on VoLTE services. For intra-frequency mobility, relative thresholds are used and can be separately configured for voice and data services. However, separate configurations are not recommended. Like the default bearer for a data service, the signaling bearer (QCI 5)for a VoLTE service always exists as long as the UE is in RRC_CONNECTED mode. Therefore, mobility parameters for QCI 5 can be set to the same values as those for the default bearer used in a data service.
4.5.2 Intra-Frequency Handover This section describes the handover parameters that are set based on QCIs in different intrafrequency handover scenarios. These parameters are as follows: l
IntraFreqHOGroup.IntraFreqHoA3Hyst
l
IntraFreqHOGroup.IntraFreqHoA3Offset
l
IntraFreqHOGroup.IntraFreqHoA3TimeToTrig
For details about intra-frequency handovers, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
4.5.3 Inter-Frequency Handover This section describes the handover parameters that are set based on QCIs in different interfrequency handover scenarios. For details about intra-frequency handovers, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
Coverage-based Inter-Frequency Handover The following handover parameters can be configured based on QCIs: l
InterFreqHoGroup.InterFreqHoA1A2Hyst
l
InterFreqHoGroup.InterFreqHoA1A2TimeToTrig
l
InterFreqHoGroup.InterFreqHoA1ThdRsrp
l
InterFreqHoGroup.InterFreqHoA1ThdRsrq
l
InterFreqHoGroup.InterFreqHoA2ThdRsrp
l
InterFreqHoGroup.InterFreqHoA2ThdRsrq
l
InterFreqHoGroup.InterFreqHoA4Hyst
l
InterFreqHoGroup.InterFreqHoA4ThdRsrp
l
InterFreqHoGroup.InterFreqHoA4ThdRsrq
l
InterFreqHoGroup.InterFreqHoA4TimeToTrig
l
InterFreqHoGroup.InterFreqHoA3Offset
l
InterFreqHoGroup.A3InterFreqHoA1ThdRsrp
l
InterFreqHoGroup.A3InterFreqHoA2ThdRsrp
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
43
eRAN VoLTE Feature Parameter Description
l
InterFreqHoGroup.InterFreqHoA5Thd1Rsrp
l
InterFreqHoGroup.InterFreqHoA5Thd1Rsrq
4 Enhanced VoLTE Features
Service-based Inter-Frequency Handover It is recommended that service-based inter-frequency handovers be used in inter-frequency co-coverage scenarios. The following handover parameters can be configured based on QCIs: l
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp
l
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrq
If operators require that service-based inter-frequency handovers be performed on voice services, that is, services with QCI of 1 be preferentially set up on a certain frequency, the following handover policies must be configured: l
Set the handover policy ServiceIfHoCfgGroup.InterFreqHoState of ServiceIfDlEarfcnGrp.DlEarfcn to PERMIT_HO. NOTE
When a UE initiates a voice service, the eNodeB delivers the A4 measurement configuration to the UE, instructing the UE to measure the frequency identified by the ServiceIfDlEarfcnGrp.DlEarfcn parameter.
l
Set the CnOperatorStandardQci.Qci parameter to configure the mapping between the inter-frequency handover frequency policy and services with a QCI of 1.
l
Set the CellStandardQci.QciPriorityForHo parameter to configure the highest handover priority for QCI 1.
l
It is recommended that initial planning and configuration be performed on neighboring cells on frequencies that carry only VoLTE services.
Distance-based Inter-Frequency Handover The following handover parameters can be configured based on QCIs: l
InterFreqHoGroup.InterFreqHoA4ThdRsrp
l
InterFreqHoGroup.InterFreqHoA4ThdRsrq
UL-Quality-based Inter-Frequency Handover Similar to coverage-based inter-frequency handover, UL-quality-based inter-frequency handover uses certain parameters that can be specified based on QCIs. For details, see Coverage-based Inter-Frequency Handover.
Frequency-Priority-based Inter-Frequency Handover The following handover parameters related to event A1 and event A2 can be separately configured based on QCIs: l
InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrp
l
InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrq
l
InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrp
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
44
eRAN VoLTE Feature Parameter Description
l
4 Enhanced VoLTE Features
InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrq
Similar to service-based inter-frequency handover, frequency-priority-based inter-frequency handover uses certain A4-related parameters that can be specified based on QCIs. For details, see Service-based Inter-Frequency Handover.
4.5.4 Inter-RAT Handover 4.5.4.1 Handover Type This section describes the handover parameters that are set based on QCIs in different interRAT handover scenarios. For details about inter-RAT handovers, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
Coverage-based Inter-RAT Handover The following common inter-RAT handover parameters can be configured based on QCIs: l
InterRatHoCommGroup.InterRatHoA1A2Hyst
l
InterRatHoCommGroup.InterRatHoA1A2TimeToTrig
l
InterRatHoCommGroup.InterRatHoA1ThdRsrp
l
InterRatHoCommGroup.InterRatHoA1ThdRsrq
l
InterRatHoCommGroup.InterRatHoA2ThdRsrp
l
InterRatHoCommGroup.InterRatHoA2ThdRsrq
The following handover parameters can be configured based on QCIs for each RAT. Table 4-1 Parameters related to coverage-based inter-RAT handover Target RAT
Parameter ID
UTRAN
l InterRatHoUtranGroup.InterRatHoUtranB1ThdEcn0 l InterRatHoUtranGroup.InterRatHoUtranB1ThdRscp l InterRatHoUtranGroup.InterRatHoUtranB1Hyst l InterRatHoUtranGroup.InterRatHoUtranB1TimeToTrig l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0 l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRscp
GERAN
l InterRatHoGeranGroup.InterRatHoGeranB1Hyst l InterRatHoGeranGroup.InterRatHoGeranB1Thd l InterRatHoGeranGroup.InterRatHoGeranB1TimeToTrig l InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd
CDMA 1x RTT
l InterRatHoCdma1XrttGroup.InterRatHoCdmaB1Hyst l InterRatHoCdma1XrttGroup.InterRatHoCdmaB1ThdPs l InterRatHoCdma1XrttGroup.InterRatHoCdmaB1TimeToTrig l InterRatHoCdma1XrttGroup.LdSvBasedHoCdmaB1ThdPs
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
45
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
Target RAT
Parameter ID
CDMA HRPD
l InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1Hyst l InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1ThdPs l InterRatHOCdmaHrpdGroup.InterRatHoCdmaB1TimeToTrig l InterRatHOCdmaHrpdGroup.LdSvBasedHoCdmaB1ThdPs l InterRatHOCdmaHrpdGroup.Cdma2000HrpdB2Thd1Rsrp l InterRatHOCdmaHrpdGroup.Cdma2000HrpdB2Thd1Rsrq
Service-based Inter-RAT Handover With service-based inter-RAT handover, voice services are handed over from the E-UTRAN to GERAN or UTRAN during the service setup phase. If VoLTE has been deployed, the configurations of service-based inter-RAT handover must meet either of the following conditions so that the eNodeB does not immediately trigger the service-based inter-RAT handover procedure after the UE sets up voice services: l
The UtranServiceHoSwitch(UtranServiceHoSwitch) and GeranServiceHoSwitch(GeranServiceHoSwitch) options of the ENODEBALGOSWITCH.HoAlgoSwitch parameter are deselected.
l
The UtranServiceHoSwitch(UtranServiceHoSwitch) and GeranServiceHoSwitch(GeranServiceHoSwitch) options of the ENODEBALGOSWITCH.HoAlgoSwitch parameter are selected, and the SERVICEIRHOCFGGROUP.InterRatHoState parameter mapping QCI of 1 and QCI of 5 is not set to MUST_HO.
Distance-based Inter-RAT Handover The eNodeB supports only distance-based inter-RAT handovers to GERAN or UTRAN. The following handover parameters can be configured based on QCIs for each RAT. These parameters also apply to coverage-based inter-RAT handovers. Table 4-2 Distance-based inter-RAT handover parameters Target RAT
Parameter ID
UTRAN
l InterRatHoUtranGroup.InterRatHoUtranB1ThdEcn0 l InterRatHoUtranGroup.InterRatHoUtranB1ThdRscp l InterRatHoUtranGroup.InterRatHoUtranB1Hyst l InterRatHoUtranGroup.InterRatHoUtranB1TimeToTrig l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0 l InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRscp
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
46
eRAN VoLTE Feature Parameter Description
4 Enhanced VoLTE Features
Target RAT
Parameter ID
GERAN
l InterRatHoGeranGroup.InterRatHoGeranB1Hyst l InterRatHoGeranGroup.InterRatHoGeranB1Thd l InterRatHoGeranGroup.InterRatHoGeranB1TimeToTrig l InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd
UL-Quality-based Inter-RAT Handover Similar to coverage-based inter-RAT handover, certain handover parameters for UL-qualitybased inter-RAT handover can be configured based on QCIs. For details, see Coverage-based Inter-RAT Handover.
4.5.4.2 Handover Mode The eNodeB determines whether to use SRVCC or PS handover for performing the preceding inter-RAT handovers so that the CS or PS domain of the target RAT can carry voice services. The eNodeB selects a handover mode based on conditions such as UE capability and whether the target RAT can carry IMS-based voice services.
SRVCC With SRVCC, the eNodeB hands over voice services from E-UTRAN to the CS domain of the GERAN or UTRAN to ensure voice call continuity. For details about SRVCC, see SRVCC Feature Parameter Description.
PS Handover With PS handover, the eNodeB hands over voice services from E-UTRAN to the PS domain of the UTRAN to ensure voice call continuity. If the UTRAN supports the IMS-based VoHSPA voice solution, voice services can be handed over to VoHSPA of the UTRAN using inter-RAT PS handovers. In this situation, the mechanism of inter-RAT PS handovers for voice services is the same as that for data services. For details about PS handovers, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
47
eRAN VoLTE Feature Parameter Description
5
5 Special Processing by Other Features
Special Processing by Other Features
ANR After LOFD-002001 Automatic Neighbour Relation (ANR) or LOFD-002002 Inter-RAT ANR are configured, the eNodeB filters out UEs performing voice services while selecting UEs to perform fast ANR measurement. l
The eNodeB does not select the UEs with bearers of QCI 1 when selecting UEs that newly access the network or are handed over to the cell.
l
For UEs that are already selected for fast ANR measurement, the eNodeB uses a measurement control policy depending on the value of the GlobalProcSwitch.VoipWithGapMode parameter:
l
–
When this parameter is set to ENABLE, the eNodeB does not delete the fast ANR measurements if the bearer with a QCI of 1 is set up for the UE. However, continuous measurement gaps may affect the voice quality of services with a QCI of 1.
–
When this parameter is set to DISABLE, the eNodeB sends an RRC Connection Reconfiguration message to delete fast ANR measurements if the UE sets up bearer with a QCI of 1.
UEs read cell global identifications (CGIs) in sleep time during DRX. The sleep time stops when a data packet arrives. This has an impact on the CGI reading success rate. This success rate is even lower for VoLTE services, which are scheduled at a fixed interval and encounter a higher probability that the sleep time stops. After a CGI is acquired, the identified cell is automatically configured as a neighboring cell. NOTE
Event-triggered ANR can be triggered by coverage-based measurements for handover or user-numberbased measurements for MLB. If coverage-based measurement for handover is enabled, gap-assisted measurement is started even for voice users to avoid call drops. If user-number-based measurement for MLB is enabled, MLB does not select voice users for load balancing. When VoLTE is deployed, it is recommended that GlobalProcSwitch.VoipWithGapMode be set to DISABLE to ensure the quality of voice services.
PCI Collision Detection and Self-Optimization After the LOFD-002007 PCI Collision Detection & Self-Optimization feature and ANRbased proactive PCI conflict detection are enabled, the eNodeB selects UEs without CQI 1 bearers for proactive PCI conflict detection. In addition, the eNodeB sends A3 and A4 Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
48
eRAN VoLTE Feature Parameter Description
5 Special Processing by Other Features
measurement configurations to the selected UEs, instructing the UEs to measure their serving frequencies and neighboring E-UTRAN frequencies. For UEs that are already selected, the eNodeB uses a measurement control policy depending on the value of the GlobalProcSwitch.VoipWithGapMode parameter: l
When this parameter is set to ENABLE, the eNodeB does not delete the measurements of the UE if the bearer of QCI of 1 is set up for the UE. However, continuous measurement gaps may affect the voice quality of services with a QCI of 1.
l
When this parameter is set to DISABLE, the eNodeB sends the RRC Reconfiguration message to delete the measurement configuration if the UE sets up a bearer with a QCI of 1. NOTE
When VoLTE is deployed, it is recommended that GlobalProcSwitch.VoipWithGapMode be set to DISABLE to ensure the quality of voice services.
Carrier Aggregation l
If voice services are initiated for carrier aggregation (CA) UEs, voice services can be scheduled only on PCells.
l
If the SccBlindCfgSwitch of the eNodeBAlgoSwitch.CaAlgoSwitch parameter is turned off, UEs that have originated voice services are not selected for CA.
l
If the SccBlindCfgSwitch of the eNodeBAlgoSwitch.CaAlgoSwitch parameter is turned on, UEs that have originated voice services can be selected for CA.
Periodic Measurement Reporting and GSM and LTE Buffer Zone Optimization For periodic measurement reporting or GSM and LTE buffer zone optimization, the eNodeB selects UEs for measurement based on the GlobalProcSwitch.VoipWithGapMode parameter setting: l
When this parameter is set to ENABLE: The eNodeB randomly selects UEs. When a UE performing voice services is selected, continuous measurement gaps may affect the voice quality of the UE.
l
When this parameter is set to DISABLE: If the UE has already initiated voice services, the eNodeB does not select the UE for periodic inter-frequency or inter-RAT measurement. –
The UE is selected for measurement decision until the UE releases voice services and is selected for the second time.
–
If the UE is not performing voice services, the eNodeB sends periodic interfrequency or inter-RAT measurement to the UE. If the UE initiates voice services later, the eNodeB updates configurations to delete existing periodic inter-frequency or inter-RAT measurement of the UE. The UE is selected for measurement decision until the UE releases voice services and is selected for the second time.
NOTE
When VoLTE is deployed, it is recommended that GlobalProcSwitch.VoipWithGapMode be set to DISABLE to ensure the quality of voice services.
Mobility Load Balancing l Issue 03 (2015-06-30)
LOFD-001032 Intra-LTE Load Balancing Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
49
eRAN VoLTE Feature Parameter Description
5 Special Processing by Other Features
The eNodeB transfers UEs based on the PRB usage. The eNodeB may transfer UEs performing voice services for small-bandwidth cells. The voice quality of transferred UEs may be affected. l
LOFD-070215 Intra-LTE User Number Load Balancing For user-number-based intra-LTE load balancing, the eNodeB does not transfer UEs performing voice services.
l
LOFD-001045 Inter-RAT Load Sharing to GERAN and LOFD-001044 Inter-RAT Load Sharing to UTRAN During inter-RAT load balancing, the eNodeB selects the UEs to be transferred based on PRB-usage and user number. The eNodeB may transfer UEs performing voice services. The voice quality of transferred UEs may be affected.
PRB-based MLB is not recommended for VoLTE.
DL Non-GBR Packet Bundling After the LOFD-001109 DL Non-GBR Packet Bundling feature is enabled, the scheduling priority of voice services is no longer the highest priority. This feature is not recommended for VoLTE when there are many voice users because this feature may slightly affect voice quality.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
50
eRAN VoLTE Feature Parameter Description
6 Related Features
6
Related Features
This chapter describes the relationships between VoLTE-related features and other features.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
51
eRAN VoLTE 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 channel conditions vary. Consequently, the IBLER may not converge on a target value. To solve this problem, closed-loop power control can be enabled to adjust UE transmit power for the PUSCH.
Mutually Exclusive Features None
Impacted Features l
LBFD-002017 DRX If the value of the DrxParaGroup.LongDrxCycle parameter for QCI of 1 is set to a value greater than the semi-persistent scheduling period (20 ms), the eNodeB does not activate downlink semi-persistent scheduling.
l
LOFD-001036 RAN Sharing with Common Carrier Voice services have a high scheduling priority and are sensitive to scheduling delays. Therefore, uplink and downlink semi-persistent scheduling does not consider the configured proportions of PRBs that can be allocated to different operators.
l
LBFD-002005 DL Asynchronous HARQ The HARQ retransmission for DL semi-persistently scheduled data is performed by using dynamic scheduling.
l
LBFD-002006 Uplink Synchronization HARQ When the activated retransmission for UL semi-persistent scheduling conflicts with higher-priority scheduling, adaptive HARQ retransmission is used.
l
LAOFD-001001 LTE-A Introduction According to section 5.10 "Semi-Persistent Scheduling" in 3GPP TS 36.321, the semipersistent scheduling feature can be configured only in the PCell for CA UEs.
l
LAOFD-0010014 DL 2x2 MIMO based on TM9 When TM9 UEs use SPS scheduling, the MIMO scheme for the UEs in PDSCH is transmit diversity based on port7.
l
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 both features are met, uplink VoIP semi-persistent scheduling takes precedence.
Uplink RLC segmentation enhancement –
Issue 03 (2015-06-30)
LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentation enhancement cannot take effect for the same UE at the same time. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
52
eRAN VoLTE Feature Parameter Description
– l
6 Related Features
LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentation enhancement can be enabled for the same cell at the same time.
TDLOFD-001007 High Speed Mobility Semi-persistent scheduling is not suitable in high-speed movement scenarios because it uses fixed MCSs and PRBs for data transmission and cannot well adapt to changes in channel conditions.
l
LBFD-081104 UL Compensation Scheduling Uplink VoIP semi-persistent scheduling and uplink compensation scheduling cannot take effect for the same UE at the same time.
6.2 LOFD-001048 TTI Bundling Prerequisite Features None
Mutually Exclusive Features None
Impacted Features l
l
LBFD-002017 DRX and LOFD-001105 Dynamic DRX –
If a UE is in the TTI bundling state, the eNodeB instructs the UE to enter DRX mode only when the UE needs to perform ANR measurement.
–
If a UE is in DRX mode, the eNodeB instructs the UE to exit DRX mode after activating TTI bundling. An exception is that if the UE is performing ANR measurement in DRX mode, the eNodeB does not instruct the UE to exit DRX mode.
LAOFD-001001 LTE-A Introduction According to 3GPP TS 36.331, TTI bundling cannot be configured if a CA UE performs data transmission in the uplink. After a CA UE enters the TTI bundling state, the secondary serving cell (SCell) of this UE will be automatically deleted and CA is no longer activated for UEs that are already in the TTI bundling state.
l
l
Uplink RLC segmentation enhancement –
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.
LOFD-001007 High Speed Mobility and LOFD-001008 Ultra High Speed Mobility To instruct UEs to enter or exit the TTI bundling state, the eNodeB needs to send RRC Connection Reconfiguration messages. When UEs are moving at high or ultra high speed, their channel conditions change rapidly. As a result, the UEs frequently enter and exit the TTI bundling state, which increases signaling load on the Uu interface, degrades voice quality, and increase the probability of service drops. Therefore, TTI bundling is not recommended in high- or ultra-high-movement scenarios.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
53
eRAN VoLTE Feature Parameter Description
6 Related Features
6.3 Uplink RLC Segmentation Enhancement Prerequisite Features None
Mutually Exclusive Features None
Impacted Features l
l
l
LOFD-001016 VoIP Semi-persistent Scheduling –
LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentation enhancement can be enabled for the same cell at the same time.
–
LOFD-001016 VoIP Semi-persistent Scheduling and uplink RLC segmentation enhancement cannot take effect for the same UE at the same time.
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.
LBFD-081105 Voice-Specific AMC The uplink IBLER of the voice user cannot converge to the target value when RLC segmentation enhancement takes effect.
6.4 LOFD-081229 Voice Characteristic Awareness Scheduling Prerequisite Features l
LBFD-002025 Basic Scheduling
l
LOFD-00101502 Dynamic Scheduling
Mutually Exclusive Features None
Impacted Features l
Issue 03 (2015-06-30)
LOFD-001016 VoIP Semi-persistent 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 both features are met, uplink VoIP semi-persistent scheduling takes precedence. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
54
eRAN VoLTE Feature Parameter Description
6 Related Features
6.5 LBFD-081104 UL Compensation Scheduling Prerequisite Features l
LBFD-002025 Basic Scheduling
l
LOFD-00101502 Dynamic Scheduling
Mutually Exclusive Features None
Impacted Features LOFD-001016 VoIP Semi-persistent Scheduling Uplink VoIP semi-persistent scheduling and uplink compensation scheduling cannot take effect for the same UE at the same time.
6.6 LBFD-081105 Voice-Specific AMC Prerequisite Features l
LBFD-001006 AMC
l
LBFD-002025 Basic Scheduling
l
LOFD-00101502 Dynamic Scheduling
Mutually Exclusive Features None
Impacted Features l
LOFD-001016 VoIP Semi-persistent Scheduling LOFD-001016 VoIP Semi-persistent Scheduling and LBFD-081105 Voice-Specific AMC can be enabled for the same cell at the same time. However, voice-specific AMC takes effect only for dynamic scheduling of VoLTE users.
l
LOFD-001048 TTI Bundling LOFD-001048 TTI Bundling and LBFD-081105 Voice-Specific AMC can be enabled for the same cell at the same time. However, voice-specific AMC applies only to VoLTE users not in the TTI bundling state.
l
RLC segmentation enhancement The uplink IBLER of the voice user cannot converge to the target value when RLC segmentation enhancement takes effect.
6.7 Other Features This chapter describes other features related to VoLTE. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
55
eRAN VoLTE Feature Parameter Description
6 Related Features
Table 6-1 Other features VoLTE-related Feature
Description
LBFD-002023 Admission Control
For details, see Admission and Congestion Control Feature Parameter Description.
LBFD-002024 Congestion Control
For details, see Admission and Congestion Control Feature Parameter Description.
LOFD-00101502 Dynamic Scheduling
For details, see Scheduling Feature Parameter Description.
LBFD-002016 Dynamic Downlink Power Allocation
This VoLTE-related feature is associated with LOFD-001016 VoIP Semi-persistent Scheduling. For details about the impact on other features, see Power Control Feature Parameter Description. The downlink semi-persistent scheduling algorithm provides the initial block error rate (IBLER) of downlink voice services as an input to the downlink power control algorithm. The IBLER is a prerequisite for PDSCH power adjustment in semi-persistent scheduling mode.
LBFD-002026 Uplink Power Control
This VoLTE-related feature is associated with LOFD-001016 VoIP Semi-persistent Scheduling. For details about the impact on other features, see Power Control Feature Parameter Description. The uplink semi-persistent scheduling algorithm provides the uplink IBLER as an input to the uplink power control algorithm. The IBLER is a prerequisite for PUSCH power adjustment in semi-persistent scheduling mode. If uplink semi-persistent scheduling is enabled, it is recommended that the CloseLoopSpsSwitch option of the CellAlgoSwitch.UlPcAlgoSwitch parameter be selected to ensure that the uplink IBLER converges on the target IBLER.
LOFD-001017 RObust Header Compression (ROHC)
Issue 03 (2015-06-30)
For details, see ROHC Feature Parameter Description.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
56
eRAN VoLTE Feature Parameter Description
6 Related Features
VoLTE-related Feature
Description
LBFD-002017 DRX
The following are the relationships between DRX and TTI bundling and between DRX and scheduling: l If a UE is in the TTI bundling state, the eNodeB instructs the UE to enter DRX mode only when the UE needs to perform ANR measurement. l If a UE is in DRX mode, the eNodeB instructs the UE to exit DRX mode after activating TTI bundling. An exception is that if the UE is performing ANR measurement in DRX mode, the eNodeB does not instruct the UE to exit DRX mode. l When the long DRX cycle for QCI 1 is greater than the semi-persistent scheduling interval (for example, always 20 ms for FDD), downlink semi-persistent scheduling does not take effect. l After DRX is enabled, preallocation does not take effect. Preallocation decreases the probability of PDCCH false detection, which may cause packet loss, and therefore improves voice quality. For more information, see DRX and Signaling Control Feature Parameter Description.
Issue 03 (2015-06-30)
Intra-frequency handover
For details, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
Inter-frequency handover
For details, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
Inter-RAT handover
For details, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description and SRVCC Feature Parameter Description.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
57
eRAN VoLTE Feature Parameter Description
7 Network Impact
7
Network Impact
This chapter describes the impact of the VoIP-related features on the network.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
58
eRAN VoLTE Feature Parameter Description
7 Network Impact
7.1 LOFD-001016 VoIP Semi-persistent Scheduling System Capacity After semi-persistent scheduling is enabled, PDCCH resources do not hinder voice service capacity because PDCCH resources are consumed only when semi-persistent scheduling is initially activated or reactivated or when semi-persistently allocated resources are released. Compared with dynamic scheduling, enabling semi-persistent scheduling increases the number of supported voice service users by more than 30% in simulation case 1, according to the simulation conditions and capacity evaluation method specified in an appendix of 3GPP TS 36.814. During semi-persistent scheduling, the MCS index cannot exceed 15. This restriction may increase the number of RBs allocated to semi-persistently scheduled users near the cell center. For example, when the coding rate is 23.85 kbit/s (without considering ROHC) and the MCS index for voice users near the cell center is 26, two RBs are required in the uplink and one RB in the downlink (dual-stream mode) when dynamic scheduling is enabled. Under the same condition, semi-persistent scheduling requires three RBs in both the uplink and downlink due to the MCS index restriction (the largest MCS index is 15). That is, compared with dynamic scheduling, semi-persistent scheduling for voice users near the cell center consumes more RB resources. Therefore, the amount of RB resource for data services decreases (compared with that when semi-persistent scheduling is disabled), and the throughput of data services may also decrease. After downlink semi-persistent scheduling is enabled and voice services are set up, the eNodeB reserves HARQ processes for downlink semi-persistent scheduling. Before the next initial transmission in semi-persistent scheduling, the HARQ processes for downlink semipersistent scheduling may not be released. As a result, periodic data for semi-persistent scheduling cannot be sent. The HARQ processes are reserved to avoid such situation. The HARQ processes reserved for downlink semi-persistent scheduling cannot be used for dynamic scheduling for other service type of the UE, such as data service. In combined services where voice and data services coexist, the HARQ processes that can be used by data services therefore decrease. Compared with the scenario where dynamic scheduling is used by both voice and data services, the use of downlink semi-persistent scheduling for voice services affects the throughput of data services, specifically, when the volume of the data services is large (such as when full buffer service is performed). When there are multiple users or a small amount of data volume, the impact of reserving HARQ processes is small because the scheduling chances for UEs are discretely distributed or a few HARQ processes are required for data services.
Network Performance Fixed-position resource allocation is adopted after semi-persistent scheduling is activated. Compared with dynamic scheduling, semi-persistent scheduling may increase the scheduling wait time.
7.2 LOFD-001048 TTI Bundling System Capacity No impact. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
59
eRAN VoLTE Feature Parameter Description
7 Network Impact
Network Performance LOFD-001048 TTI bundling increases the cell edge coverage of PUSCH, improves MCS in uplink weak-coverage areas, and reduces the packet loss rate. However, this feature increases signaling overheads because the entry and exit of the TTI bundling state requires the exchange of RRC messages. When the number of TTI bundling mode reconfiguration messages (indicated by the counters L.Signal.Num.TtiBundling.Enter and L.Signal.Num.TtiBundling.Exit) increases, the average board CPU usage (indicated by the counter VS.BBUBoard.CPULoad.Mean (%)) slightly increases. As defined in 3GPP protocols, TTI bundling uses a maximum of three PRBs and adopts QPSK with the highest MCS order of 10. That is, after TTI bundling is enabled, the maximum number of TBS that can be transmitted is 504 bits. This restricts the uplink throughput of TTI bundling. The logical channel priority of signaling and voice services is higher than that of data services, which means that UEs preferentially send signaling and voice services. As a result, the uplink throughput of data services is further restricted.
7.3 Uplink RLC Segmentation Enhancement System Capacity No impact.
Network Performance Uplink RLC segmentation enhancement can increase the mean opinion score (MOS)of VoLTE users when the users are in a weak coverage area but not in the TTI bundling state. However, uplink RLC segmentation enhancement raises the uplink MCS, IBLER and residual BLER (RBLER).
7.4 LOFD-081229 Voice Characteristic Awareness Scheduling System Capacity No impact.
Network Performance Uplink VoLTE volume estimation for dynamic scheduling can shorten voice service delays, reduce the uplink packet loss rate, and improve voice quality when a cell is heavily loaded and DRX is enabled. However, this function increases RB overheads and lowers MCS indexes allocated to voice users; when there are many voice users, this function also reduces cell throughput. Uplink delay-based dynamic scheduling can be used in heavy traffic scenarios to improve voice quality in weak-coverage areas. However, this function prolongs SR-based scheduling, which further: l
Issue 03 (2015-06-30)
Prolongs processing time such as E-RAB setup time, RRC connection setup time, ping delay, time of transition from idle mode to connected mode, and attach delay. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
60
eRAN VoLTE Feature Parameter Description
l
7 Network Impact
Slightly decreases cell throughput.
Independent configuration for voice inactivity timer has the following impacts on network performance: l
If the value of the RrcConnStateTimer.UeInactiveTimerQci1 parameter is smaller than that of the RrcConnStateTimer.UeInactiveTimer parameter, the online duration of voice service UEs becomes short and voice service drop rate decreases when there is no data transmission in the uplink and downlink while waiting for the callee to answer the call.
l
If the value of the RrcConnStateTimer.UeInactiveTimerQci1 parameter is greater than that of the RrcConnStateTimer.UeInactiveTimer parameter, the online duration of voice service UEs becomes long, RRC connection request number decreases, number of normal releases decreases, and voice service drop rate increases.
7.5 LBFD-081104 UL Compensation Scheduling System Capacity No impact.
Network Performance Uplink compensation scheduling can reduce the rate of uplink packet losses in heavy traffic scenarios, shorten voice packet delays, and improve voice quality. However, this feature increases RB and CCE overheads; when there are many voice users, this feature also reduces cell throughput. In addition, uplink compensation scheduling decreases the possibility that uplink control information of voice users is transmitted over PUCCH and increases the possibility that uplink control information of voice users is transmitted over PUSCH. This affects the possibility that PDSCH ACK/NACK is detected as DTX and slightly increases VoLTE downlink packet loss rate (indicated by L.Traffic.DL.PktUuLoss.Loss.QCI.1/ L.Traffic.DL.PktUuLoss.Tot.QCI.1).
7.6 LBFD-081105 Voice-Specific AMC System Capacity No impact.
Network Performance l
This feature affects voice quality in the following aspects: –
Issue 03 (2015-06-30)
If the CELLULSCHALGO.SinrAdjTargetIblerforVoLTE parameter is set to a smaller value, the MCS indexes selected for uplink voice services are smaller. For voice users in the cell center, the uplink QCI 1 packet loss rate may slightly decrease and voice quality almost remains unchanged. For voice users not in the cell center, the number of uplink RLC segments increases and the uplink QCI 1 packet loss rate may increase in the case of heavy load; as a result, voice quality becomes worse and voice capacity decreases. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
61
eRAN VoLTE Feature Parameter Description
–
l
7 Network Impact
If the CELLULSCHALGO.SinrAdjTargetIblerforVoLTE parameter is set to a larger value, the MCS indexes selected for uplink voice services are larger. In the uplink, the IBLER, RBLER, and QCI 1 packet loss rate increases, and voice quality becomes worse. In the downlink, the QCI 1 packet loss rate also increases and voice quality also becomes worse because the demodulation performance deteriorates for ACKs/NACKs and channel status information transmitted on the PUSCH.
This feature may also affect cell throughput and data service throughput. If the CELLULSCHALGO.SinrAdjTargetIblerforVoLTE parameter is set to a smaller value, the MCS indexes selected for uplink voice services are smaller and the number of consumed RBs increases. When there are many voice users, cell throughput decreases.
7.7 Other Features This chapter describes the impact of other features related to VoLTE on system capacity and network performance. Table 7-1 Impact of other VoLTE-related features on system capacity and network performance
Issue 03 (2015-06-30)
Feature
Description
LBFD-002023 Admission Control
Admission control maximizes system capacity while providing users with satisfied QoS, which is indicated by the voice service MOS.
LBFD-002024 Congestion Control
Congestion control maximizes system capacity while preferentially providing satisfied QoS for high-priority UEs. The priority refers to the allocation/retention priority (ARP). Congestion control ensures a high satisfaction rate of voice service users in congested cells.
LOFD-00101502 Dynamic Scheduling
Voice packets are generally small. If semi-persistent scheduling is disabled, voice service capacity is mainly subject to PDCCH resources. If a continuous increase in the number of voice service users causes PDCCH resources to become insufficient first, the cell capacity decreases.
LBFD-002016 Dynamic Downlink Power Allocation
For details, see Power Control Feature Parameter Description.
LBFD-002026 Uplink Power Control
For details, see Power Control Feature Parameter Description.
LOFD-001017 RObust Header Compression (ROHC)
For details, see ROHC Feature Parameter Description.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
62
eRAN VoLTE Feature Parameter Description
Issue 03 (2015-06-30)
7 Network Impact
Feature
Description
LBFD-002017 DRX
DRX extends voice service delay because it introduces the sleep time. If DRX parameter settings are inappropriate, voice service capacity will decrease or the packet loss rate increases because voice services cannot be scheduled in realtime. For details about the impact of DRX on network performance, see DRX Feature Parameter Description.
Intra-frequency handover
For details, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
Inter-frequency handover
For details, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description.
Inter-RAT handover
For details, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description and SRVCC Feature Parameter Description.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
63
eRAN VoLTE Feature Parameter Description
8
8 Voice Service Performance Evaluation
Voice Service Performance Evaluation
8.1 QoS Requirements Section 6.1.7 in 3GPP TS 23.203 of Release 10 provides the QoS requirements of services with standardized QCIs. Table 8-1 lists the QoS requirements of QCI 1 services. Table 8-1 QoS requirements of QCI 1 services Resource Type
Priority
Packet Delay Budget (ms)
Packet Error Loss Rate
Typical Service
GBR
2
100
10-2
Voice service
l
The preceding Packet Delay Budget indicates the threshold delay between UE and PDN gateway (P-GW). The corresponding user satisfaction rate is 98%.
l
The preceding Packet Error Loss Rate indicates the threshold proportion of SDUs that are not successfully sent from the data link layer of the transmission end to the corresponding upper layer of the receive end.
The packet delay budget, uplink and downlink Uu interface packet loss rate, and downlink PDCP packet loss rates of QCI 1 services can be measured using counters. For details about related counters, see 9.2.4.2 Voice QoS.
8.2 Quality Evaluation The mean opinion score (MOS) is an important indicator for evaluating voice quality. MOSbased evaluation involves subjective evaluation, objective evaluation, and measurement-based evaluation.
8.2.1 Subjective Evaluation MOS is a subjective measurement where listeners perceive raw speech materials and processed degraded speech materials and then score speech quality. Table 8-2 lists the MOS standards defined in ITU-T G.107. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
64
eRAN VoLTE Feature Parameter Description
8 Voice Service Performance Evaluation
Table 8-2 MOS standards MO S
Quality Level
Auditory Distortion Extent
Required Auditory Effort
5
Excellent
Distortion not noticed
Listening in a relaxed manner
4
Good
Distortion noticed, but not unpleasant
Listening with a little effort
3
Fair
Distortion noticed, and annoying
Listening in an attentive manner
2
Poor
Unpleasant but not annoying
Listen with much effort
1
Bad
Unpleasant and annoying
Cannot understand the contents
8.2.2 Objective Evaluation Perceptual Evaluation of Speech Quality (PESQ), defined in ITU-T P862, is a mainstream method of objectively evaluating AMR-NB speech quality. Perceptual Objective Listening Quality Assessment (POLQA), defined in ITU-T P863, is the evolution of PESQ; POLQA supports wider sampling scope and provides more accurate evaluation of AMR-WB or AMRNB speech quality. PESQ and POLQA are based on special tools, for example, Digital Speech Level Analyzer (DSLA). Objective evaluation is commonly used by operators to evaluate speech quality. However, it requires the collaboration of drive tests. As it cannot monitor speech quality in real time, it is generally used for tests in labs, network entry tests, and third-party evaluation of network quality.
8.2.3 Measurement-based Evaluation Overview Using the third-party's drive test tools to evaluate speech quality is time and cost consuming and cannot monitor speech quality in real time. Therefore, it is important for vendors to develop their own measurement-based evaluation methods. Huawei uses a Voice Quality Monitoring (VQM) algorithm to calculate the MOS scores of uplink and downlink voice services on the Uu interface. VQM is mainly used for network monitoring, network optimization, VIP guarantee, and user complaint handling. VQM reduces the necessity of drive tests required for obtaining voice quality. VQM applies only to the AMR speech codec scenario. VQM is controlled by the EnodebAlgoSwitch.VQMAlgoSwitch parameter, which is turned off by default. After this parameter is turned on, the eNodeB automatically identifies whether the eNodeB supports AMR speech codec. The eNodeB calculates only the MOS of voice services that use the AMR speech codec scheme. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
65
eRAN VoLTE Feature Parameter Description
8 Voice Service Performance Evaluation
VQM Principles Figure 8-1 shows the VQM implementation process. Figure 8-1 VQM implementation process
1.
The eNodeB monitors counters for voice packets of QCI of 1, including the frame error rate (FER) on the Uu interface, long frame error rate (LFER), and handover state. When detecting that the delay variation for voice packets of QCI of 1 exceeds the VQMALGO.ULDelayJitter parameter value, the eNodeB determines that a packet loss occurs.
2.
Then, the eNodeB inputs the monitoring results to the Huawei proprietary voice quality indicator (VQI) model and estimates the MOS scores of uplink and downlink voice services on the Uu interface at intervals of 2.5 seconds. The VQI model is based on the algorithms specified in ITU-T P.863 and simulates an MOS score using mathematical formulas.
3.
–
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.
The MOS scores are saved in call history records (CHRs) and are used to collect the statistics of cell-level voice quality counters and monitor user-level performance. NOTE
The voice quality monitoring results including statistics about cell-level voice quality counters and user-level performance monitoring results as well as CHRs do not include user privacy information.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
66
eRAN VoLTE Feature Parameter Description
8 Voice Service Performance Evaluation
Voice Quality Evaluation The eNodeB evaluates voice quality based on the MOS provided by the VQM and voice quality thresholds. In addition, the eNodeB collects the statistics of counters related to voice quality, as listed in Table 8-3. Table 8-3 Voice quality evaluation rules and related counters MOS Scores Provided by the VQI Model
Voice Quality Level
Related Counters
MOS > VQMAlgo.VqiExcellentThd
Excellent
For details, see Table 9-8.
VQMAlgo.VqiGoodThd < MOS ≤ VQMAlgo.VqiExcellentThd
Good
For details, see Table 9-9.
VQMAlgo.VqiPoorThd < MOS ≤ VQMAlgo.VqiGoodThd
Fair
For details, see Table 9-10.
VQMAlgo.VqiBadThd < MOS ≤ VQMAlgo.VqiPoorThd
Poor
For details, see Table 9-11.
MOS ≤ VQMAlgo.VqiBadThd
Bad
For details, see Table 9-12.
Application Limitations AMR coding rate is an important input for the VQI model. Currently, the VQM algorithm cannot monitor the AMR coding rate in real time. If the AMR coding rate changed, the output of the VQI model would be inaccurate. Up to now, it has not been found that the AMR coding rate changes in any scenario. In the following scenarios, the eNodeB cannot determine the AMR coding rate and therefore does not use the VQI model. l
One RTP packet carries multiple AMR speech frames.
l
One RTP packet carries multiple speech frames that are coded at different rates. The IP headers need to be removed when the eNodeB identifies the coding rate. The IP header length is different after the encryption. The IP header of a voice packet may include an Authentication Header (AH) or (Encapsulation Security Payload (ESP) header for encryption. The length of AHs is not fixed, and the latter part of ESP headers is encrypted, and the latter part of ESP headers is encrypted.
8.3 Capacity Evaluation The voice service capacity can be evaluated based on the number of users performing QCI 1 services. The related counters are listed below and described in 9.2.4.4 Voice Capacity. l
L.Traffic.ActiveUser.UL.QCI.1
l
L.Traffic.ActiveUser.DL.QCI.1
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
67
eRAN VoLTE Feature Parameter Description
8 Voice Service Performance Evaluation
8.4 Performance Evaluation The performance of voice services can be evaluated using the following KPIs, which are described in 9.2.4.1 Voice KPIs l
E-RAB Setup Success Rate (VoIP)
l
Call Drop Rate (VoIP)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
68
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9
Engineering Guidelines
9.1 Overview The engineering guidelines of features or functions listed in Table 9-1 are not included in this document. Table 9-1 VoLTE-related functions and features
Issue 03 (2015-06-30)
Features/Functions
Engineering Guidelines
LBFD-002023 Admission Control
For details about the engineering guidelines for this feature, see Admission and Congestion Control Feature Parameter Description.
LBFD-002024 Congestion Control
For details about the engineering guidelines for this feature, see Admission and Congestion Control Feature Parameter Description.
LOFD-00101502 Dynamic Scheduling
For details about the engineering guidelines for this feature, see Scheduling Feature Parameter Description.
Power control in dynamic scheduling
For details about the engineering guidelines for power control in dynamic scheduling, see Power Control Feature Parameter Description.
QCI and RLC mode
For details about the engineering guidelines for QCI and RLC mode, see QoS Management Feature Parameter Description.
LOFD-001017 RObust Header Compression (ROHC)
For details about the engineering guidelines for this feature, see ROHC Feature Parameter Description.
LOFD-001109 DL Non-GBR Packet Bundling
For details about the engineering guidelines for this feature, see Scheduling Feature Parameter Description.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
69
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Features/Functions
Engineering Guidelines
Intra-frequency handover
For details about the engineering guidelines for this function, see Intra-RAT Mobility Management in Connected Mode.
Inter-frequency handover
For details about the engineering guidelines for this function, see Intra-RAT Mobility Management in Connected Mode.
Inter-RAT handover
For details about the engineering guidelines for SRVCC, see SRVCC Feature Parameter Description. For details about the engineering guidelines for PS handover, see Inter-RAT Mobility Management in Connected Mode.
LBFD-002017 DRX
For details about the engineering guidelines for this feature, see DRX and Signaling Control Feature Parameter Description.
9.2 Basic Functions 9.2.1 When to Use Basic Functions Users can determine whether to deploy IMS-based VoLTE services depending on whether IMS is deployed, transmission delay, and voice service policies. The E-UTRAN supports VoLTE after the IMS is deployed. However, VoLTE is not used in the following scenarios because IMS-based VoLTE is not appropriate for these scenarios: l
Transmission delay is large.
l
Voice services are not allowed on certain frequency bands.
You can turn off the ENodeBAlgoSwitch.EutranVoipSupportSwitch if the eNodeB works in the preceding scenarios. Turning off this switch prevents UEs from initiating voice services and prevents UEs performing voice services from handing over to the eNodeB. For details, see 3.2.2 VoLTE-Prohibited Scenario. NOTE
After the ENodeBAlgoSwitch.EutranVoipSupportSwitch is turned off, you also need to disable VoLTE in the corresponding tracking areas on the MME.
In other scenarios, turn on the ENodeBAlgoSwitch.EutranVoipSupportSwitch switch so that the eNodeB supports IMS-based voice services. In scenarios where E-UTRAN coverage is discontinuous, it is recommended that the SRVCC function be enabled. If the MME supports the UE Radio Capability Match REQUEST and UE Radio Capability Match RESPONSE messages introduced in 3GPP Release 11, it is recommended that the SupportS1UeCapMatchMsg option of the GlobalProcSwitch.ProtocolSupportSwitch Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
70
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
parameter be selected on the eNodeB side. By doing this, the MME considers the VoLTE mobility capability of the UE during the voice policy negotiation. In this manner, UEs that do not support SRVCC do not adopt VoLTE as the voice policy, thereby ensuring voice continuity. It is recommended that the VQM function be enabled to monitor voice quality.
9.2.2 Required Information None
9.2.3 Deployment 9.2.3.1 Requirements Operating Environment l
UEs must support VoLTE, and the EPC must support IMS.
l
Operators have deployed the IMS.
Transmission Networking VoLTE services have high requirements on end-to-end real-time delay. For example, when the transmission delay between the eNodeB and EPC exceeds 20 ms, VoLTE is not appropriate for the eNodeB. For the requirements on transmission delay and jitter on S1 and X2 interfaces, see IP eRAN Engineering Guide Feature Parameter Description.
License None
9.2.3.2 Data Preparation There are three types of data sources: l
Network plan (negotiation not required): parameter values planned and set by the operator
l
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l
User-defined: parameter values set by users
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to set the eNodeB voice service switch.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
71
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Parameter Name
Parameter ID
Data Source
Setting Notes
Eutran Voip Support Switch
ENodeBAlgoSwitc h.EutranVoipSupp ortSwitch
Network plan (negotiation not required)
Set this parameter to ON(On) if you plan to use the VoLTE voice solution. For details about the deployment suggestion of the VoLTE voice solution, see 9.2.1 When to Use Basic Functions.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to determine whether the eNodeB supports voice mobility. Parameter Name
Parameter ID
Data Source
Setting Notes
Protocol Procedure Support Switch
GlobalProcSwitch. ProtocolSupportSwitch
Network plan (negotiation not required)
If the MME supports the UE Radio Capability Match REQUEST and UE Radio Capability Match RESPONSE messages introduced in 3GPP Release 11, set this parameter to SupportS1UeCapMatchMsg(Su pportS1UeCapMatchMsg).
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to determine whether the eNodeB supports VQM. Parameter Name
Parameter ID
Data Source
Setting Notes
Voice quality monitoring algo switch
ENodeBAlgoSwitc h.VQMAlgoSwitch
Network plan (negotiation not required)
To monitor the voice quality, set this parameter to VQM_ALGO_SWITCH_ON.
The following table describes the parameter that must be set in the RlcPdcpParaGroup MO to configure the PDCP discard timer.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
72
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Parameter Name
Parameter ID
Data Source
Setting Notes
Discard timer
RlcPdcpParaGrou p.DiscardTimer
Network plan (negotiation not required)
If the voice service bearer planning policy specified by operators is QCI 5 multiplexing for carrying voice packets, it is recommended that this parameter for QCI of 5 be set to 150 ms. Otherwise, set this parameter for QCI of 5 to Infinity.
9.2.3.3 Precautions None
9.2.3.4 Hardware Adjustment None
9.2.3.5 Initial Configuration Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs Enter the values of the parameters listed in Table 9-2 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l
The MOs in Table 9-2 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l
Some MOs in Table 9-2 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Table 9-2 Common data
Issue 03 (2015-06-30)
MO
Sheet in the Summary Data File
Parameter Group
Remarks
ENodeBAlgoS witch
ENodeBAlgoSwitch
EutranVoipSupportSwitch
Userdefined template
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
73
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
MO
Sheet in the Summary Data File
Parameter Group
Remarks
GlobalProcSwit ch
GlobalProcSwitch
ProtocolSupportSwitch
Userdefined template
ENodeBAlgoS witch
ENodeBAlgoSwitch
VQMAlgoSwitch
Userdefined template
RlcPdcpParaGr oup
RlcPdcpParaGroup
DiscardTimer
Userdefined template
Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. Step 1 The procedure is as follows: After creating a planned data area, choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode), to customize a summary data file for batch reconfiguration. NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs listed in Table 9-2 and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End
Using the CME to Perform Single Configuration On the CME, set the parameters listed in the 9.4.3.2 Data Preparation section for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
74
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Step 2 In area 1 shown in Figure 9-1, select the eNodeB to which the MOs belong. Figure 9-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL. Step 4 In area 3, double-click the MO in the Object Name column. Step 5 All parameters in this MO are displayed in area 4. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End
Using MML Commands l
Run the MOD ENODEBALGOSWITCH command to turn on the EutranVoipSupportSwitch switch.
l
Run the MOD GLOBALPROCSWITCH command and select SupportS1UeCapMatchMsg.
l
Run the MOD ENODEBALGOSWITCH command to turn on the VQMAlgoSwitch.
MML Command Examples MOD ENODEBALGOSWITCH:EUTRANVOIPSUPPORTSWITCH=ON; MOD GLOBALPROCSWITCH: ProtocolSupportSwitch=SupportS1UeCapMatchMsg-1; MOD ENODEBALGOSWITCH:VQMALGOSWITCH=VQM_ALGO_SWITCH_ON;
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
75
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.2.3.6 Activation Observation To check whether a UE can perform voice services after the EutranVoipSupportSwitch switch is turned on, perform the following steps: Step 1 Run the LST ENodeBAlgoSwitch command to check whether the EutranVoipSupportSwitch switch is turned on. Step 2 Enable a UE to access a cell and perform voice services. Step 3 View the E-RAB SETUP REQUEST and E-RAB SETUP RESPONSE messages for QCI 5 and QCI 1 in the S1 interface tracing task result on the U2000. Bearers for QCI of 5 and QCI of 1 are successfully set up, as shown in Figure 9-2, Figure 9-3, Figure 9-4, and Figure 9-5. Figure 9-2 E-RAB SETUP REQUEST (QCI5)
Figure 9-3 E-RAB SETUP RESPONSE (QCI5)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
76
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Figure 9-4 E-RAB SETUP REQUEST (QCI1)
Figure 9-5 E-RAB SETUP RESPONSE (QCI1)
Step 4 Check whether the following counters indicate successful voice service setup. Counter ID
Counter Name
Counter Description
15267266 69
L.ERAB.SuccEst.QC I.1
Number of successful E-RAB setups initiated by UEs for services with the QCI of 1 in a cell
15267266 77
L.ERAB.SuccEst.QC I.5
Number of successful E-RAB setups initiated by UEs for services with the QCI of 5 in a cell
Step 5 View the "voice support match indicator" IE in the UE RADIO CAPABILITY MATCH RESPONSE message in the S1 interface tracing task result on the U2000. If the value of the
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
77
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
IE is supported or not supported, the eNodeB can query a UE's capability in supporting VoLTE mobility and report the capability to the MME. ----End
9.2.3.7 Reconfiguration N/A
9.2.3.8 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-3. Table 9-3 Common data MO
Sheet in the Summary Data File
Parameter Group
Remarks
ENodeBAlgo Switch
ENodeBAlgoSwitch
EutranVoipSupportSwitch
OFF(Off)
GlobalProcS witch
GlobalProcSwitch
ProtocolSupportSwitch
Deselected
ENodeBAlgo Switch
ENodeBAlgoSwitch
VQMAlgoSwitch
VQM_ALGO_S WITCH_OFF
Using the CME to Perform Single Configuration On the CME, set parameters according to the MOs listed in the related tables in each scenario. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands l
Run the MOD ENODEBALGOSWITCH command to turn off the EutranVoipSupportSwitch switch.
l
Run the MOD GLOBALPROCSWITCH command and clear SupportS1UeCapMatchMsg.
l
Run the MOD ENODEBALGOSWITCH command to turn off the VQMAlgoSwitch.
MML Command Examples MOD ENODEBALGOSWITCH:EUTRANVOIPSUPPORTSWITCH=OFF; MOD GLOBALPROCSWITCH: ProtocolSupportSwitch=SupportS1UeCapMatchMsg-0; MOD ENODEBALGOSWITCH:VQMALGOSWITCH=VQM_ALGO_SWITCH_OFF;
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
78
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.2.4 Performance Monitoring After common parameters are deployed, or after both common parameters and the features and functions in Table 9-1 are deployed, you can monitor voice service performance using the following counters.
9.2.4.1 Voice KPIs E-RAB Setup Success Rate (VoLTE) Table 9-4 describes the counters used to monitor the E-RAB setup success rates of voice services. Table 9-4 Counters used to monitor the E-RAB setup success rates of voice services Counter ID
Counter Name
Counter Description
1526726668
L.E-RAB.AttEst.QCI.1
Number of E-RAB setup attempts initiated by UEs for services with the QCI of 1 in a cell
1526726676
L.E-RAB.AttEst.QCI.5
Number of E-RAB setup attempts initiated by UEs for services with the QCI of 5 in a cell
1526726669
L.E-RAB.SuccEst.QCI.1
Number of successful E-RAB setups initiated by UEs for services with the QCI of 1 in a cell
1526726677
L.E-RAB.SuccEst.QCI.5
Number of successful E-RAB setups initiated by UEs for services with the QCI of 5 in a cell
1526727853
L.ERAB.AttEst.PLMN.QCI.1
Number of E-RAB setup attempts initiated by UEs of a specified operator for services with the QCI of 1 in a cell
1526727861
L.ERAB.AttEst.PLMN.QCI.5
Number of E-RAB setup attempts initiated by UEs of a specified operator for services with the QCI of 5 in a cell
1526727854
L.ERAB.SuccEst.PLMN.QCI.1
Number of successful E-RAB setups initiated by UEs of a specified operator for services with the QCI of 1 in a cell
1526727862
L.ERAB.SuccEst.PLMN.QCI.5
Number of successful E-RAB setups initiated by UEs of a specified operator for services 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 Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
79
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526729526
L.HHO.IntraeNB.IntraFre q.PrepAttOut.VoIP
Number of intra-eNodeB intra-frequency outgoing handover attempts for UEs performing voice services in a cell
1526729527
L.HHO.IntraeNB.InterFre q.PrepAttOut.VoIP
Number of intra-eNodeB inter-frequency outgoing handover attempts for UEs performing voice services in a cell
1526729535
L.HHO.IntereNB.IntraFre q.PrepAttOut.VoIP
Number of inter-eNodeB intra-frequency outgoing handover attempts for UEs performing voice services in a cell
1526729536
L.HHO.IntereNB.InterFreq .PrepAttOut.VoIP
Number of inter-eNodeB inter-frequency outgoing handover attempts for UEs performing voice services in a cell
1526729537
L.HHO.IntereNB.InterFdd Tdd.PrepAttOut.VoIP
Number of inter-eNodeB inter-duplexmode outgoing handover attempts for UEs performing voice services in a cell
1526729529
L.HHO.IntraeNB.IntraFre q.ExecAttOut.VoIP
Number of intra-eNodeB intra-frequency outgoing handover executions for UEs performing voice services in a cell
1526729530
L.HHO.IntraeNB.InterFre q.ExecAttOut.VoIP
Number of intra-eNodeB inter-frequency outgoing handover executions for UEs performing voice services in a cell
1526729538
L.HHO.IntereNB.IntraFre q.ExecAttOut.VoIP
Number of inter-eNodeB intra-frequency outgoing handover executions for UEs performing voice services in a cell
1526729539
L.HHO.IntereNB.InterFreq .ExecAttOut.VoIP
Number of inter-eNodeB inter-frequency outgoing handover executions for UEs performing voice services in a cell
1526729540
L.HHO.IntereNB.InterFdd Tdd.ExecAttOut.VoIP
Number of inter-eNodeB inter-duplexmode outgoing handover executions for UEs performing voice services in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
80
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Counter ID
Counter Name
Counter Description
1526729532
L.HHO.IntraeNB.IntraFre q.ExecSuccOut.VoIP
Number of successful intra-eNodeB intrafrequency outgoing handovers for UEs performing voice services in a cell
1526729533
L.HHO.IntraeNB.InterFre q.ExecSuccOut.VoIP
Number of successful intra-eNodeB interfrequency outgoing handovers for UEs performing voice services in a cell
1526729541
L.HHO.IntereNB.IntraFre q.ExecSuccOut.VoIP
Number of successful inter-eNodeB intrafrequency outgoing handovers for UEs performing voice services in a cell
1526729542
L.HHO.IntereNB.InterFreq .ExecSuccOut.VoIP
Number of successful inter-eNodeB interfrequency outgoing handovers for UEs performing voice services in a cell
1526729543
L.HHO.IntereNB.InterFdd Tdd.ExecSuccOut.VoIP
Number of successful inter-eNodeB interduplex-mode outgoing handovers for UEs performing voice services in a cell
1526729528
L.HHO.IntraeNB.InterFdd Tdd.PrepAttOut.VoIP
Number of intra-eNodeB inter-duplexmode outgoing handover attempts for UEs performing voice services in a cell
1526729531
L.HHO.IntraeNB.InterFdd Tdd.ExecAttOut.VoIP
Number of intra-eNodeB inter-duplexmode outgoing handover executions for UEs performing voice services in a cell
1526729534
L.HHO.IntraeNB.InterFdd Tdd.ExecSuccOut.VoIP
Number of successful intra-eNodeB interduplex-mode outgoing handovers for UEs performing 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)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
81
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
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 Counter ID
Counter Name
Counter Description
152672668 6
L.ERAB.AbnormRel.Q CI.1
Number of abnormal E-RAB releases for services with the QCI of 1 in a cell
152672669 4
L.ERAB.AbnormRel.Q CI.5
Number of abnormal E-RAB releases for services with the QCI of 5 in a cell
152672668 7
L.ERAB.NormRel.QCI. 1
Number of normal E-RAB releases for services with the QCI of 1 in a cell
152672669 5
L.ERAB.NormRel.QCI. 5
Number of normal E-RAB releases for services with the QCI of 5 in a cell
152672787 1
L.ERAB.AbnormRel.P LMN.QCI.1
Number of abnormal releases of activated E-RABs of a specified operator for services with the QCI of 1 in a cell
152672787 9
L.ERAB.AbnormRel.P LMN.QCI.5
Number of abnormal releases of activated E-RABs of a specified operator for services with the QCI of 5 in a cell
152672787 2
L.ERAB.NormRel.PLM N.QCI.1
Number of normal E-RAB releases of a specified operator for services with the QCI of 1 in a cell
152672788 0
L.ERAB.NormRel.PLM N.QCI.5
Number of normal E-RAB releases of a specified operator 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.ERAB.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.ERAB.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.ERAB.AbnormRel.PLMN.QCI.5+L.E-RAB.NormRel.PLMN.QCI.5)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
82
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.2.4.2 Voice QoS Packet Loss Rate Table 9-7 describes the counters used to monitor the uplink and downlink packet loss rate on the Uu interface and the downlink PDCP packet discard rate of voice services. Table 9-7 Counters used to monitor the packet loss rate
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526727 961
L.Traffic.UL.PktLoss.Los s.QCI.1
Number of discarded uplink traffic PDCP SDUs for DRB services with the QCI of 1 in a cell
1526727 962
L.Traffic.UL.PktLoss.Tot .QCI.1
Number of expected uplink traffic data packets for DRB services with the QCI of 1 in a cell
1526727 934
L.Traffic.DL.PktUuLoss. Loss.QCI.1
Number of discarded downlink traffic PDCP SDUs for DRB services with the QCI of 1 in a cell over the Uu interface
1526727 935
L.Traffic.DL.PktUuLoss. Tot.QCI.1
Number of transmitted downlink traffic PDCP SDUs for DRB services with the QCI of 1 in a cell over the Uu interface
1526726 833
L.PDCP.Tx.Disc.Trf.SDU .QCI.1
Number of downlink traffic SDUs discarded by the PDCP layer for services with the QCI of 1 in a cell
1526727 889
L.PDCP.Tx.TotRev.Trf.S DU.QCI.1
Number of transmitted downlink traffic PDCP SDUs for services with the QCI of 1 in a cell
1526736 684
L.Traffic.UL.PktLoss.Los s.PLMN.QCI.1
Total number of discarded uplink PDCP SDUs for traffic services with a QCI of 1 for a specific operator in a cell
1526736 686
L.Traffic.UL.PktLoss.Tot .PLMN.QCI.1
Total number of expected uplink data packets for DRB services with a QCI of 1 for a specific operator in a cell
1526736 737
L.Traffic.DL.PktUuLoss. Loss.PLMN.QCI.1
Total number of discarded downlink PDCP SDUs for traffic services with a QCI of 1 for a specific operator in a cell
1526736 739
L.Traffic.DL.PktUuLoss. Tot.PLMN.QCI.1
Total number of expected downlink data packets for DRB services with a QCI of 1 for a specific operator in a cell
1526736 680
L.PDCP.Tx.Disc.Trf.SDU .PLMN.QCI.1
Number of downlink traffic SDUs discarded by the PDCP layer for services with a QCI of 1 for a specific operator in a cell
1526736 682
L.PDCP.Tx.TotRev.Trf.S DU.PLMN.QCI.1
Number of transmitted downlink traffic PDCP SDUs for services with a QCI of 1 for a specific operator in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
83
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
UL packet discard rate on the Uu interface for QCI 1 = L.Traffic.UL.PktLoss.Loss.QCI.1 / L.Traffic.UL.PktLoss.Tot.QCI.1 DL packet discard rate on the Uu interface for QCI 1 = L.Traffic.DL.PktUuLoss.Loss.QCI. 1 / L.Traffic.DL.PktUuLoss.Tot.QCI.1 DL PDCP packet discard rate = L.PDCP.Tx.Disc.Trf.SDU.QCI.1 / (L.PDCP.Tx.Disc.Trf.SDU.QCI.1+L.PDCP.Tx.TotRev.Trf.SDU.QCI.1) UL packet discard rate on the Uu interface for QCI 1 of a specific operator = L.Traffic.UL.PktLoss.Loss.PLMN.QCI.1 / L.Traffic.UL.PktLoss.Tot.PLMN.QCI.1 DL packet discard rate on the Uu interface for QCI 1 of a specific operator = L.Traffic.DL.PktUuLoss.Loss.PLMN.QCI.1 / L.Traffic.DL.PktUuLoss.Tot.PLMN.QCI.1 DL PDCP packet discard rate for a specific operator = L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.1 / (L.PDCP.Tx.Disc.Trf.SDU.QCI. 1+L.PDCP.Tx.TotRev.Trf.SDU.PLMN.QCI.1)
9.2.4.3 Voice Quality Table 9-8, Table 9-9, Table 9-10, Table 9-11, and Table 9-12 describe the counters used to monitor the distribution of uplink and downlink voice service QoS. Table 9-8 Counters with the voice quality being Excellent
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526728411
L.Voice.VQI.UL.Exc ellent.Times
Number of times uplink voice quality is Excellent
1526728416
L.Voice.VQI.DL.Exc ellent.Times
Number of times downlink voice quality is Excellent
1526732687
L.Voice.VQI.AMR WB.UL.Excellent.Ti mes
Number of times uplink voice quality of AMRWB services is Excellent
1526732692
L.Voice.VQI.AMR WB.DL.Excellent.Ti mes
Number of times downlink voice quality of AMRWB services is Excellent
1526736660
L.Voice.VQI.UL.Exc ellent.Times.PLMN
Number of times uplink voice quality is Excellent for a specific operator in a cell
1526736665
L.Voice.VQI.DL.Exc ellent.Times.PLMN
Number of times downlink voice quality is Excellent for a specific operator in a cell
1526736670
L.Voice.VQI.AMR WB.UL.Excellent.Ti mes.PLMN
Number of times uplink voice quality of AMRWB services is Excellent for a specific operator in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
84
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Counter ID
Counter Name
Counter Description
1526736675
L.Voice.VQI.AMR WB.DL.Excellent.Ti mes.PLMN
Number of times downlink voice quality of AMRWB services is Excellent for a specific operator in a cell
Table 9-9 Counters with the voice quality being Good Counter ID
Counter Name
Counter Description
1526728412
L.Voice.VQI.UL.Go od.Times
Number of times uplink voice quality is Good
1526728417
L.Voice.VQI.DL.Go od.Times
Number of times downlink voice quality is Good
1526732688
L.Voice.VQI.AMR WB.UL.Good.Times
Number of times uplink voice quality of AMRWB services is Good
1526732693
L.Voice.VQI.AMR WB.DL.Good.Times
Number of times downlink voice quality of AMRWB services is Good
1526736661
L.Voice.VQI.UL.Go od.Times.PLMN
Number of times uplink voice quality is Good for a specific operator in a cell
1526736666
L.Voice.VQI.DL.Go od.Times.PLMN
Number of times downlink voice quality is Good for a specific operator in a cell
1526736671
L.Voice.VQI.AMR WB.UL.Good.Times .PLMN
Number of times uplink voice quality of AMRWB services is Good for a specific operator in a cell
1526736676
L.Voice.VQI.AMR WB.DL.Good.Times .PLMN
Number of times downlink voice quality of AMRWB services is Good for a specific operator in a cell
Table 9-10 Counters with the voice quality being Accept
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526728413
L.Voice.VQI.UL.Acc ept.Times
Number of times uplink voice quality is Accept
1526728418
L.Voice.VQI.DL.Acc ept.Times
Number of times downlink voice quality is Accept
1526732689
L.Voice.VQI.AMR WB.UL.Accept.Tim es
Number of times uplink voice quality of AMRWB services is Accept
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
85
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Counter ID
Counter Name
Counter Description
1526732694
L.Voice.VQI.AMR WB.DL.Accept.Tim es
Number of times downlink voice quality of AMRWB services is Accept
1526736662
L.Voice.VQI.UL.Acc ept.Times.PLMN
Number of times uplink voice quality is Accept for a specific operator in a cell
1526736667
L.Voice.VQI.DL.Acc ept.Times.PLMN
Number of times downlink voice quality is Accept for a specific operator in a cell
1526736672
L.Voice.VQI.AMR WB.UL.Accept.Tim es.PLMN
Number of times uplink voice quality of AMRWB services is Accept for a specific operator in a cell
1526736677
L.Voice.VQI.AMR WB.DL.Accept.Tim es.PLMN
Number of times downlink voice quality of AMRWB services is Accept for a specific operator in a cell
Table 9-11 Counters with the voice quality being Poor
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526728414
L.Voice.VQI.UL.Po or.Times
Number of times uplink voice quality is Poor
1526728419
L.Voice.VQI.DL.Po or.Times
Number of times downlink voice quality is Poor
1526732690
L.Voice.VQI.AMR WB.UL.Poor.Times
Number of times uplink voice quality of AMRWB services is Poor
1526732695
L.Voice.VQI.AMR WB.DL.Poor.Times
Number of times downlink voice quality of AMRWB services is Poor
1526732890
L.Voice.NormRel.U L.LowQuality
Number of normally released voice calls (poor uplink voice quality)
1526732891
L.Voice.NormRel.D L.LowQuality
Number of normally released voice calls (poor downlink voice quality)
1526736663
L.Voice.VQI.UL.Po or.Times.PLMN
Number of times uplink voice quality is Poor for a specific operator in a cell
1526736668
L.Voice.VQI.DL.Po or.Times.PLMN
Number of times downlink voice quality is Poor for a specific operator in a cell
1526736673
L.Voice.VQI.AMR WB.UL.Poor.Times. PLMN
Number of times uplink voice quality of AMRWB services is Poor for a specific operator in a cell
1526736678
L.Voice.VQI.AMR WB.DL.Poor.Times. PLMN
Number of times downlink voice quality of AMRWB services is Poor for a specific operator in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
86
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Table 9-12 Counters with the voice quality being Bad Counter ID
Counter Name
Counter Description
1526728415
L.Voice.VQI.UL.Ba d.Times
Number of times uplink voice quality is Bad
1526728420
L.Voice.VQI.DL.Ba d.Times
Number of times downlink voice quality is Bad
1526732691
L.Voice.VQI.AMR WB.UL.Bad.Times
Number of times uplink voice quality of AMRWB services is Bad
1526732696
L.Voice.VQI.AMR WB.DL.Bad.Times
Number of times downlink voice quality of AMRWB services is Bad
1526732892
L.Voice.UL.Silent.N um
Number of times uplink voice call is silent
1526732893
L.Voice.DL.Silent.N um
Number of times downlink voice call is silent
1526736664
L.Voice.VQI.UL.Ba d.Times.PLMN
Number of times uplink voice quality is Bad for a specific operator in a cell
1526736669
L.Voice.VQI.DL.Ba d.Times.PLMN
Number of times downlink voice quality is Bad for a specific operator in a cell
1526736674
L.Voice.VQI.AMR WB.UL.Bad.Times. PLMN
Number of times uplink voice quality of AMRWB services is Bad for a specific operator in a cell
1526736679
L.Voice.VQI.AMR WB.DL.Bad.Times. PLMN
Number of times downlink voice quality of AMRWB services is Bad for a specific operator in a cell
9.2.4.4 Voice Capacity Number of UEs with Voice Services Table 9-13 describes the counters used to monitor the number of UEs with voice services. Table 9-13 Counters used to monitor the number of UEs with voice services
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526728456
L.Traffic.ActiveUser.DL.QCI.1
Number of activated UEs with the QCI of 1 in the downlink buffer
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
87
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Counter ID
Counter Name
Counter Description
1526728446
L.Traffic.ActiveUser.UL.QCI.1
Number of activated UEs with the QCI of 1 in the uplink buffer
1526730601
L.Traffic.ActiveUser.DL.QCI.1.Max
Maximum number of activated UEs with the QCI of 1 in the downlink buffer
1526730611
L.Traffic.ActiveUser.UL.QCI.1.Max
Maximum number of activated UEs with the QCI of 1 in the uplink buffer
1526732721
L.Traffic.User.VoIP.Avg
Average number of VoIP UEs in a cell
1526732722
L.Traffic.User.VoIP.Max
Maximum number of VoIP UEs in a cell
1526736692
L.Traffic.User.VoIP.Avg.PLMN
Average number of VoIP UEs of a specific operator in a cell
1526736693
L.Traffic.User.VoIP.Max.PLMN
Maximum number of VoIP UEs of a specific operator in a cell
Number of PRBs Used by Voice Services Table 9-14 describes the counters used to monitor the average number of PRBs occupied by voice services. Table 9-14 Counters used to monitor the average number of PRBs occupied by voice services Counter ID
Counter Name
Counter Description
1526730883
L.ChMeas.PRB. DL.DrbUsed.Avg .VoIP
Average number of PRBs used by DRBs on the PDSCH for downlink VoIP services
1526730884
L.ChMeas.PRB. UL.DrbUsed.Avg .VoIP
Average number of PRBs used by DRBs on the PUSCH for uplink VoIP services
Throughput Table 9-15 and Table 9-16 describe the counters used to monitor the number of PDCCH CCEs used by voice services and total uplink/downlink traffic volume of voice services. Based on these counters, you can calculate the average uplink/downlink throughput of voice services. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
88
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Table 9-15 Counters used to monitor the number of PDCCH CCEs used by voice services Counter ID
Counter Name
Counter Description
1526736735
L.ChMeas.CCE.ULUsed. VoIP
Number of PDCCH CCEs used for uplink VoIP services
1526736736
L.ChMeas.CCE.DLUsed. VoIP
Number of PDCCH CCEs used for downlink VoIP services
Table 9-16 Counters used to monitor the total uplink/downlink traffic volume of voice services Counter ID
Counter Name
Counter Description
1526726776
L.Thrp.bits.UL.QCI.1
Uplink traffic volume for PDCP PDUs of services with the QCI of 1 in a cell
1526726803
L.Thrp.bits.DL.QCI.1
Downlink traffic volume for PDCP SDUs of services with the QCI of 1 in a cell
1526726777
L.Thrp.Time.UL.QCI.1
Receive duration of uplink PDCP PDUs for services with the QCI of 1 in a cell
1526726804
L.Thrp.Time.DL.QCI.1
Transmit duration of downlink PDCP SDUs for services with the QCI of 1 in a cell
1526727849
L.Thrp.bits.UL.PLMN.Q CI.1
Uplink traffic volume for PDCP PDUs of services with the QCI of 1 in a cell
1526727850
L.Thrp.Time.UL.PLMN. QCI.1
Receive duration of uplink PDCP PDUs for services with the QCI of 1 in a cell
1526728050
L.Thrp.bits.DL.PLMN.Q CI.1
Downlink traffic volume for PDCP SDUs of services with the QCI of 1 in a cell
1526728051
L.Thrp.Time.DL.PLMN. QCI.1
Transmit duration of downlink PDCP SDUs for services with the QCI of 1 in a cell
Average uplink throughput of services with a QCI of 1 = L.Thrp.bits.UL.QCI.1 / L.Thrp.Time.UL.QCI.1 Average downlink throughput of services with a QCI of 1 = L.Thrp.bits.DL.QCI.1 / L.Thrp.Time.DL.QCI.1 Average uplink throughput of services with a QCI of 1 for a specific operator = L.Thrp.bits.UL.PLMN.QCI.1 / L.Thrp.Time.UL.PLMN.QCI.1 Average downlink throughput of services with a QCI of 1 for a specific operator = L.Thrp.bits.DL.PLMN.QCI.1/ L.Thrp.Time.DL.PLMN.QCI.1
9.2.5 Parameter Optimization N/A Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
89
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.2.6 Troubleshooting If voice services cannot get through after VoLTE is deployed, troubleshoot as follows: 1.
Check whether the RRC connection procedure is normal.
2.
Check whether the attach procedure is normal.
3.
Check whether VoLTE is normally registered in the IMS.
4.
Check whether the VoLTE call request procedure is normal.
If the results of steps 1 and 2 are abnormal, the problem is caused by the eRAN instead of VoLTE. In this case, contact Huawei technical support. If the results of steps 3 and 4 are abnormal, check for parameter settings on the eRAN side. Specifically, check the following key parameters: Whether RLCPDCPPARAGROUP.DiscardTimer is set to DiscardTimer_Infinity and eNodeBAlgoSwitch.EutranVoipSupportSwitch is set to ON. l
If the parameter settings are incorrect, modify the parameter settings and perform the verification again.
l
If the parameter settings are incorrect, verify the following counters to check the packet loss rate for QCI of 5: –
If packet loss for QCI of 5 occurs, contact Huawei technical support.
–
Otherwise, the VoLTE fault is not caused by the eNodeB. In this case, troubleshoot the IMS, EPC, or transport network. Counter Name
Counter Description
L.Traffic.UL.PktLoss.Loss. QCI.5
Number of uplink PDCP SDUs discarded for services carried on DRBs with a QCI of 5 in a cell
L.Traffic.UL.PktLoss.Tot.Q CI.5
Number of expected uplink PDCP SDUs for services carried on DRBs with a QCI of 5 in a cell
L.Traffic.DL.PktUuLoss.Lo ss.QCI.5
Number of downlink PDCP SDUs discarded for services carried on DRBs with a QCI of 5 in a cell over the Uu interface
L.Traffic.DL.PktUuLoss.To t.QCI.5
Number of downlink PDCP SDUs transmitted for services carried on DRBs with a QCI of 5 in a cell over the Uu interface
9.3 Semi-Persistent Scheduling 9.3.1 When to Use Semi-Persistent Scheduling and Deploy Power Control Semi-Persistent Scheduling This feature is recommended to save cell CCE resources when the number of simultaneously active subscribers is greater than or equal to 10 and the PDCCH CCE usage exceeds 70%. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
90
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Semi-persistent scheduling uses fixed MCS and PRBs to transmit data during talk spurts instead of updating MCS and PRBs at each TTI. This brings gains and reduces required PDCCH resources. Therefore, semi-persistent scheduling is recommended in scenarios with low-speed or where channel conditions change slowly. In high-speed or ultra-high speed cells, UEs move fast and channel conditions change significantly. Therefore, semi-persistent scheduling is not recommended in such scenarios. Cells working at a bandwidth of 1.4 MHz have only six PRBs. When the UE uses semipersistent scheduling, the highest MCS index is only 15. This means that cell center users (CCUs) and users near the cell center consume more PRBs, which wastes PRB resources. Therefore, uplink and downlink semi-persistent scheduling and power control in uplink and downlink semi-persistent scheduling are not recommended in cells working at a bandwidth of 1.4 MHz.
Power Control in Semi-Persistent Scheduling When uplink semi-persistent scheduling is enabled, power control for uplink semi-persistent scheduling must be enabled so that uplink IBLER converges on the target value. The PDSCH transmit power is evenly allocated among RBs. Adjusting the PDSCH transmit power only when performing VoIP service cannot bring gains. Therefore, it is recommended that power control in downlink semi-persistent scheduling be disabled. When this type of power control is disabled, fixed PDSCH power allocation is used for UEs that are scheduled in a semi-persistent manner.
9.3.2 Required Information None
9.3.3 Deployment of Semi-Persistent Scheduling 9.3.3.1 Requirements Operating Environment UEs must support VoLTE, semi-persistent scheduling, and closed-loop power control in semipersistent scheduling. The EPC must support IMS.
Transmission Networking N/A
License The operator has purchased the license for this feature, and activated the license.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
91
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Feature ID
Feature Name
Model
License Control Item
NE
Sales Unit
LOFD-0010 16
VoIP Semipersistent Scheduling
LT1S00V OIP00
VoIP SemiPersistent Scheduling (FDD)
eNodeB
per RRC Connected User
9.3.3.2 Data Preparation There are three types of data sources: l
Network plan (negotiation not required): parameter values planned and set by the operator
l
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l
User-defined: parameter values set by users
The following table describes the parameters that must be set in the CellAlgoSwitch MO to set uplink and downlink semi-persistent scheduling for voice services. Parameter Name
Parameter ID
Data Source
Description
Uplink schedule switch
CellAlgoSwitch .UlSchSwitch
Network plan (negotiatio n not required)
SpsSchSwitch(SpsSchSwitch) of this parameter specifies whether to enable or disable uplink semi-persistent scheduling for voice services. To enable this feature, select the SpsSchSwitch(SpsSchSwitch) option. Set this parameter by referring to 9.3.1 When to Use SemiPersistent Scheduling and Deploy Power Control.
DL schedule switch
CellAlgoSwitch .DlSchSwitch
Network plan (negotiatio n not required)
SpsSchSwitch(SpsSchSwitch) of this parameter specifies whether to enable or disable downlink semi-persistent scheduling for voice services. To enable this feature, select the SpsSchSwitch(SpsSchSwitch) option. Set this parameter by referring to 9.3.1 When to Use SemiPersistent Scheduling and Deploy Power Control.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
92
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
The following table describes the parameters that must be set in the CellAlgoSwitch MO to set power control in uplink and downlink semi-persistent scheduling for voice services. Paramet er Name
Parameter ID
Data Source
Description
Uplink power control algorithm switch
CellAlgoSwitch. UlPcAlgoSwitch
Network plan (negotiation not required)
The CloseLoopSpsSwitch option of this parameter specifies whether to enable or disable power control in uplink semipersistent scheduling for voice services. To enable this feature, select the CloseLoopSpsSwitch option. Set this parameter by referring to 9.3.1 When to Use SemiPersistent Scheduling and Deploy Power Control.
Downlink power control algorithm switch
CellAlgoSwitch. DlPcAlgoSwitch
Network plan (negotiation not required)
The PdschSpsPcSwitch option of this parameter specifies whether to enable or disable power control in downlink semi-persistent scheduling for voice services. To enable this feature, select the PdschSpsPcSwitch option. Set this parameter by referring to 9.3.1 When to Use SemiPersistent Scheduling and Deploy Power Control.
9.3.3.3 Precautions If UL semi-persistent scheduling is enabled, it is recommended that CloseLoopSpsSwitch be turned on to enable closed-loop power control for the PUSCH to ensure the convergence of uplink IBLER. If downlink semi-persistent scheduling is enabled, turn off the PdschSpsPcSwitch to disable PDSCH power control in semi-persistent scheduling mode.
9.3.3.4 Hardware Adjustment None
9.3.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-17 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
93
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l
The managed objects (MOs) in Table 9-17 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l
Some MOs in Table 9-17 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Table 9-17 Parameters related to semi-persistent scheduling MO
Sheet in the Summary Data File
Parameter Group
Remarks
CellAlgoSwitch
CELLALGOSWITCH
LocalCellID, UlSchSwitch, UlPcAlgoSwitch, DlSchSwitch
Userdefined template
Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
94
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Using the CME to Perform Single Configuration On the CME, set the parameters listed in 9.3.3.2 Data Preparation for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 9-6, select the eNodeB to which the MOs belong. Figure 9-6 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. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End
Using MML Commands l
Uplink Semi-Persistent Scheduling Run the MOD CELLALGOSWITCH command to turn on the uplink semi-persistent scheduling switch.
l
Power Control in Uplink Semi-Persistent Scheduling Run the MOD CELLALGOSWITCH command with the PUSCH semi-persistent scheduling closed-loop power control switch turned on.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
95
eRAN VoLTE Feature Parameter Description
l
9 Engineering Guidelines
Downlink Semi-Persistent Scheduling Run the MOD CELLALGOSWITCH command turn on the downlink semi-persistent scheduling switch.
l
Power Control in Downlink Semi-Persistent Scheduling Run the MOD CELLALGOSWITCH command turn on the switch of closed-loop power control in downlink semi-persistent scheduling mode.
MML Command Examples MOD MOD MOD MOD
CELLALGOSWITCH: CELLALGOSWITCH: CELLALGOSWITCH: CELLALGOSWITCH:
LocalCellId=0, LocalCellId=0, LocalCellId=0, LocalCellId=0,
UlSchSwitch=SpsSchSwitch-1; DlSchSwitch=SpsSchSwitch-1; UlPcAlgoSwitch=CloseLoopSpsSwitch-1; DlPcAlgoSwitch=PdschSpsPcSwitch-0;
9.3.3.6 Activation Observation Uplink Semi-Persistent Scheduling To verify uplink semi-persistent scheduling for voice services, perform the following steps: Step 1 Run the LST CELLALGOSWITCH command to check whether uplink semi-persistent scheduling has been activated. LST CELLALGOSWITCH: LocalCellId=0;
Step 2 After the UE accesses the cell, use the UE to perform uplink voice services. Step 3 Start a task on the U2000 client to monitor MCS-specific scheduling statistics. 1.
On the U2000, choose Monitor > Signaling Trace > Signaling Trace Management.
2.
In the left pane of the Signaling Trace Management window, choose User Performance Monitoring > MCS Count Monitoring. Set the tracing duration, to-betraced MMEc (MME ID), and mTMSI(UE TMSI).
3.
Check the MCS-specific scheduling statistics, as shown in Figure 9-7. If the uplink MCS indexes are less than or equal to 15 and the number of uplink scheduling times is about 50, uplink semi-persistent scheduling is activated for the UE. (If the UE is not far from the eNodeB, the number of uplink scheduling times is about 50. If the UE is far from the eNodeB, the number is greater than 50 due to packet segmentation). Figure 9-7 Uplink MCS-specific scheduling statistics
4.
Issue 03 (2015-06-30)
In the left pane of the Signaling Trace Management window, choose Cell Performance Monitoring >Scheduled Users Statistic Monitoring. Set the tracing duration, to-be-traced NE information, and cell ID. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
96
eRAN VoLTE Feature Parameter Description
5.
9 Engineering Guidelines
On the U2000, check Total SPS ULSCH Users and Total SPS DLSCH Users, as shown in Figure 9-8. If the value of Total SPS ULSCH Users is greater than 0, UL semi-persistent scheduling is activated for the UE. If the value of Total SPS DLSCH Users is greater than 0, DL semi-persistent scheduling is activated for the UE. Figure 9-8 Example of statistics about scheduled UEs
6.
Use the following counters to check the status of uplink semi-persistent scheduling. Counter ID
Counter Name
Counter Description
1526728562
L.Sps.UL.Er rNum
Number of times of failed uplink semi-persistent scheduling transmission in a cell
1526728494
L.Sps.UL.Sc hNum
Number of times of uplink semi-persistent scheduling in a cell
----End
Downlink Semi-Persistent Scheduling To verify downlink semi-persistent scheduling for voice services, perform the following steps: Step 1 Run the LST CELLALGOSWITCH command to check whether downlink semi-persistent scheduling has been activated. LST CELLALGOSWITCH: LocalCellId=0;
Step 2 After the UE accesses the cell, use the UE to perform downlink voice services. 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 displayed window, choose User Performance Monitoring > MCS Count Monitoring. Set the tracing duration, to-be-traced MMEc (MME ID), and mTMSI(UE TMSI).
3.
Check the MCS-specific scheduling statistics, as shown in Figure 9-9. If the downlink MCS indexes are less than or equal to 15 and the number of downlink scheduling times is about 50, downlink semi-persistent scheduling has been performed for the UE.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
97
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Figure 9-9 Downlink MCS-specific scheduling statistics
4.
Use the following counters to check the status of downlink semi-persistent scheduling. Counter ID
Counter Name
Counter Description
1526728563
L.Sps.DL.ErrNum
Number of times of failed downlink semi-persistent scheduling transmission in a cell
1526728495
L.Sps.DL.SchNum
Number of times of downlink semipersistent scheduling in a cell
----End
Power Control in Uplink Semi-Persistent Scheduling To check whether the IBLER values can converge when closed-loop power control in PUSCH semi-persistent scheduling is enabled, perform the following steps: Step 1 Run the LST CELLALGOSWITCH command to check whether closed-loop power control in PUSCH semi-persistent scheduling is enabled. Step 2 After the UE accesses the cell, use the UE to perform uplink voice services. Step 3 Start an IBLER monitoring task on the U2000 client to monitor IBLER values. 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 IBLER values are less than 10%), the IBLER values converge. If the UE is close to the eNodeB, the IBLER values are relatively small. If the UE is far from the eNodeB, the IBLER values are relatively large. In the two cases, the IBLER values do not converge.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
98
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Figure 9-10 Uplink IBLER monitoring results
----End
Power Control in Downlink Semi-Persistent Scheduling Step 1 Run the LST CELLALGOSWITCH command to check whether power control in downlink semi-persistent scheduling is enabled. Step 2 If it is not enabled, run the following command to disable it: MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PdschSpsPcSwitch-0;
----End
9.3.3.7 Reconfiguration N/A
9.3.3.8 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-18. Table 9-18 Parameters related to semi-persistent scheduling MO
Sheet in the Summary Data File
Parameter Group
Remarks
CellAlgoSwitch
CELLALGOSWITCH
LocalCellID, UlSchSwitch,
Userdefined sheet
UlPcAlgoSwitch, DlSchSwitch Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
99
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Using the CME to Perform Single Configuration On the CME, set parameters according to the MOs listed in the related tables in each scenario. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands l
Uplink Semi-Persistent Scheduling Run the MOD CELLALGOSWITCH command with the uplink semi-persistent scheduling switch turned off. MML Command Examples MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SpsSchSwitch-0; MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch=CloseLoopSpsSwitch-0;
l
Downlink Semi-Persistent Scheduling Run the MOD CELLALGOSWITCH command with the downlink semi-persistent scheduling switch turned off. MML Command Examples MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=SpsSchSwitch-0; MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PdschSpsPcSwitch-0;
9.3.4 Performance Monitoring Semi-persistent scheduling reduces PDCCH consumption, increases voice service capacity, but slightly deteriorates voice service quality. You can compare counters in the following table given the same number of UEs in a cell, UE location, and traffic model. If the values for these counters decrease after semi-persistent scheduling is enabled, PDCCH consumption is reduced. Counter ID
Counter Name
Counter Description
1526728304
L.ChMeas.CCE.ULUsed
Number of PDCCH CCEs used for uplink DCI
1526728305
L.ChMeas.CCE.DLUsed
Number of PDCCH CCEs used for downlink DCI
For details about monitoring, see 9.2.4.4 Voice Capacity and 9.2.4.3 Voice Quality. Power control in semi-persistent scheduling impacts the voice quality of voice service users. For details, see 9.2.4.3 Voice Quality. NOTE
Power control in semi-persistent scheduling must work with semi-persistent scheduling.
9.3.5 Parameter Optimization N/A Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
100
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.3.6 Troubleshooting If the result of L.Sps.UL.ErrNum/L.Sps.UL.SchNum is relatively high (greater than 10%), check whether the CloseLoopSpsSwitch option of the CELLALGOSWITCH.UlPcAlgoSwitch parameter is selected: l
If the option is deselected, select this option.
l
If the option is selected, contact Huawei technical support.
9.4 TTI Bundling 9.4.1 When to Deploy TTI Bundling It is recommended that TTI bundling be enabled to improve the coverage of cell edges and in scenarios where indoor voice services are served by outdoor sites. This function is dependent on UEs. Therefore, a compatibility test is required before enabling this feature. The RRC Connection Reconfiguration message instructs UEs to enter or exit the TTI bundling state. UE channel conditions change significantly in high speed or ultra high speed scenarios. As a result, UEs frequently enter and exit the TTI bundling state, thereby increasing signaling load on the Uu interface, degrading voice quality, and increasing the risk of call drops. Therefore, it is recommended that TTI bundling be disabled in high speed or ultra high speed cells. Cells working at a bandwidth of 1.4 MHz have only six PRBs. TTI bundling consumes resources in the time domain. Therefore, it is recommended that TTI bundling be disabled in cells working at a bandwidth of 1.4 MHz.
9.4.2 Required Information None
9.4.3 Deployment of TTI Bundling 9.4.3.1 Requirements Operating Environment UEs must support VoLTE and TTI bundling, and the EPC must support IMS-based voice services.
Transmission Networking According to 3GPP specifications, TTI bundling is supported only by cells with subframe configuration 0, 1, or 6.
License The operator has purchased the license for this feature, and activated the license. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
101
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Feature ID
Feature Name
Model
License Control Item
NE
Sales Unit
LOFD-00104 8
TTI Bundling
LT1S00TT IB00
TTI Bundling (FDD)
eNodeB
per Cell
9.4.3.2 Data Preparation There are three types of data sources: l
Network plan (negotiation not required): parameter values planned and set by the operator
l
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l
User-defined: parameter values set by users
The following table describes the parameter that must be set in the CellAlgoSwitch and CellUlschAlgo MOs to set TTI bundling. Parameter Name
Parameter ID
Data Source
Setting Notes
Uplink schedule switch
CellAlgoSwitch.UlSch Switch
Network plan (negotiation not required)
The TtiBundlingSwitch(TtiBun dlingSwitch) option of this parameter specifies whether to enable TTI bundling. l In common scenarios, deselect this option. l When the UE's channel quality is poor and transmit power is limited, select this option.
TTI Bundling Trigger Strategy
CellUlschAlgo.TtiBun dlingTriggerStrategy
Network plan (negotiation not required)
This parameter specifies a TTI bundling trigger policy. l If TTI bundling applies only to VoLTE services, set this parameter to SERVICE_VOIP(SERV ICE_VOIP). l If TTI bundling applies to VoLTE or a combination of VoLTE and data, set this parameter to SERVICE_MULTIAPP( SERVICE_MULTIAPP) .
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
102
eRAN VoLTE Feature Parameter Description
Issue 03 (2015-06-30)
9 Engineering Guidelines
Parameter Name
Parameter ID
Data Source
Setting Notes
Statistic Num Threshold for TTIB Trigger
CellUlschAlgo.Statisti cNumThdForTtibTrig
Network plan (negotiation not required)
This parameter specifies a threshold number of consecutive times that the measured SINR is less than the target SINR. When the actual number reaches this threshold number, the eNodeB instructs the UE to enter the TTI bundling state. The default parameter value is recommended.
Statistic Num Threshold for TTIB Exit
CellUlschAlgo.Statisti cNumThdForTtibExit
Network plan (negotiation not required)
This parameter specifies a threshold number of consecutive times that the measured SINR is greater than the sum of the target SINR and the CellUlSchAlgo.HystToExitT tiBundling parameter value. When the actual number reaches this threshold number, the eNodeB instructs the UE to exit the TTI bundling state. The default parameter value is recommended.
Hysteresis to Exit TTI Bundling
CellUlschAlgo.HystTo ExitTtiBundling
Network plan (negotiation not required)
This parameter specifies an SINR threshold for exiting the TTI bundling state. This threshold is equal to the sum of the SINR threshold for entering the TTI bundling state and the CellUlschAlgo.HystToExitTt iBundling parameter value. The default value is recommended.
TTIB Max Number of RLC Segments
CellUlschAlgo.TtiBun dlingRlcMaxSegNum
Network plan (negotiation not required)
This parameter specifies the maximum number of uplink RLC segments for UEs in the TTI bundling state. The default value is recommended.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
103
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Parameter Name
Parameter ID
Data Source
Setting Notes
TTIB Max Number of HARQ Transmissions
CellUlschAlgo.TtiBun dlingHarqMaxTxNum
Network plan (negotiation not required)
This parameter specifies the maximum number of HARQ transmissions for UEs in the TTI bundling state. The default value is recommended.
9.4.3.3 Precautions None
9.4.3.4 Hardware Adjustment None
9.4.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-19 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l
The managed objects (MOs) in Table 9-19 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l
Some MOs in Table 9-19 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Table 9-19 Parameters related to TTI bundling
Issue 03 (2015-06-30)
MO
Sheet in the Summary Data File
Parameter Group
Remark s
CellAlgoSwitch
CELLALGOSWITCH
LocalCellID, UlSchSwitch
Userdefined template
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
104
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
MO
Sheet in the Summary Data File
Parameter Group
Remark s
CellUlschAlgo
CELLULSCHALGO
LocalCellID, TtiBundlingTriggerStrategy, StatisticNumThdForTtibTrig, StatisticNumThdForTtibExit, HystToExitTtiBundling, TtiBundlingRlcMaxSegNum, TtiBundlingHarqMaxTxNum
Userdefined template
Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End
Using the CME to Perform Single Configuration On the CME, set the parameters listed in 9.4.3.2 Data Preparation for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 9-11, select the eNodeB to which the MOs belong. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
105
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Figure 9-11 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. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End
Using MML Commands Step 1 Run the MOD CELLALGOSWITCH command to activate TTI bundling. Step 2 (Optional) Run the MOD CellULSCHALGO command and set parameters in 9.4.3.2 Data Preparation as required. ----End
MML Command Examples MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=TtiBundlingSwitch-1;
9.4.3.6 Activation Observation To verify TTI bundling for UEs far from the eNodeB, perform the following steps: Step 1 Run the LST CELLALGOSWITCH command to check whether TTI bundling has been activated. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
106
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Step 2 Start a Uu tracing task on the U2000 client. Select test cells when creating the task. Step 3 Enable a UE to access a cell and perform UL VoIP services. Step 4 Enable the UE to be far from the eNodeB until the RRC_CONN_RECFG and RRC_CONN_RECFG_CMP messages are present in the Uu tracing result. Check the IEs mac-MainConfig > ul-SCH-Config > ttiBundling in the RRC_CONN_RECFG message. The value TRUE (as shown in Figure 9-12) indicates that TTI bundling has been activated for UL VoIP. Figure 9-12 RRC_CONN_RECFG message (indicating that TTI bundling has been activated)
Step 5 Enable the UE to be close to the eNodeB. Check the IEs mac-MainConfig > ul-SCH-Config > ttiBundling in the RRC_CONN_RECFG message. The value FALSE (as shown in Figure 9-13) indicates that TTI bundling has been deactivated for UL VoIP.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
107
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Figure 9-13 RRC_CONN_RECFG message (indicating that TTI bundling has been deactivated)
Step 6 Use the following counters to check the status of TTI bundling. TTI bundling is enabled if the values of these counters are not 0. Counter ID
Counter Name
Counter Description
1526728496
L.Traffic.User.TtiBundling. Avg
Average number of UEs for which TTI bundling is enabled in a cell
1526728911
L.Signal.Num.TtiBundling. Enter
Number of messages that trigger the entering of the TTI bundling mode
1526728912
L.Signal.Num.TtiBundling. Exit
Number of messages that trigger the exiting of the TTI bundling mode
----End
9.4.3.7 Reconfiguration N/A
9.4.3.8 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-20. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
108
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Table 9-20 Parameters related to TTI bundling MO
Sheet in the Summary Data File
Parameter Group
Setti ng Note s
CellAlgoSwitch
CellAlgoSwitch
LocalCellID, UlSchSwitch
Userdefine d sheet
CellUlschAlgo
CellUlschAlgo
LocalCellID, TtiBundlingTriggerStrategy, StatisticNumThdForTtibTrig, StatisticNumThdForTtibExit, HystToExitTtiBundling, TtiBundlingRlcMaxSegNum, TtiBundlingHarqMaxTxNum
Userdefine d sheet
Using the CME to Perform Single Configuration On the CME, set parameters according to the MOs listed in the related tables in each scenario. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands Run the MOD CELLALGOSWITCH command to deactivate TTI bundling.
MML Command Examples MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=TtiBundlingSwitch-0;
9.4.4 Performance Monitoring TTI bundling improves uplink coverage for voice service users or improves uplink packet loss rate. For details, see 9.2.4.3 Voice Quality.
9.4.5 Parameter Optimization N/A
9.4.6 Troubleshooting N/A
9.5 UL RLC Segmentation Enhancement Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
109
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.5.1 When to Use Uplink RLC Segmentation Enhancement It is recommended that this feature be enabled for VoLTE to improve the cell edge coverage of the PUSCH.
9.5.2 Required Information None
9.5.3 Deployment 9.5.3.1 Requirements Operating Environment The EPC must support IMS-based voice services.
Transmission Networking N/A
License N/A
9.5.3.2 Data Preparation There are three types of data sources: l
Network plan (negotiation not required): parameter values planned and set by the operator
l
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l
User-defined: parameter values set by users
The following table describes the parameter that must be set in a CellUlschAlgo MO to enable uplink RLC segmentation enhancement for a cell.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
110
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Parameter Name
Parameter ID
Data Source
Setting Notes
Uplink Voip Rlc Maximum Segmentation Number
CellUlschAlgo.UlVoip RlcMaxSegNum
Network plan (negotiation not required)
This parameter controls whether to enable the uplink RLC segmentation enhancement feature for VoLTE services on UEs not in the TTI bundling state and specifies the maximum number of uplink RLC segments. l If this parameter is set to 0, this feature is disabled. l If this parameter is set to a non-zero value X, this feature is enabled and the maximum number of uplink RLC segments in the non-TTI-bundling state is X.
9.5.3.3 Precautions None
9.5.3.4 Hardware Adjustment None
9.5.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-21 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l
The MOs in Table 9-21 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l
Some MOs in Table 9-21 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
111
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Table 9-21 Parameters related to UL RLC segmentation enhancement MO
Sheet in the Summary Data File
Parameter Group
Remar ks
CELLULSCH ALGO
CELLULSCHALGO
LocalCellID,
Userdefined templat e
UlVoipRlcMaxSegNum
Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End
Using the CME to Perform Single Configuration On the CME, set the parameters listed in 9.5.3.2 Data Preparation for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 9-14, select the eNodeB to which the MOs belong. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
112
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Figure 9-14 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. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End
Using MML Commands Run the MOD CELLULSCHALGO command with the Uplink Voip Rlc Maximum Segmentation Number parameter set to the recommended value of the corresponding RAT.
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, UlVoipRlcMaxSegNum=20;
9.5.3.6 Activation Observation After uplink RLC segmentation enhancement is activated with the Uplink Voip Rlc Maximum Segmentation Number parameter set to a non-zero value, the MCS index should be increased for a UE at the cell edge to control the number of uplink RLC segments. To verify this, perform the following steps: Step 1 Run the LST CELLULSCHALGO command to check whether the Uplink Voip Rlc Maximum Segmentation Number parameter is set to 0. If it is set to 0, go to Step 2. If it is set to a non-zero value, run the following command to change it to 0 (x represents the local cell ID): Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
113
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
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 service on the UE. Step 3 Start a task on the U2000 client to monitor MCS-specific scheduling statistics. 1.
Choose Monitor > Signaling Trace > Signaling Trace Management.
2.
In the left navigation tree in the Signaling Trace Management tab page, choose User Performance Monitoring > MCS Count Monitoring. Set the monitoring duration and to-be-traced MMEc (MME ID), and mTMSI (UE TMSI).
3.
Observe MCS-specific uplink scheduling statistics, including the number of scheduling times and the number of RBs. Move the UE to the cell edge, where channel quality is poor. That is, move the UE until the monitoring result indicates that the MCS with an index of 0 is selected and a maximum of three RBs are allocated by uplink scheduling of the UE.
Step 4 Run the MOD CELLULSCHALGO command with the Uplink Voip Rlc Maximum Segmentation Number parameter set to a non-zero value. NOTE
To ensure satisfactory voice quality, you are advised to set the Uplink Voip Rlc Maximum Segmentation Number parameter to its recommended value. However, to facilitate this verification, you can set this parameter to a smaller non-zero value so that the selected MCS index increases noticeably.
Step 5 On the U2000 client, observe the MCS-specific uplink scheduling statistics. If the MCS index is greater than 0 but the number of RBs is still less than or equal to 3, the eNodeB has increased the MCS index to restrict the number of uplink RLC segments. (The smaller the value of Uplink Voip Rlc Maximum Segmentation Number, the larger the MCS index.) Step 6 On a live network, you can also check the packet loss rate of uplink voice services and the proportion of uplink low-order MCSs for the PUSCH (for example, MCS index 0 or 1). If both of them decrease, RLC segmentation enhancement has taken effect. Counter ID
Counter Name
Counter Description
1526727412
L.ChMeas.PUSCH.MCS.0
to 1526727443
to L.ChMeas.PUSCH.MCS.31
Number of times that MCS indexes 0 to 31 are used for PUSCH scheduling
1526727961
L.Traffic.UL.PktLoss.Loss.QCI. 1
Number of uplink PDCP SDUs discarded for services carried on DRBs with QCIs of 1 in a cell
1526727962
L.Traffic.UL.PktLoss.Tot.QCI.1
Number of expected uplink PDCP SDUs for services carried on DRBs with QCIs of 1 in a cell
----End
9.5.3.7 Reconfiguration N/A Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
114
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.5.3.8 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-22. Table 9-22 Parameters related to UL RLC segmentation enhancement MO
Sheet in the Summary Data File
Parameter Group
Rem arks
CellUlschAlgo
CELLULSCHALGO
LocalCellID, UlVoipRlcMaxSegNum
Userdefin ed templ ate
Using the CME to Perform Single Configuration On the CME, set parameters according to the MOs listed in the related tables in each scenario. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands Run the MOD CELLULSCHALGO command with the Uplink Voip Rlc Maximum Segmentation Number parameter set to 0.
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, UlVoipRlcMaxSegNum=0;
9.5.4 Performance Monitoring UL RLC segmentation enhancement improves UL packet loss rate of VoLTE services. Monitor the performance of this feature through the following counters.
Issue 03 (2015-06-30)
ID
Name
Description
1526727961
L.Traffic.UL.PktLoss.L oss.QCI.1
Total number of discarded uplink PDCP SDUs for DRB services with the QCI of 1 in a cell
1526727962
L.Traffic.UL.PktLoss.To t.QCI.1
Total number of expected uplink data packets for DRB services with the QCI of 1 in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
115
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.5.5 Parameter Optimization N/A
9.5.6 Troubleshooting N/A
9.6 Voice Characteristic Awareness Scheduling 9.6.1 When to Use Voice Characteristic Awareness Scheduling This feature is recommended when VoLTE has been deployed and the performance of VoLTE needs to be preferentially ensured.
9.6.2 Required Information None
9.6.3 Deployment 9.6.3.1 Requirements Operating Environment The EPC must support IMS-based voice services.
Transmission Networking N/A
License The operator has purchased the license for this feature, and activated the license. Feature ID
Feature Name
Model
License Control Item
NE
Sales Unit
LOFD-08122 9
Voice Characteristic Awareness Scheduling
LT1S0 0VCA S00
Voice Characteristic Awareness Scheduling(FDD)
eNodeB
per Cell
9.6.3.2 Data Preparation There are three types of data sources: l
Issue 03 (2015-06-30)
Network plan (negotiation not required): parameter values planned and set by the operator Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
116
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
l
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l
User-defined: parameter values set by users
The following table describes the parameter that must be set in the CELLULSCHALGO to configure Voice Characteristic Awareness Scheduling for a cell.
Issue 03 (2015-06-30)
Parameter ID
Data Source
Setting Notes
CELLULSCHALGO.UlDe laySchStrategy
Network plan (negotiation not required)
This parameter specifies a policy for uplink delay-based dynamic scheduling. If this parameter is set to NO_DELAYSCH, uplink delaybased dynamic scheduling is disabled. If this parameter is set to VOIP_DELAYSCH, uplink delaybased dynamic scheduling for VoIP is enabled. The eNodeB adjusts scheduling priorities based on VoIP packet delays during uplink dynamic scheduling, thereby increasing the MOS and VoIP capacity when the cell is heavily loaded.
CELLULSCHALGO.UlEn hencedVoipSchSw
Network plan (negotiation not required)
The UlVoLTEDataSizeEstSwitch option of the CELLULSCHALGO.UlEnhence dVoipSchSw parameter specifies whether to enable uplink VoLTE volume estimation for dynamic scheduling. This estimation function shortens VoLTE packet delays, reduces the packet loss rate, and improves voice quality.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
117
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Parameter ID
Data Source
Setting Notes
eNBCellRsvdPara.RsvdSw Para3
Network plan (negotiation not required)
l When the RsvdSwPara3_bit1 option of the eNBCellRsvdPara.RsvdSwPar a3 parameter is selected and the data scheduling wait time is the same, the SR scheduling priority for UEs with QCI of 1 is higher than that for UEs without QCI of 1. l When the RsvdSwPara3_bit1 option of the eNBCellRsvdPara.RsvdSwPar a3 parameter is deselected, the eNodeB sorts the priorities of scheduling triggered by SR and BSR of VoLTE services. A longer scheduling wait time indicates a higher scheduling priority.
9.6.3.3 Precautions None
9.6.3.4 Hardware Adjustment None
9.6.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-23 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l
The MOs in Table 9-23 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l
Some MOs in Table 9-23 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
118
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Table 9-23 Parameters related to voice characteristic awareness scheduling MO
Sheet in the Summary Data File
Parameter Group
Remar ks
CellUlschAlgo
CellUlschAlgo
LocalCellId, UlDelaySchStrategy
Userdefined templat e
CellUlschAlgo
CellUlschAlgo
LocalCellID, UlEnhencedVoipSchSw, UlVoLTEDataSizeEstSwitch,
Userdefined templat e
Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End
Using the CME to Perform Single Configuration On the CME, set the parameters listed in 9.6.3.2 Data Preparation for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
119
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Step 2 In area 1 shown in Figure 9-15, select the eNodeB to which the MOs belong. Figure 9-15 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. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End
Using MML Commands Step 1 Run the MOD CELLULSCHALGO command to enable uplink delay-based dynamic scheduling. Step 2 Run the MOD CELLULSCHALGO command to enable uplink VoLTE volume estimation for dynamic scheduling. ----End
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, UlDelaySchStrategy=VOIP_DELAYSCH; MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoLTEDataSizeEstSwitch-1;
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
120
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.6.3.6 Activation Observation Step 1 On the U2000 client, start performance monitoring tasks for counters listed in Table 9-24. Step 2 On the U2000 client, check the the number of CCEs allocated for uplink QCI 1 services and the duration of receiving uplink QCI 1 data at the PDCP layer before and after the feature is enabled. If both of them increase, uplink VoLTE volume estimation for dynamic scheduling has been activated. In addition, check the proportion of VQIs that indicate poor or bad voice quality. If the proportion decreases, uplink delay-based dynamic scheduling have been activated. Table 9-24 Counters for monitoring Voice Characteristic Awareness Scheduling Counter ID
Counter Name
Counter Description
1526736735
L.ChMeas.CCE.ULUsed.VoIP
Number of PDCCH CCEs allocated to uplink VoIP
1526726777
L.Thrp.Time.UL.QCI.1
Duration of receiving uplink PDCP PDUs for services with QCIs of 1 in a cell
1526728411
L.Voice.VQI.UL.Excellent.Time s
Number of times uplink voice quality is Excellent
1526728412
L.Voice.VQI.UL.Good.Times
Number of times uplink voice quality is Good
1526728413
L.Voice.VQI.UL.Accept.Times
Number of times uplink voice quality is Accept
1526728414
L.Voice.VQI.UL.Poor.Times
Number of times uplink voice quality is Poor
1526728415
L.Voice.VQI.UL.Bad.Times
Number of times uplink voice quality is Bad
----End
9.6.3.7 Reconfiguration N/A
9.6.3.8 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-25. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
121
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Table 9-25 Parameters related to voice characteristic awareness scheduling MO
Sheet in the Summary Data File
Parameter Group
Rem arks
CellUlschAlgo
CellUlschAlgo
LocalCellID, UlDelaySchStrategy
Userdefin ed templ ate
CellUlschAlgo
CellUlschAlgo
LocalCellID, UlEnhencedVoipSchSw
Userdefin ed templ ate
Using the CME to Perform Single Configuration On the CME, set parameters according to the MOs listed in the related tables in each scenario. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands Run the MOD CELLULSCHALGO command to disable uplink delay-based dynamic scheduling. Run the MOD CELLULSCHALGO command to disable uplink VoLTE volume estimation for dynamic scheduling. Run the MOD CELLULSCHALGO command with the uplink VoIP delay scheduling switch turned off.
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, UlDelaySchStrategy=NO_DELAYSCH; MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoLTEDataSizeEstSwitch-0;
9.6.4 Performance Monitoring After voice characteristic awareness scheduling is enabled, you can use the following counters to monitor whether the uplink VoLTE packet loss rate decreases.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526727961
L.Traffic.UL.PktLoss.L oss.QCI.1
Number of uplink PDCP SDUs discarded for services carried on DRBs with QCIs of 1 in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
122
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Counter ID
Counter Name
Counter Description
1526727962
L.Traffic.UL.PktLoss.T ot.QCI.1
Number of expected uplink PDCP SDUs for services carried on DRBs with QCIs of 1 in a cell
9.6.5 Parameter Optimization N/A
9.6.6 Troubleshooting N/A
9.7 Uplink Compensation Scheduling 9.7.1 When to Use Uplink Compensation Scheduling If VoLTE has been deployed, it is recommended that uplink compensation scheduling be enabled to reduce the number of uplink VoLTE packet losses in heavy traffic scenarios.
9.7.2 Required Information None
9.7.3 Deployment 9.7.3.1 Requirements Operating Environment The EPC must support IMS-based voice services.
Transmission Networking N/A
License N/A
9.7.3.2 Data Preparation There are three types of data sources: l
Issue 03 (2015-06-30)
Network plan (negotiation not required): parameter values planned and set by the operator Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
123
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
l
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l
User-defined: parameter values set by users
The following table describes the parameters that must be set in the CELLULSCHALGO MO to enable or disable uplink compensation scheduling for a cell. Parameter Name
Parameter ID
Data Source
Setting Notes
Uplink Enhanced Voip Schedule Switch
CELLULSCHALGO. UlEnhencedVoipSchS w
Network plan (negotiation not required)
The UlVoipSchOptSwitch of the CELLULSCHALGO.UlEn hencedVoipSchSw parameter specifies whether to enable uplink compensation scheduling. l When this switch is turned off, the function does not take effect. l When this switch is turned on, uplink dynamic scheduling is triggered if the scheduling interval exceeds a threshold. The scheduling interval is a period during which a VoLTE user is not dynamically scheduled in the uplink. In this way, VoLTE users can be timely scheduled in the uplink and the number of PDCP packet losses due to discard timer expiry can be reduced even in heavy traffic scenarios.
9.7.3.3 Precautions None
9.7.3.4 Hardware Adjustment None
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
124
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.7.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-26 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l
The MOs in Table 9-26 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l
Some MOs in Table 9-26 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters. Table 9-26 Parameters related to uplink compensation scheduling MO
Sheet in the Summary Data File
Parameter Group
Remar ks
CellUlschAlgo
CELLULSCHALGO
LocalCellID,
Userdefined templat e
UlEnhencedVoipSchSw.UlV oipSchOptSwitch
Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
125
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End
Using the CME to Perform Single Configuration On the CME, set the parameters listed in 9.7.3.2 Data Preparation for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 9-16, select the eNodeB to which the MOs belong. Figure 9-16 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. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
126
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Using MML Commands Run the MOD CELLULSCHALGO command to enable uplink compensation scheduling.
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoipSchOptSwitch-1;
9.7.3.6 Activation Observation Step 1 Run the LST CELLULSCHALGO command to check whether the UlVoipSchOptSwitch is turned off. If the switch is turned on, run the following command to turn it off. If the switch has been turned off, go to Step 2. 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 and L.ChMeas.CCE.ULUsed.VoIP; if these values increase, this feature has been activated. In addition, check the uplink VoIP packet loss rate (calculated based on L.Traffic.UL.PktLoss.Loss.QCI.1 and L.Traffic.UL.PktLoss.Loss.QCI.1) to see the effect of this feature. Table 9-27 Counters Counter ID
Counter Name
Counter Description
1526736735
L.ChMeas.CCE.ULUsed.VoIP
Number of PDCCH CCEs allocated to uplink VoIP
1526726777
L.Thrp.Time.UL.QCI.1
Receive duration of uplink PDCP PDUs for services with the QCI of 1 in a cell
1526727961
L.Traffic.UL.PktLoss.Loss.QCI.1
Number of uplink PDCP SDUs discarded for services carried on DRBs with QCIs of 1 in a cell
1526727962
L.Traffic.UL.PktLoss.Tot.QCI.1
Number of expected uplink PDCP SDUs for services carried on DRBs with QCIs of 1 in a cell
----End
9.7.3.7 Reconfiguration N/A Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
127
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.7.3.8 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-28. Table 9-28 Parameters related to uplink compensation scheduling MO
Sheet in the Summary Data File
Parameter Group
Remar ks
CellUlschAlgo
CellUlschAlgo
LocalCellID, UlEnhencedVoipSchSw.Ul VoipSchOptSwitch
Userdefined templat e
Using the CME to Perform Single Configuration On the CME, set parameters according to the MOs listed in the related tables in each scenario. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands Run the MOD CELLULSCHALGO command to disable uplink compensation scheduling.
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, UlEnhencedVoipSchSw=UlVoipSchOptSwitch-0;
9.7.4 Performance Monitoring After uplink compensation scheduling is enabled, you can use the following counters to monitor whether the uplink VoLTE packet loss rate decreases.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526727961
L.Traffic.UL.PktLoss.L oss.QCI.1
Number of uplink PDCP SDUs discarded for services carried on DRBs with QCIs of 1 in a cell
1526727962
L.Traffic.UL.PktLoss.T ot.QCI.1
Number of expected uplink PDCP SDUs for services carried on DRBs with QCIs of 1 in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
128
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.7.5 Parameter Optimization N/A
9.7.6 Troubleshooting N/A
9.8 Voice-Specific AMC 9.8.1 When to Use Voice-Specific AMC If VoLTE has been deployed, it is recommended that voice-specific AMC be used. You are advised to configure this feature based on the number of VoLTE users and capacity policies. For example, if the number of online VoLTE users is small and VoLTE performance needs to be preferentially ensured, it is recommended that a small target IBLER be configured for VoLTE users.
9.8.2 Required Information None
9.8.3 Deployment 9.8.3.1 Requirements Operating Environment The EPC must support IMS-based voice services.
Transmission Networking N/A
License None
9.8.3.2 Data Preparation There are three types of data sources: l
Network plan (negotiation not required): parameter values planned and set by the operator
l
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l
User-defined: parameter values set by users
The following table describes the parameter that must be set in the CELLULSCHALGO to configure Voice-Specific AMC for a cell. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
129
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Parameter Name
Parameter ID
Data Source
Setting Notes
SINR Adjustment Target IBLER for VoLTE
CELLULSCHALGO. SinrAdjTargetIblerforVoLTE
Network plan (negotiation not required)
This parameter specifies a target IBLER for adjusting the SINRs used in dynamic scheduling of VoLTE users not in the TTI bundling state. It is recommended that this parameter be set to a value less than or equal to 10% in light-traffic scenarios and to 10% in heavy-traffic scenarios.
9.8.3.3 Precautions None
9.8.3.4 Hardware Adjustment None
9.8.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-29 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l
The MOs in Table 9-29 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l
Some MOs in Table 9-29 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
130
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Table 9-29 Parameters related to voice-specific AMC MO
Sheet in the Summary Data File
Parameter Group
Remar ks
CELLULSCH ALGO
CELLULSCHALGO
LocalCellID,
Userdefined templat e
SinrAdjTargetIblerforVoLTE
Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End
Using the CME to Perform Single Configuration On the CME, set the parameters listed in 9.8.3.2 Data Preparation for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 9-17, select the eNodeB to which the MOs belong. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
131
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Figure 9-17 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. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End
Using MML Commands Run the MOD CELLULSCHALGO to set a target IBLER for adjusting VoLTE SINRs.
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, SinrAdjTargetIblerforVoLTE=3;
9.8.3.6 Activation Observation Step 1 Run the LST CELLULSCHALGO command to check whether the value of SINR target IBLER adjustment is 10. If the value is not 10, run the following command to change it. If the value is 10, go to Step 2. 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 SINR adjustment to a value rather than 10. Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
132
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
NOTE
To ensure voice performance, you are advised to set the target IBLER to the recommended value. To facilitate activation observation, you can also set it to a smaller non-zero value so that a more obvious IBLER decrease can be seen.
Step 5 On the U2000 client, check the values of the counters listed in Table 9-30. If the uplink IBLER of QCI 1 services (calculated using the following formula) converges on the target IBLER, this feature has been activated.
Table 9-30 Counters Counter ID
Counter Name
Counter Description
1526737730
L.Traffic.UL.SCH.QPSK.ErrT B.Ibler.QCI.1
Number of erroneously transmitted QCI 1 service TBs on the UL-SCH during the initial transmission in QPSK modulation mode
1526737731
L.Traffic.UL.SCH. 16QAM.ErrTB.Ibler.QCI.1
Number of erroneously transmitted QCI 1 service TBs on the UL-SCH during the initial transmission in 16 Quadrature Amplitude Modulation (16QAM) modulation mode
1526737732
L.Traffic.UL.SCH. 64QAM.ErrTB.Ibler.QCI.1
Number of erroneously transmitted QCI 1 service TBs on the UL-SCH during the initial transmission in 64QAM modulation mode
1526737724
L.Traffic.UL.SCH.QPSK.TB.Q CI.1
Number of initially transmitted QCI 1 service TBs on the ULSCH in QPSK modulation mode
1526737725
L.Traffic.UL.SCH. 16QAM.TB.QCI.1
Number of initially transmitted QCI 1 service TBs on the ULSCH in 16QAM modulation mode
1526737726
L.Traffic.UL.SCH. 64QAM.TB.QCI.1
Number of initially transmitted QCI 1 service TBs on the ULSCH in 64QAM modulation mode
----End
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
133
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
9.8.3.7 Reconfiguration N/A
9.8.3.8 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-31. Table 9-31 Parameters related to voice-specific AMC MO
Sheet in the Summary Data File
Parameter Group
Rem arks
CellUlschAlgo
CellUlschAlgo
LocalCellID, SinrAdjTargetIblerforVoLTE
Userdefin ed templ ate
Using the CME to Perform Single Configuration On the CME, set parameters according to the MOs listed in the related tables in each scenario. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands Run the MOD CELLULSCHALGO command to set the target IBLER for VoLTE SINR adjustment to 10.
MML Command Examples MOD CELLULSCHALGO: LocalCellId=0, SinrAdjTargetIblerforVoLTE=10;
9.8.4 Performance Monitoring After voice-specific AMC is enabled, you can use the following counters to monitor whether the uplink VoLTE packet loss rate decreases.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
1526727961
L.Traffic.UL.PktLoss.L oss.QCI.1
Number of uplink PDCP SDUs discarded for services carried on DRBs with QCIs of 1 in a cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
134
eRAN VoLTE Feature Parameter Description
9 Engineering Guidelines
Counter ID
Counter Name
Counter Description
1526727962
L.Traffic.UL.PktLoss.T ot.QCI.1
Number of expected uplink PDCP SDUs for services carried on DRBs with QCIs of 1 in a cell
9.8.5 Parameter Optimization N/A
9.8.6 Troubleshooting N/A
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
135
eRAN VoLTE Feature Parameter Description
10 Parameters
10
Parameters
Table 10-1 Parameters MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
VQMAl go
VqiExce llentThd
MOD VQMA LGO
None
None
Meaning: Indicates the voice quality indicator (VQI) threshold above which the voice quality is considered as excellent.
LST VQMA LGO
GUI Value Range: 0~500 Unit: None Actual Value Range: 0~5, step:0.01 Default Value: 400
VQMAl go
VqiPoor Thd
MOD VQMA LGO LST VQMA LGO
None
None
Meaning: Indicates the voice quality indicator (VQI) threshold for determining the voice quality is poor. If the VQI evaluation value is greater than the VqiBadThd parameter value and less than or equal to the VqiPoorThd parameter value, the voice quality is considered as poor. If the VQI evaluation value is less than or equal to the VqiGoodThd parameter value and greater than the VqiPoorThd parameter value, the voice quality is considered as accepted. GUI Value Range: 0~500 Unit: None Actual Value Range: 0~5, step:0.01 Default Value: 200
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
136
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
VQMAl go
VqiGoo dThd
MOD VQMA LGO
None
None
Meaning: Indicates the voice quality indicator (VQI) threshold for determining the voice quality is good. If the VQI evaluation value is greater than the VqiGoodThd parameter value and less than or equal to the VqiExcellentThd parameter value, the voice quality is considered as good. If the VQI evaluation value is less than or equal to the VqiGoodThd parameter value and greater than the VqiPoorThd parameter value, the voice quality is considered as accepted.
LST VQMA LGO
GUI Value Range: 0~500 Unit: None Actual Value Range: 0~5, step:0.01 Default Value: 300 VQMAl go
VqiBad Thd
MOD VQMA LGO LST VQMA LGO
None
None
Meaning: Indicates the voice quality indicator (VQI) threshold equal to or below which the voice quality is considered as bad. GUI Value Range: 0~500 Unit: None Actual Value Range: 0~5, step:0.01 Default Value: 100
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
137
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
GlobalP rocSwitc h
VoipWit hGapMo de
MOD GLOBA LPROC SWITC H
LOFD-0 02001 / TDLOF D-00200 1
Meaning:
LST GLOBA LPROC SWITC H
LOFD-0 02002 / TDLOF D-00200 2
Automat ic Neighbo ur Relation (ANR)
LOFD-0 02007 / TDLOF D-00200 7 MRFD231808
InterRAT ANR PCI Collisio n Detectio n& SelfOptimiz ation GSM and LTE Buffer Zone Optimiz ation(LT E)
Indicates whether VoIP UEs are allowed to enter the periodical measurement gap and whether they can exit the gap if VoIP services are initiated during the gap. A VoIP UE can enter the periodical measurement gap during GSM and LTE buffer zone optimization or periodic inter-frequency/RAT measurements in cell tracing. If a UE enters the measurement gap and then VoIP services are initiated for this UE, fast ANR, active PCI conflict detection, GSM and LTE buffer zone optimization, or periodic inter-frequency/RAT measurements in cell tracing can trigger the UE's exiting from the gap. If this parameter is set to ENBALE, VoIP UEs are allowed to enter the periodic measurement gap during GSM and LTE buffer zone optimization and periodic inter-frequency/RAT measurement in cell tracing. The parameter setting does not affect the entering of the gap during fast ANR and active PCI conflict detection for VoIP UEs. If this parameter is set to DISABLE, VoIP UEs are prohibited to enter the periodic measurement gap and the UEs entering the gap and initiating VoIP services cannot exit the gap. GUI Value Range: DISABLE(disable), ENABLE(enable) Unit: None Actual Value Range: DISABLE, ENABLE Default Value: ENABLE(enable)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
138
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
TtiBund lingTrig gerStrat egy
MOD CELLU LSCHA LGO
LOFD-0 01048
TTI Bundlin g
Meaning:
LST CELLU LSCHA LGO
Indicates the policy of triggering transmission time interval (TTI) bundling when TtiBundlingSwitch of the UlSchSwitch parameter is on. If this parameter is set to SERVICE_VOIP, the eNodeB triggers TTI bundling for UEs running only VoIP services in the uplink. If this parameter is set to SERVICE_MULTIAPP, the eNodeB triggers TTI bundling for all UEs running VoIP services, including UEs running only VoIP services and UEs running both VoIP services and data services in the uplink. GUI Value Range: SERVICE_VOIP(SERVICE_VOIP), SERVICE_MULTIAPP(SERVICE_MULTIAPP) Unit: None Actual Value Range: SERVICE_VOIP, SERVICE_MULTIAPP Default Value: SERVICE_VOIP(SERVICE_VOIP)
CellUlsc hAlgo
Statistic NumTh dForTtib Trig
MOD CELLU LSCHA LGO LST CELLU LSCHA LGO
LOFD-0 01048
TTI Bundlin g
Meaning: Indicates the threshold of channel quality statistic times during which the channel quality of a UE consistently meets conditions for entering transmission time interval (TTI) bundling. Before a UE enters TTI bundling, the eNodeB performs statistic on the channel quality of the UE at the interval of 20 ms or longer. If the number of statistic times during which the channel quality of the UE consistently meets conditions for entering TTI bundling is greater than this parameter value, the UE enters TTI bundling. This parameter helps delay the time for entering TTI bundling and decrease the probability of unnecessary TTI bundling entering caused by wireless signal fluctuation. This parameter applies only to LTE FDD networks. GUI Value Range: N5_TTIB_ENTER(5), N10_TTIB_ENTER(10), N15_TTIB_ENTER(15), N20_TTIB_ENTER(20) Unit: None Actual Value Range: N5_TTIB_ENTER, N10_TTIB_ENTER, N15_TTIB_ENTER, N20_TTIB_ENTER Default Value: N10_TTIB_ENTER(10)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
139
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
Statistic NumTh dForTtib Exit
MOD CELLU LSCHA LGO
LOFD-0 01048
TTI Bundlin g
Meaning: Indicates the threshold of channel quality statistic times during which the channel quality of a UE consistently meets conditions for exiting from transmission time interval (TTI) bundling. Before a UE exits from TTI bundling, the eNodeB performs statistic on the channel quality of the UE at the interval of 20 ms or longer. If the number of statistic times during which the channel quality of the UE consistently meets conditions for exiting from TTI bundling is greater than this parameter value, the UE exits TTI bundling. This parameter helps delay the time for UEs to exit from TTI bundling and decrease the probability of unnecessary exit from TTI bundling caused by wireless signal fluctuation. This parameter applies only to LTE FDD networks.
LST CELLU LSCHA LGO
GUI Value Range: N10_TTIB_EXIT(10), N20_TTIB_EXIT(20), N40_TTIB_EXIT(40), N80_TTIB_EXIT(80) Unit: None Actual Value Range: N10_TTIB_EXIT, N20_TTIB_EXIT, N40_TTIB_EXIT, N80_TTIB_EXIT Default Value: N20_TTIB_EXIT(20) CellUlsc hAlgo
HystToE xitTtiBu ndling
MOD CELLU LSCHA LGO LST CELLU LSCHA LGO
LOFD-0 01048
TTI Bundlin g
Meaning: Indicates the hysteresis of the signal to interference plus noise ratio (SINR) threshold for exiting from transmission time interval (TTI) bundling against the SINR threshold for entering TTI bundling. The hysteresis decreases the probability of unnecessary exit from TTI bundling caused by wireless signal fluctuation. This parameter applies only to LTE FDD networks. GUI Value Range: 3~6 Unit: None Actual Value Range: 3~6 Default Value: 5
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
140
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
TtiBund lingRlc MaxSeg Num
MOD CELLU LSCHA LGO
LOFD-0 01048
TTI Bundlin g
Meaning: Indicates whether to apply upper limit control on service data unit (SDU) segmentation at the radio link control (RLC) layer in the uplink for services scheduled in transmission time interval (TTI) bundling mode and the maximum SDU segments at the RLC layer. If this parameter is set to 0, the upper limit control on SDU segmentation at the RLC layer is disabled in the uplink for services scheduled in TTI bundling mode. If this parameter is set to a non-zero value X, upper limit control on SDU segmentation at the RLC layer is enabled and a maximum of X SDU segments that can be divided for services in uplink dynamic scheduling in TTI bundling mode. This parameter applies only to LTE FDD networks.
LST CELLU LSCHA LGO
GUI Value Range: 0~7 Unit: None Actual Value Range: 0~7 Default Value: 4 CellUlsc hAlgo
TtiBund lingHarq MaxTx Num
MOD CELLU LSCHA LGO LST CELLU LSCHA LGO
LOFD-0 01048 / TDLOF D-00104 8
TTI Bundlin g
Meaning: Indicates the maximum transmission times of hybrid automatic repeat requests (HARQs) based on transmission time interval (TTI) in the uplink. For details, see 3GPP TS 36.331. GUI Value Range: n4(4), n8(8), n12(12), n16(16), n20(20), n24(24), n28(28) Unit: None Actual Value Range: n4, n8, n12, n16, n20, n24, n28 Default Value: n16(16)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
141
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
UlDelay SchStrat egy
MOD CELLU LSCHA LGO
LOFD-0 0101502 / TDLOF D-00101 502
Dynami c Scheduli ng
Meaning: Indicates whether to enable delay-based dynamic scheduling prioritization for VoIP services. If this parameter is set to NO_DELAYSCH, delay-based dynamic scheduling prioritization for VoIP services is disabled. If this parameter is set to VOIP_DELAYSCH, delay-based dynamic scheduling prioritization for VoIP services is enabled. Scheduling priorities are dynamically adjusted based on VoIP packet delays during uplink dynamic scheduling, thereby increasing the mean opinion score (MOS) and system capacity for VoIP services when the cell is heavily loaded with VoIP services.
LST CELLU LSCHA LGO
GUI Value Range: NO_DELAYSCH(No Delay Scheduling), VOIP_DELAYSCH(VoIP Service Delay Scheduling) Unit: None Actual Value Range: NO_DELAYSCH, VOIP_DELAYSCH Default Value: NO_DELAYSCH(No Delay Scheduling)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
142
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
UlEnhen cedVoip SchSw
MOD CELLU LSCHA LGO
LOFD-0 81229
Voice Characte ristic Awarene ss Scheduli ng
Meaning:
LST CELLU LSCHA LGO
Indicates whether to enable uplink pre-scheduling, include UlVoipPreAllocationSwtich(Bit0), UlVoipDelaySchSwitch(Bit1), UlVoIPLoadBasedSchSwitch(Bit2), UlVoipSchOptSwitch(Bit3), and UlVoLTEDataSizeEstSwitch(Bit4). UlVoipPreAllocationSwtich: This switch controls whether to schedule VoIP UEs during talk spurts when the number of online UEs exceeds 50 in a cell. If this switch is off, voice preallocation is not performed. If this switch is on, voice preallocation is performed. This switch applies only to LTE FDD networks. UlVoipDelaySchSwitch: This switch controls whether to schedule VoIP UEs based on delays when there are a large number of VoIP UEs and these UEs are evenly distributed. If this switch is turned off, delay-based scheduling is not performed. If this switch is turned on, the scheduling priorities are calculated based on delays. This switch applies only to LTE TDD networks. UlVoIPLoadBasedSchSwitch: Indicates whether to enable adaptive selection of VoIP scheduling mode based on the cell load. There are two scheduling modes: dynamic scheduling and semi-persistent scheduling. If this switch is off, adaptive selection of dynamic and semi-persistent scheduling cannot be performed for UEs running voice services based on the cell load. If this switch is off, dynamic and semipersistent scheduling can be adaptively selected for UEs running voice services based on the cell load. This switch applies only to LTE TDD cells. UlVoipSchOptSwitch: Indicates whether to enable scheduling optimization for VoIP services in the uplink. If this option is deselected, this function is disabled. If this option is selected, an uplink dynamic scheduling is triggered for VoIP UEs adopting uplink dynamic scheduling when the scheduling interval is greater than the uplink scheduling interval threshold for VoIP UEs. This ensures timely uplink scheduling on voice services even when SR missing detection occurs, thereby avoiding packet loss caused by the expiration of the PDCP packet discarding timer. UlVoLTEDataSizeEstSwitch: Indicates whether to enable the estimation of traffic volume dynamically
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
143
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
scheduled for VoLTE services in the uplink.If this option is deselected, this function is disabled. If this option is selected, the eNodeB estimates the uplink traffic volume that is dynamically scheduled for VoLTE services, which shortens the VoLTE packet delay, reduces the packet loss rate, improves the voice service quality. GUI Value Range: UlVoipPreAllocationSwtich(UlVoipPreAllocationSwtich), UlVoipDelaySchSwitch(UlVoipDelaySchSwitch), UlVoIPLoadBasedSchSwitch(UlVoIPLoadBasedSchSwitch), UlVoipSchOptSwitch(UlVoipSchOptSwitch), UlVoLTEDataSizeEstSwitch(UlVoLTEDataSizeEstSwitch) Unit: None Actual Value Range: UlVoipPreAllocationSwtich, UlVoipDelaySchSwitch, UlVoIPLoadBasedSchSwitch, UlVoipSchOptSwitch, UlVoLTEDataSizeEstSwitch Default Value: UlVoipPreAllocationSwtich:Off, UlVoipDelaySchSwitch:Off, UlVoIPLoadBasedSchSwitch:Off, UlVoipSchOptSwitch:Off, UlVoLTEDataSizeEstSwitch:Off CellUlsc hAlgo
SinrAdj TargetIb lerforVo LTE
MOD CELLU LSCHA LGO
LBFD-0 81105
VoiceSpecific AMC
LST CELLU LSCHA LGO
Meaning: Indicates the target IBLER in the SINR calibration algorithm used for dynamic scheduling of voice users in non-TTI-bundling mode. A larger value of this parameter results in a larger SINR adjustment and a higher MCS to be selected. GUI Value Range: 1~99 Unit: None Actual Value Range: 0.01~0.99,0.01 Default Value: 10
ENodeB AlgoSwi tch
EutranV oipSupp ortSwitc h
MOD ENODE BALGO SWITC H LST ENODE BALGO SWITC H
Issue 03 (2015-06-30)
None
None
Meaning: Indicates whether the VoIP services are enabled in the E-UTRAN cell. This parameter is used for determining whether the establishment, handover in, admission, and reestablishment of VoIP services is allowed. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: ON(On)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
144
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
GlobalP rocSwitc h
Protocol Support Switch
MOD GLOBA LPROC SWITC H
None
None
Meaning: Indicates whether the eNodeB supports some protocol-defined procedures. SupportS1UeCapMatchMsg(SupportS1UeCapMatch Msg): If this option is selected, the eNodeB can process and respond to the UE RADIO CAPABILITY MATCH REQUEST message over the S1 interface. For details about the message, see 3GPP TS 36.413. If the option is deselected, the eNodeB cannot process the UE RADIO CAPABILITY MATCH REQUEST message and responds with an error indication message.
LST GLOBA LPROC SWITC H
GUI Value Range: SupportS1UeCapMatchMsg(SupportS1UeCapMatch Msg) Unit: None Actual Value Range: SupportS1UeCapMatchMsg Default Value: SupportS1UeCapMatchMsg:Off
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
145
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
ENodeB AlgoSwi tch
HoAlgo Switch
MOD ENODE BALGO SWITC H
LBFD-0 0201801 / TDLBF D-00201 801
Coverag e Based Intrafrequenc y Handov er Distance Based Interfrequenc y Handov er Service Based Interfrequenc y Handov er CS Fallback to UTRAN CS Fallback to GERAN CS Fallback to CDMA2 000 1xRTT Flash CS Fallback to UTRAN Flash CS Fallback to GERAN CS Fallback
Meaning: Indicates whether to enable handover algorithms. The switches are described as follows: IntraFreqCoverHoSwitch: If this switch is on, coverage-based intra-frequency handovers are enabled to ensure service continuity. If this switch is off, coverage-based intra-frequency handovers are disabled. InterFreqCoverHoSwitch: If this switch is on, coverage-based inter-frequency handovers are enabled to ensure service continuity. If this switch is off, coverage-based inter-frequency handovers are disabled. UtranCsfbSwitch: If this switch is on, CSFB to UTRAN is enabled and UEs can fall back to UTRAN. If this switch is off, CSFB to UTRAN is disabled. GeranCsfbSwitch: If this switch is on, CSFB to GERAN is enabled and UEs can fall back to GERAN. If this switch is off, CSFB to GERAN is disabled. Cdma1xRttCsfbSwitch: If this switch is on, CSFB to CDMA2000 1xRTT is enabled and UEs can fall back to CDMA2000 1xRTT. If this switch is off, CSFB to CDMA2000 1xRTT is disabled. UtranServiceHoSwitch: If this switch is on, servicebased handovers to UTRAN are enabled and UEs running a specific type of services can be handed over to UTRAN. If this switch is off, service-based handovers to UTRAN are disabled. GeranServiceHoSwitch: If this switch is on, servicebased handovers to GERAN are enabled and UEs running a specific type of services can be handed over to GERAN. If this switch is off, service-based handovers to GERAN are disabled. CdmaHrpdServiceHoSwitch: If this switch is on, service-based handovers to CDMA2000 HRPD cells are enabled and UEs running a specific type of services can be handed over to CDMA2000 HRPD cells. If this switch is off, service-based handovers to CDMA2000 HRPD cells are disabled.This parameter is unavailable in this version. Cdma1xRttServiceHoSwitch: If this switch is on, service-based handovers to CDMA2000 1xRTT are enabled and UEs running a specific type of services can be handed over to CDMA2000 1xRTT. If this switch is off, service-based handovers to CDMA2000 1xRTT are disabled.This parameter is unavailable in this version. UlQualityInterRATHoSwitch: If this switch is on, UL-quality-based inter-RAT handovers are enabled and UEs can be handed over to inter-RAT cells to ensure service continuity when the UL signal quality is poor. If this switch is off, UL-quality-based
LST ENODE BALGO SWITC H
LBFD-0 0201802 / TDLBF D-00201 802 LBFD-0 0201804 / TDLBF D-00201 804 LBFD-0 0201805 / TDLBF D-00201 805 LOFD-0 01033 / TDLOF D-00103 3 LOFD-0 01034 / TDLOF D-00103 4 LOFD-0 01035 / TDLOF D-00103 5 LOFD-0 01052 / TDLOF D-00105 2 LOFD-0 01053 /
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
146
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
TDLOF D-00105 3
Steering to UTRAN
LOFD-0 01088 / TDLOF D-00108 8
CS Fallback Steering to GERAN
LOFD-0 01089 / TDLOF D-00108 9
Enhance d CS Fallback to CDMA2 000 1xRTT
inter-RAT handovers are disabled. InterPlmnHoSwitch: If this switch is on, inter-PLMN handovers are enabled and UEs can be handed over to cells in other PLMNs. If this switch is off, interPLMN handovers are disabled. UtranFlashCsfbSwitch: This switch takes effect only when UtranCsfbSwitch is on. If UtranFlashCsfbSwitch is on, flash CSFB to UTRAN is enabled and the eNodeB sends system information of candidate target UTRAN cells to UEs during redirections. If UtranFlashCsfbSwitch is off, flash CSFB to UTRAN is disabled. GeranFlashCsfbSwitch: This switch takes effect only when GeranCsfbSwitch is on. If GeranFlashCsfbSwitch is on, flash CSFB to GERAN is enabled and the eNodeB sends system information of candidate target GERAN cells to UEs during redirections. If GeranFlashCsfbSwitch is off, flash CSFB to GERAN is disabled. ServiceBasedInterFreqHoSwitch: If this switch is on, service-based inter-frequency handovers are enabled and UEs running a specific type of services can be handed over to inter-frequency cells. If this switch is off, service-based inter-frequency handovers are disabled. UlQualityInterFreqHoSwitch: If this switch is on, UL-quality-based inter-frequency handovers are enabled and UEs can be handed over to inter-frequency cells to ensure service continuity when the UL signal quality is poor. If this switch is off, ULquality-based inter-frequency handovers are disabled. CsfbAdaptiveBlindHoSwitch: This switch takes effect only when BlindHoSwitch is on. If CsfbAdaptiveBlindHoSwitch is on, adaptive blind handovers for CSFB are enabled and appropriate handover mechanisms are selected for UEs based on their locations. If CsfbAdaptiveBlindHoSwitch is off, adaptive blind handovers for CSFB are disabled. UtranCsfbSteeringSwitch: If this switch is on, CSFB steering to UTRAN is enabled and CSFB policies for UEs in idle mode can be configured. If this switch is off, CSFB steering to UTRAN is disabled. GeranCsfbSteeringSwitch: If this switch is on, CSFB steering to GERAN is enabled and CSFB policies for UEs in idle mode can be configured. If this switch is off, CSFB steering to GERAN is disabled. CSFBLoadInfoSwitch: If this switch is on, load-based CSFB is enabled and a target cell for CSFB is selected based on loads of candidate target cells. If this switch is off, load-based CSFB is disabled. Cdma1XrttEcsfbSwitch: If this switch is on, eCSFB to
LOFD-0 01090 / TDLOF D-00109 0 LOFD-0 01019 / TDLOF D-00101 9 LOFD-0 01020 / TDLOF D-00102 0 LOFD-0 01043 / TDLOF D-00104 3 LOFD-0 01046 / TDLOF D-00104 6 LOFD-0 01072 / TDLOF D-00107 2 LOFD-0 01073 / TDLOF Issue 03 (2015-06-30)
10 Parameters
PS InterRAT Mobility between EUTRAN and UTRAN PS InterRAT Mobility between EUTRAN and GERAN Service based interRAT handove r to UTRAN Service based interRAT handove r to GERAN Distance based
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
147
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
10 Parameters
Feature ID
Feature Name
Description
D-00107 3
interRAT handove r to UTRAN
UltraFlash CSFB to UTRAN
CDMA2000 1xRTT is enabled and UEs can fall back to CDMA2000 1xRTT through handovers. If this switch is off, eCSFB to CDMA2000 1xRTT is disabled. EmcBlindHoA1Switch: If this switch is on, blind handover event A1 measurements are enabled. If a blind handover event measurement conflicts with a handover procedure, an emergency blind handover can be triggered after the handover procedure is complete. If this switch is off, blind handover event A1 measurements are disabled. If a blind handover event measurement conflicts with a handover procedure, an emergency blind handover cannot be triggered. EmcInterFreqBlindHoSwitch: If this switch is on, the eNodeB preferentially performs an interfrequency blind handover when an emergency blind handover is triggered. If this switch is off, the eNodeB only performs an inter-RAT blind handover when an emergency blind handover is triggered. EPlmnSwitch: Indicates whether handovers to neighboring cells under the equivalent PLMNs (EPLMNs) are allowed. When inter-PLMN handovers are allowed, handovers to neighboring cells under the EPLMNs are allowed if this switch is on, and not allowed if this switch is off. The EPLMNs are delivered by the MME to the UE. ServiceBasedInterFreqHoSwitch: If this switch is on, service-based inter-frequency handovers are enabled and UEs running a specific type of services can be handed over to inter-frequency cells. If this switch is off, service-based inter-frequency handovers are disabled. This switch takes effect only for LTE TDD cells. VoipHoControlSwitch: Indicates whether the eNodeB filters out target cells that do not support VoIP services when processing intra-RAT handovers for VoIP services. The eNodeB filters out such target cells in the preceding scenario only when this switch is on. UtranUltraFlashCsfbSwitch: In this switch is on, ultra-flash CSFB to UTRAN is enabled and UEs can fall back to UTRAN based on the ultra-flash CSFB procedure. If this switch is off, ultra-flash CSFB to UTRAN is disabled. GeranUltraFlashCsfbSwitch: In this switch is on, ultra-flash CSFB to GERAN is enabled and UEs can fall back to GERAN based on the ultra-flash CSFB procedure. If this switch is off, ultra-flash CSFB to GERAN is disabled.
UltraFlash CSFB to UTRAN
GUI Value Range: IntraFreqCoverHoSwitch(IntraFreqCoverHoSwitch), InterFreqCoverHoSwitch(InterFreqCoverHoSwitch), UtranCsfbSwitch(UtranCsfbSwitch),
TDLBF D-00201 8 TDLOF D-00102 2 TDLOF D-07022 8 LOFD-0 81283 / TDLOF D-08120 3 LOFD-0 70202 / TDLOF D-07020 2 TDLOF D-08122 3
Distance based interRAT handove r to GERAN Mobility Manage ment Coverag e Based Interfrequenc y Handov er SRVCC to UTRAN ServiceRequest Based Interfrequenc y Handov er UltraFlash CSFB to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
148
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
GeranCsfbSwitch(GeranCsfbSwitch), Cdma1xRttCsfbSwitch(Cdma20001xRttCsfbSwitch), UtranServiceHoSwitch(UtranServiceHoSwitch), GeranServiceHoSwitch(GeranServiceHoSwitch), CdmaHrpdServiceHoSwitch(Cdma2000HrpdServiceHoSwitch), Cdma1xRttServiceHoSwitch(Cdma20001xRttService HoSwitch), UlQualityInterRATHoSwitch(UlQualityInterRATHoSwitch), InterPlmnHoSwitch(InterPlmnHoSwitch), UtranFlashCsfbSwitch(UtranFlashCsfbSwitch), GeranFlashCsfbSwitch(GeranFlashCsfbSwitch), ServiceBasedInterFreqHoSwitch(ServiceBasedInterFreqHoSwitch), UlQualityInterFreqHoSwitch(UlQualityInterFreqHoSwitch), CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlindHoSwitch), UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch), GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch), CSFBLoadInfoSwitch(CSFBLoadInfoSwitch), Cdma1XrttEcsfbSwitch(Cdma1XrttEcsfbSwitch), EmcBlindHoA1Switch(EmcBlindHoA1Switch), EmcInterFreqBlindHoSwitch(EmcInterFreqBlindHoSwitch), EPlmnSwitch(EPlmnSwitch), ServiceReqInterFreqHoSwitch(ServiceReqInterFreqHoSwitch), VoipHoControlSwitch(VoipHoControlSwitch), UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch), GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) Unit: None Actual Value Range: IntraFreqCoverHoSwitch, InterFreqCoverHoSwitch, UtranCsfbSwitch, GeranCsfbSwitch, Cdma1xRttCsfbSwitch, UtranServiceHoSwitch, GeranServiceHoSwitch, CdmaHrpdServiceHoSwitch, Cdma1xRttServiceHoSwitch, UlQualityInterRATHoSwitch, InterPlmnHoSwitch, UtranFlashCsfbSwitch, GeranFlashCsfbSwitch, ServiceBasedInterFreqHoSwitch, UlQualityInterFreqHoSwitch, CsfbAdaptiveBlindHoSwitch, UtranCsfbSteeringSwitch, GeranCsfbSteeringSwitch, CSFBLoadInfoSwitch, Cdma1XrttEcsfbSwitch, EmcBlindHoA1Switch, EmcInterFreqBlindHoSwitch, EPlmnSwitch, ServiceReqInterFreqHoSwitch, VoipHoControlSwitch, UtranUltraFlashCsfbSwitch, GeranUltraFlashCsfbSwitch
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
149
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
Default Value: IntraFreqCoverHoSwitch:On, InterFreqCoverHoSwitch:On, UtranCsfbSwitch:Off, GeranCsfbSwitch:Off, Cdma1xRttCsfbSwitch:Off, UtranServiceHoSwitch:Off, GeranServiceHoSwitch:Off, CdmaHrpdServiceHoSwitch:Off, Cdma1xRttServiceHoSwitch:Off, UlQualityInterRATHoSwitch:Off, InterPlmnHoSwitch:Off, UtranFlashCsfbSwitch:Off, GeranFlashCsfbSwitch:Off, ServiceBasedInterFreqHoSwitch:Off, UlQualityInterFreqHoSwitch:Off, CsfbAdaptiveBlindHoSwitch:Off, UtranCsfbSteeringSwitch:Off, GeranCsfbSteeringSwitch:Off, CSFBLoadInfoSwitch:Off, Cdma1XrttEcsfbSwitch:Off, EmcBlindHoA1Switch:Off, EmcInterFreqBlindHoSwitch:Off, EPlmnSwitch:Off, ServiceReqInterFreqHoSwitch:Off, VoipHoControlSwitch:Off, UtranUltraFlashCsfbSwitch:Off, GeranUltraFlashCsfbSwitch:Off ENodeB ConnSta teTimer
S1Msg Waiting TimerQ ci1
MOD ENODE BCONN STATET IMER
LBFD-0 02007 / TDLBF D-00200 7
RRC Connect ion Manage ment
LST ENODE BCONN STATET IMER ENodeB ConnSta teTimer
X2Mess ageWaiti ngTimer Qci1
MOD ENODE BCONN STATET IMER LST ENODE BCONN STATET IMER
Meaning: Indicates the timer governing the period that the eNodeB waits for a response message from the MME when the UE are running services with the QCI of 1. If the timer expires, the eNodeB initiates a UE context release over the S1 interface. GUI Value Range: 1~200 Unit: s Actual Value Range: 1~200 Default Value: 20
LOFD-0 02007 / TDLOF D-00200 7
RRC Connect ion Manage ment
Meaning: Indicates the timer governing the period the local eNodeB waits for a response message from the peer eNodeB when the UE is running services with the QCI of 1. If the timer expires, the eNodeB processes the same as the timer specified by the X2MessageWaitingTimer parameter expires. GUI Value Range: 1~200 Unit: s Actual Value Range: 1~200 Default Value: 20
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
150
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
ENodeB ConnSta teTimer
UuMess ageWaiti ngTimer Qci1
MOD ENODE BCONN STATET IMER
LBFD-0 02007 / TDLBF D-00200 7
RRC Connect ion Manage ment
Meaning: Indicates the timer governing the period the eNodeB waits for a response message from a UE when the UE is running services with the QCI of 1. If the timer expires, the eNodeB initiates a UE context release over the S1 interface.
LST ENODE BCONN STATET IMER RrcCon nStateTi mer
UeInacti veTimer Qci1
MOD RRCCO NNSTA TETIM ER
GUI Value Range: 1~200 Unit: s Actual Value Range: 1~200 Default Value: 35 LBFD-0 02007 / TDLBF D-00200 7
RRC Connect ion Manage ment
LST RRCCO NNSTA TETIM ER
Meaning: Indicates the length of the UE inactivity timer for UEs that are running services of QCI 1. If the eNodeB detects that a UE has neither received nor sent data for a duration exceeding the value of this parameter, the eNodeB releases the RRC connection for the UE. If this parameter is set to 0, the UE inactivity timer is not used. This timer takes effect during the setup of bearers with a QCI of 1. During a handover or RRC connection reestablishment to a new cell, the eNodeB determines whether the timer takes effect based on whether the UE is running services with a QCI of 1. If yes, the timer takes effect; otherwise, the timer does not take effect. GUI Value Range: 0~3600 Unit: s Actual Value Range: 0~3600 Default Value: 20
CellStan dardQci
TrafficR elDelay
MOD CELLS TANDA RDQCI LST CELLS TANDA RDQCI
LBFD-0 02008 / TDLBF D-00200 8
Radio Bearer Manage ment
Meaning: Indicates the waiting duration for the eNodeB to release services with a specific QCI after the eNodeB detects that the radio link is abnormal. When the eNodeB detects that the radio link is abnormal, the eNodeB waits for the UE to initiate an RRC connection reestablishment procedure to restore services. If the waiting duration times out, the eNodeB releases the services. GUI Value Range: 0~65000 Unit: ms Actual Value Range: 0~65000 Default Value: 30000
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
151
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
RlcPdcp ParaGro up
RlcMod e
ADD RLCPD CPPAR AGROU P
LBFD-0 02008 / TDLBF D-00200 8
Radio Bearer Manage ment
Meaning: Indicates the RLC transmission mode. Only the AM and UM modes are available.
MOD RLCPD CPPAR AGROU P
GUI Value Range: RlcMode_AM(Acknowledge Mode), RlcMode_UM(Un-acknowledge Mode) Unit: None Actual Value Range: RlcMode_AM, RlcMode_UM Default Value: RlcMode_AM(Acknowledge Mode)
LST RLCPD CPPAR AGROU P
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
152
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellAlg oSwitch
RacAlgo Switch
MOD CELLA LGOSW ITCH
LBFD-0 02023 / TDLBF D-00202 3
Admissi on Control
Meaning:
LST CELLA LGOSW ITCH
LBFD-0 02024 / TDLBF D-00202 4 LOFD-0 0102901
Congesti on Control Radio/ transport resource preemption
Indicates whether to enable the admission and load control algorithms. DlSwitch: Indicates whether to enable the algorithm of downlink admission control based on the satisfaction rate. If this switch is on, the algorithm is enabled. If this switch is off, the algorithm is disabled. During the calculation of the QoS satisfaction rate of services with different QCIs, the satisfaction estimation method used dedicatedly for VoIP services is implemented on services with the QCI of 1. If a service with the QCI of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the admission of GBR services. Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off. UlSwitch: Indicates whether to enable the algorithm of uplink admission control based on the satisfaction rate. If this switch is on, the algorithm is enabled. If this switch is off, the algorithm is disabled. During the calculation of the QoS satisfaction rate of services with different QCIs, the satisfaction estimation method used dedicated for VoIP services is implemented on services with the QCI of 1. If a service with the QCI of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the admission of GBR services. Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off. DlPredictSwitch: Indicates whether to enable the algorithm of downlink admission control based on prediction. If this switch is on, the algorithm is enabled. If this switch is off, the algorithm is disabled. UlPredictSwitch: Indicates whether to enable the algorithm of uplink admission control based on prediction. If this switch is on, the algorithm is enabled. If this switch is off, the algorithm is disabled. GbrUsageSwitch: Indicates whether to enable the check on the number of PRBs used by GBR services. If this switch is on, the number of PRBs used by existing GBR services is checked before a new GBR service can be admitted. If this switch is off, the number of PRBs used by existing GBR services is not
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
153
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
checked during admission evaluation of new GBR services DlLdcSwitch: Indicates whether to implement load control in the downlink of a cell. If this switch is on, the system checks for congestion in the downlink of the cell. If the downlink is congested, load control is performed. If this switch is off, the system does not check for congestion in the downlink of the cell and the congestion cannot be relieved. During the calculation of the QoS satisfaction rate of services with different QCIs, the satisfaction estimation method used dedicated for VoIP services is implemented on services with the QCI of 1. If a service with the QCI of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the cell load control. Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off. UlLdcSwitch: Indicates whether to implement load control in the uplink of a cell. If this switch is on, the system checks for congestion in the uplink of the cell. If the uplink is congested, load control is performed. If this switch is off, the system does not check for congestion in the uplink of the cell and the congestion cannot be relieved. During the calculation of the QoS satisfaction rate of services with different QCIs, the satisfaction estimation method used dedicated for VoIP services is implemented on services with the QCI of 1. If a service with the QCI of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the cell load control. Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off. RelDrbSwitch: Indicates whether low-priority services can be released in the case of congestion. If this switch is on, low-priority services can be released. If this switch is off, low-priority services cannot be released. PreemptionSwitch: Indicates whether to enable the preemption control algorithm. If this switch is on, preemption can be used when the admission of highpriority services fails. If this switch is off, only emergency calls can be admitted to the system when resources are insufficient.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
154
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
GUI Value Range: DlSwitch(dlCacSwitch), UlSwitch(ulCacSwitch), DlPredictSwitch(dlCacPredictSwitch), UlPredictSwitch(ulCacPredictSwitch), GbrUsageSwitch(GbrUsedPRbCheckSwitch), DlLdcSwitch(dlLdcSwitch), UlLdcSwitch(ulLdcSwitch), RelDrbSwitch(LdcDrbRelSwitch), PreemptionSwitch(PreemptionSwitch) Unit: None Actual Value Range: DlSwitch, UlSwitch, DlPredictSwitch, UlPredictSwitch, GbrUsageSwitch, DlLdcSwitch, UlLdcSwitch, RelDrbSwitch, PreemptionSwitch Default Value: DlSwitch:Off, UlSwitch:Off, DlPredictSwitch:Off, UlPredictSwitch:Off, GbrUsageSwitch:Off, DlLdcSwitch:Off, UlLdcSwitch:Off, RelDrbSwitch:Off, PreemptionSwitch:Off CellRac Thd
Qci1Co ngThd
MOD CELLR ACTHD LST CELLR ACTHD
LBFD-0 02024 / TDLBF D-00202 4
Congesti on Control
Meaning: Indicates the congestion threshold for services with QCI of 1. This threshold applies to both UL and DL. If the satisfaction rate of services with QCI of 1 in the cell becomes lower than this threshold, the services with QCI of 1 enter the congested state. If the satisfaction rate of services with QCI of 1 in the cell becomes higher than the sum of this threshold and the congestion relief offset, the services with QCI of 1 leave the congested state. GUI Value Range: 0~99 Unit: % Actual Value Range: 0~99 Default Value: 65
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
155
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
UlschStr ategy
MOD CELLU LSCHA LGO
LBFD-0 02025 / TDLBF D-00202 5
Basic Scheduli ng
Meaning: Indicates the UL scheduling policy, which determines the scheduling priority order in which UEs are arranged in UL. There are four UL scheduling strategies: MAX C/I, proportional fair (PF), round Robin (RR), and enhanced proportional fair (EPF). The MAX C/I policy schedules UEs in descending order of average signal to interference plus noise ratio (SINR). The PF policy schedules UEs in ascending order of ratio of the data rate to the SINR. The RR policy schedules each UE in sequence, and therefore each UE has an equal opportunity to be scheduled. The EPF policy schedules UEs in ascending order of priority. In EPF, the priority of an UE is calculated based on the following factors: the data rate, average SINR, QoS-satisfying data rate for each service, and service differentiation requirements of the UE. The MAX C/I, PF, and RR policies are basic UL scheduling policies and supported by the eNodeB by default, whereas the EPF policy is intended for commercial use.
LST CELLU LSCHA LGO
TDLOF D-00101 5 TDLOF D-00101 502
Dynami c Scheduli ng Enhance d Scheduli ng
GUI Value Range: ULSCH_STRATEGY_EPF(EPF), ULSCH_STRATEGY_MAX_CI(MAX_CI), ULSCH_STRATEGY_PF(PF), ULSCH_STRATEGY_RR(RR) Unit: None Actual Value Range: ULSCH_STRATEGY_EPF, ULSCH_STRATEGY_MAX_CI, ULSCH_STRATEGY_PF, ULSCH_STRATEGY_RR Default Value: ULSCH_STRATEGY_EPF(EPF)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
156
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellDlsc hAlgo
DlschStr ategy
MOD CELLD LSCHA LGO
LBFD-0 02025 / TDLBF D-00202 5
Basic Scheduli ng
Meaning: Indicates the switch of the DL scheduling policy. According to the Max C/I scheduling policy, the UE with good-quality channels are scheduled and hence the spectral efficiency is very high. The QoS and fairness among users, however, cannot be ensured. The Max C/I scheduling policy can be used to verify the maximum capacity of the system. The RR scheduling policy is the fairest scheduling policy. When RR is adopted, the system capacity is the smallest. Therefore, RR is used only to verify the upper bound of the scheduling fairness in the system. In terms of the scheduling effect, the PF scheduling policy is between the previous two policies. Therefore, PF can be used to verify the capacity, coverage, and fairness of the system. The EPF scheduling policy supports the features such as user QoS, system capacity, and channel frequency selection. The basic scheduling policy is mainly used for the performance test purpose. During common operation, the EPF scheduling policy is recommended.
LST CELLD LSCHA LGO
TDLOF D-00101 5 TDLOF D-00101 502
Enhance d Scheduli ng Dynami c Scheduli ng
GUI Value Range: DLSCH_PRI_TYPE_EPF(EPF), DLSCH_PRI_TYPE_PF(PF), DLSCH_PRI_TYPE_MAX_CI(MAX C/I), DLSCH_PRI_TYPE_RR(RR) Unit: None Actual Value Range: DLSCH_PRI_TYPE_EPF, DLSCH_PRI_TYPE_PF, DLSCH_PRI_TYPE_MAX_CI, DLSCH_PRI_TYPE_RR Default Value: DLSCH_PRI_TYPE_EPF(EPF)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
157
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellAlg oSwitch
DlSchS witch
MOD CELLA LGOSW ITCH
LOFD-0 01016 / TDLOF D-00101 6
VoIP Semipersisten t Scheduli ng
Meaning:
LST CELLA LGOSW ITCH
LOFD-0 0101502 / TDLOF D-00101 502 LOFD-0 01109 / TDLOF D-00110 9 LOFD-0 01070 / TDLOF D-00107 0 TDLOF D-07022 4 LBFD-0 02025 / TDLBF D-00202 5 LBFD-0 02031 / TDLBF D-00203 1 LBFD-0 70102 / TDLBF D-07010 2 LBFD-0 60202
Issue 03 (2015-06-30)
Dynami c Scheduli ng DL NonGBR Packet Bundlin g Symbol Power Saving Scheduli ng Based on Max Bit Rate Basic Scheduli ng Support of aperiodi c CQI reports MBR>G BR Configu ration Enhance d DL Frequen cy Selectiv e
Indicates the switches related to downlink scheduling in the cell. FreqSelSwitch: Indicates whether to enable frequency selective scheduling. If this switch is on, data is transmitted on the frequency band in good signal quality. ServiceDiffSwitch: Indicates whether to enable service differentiation. If this switch is on, service differentiation is applied. If this switch is off, service differentiation is not applied. SpsSchSwitch: Indicates whether to enable semipersistent scheduling during talk spurts of VoIP services. If this switch is on, semi-persistent scheduling is applied during talk spurts of VoIP services. If this switch is off, dynamic scheduling is applied during talk spurts of VoIP services. MBSFNShutDownSwitch: Indicates whether to enable Multimedia Broadcast multicast service Single Frequency Network (MBSFN) subframe shutdown. If this switch is on, MBSFN subframe shutdown is applied. If this switch is off, MBSFN subframe shutdown is not applied. This switch is valid only when SymbolShutdownSwitch is on. If the MBSFN shutdown switch is on, the setting of the switch for mapping SIBs to SI messages becomes invalid. The latter can be specified by the SiMapSwitch parameter in the CellSiMap MO. If the MBSFN subframe shutdown switch is off, the setting of the switch for mapping SIBs to SI messages becomes valid. MBSFN subframe shutdown applies only to LTE-only base stations. NonGbrBundlingSwitch: Indicates whether to enable downlink non-GBR packet bundling. If this switch is on, delay of non-GBR services can be controlled in non-congestion scenarios. If this switch is off, delay of non-GBR services cannot be controlled. EnAperiodicCqiRptSwitch: Indicates whether to enable enhanced aperiodic channel quality indicator (CQI) reporting. If this switch is on, the eNodeB triggers aperiodic CQI reporting for a UE based on downlink services of the UE and the interval at which the UE sends periodic CQI reports. If this switch is off, UEs under non-frequency selective scheduling do not trigger aperiodic CQI reporting based on downlink
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
158
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
services and triggers an aperiodic CQI reporting if no valid periodic CQI reports are sent in eight consecutive periodic CQI reporting periods. DlMbrCtrlSwitch: Indicates whether to enable downlink scheduling based on the maximum bit rate (MBR) and guaranteed bit rate (GBR) on the GBR bearer. If this switch is on, the eNodeB performs downlink scheduling on GBR bearers based on the MBR and GBR. If this switch is off, the eNodeB performs downlink scheduling on GBR bearers based on the GBR only. MbrDlSchSwitch: Indicates whether the eNodeB performs downlink scheduling based on MBR. If this switch is on, the eNodeB determines priorities of UEs based on the MBR in downlink scheduling. This parameter applies only to LTE TDD cells. UeAmbrDlSchSwitch: Indicates whether the eNodeB performs downlink scheduling based on the aggregate maximum bit rate (AMBR) of UEs. If this switch is on, the eNodeB determines priorities of UEs based on the AMBR of UEs in downlink scheduling. This parameter applies only to LTE TDD cells. EpfEnhancedSwitch: Indicates whether to enable enhanced proportional fair (EPF) for downlink scheduling. EPF for downlink scheduling is enabled only when this switch is on. AperiodicCqiTrigOptSwitch: Indicates whether to trigger aperiodic CQI optimization. If this switch is on, a UE performing initial access triggers aperiodic CQI reporting based on related triggering conditions after the DLMAC instance has been established for 200 ms and the eNodeB receives MSG5. Consider that aperiodic CQI reporting is triggered by invalid CQI reports in eight consecutive CQI reporting periods. If cyclic redundancy check (CRC) on aperiodic CQI reports fails, aperiodic CQI reporting is not repeatedly triggered when DRX is enabled; or aperiodic CQI reporting is triggered after eight TTIs when DRX is disabled. If this switch is off, a UE performing initial access triggers aperiodic CQI reporting based on related triggering conditions after the DLMAC instance has been established for 200 ms. Consider that aperiodic CQI reporting is triggered by invalid CQI reports in eight consecutive CQI reporting periods. If CRC on aperiodic CQI reports fails,
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
159
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
aperiodic CQI reporting is triggered after eight TTIs regardless of the DRX status. VoipTbsBasedMcsSelSwitch: Indicates whether the modulation and coding scheme (MCS) index is selected based on the transport block size (TBS) in downlink scheduling for VoIP services. If this switch is on, the MCS index is selected based on the TBS in downlink scheduling for VoIP services. If this switch is off, the MCS index is not selected based on the TBS in downlink scheduling for VoIP services. UeSigMcsEnhanceSwitch: Indicates whether to enable or disable the optimized MCS algorithm for UE signaling. The optimized MCS algorithm for UE signaling takes effect after this switch is on. This parameter applies only to LTE TDD cells. PagingInterfRandSwitch: Indicates whether to enable or disable interference randomizing for paging messages. If this switch is on, interference randomizing is enabled for paging messages. This switch is valid only in TDD mode. DlSingleUsrMcsOptSwitch: Indicates conditions for lowering the modulation and coding scheme (MCS) for a single UE. When this switch is on, the MCS can be lowered for a UE if the UE is the only UE to be scheduled in a transmission time interval (TTI). When this switch is off, the MCS can be lowered for a UE if there are only 10 percent of TTIs having UEs to schedule in each sparse packet determination period and the UE is the only UE to be scheduled in each TTI. SubframeSchDiffSwitch: Indicates whether subframes 3 and 8 perform scheduling based on increased number of uplink scheduling UEs when subframe configuration type 2 is used. If this switch is on, subframes 3 and 8 perform scheduling based on increased number of uplink scheduling UEs when subframe configuration type 2 is used. If this switch is off, subframes 3 and 8 perform scheduling based on the policy that other downlink subframes adopt when subframe configuration type 2 is used. This switch is dedicated to LTE TDD cells. TailPackagePriSchSwitch: Indicates the switch that controls the scheduling of downlink connected tail packages in the bearer. If this switch is on, the connected tail package is scheduled preferentially in Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
160
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
the next TTI, which reduces the delay and increases the transmission rate. If this switch is off, the scheduling strategy of the connected tail package is the same as other downlink subframes. This switch is dedicated to LTE TDD cells. FreqSelJudgeIgnorDopplerSwitch: Indicates whether Doppler determination conditions are considered during channel frequency selective scheduling determination. Doppler determination conditions are considered only when this option is deselected. This option applies only to LTE FDD. SIB1InterfRandSwitch: Indicates whether to enable SIB1 interference randomizing. If this switch is on, interference randomizing is enabled for SIB1. This switch applies only to LTE TDD cells. GUI Value Range: FreqSelSwitch(FreqSelSwitch), ServiceDiffSwitch(ServiceDiffSwitch), SpsSchSwitch(SpsSchSwitch), MBSFNShutDownSwitch(MBSFNShutDownSwitch), NonGbrBundlingSwitch(NonGbrBundlingSwitch), EnAperiodicCqiRptSwitch(EnAperiodicCqiRptSwitch), DlMbrCtrlSwitch(DlMbrCtrlSwitch), MbrDlSchSwitch(MbrDlSchSwitch), UeAmbrDlSchSwitch(UeAmbrDlSchSwitch), EpfEnhancedSwitch(EpfEnhancedSwitch), AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptSwitch), VoipTbsBasedMcsSelSwitch(VoipTbsBasedMcsSelSwitch), PagingInterfRandSwitch(PagingInterfRandSwitch), DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptSwitch), SubframeSchDiffSwitch(SubframeSchDiffSwitch), TailPackagePriSchSwitch(TailPackagePriSchSwitch), UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch), FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnorDopplerSwitch), SIB1InterfRandSwitch(SIB1InterfRandSwitch) Unit: None Actual Value Range: FreqSelSwitch, ServiceDiffSwitch, SpsSchSwitch, MBSFNShutDownSwitch, NonGbrBundlingSwitch, EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch, MbrDlSchSwitch, UeAmbrDlSchSwitch, EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch, VoipTbsBasedMcsSelSwitch, PagingInterfRandSwitch, DlSingleUsrMcsOptSwitch, SubframeSchDiffSwitch, TailPackagePriSchSwitch, Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
161
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDopplerSwitch, SIB1InterfRandSwitch Default Value: FreqSelSwitch:Off, ServiceDiffSwitch:Off, SpsSchSwitch:Off, MBSFNShutDownSwitch:Off, NonGbrBundlingSwitch:Off, EnAperiodicCqiRptSwitch:Off, DlMbrCtrlSwitch:Off, MbrDlSchSwitch:Off, UeAmbrDlSchSwitch:Off, EpfEnhancedSwitch:Off, AperiodicCqiTrigOptSwitch:Off, VoipTbsBasedMcsSelSwitch:Off, PagingInterfRandSwitch:Off, DlSingleUsrMcsOptSwitch:Off, SubframeSchDiffSwitch:Off, TailPackagePriSchSwitch:Off, UeSigMcsEnhanceSwitch:Off, FreqSelJudgeIgnorDopplerSwitch:Off, SIB1InterfRandSwitch:On
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
162
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellAlg oSwitch
CqiAdj AlgoSwi tch
MOD CELLA LGOSW ITCH
LOFD-0 0101501 / TDLOF D-00101 501
CQI Adjustm ent
Meaning:
LST CELLA LGOSW ITCH
LOFD-0 0101502 / TDLOF D-00101 502
Dynami c Scheduli ng
CqiAdjAlgoSwitch: Indicates whether to allow the eNodeB to adjust the UE-reported CQI based on the initial block error rate (IBLER). If this switch is On, the CQI adjustment algorithm is enabled. In this case, the eNodeB adjusts the UEreported CQI based on the IBLER. If this switch is off, the CQI adjustment algorithm is disabled. In this case, the eNodeB does not adjust the UE-reported CQI based on the IBLER. StepVarySwitch: Indicates whether to enable the variable-step-based adjustment algorithm. If this switch is On, the variable-step-based adjustment algorithm is enabled to accelerate the convergence of IBLER. In this case, rapid adjustment at large steps is applied if there is a relatively large difference between the measured IBLER and target IBLER; fine-tuning at small steps is applied if the measured IBLER approaches the target IBLER. If this switch is off, the adjustment is performed at a fixed step. DlVarIBLERtargetSwitch: Indicates whether to enable downlink target IBLER adaption. If this switch is On, the downlink target IBLER is adjusted based on the size of transport blocks (TBs) to improve the spectral efficiency. If this switch is off, the target IBLER is determined based on the setting of DlEnVarIblerTargetSwitch. TddBundlingCqiAdjOptSwitch: Indicates whether to use optimized CQI adjustment algorithm in ACK bundling mode. If this switch is On, the optimized CQI adjustment algorithm is used. If this switch is off, the optimized CQI adjustment algorithm cannot be used. TddMultiplexingCqiAdjOptSwitch: Indicates whether to use the optimized CQI adjustment algorithm in ACK multiplexing mode. If this switch is On, the optimized CQI adjustment algorithm is used.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
163
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
If this switch is off, the optimized CQI adjustment algorithm cannot be used. AdaptiveStepVarySwitch: Indicates whether to enable adaptive step change in CQI adjustment. If this switch is On, significant changes in the signal quality can be detected, and the CQI adjustment is performed at a large step, accelerating the IBLER convergence. If this switch is off, the CQI adjustment is performed at a fixed step. DlCqiAdjDeltaOptSwitch: Indicates whether to enable optimization on downlink CQI adjustment. If this switch is off, the CQI adjustment is calculated based on the following formula: CQI adjustment = (Number of ACKs for initial transmissions x CQI adjustment per ACK + Number of NACKs for initial transmissions x CQI adjustment per NACK)/(Number of NACKs for initial transmissions + Number of ACKs for initial transmissions). If this switch is On, the CQI adjustment is calculated based on the following formula: CQI adjustment = Number of ACKs for initial transmissions x CQI adjustment per ACK + Number of NACKs for initial transmissions x CQI adjustment per NACK). DlEnVarIblerTargetSwitch: Indicates whether to enable enhanced downlink target IBLER adaption. If this switch is On, the downlink target IBLER is adaptively adjusted based on CQI fluctuation and TB size. If this switch is off, the downlink target IBLER policy is controlled by DlVarIBLERtargetSwitch. This switch applies only to FDD cells. DlRetxTbsIndexAdjOptSwitch: Indicates whether to enable transport block size (TBS) index adjustment optimization in retransmissions. If this switch is On, TBS index adjustment optimization in retransmissions is enabled. The TBS index is lowered for the scheduling of the last two retransmissions, and the TBS index is determined based on the CQI adjustment for the scheduling of other retransmissions. If this switch is off, TBS index adjustment optimization in retransmissions is disabled. The TBS index is determined based on the CQI adjustment for the scheduling of all retransmissions.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
164
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
CfiConvertOptSwitch: Indicates whether to enable CFI calculation optimization. If this switch is turned on, new CFI calculation tables for normal and special subframes are used to ensure more accurate MCS selection in normal and special subframes and facilitate IBLER convergence to the target value. If this switch is turned off, the original CFI calculation tables for normal and special subframes are used. This switch applies only to LTE TDD networks. BundlingOptThdSwitch: Indicates whether to adjust the MCS index threshold for enabling the optimized CQI adjustment algorithm in TDD bundling mode. If this switch is turned on, the lower MCS index threshold for enabling the optimized CQI adjustment algorithm in TDD bundling mode is changed from MCS index 6 to MCS index 0. If this switch is turned off, the lower MCS index threshold for enabling the optimized CQI adjustment algorithm in TDD bundling mode is MCS index 6. This switch applies only to LTE TDD networks. GUI Value Range: CqiAdjAlgoSwitch(CqiAdjAlgoSwitch), StepVarySwitch(StepVarySwitch), DlVarIBLERtargetSwitch(DlVarIBLERtargetSwitch), TddBundlingCqiAdjOptSwitch(TddBundlingCqiAdjOptSwitch), TddMultiplexingCqiAdjOptSwitch(TddMultiplexingCqiAdjOptSwitch), AdaptiveStepVarySwitch(AdaptiveStepVarySwitch), DlCqiAdjDeltaOptSwitch(DlCqiAdjDeltaOptSwitch), DlEnVarIblerTargetSwitch(DlEnVarIblerTargetSwitch), DlRetxTbsIndexAdjOptSwitch(DlRetxTbsIndexAdjOptSwitch), CfiConvertOptSwitch(CfiConvertOptSwitch), BundlingOptThdSwitch(BundlingOptThdSwitch) Unit: None Actual Value Range: CqiAdjAlgoSwitch, StepVarySwitch, DlVarIBLERtargetSwitch, TddBundlingCqiAdjOptSwitch, TddMultiplexingCqiAdjOptSwitch, AdaptiveStepVarySwitch, DlCqiAdjDeltaOptSwitch, DlEnVarIblerTargetSwitch, DlRetxTbsIndexAdjOptSwitch, CfiConvertOptSwitch, BundlingOptThdSwitch Default Value: CqiAdjAlgoSwitch:On, StepVarySwitch:Off, DlVarIBLERtargetSwitch:Off, TddBundlingCqiAdjOptSwitch:Off, TddMultiplexingCqiAdjOptSwitch:Off, AdaptiveStepVarySwitch:Off, DlCqiAdjDeltaOptSIssue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
165
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
witch:Off, DlEnVarIblerTargetSwitch:Off, DlRetxTbsIndexAdjOptSwitch:Off, CfiConvertOptSwitch:Off, BundlingOptThdSwitch:Off
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
166
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellAlg oSwitch
UlSchS witch
MOD CELLA LGOSW ITCH
LOFD-0 01016 / TDLOF D-00101 6
VoIP Semipersisten t Scheduli ng
Meaning:
LST CELLA LGOSW ITCH
LOFD-0 01048 / TDLOF D-00104 8 LOFD-0 0101502 / TDLOF D-00101 502 TDLBF D-00202 5 LBFD-0 70102 / TDLBF D-07010 2 LOFD-0 01002 LOFD-0 01058 LBFD-0 01006
TTI Bundlin g Dynami c Scheduli ng Basic Scheduli ngTDL OFD-07 0224:Sc heduling Based on Max Bit Rate MBR>G BR Configu ration UL 2x2 MUMIMO UL 2x4 MUMIMO AMC
This parameter indicates the switches related to uplink (UL) scheduling in the cell. The switches are used to enable or disable specific UL scheduling functions. SpsSchSwitch: Indicates the switch used to enable or disable semi-persistent scheduling during talk spurts of VoIP services. If this switch is on, semi-persistent scheduling is applied during talk spurts of VoIP services. If this switch is off, dynamic scheduling is applied during talk spurts of VoIP services. SinrAdjustSwitch: Indicates whether to adjust the measured signal to interference plus noise ratio (SINR) based on ACK/NACK in UL hybrid automatic repeat request (HARQ) processes. PreAllocationSwitch: Indicates whether to enable preallocation in the uplink. When this switch is on: (1) If SmartPreAllocationSwitch is off and a UE is in the discontinuous reception (DRX) state, preallocation is disabled for the UE in the uplink; (2) If SmartPreAllocationSwitch is off and the UE is not in the DRX state, preallocation is enabled for the UE in the uplink; (3) If SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter value is greater than 0, smart preallocation is enabled for the UE in the uplink; (4) If SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter value is 0, preallocation is disabled for the UE in the uplink. If this switch is off, preallocation is disabled for the UE in the uplink. If bearer-level preallocation or bearer-level smart preallocation is enabled for a UE with a QCI class, cell-level preallocation and celllevel smart preallocation do not apply to UEs with the QCI. UlVmimoSwitch: Indicates whether to enable multiuser MIMO (MU-MIMO) in the UL. If this switch is on, the eNodeB performs MU-MIMO pairing among UEs based on related principles. UEs forming a pair transmit data using the same time-frequency resources, which improves system throughput and spectral efficiency. TtiBundlingSwitch: Indicates whether to enable transmission time interval (TTI) bundling. If TTI bundling is enabled, more transmission opportunities are available to UEs within the delay budget for VoIP
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
167
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
services on the Uu interface, thereby improving uplink coverage. ImIcSwitch: Indicates whether to enable the intermodulation interference (IM) cancellation for UEs. When data is transmitted in both uplink and downlink, two IM components are generated symmetrically beside the Direct Current (DC) subcarrier on the downlink receive channel due to interference from uplink radio signals. If this switch is on, IM component elimination is performed on UEs. If this switch is off, IM component elimination is not performed on UEs. This switch applies only to FDD cells working in frequency band 20. SmartPreAllocationSwitch: Indicates whether to enable uplink smart preallocation when preallocation is enabled (by turning on PreAllocationSwitch). If both PreAllocationSwitch and SmartPreAllocationSwitch are on and SmartPreAllocationDuration is set to a value greater than 0, uplink smart preallocation is enabled; otherwise, uplink smart preallocation is disabled. PuschDtxSwitch: Indicates whether the eNodeB uses the physical uplink shared channel (PUSCH) discontinuous transmission (DTX) detection result during UL scheduling. In an LTE FDD cell, if this switch is on, based on the PUSCH DTX detection result, the eNodeB determines whether to perform adaptive retransmission during UL scheduling and also adjusts the control channel element (CCE) aggregation level of the physical downlink control channel (PDCCH) carrying downlink control information (DCI) format 0. If an FDD cell is established on an LBBPc, this switch takes effect only when the cell uses less than four RX antennas and normal cyclic prefix (CP) in the uplink and the SrsCfgInd parameter in the SRSCfg MO is set to BOOLEAN_TRUE. Note that the LBBPc does not support PUSCH DTX detection for UEs with MUMIMO applied. In an LTE TDD cell, this switch takes effect only when the cell is configured with subframe configuration 2 or 5. After this switch takes effect, the eNodeB adjusts the CCE aggregation level based on the PUSCH DTX detection results. Note that LTE TDD cells established on LBBPc boards do not support PUSCH DTX detection. UlIblerAdjustSwitch: Indicates whether to enable the uplink initial block error rate (IBLER) adjustment Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
168
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
algorithm. If this switch is on, IBLER convergence target is adjusted to increase the cell edge throughput. When this switch is on, the recommended configuration of parameter DopMeasLevel in MO CellUlschAlgo is CLASS_1. UlEnhancedFssSwitch: Indicates whether to enable uplink load-based enhanced frequency selection. This switch applies only to FDD cells. UlIicsAlgoSwitch: Indicates whether to enable the UL IICS algorithm. If this switch is on, interference can be reduced based on accurate detection of user attributes and resource scheduling coordination, thereby increasing the cell edge throughput. This switch applies only to LTE TDD networks. UlEnhancedSrSchSwitch: Indicates whether uplink rescheduling is performed only when the On Duration timer for the DRX long cycle starts. Uplink rescheduling is required if the number of HARQ retransmissions for a scheduling request (SR) reaches the maximum value but the scheduling still fails. If this switch is on, uplink re-scheduling is performed only when the On Duration timer for the DRX long cycle starts. If this switch is off, uplink re-scheduling is performed immediately when the number of HARQ retransmissions for SR reaches the maximum value but the scheduling still fails. It is recommended that the switch be turned on in live networks. SchedulerCtrlPowerSwitch: Indicates whether the uplink scheduler performs scheduling without considering power control restrictions. If this switch is on, the uplink scheduler performs scheduling without considering power control restrictions, which ensures full utilization of the transmit power for all UEs. If this switch is off, the uplink scheduler considers power control restrictions while performing scheduling, which prevents full utilization of the transmit power for UEs at far or medium distances from the cell center. UlMinGbrSwitch: Indicates whether to enable uplink minimum guaranteed bit rate (GBR). If this switch is on, the minimum GBR of non-GBR services is ensured by increasing the scheduling priority of UEs whose non-GBR service rates are lower than the minimum GBR of GBR services. UlMbrCtrlSwitch: Indicates whether to enable uplink scheduling based on the maximum bit rate (MBR) and Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
169
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
guaranteed bit rate (GBR) on the GBR bearer. If this switch is on, the eNodeB performs uplink scheduling on GBR bearers based on the MBR and GBR. If this switch is off, the eNodeB performs uplink scheduling on GBR bearers based only on the GBR. MbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on MBR. If this switch is on, the eNodeB prioritizes UEs based on the MBRs during uplink scheduling. This parameter applies only to LTE TDD cells. UeAmbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on the aggregate maximum bit rate (AMBR) of UEs. If this switch is on, the eNodeB prioritizes UEs based on the AMBRs during uplink scheduling. This parameter applies only to LTE TDD cells. UlEnhancedDopplerSwitch: Indicates whether to enable enhanced uplink scheduling based on mobility speed. If this switch is on, enhanced uplink scheduling based on mobility speed is enabled. If this switch is on, the eNodeB determines whether a UE is a lowmobility UE based on the Doppler measurement in the physical layer, and then improves uplink frequency selective scheduling performance for low-mobility UEs. If this switch is off, enhanced uplink scheduling based on mobility speed is disabled. This switch takes effect only when the UlEnhancedDopplerSwitch parameter is set to CLASS_1. This switch does not take effect on cells established on an LBBPc. UlRaUserSchOptSw: Indicates whether the eNodeB raises the scheduling priority of UEs sending uplink access signaling, including MSG5 and the RRC Connection Reconfiguration Complete message. If this switch is on, the eNodeB raises the scheduling priority of UEs sending uplink access signaling. If this switch is off, the eNodeB does not raise the scheduling priority of UEs sending uplink access signaling. UlLast2RetransSchOptSwitch: Indicates whether to enable optimization on the scheduling policy for the last two retransmissions. If this switch is on, optimization on the scheduling policy for the last two retransmissions is enabled. If the UE transmit power is not limited, adaptive retransmission is used and the number of RBs increases in the last two retransmissions to increase the receive success rate of Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
170
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
the last two retransmissions and decrease uplink RBLER. If this switch is off, optimization on the scheduling policy for the last two retransmissions is disabled. This switch does not apply to LTE TDD cells. UlInterfFssSwitch: Indicates whether to enable interference-based uplink frequency-selective scheduling. This switch applies only to LTE FDD networks. UlSmallRBSpectralEffOptSw: Indicates whether to enable spectral efficiency optimization on uplink small RBs. If this switch is on, the optimization is enabled, thereby ensuring that the transmission block size calculated based on optimized spectral efficiency is not less than the traffic volume needs to be scheduled. If this switch is off, the optimization is disabled. PuschUsePucchRbSwitch: Indicates whether PUCCH RBs can be occupied by the PUSCH. In scenarios with a single user, if this switch is on, PUCCH RBs can be occupied by the PUSCH. If this switch is off, PUCCH RBs cannot be occupied by the PUSCH. In scenarios with multiple users, PUCCH RBs cannot be occupied by the PUSCH no matter whether this switch is on or off. PuschDtxSchOptSwitch: If this switch is on, the eNodeB determines whether to perform adaptive retransmission during UL scheduling based on the PUSCH DTX detection result. This switch takes effect only when subframe configuration 2 or 5 is used. If a TDD cell is established on an LBBPc, PUSCH DTX detection is not supported. This switch applies only to LTE TDD cells. PrachRbReuseSwitch:If this switch is on, the PUSCH and PRACH transmissions can use the same resource. If this switch is off, the PUSCH and PRACH transmissions cannot use the same resource. This switch applies only to LTE TDD cells. ULFSSAlgoswitch:If this switch is off, uplink frequency-selective scheduling is disabled. If this switch is on, uplink frequency-selective scheduling is enabled. This switch is invalid if the HighSpeedFlag parameter in the Cell MO is set to HIGH_SPEED(High speed cell flag) or
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
171
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
ULTRA_HIGH_SPEED(Ultra high speed cell flag), that is, uplink frequency-selective scheduling is disabled in high speed and ultra high speed mobility conditions. This switch applies only to LTE TDD cells. SrSchDataAdptSw: Indicates whether to enable data volume adaption in SR scheduling. Data volume adaption in SR scheduling is enabled only when this option is selected. UlFssUserThdStSwitch: UlFssUserThdStSwitch: Indicates whether to enable the optimization policy on the UE number threshold for frequency selective scheduling. The optimization policy is enabled only when this option is selected. GUI Value Range: SpsSchSwitch(SpsSchSwitch), SinrAdjustSwitch(SinrAdjustSwitch), PreAllocationSwitch(PreAllocationSwitch), UlVmimoSwitch(UlVmimoSwitch), TtiBundlingSwitch(TtiBundlingSwitch), ImIcSwitch(ImIcSwitch), SmartPreAllocationSwitch(SmartPreAllocationSwitch), PuschDtxSwitch(PuschDtxSwitch), UlIblerAdjustSwitch(UlIblerAdjustSwitch), UlEnhancedFssSwitch(UlEnhancedFssSwitch), UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch), SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch), UlIicsAlgoSwitch(UlIicsAlgoSwitch), UlMinGbrSwitch(UlMinGbrSwitch), UlMbrCtrlSwitch(UlMbrCtrlSwitch), MbrUlSchSwitch(MbrUlSchSwitch), UeAmbrUlSchSwitch(UeAmbrUlSchSwitch), UlEnhancedDopplerSwitch(UlEnhancedDopplerSwitch), UlRaUserSchOptSw(UlRaUserSchOptSw), UlLast2RetransSchOptSwitch(UlLast2RetransSchOpt Switch), UlInterfFssSwitch(UlInterfFssSwitch), UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEfficiencyOptSw), PuschUsePucchRbSwitch(PuschUsePucchRbSwitch), PuschDtxSchOptSwitch(PuschDtxSchOptSwitch), ULFSSAlgoSwitch(ULFSSAlgoSwitch), PrachRbReuseSwitch(PrachRbReuseSwitch), SrSchDataAdptSw(SrSchDataAdptSw), UlFssUserThdStSwitch(UlFssUserThdStSwitch) Unit: None Actual Value Range: SpsSchSwitch, SinrAdjustSwitch, PreAllocationSwitch, UlVmimoSwitch, TtiBundlingSwitch, ImIcSwitch, Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
172
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
SmartPreAllocationSwitch, PuschDtxSwitch, UlIblerAdjustSwitch, UlEnhancedFssSwitch, UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch, UlMinGbrSwitch, UlMbrCtrlSwitch, MbrUlSchSwitch, UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch, UlRaUserSchOptSw, UlLast2RetransSchOptSwitch, UlInterfFssSwitch, UlSmallRBSpectralEffOptSw, PuschUsePucchRbSwitch, PuschDtxSchOptSwitch, ULFSSAlgoSwitch, PrachRbReuseSwitch, SrSchDataAdptSw, UlFssUserThdStSwitch Default Value: SpsSchSwitch:Off, SinrAdjustSwitch:On, PreAllocationSwitch:On, UlVmimoSwitch:Off, TtiBundlingSwitch:Off, ImIcSwitch:Off, SmartPreAllocationSwitch:Off, PuschDtxSwitch:On, UlIblerAdjustSwitch:Off, UlEnhancedFssSwitch:On, UlEnhancedSrSchSwitch:Off, SchedulerCtrlPowerSwitch:Off, UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off, UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off, UeAmbrUlSchSwitch:Off, UlEnhancedDopplerSwitch:Off, UlRaUserSchOptSw:Off, UlLast2RetransSchOptSwitch:Off, UlInterfFssSwitch:Off, UlSmallRBSpectralEffOptSw:Off, PuschUsePucchRbSwitch:Off, PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On, PrachRbReuseSwitch:Off, SrSchDataAdptSw:On, UlFssUserThdStSwitch:Off CellUlsc hAlgo
SrMask Switch
MOD CELLU LSCHA LGO LST CELLU LSCHA LGO
LOFD-0 01016 / TDLOF D-00101 6
VoIP Semipersisten t Scheduli ng
Meaning: Indicates whether to enable scheduling request (SR) masking in logical channels for UEs complying with 3GPP Release 9 or later when the SpsSchSwitch option under the UlSchSwitch parameter is selected. If this parameter is set to ON(On), SR masking in logical channels is enabled. If this parameter is set to OFF(Off), SR masking in logical channels is disabled. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: OFF(Off)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
173
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
SpsRelT hd
MOD CELLU LSCHA LGO
LOFD-0 0101502 / TDLOF D-00101 502
Dynami c Scheduli ng
Meaning: Indicates the threshold for the number of consecutive zero-payload packets received by the eNodeB. After receiving consecutive zero-payload packets of a number that is equal to the value of this parameter, the eNodeB performs implicit release of semi-persistent resources.
LST CELLU LSCHA LGO
GUI Value Range: 2~3 Unit: None Actual Value Range: 2~3 Default Value: 2
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
174
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellAlg oSwitch
UlPcAlg oSwitch
MOD CELLA LGOSW ITCH
LBFD-0 02009 / TDLBF D-00200 9
Broadca st of system informat ion
Meaning:
LBFD-0 02026 / TDLBF D-00202 6
Uplink Power Control
LST CELLA LGOSW ITCH
LBFD-0 81101 / TDLBF D-08110 4
Issue 03 (2015-06-30)
PUCCH Outer Loop Power Control
Indicates the switches used to enable or disable power control for the PUSCH or PUCCH. CloseLoopSpsSwitch: Indicates whether to enable closed-loop power control for the PUSCH in semipersistent scheduling mode. If this switch is on, TPC commands are adjusted based on correctness of the received initial-transmission packets to decrease the IBLER. InnerLoopPuschSwitch: Indicates whether to enable inner-loop power control for the PUSCH in dynamic scheduling mode. Inner-loop power control for the PUSCH in dynamic scheduling mode is enabled only when this switch is on. PhSinrTarUpdateSwitch: None. InnerLoopPucchSwitch: Indicates whether to enable inner-loop power control for the PUCCH. Inner-loop power control for the PUCCH is enabled only when this switch is on. OiSinrTarUpdateSwitch: None. PowerSavingSwitch: None. CloseLoopOptPUSCHSwitch: Indicates whether to enable the optimization on closed-loop power control for the PUSCH in dynamic scheduling mode. This parameter applies only to LTE TDD cells. PucchPcDtxSinrSwitch: Indicates whether the eNodeB processes the measured uplink SINR in the DTX state when the PUCCH DTX is detected. If this switch is off, the eNodeB does not process the measured uplink SINR in the DTX state when the PUCCH DTX is detected. If this switch is on, the eNodeB processes the measured uplink SINR even when PUCCH DTX is detected, generates power control commands based on the SINR, and delivers the power control commands to UEs. PuschIoTCtrlSwitch: Indicates whether to enable interference control in closed-loop power control for the PUSCH in dynamic scheduling mode. Interference control in closed-loop power control for the PUSCH in dynamic scheduling mode is enabled only when this switch is on. SrsPcSwitch: Indicates whether to enable SRS power control adjustment. SRS power control adjustment is enabled only when this switch is on. This switch applies only to LTE TDD. NearPointUeOptPUSCHSwitch: Indicates whether to apply optimized closed-loop power control for the PUSCH to UEs near the cell center. The optimization helps UEs near the cell center to avoid unnecessary power lowering due to inter-RAT or abrupt interference. If this switch is on, optimized closedloop power control for the PUSCH is applied to UEs
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
175
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
near the cell center. If this switch is off, optimized closed-loop power control for the PUSCH is not applied to UEs near the cell center. This switch applies only to LTE FDD cells. PuschRsrpHighThdSwitch: Indicates whether closed-loop power control for the PUSCH limits the maximum value of RSRP. If this switch is off, closed-loop power control for the PUSCH does not limit the maximum value of RSRP. If this switch is on, the maximum value of RSRP cannot exceed the RSRP value specified by the PuschRsrpHighThd parameter in the CellAlgoSwitch in this version. This switch applies only to LTE FDD cells. OuterLoopPucchSwitch: Indicates whether to enable outer-loop PUCCH power control. Outer-loop PUCCH power control is enabled only when this switch is on.This option does not apply to cells established on LBBPc boards. GroupPCForPucchSwitch: Indicates whether to enable group power control for the PUCCH in dynamic scheduling mode. This switch applies only to LTE TDD cells in which UEs must support group power control for the PUCCH. GUI Value Range: CloseLoopSpsSwitch(CloseLoopSpsSwitch), InnerLoopPuschSwitch(InnerLoopPuschSwitch), PhSinrTarUpdateSwitch(PhSinrTarUpdateSwitch), InnerLoopPucchSwitch(InnerLoopPucchSwitch), OiSinrTarUpdateSwitch(OiSinrTarUpdateSwitch), PowerSavingSwitch(PowerSavingSwitch), CloseLoopOptPUSCHSwitch(CloseLoopOptPUSCHSwitch), PucchPcDtxSinrSwitch(PucchPcDtxSinrSwitch), PuschIoTCtrlSwitch(PuschIoTCtrlSwitch), SrsPcSwitch(SrsPcSwitch), NearPointUeOptPUSCHSwitch(NearPointUeOptPUSCHSwitch), PuschRsrpHighThdSwitch(PuschRsrpHighThdSwitch), OuterLoopPucchSwitch(OuterLoopPucchSwitch), GroupPCForPucchSwitch(GroupPCForPucchSwitch) Unit: None Actual Value Range: CloseLoopSpsSwitch, InnerLoopPuschSwitch, PhSinrTarUpdateSwitch, InnerLoopPucchSwitch, OiSinrTarUpdateSwitch, PowerSavingSwitch, CloseLoopOptPUSCHSwitch, PucchPcDtxSinrSwitch, PuschIoTCtrlSwitch, SrsPcSwitch, NearPointUeOptPUSCHSwitch,
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
176
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
PuschRsrpHighThdSwitch, OuterLoopPucchSwitch, GroupPCForPucchSwitch Default Value: CloseLoopSpsSwitch:Off, InnerLoopPuschSwitch:On, PhSinrTarUpdateSwitch:Off, InnerLoopPucchSwitch:On, OiSinrTarUpdateSwitch:Off, PowerSavingSwitch:Off, CloseLoopOptPUSCHSwitch:Off, PucchPcDtxSinrSwitch:Off, PuschIoTCtrlSwitch:Off, SrsPcSwitch:On, NearPointUeOptPUSCHSwitch:Off, PuschRsrpHighThdSwitch:Off, OuterLoopPucchSwitch:Off, GroupPCForPucchSwitch:Off
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
177
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellAlg oSwitch
DlPcAlg oSwitch
MOD CELLA LGOSW ITCH
LBFD-0 02003 / TDLBF D-00200 3
Physical Channel Manage ment
Meaning:
Broadca st of system informat ion
PdschSpsPcSwitch: Indicates the switch for power control during semi-persistent scheduling on the PDSCH. If the switch is off, power is allocated evenly during semi-persistent scheduling on the PDSCH. If the switch is on, power control is applied during semipersistent scheduling on the PDSCH, ensuring communication quality (indicated by IBLER) of VoIP services in the QPSK modulation scheme.
LST CELLA LGOSW ITCH
LBFD-0 02009 / TDLBF D-00200 9 LBFD-0 02016 / TDLBF D-00201 6
Dynami c Downlin k Power Allocati on
Indicates the switches used to enable or disable power control for PDSCH, PDCCH, and PHICH.
PhichInnerLoopPcSwitch: Indicates the switch for PHICH inner-loop power control. If the switch is off, only the initial transmit power for the PHICH is set. If the switch is on, the eNodeB controls the physical channel transmit power to enable the receive SINR to converge to the target SINR. PdcchPcSwitch: Indicates the switch for PDCCH power control. If the switch is off, power is allocated evenly to PDCCH. If the switch is on, power allocated to PDCCH is adjusted dynamically. EDlMaxTXPwrSwitch: Indicates the switch for enhanced maximum TX power of the cell. If this switch is off, the maximum TX power of the cell is determined by the reference signal (RS) power and the scaling factor indexes Pa and Pb. If this switch is on, the maximum TX power of the cell can be increased to improve the RB usage in the cell. This switch has no impact on the TDD 20M, TDD 15HMz and 10M cell. BFModeUserPwrSwitch: Specifies whether to turn on the UE power optimization switch in BF mode. If the BFModeUserPwrSwitch check box is cleared, BF UEs adopt the existing power allocation principle. If the BFModeUserPwrSwitch check box is selected, the eNodeB increases the BF UE power based on the configured power headroom. This switch applies only to LTE TDD networks. SigPowerIncreaseSwitch: Indicates the switch controlling signaling power improvement. If this switch is off, the signaling is transmitted using the original power during network entry. If this switch is on, the PDSCH transmit power increases when scheduling is performed for downlink retransmission
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
178
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
of signaling during network entry. This switch applies only to LTE TDD networks. GUI Value Range: PdschSpsPcSwitch, PhichInnerLoopPcSwitch, PdcchPcSwitch, EDlMaxTXPwrSwitch, BFModeUserPwrSwitch, SigPowerIncreaseSwitch Unit: None Actual Value Range: PdschSpsPcSwitch, PhichInnerLoopPcSwitch, PdcchPcSwitch, EDlMaxTXPwrSwitch, BFModeUserPwrSwitch, SigPowerIncreaseSwitch Default Value: PdschSpsPcSwitch:Off, PhichInnerLoopPcSwitch:Off, PdcchPcSwitch:On, EDlMaxTXPwrSwitch:Off, BFModeUserPwrSwitch:Off, SigPowerIncreaseSwitch:Off PdcpRo hcPara
RohcSw itch
MOD PDCPR OHCPA RA LST PDCPR OHCPA RA
LOFD-0 01017 / TDLOF D-00101 7
RObust Header Compre ssion (ROHC)
Meaning: Indicates whether to enable ROHC. Set this parameter to ON if the eNodeB is expected to support VoIP or video services. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: OFF(Off)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
179
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellUlsc hAlgo
UlVoipR lcMaxSe gNum
MOD CELLU LSCHA LGO
LOFD-0 0101502 / TDLOF D-00101 502
Dynami c Scheduli ng
Meaning:
LST CELLU LSCHA LGO
Indicates whether to apply upper limit control on service data unit (SDU) segmentation at the radio link control (RLC) layer in the uplink for VoIP services scheduled in non-TTI bundling mode and the maximum SDU segments at the RLC layer. If this parameter is set to 0, the upper limit control on SDU segmentation at the RLC layer is disabled in the uplink for VoIP services scheduled in non-TTI bundling mode. If this parameter is set to a non-zero value X, upper limit control on SDU segmentation at the RLC layer is enabled and a maximum of X SDU segments that can be divided for VoIP services in uplink dynamic scheduling in non-TTI bundling mode. GUI Value Range: 0~20 Unit: None Actual Value Range: 0~20 Default Value: 0
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
180
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
GlobalP rocSwitc h
LcgProfi le
MOD GLOBA LPROC SWITC H
LBFD-0 02025 / TDLBF D-00202 5
Basic Scheduli ng
Meaning:
LST GLOBA LPROC SWITC H
LOFD-0 0101502 / TDLOF D-00101 502
Dynami c Scheduli ng
Currently, three logical channel group profiles are available. If this parameter is set to LCG_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 nonGBR services are assigned logical channel groups 0, 1, 2, and 3, respectively.
Indicates the logical channel group configuration.
If this parameter is set to LCG_PROFILE_1, the control-plane services, VoIP services, GBR services, high-priority non-GBR services, and low-priority nonGBR services are assigned logical channel groups 0, 1, 2, and 3, respectively. If this parameter is set to LCG_PROFILE_2, the control-plane services, VoIP services, high-priority non-GBR services, and low-priority non-GBR services are assigned logical channel groups 0, 1, 2, 3, respectively. In addition, services with a QCI of 2 to 4 are also assigned logical channel group 1. If this parameter is set to LCG_PROFILE_2, VoIP services must be carried by bearers with a QCI of 1 and bearers with a QCI of 2 to 4 are not used. The parameter value LCG_PROFILE_2 does not apply to LTE TDD. GUI Value Range: LCG_PROFILE_0, LCG_PROFILE_1, LCG_PROFILE_2 Unit: None Actual Value Range: LCG_PROFILE_0, LCG_PROFILE_1, LCG_PROFILE_2 Default Value: LCG_PROFILE_0
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
181
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
DrxPara Group
LongDr xCycle
ADD DRXPA RAGRO UP
LBFD-0 02017 / TDLBF D-00201 7
DRX
Meaning: Indicates the length of the long DRX cycle. Because of the impact of the SRS bandwidth and TA period specified by the TimeAlignmentTimer parameter, the actual value of this parameter assigned to a UE may be less than the configured value. In addition, the configured value will be rounded down to an integral multiple of 10. Therefore, you are advised to configure this parameter to a value that is an integral multiple of 10. If users hope that the value actually assigned to a UE is equal to or greater than 80 ms, set the TimeAlignmentTimer parameter to a value equal to or greater than 10240 ms. If the TimingAdvCmdOptSwitch parameter is set to ON, it is recommended that the LongDrxCycle parameter be set to a value smaller than or equal to 320 ms. Otherwise, the uplink time alignment performance of UEs is affected. If the TimingAdvCmdOptSwitch parameter is set to ON, it is recommended that the TimeAlignmentTimer parameter be set to sf10240. A smaller value of the TimeAlignmentTimer parameter, such as sf5120, increases the probability that UEs in DRX mode become uplink asynchronized. The length of the long DRX cycle must be smaller than the length of the PDCP packet discarding timer for the corresponding QCI. Otherwise, packet loss occurs during a ping operation or low-traffic service.
MOD DRXPA RAGRO UP LST DRXPA RAGRO UP
GUI Value Range: SF10(10 subframes), SF20(20 subframes), SF32(32 subframes), SF40(40 subframes), SF64(64 subframes), SF80(80 subframes), SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes), SF1024(1024 subframes), SF1280(1280 subframes), SF2048(2048 subframes), SF2560(2560 subframes) Unit: subframe Actual Value Range: SF10, SF20, SF32, SF40, SF64, SF80, SF128, SF160, SF256, SF320, SF512, SF640, SF1024, SF1280, SF2048, SF2560 Default Value: SF40(40 subframes)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
182
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
Drx
DrxAlg Switch
MOD DRX
LBFD-0 02017 / TDLBF D-00201 7
DRX
Meaning: Indicates the DRX switch. The setting of this parameter has no effect on dynamic DRX. DRX applies to a CA UE only when this parameter is set to ON(On) on both eNodeBs to which the PCell and SCell of the CA UE belong.
LST DRX
GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: OFF(Off)
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
183
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
CellStan dardQci
QciPrior ityForH o
MOD CELLS TANDA RDQCI
LBFD-0 0201801
LST CELLS TANDA RDQCI
LBFD-0 0201804
Coverag e Based Intrafrequenc y Handov er
Meaning: Indicates the QCI priority used by each QCI-based handover algorithm. A larger value of this parameter indicates a lower priority. This parameter applies to handover parameter selection based on QCI priorities, target frequency selection in service-based inter-frequency handovers, and inter-RAT handover policy selection. For a service that involves all the preceding selection, the setting of this parameter determines the handover parameter, target frequency, and handover policy corresponding to a QCI.
LBFD-0 0201802
LBFD-0 0201805 LOFD-0 01072 LOFD-0 01073
Coverag e Based Interfrequenc y Handov er Distance Based Interfrequenc y Handov er
GUI Value Range: 1~9 Unit: None Actual Value Range: 1~9 Default Value: 9
Service Based Interfrequenc y Handov er Distance based InterRAT handove r to UTRAN Distance based InterRAT handove r to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
184
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
IntraFre qHoGro up
IntraFre qHoA3 Hyst
ADD INTRA FREQH OGROU P
LBFD-0 0201801 / TDLBF D-00201 801
Coverag e Based Intrafrequenc y Handov er
Meaning: Indicates the hysteresis for intra-frequency handover event A3. This parameter decreases frequent event triggering due to radio signal fluctuations and reduces the probability of handover decision errors and ping-pong handovers. A larger value of this parameter results in a lower probability. The hysteresis for event inter-frequency handover event A3 is the same as the value of this parameter. For details, see 3GPP TS 36.331.
MOD INTRA FREQH OGROU P
GUI Value Range: 0~30
LST INTRA FREQH OGROU P IntraFre qHoGro up
IntraFre qHoA3 Offset
ADD INTRA FREQH OGROU P MOD INTRA FREQH OGROU P LST INTRA FREQH OGROU P
Issue 03 (2015-06-30)
Unit: 0.5dB Actual Value Range: 0~15 Default Value: 2
LBFD-0 0201801 / TDLBF D-00201 801
Coverag e Based Intrafrequenc y Handov er
Meaning: Indicates the offset for event A3. If the parameter is set to a large value, an intra-frequency handover is performed only when the signal quality of the neighboring cell is significantly better than that of the serving cell and other triggering conditions are met. For details, see 3GPP TS 36.331. GUI Value Range: -30~30 Unit: 0.5dB Actual Value Range: -15~15 Default Value: 2
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
185
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
IntraFre qHoGro up
IntraFre qHoA3T imeToTr ig
ADD INTRA FREQH OGROU P
LBFD-0 0201801 / TDLBF D-00201 801
Coverag e Based Intrafrequenc y Handov er
Meaning:
MOD INTRA FREQH OGROU P
Indicates the time-to-trigger for intra-frequency handover event A3. When the UE detects that the signal quality in the serving cell and that in at least one neighboring cell meet the entering condition, it does not immediately send a measurement report to the eNodeB. Instead, the UE sends a report only when the signal quality meets the entering condition throughout the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of incorrect handovers, preventing unnecessary handovers. The time-to-trigger for inter-frequency handover event A3 is the same as the value of this parameter.
LST INTRA FREQH OGROU P
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: ms Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 320ms InterFre qHoGro up
InterFre qHoA1 A2Hyst
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Issue 03 (2015-06-30)
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the hysteresis of event A1/A2 for triggering inter-frequency measurement. This parameter is used to prevent frequent triggering of event evaluation caused by radio signal fluctuation. In this way, the probability of ping-pong handovers or handover decision errors is reduced. A larger value of this parameter results in a lower probability. GUI Value Range: 0~30 Unit: 0.5dB Actual Value Range: 0~15 Default Value: 2
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
186
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
InterFre qHoA1 A2Time ToTrig
ADD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning:
MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Indicates the time-to-trigger of event A1/A2 for triggering inter-frequency measurement. When detecting that the signal quality in the serving cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of wrong handovers. In summary, it helps prevent unnecessary handovers. GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: ms Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 640ms
InterFre qHoGro up
InterFre qHoA1T hdRsrp
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Issue 03 (2015-06-30)
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the RSRP threshold for event A1 related to event-A4/A5-triggered inter-frequency handover. When the measured RSRP value exceeds this threshold, a measurement report will be sent. GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -105
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
187
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
InterFre qHoA1T hdRsrq
ADD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning:
MOD INTERF REQHO GROUP
InterFre qHoA2T hdRsrp
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP
InterFre qHoA2T hdRsrq
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Issue 03 (2015-06-30)
GUI Value Range: -40~-6 Actual Value Range: -20~-3 Default Value: -20
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the RSRP threshold for event A2 related to event-A4/A5-triggered inter-frequency handover. When the measured RSRP value is lower than this threshold, a measurement report will be sent. GUI Value Range: -140~-43 Unit: dBm
LST INTERF REQHO GROUP InterFre qHoGro up
When the measured RSRQ value exceeds this threshold, a measurement report will be sent. Unit: 0.5dB
LST INTERF REQHO GROUP InterFre qHoGro up
Indicates the RSRQ threshold for event A1 related to event-A4/A5-triggered inter-frequency handover.
Actual Value Range: -140~-43 Default Value: -109
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the RSRQ threshold for event A2 related to event-A4/A5-triggered inter-frequency handover. When the measured RSRQ value is lower than this threshold, a measurement report will be sent. GUI Value Range: -40~-6 Unit: 0.5dB Actual Value Range: -20~-3 Default Value: -24
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
188
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
InterFre qHoA4 Hyst
ADD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the hysteresis for event A4. This parameter is used to prevent frequent triggering of event evaluation caused by radio signal fluctuation. In this way, the probability of ping-pong handovers or handover decision errors is reduced. A larger value of this parameter results in a lower probability.
Distance Based Interfrequenc y Handov er
Unit: 0.5dB
MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
LBFD-0 0201804 / TDLBF D-00201 804 LBFD-0 0201805 / TDLBF D-00201 805
InterFre qHoGro up
InterFre qHoA4T hdRsrp
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Issue 03 (2015-06-30)
LBFD-0 0201802 / TDLBF D-00201 802 LBFD-0 0201804 / TDLBF D-00201 804
GUI Value Range: 0~30 Actual Value Range: 0~15 Default Value: 2
Service Based Interfrequenc y Handov er Coverag e Based Interfrequenc y Handov er Distance Based Interfrequenc y Handov er
Meaning: Indicates the RSRP threshold for event A4 related to coverage-based inter-frequency handover. When the measured RSRP value exceeds this threshold, event A4 is reported. The value of this parameter is also used as the RSRP threshold for event A4 related to distance-based, UL-power-based, or SPID-based inter-frequency handover back to the HPLMN. GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -105
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
189
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
InterFre qHoA4T hdRsrq
ADD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the RSRQ threshold for event A4 related to coverage-based inter-frequency handover. When the measured RSRQ value exceeds this threshold, event A4 is reported. The value of this parameter is also used as the RSRQ threshold for event A4 related to distance-based, UL-power-based, or SPID-based inter-frequency handover back to the HPLMN.
MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
InterFre qHoGro up
InterFre qHoA4T imeToTr ig
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
LBFD-0 0201804 / TDLBF D-00201 804
LBFD-0 0201802 / TDLBF D-00201 802 LBFD-0 0201804 / TDLBF D-00201 804 LBFD-0 0201805 / TDLBF D-00201 805
Distance Based Interfrequenc y Handov er Coverag e Based Interfrequenc y Handov er Distance Based Interfrequenc y Handov er Service Based Interfrequenc y Handov er
GUI Value Range: -40~-6 Unit: 0.5dB Actual Value Range: -20~-3 Default Value: -20 Meaning: Indicates the time-to-trigger for event A4 for the interfrequency handover. When detecting that the signal quality in at least one neighboring cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of wrong handovers. In summary, it helps prevent unnecessary handovers. GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: ms Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 640ms
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
190
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
InterFre qHoA3 Offset
ADD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the offset for event A3 associated with inter-frequency handover. This parameter determines the border between the serving cell and the neighboring cell. If the parameter is set to a large value, an inter-frequency handover is performed only when the signal quality of the neighboring cell is significantly better than that of the serving cell and other triggering conditions are met. For details, see 3GPP TS 36.331.
MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
GUI Value Range: -30~30 Unit: 0.5dB Actual Value Range: -15~15 Default Value: 2
InterFre qHoGro up
A3Inter FreqHo A1ThdR srp
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
A3Inter FreqHo A2ThdR srp
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Issue 03 (2015-06-30)
GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -95
LST INTERF REQHO GROUP InterFre qHoGro up
Meaning: Indicates the RSRP threshold for event A1 related to event-A3-triggered inter-frequency handover. When the measured RSRP value exceeds this threshold, a measurement report will be sent.
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning: Indicates the RSRP threshold for event A2 related to event-A3-triggerd inter-frequency handover. When the measured RSRP value is lower than this threshold, a measurement report will be sent. GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -99
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
191
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
InterFre qHoA5T hd1Rsrp
ADD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
Meaning:
MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Indicates the RSRP threshold 1 in the serving cell of event A5 for triggering inter-frequency handovers. When the measured RSRP in the serving cell is smaller than the value of this parameter and the RSRP or RSRQ in the neighboring cell is higher than the value of InterFreqHoA4ThdRsrp or InterFreqHoA4ThdRsrq, the UE reports event A5. GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -109
InterFre qHoGro up
InterFre qHoA5T hd1Rsrq
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP
LBFD-0 0201802 / TDLBF D-00201 802
Coverag e Based Interfrequenc y Handov er
LST INTERF REQHO GROUP
Meaning: Indicates the RSRQ threshold 1 in the serving cell of event A5 for triggering inter-frequency handovers. When the measured RSRQ in the serving cell is smaller than the value of this parameter and the RSRP or RSRQ in the neighboring cell is higher than the value of InterFreqHoA4ThdRsrp or InterFreqHoA4ThdRsrq, the UE reports event A5. GUI Value Range: -40~-6 Unit: 0.5dB Actual Value Range: -20~-3 Default Value: -24
InterFre qHoGro up
InterFre qLoadB asedHo A4ThdR srp
ADD INTERF REQHO GROUP MOD INTERF REQHO GROUP LST INTERF REQHO GROUP
Issue 03 (2015-06-30)
LBFD-0 0201805 / TDLBF D-00201 805
Service Based Interfrequenc y Handov er
Meaning: Indicates the RSRP threshold for event A4 related to load-based inter-frequency handover. When the measured RSRP value exceeds this threshold, event A4 is reported. The value of this parameter is also used as the RSRP threshold for event A4 related to frequency-priority-based handover, service-based inter-frequency handover, inter-frequency handover of low-speed UEs, or redirection of high-speed UEs. GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -103
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
192
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
InterFre qLoadB asedHo A4ThdR srq
ADD INTERF REQHO GROUP
LBFD-0 0201805 / TDLBF D-00201 805
Service Based Interfrequenc y Handov er
Meaning: Indicates the RSRQ threshold for event A4 related to load-based inter-frequency handover. When the measured RSRQ value exceeds this threshold, event A4 is reported. The value of this parameter is also used as the RSRQ threshold for event A4 related to frequency-priority-based, service-based interfrequency handover, inter-frequency handover of lowspeed UEs, or redirection of high-speed UEs.
MOD INTERF REQHO GROUP
GUI Value Range: -40~-6
LST INTERF REQHO GROUP InterFre qHoGro up
InterFre qHoGro up
FreqPriI nterFreq HoA1Th dRsrp
FreqPriI nterFreq HoA1Th dRsrq
Issue 03 (2015-06-30)
ADD INTERF REQHO GROUP
Unit: 0.5dB Actual Value Range: -20~-3 Default Value: -18 None
None
Meaning: Indicates the RSRP threshold for frequencypriority-based inter-frequency measurement event A1. When the measured RSRP value exceeds this threshold, an event A1 report will be sent.
MOD INTERF REQHO GROUP
GUI Value Range: -140~-43
LST INTERF REQHO GROUP
Default Value: -85
ADD INTERF REQHO GROUP
Unit: dBm Actual Value Range: -140~-43
None
None
Meaning: Indicates the RSRQ threshold for frequency-prioritybased inter-frequency measurement event A1.
MOD INTERF REQHO GROUP
When the measured RSRQ value exceeds this threshold, an event A1 report will be sent.
LST INTERF REQHO GROUP
Actual Value Range: -20~-3
GUI Value Range: -40~-6 Unit: 0.5dB Default Value: -16
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
193
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterFre qHoGro up
FreqPriI nterFreq HoA2Th dRsrp
ADD INTERF REQHO GROUP
None
None
Meaning:
InterFre qHoGro up
FreqPriI nterFreq HoA2Th dRsrq
Issue 03 (2015-06-30)
Indicates the RSRP threshold for frequency-prioritybased inter-frequency measurement event A2.
MOD INTERF REQHO GROUP
If the measured RSRP value is less than this threshold, an event A2 report will be sent.
LST INTERF REQHO GROUP
Actual Value Range: -140~-43
ADD INTERF REQHO GROUP
GUI Value Range: -140~-43 Unit: dBm Default Value: -87
None
None
Meaning: Indicates the RSRQ threshold for inter-frequency measurement event A2.
MOD INTERF REQHO GROUP
When the measured RSRQ value is below this threshold, a measurement report will be sent.
LST INTERF REQHO GROUP
Actual Value Range: -20~-3
GUI Value Range: -40~-6 Unit: 0.5dB Default Value: -20
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
194
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCom mGroup
InterRat HoA1A 2Hyst
ADD INTER RATHO COMM GROUP
LOFD-0 01019 / TDLOF D-00101 9
MOD INTER RATHO COMM GROUP
LOFD-0 01020 / TDLOF D-00102 0
PS InterRAT Mobility between EUTRAN and UTRAN
Meaning: Indicates the hysteresis of event A1/A2 for triggering inter-RAT measurement. This parameter is used to prevent frequent triggering of event evaluation caused by radio signal fluctuation. In this way, the probability of ping-pong handovers or handover decision errors is reduced. A larger value of this parameter results in a lower probability. Unit: 0.5dB
LST INTER RATHO COMM GROUP
LOFD-0 01021 / TDLOF D-00102 1
PS InterRAT Mobility between EUTRAN and GERAN
TDLOF D-00102 2 TDLOF D-00102 3
GUI Value Range: 0~30 Actual Value Range: 0~15 Default Value: 2
PS InterRAT Mobility between EUTRAN and CDMA2 000 SRVCC to UTRAN SRVCC to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
195
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCom mGroup
InterRat HoA1A 2TimeT oTrig
ADD INTER RATHO COMM GROUP
LOFD-0 01019 / TDLOF D-00101 9
Meaning:
MOD INTER RATHO COMM GROUP
LOFD-0 01020 / TDLOF D-00102 0
PS InterRAT Mobility between EUTRAN and UTRAN
LST INTER RATHO COMM GROUP
LOFD-0 01021 / TDLOF D-00102 1 TDLOF D-00102 2 TDLOF D-00102 3
PS InterRAT Mobility between EUTRAN and GERAN PS InterRAT Mobility between EUTRAN and CDMA2 000
Indicates the time-to-trigger of event A1/A2 for triggering inter-RAT measurement. When detecting that the signal quality in the serving cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of wrong handovers. In summary, it helps prevent unnecessary handovers. GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: ms Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 640ms
SRVCC to UTRAN SRVCC to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
196
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCom mGroup
InterRat HoA1Th dRsrp
ADD INTER RATHO COMM GROUP
LOFD-0 01019 / TDLOF D-00101 9
Meaning: Indicates the RSRP threshold for inter-RAT measurement event A1. When the measured RSRP value of the serving cell exceeds this threshold, an event A1 report will be sent.
MOD INTER RATHO COMM GROUP
LOFD-0 01020 / TDLOF D-00102 0
PS InterRAT Mobility between EUTRAN and UTRAN
Default Value: -111
LST INTER RATHO COMM GROUP
LOFD-0 01021 / TDLOF D-00102 1
PS InterRAT Mobility between EUTRAN and GERAN
TDLOF D-00102 2 TDLOF D-00102 3
GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43
PS InterRAT Mobility between EUTRAN and CDMA2 000 SRVCC to UTRAN SRVCC to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
197
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCom mGroup
InterRat HoA1Th dRsrq
ADD INTER RATHO COMM GROUP
LOFD-0 01019 / TDLOF D-00101 9
Meaning:
MOD INTER RATHO COMM GROUP
LOFD-0 01020 / TDLOF D-00102 0
PS InterRAT Mobility between EUTRAN and UTRAN
LST INTER RATHO COMM GROUP
LOFD-0 01021 / TDLOF D-00102 1 TDLOF D-00102 2 TDLOF D-00102 3
PS InterRAT Mobility between EUTRAN and GERAN
Indicates the RSRQ threshold for inter-RAT measurement event A1. When the measured RSRQ value of the serving cell exceeds this threshold, an event A1 report will be sent. GUI Value Range: -40~-6 Unit: 0.5dB Actual Value Range: -20~-3 Default Value: -20
PS InterRAT Mobility between EUTRAN and CDMA2 000 SRVCC to UTRAN SRVCC to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
198
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCom mGroup
InterRat HoA2Th dRsrp
ADD INTER RATHO COMM GROUP
LOFD-0 01019 / TDLOF D-00101 9
Meaning:
MOD INTER RATHO COMM GROUP
LOFD-0 01020 / TDLOF D-00102 0
PS InterRAT Mobility between EUTRAN and UTRAN
LST INTER RATHO COMM GROUP
LOFD-0 01021 / TDLOF D-00102 1 TDLOF D-00102 2 TDLOF D-00102 3
PS InterRAT Mobility between EUTRAN and GERAN
Indicates the RSRP threshold for inter-RAT measurement event A2. When the measured RSRP value of the serving cell is below this threshold, an event A2 report will be sent. If you need to change the parameter value, you are advised to set this parameter to a value greater than the value of the BlindHoA1A2ThdRsrp parameter in the CellHoParaCfg MO. GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -115
PS InterRAT Mobility between EUTRAN and CDMA2 000 SRVCC to UTRAN SRVCC to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
199
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCom mGroup
InterRat HoA2Th dRsrq
ADD INTER RATHO COMM GROUP
LOFD-0 01019 / TDLOF D-00101 9
Meaning:
MOD INTER RATHO COMM GROUP
LOFD-0 01020 / TDLOF D-00102 0
PS InterRAT Mobility between EUTRAN and UTRAN
LST INTER RATHO COMM GROUP
LOFD-0 01021 / TDLOF D-00102 1 TDLOF D-00102 2 TDLOF D-00102 3
PS InterRAT Mobility between EUTRAN and GERAN
Indicates the RSRQ threshold for inter-RAT measurement event A2. When the measured RSRQ value of the serving cell is below this threshold, an event A2 report will be sent. If you need to change the parameter value, you are advised to set this parameter to a value greater than the value of the BlindHoA1A2ThdRsrq parameter in the CellHoParaCfg MO. GUI Value Range: -40~-6 Unit: 0.5dB Actual Value Range: -20~-3 Default Value: -24
PS InterRAT Mobility between EUTRAN and CDMA2 000 SRVCC to UTRAN SRVCC to GERAN
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
200
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoUtran Group
InterRat HoUtran B1ThdE cn0
ADD INTER RATHO UTRAN GROUP
LOFD-0 01019 / TDLOF D-00101 9
MOD INTER RATHO UTRAN GROUP
TDLOF D-00102 2
PS InterRAT Mobility between EUTRAN and UTRAN
Meaning: Indicates the Ec/N0 threshold for event B1 related to coverage-based inter-RAT handover to UTRAN. This parameter specifies the requirement for Ec/N0 of the target UTRAN cell. For a cell with large signal fading variance, set this parameter to a large value to prevent unnecessary handovers. For a cell with small signal fading variance, set this parameter to a small value to ensure timely handovers. A large value of this parameter results in a low probability of handover to the UTRAN cell, and a small value leads to a high probability. When the measurement value exceeds this threshold, a measurement report will be sent.
SRVCC to UTRAN
LST INTER RATHO UTRAN GROUP
GUI Value Range: -48~0 Unit: 0.5dB Actual Value Range: -24~0 Default Value: -24
InterRat HoUtran Group
InterRat HoUtran B1ThdR scp
ADD INTER RATHO UTRAN GROUP
LOFD-0 01019 / TDLOF D-00101 9
MOD INTER RATHO UTRAN GROUP
TDLOF D-00102 2
LST INTER RATHO UTRAN GROUP
Issue 03 (2015-06-30)
PS InterRAT Mobility between EUTRAN and UTRAN SRVCC to UTRAN
Meaning: Indicates the RSCP threshold for event B1 related to coverage-based inter-RAT handover to UTRAN. This parameter specifies the requirement for RSCP of the target UTRAN cell. When the measurement value exceeds this threshold, a measurement report will be sent. GUI Value Range: -120~-25 Unit: dBm Actual Value Range: -120~-25 Default Value: -103
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
201
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoUtran Group
InterRat HoUtran B1Hyst
ADD INTER RATHO UTRAN GROUP
LOFD-0 01019 / TDLOF D-00101 9
MOD INTER RATHO UTRAN GROUP
TDLOF D-00102 2
PS InterRAT Mobility between EUTRAN and UTRAN
Meaning: Indicates the hysteresis for event B1 related to inter-RAT handover to UTRAN. This parameter is used to prevent frequent triggering of event evaluation caused by radio signal fluctuation. In this way, the probability of ping-pong handovers or handover decision errors is reduced. A larger value of this parameter results in a lower probability of ping-pong handovers or handover decision errors.
SRVCC to UTRAN
GUI Value Range: 0~30
LST INTER RATHO UTRAN GROUP InterRat HoUtran Group
InterRat HoUtran B1Time ToTrig
Actual Value Range: 0~15 Default Value: 0
ADD INTER RATHO UTRAN GROUP
LOFD-0 01019 / TDLOF D-00101 9
MOD INTER RATHO UTRAN GROUP
TDLOF D-00102 2
LST INTER RATHO UTRAN GROUP
Unit: 0.5dB
PS InterRAT Mobility between EUTRAN and UTRAN SRVCC to UTRAN
Meaning: Indicates the time-to-trigger for event B1 related to inter-RAT handover to UTRAN. When detecting that the signal quality in at least one neighboring cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers and the number of wrong handovers, preventing unnecessary handovers. GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: ms Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 320ms
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
202
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoUtran Group
LdSvBa sedHoUt ranB1Th dEcn0
ADD INTER RATHO UTRAN GROUP
LOFD-0 01043
Service based interRAT handove r to UTRAN
Meaning:
TDLOF D-00102 2
MOD INTER RATHO UTRAN GROUP
SRVCC to UTRAN
LST INTER RATHO UTRAN GROUP
Indicates the Ec/N0 threshold for event B1 related to load- or service-based inter-RAT handover to UTRAN. This parameter specifies the requirement for Ec/N0 of the target UTRAN cell. When the measurement value exceeds this threshold, a measurement report may be sent. For a cell with large signal fading variance, set this parameter to a large value to prevent unnecessary handovers. For a cell with small signal fading variance, set this parameter to a small value to ensure timely handovers. GUI Value Range: -48~0 Unit: 0.5dB Actual Value Range: -24~0 Default Value: -18
InterRat HoUtran Group
LdSvBa sedHoUt ranB1Th dRscp
ADD INTER RATHO UTRAN GROUP MOD INTER RATHO UTRAN GROUP LST INTER RATHO UTRAN GROUP
Issue 03 (2015-06-30)
LOFD-0 01043 TDLOF D-00102 2
Service based interRAT handove r to UTRAN SRVCC to UTRAN
Meaning: Indicates the RSCP threshold for event B1 related to load- or service-based inter-RAT handover to UTRAN. This parameter specifies the requirement for RSCP of the target UTRAN cell. When the measurement value exceeds this threshold, a measurement report will be sent. GUI Value Range: -120~-25 Unit: dBm Actual Value Range: -120~-25 Default Value: -101
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
203
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoGera nGroup
InterRat HoGera nB1Hyst
ADD INTER RATHO GERAN GROUP
LOFD-0 01020 / TDLOF D-00102 0
MOD INTER RATHO GERAN GROUP
TDLOF D-00102 3
PS InterRAT Mobility between EUTRAN and GERAN
Meaning: Indicates the hysteresis for event B1 related to inter-RAT handover to GERAN. This parameter is used to prevent frequent triggering of event evaluation caused by radio signal fluctuation. In this way, the probability of ping-pong handovers or handover decision errors is reduced. A larger value of this parameter results in a lower probability of ping-pong handovers or handover decision errors.
SRVCC to GERAN
GUI Value Range: 0~30
LST INTER RATHO GERAN GROUP InterRat HoGera nGroup
InterRat HoGera nB1Thd
ADD INTER RATHO GERAN GROUP MOD INTER RATHO GERAN GROUP LST INTER RATHO GERAN GROUP
Issue 03 (2015-06-30)
Unit: 0.5dB Actual Value Range: 0~15 Default Value: 2
LOFD-0 01020 / TDLOF D-00102 0
PS InterRAT Mobility between EUTRAN and GERAN
Meaning: Indicates the RSSI threshold for event B1 related to coverage-based inter-RAT handover to GERAN. A UE sends a measurement report related to event B1 to the eNodeB when the RSSI in at least one GERAN cell exceeds this threshold and other triggering conditions are met. For details, see 3GPP TS 36.331. GUI Value Range: -110~-48 Unit: dBm Actual Value Range: -110~-48 Default Value: -100
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
204
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoGera nGroup
InterRat HoGera nB1Tim eToTrig
ADD INTER RATHO GERAN GROUP
LOFD-0 01020 / TDLOF D-00102 0
Meaning:
MOD INTER RATHO GERAN GROUP
TDLOF D-00102 3
PS InterRAT Mobility between EUTRAN and GERAN SRVCC to GERAN
LST INTER RATHO GERAN GROUP
Indicates the time-to-trigger for event B1 related to inter-RAT handover to GERAN. When detecting that the signal quality in at least one neighboring cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers and the number of wrong handovers, preventing unnecessary handovers. GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: ms Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 640ms
InterRat HoGera nGroup
LdSvBa sedHoG eranB1T hd
ADD INTER RATHO GERAN GROUP MOD INTER RATHO GERAN GROUP LST INTER RATHO GERAN GROUP
Issue 03 (2015-06-30)
LOFD-0 01046 / TDLOF D-00104 6
Service based interRAT handove r to GERAN
Meaning: Indicates the RSSI threshold for event B1 related to load- or service-based inter-RAT handover to GERAN. When the measured RSSI value exceeds this threshold, a measurement report will be sent. GUI Value Range: -110~-48 Unit: dBm Actual Value Range: -110~-48 Default Value: -98
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
205
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCdm a1xRttG roup
InterRat HoCdm aB1Hyst
ADD INTER RATHO CDMA1 XRTTG ROUP
LOFD-0 01090 / TDLOF D-00109 0
Enhance d CS Fallback to CDMA2 000 1xRTT
Meaning: Indicates the hysteresis for event B1 for inter-RAT handover to CDMA2000 1xRTT. This parameter is used to prevent frequent triggering of event evaluation caused by radio signal fluctuation. In this way, the probability of ping-pong handovers or handover decision errors is reduced. A larger value of this parameter results in a lower probability of pingpong handovers or handover decision errors.
MOD INTER RATHO CDMA1 XRTTG ROUP
GUI Value Range: 0~30 Unit: 0.5dB Actual Value Range: 0~15 Default Value: 2
LST INTER RATHO CDMA1 XRTTG ROUP InterRat HoCdm a1xRttG roup
InterRat HoCdm aB1Thd Ps
ADD INTER RATHO CDMA1 XRTTG ROUP MOD INTER RATHO CDMA1 XRTTG ROUP
None
None
Meaning: Indicates the pilot strength threshold for event B1 related to coverage-based inter-RAT handover to CDMA2000 1xRTT. When the measurement value exceeds this threshold, a measurement report will be sent. GUI Value Range: -63~0 Unit: 0.5dB Actual Value Range: -31.5~0 Default Value: -28
LST INTER RATHO CDMA1 XRTTG ROUP
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
206
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCdm a1xRttG roup
InterRat HoCdm aB1Tim eToTrig
ADD INTER RATHO CDMA1 XRTTG ROUP
LOFD-0 01090 / TDLOF D-00109 0
Enhance d CS Fallback to CDMA2 000 1xRTT
Meaning:
MOD INTER RATHO CDMA1 XRTTG ROUP
Indicates the time-to-trigger for event B1 related to inter-RAT handover to CDMA2000 1xRTT. When detecting that the signal quality in at least one neighboring cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers and the number of wrong handovers, preventing unnecessary handovers.
LST INTER RATHO CDMA1 XRTTG ROUP
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: None Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 640ms
InterRat HoCdm a1xRttG roup
LdSvBa sedHoC dmaB1T hdPs
ADD INTER RATHO CDMA1 XRTTG ROUP MOD INTER RATHO CDMA1 XRTTG ROUP
LOFD-0 01021 / TDLOF D-00102 1
PS InterRAT Mobility between EUTRAN and CDMA2 000
Meaning: Indicates the pilot strength threshold for event B1 related to load- or service-based inter-RAT handover to CDMA2000 1xRTT. When the measurement value exceeds this threshold, a measurement report will be sent. GUI Value Range: -63~0 Unit: 0.5dB Actual Value Range: -31.5~0 Default Value: -24
LST INTER RATHO CDMA1 XRTTG ROUP
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
207
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCdm aHrpdGr oup
InterRat HoCdm aB1Hyst
ADD INTER RATHO CDMA HRPDG ROUP
LOFD-0 01021 / TDLOF D-00102 1
PS InterRAT Mobility between EUTRAN and CDMA2 000
Meaning: Indicates the hysteresis for event B1 related to inter-RAT handover to CDMA2000 HRPD. This parameter is used to prevent frequent triggering of event evaluation caused by radio signal fluctuation. In this way, the probability of ping-pong handovers or handover decision errors is reduced. A larger value of this parameter results in a lower probability of pingpong handovers or handover decision errors.
MOD INTER RATHO CDMA HRPDG ROUP
Unit: 0.5dB Actual Value Range: 0~15 Default Value: 2
LST INTER RATHO CDMA HRPDG ROUP InterRat HoCdm aHrpdGr oup
InterRat HoCdm aB1Thd Ps
ADD INTER RATHO CDMA HRPDG ROUP MOD INTER RATHO CDMA HRPDG ROUP
GUI Value Range: 0~30
LOFD-0 01021 / TDLOF D-00102 1
PS InterRAT Mobility between EUTRAN and CDMA2 000
Meaning: Indicates the pilot strength threshold for event B1 related to load- or service-based inter-RAT handover to CDMA2000 HRPD. When the measurement value exceeds this threshold, a measurement report will be sent. GUI Value Range: -63~0 Unit: 0.5dB Actual Value Range: -31.5~0 Default Value: -14
LST INTER RATHO CDMA HRPDG ROUP
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
208
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCdm aHrpdGr oup
InterRat HoCdm aB1Tim eToTrig
ADD INTER RATHO CDMA HRPDG ROUP
LOFD-0 01021 / TDLOF D-00102 1
PS InterRAT Mobility between EUTRAN and CDMA2 000
Meaning:
MOD INTER RATHO CDMA HRPDG ROUP
Indicates the time-to-trigger for event B1 related to inter-RAT handover to CDMA2000 HRPD. When detecting that the signal quality in at least one neighboring cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers and the number of wrong handovers, preventing unnecessary handovers.
LST INTER RATHO CDMA HRPDG ROUP
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Unit: ms Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms Default Value: 640ms
InterRat HoCdm aHrpdGr oup
LdSvBa sedHoC dmaB1T hdPs
ADD INTER RATHO CDMA HRPDG ROUP MOD INTER RATHO CDMA HRPDG ROUP
LOFD-0 01035 / TDLOF D-00103 5
CS Fallback to CDMA2 000 1xRTT
Meaning: Indicates the pilot strength threshold for event B1 related to load- or service-based inter-RAT handover to CDMA2000 HRPD. When the measurement value exceeds this threshold, a measurement report will be sent. GUI Value Range: -63~0 Unit: 0.5dB Actual Value Range: -31.5~0 Default Value: -10
LST INTER RATHO CDMA HRPDG ROUP
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
209
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
InterRat HoCdm aHrpdGr oup
Cdma20 00Hrpd B2Thd1 Rsrp
ADD INTER RATHO CDMA HRPDG ROUP
LOFD-0 01021 / TDLOF D-00102 1
PS InterRAT Mobility between EUTRAN and CDMA2 000
Meaning: Indicates the B2 RSRP threshold 1 used during optimized handovers from E-UTRAN to CDMA2000 eHRPD.
PS InterRAT Mobility between EUTRAN and CDMA2 000
Meaning: Indicates the B2 RSRQ threshold 1 used during optimized handovers from E-UTRAN to CDMA2000 eHRPD.
MOD INTER RATHO CDMA HRPDG ROUP
GUI Value Range: -140~-43 Unit: dBm Actual Value Range: -140~-43 Default Value: -113
LST INTER RATHO CDMA HRPDG ROUP InterRat HoCdm aHrpdGr oup
Cdma20 00Hrpd B2Thd1 Rsrq
ADD INTER RATHO CDMA HRPDG ROUP MOD INTER RATHO CDMA HRPDG ROUP
LOFD-0 01021 / TDLOF D-00102 1
GUI Value Range: -40~-6 Unit: 0.5dB Actual Value Range: -20~-3 Default Value: -14
LST INTER RATHO CDMA HRPDG ROUP
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
210
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
ENodeB AlgoSwi tch
CaAlgo Switch
MOD ENODE BALGO SWITC H
LAOFD -001001 01
IntraBand Carrier Aggrega tion for Downlin k 2CC in 20MHz
Meaning:
LST ENODE BALGO SWITC H
LAOFD -001001 02 LAOFD -001002 01 / TDLAO FD-001 002 LAOFD -001002 02 / TDLAO FD-001 00102 LAOFD -070201 / TDLAO FD-070 201 LAOFD -070202 TDLAO FD-001 00111 LAOFD -080202 LAOFD -080201
Issue 03 (2015-06-30)
InterBand Carrier Aggrega tion for Downlin k 2CC in 20MHz Carrier Aggrega tion for Downlin k 2CC in 40MHz Support of UE Categor y6 Flexible CA from Multiple Carriers
LBFD-0 0201805 / TDLBF D-00201 805
IntereNodeB CA based on Coordin ated BBU
LOFD-0 0105401 / TDLOF D-00105 401
Intraband Carrier Aggrega tion for Downlin
Indicates whether to enable carrier aggregation (CA). The switches are described as follows: PdcchOverlapSrchSpcSwitch: Indicates whether CA UEs regard the overlapping PDCCH candidates of the common search space and UE-specific search space, which are transmitted by the primary serving cell (PCell), as PDCCH candidates of the common or UEspecific search space. If this switch is On and if a CA UE supports cross-carrier scheduling and is assigned a carrier indicator field (CIF), the CA UE determines that the overlapping PDCCH candidates belong to the common search space; otherwise, the CA UE determines that the overlapping PDCCH candidates belong to the UE-specific search space. If this switch is Off, the CA UE always determines that the overlapping PDCCH candidates belong to the common search space. CaCapbFiltSwitch: Indicates how the eNodeB performs CA after a CA UE reports the combination of frequency bands. If the UECapabilityInformation message reported by a UE does not contain the IE supportedBandwidthCombinationSet, the eNodeB performs CA as follows: If this option is Off, the eNodeB configures a secondary component carrier (SCC) for the UE using the default value of the IE supportedBandwidthCombinationSet defined in 3GPP specifications. If this option is On, the eNodeB does not configure an SCC for the UE. PccAnchorSwitch: Indicates whether to enable the anchor function of the primary component carrier (PCC). This switch is not subject to the setting of FreqCfgSwitch of the CaAlgoSwitch parameter. The anchor function of the PCC is enabled only when this switch is On. SccBlindCfgSwitch: Indicates whether a secondary serving cell (SCell) can be blindly configured. If this switch is On, the eNodeB configures a candidate SCell as an SCell for a CA UE without A4 measurements. If this switch is Off, the eNodeB delivers A4 measurement configurations for measuring the frequency of a candidate SCell before configuring the candidate SCell as an SCell for the CA UE. FreqCfgSwitch: Indicates whether to configure CA based on frequencies or CA groups. If this switch is
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
211
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
k 2CC in 30MHz
On, CA can be configured based on frequencies. If this switch is Off, CA can be configured based on CA groups.
Carrier Aggrega tion for Uplink 2CC
SccA2RmvSwitch: Indicates whether to deliver A2 measurement configurations for measuring a secondary component carrier (SCC) after the SCC is configured. This option is not subject to the setting of the FreqCfgSwitch option of the CaAlgoSwitch parameter. If FreqCfgSwitch is Off and SccBlindCfgSwitch is On, the setting of SccA2RmvSwitch does not take effect. The eNodeB delivers A2 measurement configurations for measuring an SCC after the SCC is configured only when SccA2RmvSwitch is On.
IntereNodeB CA based on relaxed backhau l Service Based Interfrequenc y Handov er Camp & Handov er Based on SPID
CaTrafficTriggerSwitch: Indicates whether to add and remove an SCC based on the traffic volume of a CA UE after the UE accesses the network. This switch is not subject to the settings of FreqCfgSwitch. If the CarrierMgtSwitch parameter is set to Off and CaTrafficTriggerSwitch is On, an added SCC cannot be removed based on the traffic volume of a CA UE. HoWithSccCfgSwitch: Indicates whether an SCC can be configured for a CA UE during a handover. It is recommended that the SccA2RmvSwitch option of the CaAlgoSwitch parameter be selected when the HoWithSccCfgSwitch option of the same parameter is selected. If the SccA2RmvSwitch option is deselected, UEs cannot report the signals of neighboring cells that operate on the frequencies of their SCell, affecting SCell configuration in handovers. This switch is not subject to the setting of FreqCfgSwitch of the CaAlgoSwitch parameter. If this switch is On, the source cell sends SCC information to the target cell during the handover and the SCC is configured for the CA UE. If this switch is Off, the source cell does not send SCC information to the target cell during the handover. SccModA6Switch: Indicates whether the eNodeB delivers event A6 measurement configurations to a CA UE after configuring an SCC for the UE. The eNodeB delivers event A6 measurement configurations to a CA UE after configuring an SCC for the UE only when the switch is On. GbrAmbrJudgeSwitch: Indicates whether to check the GBR or AMBR when an SCell is to be activated for downlink CA. If this switch is On, the bit rate of the
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
212
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
bearer or aggregate bit rate of the CA UE is checked when an SCell is to be activated. An SCell can be activated if the bit rate has not reached the GBR or the aggregate bit rate of the UE has not reached the AMBR. If this switch is Off, neither the bit rate of the bearer nor the aggregate bit rate of the CA UE is checked when an SCell is to be activated. MtaAlgSwitch: Indicates whether multiple timing advances (MTAs) are supported in uplink CA scenarios. This parameter applies only to LTE FDD. If this switch is On, MTAs are supported. If the reported UE capabilities indicate that the UE supports MTAs in the uplink, uplink timing is performed on the UE based on multiple timing advance groups (TAGs) in uplink CA scenarios. If the UE does not support MTAs in the uplink, uplink timing is performed on the UE based on a single TAG in uplink CA scenarios. If this switch is Off, MTAs are not supported in uplink CA scenarios, and uplink timing is performed on UEs based on a single TAG. You are advised to set this switch to On in inter-eNodeB CA scenarios and scenarios where RRUs are installed remotely. RelaxedBackhaulCaSwitch: Indicates whether to enable inter-eNodeB downlink CA based on relaxed backhaul. Inter-eNodeB CA based on relaxed backhaul is enabled only when this switch is On. AdpCaSwitch: Indicates whether to allow adaptive frequency-based CA configuration. If this switch is On, in frequency-based configuration mode, the eNodeB can configure SCells in a blind manner based on preconfigured CA group information. If this switch is Off, blind SCell configuration is not allowed in frequency-based CA configuration mode. CaHoControlSwitch: Indicates whether CA UEs can be handed over to non-macro cells during unnecessary intra-RAT handovers. If this switch is On, CA UEs cannot be handed over to non-macro cells during unnecessary intra-RAT handovers. If this switch is Off, CA UEs can be handed over to non-macro cells during unnecessary intra-RAT handovers. DistributeCloudbbCaSwitch: Indicates whether to enable CA based on distributed Cloud BB. CA based on distributed Cloud BB applies to cells served by the eNodeB only when this switch is On. SccSmartCfgSwitch: Indicates whether to enable smart SCC selection. The eNodeB considers the load Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
213
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
status indicators of candidate SCells when configuring the SCell only when this switch is On. IdleModePccAnchorSwitch: Indicates whether to enable the anchor function of the primary component carrier (PCC) for UEs in idle mode. If this option is selected, this function is enabled. If this option is deselected, this function is disabled. FreqPriBasedHoCaFiltSwitch: Indicates whether the eNodeB filters out CA UEs when delivering measurement configuration for frequency-prioritybased handovers. CA UEs are filtered out only if this option is selected. CaSccSuspendSwitch: Indicates whether the eNodeB stops scheduling carrier aggregation (CA) UEs in their secondary serving cells (SCells) when the channel quality for the CA UEs is poor. If this option is selected, the eNodeB stops scheduling CA UEs when the channel quality for the CA UEs is worse than that indicated by the SccDeactCqiThd parameter value in single-codeword transmission. The eNodeB resumes scheduling CA UEs in their SCells when the channel quality for the CA UEs is better than that indicated by the SccDeactCqiThd parameter value plus 2 in singlecodeword transmission. GUI Value Range: PdcchOverlapSrchSpcSwitch(PdcchOverlapSrchSpcSwitch), CaCapbFiltSwitch(CaCapbFiltSwitch), PccAnchorSwitch(PccAnchorSwitch), SccBlindCfgSwitch(SccBlindCfgSwitch), FreqCfgSwitch(FreqCfgSwitch), SccA2RmvSwitch(SccA2RmvSwitch), CaTrafficTriggerSwitch(CaTrafficTriggerSwitch), HoWithSccCfgSwitch(HoWithSccCfgSwitch), SccModA6Switch(SccModA6Switch), GbrAmbrJudgeSwitch(GbrAmbrJudgeSwitch), MtaAlgSwitch(MtaAlgSwitch), RelaxedBackhaulCaSwitch(RelaxedBackhaulCaSwitch), AdpCaSwitch(AdpCaSwitch), CaHoControlSwitch(CaHoControlSwitch), DistributeCloudbbCaSwitch(DistributeCloudbbCaSwitch), SccSmartCfgSwitch(SccSmartCfgSwitch), IdleModePccAnchorSwitch(IdleModePccAnchorSwitch), FreqPriBasedHoCaFiltSwitch(FreqPriBasedHoCaFiltSwitch), CaSccSuspendSwitch(CaSccSuspendSwitch) Unit: None Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
214
eRAN VoLTE Feature Parameter Description
MO
Parame ter ID
MML Comma nd
Feature ID
10 Parameters
Feature Name
Description
Actual Value Range: PdcchOverlapSrchSpcSwitch, CaCapbFiltSwitch, PccAnchorSwitch, SccBlindCfgSwitch, FreqCfgSwitch, SccA2RmvSwitch, CaTrafficTriggerSwitch, HoWithSccCfgSwitch, SccModA6Switch, GbrAmbrJudgeSwitch, MtaAlgSwitch, RelaxedBackhaulCaSwitch, AdpCaSwitch, CaHoControlSwitch, DistributeCloudbbCaSwitch, SccSmartCfgSwitch, IdleModePccAnchorSwitch, FreqPriBasedHoCaFiltSwitch, CaSccSuspendSwitch Default Value: PdcchOverlapSrchSpcSwitch:On, CaCapbFiltSwitch:Off, PccAnchorSwitch:Off, SccBlindCfgSwitch:Off, FreqCfgSwitch:Off, SccA2RmvSwitch:On, CaTrafficTriggerSwitch:Off, HoWithSccCfgSwitch:Off, SccModA6Switch:Off, GbrAmbrJudgeSwitch:On, MtaAlgSwitch:Off, RelaxedBackhaulCaSwitch:Off, AdpCaSwitch:Off, CaHoControlSwitch:Off, DistributeCloudbbCaSwitch:Off, SccSmartCfgSwitch:Off, IdleModePccAnchorSwitch:Off, FreqPriBasedHoCaFiltSwitch:Off, CaSccSuspendSwitch:Off RrcCon nStateTi mer
UeInacti veTimer
MOD RRCCO NNSTA TETIM ER
LBFD-0 02007 / TDLBF D-00200 7
RRC Connect ion Manage ment
LST RRCCO NNSTA TETIM ER
Meaning: Indicates the length of the UE inactivity timer for UEs that are running non-QCI1 services. If the eNodeB detects that a UE has neither received nor sent data for a duration exceeding the value of this parameter, the eNodeB releases the RRC connection for the UE. If this parameter is set to 0, the UE inactivity timer is not used. If the parameter setting is changed, the change applies to UEs that newly access the network. GUI Value Range: 0~3600 Unit: s Actual Value Range: 0~3600 Default Value: 20
ENodeB AlgoSwi tch
VQMAl goSwitc h
MOD ENODE BALGO SWITC H LST ENODE BALGO SWITC H
Issue 03 (2015-06-30)
None
None
Meaning: Indicates the switch used to enable or disable the voice quality monitoring algorithm. GUI Value Range: VQM_ALGO_SWITCH_OFF(Disable), VQM_ALGO_SWITCH_ON(Enable) Unit: None Actual Value Range: VQM_ALGO_SWITCH_OFF, VQM_ALGO_SWITCH_ON Default Value: VQM_ALGO_SWITCH_OFF(Disable)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
215
eRAN VoLTE Feature Parameter Description
10 Parameters
MO
Parame ter ID
MML Comma nd
Feature ID
Feature Name
Description
VQMAl go
ULDela yJitter
MOD VQMA LGO
None
None
Meaning: Indicates the maximum UL voice packet delay variation allowed on the Uu interface. If the actual delay variation of a UL voice packet exceeds this limit, this packet is regarded as lost during the evaluation of voice quality indicator (VQI). The delay variation is measured at the eNodeB PDCP layer.
LST VQMA LGO
GUI Value Range: 1~255 Unit: ms Actual Value Range: 1~255 Default Value: 100 RlcPdcp ParaGro up
Discard Timer
ADD RLCPD CPPAR AGROU P MOD RLCPD CPPAR AGROU P LST RLCPD CPPAR AGROU P
Issue 03 (2015-06-30)
LBFD-0 02008 / TDLBF D-00200 8
Radio Bearer Manage ment
Meaning: Indicates the length of the PDCP discard timer. 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)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
216
eRAN VoLTE Feature Parameter Description
11 Counters
11
Counters
Table 11-1 Counters Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526726668
L.ERAB.AttEst.QCI.1
Number of E-RAB setup attempts initiated by UEs for services with the QCI of 1 in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management
TDLBFD-002008 1526726669
L.ERAB.SuccEst.QCI. 1
Number of successful E-RAB setups initiated by UEs for services with the QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management
TDLBFD-002008 1526726676
L.ERAB.AttEst.QCI.5
Number of E-RAB setup attempts initiated by UEs for services with the QCI of 5 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management
TDLBFD-002008 1526726677
L.ERAB.SuccEst.QCI. 5
Number of successful E-RAB setups initiated by UEs for services with the QCI of 5 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management
TDLBFD-002008
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
217
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526726686
L.ERAB.AbnormRel.Q CI.1
Number of abnormal releases of activated ERABs for services with the QCI of 1 in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management
TDLBFD-002008 1526726687
L.ERAB.NormRel.QCI .1
Number of normal E-RAB releases for services with the QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management
TDLBFD-002008 1526726694
L.ERAB.AbnormRel.Q CI.5
Number of abnormal releases of activated ERABs for services with the QCI of 5 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management
TDLBFD-002008 1526726695
L.ERAB.NormRel.QCI .5
Number of normal E-RAB releases for services with the QCI of 5 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management
TDLBFD-002008 1526726776
L.Thrp.bits.UL.QCI .1
Uplink traffic volume for PDCP PDUs of services with the QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
218
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526726777
L.Thrp.Time.UL.Q CI.1
Receive duration of uplink PDCP PDUs for services with the QCI of 1 in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025 1526726803
L.Thrp.bits.DL.QCI .1
Downlink traffic volume for PDCP SDUs of services with the QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025 1526726804
L.Thrp.Time.DL.Q CI.1
Transmit duration of downlink PDCP SDUs for services with the QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025 1526726833
L.PDCP.Tx.Disc.Tr f.SDU.QCI.1
Number of downlink PDCP SDUs discarded for services carried on DRBs with a QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
219
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526727412
L.ChMeas.PUSCH. MCS.0
Number of times MCS index 0 is scheduled on the PUSCH
Multi-mode: None
Basic Scheduling
GSM: None
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
UMTS: None LTE: LBFD-002025 LBFD-001005 TDLBFD-002025 TDLBFD-001005
1526727443
L.ChMeas.PUSCH. MCS.31
Number of times MCS index 31 is scheduled on the PUSCH
Basic Scheduling
GSM: None
Basic Scheduling
UMTS: None
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
TDLBFD-002025 LBFD-001005 TDLBFD-001005 LOFD-001006 TDLOFD-001006 L.Thrp.bits.UL.PL MN.QCI.1
Total traffic volume of uplink PDCP PDUs of QCI-1 services
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
Multi-mode: None
LTE: LBFD-002025
1526727849
Basic Scheduling
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 LOFD-001036 LOFD-001037 LBFD-002025 TDLBFD-002008 TDLOFD-001036 TDLOFD-001037
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM UL 64QAM UL 64QAM Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Basic Scheduling Radio Bearer Management RAN Sharing with Common Carrier
TDLBFD-002025
RAN Sharing with Dedicated Carrier
LOFD-070206
Basic Scheduling Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
220
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526727850
L.Thrp.Time.UL.PL MN.QCI.1
Duration for receiving uplink PDCP SDUs of QCI-1 services
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008 LOFD-001036 LOFD-001037 LBFD-002025 TDLBFD-002008 TDLOFD-001036 TDLOFD-001037
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Basic Scheduling Radio Bearer Management RAN Sharing with Common Carrier
TDLBFD-002025
RAN Sharing with Dedicated Carrier
LOFD-070206
Basic Scheduling Hybrid RAN Sharing
1526727853
L.ERAB.AttEst.PLMN. QCI.1
Number of E-RAB setup attempts initiated by UEs for services with the QCI of 1for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
221
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526727854
L.ERAB.SuccEst.PLM N.QCI.1
Number of successful E-RAB setups initiated by UEs for services with the QCI of 1 for a specific operator in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526727861
L.ERAB.AttEst.PLMN. QCI.5
Number of E-RAB setup attempts initiated by UEs for services with the QCI of 5 for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526727862
L.ERAB.SuccEst.PLM N.QCI.5
Number of successful E-RAB setups initiated by UEs for services with the QCI of 5 for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
222
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526727871
L.ERAB.AbnormRel.P LMN.QCI.1
Number of abnormal releases of activated ERABs for services with the QCI of 1 for a specific operator in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526727872
L.ERAB.NormRel.PL MN.QCI.1
Number of normal E-RAB releases for services with the QCI of 1 for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526727879
L.ERAB.AbnormRel.P LMN.QCI.5
Number of abnormal releases of activated ERABs for services with the QCI of 5 for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
223
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526727880
L.ERAB.NormRel.PL MN.QCI.5
Number of normal E-RAB releases for services with the QCI of 5 for a specific operator in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LOFD-001036 LOFD-001037 TDLOFD-001036 TDLOFD-001037 LOFD-070206
Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526727889
L.PDCP.Tx.TotRev. Trf.SDU.QCI.1
Number of downlink PDCP SDUs transmitted for services carried on DRBs with a QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025 1526727934
L.Traffic.DL.PktUu Loss.Loss.QCI.1
Number of downlink PDCP SDUs discarded for services carried on DRBs with a QCI of 1 in a cell over the Uu interface
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025 1526727935
L.Traffic.DL.PktUu Loss.Tot.QCI.1
Number of downlink PDCP SDUs transmitted for services carried on DRBs with a QCI of 1 in a cell over the Uu interface
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
224
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526727961
L.Traffic.UL.PktLo ss.Loss.QCI.1
Number of uplink PDCP SDUs discarded for services carried on DRBs with a QCI of 1 in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025 1526727962
L.Traffic.UL.PktLo ss.Tot.QCI.1
Number of expected uplink PDCP SDUs for services carried on DRBs with a QCI of 1 in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling
LBFD-002025 TDLBFD-002025 1526728050
L.Thrp.bits.DL.PL MN.QCI.1
Total traffic volume of downlink PDCP PDUs of QCI-1 services
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 LOFD-001036 LOFD-001037 LBFD-002025 TDLBFD-002008 TDLOFD-001036 TDLOFD-001037
Radio Bearer Management RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Basic Scheduling Radio Bearer Management RAN Sharing with Common Carrier
TDLBFD-002025
RAN Sharing with Dedicated Carrier
LOFD-070206
Basic Scheduling Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
225
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526728051
L.Thrp.Time.DL.PL MN.QCI.1
Duration for transmitting downlink PDCP SDUs of QCI-1 services
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008 LOFD-001036 LOFD-001037 LBFD-002025 TDLBFD-002008 TDLOFD-001036 TDLOFD-001037
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier Basic Scheduling Radio Bearer Management RAN Sharing with Common Carrier
TDLBFD-002025
RAN Sharing with Dedicated Carrier
LOFD-070206
Basic Scheduling Hybrid RAN Sharing
1526728304
L.ChMeas.CCE.UL Used
Number of PDCCH CCEs used for uplink DCI in a measurement period
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002003
Physical Channel Management Physical Channel Management
TDLBFD-002003 1526728305
L.ChMeas.CCE.DL Used
Number of PDCCH CCEs used for downlink DCI in a measurement period
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002003
Physical Channel Management Physical Channel Management
TDLBFD-002003 1526728411
L.Voice.VQI.UL.Ex cellent.Times
Number of times uplink voice quality is Excellent
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526728412
L.Voice.VQI.UL.G ood.Times
Number of times uplink voice quality is Good
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
226
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526728413
L.Voice.VQI.UL.Ac cept.Times
Number of times uplink voice quality is Accept
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008
1526728414
L.Voice.VQI.UL.Po or.Times
Number of times uplink voice quality is Poor
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526728415
L.Voice.VQI.UL.Ba d.Times
Number of times uplink voice quality is Bad
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526728416
L.Voice.VQI.DL.Ex cellent.Times
Number of times downlink voice quality is Excellent
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526728417
L.Voice.VQI.DL.G ood.Times
Number of times downlink voice quality is Good
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526728418
L.Voice.VQI.DL.Ac cept.Times
Number of times downlink voice quality is Accept
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526728419
L.Voice.VQI.DL.Po or.Times
Number of times downlink voice quality is Poor
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
227
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526728420
L.Voice.VQI.DL.Ba d.Times
Number of times downlink voice quality is Bad
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008
1526728446
L.Traffic.ActiveUse r.UL.QCI.1
Number of activated UEs with the QCI of 1 in the uplink buffer
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002007
RRC Connection Management RRC Connection Management
TDLBFD-002007 1526728456
L.Traffic.ActiveUse r.DL.QCI.1
Number of activated UEs with the QCI of 1 in the downlink buffer
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002007
RRC Connection Management RRC Connection Management
TDLBFD-002007 1526728494
L.Sps.UL.SchNum
Number of uplink semi-persistent scheduling times in a cell
Multi-mode: None GSM: None UMTS: None LTE: LOFD-001016
VoIP Semipersistent Scheduling VoIP Semipersistent Scheduling
TDLOFD-001016 1526728495
L.Sps.DL.SchNum
Number of downlink semipersistent scheduling times in a cell
Multi-mode: None GSM: None UMTS: None LTE: LOFD-001016
VoIP Semipersistent Scheduling VoIP Semipersistent Scheduling
TDLOFD-001016 1526728496
L.Traffic.User.TtiB undling.Avg
Average number of UEs on which TTI bundling takes effect in a cell
Multi-mode: None
TTI Bundling
GSM: None
TTI Bundling
UMTS: None LTE: LOFD-001048 TDLOFD-001048
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
228
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526728562
L.Sps.UL.ErrNum
Number of failed uplink semipersistent scheduling transmissions in a cell
Multi-mode: None
VoIP Semipersistent Scheduling
GSM: None UMTS: None LTE: LOFD-001016
VoIP Semipersistent Scheduling
TDLOFD-001016 1526728563
L.Sps.DL.ErrNum
Number of failed downlink semipersistent scheduling transmission in a cell
Multi-mode: None GSM: None UMTS: None LTE: LOFD-001016
VoIP Semipersistent Scheduling VoIP Semipersistent Scheduling
TDLOFD-001016 1526728911
L.Signal.Num.TtiB undling.Enter
Number of messages sent for instructing UEs to enter TTI bundling mode
Multi-mode: None
TTI Bundling
GSM: None
TTI Bundling
UMTS: None LTE: LOFD-001048 TDLOFD-001048
1526728912
L.Signal.Num.TtiB undling.Exit
Number of messages sent for instructing UEs to exit TTI bundling mode
Multi-mode: None
TTI Bundling
GSM: None
TTI Bundling
UMTS: None LTE: LOFD-001048 TDLOFD-001048
1526729526
1526729527
Issue 03 (2015-06-30)
L.HHO.IntraeNB.In traFreq.PrepAttOut. VoIP
L.HHO.IntraeNB.In terFreq.PrepAttOut. VoIP
Number of intraeNodeB intrafrequency outgoing handover attempts for UEs performing voice services in a cell
Multi-mode: None
Number of intraeNodeB interfrequency outgoing handover attempts for UEs performing voice services in a cell
Multi-mode: None
GSM: None UMTS: None LTE: LBFD-00201801
Coverage Based Intra-frequency Handover Coverage Based Intra-frequency Handover
TDLBFD-0020180 1
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
229
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526729528
L.HHO.IntraeNB.In terFddTdd.PrepAtt Out.VoIP
Number of intraeNodeB interduplex-mode outgoing handover attempts for UEs performing voice services in a cell
Multi-mode: None
Coverage Based Inter-frequency Handover
Number of intraeNodeB intrafrequency outgoing handover executions for UEs performing voice services in a cell
Multi-mode: None
Number of intraeNodeB interfrequency outgoing handover executions for UEs performing voice services in a cell
Multi-mode: None
Number of intraeNodeB interduplex-mode outgoing handover executions for UEs performing voice services in a cell
Multi-mode: None
Number of successful intraeNodeB intrafrequency outgoing handovers for UEs performing voice services in a cell
Multi-mode: None
1526729529
1526729530
1526729531
1526729532
Issue 03 (2015-06-30)
L.HHO.IntraeNB.In traFreq.ExecAttOut .VoIP
L.HHO.IntraeNB.In terFreq.ExecAttOut .VoIP
L.HHO.IntraeNB.In terFddTdd.ExecAtt Out.VoIP
L.HHO.IntraeNB.In traFreq.ExecSuccO ut.VoIP
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201801
Coverage Based Intra-frequency Handover Coverage Based Intra-frequency Handover
TDLBFD-0020180 1
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201801
Coverage Based Intra-frequency Handover Coverage Based Intra-frequency Handover
TDLBFD-0020180 1
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
230
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526729533
L.HHO.IntraeNB.In terFreq.ExecSuccO ut.VoIP
Number of successful intraeNodeB interfrequency outgoing handovers for UEs performing voice services in a cell
Multi-mode: None
Coverage Based Inter-frequency Handover
Number of successful intraeNodeB interduplex-mode outgoing handovers for UEs performing voice services in a cell
Multi-mode: None
Number of intereNodeB intrafrequency outgoing handover attempts for UEs performing voice services in a cell
Multi-mode: None
Number of intereNodeB interfrequency outgoing handover attempts for UEs performing voice services in a cell
Multi-mode: None
Number of intereNodeB interduplex-mode outgoing handover attempts for UEs performing voice services in a cell
Multi-mode: None
1526729534
1526729535
1526729536
1526729537
Issue 03 (2015-06-30)
L.HHO.IntraeNB.In terFddTdd.ExecSuc cOut.VoIP
L.HHO.IntereNB.In traFreq.PrepAttOut. VoIP
L.HHO.IntereNB.In terFreq.PrepAttOut. VoIP
L.HHO.IntereNB.In terFddTdd.PrepAtt Out.VoIP
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201801
Coverage Based Intra-frequency Handover Coverage Based Intra-frequency Handover
TDLBFD-0020180 1
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
231
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526729538
L.HHO.IntereNB.In traFreq.ExecAttOut .VoIP
Number of intereNodeB intrafrequency outgoing handover executions for UEs performing voice services in a cell
Multi-mode: None
Coverage Based Intra-frequency Handover
Number of intereNodeB interfrequency outgoing handover executions for UEs performing voice services in a cell
Multi-mode: None
Number of intereNodeB interduplex-mode outgoing handover executions for UEs performing voice services in a cell
Multi-mode: None
Number of successful intereNodeB intrafrequency outgoing handovers for UEs performing voice services in a cell
Multi-mode: None
Number of successful intereNodeB interfrequency outgoing handovers for UEs performing voice services in a cell
Multi-mode: None
1526729539
1526729540
1526729541
1526729542
Issue 03 (2015-06-30)
L.HHO.IntereNB.In terFreq.ExecAttOut .VoIP
L.HHO.IntereNB.In terFddTdd.ExecAtt Out.VoIP
L.HHO.IntereNB.In traFreq.ExecSuccO ut.VoIP
L.HHO.IntereNB.In terFreq.ExecSuccO ut.VoIP
GSM: None UMTS: None LTE: LBFD-00201801
Coverage Based Intra-frequency Handover
TDLBFD-0020180 1
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-00201801
Coverage Based Intra-frequency Handover Coverage Based Intra-frequency Handover
TDLBFD-0020180 1
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
232
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526729543
L.HHO.IntereNB.In terFddTdd.ExecSuc cOut.VoIP
Number of successful intereNodeB interduplex-mode outgoing handovers for UEs performing voice services in a cell
Multi-mode: None
Coverage Based Inter-frequency Handover
Maximum number of activated UEs with the QCI of 1 in the downlink buffer
Multi-mode: None
1526730601
L.Traffic.ActiveUse r.DL.QCI.1.Max
GSM: None UMTS: None LTE: LBFD-00201802
Coverage Based Inter-frequency Handover
TDLBFD-0020180 2
GSM: None UMTS: None LTE: LBFD-002007
RRC Connection Management RRC Connection Management
TDLBFD-002007 1526730611
L.Traffic.ActiveUse r.UL.QCI.1.Max
Maximum number of activated UEs with the QCI of 1 in the uplink buffer
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002007
RRC Connection Management RRC Connection Management
TDLBFD-002007 1526730883
L.ChMeas.PRB.DL .DrbUsed.Avg.VoIP
Average number of PRBs used by DRBs on the PDSCH for downlink VoIP services
Multi-mode: None
Basic Scheduling
GSM: None
Basic Scheduling
UMTS: None
Adaptive SFN/ SDMA
LTE: LBFD-002025 TDLBFD-002025 LOFD-070205
1526730884
L.ChMeas.PRB.UL .DrbUsed.Avg.VoIP
Average number of PRBs used by DRBs on the PUSCH for uplink VoIP services
Multi-mode: None
Basic Scheduling
GSM: None
Basic Scheduling
UMTS: None
Adaptive SFN/ SDMA
LTE: LBFD-002025 TDLBFD-002025 LOFD-070205
1526732687
Issue 03 (2015-06-30)
L.Voice.VQI.AMR WB.UL.Excellent.T imes
Number of times uplink voice quality of AMR-WB services is Excellent
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
233
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526732688
L.Voice.VQI.AMR WB.UL.Good.Time s
Number of times uplink voice quality of AMR-WB services is Good
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008
1526732689
L.Voice.VQI.AMR WB.UL.Accept.Ti mes
Number of times uplink voice quality of AMR-WB services is Accept
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526732690
L.Voice.VQI.AMR WB.UL.Poor.Times
Number of times uplink voice quality of AMR-WB services is Poor
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526732691
L.Voice.VQI.AMR WB.UL.Bad.Times
Number of times uplink voice quality of AMR-WB services is Bad
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526732692
1526732693
1526732694
Issue 03 (2015-06-30)
L.Voice.VQI.AMR WB.DL.Excellent.T imes
L.Voice.VQI.AMR WB.DL.Good.Time s
L.Voice.VQI.AMR WB.DL.Accept.Ti mes
Number of times downlink voice quality of AMRWB services is Excellent
Multi-mode: None
Number of times downlink voice quality of AMRWB services is Good
Multi-mode: None
Number of times downlink voice quality of AMRWB services is Accept
Multi-mode: None
GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
234
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526732695
L.Voice.VQI.AMR WB.DL.Poor.Times
Number of times downlink voice quality of AMRWB services is Poor
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008
1526732696
L.Voice.VQI.AMR WB.DL.Bad.Times
Number of times downlink voice quality of AMRWB services is Bad
Multi-mode: None GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
1526732721
L.Traffic.User.VoIP. Avg
Average number of VoIP UEs in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002007
RRC Connection Management RRC Connection Management
TDLBFD-002007 1526732722
L.Traffic.User.VoIP. Max
Maximum number of VoIP UEs in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002007
RRC Connection Management RRC Connection Management
TDLBFD-002007 1526732890
1526732891
1526732892
Issue 03 (2015-06-30)
L.Voice.NormRel.U L.LowQuality
L.Voice.NormRel.D L.LowQuality
L.Voice.UL.Silent. Num
Number of normal voice call releases in the cell (poor uplink voice quality)
Multi-mode: None
Number of normal voice call releases in the cell (poor downlink voice quality)
Multi-mode: None
Number of times that a UE experiences uplink voice mute in the cell
Multi-mode: None
GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
GSM: None
Performance Management
UMTS: None LTE: LBFD-004008
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
235
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526732893
L.Voice.DL.Silent. Num
Number of times that a UE experiences downlink voice mute in the cell
Multi-mode: None
Performance Management
Number of times uplink voice quality is Excellent for a specific operator in a cell
Multi-mode: None
1526736660
L.Voice.VQI.UL.Ex cellent.Times.PLM N
GSM: None UMTS: None LTE: LBFD-004008
GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
1526736661
L.Voice.VQI.UL.G ood.Times.PLMN
Number of times uplink voice quality is Good for a specific operator in a 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.Ac cept.Times.PLMN
Number of times uplink voice quality is Accept for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
236
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736663
L.Voice.VQI.UL.Po or.Times.PLMN
Number of times uplink voice quality is Poor for a specific operator in a cell
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
1526736664
L.Voice.VQI.UL.Ba d.Times.PLMN
Number of times uplink voice quality is Bad for a specific operator 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.Ex cellent.Times.PLM N
Number of times downlink voice quality is Excellent for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
237
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736666
L.Voice.VQI.DL.G ood.Times.PLMN
Number of times downlink voice quality is Good for a specific operator in a cell
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
1526736667
L.Voice.VQI.DL.Ac cept.Times.PLMN
Number of times downlink voice quality is Accept for a specific operator 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.Po or.Times.PLMN
Number of times downlink voice quality is Poor for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
238
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736669
L.Voice.VQI.DL.Ba d.Times.PLMN
Number of times downlink voice quality is Bad for a specific operator in a cell
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
1526736670
L.Voice.VQI.AMR WB.UL.Excellent.T imes.PLMN
Number of times uplink voice quality of AMR-WB services is Excellent for a specific operator in a 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.AMR WB.UL.Good.Time s.PLMN
Number of times uplink voice quality of AMR-WB services is Good for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
239
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736672
L.Voice.VQI.AMR WB.UL.Accept.Ti mes.PLMN
Number of times uplink voice quality of AMR-WB services is Accept for a specific operator in a cell
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
1526736673
L.Voice.VQI.AMR WB.UL.Poor.Times .PLMN
Number of times uplink voice quality of AMR-WB services is Poor for a specific operator in 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.AMR WB.UL.Bad.Times. PLMN
Number of times uplink voice quality of AMR-WB services is Bad for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
240
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736675
L.Voice.VQI.AMR WB.DL.Excellent.T imes.PLMN
Number of times downlink voice quality of AMRWB services is Excellent for a specific operator in a cell
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
1526736676
L.Voice.VQI.AMR WB.DL.Good.Time s.PLMN
Number of times downlink voice quality of AMRWB services is Good for a specific operator 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.AMR WB.DL.Accept.Ti mes.PLMN
Number of times downlink voice quality of AMRWB services is Accept for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
241
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736678
L.Voice.VQI.AMR WB.DL.Poor.Times .PLMN
Number of times downlink voice quality of AMRWB services is Poor for a specific operator in a cell
Multi-mode: None
Performance Management
GSM: None UMTS: None LTE: LBFD-004008 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
1526736679
L.Voice.VQI.AMR WB.DL.Bad.Times. PLMN
Number of times downlink voice quality of AMRWB services is Bad for a specific operator 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.Tr f.SDU.PLMN.QCI. 1
Number of downlink traffic SDUs discarded by the PDCP layer for services with a QCI of 1 for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Performance Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing Radio Bearer Management Radio Bearer Management Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
RAN Sharing with Common Carrier
TDLBFD-002025 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
242
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736682
L.PDCP.Tx.TotRev. Trf.SDU.PLMN.Q CI.1
Number of transmitted downlink traffic PDCP SDUs for services with a QCI of 1 for a specific operator in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
RAN Sharing with Common Carrier
TDLBFD-002025 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526736684
L.Traffic.UL.PktLo ss.Loss.PLMN.QCI .1
Total number of discarded uplink PDCP SDUs for traffic services with a QCI of 1 for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
RAN Sharing with Common Carrier
TDLBFD-002025 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
243
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736686
L.Traffic.UL.PktLo ss.Tot.PLMN.QCI.1
Total number of expected uplink data packets for DRB services with a QCI of 1 for a specific operator in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
RAN Sharing with Common Carrier
TDLBFD-002025 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526736692
L.Traffic.User.VoIP. Avg.PLMN
Average number of VoIP UEs of a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002007 TDLBFD-002007 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RRC Connection Management RRC Connection Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
244
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736693
L.Traffic.User.VoIP. Max.PLMN
Maximum number of VoIP UEs of a specific operator in a cell
Multi-mode: None
RRC Connection Management
GSM: None UMTS: None LTE: LBFD-002007 TDLBFD-002007 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RRC Connection Management RAN Sharing with Common Carrier RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526736735
L.ChMeas.CCE.UL Used.VoIP
Number of PDCCH CCEs used for uplink VoIP services
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002003
Physical Channel Management Physical Channel Management
TDLBFD-002003 1526736736
L.ChMeas.CCE.DL Used.VoIP
Number of PDCCH CCEs used for downlink VoIP services
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002003
Physical Channel Management Physical Channel Management
TDLBFD-002003
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
245
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526736737
L.Traffic.DL.PktUu Loss.Loss.PLMN.Q CI.1
Total number of discarded downlink PDCP SDUs for traffic services with a QCI of 1 for a specific operator in a cell
Multi-mode: None
Radio Bearer Management
GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
RAN Sharing with Common Carrier
TDLBFD-002025 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
1526736739
L.Traffic.DL.PktUu Loss.Tot.PLMN.QC I.1
Total number of expected downlink data packets for DRB services with a QCI of 1 for a specific operator in a cell
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008
Radio Bearer Management Radio Bearer Management Basic Scheduling
TDLBFD-002008
Basic Scheduling
LBFD-002025
RAN Sharing with Common Carrier
TDLBFD-002025 LOFD-001036 TDLOFD-001036 LOFD-001037 TDLOFD-001037 LOFD-070206
RAN Sharing with Common Carrier RAN Sharing with Dedicated Carrier RAN Sharing with Dedicated Carrier Hybrid RAN Sharing
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
246
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526737724
L.Traffic.UL.SCH. QPSK.TB.QCI.1
Number of QCI-1 Service TBs initially transmitted on the uplink SCH in QPSK modulation mode
Multi-mode: None
Transport Channel Management
GSM: None UMTS: None LTE: LBFD-002002 LBFD-001005 TDLBFD-002002
1526737725
L.Traffic.UL.SCH. 16QAM.TB.QCI.1
Number of QCI-1 Service TBs initially transmitted on the uplink SCH in 16QAM modulation mode
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
Multi-mode: None
Transport Channel Management
GSM: None UMTS: None LTE: LBFD-002002 TDLBFD-002002
L.Traffic.UL.SCH. 64QAM.TB.QCI.1
Number of QCI-1 Service TBs initially transmitted on the uplink SCH in 64QAM modulation mode
Transport Channel Management
TDLBFD-001005
LBFD-001005
1526737726
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM Transport Channel Management
TDLBFD-001005
Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
Multi-mode: None GSM: None
Transport Channel Management
UMTS: None
UL 64QAM
LTE: LBFD-002002
Transport Channel Management
LOFD-001006
UL 64QAM
TDLBFD-002002 TDLOFD-001006 1526737730
Issue 03 (2015-06-30)
L.Traffic.UL.SCH. QPSK.ErrTB.Ibler. QCI.1
Number of QCI-1 Service TBs with initial transmission failures on the uplink SCH in QPSK modulation mode
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002002
Transport Channel Management Transport Channel Management
TDLBFD-002002
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
247
eRAN VoLTE Feature Parameter Description
11 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526737731
L.Traffic.UL.SCH. 16QAM.ErrTB.Ible r.QCI.1
Number of QCI-1 Service TBs with initial transmission failures on the uplink SCH in 16QAM modulation mode
Multi-mode: None
Transport Channel Management
Number of QCI-1 Service TBs with initial transmission failures on the uplink SCH in 64QAM modulation mode
Multi-mode: None
1526737732
Issue 03 (2015-06-30)
L.Traffic.UL.SCH. 64QAM.ErrTB.Ible r.QCI.1
GSM: None UMTS: None LTE: LBFD-002002
Transport Channel Management
TDLBFD-002002
GSM: None UMTS: None LTE: LBFD-002002
Transport Channel Management Transport Channel Management
TDLBFD-002002
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
248
eRAN VoLTE Feature Parameter Description
12 Glossary
12
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
249
eRAN VoLTE Feature Parameter Description
13 Reference Documents
13
Reference Documents
1.
3GPP TS 23401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
2.
3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC)"
3.
3GPP TS 23.203, "Policy and charging control architecture"
4.
3GPP TS 36.814, "Physical layer aspects for evolved Universal Terrestrial Radio Access (UTRA)"
5.
3GPP TS 36.321, "Medium Access Control (MAC) protocol specification"
6.
ITU-T G.107, "The E-model: a computational model for use in transmission planning"
7.
ROHC Feature Parameter Description
8.
Scheduling Feature Parameter Description
9.
DRX and Signaling Control Feature Parameter Description
10. Admission and Congestion Control Feature Parameter Description 11. Power Control Feature Parameter Description 12. QoS Management Feature Parameter Description
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
250
