VoLTE Overview R22

30/10/2023 15:00 LTE VoLTE Overview (ITRAN LR22)
::: >>
1 Introduction +
2 Feature Description +
LTE VoLTE Overview (ITRAN

3 Technical Principles +
4 Engineering Guide +
LR22) 5
and Alarms
Related Counters, KPI
+
6 Abbreviations
Feature Guide
7 References
127.0.0.1:8890/Web/Index.html#?pid=20200320143556&pv=R1.2 1/45
::: >>
1 Introduction +
5 Related Counters, KPI

and Alarms +
6 Abbreviations
7 References
:::
LTE VoLTE Overview (ITRAN LR22) >>
Version Date Author Reviewer Notes

1 Introduction +
Li Kangkang 2 Feature Description +

V1.0 2022-06-30 Chen Xing Zhang Fan Not open to the third party
Lv Yifa
V1.1 2022-09-30 Lv Yifa Zhang Fan Refer to Change History 4 Engineering Guide +

TABLE OF CONTENTS and Alarms +
6 Abbreviations
1 Introduction
1.1 Change History 7 References
1.1.1 LR22 (2022-09-30)
1.1.2 LR22 (2022-08-30)
1.2 Related Feature List and License Control
1.3 Correlation with Other Features
1.4 Differences between FDD and TDD
2 Feature Description
2.1 Background
2.2 Feature Introduction
2.3 Feature Values
2.4 System Architecture
2.4.1 Network Architecture
2.4.2 Functional Structure
3 Technical Principles
3.1 Basic Functions
3.1.1 Voice Coding Mode and Service Model
3.1.2 Voice Policy Selection
3.1.3 Basic calling procedure of voice service
3.1.4 Voice Service Dynamic Scheduling
3.1.5 Admission Control and Congestion Control
3.1.6 Moblity Management
3.1.7 RLC PDU and Functions
3.2 Enhanced Functions
3.3 ROHC
3.4 Special Scenarios
3.4.1 VoLTE Services in Carrier Aggregation Scenarios
3.4.2 VoLTE Services in High-Speed Railway Scenarios
3.4.3 PCI Detection and Self-Optimization
3.4.4 ANR (FDD Only)
3.4.5 Tool MR Task Measurement
3.4.6 Loose Delay JR-based Uplink Inter-eNB CoMP (Voice CoMP)
3.4.7 VoLTE Services in DSS Scenario
3.5 Voice Service Performance Improvement
3.6 VoLTE Services Quality Evaluation
3.6.1 QoS for VoLTE Services
3.6.2 VoLTE Services Quality Evaluation
3.6.3 EMI
4 Engineering Guide
4.1 Basic Functions
4.1.1 Admission Control and Congestion Control Based for VoLTE
4.1.2 RLC PDU Related Function
4.2 ROHC
4.3.1 ANR (FDD only)
4.4 EMI Counters
4.4.1 Application Scenarios
4.4.2 Requirements
4.4.3 Function Activation
4.4.4 Deactivating the Feature
4.4.5 Parameter Optimization
4.4.6 Activation Observation
4.4.7 Related Counters
4.4.8 Impact on Network
5 Related Counters, KPI and Alarms

5.1 Related Counters
5.2 Related KPI
5.3 Related Alarms
6 Abbreviations
7 References
FIGURES
Figure 2‑1 Network Architecture of the LTE Voice Network
Figure 3‑1 Voice Services States
Figure 3‑2 Voice Policy Selection
Figure 3‑3 VoLTE Call Establishment Flow ::: >>
Figure 4‑1 Configuring Switch of VoLTE Admission Control Base on User Experience
1 Introduction +
Figure 4‑2 Configuring QCI1 /QCI2 Bearer VoLTE Admission Control Threshold Base on User Experience
Figure 4‑3 Configuring Switch of VoLTE User Number Congestion Control
Figure 4‑4 Configuring Performance Period of VoLTE User Number Congestion Control 3 Technical Principles +
Figure 4‑5 Configuring Threshold of Starting VoLTE User Number Congestion Control 4 Engineering Guide +
Figure 4‑6 Configuring Threshold of Stopping VoLTE User Number Congestion Control 5 Related Counters, KPI
Figure 4‑7 Configuring The Number of Migration Volte User for VoLTE User Number Congestion Control and Alarms +
Figure 4‑8 Configuring Measurement Index of SRVCC to WCDMA/GERAN Based VoLTE Congestion 6 Abbreviations
Control
Figure 4‑9 Configuring Switch of VoLTE Admission Control Base on User Experience/ Switch of VoLTE 7 References
User Number Congestion Control
Figure 4‑10 Configuring RLC Sequence Number Type
Figure 4‑11 Configuring Reordering Timer for RLC FDD
Figure 4‑12 Configuring Measurement Frequency Configuration Strategy for Non-SPID VoLTE Users
Parameters
Figure 4‑13 Configuring Measurement Frequency Configuration Strategy for SPID VoLTE Users
Parameters
Figure 4‑14 Configuring Measurement Frequency Configuration Strategy for SPID Data Users Parameters
Figure 4‑15 Configuring Switch for the Configuration of Different Inter-Frequency Measurement Indication
for Voice/Data Users
Figure 4‑16 Configuring VTHO Measurement Indication of EUTRAN Frequencies
Parameters
Parameters
Figure 4‑19 Configuring Measurement Frequency Configuration Strategy for SPID Data Users Parameters
Figure 4‑20 Configuring Switch for the Configuration of Different Inter-Frequency Measurement Indication
for Voice/Data Users Close
Figure 4‑21 Configuring Switch for EMI
Figure 4‑22 Configuring Period for Calculating the EMI Value
Figure 4‑23 Configuring EMI Counter Range
Figure 4‑24 Close EMI function
TABLES
Table 1‑1 Text changes
Table 1‑2 Related Feature List
Table 1‑3 Correlation with Other Features
Table 1‑4 Differences Between TDD and FDD Functions
Table 2‑1 VoLTE function classification
Table 3‑1 Parameter Description
Table 3‑2 QoS Requirement List of Different QCI1
Table 3‑3 Capacity of VoLTE Voice Users and Video Users of a TDD 20 MHz Cell
Table 3‑4 Parameters related to admission control for the number of VoLTE bearers
Table 3‑5 Parameters Related to Congestion Control
Table 3‑6 Parameters Related to RLC PDU
Table 3‑7 Parameters Related of ANR Scenarios
Table 3‑8 QoS for VoLTE Services
Table 3‑9 Relationship between Voice Perception Satisfaction and MOS
Table 3‑10 Related parameters of EMI Couter
Table 4‑1 FDD VoLTE admission control license requirement
Table 4‑2 Admission Control and Congestion Control Based for VoLTE configuration principle
Table 4‑3 The Related Counter of VoLTE Admission and Congestion Function
Table 4‑4 Engineering Guide Parameters Related to Admission Control
Table 4‑5 RLC PDU related function configuration principle
Table 4‑6 Measurement Configuration Strategy of Voice Users and ANR configuration principle
Table 4‑8 EMI Related Counters
Table 5‑1 VoLTE related counters
Table 5‑2 VoLTE related KPIs
1 Introduction
This document is applicable to LTE FDD and TDD modes. ::: >>
The process mode of SRVCC and eSRVCC is the same in eNodeB but different in EPC.
1 Introduction +
1.1 Change History
This section describes the changes between versions of the product, including two types of changes:
Technical changes: technical and related parameter changes between two versions.
Text changes: description and structure changes between versions, including content optimization and and Alarms +
supplementation.
6 Abbreviations
7 References
1.1.1 LR22 (2022-09-30)
Technical changes:
None
Text Change:
Table 1‑1 Text changes
SN Section Change Description

1 3.6 Added Chapter 3.6 VoLTE Services Quality Evaluation,
and the original chapter 3.6 EMI is changed to 3.6.3
1.1.2 LR22 (2022-08-30)

Compared with the previous version, LR22 has the following changes:
Technical changes:
None
Text Change:
None
1.2 Related Feature List and License Control
Table 1‑2 Related Feature List
No Feature ID Feature Name License Technical

Control or Part
not
1 ZLF31-08-011 VOIP Admission Control Yes 3.1.5
Enhancement
2 ZLF31-10-002 RLC PDU and Functions No 3.1.6
1.3 Correlation with Other Features
Table 1‑3 Correlation with Other Features
Feature ID Feature Name Required Mutually Impacted

features exclusive features
features
ZLF31-08-011 VOIP Admission Control ZLF31-08-001 None None
Enhancement radion
admission
control
ZLF31-10-002 RLC PDU and its None None None
functions
1.4 Differences between FDD and TDD
Table 1‑4 Differences Between TDD and FDD Functions
No. Function point FDD TDD Chapter

1 ANR Support Not support Chapter 3.4.4
2 VoLTE Services in Support Not support Chapter 3.4.7
DSS Scenario
2 Feature Description
2.1 Background
The voice solutions of the LTE network include:
l Dual standby terminal-based voice solution
A dual standby terminal can receive and send LTE and 2G/3G signals simultaneously: or receive
LTE and 2G/3G signals simultaneously but send either LTE or 2G/3G signals. The dual standby :::
terminal selects a 2G or 3G network automatically to perform the voice services of the CS domain, >>
and selects an LTE network to perform data services.
1 Introduction +
l CSFB-based voice solution
In an LTE network without IMS deployment, based on the CSFB solution, a terminal falls back to a
2G/3G network under the instruction of the MME, and provides voice services through the CS
domain. 4 Engineering Guide +
l IMS-based voice solution (VoLTE solution) 5 Related Counters, KPI
VoLTE is the mature phase of the voice solution of the LTE network. After the IMS is deployed, a
and Alarms +
UE can directly perform voice services in the LTE network. If the UE supports eSRVCC or PS
domain handover, it can realize the seamless handover from the LTE network to a non-LTE
6 Abbreviations
network while ensuring the continuity of voice services.
7 References
The basic principle of the first two solutions (dual standby solution and CSFB solution) is to provide
voice services to the users in the LTE network by reusing the CS domain devices of the existing 2G/3G
network. However, the IMS-based voice solution (VoLTE) is an ultimate voice solution, which provides
voice services to users directly through the LTE network. This section describes the IMS-based solution
(VoLTE).
2.2 Feature Introduction

VoLTE refers to the voice sessions between the UE and IMS borne on the IP network. Both the caller
and callee can use this technology to implement voice services in the LTE packet domain network. The
core service control network of VoLTE is the IP Multimedia Subsystem (IMS). It is used together with
the LTE and EPC networks to implement end-to-end voice and video communication services based on
the packet domain. The features of VoLTE are as follows:
l Service access: The LTE network is an all IP network without CS domain. Both voice services and
data services are carried on the LTE network.
l Service control: The EPC network does not support the call control function of voice services and
multimedia services. The service control function of the EPC network is provided by the IMS
network.
l Service handover: In the areas where the LTE coverage is poor, the continuity of the voice services
between the LTE and 2G/3G CS networks is implemented by eSRVCC technology.
2.3 Feature Values

