ATP - eRAN8.1 VoLTE Test Guide

Product Name Confidentiality Level
LTE eNodeB INTERNAL

Product Version Total 41 pages
eRAN8.1
eRAN8.1 VoLTE Test Guide
Prepared by GUL I&V Dept Date 2014-12-31
Reviewed by Date
Approved by Date
Authorized by Date
Huawei Technologies Co., Ltd.

All rights reserved
LTE eNodeB
eRAN8.1 VoLTE Test Guide About This Document
About This Document
Change History
Date Version Change Description Author
2011-1-20 1.00 Completed the draft. Qiu Jun

2014-12-31 1.0 Completed the draft. Chen Jinqiao
Key words
LTE, VoLTE, Test guide
Abstracts
This document describes the principles of LTE VoLTE, the VoLTE test process, configuration
of the test on eRAN8.1, and FAQ. The FAQ can help solve the test problems.
Issue 01 (2014-06-27) Huawei Proprietary and Confidential ii

Copyright © Huawei Technologies Co.,
Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide Contents
Contents
About This Document....................................................................................................................ii

1 Overview.........................................................................................................................................1
2 Introduction to VoLTE.................................................................................................................2
2.1 Background of the VoLTE Service.................................................................................................................................2
2.2 VoLTE Service Model....................................................................................................................................................2
2.2.1 Introduction to AMR...................................................................................................................................................2
2.2.2 Features of the VoLTE Service....................................................................................................................................5
2.3 Introduction to the Semi-Persistent Scheduling.............................................................................................................5
2.3.1 Activating and Deactivating the Semi-persistent Scheduling.....................................................................................6
2.3.2 Allocating the Resource of the Semi-persistent Scheduling........................................................................................7
2.3.3 VoLTE Service Status Transition and the Semi-persistent Scheduling.......................................................................7
2.4 Introduction to the TTI Bundling...................................................................................................................................8
2.4.1 TTI Bundling...............................................................................................................................................................8
2.4.2 Triggering the TTI Bundling and Selecting an MCS RB Number..............................................................................9
2.5 ROHC Used by the VoLTE Service..............................................................................................................................10
3 VoLTE Test Environment..........................................................................................................12

3.1 Test Scenarios...............................................................................................................................................................12
3.2 VoLTE Networking.......................................................................................................................................................12
4 VoLTE Test Method and Tools for Commercial UEs...........................................................13

4.1 Introduction to DSLA...................................................................................................................................................13
4.2 Preparation for the Voice Quality Test..........................................................................................................................14
4.2.2 Installing the DSLA...................................................................................................................................................15
4.2.3 Editing a DSLA Script...............................................................................................................................................17
4.3 Test Procedure..............................................................................................................................................................18
4.3.1 Performing the Voice Quality Test............................................................................................................................18
4.3.2 Performing DSLA Monitoring on the Voice Quality Test.........................................................................................19
4.3.3 Querying the Voice Quality Test Result....................................................................................................................20
4.4 Test Procedure for Commercial UEs............................................................................................................................21
4.4.1 Preparing for Accessing the VoLTE Network...........................................................................................................21
4.4.2 Registration Procedure for Commercial UEs............................................................................................................22
4.5 Other Test Scenario......................................................................................................................................................23
Issue 01 (2014-06-27) Huawei Proprietary and Confidential iii

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide Contents
4.5.1 Interference Scenario for Downlink Data Channels and Control Channnels............................................................23
5 Analyzing the Test Result on Commercial UEs and Comparing the Test Result with
the Expected Result........................................................................................................................25
5.1 Calculating the MOS and Test Result and Comparing Them with the Baseline..........................................................25
5.1.1 Expected Test Result.................................................................................................................................................25
5.2 Triggering the Semi-persistent Scheduling and Observing the Trigger.......................................................................25
5.3 Observing the Trigger of TTI Bundling.......................................................................................................................27
5.4 Observing the Trigger of ROHC..................................................................................................................................28
6 FAQs...............................................................................................................................................31
6.1 TTI bundling cannot be triggered.................................................................................................................................31
7 Appendix.......................................................................................................................................35
7.1 SIP Signaling Process...................................................................................................................................................35
7.1.1 Call Setup Process.....................................................................................................................................................35
7.1.2 Call Completion Process...........................................................................................................................................36
Issue 01 (2014-06-27) Huawei Proprietary and Confidential iv

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 Overview
1 Overview
This document describes the following tests:

 Test on VoLTE services
 VoLTE service under semi-persistent scheduling and dynamic scheduling
 Performance gain of the transmission time interval (TTI) bundling
 ROHC performance tests
This document describes the eRAN8.1 VoLTE test, test networking, test procedure, parameter
settings, and observation of the test result.
Required license: The semi-persistent scheduling (SPS), TTI bundling and ROHC features
require licenses.
Issue 01 (2014-06-27) Huawei Proprietary and Confidential 1

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 Introduction to VoLTE
2 Introduction to VoLTE
2.1 Background of the VoLTE Service

