Professional Documents
Culture Documents
Lte Volte Solution
Lte Volte Solution
Contents
1 Introduction.................................................................................................................................... 4
1.1 Purpose and Scope ........................................................................................................................................... 4
1.1.1 Purpose.................................................................................................................................................... 4
1.1.2 Scope....................................................................................................................................................... 4
1.1.2 Scope
This document mainly provides guidelines for implementing the VoLTE solutions. Application guides of
related features are optional in this document.
2 Solution Overview
2.1 Scenario Analysis
Voice over LTE (VoLTE) is an IMS-based voice service on the LTE network. The IMS supports various
access and multimedia services and has become the standard architecture of EPC in the all-IP era. The
IMS-based VoLTE has been specified by 3GPP and Global System for Mobile Communications
Association (GSMA) as a standard voice solution for LTE networks.
VoLTE was first put into commercial use in South Korea in 2012. As an increasing number of UEs
support VoLTE and the IMS network is deployed, the second VoLTE deployment peak for commercial
use occurs in North America, Europe and Japan markets in 2015, and the third peak occurs in Australia,
Thailand, France, Turkey, and United Kingdom markets in 2016.
By the end of 2016, many telecom operators have released VoLTE for commercial use, and the
following provides some examples:
Turkcell, TT, and VDF in Turkey released VoLTE for commercial use in the end of June 2016.
SFR in France released VoLTE for commercial use in March 2016.
True and AIS in Thailand released VoLTE for commercial use in March 2016.
The Hong Kong branch of China Mobile released VoLTE for commercial use in September 2015.
D2 in Germany released VoLTE for commercial use in March 2015.
M1 in Singapore released VoLTE for commercial use in May 2015.
LG Uplus in Korea released VoLTE for commercial use in 2014.
PCCW in Hong Kong released VoLTE for commercial use on May 15, 2014.
T-Mobile in the USA released VoLTE in Seattle on May 22, 2014 before AT&T.
AT&T in the USA supports VoLTE services in Illinois, Indiana, Minnesota, and Wisconsin since
May 23, 2014.
SingTel in Singapore launched ClearVoice, the first full-function commercial VoLTE service in the
world, together with Ericsson and Samsung on May 31, 2014.
NTT DoCoMo in Japan announced that it launched VoLTE services in the second half of June
2014.
Verizon in the USA announced on May 21, 2014 that it will launch VoLTE in the next few months.
M1 and StarHub in Singapore claimed that they supported VoLTE services in the second half of
2014.
SBM in Japan claimed at the end of June 2014 that it will launch VoLTE services.
The deployment of VoLTE brings the following benefits to telecom operators:
VoLTE improves the spectral efficiency and reduces network costs. The spectral efficiency on LTE
networks is far higher than that on traditional GSM/UMTS networks. Provided with the same
bandwidth, an LTE cell has a voice capacity more than 100% larger than a UMTS cell.
VoLTE improves user experience. VoLTE uses high-definition broadband AMR voices, which
deliver a better auditory experience than narrowband AMR voices commonly used by GSM/UMTS
networks. The mean opinion score (MOS) for broadband AMR voices at a peak rate of 23.85 kbit/s
is 1 higher than the MOS for narrowband AMR voices at a peak rate of 12.2 kbit/s. In addition,
tests show that the call setup delay for VoLTE is reduced by more than 2/3 when compared with the
delay on GSM/UMTS networks.
Huawei classifies the VoLTE solutions as follows based on customer requirements:
Function Description
Speech codec and The calling and called UEs determine the speech codec scheme. The IMS is an
traffic model optional entity in this process. A common speech codec scheme is Adaptive Multirate
(AMR). For details about the VoLTE traffic model under AMR, see VoLTE Feature
Parameter Description.
VoLTE policy During the attach procedure, the UE negotiates with the MME and determines whether
selection to select VoLTE as the voice policy. For details about VoLTE policy selection, see
VoLTE Feature Parameter Description.
Radio bearer Radio bearers with QoS class identifiers (QCIs) of 1, 2, and 5 are set up between the
management calling and called UEs to carry conversational voice, signaling, and video,
respectively. For details about radio bearer management, see VoLTE Feature
Parameter Description.
Function Description
Admission and The eNodeB performs admission and congestion control for conversational voice
congestion control (QCI = 1), signaling (QCI = 5), and video (QCI = 2). For details about admission and
congestion control, see VoLTE Feature Parameter Description.
The admission and congestion control is a basic feature and is not under license
control.
Dynamic scheduling By default, the eNodeB performs dynamic scheduling and uses power control policies
and power control that are suitable for dynamic scheduling.
The following was introduced in eRAN12.0:
● The PUSCH RSRP upper limit is independently added for voice services. It is
equal to the PUSCH RSRP upper limit for data services plus an offset. The offset
is specified by CellPcAlgo.PuschRsrpHighThdOffsetVoIP. In heavy load
scenarios, the PUSCH transmit power of UEs running voice services in the cell
center and at a medium distance from the cell center increases, and the uplink
voice performance improves as well.
● During uplink VoLTE continuous scheduling, VoLTE UEs are continuously
scheduled in the uplink during talk spurts to reduce the uplink scheduling delay,
which decreases the uplink packet delay and delay variation for VoLTE services
and improves voice quality.
The following was introduced in eRAN13.0:
If interference is severe in the downlink or the PDCCH coverage is insufficient, the
function of scheduling in downlink control information (DCI) format 1A improves
PDCCH demodulation reliability. After this function is enabled, DCI format 1A is
used for downlink grant scheduling for rank 1 transmissions or for handovers of UEs
performing QCI 1 services in TM3 mode.
For details about dynamic scheduling and power control, see VoLTE Feature
Parameter Description.
Downlink TBS-based This function is an internal optimization introduced in eRAN7.0 and is not under
MCS selection license control.
In the downlink, the eNodeB selects a modulation and coding scheme (MCS) index
and resource blocks (RBs) for voice users. If a large number of padding bytes are
required after the selection, the eNodeB remains the number of RBs unchanged and
selects a smaller MCS index to reduce the number of padding bytes. This increases the
once-off transmission success rate for voice packets and decreases the number of
retransmissions. This function applies only to downlink voice services. This is because
the data packets for voice services have a relatively small and fixed size. It is
recommended that this function be enabled (with the VoipTbsBasedMcsSelSwitch
option of the CellAlgoSwitch.DlSchSwitch parameter selected).
This function is for commercial use at office L in country K.
UL HARQ MCS This function is an internal optimization introduced in eRAN7.0 and is not under
decrease optimization license control. If the user data fails to be transmitted for the first time, hybrid
DL HARQ MCS automatic repeat request (HARQ) retransmission is required. In the last two
decrease optimization retransmissions, the eNodeB selects a smaller MCS index (more RBs) to improve the
HARQ retransmission success rate and to decrease the residual block error rate
(BLER) and packet loss rate.
This function applies to both data and voice services. It can be used as a service
optimization function that applies to sites or cells with a high voice packet loss rate.
In eRAN7.0, this function is controlled by the following reserved parameters:
Function Description
eNBCellRsvdPara:RsvdSwPara1=RsvdSwPara1_bit6-1 for UL HARQ MCS
decrease optimization
eNBCellRsvdPara:RsvdSwPara0=RsvdSwPara0_bit27-1 for DL HARQ MCS
decrease optimization
Since eRAN8.0, this function is controlled by the following parameters:
● UlLast2RetransSchOptSwitch option of the UlSchSwitch parameter for UL
HARQ MCS decrease optimization
● DlRetxTbsIndexAdjOptSwitch option of the CqiAdjAlgoSwitch parameter for
DL HARQ MCS decrease optimization
In eRAN11.0, the UlVoipRblerControlSwitch option of the
CELLULSCHALGO.UlEnhencedVoipSchSw parameter is added for UL HARQ
MCS decrease optimization. This option helps improve the uplink coverage for voice
services in heavy load scenarios, thereby improving voice quality. When the number
of UEs in RRC_CONNECTED mode in a cell is greater than 150, the eNodeB selects
a smaller MCS index for the last two retransmissions of UEs performing
retransmissions, which decreases the uplink RBLER.
In eRAN12.0, the CELLULSCHALGO.UlVoLTERetransSchStrategy parameter is
added. If the FIRST_RETRANS_EXPN_RB_SWITCH option of this parameter is
selected, a smaller MCS index (more RBs) will be selected from the first uplink
HARQ retransmission onwards which is performed by VoLTE UEs with sufficient
power. This reduces the uplink retransmission delay and uplink RBLER, improving
the voice quality.
Voice preallocation This function is an internal optimization and is not under license control. It is used on
a large scale at office L in country K, and is recommended for enabling. This function
must be used together with the uplink preallocation function.
Uplink voice preallocation is introduced to reduce the delay of voice services. When
the number of UEs in a cell exceeds 50, the eNodeB preallocates 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 following parameters:
eRAN7.0: eNBCellRsvdPara: RsvdSwPara0=RsvdSwPara0_bit30-1
eRAN8.0: CellUlschAlgo: UlEnhencedVoipSchSw=UlVoipPreAllocationSwtich-1
Uplink compensation The uplink compensation scheduling is a basic function packed in eRAN8.1 and is
scheduling controlled by the UlVoipSchOptSwitch option of the
CellUlschAlgo.UlEnhencedVoipSchSw parameter. This function is supported in both
eRAN7.0 (V100R009C00SPC180) and eRAN8.0 and is controlled by the reserved
parameter eNBCellRsvdPara.RsvdSwPara1 bit20. This function is not under license
control in all these versions.
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 transmitted in time. In this
way, this feature shortens the waiting time of voice packets and reduces the number of
packets discarded due to the expiry of PDCP Discard Timer.
In eRAN11.0, the UlVoipServStateEnhancedSw option of the
CELLULSCHALGO.UlEnhencedVoipSchSw parameter is added for enhanced
determination of talk spurts and silent periods. Selecting this option shortens the talk
Function Description
spurt determination delay and decreases the probability of the voice service being
falsely determined as in the silent period. This further decreases the voice packet loss
rate caused by SR missing detection and improves the voice quality. In addition, the
CELLULSCHALGO.UlCompenSchPeriodinSpurt and
CELLULSCHALGO.UlCompenSchPeriodinSilence parameters are added for
configuring the minimum interval for compensation scheduling during the talk spurt
and silent period, respectively.
It is recommended that this function be enabled in the scenario where VoLTE services
are deployed.
UE power saving Discontinuous With DRX, UEs enter the sleep state when data is not transmitted,
reception (DRX) saving UE power.
In eRAN11.1, voice quality is improved as follows: relieving voice
packet loss (for UEs in DRX mode) due to status inconsistency
between the eNodeB and UEs which is caused by SR false detection;
relieving packet loss by increasing the probability that UEs enter the
active state under DRX.
For details, see DRX Feature Parameter Description.
Mobility Intra-frequency The eNodeB performs intra-frequency, inter-frequency, or inter-RAT
management handover handovers to transfer UEs performing voice services to appropriate
neighboring cells to maintain voice continuity. Handover policies for
Inter-frequency voice and data services differ.
handover
For details about how mobility management works for VoLTE, see
Inter-RAT VoLTE Feature Parameter Description and SRVCC Feature
handover Parameter Description.
2.2 Benefits
Basic VoLTE Solution
The basic VoLTE solution is a simple and efficient VoLTE service deployment solution that
guarantees basic VoLTE service experience. Other enhanced functions that require the support of
UEs are not involved in this solution because UE compatibility problems may occur at the initial
phase of VoLTE service deployment.
Enhanced VoLTE Solution
The enhanced VoLTE solution improves the VoLTE performance in terms of capacity, coverage,
UE power saving, and mobility management based on the basic VoLTE services. Some features
require UE support. UE compatibility test must be performed before you enable related features.
VoLTE VQM Solution
The VoLTE VQM solution monitors real-time VoLTE quality on the network side to provide
reference for timely network optimization, reducing the necessity of drive tests required for
obtaining voice quality.
2.3 General Solution
The following figure shows the maturity of the VoLTE features.
UE power
DRX
saving
Voice quality
monitoring and VQM E2E VQI EVS VQM
evaluation
For the SRVCC feature, only SRVCC with CS only is commercialized. ZainA beta test on SRVCC
with CS+PS has been performed in Zain Saudi Arabia. However, SRVCC with CS+PS is still not
mature and has not been commercially used.
Beta tests for ROHC and TTIB have been finished in Hong Kong. Therefore, these two features are
recommended for commercial use. However, the SPS feature is not recommended for commercial
use. If it is required at specific sites, contact the leader of the Feature Maturity Acceleration Team
Peng Hong (employee ID: 00302729).
The DRX feature has been put into commercial use for data services. The DRX deployment
policies for voice services are as follows:
− It is recommended that the DRX feature be disabled for voice services (QCI of 1). Enabling the
DRX feature will affect the VoLTE performance, such as prolonging the waiting time of uplink
voice packets and increasing the voice packet loss rate.
− If telecom operators or UE manufacturers (for example, Apple) insist that the DRX feature be
enabled to reduce battery consumption during voice calls, the following configurations are
recommended:
1. Scenario A: If downlink semi-persistent scheduling is enabled, the following parameter
settings for voice services (QCI of 1) are recommended: LongDRXCycle = 20ms;
OnDurationTimer = 10ms; InactiveTimer = 80ms; ReTransmissionTimer = 8ms;
SupportShortDrx = uu_Disable.
2. Scenario B: If downlink semi-persistent scheduling is disabled or telecom operators accept
that downlink semi-persistent scheduling does not take effect after being enabled, the
following parameter settings for voice services (QCI of 1) are recommended: LongDRXCycle
= 40ms; OnDurationTimer = 10; InActiveTimer = 80ms; ReTransmissionTimer = 8ms;
SupportShortDrx = uu_Disable.
The VQM and UL/DL HARQ MCS decrease optimization functions are not under license control.
They are being enabled at multiple sites in South Korea and Hong Kong.
The uplink delay-based dynamic scheduling is a trial feature introduced in eRAN7.0 and is packed
as the voice characteristic awareness scheduling feature in eRAN8.1. This feature applies to high
traffic volume scenarios where both data and voice services are performed.
The voice characteristic awareness scheduling and Voice Specific AMC features are newly packed
in eRAN8.1. Beta tests have been performed at site L in country K, and results show that specific
functions satisfy expectations and performance gains are specific to scenarios.
Contact the leader of the Feature Maturity Acceleration Team Peng Hong (employee ID: 00302729)
before putting into first commercial usage of the features on live networks for which beta tests
have not been performed and R&D assurance for the first commercial usage is required as
indicated in the solution feature maturity table.
QCI Resource Type Priority Delay Packet Loss Rate Typical Services
3.1.3.1 License
Admission and congestion control and uplink compensation scheduling are basic features and are
not under license control.
UL/DL HARQ MCS decrease optimization, voice preallocation, and TBS-based MCS selection are
internal optimizations and are not under license control.
3.1.3.2 UE
N/A
NOTE
When the ENodeBAlgoSwitch.EutranVoipSupportSwitch parameter is set to ON(On), dedicated bearer for
services with QCI of 1 can be set up for the eNodeB. When this parameter is set to OFF(Off), dedicated bearer
for services with QCI of 1 cannot be set up for the eNodeB.
The EutranVoipCapSwitch option of the eNodeBAlgoSwitch parameter is no longer used though the
configuration interface in this version supports delivery and synchronization of the setting of this parameter.
When deploying VoLTE services, do not configure or consider the value of the EutranVoipCapSwitch option.
3.1.5.1.7 Throughput
The following table describes the counters used to monitor the total and maximum UL/DL traffic
volumes, based on which you can calculate the average and maximum UL/DL throughput for voice
services.
SPS_SWITCH_OFF Description
(UeCompat.BlkLstCtrlSwitch)
After semi-persistent scheduling is enabled for VoLTE, the semi-persistent power on the PUSCH and
PDSCH can be adjusted by switches so that best voice performance can be achieved.
Deployment scenario: This feature applies to the scenario where the CCE usage of a cell exceeds 70%
and the number of concurrent online VoLTE users is greater than 10.
Deployment constraints
It is recommended that an interoperability test (IoT) be performed in the lab before the deployment.
This is because the semi-persistent scheduling feature requires the support of UEs.
Both the uplink semi-persistent scheduling feature and the uplink semi-persistent power control
feature must be enabled. Otherwise, the voice MOS will decrease.
The downlink semi-persistent power control feature must be disabled before the downlink
semi-persistent scheduling is enabled. For detailed reasons, see VoLTE Feature Parameter
Description.
If the DlSpsDrxDecouplingSwitch option is deselected, DRX is enabled for voice services, and
the long DRX cycle is greater than or equal to 20 ms in a cell, the downlink semi-persistent
scheduling feature cannot be activated even when the downlink semi-persistent scheduling switch
is turned on. Uplink semi-persistent scheduling is not under such a constraint.
This is because some UE chips (for example, Intel and Nvidia chips) cannot receive data through
the PDSCH during the silent period of DRX. In the uplink, UE can send data through the PUSCH
in the silent period of DRX, as specified by 3GPP specifications.
Negative impact
As specified in 3GPP specifications, the largest MCS index that can be used by semi-persistent
scheduling is 15. If a large number of voice users are in the cell center, the number of RBs will
decrease, which affects the throughput of data services in the cell.
Semi-persistent scheduling uses a fixed MCS and a fixed number of RBs, leading to poor link
adaptation performance. When the channel changes, the links cannot timely respond to the change,
which causes voice quality fluctuation. This is why emergency calls do not use semi-persistent
scheduling.
After downlink semi-persistent scheduling is enabled and voice services are set up, the eNodeB
reserves HARQ processes for downlink semi-persistent scheduling. Before the next initial
transmission in semi-persistent scheduling, the HARQ processes for downlink semi-persistent
scheduling may not be released. As a result, periodic data for semi-persistent scheduling cannot be
sent. The HARQ processes are reserved to avoid such situation. If the DlSpsRevHarqUseSwitch
option of the CellDlschAlgo.DlEnhancedVoipSchSw parameter is deselected, the HARQ
processes reserved for downlink semi-persistent scheduling cannot be used for dynamic scheduling
for other service types of the UE, such as data services. 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, when the volume of the data services is large (such as when the 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 only a few HARQ processes are required for data services. Uplink semi-persistent
scheduling uses non-adaptive HARQ retransmission, and therefore, is under no such restriction.
eRAN11.0 optimizes DS and SPS adaptive scheduling which can now be performed based on load. The
following table describes dynamic scheduling and semi-persistent scheduling for voice services.
With load-based scheduling, dynamic scheduling and semi-persistent scheduling can be adaptively
adopted based on load for UEs that newly initiate voice services.
When load is heavy, semi-persistent scheduling will be adopted to prevent overloaded PDCCHs
which may affect voice performance and capacity.
When load is light, dynamic scheduling will be adopted to provide better user experience of voice
services and improve spectral efficiency.
Uplink and downlink load-based scheduling can be enabled using the following switches:
For uplink load-based scheduling: UlVoIPLoadBasedSchSwitch of the
CellUlSchAlgo.UlEnhencedVoipSchSw parameter
For downlink load-based scheduling: DlVoIPLoadBasedSchSwitch of the
CellDlSchAlgo.DlEnhancedVoipSchSw parameter
NOTE
For details about the adaptive SRI period function, see Physical Channel Resource Management Feature Parameter
Description.
Deployment scenario: This feature applies to the scenario where VoLTE is deployed.
Deployment constraints: None
Negative impact: Independent configuration for voice inactivity timer has the following impacts on
networks after being enabled:
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 shorter, and the voice service drop rate decreases when there is no data transmission in
the uplink or downlink during the waiting for the callee to answer the call.
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 longer, the number of RRC connection requests decreases, the number of normal releases
decreases, and the voice service drop rate increases.
Smart recovery of AMR voice frames
This function was introduced in eRAN13.0 and is controlled by the AmrVoiceFrameSmartCoverySw
option of the CellUlschAlgo.UlEnhencedVoipSchSw parameter. After this option is selected, the
average MOS of AMR-WB voice service UEs with low scores increases, the uplink packet loss rate of
CEUs decreases, and the proportions of uplink VQIs being Poor and Bad decrease. This function does
not produce any negative gains.
Deployment scenario: VoLTE is deployed, and there are AMR-WB voice service UEs on the network.
Deployment constraints: None
Negative impact: None
3.2.2.1.5 ROHC
ROHC provides an efficient header compression mechanism for data packets. It is specially designed
for the radio links with high bit error rates (BERs) and with a long round trip time (RTT). ROHC helps
reduce header overhead, lower the packet loss rate, shorten the response time, and therefore helps
improve network performance.
ROHC is an extensible framework consisting of different profiles for data streams compliant with
different protocols. Profiles define the compression modes for streams with different types of protocol
headers. The profile ID identifies a profile. If the profile ID is 0x0000, the headers are not compressed.
The following table describes the mapping between the profile IDs and protocols. VoLTE services use
profiles 0x0001 and 0x0002.
Profile ID Protocol
0x0001 RTP/UDP/IP
Profile ID Protocol
0x0002 UDP/IP
0x0003 ESP/IP
0x0004 IP
The ROHC function entity in an LTE system is contained in the PDCP entity at the user plane of the UE
and eNodeB, which is used only for compressing and decompressing headers of packets on the user
plane. For DL services, the compressor is on the eNodeB side and the decompressor is on the UE side.
For UL services, the compressor is on the UE side and the decompressor is on the eNodeB side. The
compressor and the decompressor operate in three states and modes. In radio environments of different
qualities, the states and operating modes can be switched to ensure normal decompression of
compressed packets.
The compressor operates in three states, which are Initialization and Refresh (IR), First Order (FO), and
Second Order (SO). The volume of information carried by compressed data packets varies according to
the state in which the data packets are compressed. The IR state ranks the lowest. The compressor is in
this state when the static part of the context on the decompressor side is not established yet or the
decompression fails due to invalidity of the static part on the decompressor side. In this state, only
uncompressed data packets are sent. When the compressor detects some irregularities in the dynamic
fields of the context, the compressor enters the FO state and sends the compressed packets. The SO state
is the optimal compression state. In this state, the compressor sends the data packets with the maximum
compression rate. In most cases, the compressor is in this state. The compressor starts in the lowest
compression state (IR) and switches gradually to higher compression states (from FO to SO).
The decompressor operates in three states, which are No Context, Static Context, and Full Context. The
decompressor starts in the No Context state, in which the context is not established yet or unavailable on
the decompressor side. The decompressor enters the Static Context state when it finds that the dynamic
fields in context identifier (CID) are invalid. The decompressor enters the Full Context state after a
complete context is established. In this state, the decompressor can decompress the data packets with
the maximum compression ratio. The decompressor can switch to different states. The following figure
shows the state transition of the decompressor.
ROHC operates in three modes, which are Unidirectional Mode (U-Mode for short), Bi-directional
Optimistic Mode (O-Mode for short), and Bi-Directional Reliable Mode (R-Mode for short). The
reliability of these modes and resources used for transmitting feedback are different.
The initial operating mode of the compressor must be U-Mode, which then gradually switches to
O-Mode or R-Mode. The operating mode transition is determined by the decompressor. When the
eNodeB is the compressor, the UE works as the decompressor and instructs the eNodeB to change the
operating mode. When the eNodeB is the decompressor, it instructs the UE to change the operating
mode based on the configured parameter.
ROHC features high header compression efficiency. For example, it can compress a packet header into a
minimum of one byte. ROHC effectively reduces the size of VoLTE packets and the required RBs when
the eNodeB schedules VoLTE services. The common compression efficiency is 15%.
Deployment scenario: This feature applies to the scenario where VoLTE is deployed.
Deployment constraints: ROHC requires the support of UEs. If UEs do not support ROHC, this
function will not take effect.
Negative impact
UE compatibility issues may occur. The standards compliance between the UEs and eNodeB may
be different. This feature requires the support of UEs.
The average CPU usage increases after ROHC is enabled. The average CPU usage positively
correlates to the number of ROHC users. According to the test result, the average CPU usage
increases by 5% if there are 400 ROHC users. The average CPU usage increases by less than 1% if
there are less than 100 ROHC users.
For newly originated voice services, load-based scheduling allows the eNodeB to adaptively select
dynamic or semi-persistent scheduling based on service load in both uplink and downlink.
When the load is high, the eNodeB applies semi-persistent scheduling to avoid PDCCH overload
and the impact on voice quality and capacity.
When the load is low, the eNodeB applies dynamic scheduling to provide better experience on
voice services and improve spectral efficiency.
The load is determined based on the number of users scheduled in each TTI.
Deployment scenario: It is recommended that an IoT be performed. This is because the ROHC feature
requires the support of UEs.
Deployment constraints: This feature applies to the scenario where VoLTE is deployed and
semi-persistent scheduling is enabled.
Negative impact: None
3.2.2.1.7 VoLTE User Prior Access
The VoLTE mobile originated (MO) service preferential access function on a heavy-load network is
controlled by the VoLTEMoPrefSwitch option of the CellAlgoSwitch.VoLTESwitch parameter.
The eNodeB identifies a VoLTE calling user based on the cause value contained in the RRC Connection
Request message.
After identifying a VoLTE calling user, the eNodeB performs the following optimization to increase the
call setup success rate and improve VoLTE user experience:
Preallocation
The eNodeB performs preallocation after the Msg4 transmission regardless of the threshold of the
user number for preallocation activation.
DRX
The DRX feature does not take effect on the default bearer of an identified voice user. This
eliminates the impact of sleep time on the SIP message carried on the QCI 5 bearer and increases
scheduling chances of the SIP message. The DRX feature does not take effect until the QCI 1
bearer is set up.
Admission and congestion control
The eNodeB increases the ARP of an identified VoLTE user. In this way, the VoLTE user can
preempt the resources of low-ARP users when the user number specification is limited.
CA
The eNodeB reduces the probability of performing CA on identified VoLTE users.
Flow control
The eNodeB prioritizes identified VoLTE users in flow control for the Initial Access Request
Control messages.
Preallocation, DRX, CA, and flow control are optimized by default. Optimization on admission and
congestion control is controlled by the CellRacThd.VolteArpOverride parameter.
Deployment scenario: This feature applies to the scenario where VoLTE is deployed and the cell
capacity in terms of the number of users is limited.
Deployment constraints: There are VoLTE UEs that support 3GPP Release 12 on the network.
Essentially, the RRC Connection Request Message sent by the UEs can contain the
mo-VoiceCall-v1280 cause value.
Negative impact: If the cell capacity in terms of the number of users is limited, the identified VoLTE
UEs can preempt the resources of low-ARP UEs, increasing the call drop rate of low-ARP UEs whose
resources are preempted by VoLTE UEs. Preallocation may increase the uplink RB resource usage on
the PUSCH.
Related features: See the "Related Features" chapter in VoLTE Feature Parameter Description.
3.2.2.2.1 License
The following table lists the optional features.
Basic feature: LBFD-081105 Voice-Specific AMC is a basic feature and is not under license control.
3.2.2.2.2 UE
UEs require semi-persistent scheduling and ROHC capabilities.
The following table describes the counters used to observe the running status of the ROHC feature.
The following table describes the counters used to observe the running status of the VoLTE MO service
preferential access function. For detailed observation methods, see VoLTE Feature Parameter
Description.
The following table describes counters used to observe the running status of smart recovery of AMR
voice frames. For detailed observation methods, see VoLTE Feature Parameter Description.
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 parameter.
When the measured SINR is greater than the sum of the CellTtiBundlingAlgo.SinrThdToTrigTtib and
CellUlschAlgo.HystToExitTtiBundling parameter values 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 only when the UE meets the exit conditions,
experiences handover or service drop, or needs to reestablish a new connection.
eRAN11.1 introduces the CellTtiBundlingAlgo.SinrThdToTrigTtib parameter to configure the SINR
threshold when TTI bundling is enabled for a UE. If this parameter is set to 255, the SINR threshold
will be dynamically calculated.
In eRAN12.0, the CellUlschAlgo.TtiBundlingRetxStrategy parameter is added. If the
RetxFssSchSwitch option of this parameter is selected, frequency selective scheduling can be
performed on retransmissions of UEs in TTI bundling states, that is, adaptive retransmissions. In this
scenario, frequency selective scheduling gains are produced, and uplink voice quality improves.
In eRAN12.1, during a handover or RRC connection reestablishment, the UE inherits the TTI bundling
state from the source cell. Essentially, if a UE is in the TTI bundling state before a handover or RRC
connection reestablishment, the UE enters the TTI bundling state after the handover or RRC connection
reestablishment without another TTI bundling determination. In this way, reconfiguration signaling
reduces and the impact of re-entering the TTI bundling state on voice quality is avoided during
handovers or RRC connection reestablishments.
eRAN12.1 supports R12 TTI Bundling. When TTI bundling is enabled, the modulation scheme must be
QPSK but there is no restriction on the PRB resource allocation size, increasing the flexibility of
resource allocation for TTI bundling. The new HARQ feedback time sequence and the number of
simultaneous uplink HARQ processes is changed from four to three.
3.2.3.1.2 ROHC
ROHC compresses the RTP, UDP, and IP headers in voice packets to reduce the size of the entire voice
packets. This lowers the requirements on cell-edge data rate, and therefore improves cell coverage. In
addition, ROHC reduces the number of voice packet segments to reduce header overheads and increases
the once-off transmission success rate for voice packets, which improves cell coverage for voice
services.
For details about the principles, see the ROHC-related information in section 3.2.2 "Application of
Capacity Enhancement."
Table 3-2 Value of eNodeB-specific timer for reordering at the receiver in AM/UM for each bearer in the
non-TTI bundling state
8 60 ms
Table 3-3 Value of eNodeB-specific timer for reordering at the receiver in AM/UM for each bearer in the
TTI bundling state.
N24 80 ms
N28 95 ms
This feature applies to scenarios where uplink coverage is limited (in suburban or rural areas, or when
outdoor sites cover indoor areas).
Details are as follows:
There are a certain number of UEs performing voice services.
L.Traffic.User.VoIP.Avg/L.Traffic.User.Avg > 5%
The percentage of packets from CEUs reaches a specified threshold.
L.Traffic.UL.FarUE.PktLoss.Tot.QCI.1/L.Traffic.UL.PktLoss.Tot.QCI.1 > 5%
The uplink voice packet loss rate of CEUs exceeds a specified threshold.
L.Traffic.UL.FarUE.PktLoss.Loss.QCI.1/L.Traffic.UL.FarUE.PktLoss.Tot.QCI.1 > 2%
Deployment scenario: This feature applies to the scenario where VoLTE is deployed.
Deployment constraints: None
Negative impact: This feature increases the uplink scheduling delay over the air interface for voice
packets to achieve specific gains, which increases the E2E delay of voice packets as a result.
Related features: See the "Related Features" chapter in VoLTE Feature Parameter Description.
3.2.3.2.1 License
Feature ID Feature Name License Control Item NE Sales Unit
LOFD-001048 TTI Bundling TTI Bundling (FDD) eNodeB per cell
LOFD-001017 RObust Header RObust Header Compression eNodeB per RRC
Compression (ROHC) (ROHC) (FDD) connected user
LOFD-111207 VoLTE Rate Control VoLTE Rate Control (FDD) eNodeB per cell
LOFD-120204 VoLTE Coverage VoLTE Coverage eNodeB per cell
Enhancement Based on Enhancement Based on
Extended Delay Budget Extended Delay Budget(FDD)
LEOFD-121202 EVS Rate Control EVS Rate Control(FDD) eNodeB per Cell
3.2.3.2.2 UE
UEs support the TTI bundling and ROHC capabilities.
3.2.3.2.3 Configurable Parameters
Parameter Parameter ID Description Setting Notes
Name
Uplink CellAlgoSwitch.UlSchSwit The TtiBundlingSwitch The recommendation will be
schedule switch ch option in this parameter provided after the beta test.
indicates whether to enable Before the beta test, you are
TTI bundling. advised to deselect this option.
Max Number CellUlschAlgo.UlVoipRlc Indicates whether to apply ● If this parameter is set to 0,
of UL RLC MaxSegNum upper limit control on the upper limit control on
Segments for service data unit (SDU) SDU segmentation at the
VoIP segmentation at the RLC RLC layer is disabled in
layer in the uplink for the uplink for VoLTE
VoLTE services scheduled services scheduled in
in non-TTI bundling mode non-TTI bundling mode.
and the maximum SDU
● If this parameter is set to a
segments at the RLC layer.
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 VoLTE
services in uplink dynamic
scheduling in non-TTI
bundling mode.
The recommended value is 20.
TTI Bundling CellUlschAlgo.TtiBundlin Indicates the TTI bundling The default value is
Trigger gTriggerStrategy triggering policy. SERVICE_VOIP(SERVICE
Strategy ● If TTI bundling applies to _VOIP). Set this parameter to
SERVICE_MULTIAPP(SER
only VoLTE services, set
VICE_MULTIAPP) only
this parameter to
when telecom operators
SERVICE_VOIP(SER
require that the TTI bundling
VICE_VOIP).
apply to only VoLTE service
● If TTI bundling applies to and a combination of VoLTE
only VoLTE service and and data services.
a combination of VoLTE
and data services, set this
parameter to
SERVICE_MULTIAPP
(SERVICE_MULTIAP
P).
Statistic Num CellUlschAlgo.StatisticNu Indicates a threshold number You are advised to set this
Threshold for mThdForTtibTrig of consecutive times that the parameter to the default value
TTIB Trigger measured SINR is less than 10.
the target SINR. When the
actual number reaches this
threshold number, the
eNodeB instructs the UE to
enter the TTI bundling state.
Parameter Parameter ID Description Setting Notes
Name
Statistic Num CellUlschAlgo.StatisticNu Indicates a threshold number You are advised to set this
Threshold for mThdForTtibExit of consecutive times that the parameter to the default value
TTIB Exit measured SINR is greater 10.
than the sum of the
CellTtiBundlingAlgo.SinrT
hdToTrigTtib and
CellUlschAlgo.HystToExitT
tiBundling parameter values.
When the actual number
reaches this threshold
number, the eNodeB
instructs the UE to exit the
TTI bundling state.
Hysteresis to CellUlschAlgo.HystToExit Indicates an SINR threshold You are advised to set this
Exit TTI TtiBundling for exiting the TTI bundling parameter to the default value
Bundling state. This threshold is equal 5dB.
to the sum of the SINR
threshold for entering the
TTI bundling state and the
CellUlschAlgo.HystToExitT
tiBundling parameter value.
TTIB Max CellUlschAlgo.TtiBundlin Indicates the maximum You are advised to set this
Number of gRlcMaxSegNum number of RLC segments for parameter to the default value
RLC Segments UEs in the TTI bundling 4.
state.
TTIB Max CellUlschAlgo.TtiBundlin Indicates the maximum You are advised to set this
Number of gHarqMaxTxNum number of HARQ parameter to the default value
HARQ transmission times for UEs 16.
Transmissions in the TTI bundling state. Note that the value of this
parameter must be an integer
multiple of 4.
SINR SinrThdToTrigTtib Indicates the configuration You are advised to set this
Threshold To policy and value of the SINR parameter to the default value
Trigger TTI threshold when TTI bundling 255.
Bundling is enabled for a UE. If this
parameter is set to 255, the
SINR threshold
configuration policy is
"dynamic calculation",
indicating that the SINR
threshold is dynamically
calculated based on the voice
packet size and channel
quality. If this parameter is
set to a value other than 255,
the SINR threshold
configuration policy is
"manual configuration",
indicating that the SINR
Parameter Parameter ID Description Setting Notes
Name
threshold is manually
configured on the GUI. This
parameter applies only to
LTE FDD.
Uplink Rate CellAlgoSwitch.UlAmrcM Indicates the uplink voice You are advised to determine
Control Mode ode rate control mode of a cell. whether to enable AMR or
● If this parameter is set to EVS rate control and whether
to use the eNodeB or SBC for
ULRATECTRL_OFF,
AMR or EVS rate control
uplink voice AMR
based on live network
control does not take
conditions.
effect.
● If this parameter is set to
ULAMRC_ENB_CON
TROL, the eNodeB
executes uplink voice
AMR control (AMR-NB
and AMR-WB).
● If this parameter is set to
ULAMRC_SBC_CONT
ROL, the eNodeB
triggers the SBC on the
EPC to execute uplink
voice AMR control
(AMR-NB and
AMR-WB). The SBC
must be a Huawei SBC
supporting uplink voice
AMR control.
● If this parameter is set to
ULEVSC_ENB_CONT
ROL, the eNodeB
adjusts the uplink
EVS-SWB rate for
VoLTE services.
● If this parameter is set to
ADAPTIVE_ENB_CO
NTROL, the eNodeB
adaptively adjusts the
uplink AMR or EVS rate
for VoLTE services.
Uplink Rate CellOp.UlAmrcMode Indicates the uplink voice You are advised to configure
Control Mode rate control mode for an this parameter based on
operator. cell-level uplink rate control
● If this parameter is set to settings and operators'
policies.
INVALID, it is
considered that this
parameter has not been
configured.
Parameter Parameter ID Description Setting Notes
Name
● If this parameter is set to
ULRATECTRL_OFF,
Rate control features are
disabled.
● If this parameter is set to
ULAMRC_ENB_CON
TROL, the eNodeB
adjusts the uplink
AMR-NB/AMR-WB rate
for voice services.
● If this parameter is set to
ULAMRC_SBC_CONT
ROL, the eNodeB
triggers the SBC on the
EPC to adjust the uplink
AMR-NB/AMR-WB rate
for voice services. The
SBC must be a Huawei
SBC that supports AMR
Rate Control.
● If this parameter is set to
ULEVSC_ENB_CONT
ROL, the eNodeB
adjusts the uplink EVS
rate for voice services.
● If this parameter is set to
ADAPTIVE_ENB_CO
NTROL, the eNodeB
adaptively adjusts the
uplink AMR or EVS rate
for voice services.
Black List UeCompatOpt. UL_AMRC_SWITCH_OF If abnormal UEs do not
Control Switch BlkLstCtrlSwitch F: Indicates whether to support AMR rate adjustment
disable uplink AMRC for or IOT tests have detected
defective UEs. Uplink AMR or EVS rate adjustment
AMRC is disabled for exceptions, you are advised to
defective UEs only if this disable AMR rate adjustment
option is selected. for this type of UEs.
UL_EVSC_SWITCH_OFF
: Indicates whether to disable
uplink EVSC for defective
UEs. Uplink EVSC is
disabled for defective UEs
only if this option is selected.
White List UeCompatOpt. UL_AMRC_SWITCH_ON You are advised to select this
Control Switch WhiteLstCtrlSwitch : Indicates whether to enable option for whitelisted UEs.
the function of uplink
AMRC for specified UEs.
This function is enabled only
Parameter Parameter ID Description Setting Notes
Name
if this option is selected.
UL_EVSC_SWITCH_ON:
Indicates whether to enable
the function of uplink EVSC
for specified UEs. This
function is enabled only if
this option is selected.
Rate Control CellAlgoSwitch.AmrcAlgo UlAmrcExceedingInitialSw You are advised to select this
Algorithm Switch : option to obtain better voice
Switch ● If this option is selected, quality by allowing the
increased coding rate to
the increased coding rate
exceed the initial coding rate
can exceed the initial
of this call.
coding rate of this call.
If PDCCH resources are
● If this option is
insufficient, you are advised to
deselected, the increased deselect this option.
coding rate cannot exceed
the initial coding rate of To prevent a data rate that a
this call. UE does not support after
adjustment by considering UE
UlEvsExceedingInitialSw: compatibility, you are advised
● If this option is selected, to select the UlAmrCheckSw
the adjusted coding rate option.
can exceed the initial If the voice traffic model on
coding rate of this call. the live network needs to be
● If this option is evaluated and distribution
changes in voice coding
deselected, the adjusted
modes need to be observed,
coding rate cannot exceed
you are advised to select the
the initial coding rate of
VoiceCodingModeMeasSw
this call.
option.
UlAmrCheckSw: If network capacity is
● If this option is selected, insufficient or a large number
the uplink AMR speech of UEs perform voice service,
coding rate cannot be you are advised to select the
adjusted before the VoLTELoadAmrcSw option.
eNodeB obtains the rate In other scenarios, you are
set information about this advised not to select this
session. option.
● If this option is
deselected, the uplink
AMR speech coding rate
can be adjusted before the
eNodeB obtains the rate
set information about this
session.
It is recommended that this
option be selected.
Parameter Parameter ID Description Setting Notes
Name
VoiceCodingModeMeasSw:
● If this option is selected,
the eNodeB measures
counters related to voice
coding mode distribution.
● If this option is
deselected, the eNodeB
does not measure the
counters.
VoLTELoadAmrcSw
● If this option is selected,
voice-load-based
AMRC/EVS rate control
is enabled.
● If this option is
deselected,
voice-load-based
AMRC/EVS rate control
is disabled.
High Rate VoiceAmrControl. Indicates the high rate You are advised to configure
Coding Mode HighAmrCodingMode coding mode for the this parameter as required, and
corresponding parameter the default value is
group ID. This parameter is recommended.
used to configure the high
rate coding mode for the
corresponding parameter
group ID.
Low Rate VoiceAmrControl. Indicates the low rate coding You are advised to configure
Coding Mode LowAmrCodingMode mode for the corresponding this parameter as required, and
parameter group ID. This the default value is
parameter is used to recommended.
configure the low rate coding
mode for the corresponding
parameter group ID.
Packet Loss VoiceAmrControl. Indicates the threshold of the You are advised to set this
Rate Thd for PlrThdForDecreasingAmr packet loss rate for reducing parameter to the default value.
Decreasing the data rate of uplink voice
services when a specified
parameter group ID is used.
If the uplink QCI 1 packet
loss rate is greater than the
threshold and the TBS meets
the rate reduction conditions,
rate reduction is triggered.
Packet Loss VoiceAmrControl. Indicates the threshold of the You are advised to set this
Rate Thd for PlrThdForIncreasingAmr packet loss rate for parameter to the default value.
increasing the data rate of
Parameter Parameter ID Description Setting Notes
Name
Increasing uplink voice services when a
specified parameter group ID
is used. If the uplink QCI 1
packet loss rate is less than
the threshold and the TBS
meets the rate increase
conditions, the rate
increases.
RLC Segment VoiceAmrControl. Indicates the threshold of the You are advised to set this
Num Thd for RsnThdForDecreasingAmr number of RLC segments for parameter to the default value.
Decreasing reducing the data rate of
uplink voice services when a
specified parameter group ID
is used. This parameter is
used to calculate the TBS
threshold for reducing the
data rate of uplink voice
services. If this parameter is
set to 0, only the uplink QCI
1 packet loss rate is used to
determine whether to reduce
the data rate of uplink voice
services, not the number of
RLC segments.
RLC Segment VoiceAmrControl. Indicates the threshold of the You are advised to set this
Num Thd for RsnThdForIncreasingAmr number of RLC segments for parameter to the default value.
Increasing increasing the data rate of
uplink voice services when a
specified parameter group ID
is used. This parameter is
used to calculate the TBS
threshold for increasing the
data rate of uplink voice
services.
UL RB Usage CellRacThd.UlRbThdforV Indicates the threshold of You are advised to set this
Thld for olteLoadAmrc uplink RB usage for parameter to the default value.
VoLTE Load voice-load-based rate control
Rate Control when the
VoLTELoadAmrcSw
option of the
CellAlgoSwitch.AmrcAlgoS
witch parameter is selected.
CCE Usage CellRacThd.CceThdforVol Indicates the threshold of You are advised to set this
Thld for teLoadAmrc CCE usage for parameter to the default value.
VoLTE Load voice-load-based rate control
Rate Control when the
VoLTELoadAmrcSw
option of the
CellAlgoSwitch.AmrcAlgoS
Parameter Parameter ID Description Setting Notes
Name
witch parameter is selected.
AMRC CellUlSchAlgo.AmrcDecre Indicates the period during You are advised to set this
Decreasing asingPeriod which the eNodeB parameter to the default value.
Period determines whether to
perform AMRC-based rate
reduction. During this
period, if the uplink QCI 1
packet loss rate and the TBS
meet the conditions for
AMRC-based rate reduction,
the eNodeB triggers
AMRC-based rate reduction.
Rate Control CellUlSchAlgo.RateCtrlC Indicates whether the local You are advised to set this
CMR Process mrProcessStrategy end performs rate adjustment parameter to the default value.
Strategy when the eNodeB detects
that other NEs perform rate
adjustment.
● When this parameter is
set to
BASIC_STRATEGY,
the local end does not
perform rate adjustment
if the eNodeB detects that
other NEs perform rate
adjustment.
● When this parameter is
set to
ADAPTIVE_STRATEG
Y, the local end performs
rate adjustment if the
eNodeB detects that other
NEs perform rate
adjustment. However, the
target adjusted rate must
be lower than or equal to
the expected adjusted rate
of other NEs.
Rate Control CellUlschAlgo.RateCtrlRs Indicates the threshold for You are advised to set this
Response pDecisionThld determining whether a UE parameter to the default value.
Decision has responded to a rate
Threshold adjustment request. The
eNodeB determines whether
a UE has successfully
responded to a rate
adjustment request if the UE
responds before the number
of uplink voice packets
received by the eNodeB
exceeds this threshold.
Parameter Parameter ID Description Setting Notes
Name
TTI Bundling CellUlschAlgo.TtiBundlin RetxFssSchSwitch: Indicates This option is deselected by
UE gRetxStrategy whether to apply frequency default.
Retransmission selective scheduling to You are advised to select this
Strategy inter-bundle retransmissions option in cells where TTI
for UEs in the TTI bundling bundling is enabled to improve
state. When this option is uplink voice quality.
deselected, frequency
selective scheduling does not
take effect for
retransmissions. When this
option is selected, the
eNodeB determines whether
to apply frequency selective
scheduling to
retransmissions for UEs in
the TTI bundling state based
on the frequency selective
status.
R12 TTI CellTtiBundlingAlgo.R12T Indicates whether to enable The default and recommended
Bundling tiBundlingSwitch R12 TTI bundling. If this value is OFF(Off).
Switch parameter is set to ON, R12
TTI bundling works for UEs
that support this function. If
this parameter is set to OFF,
R12 TTI bundling cannot
take effect on these UEs.
This parameter applies only
to LTE FDD.
R12 TTI R12TtiBHarqMaxTxNum Indicates the maximum The default and recommended
Bundling number of uplink HARQ value is n20(20).
HARQ Max transmissions in the TTI
Trans Num bundling state from a UE
capable of R12 TTI
bundling. For details, see
3GPP TS 36.331. This
parameter applies only to
LTE FDD.
SINR SinrThdToTrigR12TtiB Indicates the SINR threshold The default and recommended
Threshold To used to trigger R12 TTI value is 3.
Trigger R12 bundling for UEs capable of
TTI Bundling R12 TTI bundling. This
parameter applies only to
LTE FDD.
TTI Bundling CellTtiBundlingAlgo.TtiB TTIBUNDLING_ALGO_E This option is deselected by
Algorithm undlingAlgoSw NHANCE_SW: If this default.
Switch option is selected, UEs You are advised to deselect
inherit the TTI bundling state this option.
from the source cell during
handovers and RRC
Parameter Parameter ID Description Setting Notes
Name
connection reestablishments,
and the restriction that the
MCS index must be less than
or equal to 10 is removed.
Delta Offset DeltaOffsetAckIndexForTt Indicates the index mapped The default value is 9.
Acknowledge iB to the MCS offset for The recommended value is 11
Index for TTI acknowledgments (ACKs) when TTI bundling is enabled.
Bundling transmitted with data on
PUSCH. When this
parameter is set to a reserved
value, UEs initiate RRC
connection reestablishments
or fail to access the network.
This parameter applies only
to UEs in the TTI bundling
state. This parameter applies
only to LTE FDD and LTE
TDD.
Uplink CELLULSCHALGO.UlEn UlVoipCrosslayerOptSwitch This option is deselected by
Enhanced VoIP hencedVoipSchSw : When this option is default.
Schedule selected, the configurations You are advised to select this
Switch of the following parameters option when the uplink
sent from the eNodeB to coverage is limited to improve
VoLTE UEs using QCI 1 are uplink voice quality.
invalid: DiscardTimer,
UlHarqMaxTxNum,
TtiBundlingHarqMaxTxN
um,
ENodeBAmReorderingTim
er, and
ENodeBUmReorderingTim
er. The actual values of these
parameters are determined
by the eNodeB. Then, based
on the traffic volume to be
scheduled for VoLTE
services, the eNodeB selects
an optimal MCS, and
allocates an optimal number
of RBs to such services. In
this way, the uplink VoIP
packet loss rate decreases,
and the voice quality
improves.
Max Number CellUlSchAlgo. Indicates whether to enable The recommended value is 23
of UL RLC UlVoipRlcMaxSegNum upper limit control on when
Segments for service data unit (SDU) UlVoipCrosslayerOptSwitch
VoIP segmentation at the radio is selected and 20 when
link control (RLC) layer in UlVoipCrosslayerOptSwitch
the uplink for VoLTE is deselected.
Parameter Parameter ID Description Setting Notes
Name
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 VoLTE 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 an SDU
can be divided into a
maximum of X segments for
VoLTE services in uplink
dynamic scheduling in
non-TTI bundling mode.
TTIB Max CellUlSchAlgo. Indicates the maximum The recommended value is 5
Number of TtiBundlingRlcMaxSegNu number of RLC segments in when
RLC Segments m the uplink when UEs are in UlVoipCrosslayerOptSwitch
the TTI bundling state. is selected and 4 when
UlVoipCrosslayerOptSwitch
is deselected.
The following table describes the counters used to observe the running status of the ROHC feature.
There is no counter used to monitor the UL RLC segmentation enhancement feature. For detailed
observation methods, see VoLTE Feature Parameter Description.
The following table describes the counters used to observe the running status of the VoLTE Rate Control
feature.
There is no counter used to monitor the VoLTE Coverage Enhancement Based on Extended Delay
Budget feature. For detailed observation methods, see VoLTE Feature Parameter Description.
3.2.4.2.1 License
N/A
3.2.4.2.2 UE
N/A
3.2.5.2.1 License
Feature ID Feature Name License Control Item NE Sales Unit
LOFD-001019 PS Inter-RAT Mobility PS Inter-RAT Mobility eNodeB per RRC
between E-UTRAN and between E-UTRAN and connected user
UTRAN UTRAN
LOFD-001043 Service based inter-RAT Service based inter-RAT eNodeB per RRC
handover to UTRAN handover to UTRAN connected user
LOFD-001072 Distance based Inter-RAT Distance based Inter-RAT eNodeB per RRC
handover to UTRAN handover to UTRAN connected user
LOFD-001078 E-UTRAN to UTRAN E-UTRAN to UTRAN eNodeB per RRC
CS/PS Steering CS/PS Steering connected user
LOFD-001022 SRVCC to UTRAN SRVCC to UTRAN eNodeB per RRC
connected user
LOFD-001087 SRVCC Flexible Steering SRVCC Flexible Steering eNodeB per RRC
to UTRAN to UTRAN connected user
LOFD-001023 SRVCC to GERAN SRVCC to GERAN eNodeB per RRC
Feature ID Feature Name License Control Item NE Sales Unit
connected user
3.2.5.2.2 UE
Inter-RAT handover requires that UEs support inter-RAT measurement and handover capabilities.
3.2.6.2.1 License
VoLTE User Prior Access
LOFD-121202 VoLTE User Prior VoLTE User Prior eNodeB per Cell
Access Access
3.3.3.1 License
None
3.3.3.2 UE
N/A
NOTE
VoLTE MOS is affected by SINR. When SINR is less than -3 dB, the MOS decreases significantly. Transcoder Free
Operation (TrFO) is not enabled on the UMTS network at office P. Therefore, the MOS is relatively low. In the
preceding table, L2L refers to an LTE-to-LTE call and L2U refers to an LTE-to-UMTS call.
Access delay
RSRP 23.05K 12.65K 23.05K 12.65K 12.65K 12.65K 12.65K
LTE-LTE LTE-LTE LTE-LTE LTE-LTE LTE-3G LTE-3G 3G-3G
(CONNECT) (CONNECT) (IDLE) (IDLE) CONNECT IDLE
-80 dBm 632 643 1651 1669 3914 3925 5786
-90 dBm 636 641 1653 1663 3906 4049 5938
-100 dBm 638 675 1681 1677 3931 4233 6020
-110 dBm 676 714 1821 1736 3974 4295 6034
-120 dBm 825 785 2168 2413 4962 7454 11038
NOTE
The call setup delay is similar in an LTE-to-LTE call where different speech coding rates are used. If the radio
coverage is weak, data packets are more likely to be retransmitted and the call setup delay may increase. The call
setup delay for UEs in idle mode may fluctuate due to the impact from the paging period (1.28s).
From the perspective of the eNodeB, a VoLTE-to-VoLTE call setup procedure is divided into RRC
connection setup over the air interface and the setup of bearers with QCIs of 1 and 5.
QoS control is performed on the dedicated VoLTE bearer based on the dynamic PCC rule. The
following shows the QoS control procedure.
Step 1 The IMS (P-CSCF) sends the QCI information to the PCRF over the Rx interface.
Step 2 The PCRF generates QoS rules based on the QoS parameters for VoLTE and the user subscription
information. Then, the PCRF sends the QoS rules to the P-GW over the Gx interface. The key QoS
parameters include QCI, allocation/retention priority (ARP), GBR, and maximum bit rate (MBR).
Step 3 The P-GW instructs the S-GW, MME, eNodeB to set up bearers in the EPS based on the QoS rules sent
from the PCRF. Different services are carried on bearers with different QCIs according to the QoS
requirement, as shown in the following table (specified in 3GPP TS 23.203).
----End
The VoLTE service states can be divided into talk spurts and silent period
Talk spurts occur when the user is talking. In this state, voice packets are transmitted at an interval
of 20 ms, and the packet size is determined by the speech coding rate.
Silent periods occur when the user is listening. In this state, an SID frame is sent at an interval of
160 ms to improve user experience.
AMR is classified into AMR-WB and AMR-NB. AMR is widely used in the GERAN and UTRAN and
is also applicable to VoLTE. AMR-WB is a new speech codec introduced in 3GPP Release 5. AMR-WB
requires that voices are sampled at a rate of 16 kHz. According to the Nyquist sampling theorem, the
sampling rate must be greater than or equal to twice of the maximum frequency of the sampled signal.
Otherwise, the original signal cannot be restored. If a sampling rate of 16 kHz is used, the voice signal
whose frequency is less than 8 kHz can be restored.
The following lists the common sampling rate in the digital audio field:
8,000 Hz: Sampling rate for phone calls, which is sufficient for human voices.
11,025 Hz/22,050 Hz: Sampling rates for radio broadcasting.
32,000 Hz: Sampling rates for miniDV digital video, camcorder, and digital audio tape (DAT) in
LP mode.
44,100 Hz: Sampling rate for audio CD, MPEG-1 audios (including VCD, SVCD, and MP3).
47,250 Hz: Sampling rate for the world's first commercial PCM recorder developed by Nippon
Columbia (Denon).
48,000 Hz: Sampling rate for the digital voice of miniDV, digital TV, DVD, DAT, movie and
professional audio.
50,000 Hz: Sampling rate for the world' first commercial digital recorder jointly developed by 3M
and Soundstream in the late 1970s.
50,400 Hz: Sampling rate for Mitsubishi X-80 digital recorder.
96,000 Hz/192,000 Hz: Sampling rates for DVD-Audio and the audio tracks of some LPCM DVDs,
BD-ROMs (Blu-ray Discs), and high definition DVDs (HD-DVDs).
2.8224 MHz: Sampling rate for the 1-digit sigma-delta modulation procedure of Direct Stream
Digital jointly developed by SACD, Sony and Philips.
Generally, the sampling rate of the audio cards is 44.1 kHz. That is, the audios are sampled 44,100 times
per second. The phone-call-level voice quality is obtained by using a sampling rate of 11 kHz.
Broadcast-level voice quality is obtained by using a sampling rate of 22 kHz. CD-level voice quality is
obtained by using a sampling rate of 44.1 kHz. A larger sampling rate indicates better voice quality and
greater disk (or CD) space usage. The size of a song with CD-level voice quality is about 45 MB.
AMR-WB is a broadband speech codec scheme using a sampling rate of 16 kHz. Generally, the quality
of the obtained audio reaches the amplitude broadcast level. The new-generation speech codec scheme
Enhanced Voice Services (EVS) will further increase the sampling rate. The voice quality will also
further improve. The EVS is under discussion in 3GPP Release 12 and is expected to be standardized in
2015.
AMR-WB has nine coding rates in addition to the SID frames. The following table lists the voice
quality of these coding rates obtained based on the ITU-T P.863 assessment criteria.
Coding 23.85 23.05 19.85 18.25 15.85 14.25 12.65 8.85 6.6 SID
Rate
(kbit/s)
MOS 4.14 4.12 4.1 4.08 4.04 4.00 3.90 3.54 3.14 \
When AMR-WB was introduced in 3GPP Release 5, only five of the preceding speech coding rates are
recommended to prevent an excessive number of speech coding rates from being used. The following
table lists the combination of these rates (mode set) recommended in 3GPP TS26.103.
POLQA supports a wider sampling scope and can assess the voice quality of AMR-WB more accurately.
This following figure shows the comparison result between POLQA and PESQ. The MOS results are
different for the same voice sample using different assessment criteria. For example, the MOS of a voice
sample assessed based on the PESQ criterion is 4.2. The MOS of the same voice sample assessed based
on the POLQA criterion is 3.6.
SRI
Bearer Establishment
On The Caller Side
INVITE
Paging
Bearer Establishment
100 On The Callee Side
183
PRACK
200
Alerting
180
PRACK
200
Alerting
Connect
200
Connect
Connect Ack
Ack
Connect Ack
Step 2 Outgoing route data is obtained from the SRI at the MSC_T side and bearers are set up at the MSC_O
side.
Step 3 The MSC_O sends an INVITE message to the MSC_T. The following shows the format of the INVITE
message.
Request line: Includes the request type, the Tel uniform resource identifier (URI) of the called UE
("user=phone" indicates that the URI is in the MSISDN format), transmission protocol (SCTP),
and the SIP version.
Message head
− Via: Indicates the path where the request passes through. In this example, the INVITE message
is generated by the MSC_O. Therefore, the IP address included in this line is that of the
MSC_O. Branch indicates a request transaction ID.
− Route: Indicates that the next hop IP address. In this example, the next hop IP address is that of
the MSC_T.
− Call-ID: Indicates a SIP cal. Call-ID is unique globally. A multimedia session may contain
multiple SIP calls with multiple Call-IDs.
− From: Indicates the source of the message. In this example, the source is the MSC_O.
− To: Indicates the destination of the message. In this example, the destination is MSC_T.
− Cseq: Indicates the sequence number of the message. The initial number is 1, and the sequence
number increases in an ascending order for subsequent messages. The sequence number does
not increase if a message is retransmitted. INVITE indicates the message type.
− Max-Forwards: Indicates the maximum number of times the message can be forwarded by an
agent or gateway during the transmission. This number decreases by one each time the message
is forwarded.
− Contact: Indicates the URI of the message sender. The URI can be an SIP URI or an SIPS URI.
It must be in the same format (SIP URI or SIPS URI) as the Request URI or the URI in the
route header field. The Contact field enables the called UE to send requests (such as BYE
message) directly to the IP address where the INVITE message is sent. In this way, the requests
do not need to be transmitted through a few agents based on the Via field.
− Allow: Indicates the request type supported by the server.
− Supported: Indicates the extended request type supported by the server.
− Session-Expires: Indicates the session update interval. It is negotiated between the MSC_O and
MSC_T sides. After the negotiation, the MSC_O sends a RE-INVITE or UPDATE message to
the MSC_T at the negotiated interval during a session to detect the session status of the
MSC_T.
− Content-Length/Content-Type: Indicates the length and type of the message body.
Message body
The message bodies included in the message body are as follows:
− SDP
The Session Description Protocol (SDP) message body uses UIF-8 for coding and is used for
media negotiation. The SDP message body is in the format of text. Information elements (IEs)
included in the SDP message body are as follows:
1. m indicates the media name and transmission address. It is in the format of <Media
name><Port><Transport>. The media name can be audio, video, and data. The "136" field
indicates the number of the port that transmits the media stream. RTP/AVP indicates the
transmission protocol. And the other numbers indicate the payload format of the media stream.
2. a indicates the attribute and is in the format of <Attribute>:<Value>. An SDP has one or
more attribute descriptions.
3. The calling and called UEs preferentially use the mode set in the first m line.
"modeset=0,2,5,7" indicates a mode set with four coding rates. These coding rates are
supported by both the calling and called UEs. The coding rate to be used depends on the
mechanism adopted by the UE manufacturers.
− ISUP
If an SIP message contains an ISDN User Part (ISUP) message, it encapsulates the ISUP
message in hexadecimal format in the message body of the INVITE message so that the ISUP
message is transmitted over an SIP network without any loss.
You can run the Show ISUP Body command to query the contents in the ISUP message
encapsulated in the INVITE message.
Step 4 After receiving the INVITE message, the MSC_T authenticates the message. If the authentication is
successful, the MSC_T initiates the paging and bearer setup procedures.
Step 5 During the paging and bearer setup procedures, the MSC_T sends a 100 Trying message to the MSC_O,
indicating that the MSC_T is processing the INVITE message.
Step 6 The MSC_T starts to process the INVITE message and monitors the processing progress for
constructing a 183 Session Progress message. The 183 Session Progress message is a part of the media
negotiation between the MSC_O and MSC_T sides. The SIP media negotiation information cannot be
contained in temporary and unreliable messages. However, with 100rel extension to SIP, the UAC
sends the PRACK message (which will be responded with a 200 For Prack message) after receiving a
temporary response from the UAS.
Reliable 183 Session Progress messages must contain the Require and Response Sequence(RSeq)
header fields.
Step 7 After receiving the 183 Session Progress message, the MSC_O that supports 100rel extension to SIP
responds with a PRACK message. Then, the MSC_T responds with a 200 For PRACK message to
complete the media negotiation. If the media need to be changed, the MSC_O sends an UPDATE
message to update the media negotiation information.
Step 8 After the assignment is completed on the MSC_T side and the called UE rings, the MSC_T sends a 180
Ringing message to the MSC_O. CSeq: 1 INVITE indicates the response to the initial INVITE message.
Reliable 180 Ringing messages must contain the Require and Response Sequence(RSeq) header fields.
Subscriber-free is contained in the ISUP message, indicating that the called UE is released.
Step 9 After receiving the 180 Ringing message, the MSC_O sends an Alert message to the calling UE and a
PRACK message containing "Cseq:3 PRACK" to the MSC_T. The MSC_T responds with a 200 For
PRACK message. The 1XX procedure using the 100rel mechanism is completed.
Step 10 After the called UE is off-hook, it sends a Connect message to the MSC_T. The MSC_T completes the
processing of the INVITE message and then sends a 200 OK message to the MSC_O.
Step 11 After the MSC_T receives an ACK message, the call setup procedure is complete and the calling and
called parties can communicate.
----End
When a VoLTE UE calls a GSM, UMTS, or VoBB MS/UE, the SBC/IM-MGW needs to participate in
the transcoding because the existing GSM, UMTS, or VoBB MS/UEs do not support
AMR-WB/AMR-NB (they only support GSM single-rate codec).