VoLTE provides voice services to the terminals in the E-UTRAN network. Compared with the CS
domain calls of 2G and 3G networks, VoLTE has the following advantages:
- Higher frequency spectrum efficiency
- Shorter access delay
- Better voice quality and user experience
2.4 System Architecture
2.4.1 Network Architecture
The LTE voice network can be divided into 3 parts: a wireless access network, a core network, and a
control part.
Figure 2‑1 Network Architecture of the LTE Voice Network
The eNodeB is responsible for the wireless access of terminals. The MME is a mobility management
entity in the core network. The S-GW is a media gateway, which forwards the data of the user plane
and acts as a mobility anchor for forwarding data during the handover process. The P-GW provides IP
addresses to the terminals and acts as the interface for accessing the PDN. The IMS is a functional
entity for controlling voice sessions. The HSS stores user subscription information. The PCRF is used
for policy billing.
2.4.2 Functional Structure
Table 2‑1 VoLTE function classification ::: >>

Category Function Description
1 Introduction +
Basic functions Voice coding and Channel coding can be used to
service model effectively compress the data amount of 2 Feature Description +
voice services. Before initiating a call, the
calling party, called party, and IMS are 3 Technical Principles +
involved to negotiate the voice coding
rate. In most cases, VoLTE services use 4 Engineering Guide +
AMR coding. For the detailed voice
coding and service mode, refer to 5 Related Counters, KPI
Section 3.1.1 Voice Coding Mode and and Alarms +
Service Model.
LTE voice policy The LTE network can use various voice 6 Abbreviations
selection service bearer solutions. For the detailed
information about how to select a voice 7 References
policy, refer to Section 3.1.2 Voice Policy
Selection.
QoS and dynamic Different services have different
scheduling requirements for delay, jitter, and packet
loss rate. Therefore, different services
use different scheduling policies to meet
the corresponding QoS requirements.
For the VoLTE-related service bearer and
scheduling policy, refer to Section 3.1.3
Basic calling procedure of voice
service.
Admission control and Compared with data services, voice
congestion control services have different requirements for
QoS. For the VoLTE-related service
admission and congestion control policy,
refer to Section 3.1.5 Admission Control
and Congestion Control.
Mobility management Compared with data services, voice
services have different requirements for
service continuity. For the VoLTE-related
mobility management policy, refer to LTE
VoLTE Mobility Guide.
Enhanced Coverage A series of voice coverage enhancement
functions enhancement policies are introduced to improve the
coverage of VoLTE services. For the
detailed information, refer to LTE VoLTE
Enhancement Guide.
Quality enhancement A series of voice quality enhancement
policies are introduced to improve the
voice quality of VoLTE services. For the
Enhancement Guide.
Capacity A series of voice capacity enhancement
enhancement policies are introduced to improve the
voice capacity of VoLTE services. For the
Enhancement Guide.
Special Carrier aggregation For the detailed information about the
Scenarios scenario of VoLTE voice service policy in special scenarios,
services such as carrier aggregation scenarios
and high-speed railway scenarios, refer
to Section 3.4 Special Scenarios.
3 Technical Principles
3.1 Basic Functions
3.1.1 Voice Coding Mode and Service Model
Voice coding mode
Coding, transmission, storage, and decoding are necessary processes of digital voice transmission
and storage. The purpose of voice coding is to digitalize voice and use the redundancy of the human
vocalization process and human auditory characteristics to reduce the coding ratio.
AMR (Adaptive Multi Rate) is a voice coding mode that is widely used in the GERAN, UTRAN, and E-
UTRAN networks. AMR can be divided into AMR-NB and AMR-WB, both of which use multi-rate
wideband Algebraic Code Excited Linear Prediction (ACELP).
AMR-NB provides eight voice coding rates, and AMR-WB provides nine voice coding rates:
1. AMR-NB: 12.2kbit/s, 10.2kbit/s, 7.95kbit/s, 7.4kbit/s, 6.7kbit/s, 5.9kbit/s, 5.15kbit/s,

and 4.75kbit/s
2. AMR-WB: 23.85kbit/s, 23.05kbit/s, 19.85kbit/s, 18.25kbit/s, 15.85kbit/s,

14.25kbit/s, 12.65kbit/s, 8.85kbit/s, and 6.6kbit/s
Service model
Figure 3‑1 Voice Services States
::: >>
1 Introduction +
Voice services can be divided into three states:
1. The transient state: It refers to the initial state when a service is set up but not yet stabilized.
During the transient state, one data packet is transmitted every 20ms. In this state, packets are 5 Related Counters, KPI
usually very large. According to the transmitted packets data collected at the UE side, the and Alarms +
transient state is very short and it is even not found in some types of smart phones, such as
Samsung Note 3. Whether the transient state exists depends on the voice algorithm adopted by of 6 Abbreviations
the chip.
7 References
2. The talk spurt state: it refers to the state when a UE is talking. In the talk spurt state, an RTP voice
packet is sent every 20ms. The size of the voice packet sent in the talk spurt state depends on the
encoding rate currently used. In the talk spurt state, RTCP packets are sent to exchange time
information between voice chips. The interval between an RTCP packet and an RTP packet does
not follow the 20 ms rule. Usually, an RTCP packet is sent between two RTP packets at an
interval that is related to the voice algorithm adopted by the chip.
3. The silent period: it refers to the state when a UE stops talking. SID packets (a kind of RTP
packets) are sent at an interval of 160ms. The interval between an RTCP packet and an RTP
packet does not follow the 160 ms rule.
4. The above describes the ideal voice service flow of a voice chip. However, after transmission (over
wired and wireless networks), the service model is deformed. In terms of PS domain index, the
larger deformation means larger jitter, larger delay, more lost packets, and worse voice quality. In
addition, eNodeB functional configurations also aggravate the deformation of the service data
flow.
3.1.2 Voice Policy Selection
As a PS-based All-IP network, the LTE network abandons traditional CS (circuit switching) domain. The
LTE network supports voice services by means of various policies so as to fulfill operators’ different
requirements in different deployment phases:
1. Dual standby terminal-based voice solution (SVLTE)
2. Circuit Switched Fallback (CSFB) solution
3. IMS-based VoLTE + eSRVCC solution
4. Other voice solution (VoIP)
A registered user of OTT (Over the Top) application software (such as WeChat and Skype) can initiate
voice or video calls through the IP data connection channel of the LTE network. These calls (aka. VoIP)
are actually data services. This solution only needs to deploy a common SIP server, so the deployment
is simple and the cost is low. However, these OTT VoIP services are still processed as ordinary data
services, so their QoS cannot be guaranteed, and a user cannot communicate with CS users or VoLTE
users. This solution can only be used as a supplementary voice solution of the LTE network.
Voice solution selection policies are as follows:
1. Based on different terminal chips, for the terminals and networks supporting only the dual-standby
terminal solution, voice services use the 2G/3G circuit domain solution.
2. For the networks supporting the CSFB solution and the terminals only supporting the CSFB
solution, voice services use the CSFB solution.
3. For the network supporting the eSRVCC and VoLTE solutions and the terminals only supporting
the eSRVCC and VoLTE solutions, voice services use the VoLTE solution within the LTE coverage
area.
4. For the networks and terminals that support both the CSFB and VoLTE + eSRVCC solutions, the
voice solution is selected based on the following principle.
Figure 3‑2 Voice Policy Selection
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
The UE has a configurable voice service domain selection parameter (Voice domain pref for EUTRAN).
Through this parameter, the UE can use an Attach Request message to inform the EPS of the
preferred voice solution. For a description of the four options of this parameter, refer to the following
table.
Table 3‑1 Parameter Description
IE Parameter Value Description

0 (CS Voice only) UE only supports CSFB
UE only supports
1 (IMS PS Voice only)
IMS/VoLTE
UE supports CSFB and
Voice domain pref for 2 (CS Voice preferred, IMS VoLTE simultaneously,
EUTRAN PS Voice as secondary) while CSFB takes
precedence.
UE supports CSFB and
3 (IMS PS Voice preferred, VoLTE simultaneously,
CS Voice as secondary) while VoLTE takes
precedence.
In the following scenarios, the VoLTE solution is not recommended:
1. Transmission requirement: to ensure voice quality, the voice end-to-end delay must be lower than
200ms, and jitter must be lower than 40ms.
2. Requirements of laws and regulations
For example, TDD bands should not be used to carry voice services. So UE cannot be handed over to
a TDD cell over QCI1 bearer.
3.1.3 Basic calling procedure of voice service
Based on the service type, delay, and packet loss rate, the LTE network divides the services of different
features into the services of different QCIs. In this case, the LTE network can use different scheduling
priorities and differentiated scheduling policies to guarantee the service quality of different services.
Voice-Related Bearers
The bearers that are directly related to VoLTE services are QCI1, QCI2, and QCI5, among which QCI1
carries voice services, QCI2 carries video services, and QCI5 carries the IMS signaling used for
establishing VoLTE. For the mapping relationship between QCI and service, please refer to LTE QoS
Function Guide.
In most cases, QCI5 is established through a default bearer, and the default bearer is established
through QCI6, QCI8, and QCI9. For the detailed information, refer to the following table.
::: >>
Table 3‑2 QoS Requirement List of Different QCI1
Packet Packet 1 Introduction +

Resource Delay Error
QCI Priority Example Services 2 Feature Description +
Type Budget Loss
(ms) Rate
1 2 100 10-2 Conversational Voice
Conversational Video 4 Engineering Guide +
2 4 150 10-3 (Live Streaming)
GBR
3 3 50 10-3 Real Time Gaming
and Alarms +
Non-Conversational
4 5 300 10-6 Video (Buffered 6 Abbreviations
Streaming)
7 References
5 1 100 10-6 IMS Signaling
Video (Buffered
Streaming)
TCP-based (e.g., www,
6 6 300 10-6
e-mail, chat, ftp, p2p file
sharing, progressive
video, etc.)
Non-GBR Voice, Video (Live
7 7 100 10-3 Streaming)
Interactive Gaming
Video (Buffered
8 8 300 10-6 Streaming) TCP-based
(e.g., www, e-mail, chat,
ftp, p2p file sharing,
9 9 300 10-6
progressive video, etc.)
Bearer Establishment Flow
The following figure shows the establishment flow of a VoLTE call.
Figure 3‑3 VoLTE Call Establishment Flow
3.1.4 Voice Service Dynamic Scheduling