The all-IP network is the trend of the future cellular system. The next generation mobile
network (NGMN) faces the challenge of providing voice service over the all-IP network. The
voice over internet protocol (VoLTE) is the best solution. The VoLTE service must support
high-speed seamless mobility for UEs moving at as high as 350 km/h and good voice quality
at the cell edge. The VoLTE voice quality must not be affected by handovers. When the
network is congested, the VoLTE voice quality should be better than 3G AMR 12.2 kbit/s CS
service or WB AMR 12.65 kbit/s CS service.
In the present LTE network, the voice service is still the basic service. The LTE network has
only packet switched (PS) domain, and therefore the VoLTE service that is also in the PS
domain suits the LTE network perfectly and improves the network efficiency. Meanwhile, the
bearer is separated from the service, improving the service flexibility and simplifying the
network architecture and management. Therefore, the performance of the VoLTE service is
critical for the LTE network.
2.2 VoLTE Service Model

2.2.1 Introduction to AMR
The automatic meter reading system (AMR) is an audio data compression and optimization
solution for voice coding and widely applies to the GSM and UMTS networks.
In AMR coding, a coding rate is adaptively selected based on radio channel conditions to suit
the change of the channel quality. The size of the data packets is determined based on the
AMR coding rate. The VoLTE service usually uses AMR wideband coding. Figure 1-1 and
Figure 1-2 list the VoLTE packet sizes of different AMR coding rates (classified into
narrowband rates and wideband rates).

Ltd.
LTE eNodeB
Figure 1-1 Mapping between AMR NB coding rates and VoLTE packet sizes

Ltd.
LTE eNodeB
Figure 1-2 Mapping between AMR WB coding rates and VoLTE packet sizes
Where the size of the AMR header is determined by the following protocols:
 According to the 3GPP TS 26.101, the size of the AMR-NB header is 19 bits and the size
of the AMR-WB header is 21 bits.
 According to the RFC 3267, the size of the AMR header is 12 bits.
Consider the difference of resource used, AMR usually Used in 2G/3G, AMR-WB
usually used in 4G /3G.
Figure 1-3 shows the process of generating VoLTE packets from AMR frames.

Ltd.
LTE eNodeB
Figure 1-3 Process of generating VoLTE packets from AMR frames
2.2.2 Features of the VoLTE Service

The VoLTE service is divided into transient period, talk period, and silent period. In the talk
period, data is sent every 20 ms. In the silent period, a silence insertion descriptor (SID) frame
is sent every 160 ms. Figure 1-4 shows the VoLTE packets in the time domain.
Figure 1-4 VoLTE packets in the time domain
2.3 Introduction to the Semi-Persistent Scheduling

The VoLTE service uses the semi-persistent scheduling and is the typical application of the
semi-persistent scheduling. The semi-persistent scheduling consists of the uplink semi-
persistent scheduling and downlink semi-persistent scheduling. For the uplink, the uplink
semi-persistent scheduling is used for the initial transmission data and the synchronous non-
adaptive hybrid automatic repeat request (HARQ) is used for the retransmission data if the
retransmission data is not in conflict. For the downlink, the downlink semi-persistent
scheduling is used for the initial transmission data and the asynchronous adaptive HARQ is

Ltd.
LTE eNodeB
used for the retransmission data. The semi-persistent scheduling is suitable for processing
services of low and stable data rates and low delay. Semi-persistent scheduling of the VoLTE
service avoids insufficient resource utilization caused by lack of the physical downlink
control channel (PDCCH) resource.
From eRAN3.0, the semi-persistent scheduling is applicable to the VoLTE service only. In the
transient period and silent period of the VoLTE service, the dynamic scheduling is used; in the
talk period, the semi-persistent scheduling is used in principle, except that the dynamic
scheduling is used in the following scenarios:
 In high-speed railways where UEs move at high speed, the dynamic scheduling is used
in the talk period of the VoLTE service.
 If the UE has set up other bearers in addition to the default bearer and VoLTE bearer, the
dynamic scheduling is used in the talk period of the VoLTE service.
 During the activation of the semi-persistent scheduling, if the semi-persistent scheduling
indication fails to be delivered due to insufficient PDCCH resource, the current data
packet uses dynamic scheduling in the next TTI. That is, the bearer needs to compete for
resource with other bearers. The resource of the semi-persistent scheduling assigned to
this bearer is reserved and an indication for activating the semi-persistent scheduling is
sent again in the next semi-persistent scheduling period.
 During a TTI of semi-persistent scheduling, if there are large data packets (such as
ROHC update context), the dynamic scheduling is used.
2.3.1 Activating and Deactivating the Semi-persistent Scheduling

When the VoLTE service uses the semi-persistent scheduling, the period of the semi-persistent
scheduling (the default period is 20 ms) is configured on the RRC and the resource of the
semi-persistent scheduling is activated or deactivated by the scheduler on the PDCCH. When
the VoLTE service moves from the silent period to the talk period, the resource is activated;
When the VoLTE service moves from the talk period to the silent period, the resource is
deactivated.
2.3.1.1 Activating the Semi-persistent Scheduling

Activating the uplink semi-persistent scheduling
WA UE sends the eNodeB a scheduling request (SR) before sending data. The eNodeB
cannot determine that it is the VoLTE service based on the SR and delivers the ordinary C-
RNTI scrambled PDCCH downlink control information (DCI) 0 to the UE. The UE sends the
BSR and VoLTE data to the eNodeB. The eNodeB determines that it is the VoLTE service and
delivers the SPS C-RNTI scrambled PDCCH DCI0 to activate the semi-persistent scheduling.
Activating the downlink semi-persistent scheduling
The packet data convergence protocol (PDCP) checks whether the PDCP SDU of QoS class
identifier (QCI) 1 before header compression is a SID frame. If not, the PDCP determines that
the VoLTE service is in the talk period and activates the semi-persistent scheduling.
The PDCP layer of the eNodeB checks for the VoLTE service based on the following steps:
2. Checks whether the sent data belongs to QCI1. If yes, the service is VoLTE.
3. Calculates the code rate based on the packet size described in Figure 1-1 and Figure 1-2
to obtain the transport block size.

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 Deactivating the semi-persistent scheduling
2.3.1.2 Deactivating the semi-persistent scheduling

If the eNodeB continuously receives SID frames or null data packets, the eNodeB deactivates
the semi-persistent scheduling and releases the resource of the semi-persistent scheduling.
Deactivating the uplink semi-persistent scheduling
The uplink semi-persistent scheduling can be deactivated explicitly or implicitly. If the UE
has no service data to send over the resource of the semi-persistent scheduling for consecutive
N1 times, the semi-persistent scheduling is implicitly deactivated. If the UE sends the SID
frames over the resource of the semi-persistent scheduling for consecutive N2 times, the semi-
persistent scheduling is explicitly deactivated.
Deactivating the downlink semi-persistent scheduling
The downlink semi-persistent scheduling can be deactivated explicitly or implicitly. The
PDCP checks whether the PDCP SDU of QCI1 before header compression is a SID frame. If
yes, the PDCP determines that the UE is in silence period and deactivates the semi-persistent
scheduling.
The deactivation of the semi-persistent scheduling is triggered in the following scenarios:
 The VoLTE service is complete. That is, when the semi-persistent scheduling TTI comes,
the eNodeB determines that there is no VoLTE packet for consecutive N TTIs. According
to the protocols, the value of N can be 2, 3, 4, or 8.
 The eNodeB continuously receives the SID frames or null data packets.
2.3.2 Allocating the Resource of the Semi-persistent Scheduling

Allocating the resource of the uplink semi-persistent scheduling
The eNodeB allocates the resource of the semi-persistent scheduling based on the compressed
VoLTE packet size and average signal to interference plus noise ratio (SINR) of the UE. First,
the eNodeB searches the compressed VoLTE packet size in the transport block size (TBS)
table. The resource block (RB) is numbered from 1 in ascending order and the TBS indexes
are from 0 to 15. When a TBS satisfies the VoLTE packet size and the average SINR is greater
than the SINR threshold of the modulation and coding scheme (MCS) corresponding to the
TBS, the MCS and RB number are used.
Allocating the resource of the downlink semi-persistent scheduling
The eNodeB allocates the resource of the semi-persistent scheduling based on the compressed
VoLTE packet size and the filtered full-band CQI (not adjusted) by performing the following
steps:
4. The compressed VoLTE packet size and filtered full-band CQI are mapped to an MCS
value (the value is rounded to 15 if it is greater than 15).
5. The eNodeB searches the MCS in the TBS table to obtain the minimum RB number that
satisfies the VoLTE packet size.
6. The eNodeB looks the RB number and VoLTE packet size in the TBS table to obtain the
minimum MCS that satisfies the VoLTE packet size.
2.3.3 VoLTE Service Status Transition and the Semi-persistent

Scheduling
After the VoLTE service is set up, the PDCP checks the size of the first VoLTE service data
packet (uplink: after decompression; downlink: before compression) to decide whether the

Ltd.
LTE eNodeB
VoLTE service is in the talk period or silence period. The first packet after the setup of the
VoLTE service uses the dynamic scheduling. Figure 1-1 shows the VoLTE service status
transition and the corresponding scheduling strategy.
Figure 1-1 VoLTE in talk period after service setup
2.4 Introduction to the TTI Bundling

This document describes the uplink TTI bundling.
2.4.1 TTI Bundling

The cell edge users (CEU) are power-restrained and one RLC SDU requires several HARQs
before the RLC SDU can be correctly transmitted. In the semi-persistent scheduling, the RLC
is not adaptive. That is, the RLC does not perform adaptive fragment retransmission based on
the channel quality (the VoLTE data packets use unacknowledged mode at the RLC layer).
Therefore, the retransmission totally depends on the HARQ. This increases the probability of
retransmission. In the 3GPP protocols, the probability of retransmission is lowered by
increasing the redundancy. This is the TTI bundling.
The TTI bundling means that the same transport block is transferred over several consecutive
subframes and that several bundled TTIs are treated as one unit, with each TTI transferring
different redundant versions of the same SDU.
Figure 1-2 shows that the TTI bundling size is fixed to 4. The HARQ retransmission is also a
TTI bundling and is synchronous non-adaptive retransmission. The HARQ retransmission

Ltd.
LTE eNodeB
interval changes from the normal 8 TTIs (normal HARQ RTT) to 16 TTIs (bundle HARQ
RTT).
Figure 1-2 TTI bundling size
The FDD eNodeB has the following requirements:

 The TTI bundling size is fixed to 4. The sequences of the redundancy versions using the
four subframes are 0, 2, 3, and 1.
 The TTI bundling HARQ RTT changes from 8 TTIs to 16 TTIs, and the number of
HARQ processes decreases from 8 to 4.
 The ACK/NACK starts from the last TTI of the bundling TTI.
 The number of RBs allocated to each bundled TTI is less than or equal to 3 and the
modulation can use QPSK only.
2.4.2 Triggering the TTI Bundling and Selecting an MCS RB