Dynamic scheduling is a commonly-used basic scheduling policy of voice services. Dynamic
scheduling has the greatest degree of freedom, which can select a flexible and optimal resource
distribution policy based on channel conditions and loads. Due to the small payload and short period
characteristics of VoLTE, the dynamic scheduling of each VoLTE packet requires a PDCCH control
channel resource. In this case, control channel resources might be limited in the scenarios with high
service loads.
Besides dynamic scheduling, eNodeB also serve SPS policy for VoLTE. For the detailed information,
refer to LTE VoLTE Enhancement Feature Guide.
Different scheduling algorithms can be configured for different scenarios, including the EPF algorithm
and RR algorithm. For the detailed information, refer to the LTE QoS Feature Guide.
3.1.5 Admission Control and Congestion Control
3.1.5.1 QoS Admission Control of VoLTE
If a UE establishes multiple bearers, the eNodeB needs to sort the bearers based on the ARP and
QoS, and then admits the bearers in order. For the detailed information, refer to LTE Admission Control
Feature Guide. For VoLTE services, including QCI5, QCI1, and QCI2, the bearer admission priority of
the eNodeB is QCI5 > QCI1 > QCI2 > other NGBR bearers except the default bearer.
3.1.5.2 Bearer Quantity Admission Control of VoLTE Services
When voice calls, video calls, and data services are all deployed on the same frequency point, the
eNodeB schedules voice/video call services preferentially. In this case, voice/video calls may preempt ::: >>
scheduling resources and RB resources as listed as follows:
1 Introduction +
l If a large number of VoLTE voice users access the cell, due to scheduling resource limitation, voice
user experience cannot be guaranteed, meanwhile, video call services or data services cannot be 2 Feature Description +
scheduled. As a result, the RB usage rate of the cell is low, and the user experiences of voice
services, video call services, and data services are poor. 3 Technical Principles +
l If a large number of VoLTE video users access the cell, a large number of RB resources are 4 Engineering Guide +
occupied. In this case, other data services cannot be scheduled, and the user experience of data
services is poor, which might affect the service experience of other users. 5 Related Counters, KPI
and Alarms +
The table below lists the capacity of VoLTE voice users and video users of a TDD 20 MHz cell.
6 Abbreviations
Table 3‑3 Capacity of VoLTE Voice Users and Video Users of a TDD 20 MHz Cell 7 References
Scenario VoLTE Scenario VoLTE

Voice Video
Capacity Capacity
UL/DL Voice Service User Distribution Number UL/DL Video User VoLTE
Subframe of VoLTE Subframe Service Distribution Video
Ratio Voice Ratio users
Rate Silence Near:Medium:Far: Users Near:
Format Medium
Factor
1 23.85kbps 0.5 3:4:3 150 1 VGA 30 1: 1 8

frames
If the full capacity carries voice services, scheduling resources are exhausted, but there are still
massive RB resources left. If the full capacity carriers video services, RB resources are exhausted, but
there are still massive scheduling resources left. In commercial networks, the proportions of the voice
services, video call services, and data services of the cell constantly changes. Once the proportion of
either voice or video call services is too large, it may affect the experience of all users. Therefore, ZTE
provides a flexible policy for controlling the number of the VoLTE voice users and video users to
properly limit and schedule the proportions of the users of different types in the cell and improve the
overall experience. The function is controlled by Switch of VoLTE Admission Control Base on User
Experience. The details are as follows:
l Divide the number of the users in the cell based on VoLTE voice services, video services, and data
services, and then limit the number of VoLTE services and video services at moderate proportions,
so as to maximize the resource utilization. The number of QCI1 users is controlled by QCI1
Bearer Admission Control Threshold Based on User Experience. The number of QCI2 users
is controlled by QCI2 Bearer Admission Control Threshold Based on User Experience.
l If there are not enough QCI1 or QCI2 bearers to establish VoLTE voice services or video services
upon reception of E-RAB SETUP REQUEST, the services will be refused without any further
actions for the user.
l Perform the admission control for the VoLTE bearers that are RRC accessed, handover in, or
normally initiated to ensure that the number of VoLTE users does not exceed the threshold.
l When Switch of VoLTE Admission Control Base on User Experience is set to "Control RRC
Access and E-RAB Establishment Strategy", the voice or video users are admitted in the access
and ERAB setup phases. When Switch of VoLTE Admission Control Base on User Experience
is set to "Control E-RAB Establishment Strategy", the voice or video subscribers will be admitted in
the ERAB setup phase.
l If the admission fails, eNB returns the failure cause value "Radio resources not avalible" to the core network.
The core network triggers the CSFB process according to this failure cause value.
l For VoLTE voice users, if the RRC request cause is mo-VoiceCall-V1280, it can use the reserved
RRC number resources for handover users. It means that VoLTE voice users and handover users
share the reserved resources. The number of reserved resources can be configured by User
reserved for handover. For the detailed information, refer to LTE Admission Control Feature
Guide.
l Perform the admission control for the video bearers that are handed over or normally initiated to
ensure that the number of video users does not exceed the threshold.
n If the number of QCI1 users exceeds QCI1 admission control threshold, new access VoLTE
users will be rejected.
n If the number of QCI1 users exceeds QCI1 admission control threshold, the handover operation
on VoLTE users will be cancelled.
n If the number of QCI1 users exceeds QCI1 admission control threshold, the re-established
VoLTE users will be accseed as long as the number of RRC connections and the number of
ERAB users do not reach the thresholds. This can guarantee VoLTE user experience.
n If the number of QCI2 users excceds QCI2 admission control threshold, the QCI2 bearing
request from new access users, handover users and re-established users will be rejected.
l For inter-cell VoLTE re-establishment, the denial of the re-establishment request may cause the
direct disconnection of voice services, which might greatly affect the experience of voice users.
Therefore, the admission control of VoLTE bearers is not performed during inter-cell VoLTE re-
establishment.
Table 3‑4 Parameters related to admission control for the number of VoLTE bearers
No. Parameter FDD Parameter TDD Parameter

Name
1 Switch of VoLTELoadFDDLTE.voLTEACSwch VoLTELoadTDDLTE.voLTEACSwch
VoLTE
Admission
Control
Name
Base on
User ::: >>
Experience
2 QCI1 VoLTELoadFDDLTE.qci1NumACThrd VoLTELoadTDDLTE.qci1NumACThrd 1 Introduction +
Bearer
Admission 2 Feature Description +
Control
Threshold 3 Technical Principles +
Based on
User
Experience
3 QCI2 VoLTELoadFDDLTE.qci2NumACThrd VoLTELoadTDDLTE.qci2NumACThrd 5 Related Counters, KPI
Bearer
Admission and Alarms +
Control
Threshold 6 Abbreviations
Based on
User 7 References
Experience
4 User ACFDDLTE.reservedHO ACTDDLTE.reservedHO
reserved
for
handover
3.1.5.3 Congestion Control
When eNodeB performs service admission, PRB pre-emption may be triggered due to insufficient PRB
resources, and PRB resources of other services in the cell can be preempted. This policy can be
configured not forcibly release (configure The first rank of pre-emption QCI and The second rank of
pre-emption QCI without QCI1) or not priority forcibly release VoLTE service at first (configure The
second rank of pre-emption QCI with QCI1) by The first rank of pre-emption QCI and The second
rank of pre-emption QCI to guarantee the VoLTE user experience. For details, please refer to LTE
Congestion Control Feature Guide.
In addition, if the admission control is performed on the number of the VoLTE users in the cell, and if
the proportion of VoLTE voice users exceeds the QCI1 Bearer Admission Control Threshold Based
on User Experience, VoLTE voice services are refused, which greatly affects the user experience. To
avoid this situation, the congestion control of VoLTE voice service must be enabled. In other words, the
eNodeB periodically (Performance Period of VoLTE User Number Congestion Control) monitors
the number of VoLTE voice users. If the proportion of VoLTE voice users exceeds the congestion
threshold (Threshold of Starting VoLTE User Number Congestion Control) configured by the UME,
some VoLTE users are selected to migrate to other systems until the proportion of VoLTE voice users is
lower than Threshold of Stopping VoLTE User Number Congestion Control. The migration process
is performed based on measurement (Measurement Index of SRVCC to WCDMA Based VoLTE
congestion control and Measurement Index of SRVCC to GERAN Based VoLTE congestion
control). The number of the users that need to be migrated (The Number of Migration Volte User for
VoLTE User Number Congestion Control) each period can be configured .This function can be
configured by Switch of VoLTE User Number Congestion Control.
The proportion of VoLTE voice users = the number of QCI1 users / QCI1 Bearer Admission Control
Threshold Based on User Experience.
Note:
Suggested that Performance Period of VoLTE User Number Congestion Control not be configured
too small, because this makes easy for the VoLTE user's SRVCC process to span two periods,
resulting in SRVCC being executed for the user in the previous period, and in this period the user's
SRVCC process does not end. Therefore, statistics on this user in this load evaluation period may
cause the function to be triggered once more incorrectly.
Table 3‑5 Parameters Related to Congestion Control

Name
1 The first rank ACFDDLTE.premptQciRank1 ACTDDLTE.premptQciRank1
of pre-
emption QCI
2 The second ACFDDLTE.premptQciRank2 ACTDDLTE.premptQciRank2
rank of pre-
emption QCI
3 Performance VoLTELoadFDDLTE.voLTECongPeriod VoLTELoadTDDLTE.voLTECongPeriod
Period of
VoLTE User
Number
Congestion
Control(s)
4 Threshold of VoLTELoadFDDLTE.volteCongStarThrd VoLTELoadTDDLTE.volteCongStarThrd
Starting
VoLTE User
Number
Congestion
Control
5 Threshold of VoLTELoadFDDLTE.volteCongStopThrd VoLTELoadTDDLTE.volteCongStopThrd
Stopping
VoLTE User
Number
Congestion
Control
6 Measurement CellMeasGroupLTE.wcdmaSRVCCBasVoLTECongMeasCfg CellMeasGroupLTE.wcdmaSRVCCBasVoLTECongMeasCfg
Index of
SRVCC to
WCDMA
Based VoLTE
congestion
control
Name
7 Measurement CellMeasGroupLTE.geranSRVCCBasVoLTECongMeasCfg CellMeasGroupLTE.geranSRVCCBasVoLTECongMeasCfg
Index of ::: >>
SRVCC to
GERAN 1 Introduction +
Based VoLTE
congestion
control
8 The Number VoLTELoadFDDLTE.volteNum2Migration 3
VoLTELoadTDDLTE.volteNum2Migration Technical Principles +
of Migration
Volte User 4 Engineering Guide +
for VoLTE
User Number
Congestion
Control and Alarms +
9 Switch of VoLTELoadFDDLTE.volteCongSwch VoLTELoadTDDLTE.volteCongSwch
VoLTE User 6 Abbreviations
Number
Congestion 7 References
Control
10 QCI1 Bearer VoLTELoadFDDLTE.qci1NumACThrd VoLTELoadTDDLTE.qci1NumACThrd
Admission
Control
Threshold
Based on
User
Experience
3.1.6 Moblity Management
Refer to LTE VoLTE Mobility Feature Guide.
3.1.7 RLC PDU and Functions