Number
The eNodeB obtains the AMR code rate and the UE power headroom of the VoLTE service
and looks up the table to obtain the upper threshold and lower threshold for triggering the TTI
bundling. When the UE full-band uplink average SINR is lower than a preset threshold, the
UE channel quality is measured. In the measurement period, if the UE full-band average
SINR is lower than the upper threshold for not less than N% of the time and higher than the
lower threshold for not less than 1-N% of the time, the TTI bundling is triggered. If the SINR
is lower than the lower threshold for more than N% of the time, the eNodeB repeats the
preceding decision process in the next measurement period and treats the call as a call drop if
the triggering condition is still not satisfied.
The triggering of the TTI bundling depends on two thresholds: signal measurement threshold
and decision threshold. Figure 1-3 shows that the first threshold triggers the UE channel
quality measurement and is referred to as threshold 1. The second threshold determines the
SINR range for the UE and is referred to as threshold 2.

Ltd.
LTE eNodeB
Figure 1-3 Thresholds of the TTI bundling
When the transmit power headroom satisfies a certain condition (Pc within [0,6.02]), the
eNodeB starts to calculate the threshold 2 to obtain the upper and lower thresholds. When the
average SINR of the UE is lower than the signal measurement threshold 1, the eNodeB starts
to measure the channel quality.
When the measured channel quality is within threshold 2 for a preset probability, the TTI
bundling is triggered.
When the measured channel quality is higher than the upper threshold of threshold 2 for a
preset probability, the UE exits the TTI bundling.
When the measured channel quality is lower than the lower threshold of threshold 2 for a
preset probability, the UE exits the network.
2.5 ROHC Used by the VoLTE Service

The VoLTE header compression uses robust header compression (ROHC) algorithm. The
ROHC is a robust algorithm that can compress RTP, UDP, and IP packets.
The header compression algorithm is able to reduce the header overhead, increase the
interactive response, and decrease the packet loss.
The development of IP networks increases the percentage of protocol headers in the packets.
For some data streams, most of the content in the IP header, UDP header, or RTP header is
unchanged and is easily compressed. Context information is maintained between the ROHC
compressor and decompressor. The compressor sends the compressed packets and the
decompressor restores the original packets based on the context information. Figure 1-4
shows the compression and decompression process.

Ltd.
LTE eNodeB
Figure 1-4 Compression and decompression process

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 VoLTE Test Environment
3 VoLTE Test Environment
3.1 Test Scenarios

Scenarios of the VoLTE test are as follows:
 The Digital Speech Level Analyser (DSLA) and the control software installed on the PC
are used to simulate the VoLTE service.
 The VoLTE service is simulated and the VoLTE access delay is tested. The IX Chariot
software constructs correct scenarios, configures the algorithm switches and algorithm
parameters, and combines service types to test and optimize the VoLTE capacity, MOS,
packet loss rate, delay, delay variance, and call drop rate.
3.2 VoLTE Networking

The DSLA software is installed on the PC that is connected to two UEs (two Huawei Acsend
P1 UEs) and the DSLA. The headsets of the UEs are connected to the handset ports on the
DSLA. The DSLA software is used to simulate the VoLTE service between the UEs.
Figure 1-5 VoLTE networking

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 VoLTE Test Method and Tools for Commercial UEs
4 VoLTE Test Method and Tools for

Commercial UEs
4.1 Introduction to DSLA

The digital speech level analyser (DSLA) is a voice quality test device developed by Malden,
and can be applied to end-to-end voice quality test.
Figure 1-6 Exterior of the DSLA
The DSLA provides the following functions:

 Voice level measurement: The actual level of the activated voice segment is measured.
 Perceptual evaluation of speech quality (PESQ), PESQ-LQ, PESQ-P.862.1/2, and
PALQA.
 PARMS: This function is optional.
 PSQM/PSQM+: This function is optional.
 Delay measurement with the precision of 1 ms.
 Clipping test: This function is optional.
 Echo level test.
 Dual tone multiple frequency (DTMF) tone test.
 Noise level test.
 Mute mode detection.

Ltd.
LTE eNodeB
 Noise importing.
The DSLA supports end-to-end voice quality tests by directly connecting to UEs in all kinds
of networking, such as WCDMA, PSTN, CDMA2000, and TD-CDMA.
4.2 Preparation for the Voice Quality Test

Figure 1-7 shows the location of the DSLA in the voice quality test.
Figure 1-7 Location of the DSLA in the voice quality test
Ports on the panel of the DSLA and devices connecting to these ports are as follows:
 Handset port (RJ22): This port is used to connect the DSLA to a fixed phone, mobile
phone, or audio card through their receiver, Mic In port, or Line Out port.
 Telephone Line port (RJ11): This port is used to connect THE DSLA to telephone lines.
A voice quality test involves two ports. One port is used to transmit signals, and can be
referred as Channel A. The other port is used to receive signals, and can be referred as
Channel B. The voice quality test result is calculated by comparing the reference signal and
degraded signal.

Ltd.
LTE eNodeB
NOTE
The Handset port of the DSLA connects the RJ22 connector and the Mic In port of a mobile phone.
Most Mic In ports of mobile phones are not standard 2.5 mm audio ports. Only some mobile phone
vendors provide adapter plugs to connect the non-standard Mic In ports. When connecting the DSLA to
smartphones, connect the Mic In port of a UE to the RJ22 connector of the DSLA directly.
4.2.1 Installing the DSLA

The DSLA must connect to a PC before performing voice quality tests. The PC executes test
commands and assigns tasks to the DSLA. The DSLA reports test results to the PC.
The software version of the PC can be Windows 2000 or Windows XP.
The DSLA software is installed in C:\Program Files\DSLA by default. If the installation
directory of the DSLA software must be changed, the Playlist folder of the DSLA must be
saved into C:\Program Files\DSLA, and the new installation directory is C:\Program Files\
DSLA\Playlist. You are advised not to change the default installation directory.
Connecting the DSLA and PC

A PC that has the control software installed can connect to the DSLA in either of the
following methods:
 Using an Ethernet port
 Using a serial port
The default IP address of the DSLA is 90.0.0.154. The IP address of the PC must be changed
to an IP address in the same network segment as the default DSLA IP address. Then, the
DSLA can connect to the PC.
To change the PC IP address, perform related operations based on the following scenarios:
 If the DSLA IP address is known, set the PC IP address to an IP address in the same
network segment as the DSLA IP address.
 If the DSLA IP address is unknown, change the DSLA IP address on a serial port by
performing the following steps:
7. Connect the DSLA to a PC by using a serial port.
8. Start the DSLA.
9. Choose Tools > Options.
The Options dialog box is displayed, as shown in the following figure.

Ltd.
LTE eNodeB
10. Click the Local Area Network using the following IP address option button, and set
IP Address to the DSLA IP address, and ensure that the IP address of the DSLA and PC
are in the same segment.
11. Power off and then power on the DSLA.
12. Disable the serial port, connect the DSAL to the PC by using an Ethernet port, and start
the DSLA.
The DSLA is functioning correctly, and can perform voice quality tests.
----End
Copying an Audio File

If there is no audio file for voice quality tests in the DSLA or the audio file to be tested is not
available in the DSLA, copy an audio file in WAV or ASTS 2 format from the flash disk of the
DSLA. The file can be permanently stored in the DSLA.
To copy an audio file to the DSLA, perform the following steps:
Step 2 Start the DSLA, and choose Tools > DSLA Explorer.
The DSLA Explorer is displayed, as shown in the following figure.

Ltd.
LTE eNodeB
NOTE
 There are the DSLA folder in the DSLA and the Local Files folder in the PC. Only files in the two
folders can be used in voice quality tests.
 The Local Files folder corresponds to the Phonytalk folder in the DSLA installation directory in the
PC.
Step 3 Copy the Misc and British folders under the Local Files folder to the DSLA folder.
----End
4.2.2 Editing a DSLA Script

This section describes methods for the design of basic voice quality tests. For details about the
design for complex voice quality tests, see related DSLA user guide.
Selecting an Audio File

The DSLA provides the Artificial Speech Test Stimulus (ASTS) developed by Psytechnics to
generate test samples and obtain reference signals in voice quality tests. The ASTS is
designed to perform voice quality tests on the non-linear telecommunication system bearing
voice services by interworking with the PESQ and PAMS algorithms. Because the typical
voice signal contains a great amount of redundant information, a voice quality test on the
typical voice signal must last for 10 minutes at least. The ASTS can significantly decrease
redundant information in the typical voice signal. A 15-second ASTS voice signal file
contains valid information of a 2-hour typical voice signal file. Therefore, the ASTS greatly
decreases the test duration while reducing costs.
Table 1-1 ASTS audio files

ASTS Audio File Required Test Duration (s)
Joed 1.41
This 2.42

Ltd.
LTE eNodeB
ASTS Audio File Required Test Duration (s)
Oatlet 4.26
Woaner 5.01
Nullow 5.69
illindge 6.92
Lowlant 8.70
Else 10.19
4.2.2.1 Editing a Voice Quality Test Event

To generate a voice quality test event, perform the following steps:
Step 4 In the DSLA, select View, and then select Channel A or Channel B for the direction of the
voice quality test.
NOTE
 If Channel A is selected as the monitoring channel, voice signals sent from smartphone B to
smartphone A are monitored.
 If Channel B is selected as the monitoring channel, voice signals sent from smartphone A to
smartphone B are monitored.
Step 5 Specify the begin time, end time, loudness, and tone color, and then play the voice.
Step 6 Wait about 2 seconds after the voice play process ends. Ensure that the received audio file is
complete.
Step 7 Evaluate the voice quality.
Step 8 Store the voice quality test event records in C:\Program Files\DSLA\Playlists\Quick Start\
British.
----End
4.2.2.2 Editing a Voice Quality Test Scheduler

To generate a voice quality test scheduler based on voice quality test event records, perform
the following steps:

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 Editing a Voice Quality Test Scheduler
Step 9 Arrange voice quality test events based on the sequence numbers to form a scheduler.
The scheduler supports cyclic operations.
Step 10 Choose Tools > Scheduler to open the Scheduler dialog box.
Step 11 Add, delete, edit, or repeat a voice quality test event.
Step 12 Store the scheduler in C:\Program Files\DSLA\Playlists\Library\British.
----End
4.3 Test Procedure