RTP packets of QCI1 bearer are transmit by RLC PDU. A RTP packet may be divided in several RLC
PDUs and transmit separately, when Physical transmission rate is not enough. ENB combines the RLC
PDUs to PDCP PDU in uplink direction, and divide PDCP PDU to RLC PDUs in downlink direction.
Every RLC PDU segment is signed by a RLC SN separately. In order to avoid duplication of RLC SN,
sn_FieldLength should not be too small. If there are not many RLC segments, there is small probability
that this phenomenon occurs. In this case, sn_FieldLength may be configured to “5 bit”. But the
corresponding coverage requirement needs to be degraded. sn_FieldLength can be configured by
parameter RLC Sequence Number Type.
RLC layer needs reordering RLC PDU whether in uplink or in downlink. But the reordering needs to be
finished in RLC reordering timer Reordering Timer for RLC FDD(ms) or Reordering Timer for RLC
TDD(ms).
RLC SN 5bit compared with PDCP SN 12bit, or RLC SN 10bit compared with PDCP SN 7bit, these two
combinations ablove is not commonly used, the two combination are not suggested.
Table 3‑6 Parameters Related to RLC PDU

Name
1 RLC QoSServiceClassLTE.sequenceNumType QoSServiceClassLTE.sequenceNumType
Sequence
Number
Type
2 Reordering RLCParaLTE.tReorderingFdd RLCParaLTE.tReorderingTdd
Timer for
RLC
FDD(ms)
Reordering
Timer for
RLC
TDD(ms)
3.2 Enhanced Functions

Refer to LTE VoLTE Enhancement Feature Guide.
3.3 ROHC
Robust Header Compression (ROHC) is an IP-based compression technology, used for air interfaces in
wireless transmission to improve the resource usage of air interfaces. It is commonly used for voice
and video. It is suggested to open ROHC function on QCI1 bearer.
Note:
For more information about ROHC, Refer to LTE ROHC Feature Guide.
3.4.1 VoLTE Services in Carrier Aggregation Scenarios
In downlink multicarrier aggregation scenarios, because the amount of voice data is not large, only the
primary carrier is used to carry QCI1 VoLTE services, which is convenient for observation and
maintenance.
In addition, the protocol specifies that if uplink secondary carrier is configured, UE cannot enable TTI
Bundling.
::: >>
3.4.2 VoLTE Services in High-Speed Railway Scenarios
1 Introduction +
In high-speed rail scenarios, the channel quality changes rapidly and intensely. Therefore,
uplink/downlink SPS technology and TTI Bundling technology are not applicable for high-speed rail 2 Feature Description +
scenarios.
In principle, high-speed rail network and the public network along high-speed rail should be inter-
frequency networking, and avoid the overlap area of these two networks. However, limited by the actual 4 Engineering Guide +
network architecture, a high-speed cell of the dedicated LTE network and an ordinary cell of the public
LTE network are usually configured as neighbor cells. It is recommended to enable the UE Speed 5 Related Counters, KPI
Based Mobility Management Enhancement in a combined networking scenario of an LTE high-speed and Alarms +
network (for example, on a high-speed train) and a normal LTE network. According to the detected UE
speed, the system can guarantee only high-speed UEs to stay in the high-speed network, thus 6 Abbreviations
preventing the resources of high-speed users from being occupied by ordinary users and improving the
experience of high-speed UEs. 7 References
3.4.3 PCI Detection and Self-Optimization
In PCI conflict/confusion detection scenarios, there are two scenarios involving the influence of VoLTE
users, including PCI conflict/confusion detection during ANR and known PCI measurement based on
air interface measurement. Both scenarios involve the measurement of the ECGI. For the selection of
the measurement UE, the VoLTE users are excluded. Apart from that, before the PCI optimization of a
cell takes effect, its users will be migrated (including voice users) to neighboring cells. By this means,
VoLTE user experience can be guaranteed.
3.4.4 ANR (FDD Only)
Since ANR procedure requires ECGI measurement, especially inter-RAT ECGI measurement, which
needs a long DRX period. In order not to affect the user experience of voice services, VoLTE users will
not be chosen to perform ANR.
If the function is enabled, non-SPID voice users and SPID voice users will not be configured with ANR
frequency when coverage-based measurement frequency is delivered.
Non-SPID voice users will not be configured with ANR frequency when Measurement Frequency
Configuration Strategy for Non-SPID VoLTE Users is configured to “Not considering ANR frequency
points”. It is unnecessary to deliver ANR frequency to non-SPID voice users.
And SPID voice users will not be configured with ANR frequency when Measurement Frequency
Configuration Strategy for SPID VoLTE Users is configured to “Not considering ANR frequency
points”. It is unnecessary to deliver ANR frequency to SPID voice users.
ENB measurement configuration strategy is as follows:
1. Intra-RAT and inter-RAT frequency measurement will be configured when the frequency
measurement is not 0 and neighbor cell exist.
2. ANR measurement for reporting the highest cell and ReportCGI, will be configured when the
frequency measurement is not 0 and neighbor cell exist. Voice users will not be configured
measurement of GERAN frequency.
Intra-RAT and inter-RAT frequency measurement based on coverage needs to be reconfigured when
QCI1 bearer deleted. ANR measurement for reporting the highest cell and ReportCGI will be deleted
when QCI1 bearer setup.
Table 3‑7 Parameters Related of ANR Scenarios
No. Parameter name FDD Parameter

1 Measurement Frequency EUtranCellMeasFDDLTE.voLTEMeasFreqStgy
Configuration Strategy for
Non-SPID VoLTE Users
2 Measurement Frequency EUtranCellMeasFDDLTE.sPIDVoiceMeasFreqStgy
Configuration Strategy for
SPID VoLTE Users
3.4.5 Tool MR Task Measurement
If VoLTE users are chosen by tool MR task to perform “MR task” measurement, VoLTE user experience
will be affected because the priority of measurement report package is higher than QCI1; in this case
VoLTE packages cannot be scheduled in time.
Whether VoLTE users are chosen to do “MR task” measurement can be configured by the tool
parameter volteUeMeasSwitch. The parameter configuration path is “ENBCUCPFunction-->CULTE--
>Tool-->ToolPubConfig” on the UME.
- If the switch is set to “Y”, VoLTE users can choose to perform “MR task” measurement;
- If the switch is set to “N”, VoLTE users will be avoided to perform “MR task” measurement.
3.4.6 Loose Delay JR-based Uplink Inter-eNB CoMP (Voice CoMP)
Refer to LTE CoMP Feature Guide.
3.4.7 VoLTE Services in DSS Scenario

In the DSS scenario, SPS will not be activated even it is configured.
3.5 Voice Service Performance Improvement

1. VoLTE uplink packet loss Improvement:
- Adjustable function, reducing target BLER of QCI1; ::: >>
- Control HARQ transmission times; 1 Introduction +
- Configure PDCP Discard Timer.
2. VoLTE downlink packet loss improvement:
- Adjustable function, reducing target BLER of QCI1;
- Control HARQ transmission times. 4 Engineering Guide +
3. VoLTE calldrop improvement: 5 Related Counters, KPI

- Close QCI1 redirection function and Alarms +
- Prolong QCI1 RLF timer 6 Abbreviations

- SON functions to improve handover and ping-pang handover success rate
7 References
- Reducing Ping-pang handover and decreasing neighbor cell missing configuration/wrong
configuration to improve handover success rate and VoLTE KPI in calldrop.
- Super cell, CoMP and other interference solutions to improve intra-frequency interference
performance and reduce calldrop probability.
3.6 VoLTE Services Quality Evaluation
3.6.1 QoS for VoLTE Services
QoS for VoLTE services is listed as follows:
Table 3‑8 QoS for VoLTE Services
Resource Packet Delay Packet Error Example

Priority
Type Budget (ms) Loss Rate Services
Conversational
GBR 2 100 ms 10-2 Voice
Packet Delay Budget defines the delay requirements between UEs and the P-GW.
Packet Error Loss Rate defines the ratio upper limit of SDUs that fail to reach the upper layer of the
receiving end.
The uplink packet loss rate, downlink packet loss rate, downlink packet discard rate, and delay of the
VoLTE services can be calculated through the counters and KPIs described in Chapter 5.
3.6.2 VoLTE Services Quality Evaluation
In the network that provides voice services, voice quality is the most important factor that affects
service quality. During voice service transmission, packet loss, delay, and jitter affect voice quality.
Generally, the voice quality is evaluated in terms of MOS (Mean Opinion Score) value. MOS is a
common subjective appraisal criteria. ITU-T G.107 defines five levels for the MOS of voice services.
For the relationship between voice perception satisfaction and MOS, refer to the following table. On
condition of the same packet loss rate, delay, and jitter, the MOS values vary with different voice coding
rates.
Table 3‑9 Relationship between Voice Perception Satisfaction and MOS
Level MOS Vaule Voice Perception Satisfaction