4.3.1 Performing the Voice Quality Test
To carry out the voice quality test, perform the following steps:
Step 13 Connect the test smartphones to the DSLA.
Step 14 Connect the DSLA to the PC, and execute the test script.
Step 15 Use a smartphone to initiate a voice call.
Step 16 Start the voice quality test.
Step 17 After the test, move the Result.log file out of the default director.
NOTE
The Result.log file under the default directory must be removed. Otherwise, new Result.log files cannot
be generated, and results of the following tests will be recorded on the existing Result.log file.
----End
4.3.2 Performing DSLA Monitoring on the Voice Quality Test

Starting the DSLA Monitoring
To start the DSLA monitoring, perform the following steps:

Ltd.
LTE eNodeB
Step 18 On the DSLA, choose Tools > Monitor Levels.

The Monitor Levels dialog box is displayed, as shown in the following figure.
Step 19 Insert an earphone plug into the Monitor socket on the DSLA panel.
Step 20 Specify the channel to be monitored, click In or Out, and adjust the slider label of In or Out.
NOTE
 The Channel A or Channel B and the option button In or Out can be selected simultaneously.
 If none of these items is specified, no voice can be heard.
----End
Benefits of DSLA Monitoring

The voice quality test result can be verified by using the DSLA monitoring.
4.3.3 Querying the Voice Quality Test Result

The voice quality test results, such as voice clarity and delay, are recorded in the Results.log
file. You are advised to save the file with information about related test conditions.
Table 1-1 Description about the Results.log file

Abbreviation and Description
Acronym
DUR(s) Duration.
LNGTRM Long-term level, the unit is dBm.
ACTLVL Active level, the unit is dBm.
PEAK Peak level, the unit is dBm.
NSE Noise level, the unit is dBm.
ACT% Activity factor, the unit is %.
DLY Delay that measured by TimeAlign or ActiveLevel, the unit is ms.

Ltd.
LTE eNodeB
Abbreviation and Description

Acronym
DAF Dual activity, the unit is %.

PESQ PESQ MOS value.
PESQLQ PESQ-LQ MOS value.
P862.1 P.862.1 MOS value.
IE Impairment factor.
OFFSET Time offset that measured by PESQ or PAM, and the unit is ms.
CONF% Time offset confidence that measured by PESQ or PAMS.
MIN Minimum time offset calculated based on the measured PESQ
values or PAMS values, and the unit is ms.
MAX Maximum time offset calculated based on the measured PESQ
values or PAMS values, and the unit is ms.
MEDIAN Medium time offset calculated based on the measured PESQ values
or PAMS values, and the unit is ms.
STDDEV Standard deviation calculated based on the measured PESQ values
or PAMS values, and the unit is ms.
UTTCNT Utterance count
MUTED% Proportion of Speed Muted.
LNGMUTE Longest muted section, the unit is ms.
FILEID File name of obtained reference signal and degraded signals.
DATE/TIME Time to start the test.
4.4 Test Procedure for Commercial UEs

4.4.1 Preparing for Accessing the VoLTE Network
Before enabling a commercial UE to access the VoLTE network, collect the following
information:
 IP multimedia private identity (IMPI)
 IMS public user identity (IMPU)
 Domain
 Authentication mode (whether AKA authentication is required)
 Password
 Access point name (APN)

Ltd.
LTE eNodeB
 Method to obtain the PCSCF IP address (Configuration delivered to the UE from the
network side)
 PCSCF IP address and port number
In the preceding information, IMPI, IMPU, Domain, authentication mode, and password can
be written on the IMS subscriber identity module (ISIM). If no ISIM is available, the NV
67258 (a test smartphone chip developed by Qualcomm) can be used to record the
information, as shown in the following figure.
When the NV 67258 (a test smartphone chip developed by Qualcomm) is used, the NV67261
must be used to set the value of the IMSParamSRC parameter to specify whether the IMPI
and IMPU are read from the ISIM card or the UE.
NOTE
 When the IMSParamSRC parameter is set to 2, the IMPI and IMPU are read from the SIM card.
 When the IMSParamSRC parameter is set to 0, the IMPI and IMPU are read from the UE.
Required information for account registration is categorized as follows:

 USIM: IMSI, Ki, OPc
 ISIM: IMPI, IMPU, Domain name, Ki, OPc, PCSCF IP address (This item is optional)
4.4.2 Registration Procedure for Commercial UEs

To enable a commercial UE to register with the VoLTE network, perform the following steps:
Step 21 Set up the default bearers.
In the e-RABToBeSetupListCtxtSUReq message when the UE accesses the network, the
default bearers for QCI 5 are set up, as shown in the following figures.

Ltd.
LTE eNodeB
Step 22 Set up a dedicated bearer.

In the e-RABToBeSetupListCtxtSUReq message when the UE initiates a VoLTE service, a
dedicated bearer eRAB 6 is set up for QCI 1, as shown in the following figure.
----End
4.5 Other Test Scenario

4.5.1 Interference Scenario for Downlink Data Channels and
Control Channnels
4.5.1.1 PDSCH Interference Scenario
Use the following MML command in eNodeB to simulate the PDSCH interference.
ADD CELLSIMULOAD: LocalCellId=0, SimLoadCfgIndex=4;

Ltd.
LTE eNodeB
Explain: Difference index Number denotation different simulate load is.
4.5.1.2 PDCCH Interference Scenario

Use the following MML command in eNodeB to simulate the PDCCH interference.
MOD CELLPDCCHALGO: LocalCellId=0, VirtualLoadPro=50, DPDVirtualLoadSwitch=ON;
PDCCH virtual Loading of interference can adjust form 0 to 100, and need enable the DPD
Virtual load switch.
The result of volte in interference scenario as follows:

Ltd.
LTE eNodeB

Ltd.
LTE eNodeB 1 Analyzing the Test Result on Commercial UEs and
eRAN8.1 VoLTE Test Guide Comparing the Test Result with the Expected Result
5 Analyzing the Test Result on Commercial

UEs and Comparing the Test Result with the
Expected Result
5.1 Calculating the MOS and Test Result and Comparing

Them with the Baseline
5.1.1 Expected Test Result
Pay attention to the following data: MOS, end-to-end delay, percent bytes lost E1 to E2, and
header compression ratio.
The baseline data is as follows:
 Pay special attention to the MOS average. The MOS average varies with the speech
coding methods and must be greater than 3.5 for P863 coding with the sampling rate of
48 kHz. Other data, such as delay, which strongly depends on the UE capability, is
auxiliary reference data when the MOS average does not reach the baseline.
 The test of the dynamic scheduling is not obviously different from the test result of the
semi-persistent scheduling. The difference of the two scheduling methods lies in the
scheduling strategy and user priority as follows:
When a cell has high load, the users using semi-persistent scheduling have higher priority
than those using dynamic scheduling.
When a user uses semi-persistent scheduling, the U2000 shows that the highest MCS is MCS
15.
5.2 Triggering the Semi-persistent Scheduling and

Observing the Trigger
Step 23 Run the following command to enable semi-persistent scheduling:

Ltd.
MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=SpsSchSwitch-1,

UlSchSwitch=SpsSchSwitch-1;
Step 24 After the UE accesses the cell, use the UE to initiate VoLTE services and start the DSLA to
perform the MOS test.
Step 25 On the U2000, start monitoring tasks on the MCS index and number of schedules. The
procedure is as follows:
1. On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace
Management.
2. In the navigation tree on the left of the Signaling Trace Management tab page, choose
User Performance Monitoring >MCS Count Monitoring. In the MCS Count
Monitoring window, enter the trace duration, the MME ID of the NE to be traced, and
UE TMSI information. Start the trace tasks on the MCS index and the number of
schedules.
3. The U2000 shows that the MCS is 15 or below, the number of schedules is around 50
(around 50 for UE in the cell center, and above 50 for UE in the cell edge due to RLC
segmentation). This indicates that the UE enters semi-persistent scheduling. The
following figures show the data of the semi-persistent scheduling.
4. View the following counters to observe the operation status of uplink and
downlink semi-persistent scheduling.
Counter Name Counter Description
L.Sps.UL.ErrNum Number of failed uplink semi-persistent

scheduling transmissions in a cell

Ltd.
----End
5.3 Observing the Trigger of TTI Bundling

Step 26 Run the following command to enable TTI bundling:
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=TtiBundlingSwitch-1;
Step 27 On the U2000, start a Uu interface trace task and choose the test cell.
Step 29 Move the UE to a remote place until the RRC_CONN_RECFG and
RRC_CONN_RECFG_CMP messages are observed over the Uu interface. Check mac-
MainConfig > ul-SCH-Config > ttiBundling contained in the RRC_CONN_RECFG
message. If it is TRUE, uplink VoLTE services normally enter the TTI bundling state, as
shown in the following figures.
Figure 1-1 Uu interface trace
In this message, the value of ttiBundling is TRUE.

Step 30 Move the UE from the remote place to a place near the eNodeB. Check mac-MainConfig >
ul-SCH-Config > ttiBundling contained in the RRC_CONN_RECFG message. If the value
of ttiBundling is FALSE, uplink VoLTE services exit the TTI bundling state.

Ltd.
When TTI bundling is not activated, the HARQ tab page of the Probe shows that the UE
MAX ReTx Count is 4.
Step 31 View the following counters to observe the operation status of TTI bundling.
L.Traffic.User.TtiBundling.Avg Average number of UEs on which TTI

bundling takes effect in a cell
L.Signal.Num.TtiBundling.Enter Number of messages sent for instructing
UEs to enter TTI bundling mode
L.Signal.Num.TtiBundling.Exit Number of messages sent for instructing
UEs to exit TTI bundling mode
5.4 Observing the Trigger of ROHC

Check whether ROHC can be activated after turning on the ROHC switch and what impact
ROHC have on VoLTE service.
Step 32 Run the following command to turn on the ROHC switch:
MOD PDCPROHCPARA: RohcSwitch=ON;
Step 33 On the U2000, start a Uu interface trace task and choose the test cell.

Ltd.
Step 35 Check pdcp Config > header Compression > rohc contained in the RRC_CONN_RECFG
message for DRB configuration when QCI 1 bearers are set up. If one of the profiles is 1,
ROHC is enabled.
Step 36 Observe the throughput of VoLTE service when ROHC is activated. The throughput of
VoLTE service is lower than the condition when ROHC is deactivated.
Step 37 On the U2000, view the following counters to observe the operation status of ROHC.
L.PDCP.DL.RoHC.HdrCompRatio Compression rate of headers of all

downlink PDCP SDUs after the ROHC
L.PDCP.DL.RoHC.PktCompRatio Compression rate of all downlink PDCP
SDUs (including headers and payloads)
after the ROHC
L.PDCP.UL.RoHC.HdrCompRatio Compression rate of headers of all uplink
PDCP SDUs