Very good. You can hear clearly. The delay is very
Excellent 4.0～5.0
small. The communication is smooth.
Good. Sound clear. The delay is small. The
Good 3.5～4.0
communication is not very smooth and has noise.
Just so so. Sound not clear. Have some delay. Can
Average 3.0～3.5
do effective communication.
Poor. Don't hear clearly. Have long delay. Need to
Poor 1.5～3.0
communicate repeatedly.
Extremely poor. Unintelligible. Large delay. The
Bad 0～1.5
communication is very not smooth.
3.6.3 EMI
For VoLTE voice quality evaluation, test software +MOS box is commonly used, and the POLQA
(Perceptual Objective Listening Quality Assessment) algorithm is selected to score the MOS. This
method features the high correctness, but it requires driving test or dial test: which makes the
evaluation range is limited, the expense is high, and it cannot correlate to the wireless network data for
analysis.
Hence, ZTE e-Model based EMI model (Equivalent MOS Indicator) is developed for VoLTE quality
evaluation. It evaluates users’ voice quality by KPIs (packets loss rate, delay, jitter and so on) during a
voice quality evaluation period. Its evaluation range is wide and the driving test is not required, and the
cost is low. Although it might be small margin of errors compared with test software +MOS box, EMI is
still valuable in practice, considering the whole-network evaluation range and low cost. What’s more,
the Netmax EMI statistics can be correlated automatically to MR/CDT data for the optimization of
wireless network, greatly improving the voice quality optimizing efficiency. The EMI value statistics
requires a separate Netmax server.
In addition, the eNodeB provides a group of EMI counters to evaluate the call quality of voice users in
the network. The higher the EMI value, the better the call quality. If the Switch for EMI is open, the
eNodeB calculates the uplink and downlink EMI values of voice users based on some key monitoring
Indicators (packet loss rate, delay, jitter, and coding rate) on the network side within period for
Calculating the EMI Value. There are eight EMI counters in total. The uplink and downlink EMI values
are in four ranges, and the uplink and downlink EMI scope values are the same. The four ranges can :::
be flexibly configured through EMI counter range, so that users can observe the EMI value distribution
>>
in a range.
1 Introduction +
Note: Due to the restriction of the conditions of the sampling point, the EMI value output by the Netmax 2 Feature Description +
servier may differs from that output by the test software+MOS box.
Table 3‑10 Related parameters of EMI Couter 4 Engineering Guide +
No. Parameter FDD Parameter TDD Parameter 5 Related Counters, KPI
name
and Alarms +
1 Switch for VoLTEConfigCellFDDLTE.emiSwch VoLTEConfigCellTDDLTE.emiSwch
EMI 6 Abbreviations
2 Period for VoLTEConfigCellFDDLTE.eMIPeriod VoLTEConfigCellTDDLTE.eMIPeriod
Calculating 7 References
the EMI
Value
3 EMI VoLTEConfigCellFDDLTE.eMIValue VoLTEConfigCellTDDLTE.eMIValue
Counter
Range
4 Engineering Guide
4.1 Basic Functions
4.1.1 Admission Control and Congestion Control Based for VoLTE
4.1.1.1 Application Scenarios
This feature provides the control stategy for cell voice users and video users. Rational restriction and
regulation of the proportion of different types of users in the cell. When the voice user reaches a certain
threshold in the cell, trigger the congestion control and the voice users are migrated to other inter-RAT
cell in order to enhance the VoLTE user experience.
4.1.1.2 Requirements
4.1.1.2.1 Hardware Requirement
No special requirements
4.1.1.2.2 EPC Requirements
EPC support IMS.
4.1.1.2.3 Frequency Band, Frequency and Bandwidth Requirements
LTE network configure Inter-RAT neighbor cell.
4.1.1.2.4 UE Requirement
UE should support VoLTE and GERAN/UTRAN.
4.1.1.2.5 Transmission Bandwidth Requirements
4.1.1.2.6 License Requirement
Table 4‑1 FDD VoLTE admission control license requirement
No FL FL name License file License control Control

No. item level
1 ZLF31-08- VOIP Admission LTE- LTE FDD VoLTE eNodeB
011 Control FDD_ENB_F157 congestion control
Enhancement enahcnement
2 ZLF31-08- VOIP Admission LTE- LTE FDD VOIP eNodeB
011 Control FDD_ENB_F156 based admission
Enhancement control
endhancement
4.1.1.3 Function Activation
4.1.1.3.1 Related parameters ::: >>
1 Introduction +
Table 4‑2 Admission Control and Congestion Control Based for VoLTE configuration principle
Parameter Parameter
2Default Feature Description +
SN Parameter Range value
Name explanation value
To guarantee
user 4 Engineering Guide +
experience in
the cell, this 5 Related Counters, KPI
parameter is
used to
enum(Close, and Alarms +
Control RRC
FDD: Switch of control the
VoLTE admission
Access and E- 6 Abbreviations
VoLTELoadFDDLTE.voLTEACSwch RAB
Admission control
1
Control Base strategy
Establishment 7
Close References
TDD: Strategy,Control E-
on User based on
VoLTELoadTDDLTE.voLTEACSwch RAB
Experience VoLTE
Establishment
numbers and
Strategy)
E-RAB
numbers
whether to
take effect or
not.
FDD:
ACFDDLTE.reservedHO User
User reserved Reserved for
2 [0..100] 5
for handover handover and
TDD: VoLTE
ACTDDLTE.reservedHO
To guarantee
user
experience in
the cell, this
parameter is
used to limit
the number of
FDD: QCI1 Bearer access QCI1
VoLTELoadFDDLTE.qci1NumACThrd Admission bearing. The
Control operator can
3 [0..800] 100
Threshold Base configure it
TDD: on User according to
VoLTELoadTDDLTE.qci1NumACThrd Experience actual needs,
but no more
than the
threshold of
RRC
Connection
user
numbers.
To guarantee
user
experience in
the cell, this
parameter is
used to limit
the number of
FDD: QCI2 Bearer access QCI2
VoLTELoadFDDLTE.qci2NumACThrd Admission bearing. The
Control operator can
4 [0..400] 4
Threshold Base configure it
TDD: on User according to
VoLTELoadTDDLTE.qci2NumACThrd Experience actual needs,
but no more
than the
threshold of
RRC
Connection
user
numbers.
Switch of
VoLTE user
number
FDD: congestion
Switch of
VoLTELoadFDDLTE.volteCongSwch control, which
VoLTE User
determine
5 Number enum(Close,Open) Close
whether
TDD: Congestion
VoLTE user
VoLTELoadTDDLTE.volteCongSwch Control
number
congestion
control is
valid or not.
Performance
period of
VoLTE user
FDD: Performance number
VoLTELoadFDDLTE.voLTECongPeriod Period of congestion
VoLTE User control is
6 [3~65535] 5
Number used to
TDD: Congestion evaluate
VoLTELoadTDDLTE.voLTECongPeriod Control(second) VoLTE user
number load
and SRVCC
process.
This
parameter is
FDD: Threshold of used to judge
VoLTELoadFDDLTE.volteCongStarThrd Starting VoLTE whether the :::
7 User Number VoLTE user [0..100] 90 >>
TDD: Congestion number of the
Control cell is 1 Introduction +
VoLTELoadTDDLTE.volteCongStarThrd
congestion or
not. 2 Feature Description +
This 3 Technical Principles +
parameter is
FDD: Threshold of
used to judge 4 Engineering Guide +
VoLTELoadFDDLTE.volteCongStopThrd Stopping
whether the
VoLTE User
8 VoLTE user [0..100] 80
Number
TDD: number
Congestion
congestion of and Alarms +
VoLTELoadTDDLTE.volteCongStopThrd Control
the cell is
relieve or not. 6 Abbreviations
FDD: The Number of

This 7 References
parameter
VoLTELoadFDDLTE.volteNum2Migration Migration Volte
determines
User for VoLTE
9 the number of [1..20] 1
User Number
TDD: volte user
Congestion
VoLTELoadTDDLTE.volteNum2Migration migrated by
Control
SRVCC.
The first rank
of Pre-
FDD: emption QCI. 0:None,
ACFDDLTE.premptQciRank1 GBR E-RABs 1:QCI1,
The first rank of [QCI2,
which QCI in
10 pre-emption 2:QCI2, QCI3,
Rank1 will be
TDD: QCI 3:QCI3, QCI4,None]
preempted
ACTDDLTE.premptQciRank1 first in 4:QCI4
congestion
control.
The second
rank of Pre-
FDD: emption QCI. 0:None,
ACFDDLTE.premptQciRank2 GBR E-RABs 1:QCI1, [QCI1,
The second
which QCI in None,
11 rank of pre- 2:QCI2,
Rank1 will be None,
TDD: emption QCI 3:QCI3,
preempted None]
ACTDDLTE.premptQciRank2 first in 4:QCI4
congestion
control.
This
parameter is
an index of
Measurment,
uniquely
Measurement
FDD: related to a
Index of
CellMeasGroupLTE.wcdmaSRVCCBasVoLTECongMeasCfg Measurement
SRVCC to
Configuration,
12 WCDMA Based [1..65535] 1772
and it is used
TDD: VoLTE
as the
CellMeasGroupLTE.wcdmaSRVCCBasVoLTECongMeasCfg Congestion
SRVCC to
Control
WCDMA
measurement
Based VoLTE
congestion
control.
This
parameter is
an index of
Measurment,
uniquely
Measurement
FDD: related to a
Index of
CellMeasGroupLTE.geranSRVCCBasVoLTECongMeasCfg Measurement
SRVCC to
Configuration,
13 GERAN Based [1..65535] 1722
and it is used
TDD: VoLTE
as the
CellMeasGroupLTE.geranSRVCCBasVoLTECongMeasCfg Congestion
SRVCC to
Control
GERAN
measurement
Based VoLTE
congestion
control.
4.1.1.3.2 Activating the Feature
1. Configuring Switch of VoLTE Admission Control Base on User Experience
FDD: Select [Managed Element->eNodeB CU->LTE->E-UTRAN FDD Cell-> VoLTE->LTE FDD

Comprehensive Solution for VoLTE Over Load],
TDD: Select [Managed Element->eNodeB CU->LTE->E-UTRAN TDD Cell-> VoLTE->LTE TDD

click (edit) button. Set [Switch For VoLTE Admission Control Base on User Experience] to
[Control RRC Access and E-RAB Establishment Strategy] or [Control E-RAB Establishment
Strategy], See the figure below. Then click (activate) button.
Figure 4‑1 Configuring Switch of VoLTE Admission Control Base on User Experience
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
2. Configuring QCI1/QCI2 Bearer VoLTE Admission Control Threshold Base on User Experience


click (edit) button. According to operator configuration, Set [QCI1 Bearer VoLTE Admission
Control Threshold Base on User Experience] and [QCI2 Bearer VoLTE Admission Control
Threshold Base on User Experience].See the figure below, Then click (activate) button.
Figure 4‑2 Configuring QCI1 /QCI2 Bearer VoLTE Admission Control Threshold Base on User
Experience
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
3. Configuring Switch of VoLTE User Number Congestion Control
FDD:Select [Managed Element->eNodeB CU->LTE->E-UTRAN FDD Cell-> VoLTE->LTE FDD

TDD:Select [Managed Element->eNodeB CU->LTE->E-UTRAN TDD Cell-> VoLTE->LTE TDD

click (edit) button. Set [Switch of VoLTE User Number Congestion Control] to [Open], See the
figure below. Then click (activate) button.
Figure 4‑3 Configuring Switch of VoLTE User Number Congestion Control
4. Configuring Performance Period of VoLTE User Number Congestion Control

Comprehensive Solution for VoLTE Over Load], ::: >>
1 Introduction +
click (edit) button. Set [Performance Period of VoLTE User Number Congestion Control]
to [5], See the figure below. Then click (activate) button. According to operator configure this
parameter.
Figure 4‑4 Configuring Performance Period of VoLTE User Number Congestion Control 5 Related Counters, KPI
and Alarms +
6 Abbreviations
7 References
5. Configuring Threshold of Starting VoLTE User Number Congestion Control


click (edit) button. Set [Threshold of Starting VoLTE User Number Congestion Control(%)]
to [90], See the figure below. Then click (activate) button. According to operator configure this
parameter.
Figure 4‑5 Configuring Threshold of Starting VoLTE User Number Congestion Control
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
6. Configuring Threshold of Stopping VoLTE User Number Congestion Control


click (edit) button. Set [Threshold of Stopping VoLTE User Number Congestion Control(%)] to
[80],See the figure below. Then click (activate) button. According to operator configure this
parameter.
Figure 4‑6 Configuring Threshold of Stopping VoLTE User Number Congestion Control
7. Configuring The Number of Migration Volte User for VoLTE User Number Congestion Control

Comprehensive Solution for VoLTE Over Load], ::: >>
1 Introduction +
click (edit) button. Set [The Number of Migration Volte User for VoLTE User Number
Congestion Control] to [1],See the figure below. Then click (activate) button. According to
operator configure this parameter.
Figure 4‑7 Configuring The Number of Migration Volte User for VoLTE User Number Congestion Control 5 Related Counters, KPI
and Alarms +
6 Abbreviations
7 References
8. Configuring Measurement Index of SRVCC to WCDMA/GERAN Based VoLTE Congestion Control
FDD: Select [Managed Element->eNodeB CU->LTE->UE measurement-> Measurement

Config Group],
TDD: Select [Managed Element->eNodeB CU->LTE->UE measurement-> Measurement

Config Group],
click (edit) button. Set [Measurement Index of SRVCC to WCDMA Based VoLTE
Congestion Control] to [1772]. Then click (activate) button.
FDD: Select [Managed Element->eNodeB CU->LTE->UE measurement-> Measurement

Config Group],
TDD: Select [Managed Element->eNodeB CU->LTE->UE measurement-> Measurement

Config Group],
click (edit) button. Set [Measurement Index of SRVCC to Geran Based VoLTE Congestion
Control] to [1722]. Then click (activate) button.
Figure 4‑8 Configuring Measurement Index of SRVCC to WCDMA/GERAN Based VoLTE Congestion
Control
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
4.1.1.4 Deactivating the Feature
1. Configuring Switch of VoLTE Admission Control Base on User Experience and Switch of VoLTE


click (edit) button. Set [Switch of VoLTE Admission Control Base on User Experience/
Switch of VoLTE User Number Congestion Control] to [Close]. Then click (activate) button.
Figure 4‑9 Configuring Switch of VoLTE Admission Control Base on User Experience/ Switch of VoLTE
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
4.1.1.5 Parameter Optimization
During VoLTE-based admission and congestion control process, the number of VoLTE users and the
start congestion control threshold and the stop congestion control threshold are configurable. By
modifying the parameters, the VoLTE user experience is optimized.
4.1.1.6 Signaling Observation
Terminals initiate VoLTE voice service on LTE network. For VoLTE admission control, the number of
voice service UEs is controlled during new user access process and handover process. This ensures
that the number of VoLTE users will not exceed the threshold. For VoLTE congestion control, when the
number of voice service users in a cell reaches the Threshold of Starting VoLTE User Number
Congestion Control, UE migration process is triggered. Voice users are migrated through eSRVCC.
When the number of users in a cell reaches the Threshold of Stopping VoLTE User Number
Congestion Control, migration stops.
4.1.1.7 Related Counters
Table 4‑3 The Related Counter of VoLTE Admission and Congestion Function
Counter ID Counter Name

C373210472 Number of E-RAB(QCI1) HO Incoming Admission Request
C373210482 Number of E-RAB(QCI1) HO Incoming Admission Fail
Number of Initial QCI1 E-RAB Setup Failures due to ENB
C373210201
Admission Failure
Number of QCI1 E-RAB Modification Failure due to ENB
C373210309
Admission Failure
Number of QCI1 E-RAB Release by ENB Through E-RAB
C373210412
Release Procedure due to Cell Congestion
4.1.1.8 Impact on Network
4.1.1.8.1 Gain Analysis
The percentages of voice, video and data services in a cell unceasingly change on a commercial
network. Once the percentage of one type of VoLTE services is very big, it is certain that the
experience of all users will be affected. When the number of voice service users reaches system
capacity, scheduling resources are used up, but there are still many idle RB resources. When the
number of video service users reaches system capacity, RB resources are used by, but there are still
many idle scheduling resources. Thus, it is necessary to implement admission and congestion control
on the number of VoLTE voice users and the number of video users in a cell. The purpose is to improve
all user experience by properly restraining and adjusting the proportions of different types of users in a
cell.
Function enabling suggestions: At VoLTE initial commercial stage, the number of VoLTE users is small.
In this situation, it is impossible for VoLTE voice or video service users to occupy many scheduling
resources and PRB resources. Enablig admission and congestion control switch, there is no change for
the system to run control process, thus users in the cell will not experience much change. As the
number of VoLTE users grows to a large scale, it is necessary to run admission and congestion control
process to guarantee that different type of users have satisfied experience. Thus, this function should
be enabled. As for small bandwidth, e.g. 3M, sytem capacity is very limit, it is suggested to enable ::: >>
admission and congestion control function to ensure intra-RAT uses have satisfied experience.
Additionally, it is suggested to set Switch of Redirection for Admit Failure to “open” for 3M
1 Introduction +
bandwidth. In this situation, UE can be re-directed to a heterogeneous system. As for other bandwidth,
it is unnecessary to set Switch of Redirection for Admit Failure open. 2 Feature Description +
4.1.1.8.2 Impact Analysis
The system runs congestion control process when the number of VoLTE users reaches 90% of the
configured admission control threshold. During the process, the system selects several configurable 5 Related Counters, KPI
UEs to trigger eSRVCC. When the number of VoLTE users is smaller than 80% of the configured and Alarms +
admission control threshold the system exits congestion control process. Therefore, it is predicated that
VoLTE resident ratio will decrease. 6 Abbreviations
When the number of VoLTE reaches the configured threshold, admission control works so that the 7 References
system will reject new VoLTE users. If admission failure re-direction siwth is off (default state), VoLTE
user access fails or calldrops, VoLTE connection success rate or drop call rate will rise.
If Switch of Redirection for Admit Failure is open, the new VoLTE user access will trigger re-
direction process, thus, more users are redirected from VoLTE to a heterogeneous system.
Table 4‑4 Engineering Guide Parameters Related to Admission Control

Name
1 Switch of ACFDDLTE.swchOfRedi4ACFail ACTDDLTE.swchOfRedi4ACFail

Redirection
for Admit
Failure
4.1.2 RLC PDU Related Function
RTP packets on QCI1 bearer are transmitted in RLC PDU unit. A RTP packet may be divided into
several RLC PDUs and transmitted separately. The configuration of RLC SN field is carried in the QCI1
bearer reconfiguration message.
No special requirements.
EPC support IMS.
UE supports VoLTE.
Null
4.1.2.3.1 Related parameters ::: >>
1 Introduction +
Table 4‑5 RLC PDU related function configuration principle
Parameter Parameter
2
Default
Feature Description +
SN Parameter Range value
Name explanation value
This
FDD:
parameter 4 Engineering Guide +
indicates the
QoSServiceClassLTE.sequenceNumType RLC
SN length 5 Related Counters, KPI
Sequence
1 range of the enum(5bit,10bit) 10bit
Number and Alarms +
TDD: RLC in UM
Type
mode. It can
QoSServiceClassLTE.sequenceNumType 6 Abbreviations
be set to 5bit
and 10bit.
This 7 References
parameter
Reordering sets the enum(0,5,10,15,20,25,30,35,40,45,50,
Timer for reordering
2 RLCParaLTE.tReorderingFdd 55,60,65,70,75,80,85,90,95,100, 45
RLC timer for FDD
FDD(ms) RLC (AM 110,120,130,140,150,160,170,180,190,200)
mode or UM
mode).
This
parameter
Reordering sets the enum(0,5,10,15,20,25,30,35,40,45,50,
Timer for reordering
3 RLCParaLTE.tReorderingTdd RLC timer for TDD 55,60,65,70,75,80,85,90,95,100, 45
TDD(ms) RLC (AM 110,120,130,140,150,160,170,180,190,200)
mode or UM
mode).
1. Configuring RLC Sequence Number Type: select [Managed Element->eNodeB CU->LTE->QoS-

> QoS Service Class], click (edit) button. Set [RLC Sequence Number Type] to [10bit[1]].
Then click (activate) button.
Figure 4‑10 Configuring RLC Sequence Number Type
2. Configuring Reordering Timer for RLC FDD(ms): select [Managed Element->eNodeB CU->LTE-
>Qos->RLC Parameters], click (edit) button. Set [Reordering Timer for RLC FDD(ms)] to
[45[9]]. Then click (activate) button.
Figure 4‑11 Configuring Reordering Timer for RLC FDD
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
No
4.1.2.5 Related Couters
None
eNodeB can carry RLC SN configuration and FDD RLC t-Reordering timer=45ms (timer length) in a
voice service setup reconfiguration message. This can avoid downlink RTP packets being lost because
t-Reordering timer is time out, even though the maxmimum number of MAC HARQ retransmissions is
not reached. Thus, downlink RTP packet loss rate can be reduced by changing the timer length.
4.1.2.6.2 Impat Analysis
Impact on network:
Originally RLC SN and RLC t-Reordering timer are carried in the QCI1 reconfiguration message for
QCI 1. In this function, RLC t-Reordering timer is changed from 35ms to 45ms. Because the timer
length is changed, more data is buffered at RLC layer. Thus, scheduling delay may be prolonged.
Impact on functions:
Null
4.2 ROHC
Refer to LTE ROHC Feature Guide.
4.3.1 ANR (FDD only) ::: >>
1 Introduction +
At present, voice users can configure the mobility policy separately, in which the configuration of
frequency points will be affected by the ANR function, so the overlay configuration will conflict with the
configuration of voice mobility policy separately. Therefore, it is decided whether the final ANR initiates 4 Engineering Guide +
eCGI measurement or not according to whether it is used as a filtering condition for voice users.
and Alarms +
6 Abbreviations
7 References
EPC support IMS and VoLTE
UE should support VoLTE and ANR
Null
4.3.1.3.1 Related parameters
Table 4‑6 Measurement Configuration Strategy of Voice Users and ANR configuration principle
Parameter Parameter Range Default

SN Parameter
Name Explanation Value Value
This
parameter
sets the
measurement
frequency
configuration
strategy for
non-SPID
VoLTE users.
If it is set to
“Considering
ANR
[Considering
frequency
Measurement ANR
points”,
Frequency frequency Considering
additional
Configuration points, Not ANR
1 EUtranCellMeasFDDLTE.voLTEMeasFreqStgy measurement
Strategy for considering frequency
needs to be
Non-SPID ANR points
performed on
VoLTE Users frequency
ANR
points]
frequencies.
If it is set to
“Not
considering
ANR
frequency
points”, no
additional
measurement
is required for
ANR
frequencies.
This
parameter
sets the
measurement :::
frequency >>
configuration
strategy for 1 Introduction +
SPID VoLTE
users. If it is 2 Feature Description +
set to
“Considering 3 Technical Principles +
ANR
frequency
[Considering 4 Engineering Guide +
Measurement ANR
points”,
Frequency
additional
frequency Considering 5 Related Counters, KPI
2 EUtranCellMeasFDDLTE.sPIDVoiceMeasFreqStgy
Strategy for
measurement
considering frequency
and Alarms +
needs to be
SPID VoLTE ANR points
Users
performed on
frequency
6 Abbreviations
ANR
points]
frequencies. 7 References
If it is set to
“Not
considering
ANR
frequency
points”, no
additional
measurement
is required for
ANR
frequencies.
This
parameter
sets the
measurement
frequency
configuration
strategy for
SPID data
users. If it is
set to
“Considering
ANR
[Considering
frequency
Measurement ANR
points”,
Frequency frequency Considering
additional
3 EUtranCellMeasFDDLTE.sPIDDataMeasFreqStgy measurement
Strategy for considering frequency
needs to be
SPID Data ANR points
performed on
Users frequency
ANR
points]
frequencies.
If it is set to
“Not
considering
ANR
frequency
points”, no
additional
measurement
is required for
ANR
frequencies.
1. Configuring Measurement Frequency Configuration Strategy for Non-SPID VoLTE Users
Select [Managed Element->eNodeB CU->LTE->E-UTRAN FDD Cell->LTE FDD Measurement

Parameter],
click (edit) button. Set [Measurement Frequency Configuration Strategy for Non-SPID
VoLTE Users] to [Not considering ANR frequency points[1]], Then click (activate) button.
Parameters
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
2. Configuring Measurement Frequency Configuration Strategy for SPID VoLTE Users

Parameter],
click (edit) button. Set [Measurement Frequency Configuration Strategy for SPID VoLTE
Users] to [Not considering ANR frequency points[1]], Then click (activate) button.
Parameters
3. Configuring Measurement Frequency Configuration Strategy for SPID Data Users
Parameter],
click (edit) button. Set [Measurement Frequency Configuration Strategy for SPID Data ::: >>
Users] to [Not considering ANR frequency points[1]]. Then click (activate) button.
1 Introduction +
Figure 4‑14 Configuring Measurement Frequency Configuration Strategy for SPID Data Users Parameters 2 Feature Description +