Ltd.
L.PDCP.UL.RoHC.PktCompRatio Compression rate of all uplink PDCP

SDUs (including headers and payloads)
after the ROHC
L.PDCP.UL.RoHC.FailDecompRatio Decompression failure rate of all uplink
PDCP SDUs after the ROHC
L.Traffic.User.RoHC.Max Maximum number of UEs on which
ROHC takes effect in a cell
L.Traffic.User.RoHC.Avg Average number of UEs on which ROHC
takes effect in a cell
ROHC is activated if the value of any counter above is lower than 1. The counter values
might be higher than 1 under bad radio conditions, in which case the eNodeB may add extra
message to the header of packet to ensure the success of decompression of the packet sent out.
Under that condition, it also shows that ROHC is activated.
----End

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 FAQs
6 FAQs
6.1 TTI bundling cannot be triggered.

6.1.1.1 Symptom
When a UE that is doing the VoLTE service moves to a remote place, TTI bundling cannot be
triggered.
6.1.1.2 Cause Analysis

To locate the problem, perform the following steps:
Step 38 Run the following command to view whether the TTI bundling switch is on:
LST CELLALGOSWITCH: LOCALCELLID=0;
Step 39 Analyze the logs.

Step 40 Check whether the downlink SINR is too bad to provide a call due to interference. If yes,
solve the problem of downlink interference.
Figure 1-1 shows the downlink RSRP and SINR observed from the Probe.

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 Cause Analysis
Figure 1-1 RSRP and SINR
Step 41 Confirm that the RB number is three.

Figure 1-1 shows the scheduling observed from the Probe.
Figure 1-1 Observation from the Probe

Ltd.
LTE eNodeB
Check whether the uplink SINR reaches the triggering threshold. The triggering threshold is
that the uplink SINR is about 2 dB.
Figure 1-2 shows the user performance monitoring observed from the U2000.
Figure 1-2 User performance monitoring

Ltd.
LTE eNodeB
----End
6.1.1.3 Conclusion
First ensure that the parameters and the radio environment are normal and that the downlink
SINR does not deteriorate due to interference.
Then ensure that the RB number is three and that the uplink SINR reaches the triggering
threshold.

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 Appendix
7 Appendix
7.1 SIP Signaling Process

7.1.1 Call Setup Process
Figure 1-3 shows the SIP signaling process in compliance with the protocols and based on
previous analysis.
Figure 1-3 VoLTE call setup process

Ltd.
LTE eNodeB
eRAN8.1 VoLTE Test Guide 1 Appendix
7.1.2 Call Completion Process

Figure 1-4 shows the call completion process.
Figure 1-4 VoLTE call completion process

Ltd.

ATP - eRAN8.1 VoLTE Test Guide

Uploaded by

Document Information

Original Title

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

ATP - eRAN8.1 VoLTE Test Guide

Uploaded by

Copyright:

Available Formats

Product Name Confidentiality Level

LTE eNodeB INTERNAL

eRAN8.1 VoLTE Test Guide

Prepared by GUL I&V Dept Date 2014-12-31

Huawei Technologies Co., Ltd.

About This Document

2011-1-20 1.00 Completed the draft. Qiu Jun

Issue 01 (2014-06-27) Huawei Proprietary and Confidential ii

About This Document....................................................................................................................ii

3 VoLTE Test Environment..........................................................................................................12

4 VoLTE Test Method and Tools for Commercial UEs...........................................................13

Issue 01 (2014-06-27) Huawei Proprietary and Confidential iii

Issue 01 (2014-06-27) Huawei Proprietary and Confidential iv

This document describes the following tests:

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 1

2.1 Background of the VoLTE Service

2.2 VoLTE Service Model

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 2

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 3

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 4

Figure 1-3 Process of generating VoLTE packets from AMR frames

2.2.2 Features of the VoLTE Service

Figure 1-4 VoLTE packets in the time domain

2.3 Introduction to the Semi-Persistent Scheduling

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 5

2.3.1 Activating and Deactivating the Semi-persistent Scheduling

2.3.1.1 Activating the Semi-persistent Scheduling

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 6

2.3.1.2 Deactivating the semi-persistent scheduling

2.3.2 Allocating the Resource of the Semi-persistent Scheduling

2.3.3 VoLTE Service Status Transition and the Semi-persistent

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 7

Figure 1-1 VoLTE in talk period after service setup

2.4 Introduction to the TTI Bundling

2.4.1 TTI Bundling

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 8

Figure 1-2 TTI bundling size

The FDD eNodeB has the following requirements:

2.4.2 Triggering the TTI Bundling and Selecting an MCS RB

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 9

Figure 1-3 Thresholds of the TTI bundling

2.5 ROHC Used by the VoLTE Service

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 10

Figure 1-4 Compression and decompression process

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 11

3 VoLTE Test Environment

3.1 Test Scenarios

3.2 VoLTE Networking

Figure 1-5 VoLTE networking

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 12

4 VoLTE Test Method and Tools for

4.1 Introduction to DSLA

Figure 1-6 Exterior of the DSLA

The DSLA provides the following functions:

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 13

4.2 Preparation for the Voice Quality Test

Figure 1-7 Location of the DSLA in the voice quality test

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 14

4.2.1 Installing the DSLA

Connecting the DSLA and PC

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 15

Copying an Audio File

Issue 01 (2014-06-27) Huawei Proprietary and Confidential 16