and Alarms +
6 Abbreviations
7 References
4. Configuring Switch for the Configuration of Different Inter-Frequency Measurement Indication for
Voice/Data Users
Select [Managed Element->eNodeB CU->LTE->Global Switch],
click (edit) button. Set [Switch for the Configuration of Different Inter-Frequency
Measurement Indication for Voice/Data Users] to [Open[1]], Then click (activate) button.
Figure 4‑15 Configuring Switch for the Configuration of Different Inter-Frequency Measurement
Indication for Voice/Data Users
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
5. Configuring VTHO Measurement Indication of EUTRAN Frequencies

Parameter->EUtran Inter-frequency Measurement Parameters],
click (edit) button. Set [VTHO Measurement Indication of EUTRAN Frequencies] to [1].
Then click (activate) button.
Figure 4‑16 Configuring VTHO Measurement Indication of EUTRAN Frequencies
1. Configuring Measurement Frequency Configuration Strategy for Non-SPID VoLTE Users

::: >>
Parameter], 1 Introduction +
click (edit) button. Set [Measurement Frequency Configuration Strategy for Non-SPID 2 Feature Description +
VoLTE Users] to [considering ANR frequency points[0]], Then click (activate) button.
Figure 4‑17 Configuring Measurement Frequency Configuration Strategy for Non-SPID VoLTE Users 4 Engineering Guide +
Parameters
and Alarms +
6 Abbreviations
7 References
2. Configuring Measurement Frequency Configuration Strategy for SPID VoLTE Users

Parameter],
click (edit) button. Set [Measurement Frequency Configuration Strategy for SPID VoLTE
Users] to [considering ANR frequency points[0]], Then click (activate) button.
Parameters
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
3. Configuring Measurement Frequency Configuration Strategy for SPID Data Users

Parameter],
click (edit) button. Set [Measurement Frequency Configuration Strategy for SPID Data
Users] to [Not considering ANR frequency points[1]], Then click (activate) button.
Figure 4‑19 Configuring Measurement Frequency Configuration Strategy for SPID Data Users
Parameters
4. Close Switch for the Configuration of Different Inter-Frequency Measurement Indication for
Voice/Data Users
Select [Managed Element->eNodeB CU->LTE->Global Switch],
click (edit) button. Set [Switch for the Configuration of Different Inter-Frequency
Measurement Indication for Voice/Data Users] to [Close[0]], Then click (activate) button.
::: >>
1 Introduction +
Figure 4‑20 Configuring Switch for the Configuration of Different Inter-Frequency Measurement
Indication for Voice/Data Users Close 2 Feature Description +

and Alarms +
6 Abbreviations
7 References
4.3.1.5 Activation Oberservation

Inter-frequency A2 measurement and fast ANR measurement will be configured in RRC Connection
Reconfiguration message in UE attachment. UE will send A2 measurement report after QCI1 bearer is
setup, and eNB will configure inter-frequency A3 measurement without ECGI.
4.3.1.5.1 Signaling Oberservation
In inter-frequency A2 measurement configuration, there will no inter-frequency A2 measurement

configured, and all inter-frequency A2 measurement configured will be deleted when all VTHO
measurement indication of inter-frequency measurement is 0 for QCI1 user.
QCI1 user will not be configured ECGI measurement, and data user still will be configured ECGI
measurement.
4.3.1.6 Related Counters
None
4.3.1.7 Network Monitoring
None
For non-SPID VoLTE users, SPID VoLTE users and SPID data users, whether ANR frequency
measurement can be configured on OMC. If ANR measurement is not considered, the UE will only
report the mobility measurement result, so it will not occur the conflict between ANR frequency
measurement and mobility frequency measurement. The feature can ensure the timeliness of mobility
measurement and also reduce the user experience impact of services.
Function enabling suggestions
In order to reduce the impact of voice users, it suggests that the non-SPID and SPID voice users are
configured to not consider ANR frequency points, and the data users are configured to consider ANR
frequency points, meeting the requirement of ANR strategy.
4.3.1.8.2 Impact Analysis
Reduce the sample of voice users’ ANR measurement, the ANR measurement result may be impacted,
and the veracity of ANR strategy. But there are large data users in the network, the impact is little. ::: >>
Impact on function
1 Introduction +
None. 2 Feature Description +
4.4 EMI Counters

4.4.1 Application Scenarios
and Alarms +
For VoLTE voice quality evaluation, although the test software +MOS box has high accuracy, its
6 Abbreviations
evaluation scope is limited and the evaluation cost is very high. The netmax server needs to be
deployed for netmax EMI value evaluation. The EMI counters can be widely used and cost-effective 7 References
used toevaluate the call quality of voice users in the network. Compared with the test software +MOS
box and netmax, the EMI counter has a certain error.
4.4.2 Requirements
4.4.2.1 Hardware Requirement
4.4.2.2 EPC Requirements
EPC support IMS and VoLTE
4.4.2.3 Frequency Band, Frequency and Bandwidth Requirements
4.4.2.4 UE Requirement
UE should support VoLTE.
4.4.2.5 Transmission Bandwidth Requirements
4.4.3 Function Activation
4.4.3.1 Related parameters
Parameter Parameter
SN Parameter Range Value Default Value
Name Explanation
The
FDD: parameter is
VoLTEConfigCellFDDLTE.emiSwch used to
Switch for
1 control enum(Close,Open) Close
EMI
TDD: whether EMI
VoLTEConfigCellTDDLTE.emiSwch value report
or not.
This
parameter
sets the
period for
calculating
the EMI
value. If the
EMI function
is enabled,
the uplink
FDD: and
Period for
VoLTEConfigCellFDDLTE.eMIPeriod downlink
Calculating
2 EMI values [5..60] 8
the EMI
TDD: of a VoLTE
Value
VoLTEConfigCellTDDLTE.eMIPeriod UE are
calculated in
each
statistical
period to
evaluate the
call quality
of the UE
during this
period of
time.
This
parameter
sets the
range of :::
EMI values. >>
The first
element of 1 Introduction +
the
parameter 2 Feature Description +
value
indicates the 3 Technical Principles +
maximum
value of EMI 4 Engineering Guide +
counter
range 1, the 5 Related Counters, KPI
second and Alarms +
element
indicates the 6 Abbreviations
maximum
FDD: value of EMI 7 References
VoLTEConfigCellFDDLTE.eMIValue EMI counter [1..5] step 0.1 [4.5,3.8,2.8,1.8,1]
3 Counter range 2, the
TDD: Range third
element
VoLTEConfigCellTDDLTE.eMIValue
indicates the
maximum
value of EMI
counter
range 3, the
fourth
element
indicates the
maximum
value of EMI
counter
range 4, and
the fifth
element
indicates the
minimum
value of EMI
counter
range 4.
4.4.3.2 Activating the Feature
1. Configuring the switch of EMI function
FDD: Select Rancm->Smart CM->Mo Content->Managed Element->eNodeB CU->LTE->E-UTRAN

FDD Cell->VoLTE->LTE FDD VoLTE Config->Switch for EMI,
TDD: Select Rancm->Smart CM->Mo Content->Managed Element->eNodeB CU->LTE->E-UTRAN

TDD Cell-> VoLTE->LTE TDD VoLTE Config->Switch for EMI,
Click (Edit) and set Switch for EMI to Open[1]. Click “OK” to save configuration.
Take FDD as as example:
Figure 4‑21 Configuring Switch for EMI
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
2. Configuring the Period for Calculating the EMI Value

FDD Cell->VoLTE->LTE FDD VoLTE Config-> Period for Calculating the EMI Value,

TDD Cell-> VoLTE->LTE TDD VoLTE Config-> Period for Calculating the EMI Value,
Click (Edit) and set Period for Calculating the EMI Value to 8. Click “OK” to save configuration.
Take FDD as an example:
Figure 4‑22 Configuring Period for Calculating the EMI Value
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
3. Configuring the EMI counter range

FDD Cell->VoLTE->LTE FDD VoLTE Config-> EMI Counter Range,

TDD Cell-> VoLTE->LTE TDD VoLTE Config-> EMI Counter Range,
Click (Edit) and set EMI Counter Range to [4.5, 3.8, 2.8, 1.8, 1]. Click “OK” to save configuration.
Take FDD as as example:
Figure 4‑23 Configuring EMI Counter Range
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
4. Check the configuration and click Activate button.
4.4.4 Deactivating the Feature
1. Close Switch of EMI function

FDD Cell->VoLTE->LTE FDD VoLTE Config->Switch for EMI,

TDD Cell-> VoLTE->LTE TDD VoLTE Config->Switch for EMI,
Click (Edit) and set Switch for EMI to Close[0]. Click “OK” to save configuration.
Take FDD as an example:
Figure 4‑24 Close EMI function
::: >>
1 Introduction +

and Alarms +
6 Abbreviations
7 References
2. Check the configuration and click Activate button.
4.4.5 Parameter Optimization
According to the test, the UE adjusts the parameter of period for calculating the EMI value and EMI
counter range.
4.4.6 Activation Observation
4.4.6.1 Signaling Observation
There is no relevant signaling.
4.4.6.2 Performance Monitoring
Null
4.4.7 Related Counters
EMI switch is on. If there are VoLTE voice users in the cell, the values of the following counters will not
be all-zero.
Table 4‑8 EMI Related Counters
Counter ID Counter Name

Number of Times the UL EMI Is in Range 1 for VoLTE
C374251962
Users
C374251963
Users
C374251964
Users
C374251965
Users
Number of Times the DL EMI Is in Range 1 for VoLTE
C374251966
Users
C374251967
Users
C374251968
Users
Number of Times the DL EMI Is in Range4 for VoLTE
C374251969
Users
::: >>
4.4.8 Impact on Network
1 Introduction +
4.4.8.1 Gain Analysis 2 Feature Description +
EMI counters are used to evaluate the voice quality of voice users on the network. The evaluation 3 Technical Principles +
result shall be used as reference for further improvement of voice quality.

4.4.8.2 Impact Analysis
and Alarms +
Null
6 Abbreviations
7 References
5 Related Counters, KPI and Alarms
5.1 Related Counters
Table 5‑1 VoLTE related counters
SN Counter ID Counter Name

Number of Initial QCI1 E-RAB Successful
1 C373210200
Setup
Number of Initial QCI1 E-RAB Setup Failures
2 C373210201
due to ENB Admission Failure
3 C373210202
due to Uu interface Failure
4 C373210203
due to Security Failure
5 C373210204
due to Parameter Error
6 C373210205
due to Other Reason
Number of Additional QCI1 E-RAB
7 C373210254
Successful Setup
Number of Additional QCI1 E-RAB Setup
8 C373210255
Failures due to ENB Admission Failure
9 C373210256
Failures due to Uu interface Failure
10 C373210257
Failures due to Handover Trigger
11 C373210258
Failures due to Parameter Error
12 C373210259
Failures due to Other Reason
Number of QCI1 E-RAB Release by MME
13 C373210362
Normal Release
Number of QCI1 E-RAB Release by ENB
14 C373210372 Through E-RAB Release Procedure due to
Overload Control
Other Abnormal Reason
Cell Congestion
HO Fail
Radio Link Failure
Reestablish Fail
UserInactive
Shut Down or Reset Cell
Number of QCI1 E-RAB Release by
22 C373210512
Reestablish Failure inter eNB
Redirection
Number of Calls of a VoLTE User Using the
24 C374251970
AMR-NB Coding Scheme
SN Counter ID Counter Name
25 C374251971
AMR-WB Coding Scheme
::: >>
26 C374251972
EVS Coding Scheme
1 Introduction +
Number of Calls of a VoLTE User Using
27 C374251973 2 Feature Description +
Other Coding Schemes
28 C373210472 Number of E-RAB(QCI1) HO Incoming 3 Technical Principles +
Admission Request
29 C373210482 Number of E-RAB(QCI1) HO Incoming 4 Engineering Guide +
Admission Fail
30 C374500000 Number of Uplink QCI1 TBs Initially
Transmitted for NSA UEs in a Cell and Alarms +
31 C374500001 Number of Errored Uplink QCI1 TBs Initially 6 Abbreviations

Transmitted for NSA UEs in a Cell
32 C374500002 Number of Downlink QCI1 TBs Initially 7 References
Transmitted for NSA UEs in a Cell
33 C374500003 Number of Errored Downlink QCI1 TBs
Initially Transmitted for NSA UEs in a Cell
34 C374500004 Number of Uplink QCI1 HARQ FAIL TBs
Transmitted for NSA UEs
35 C374500005 Number of Downlink QCI1 HARQ FAIL TBs
Transmitted for NSA UEs
36 C374500006 Number of Downlink QCI1 TBs Initially
Transmitted for NSA UEs in a Cell Counted
by CQI
5.2 Related KPI
Table 5‑2 VoLTE related KPIs
SN FDD KPI TDD KPI KPI Name

1 P310504 P311118 E-RAB Drop Rate
2 P310563 P310563 QCI1 E-RAB Retainability
3 P310564 P310564 QCI2 E-RAB Retainability
4 P310640 P311043 DL PDCP SDU Discard Rate(QCI=1)
5 P310641 P311044 DL PDCP SDU Discard Rate(QCI=2)
6 DL PDCP SDU Air Interface Loss

P310649 P311034
Rate(QCI=1)
7 DL PDCP SDU Air Interface Loss
P310650 P311035
Rate(QCI=2)
8 P310658 P311025 UL PDCP SDU Loss rate(QCI=1)
9 P310659 P311026 UL PDCP SDU Loss rate(QCI=2)
10 Average DL PDCP SDU

P310667 P311052
Delay(QCI=1)
11 Average DL PDCP SDU
P310668 P311053
Delay(QCI=2)
12 E-RAB Setup Success Rate in
P311502 P311502
Cell,QCI=1
13 E-RAB Setup Success Rate in
P311503 P311503
Cell,QCI=2
14 Uplink Residual BLER of QCI1 TBs
P341144 P341144
for NSA UEs in a Cell
15 Downlink Residual BLER of QCI1
P341145 P341145
TBs for NSA UEs in a Cell
16 Average BLER of Uplink QCI1 TBs
P341146 P341146
Initially Transmitted for NSA UEs
17 Average BLER of Downlink QCI1
P341147 P341147 TBs Initially Transmitted for NSA
UEs
5.3 Related Alarms

None
6 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.
7 References
1. 3GPP TS, 36.101,"User Equipment (UE) radio transmission and reception"
2. 3GPP TS, 36.104,"Base Station (BS) radio transmission and reception"
3. 3GPP TS 36.300,"Overall description"
4. 3GPP TS 36.306,"User Equipment (UE) radio access capabilities"
5. 3GPP TS 36.321,"Medium Access Control (MAC) protocol specification"
6. 3GPP TS 36.331,"Radio Resource Control (RRC);Protocol specification"
7. LTE Intra-RAT Connected Mobility Feature Guide ::: >>
8. LTE MAC Scheduling Feature Guide
9. LTE Admission Control Feature Guide
1 Introduction +
10. LTE Congestion Control Feature Guide 2 Feature Description +

11. LTE CoMP Feature Guide 3 Technical Principles +
12. LTE VoLTE Enhancement Feature Guide

and Alarms +
6 Abbreviations
7 References

VoLTE Overview R22

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VoLTE Overview R22

Uploaded by

Copyright:

Available Formats

30/10/2023 15:00 LTE VoLTE Overview (ITRAN LR22)

LTE VoLTE Overview (ITRAN

5 Related Counters, KPI

Version Date Author Reviewer Notes

Li Kangkang 2 Feature Description +

5 Related Counters, KPI

5 Related Counters, KPI and Alarms

Figure 2‑1 Network Architecture of the LTE Voice Network

Table 1‑1 Text changes

SN Section Change Description

1.1.2 LR22 (2022-08-30)

1.2 Related Feature List and License Control

Table 1‑2 Related Feature List

No Feature ID Feature Name License Technical

1.3 Correlation with Other Features

Table 1‑3 Correlation with Other Features

Feature ID Feature Name Required Mutually Impacted

1.4 Differences between FDD and TDD

Table 1‑4 Differences Between TDD and FDD Functions

No. Function point FDD TDD Chapter

2.2 Feature Introduction

2.3 Feature Values

- Higher frequency spectrum efficiency

- Shorter access delay

- Better voice quality and user experience

2.4 System Architecture

2.4.1 Network Architecture

Figure 2‑1 Network Architecture of the LTE Voice Network

Table 2‑1 VoLTE function classification ::: >>

3.1 Basic Functions

3.1.1 Voice Coding Mode and Service Model

Voice coding mode

1. AMR-NB: 12.2kbit/s, 10.2kbit/s, 7.95kbit/s, 7.4kbit/s, 6.7kbit/s, 5.9kbit/s, 5.15kbit/s,

2. AMR-WB: 23.85kbit/s, 23.05kbit/s, 19.85kbit/s, 18.25kbit/s, 15.85kbit/s,

3.1.2 Voice Policy Selection

1. Dual standby terminal-based voice solution (SVLTE)

2. Circuit Switched Fallback (CSFB) solution

3. IMS-based VoLTE + eSRVCC solution

4. Other voice solution (VoIP)

Voice solution selection policies are as follows:

5 Related Counters, KPI

Table 3‑1 Parameter Description

IE Parameter Value Description

In the following scenarios, the VoLTE solution is not recommended:

2. Requirements of laws and regulations

3.1.3 Basic calling procedure of voice service

Packet Packet 1 Introduction +

Bearer Establishment Flow

The following figure shows the establishment flow of a VoLTE call.

Figure 3‑3 VoLTE Call Establishment Flow

3.1.4 Voice Service Dynamic Scheduling

3.1.5 Admission Control and Congestion Control

3.1.5.1 QoS Admission Control of VoLTE

Scenario VoLTE Scenario VoLTE

1 23.85kbps 0.5 3:4:3 150 1 VGA 30 1: 1 8

No. Parameter FDD Parameter TDD Parameter

3.1.5.3 Congestion Control

Table 3‑5 Parameters Related to Congestion Control

No. Parameter FDD Parameter TDD Parameter

3.1.6 Moblity Management

Refer to LTE VoLTE Mobility Feature Guide.

3.1.7 RLC PDU and Functions

Table 3‑6 Parameters Related to RLC PDU

No. Parameter FDD Parameter TDD Parameter