LTE Analysis

Tools: TEMS Discovery and NEO parser

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 1 (17) Ericsson Internal
 Overview of the Data
collection
SGi Traces

MME Traces

TI Logs UETR
Non E///

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 2 (17) Ericsson Internal
 LTE Layer 3 KPIs for TEMS
Discovery
Access ability and Retain ability are two main KPIs for LTE Layer 3 Analysis. ASCOMs
VoLTE report also provides LTE RRC KPIs like RRC Setup Failure Rate, RRC Setup
Attempts, RRC Setup Complete, RRC Drop Rate, RRC Calls Successfully Completed,
RRC Drops, etcetera.
RRC Setup Failure Rate: (# of RRC Connection Setup Attempt - # of RRC Connection
Setup Success) / # of RRC Connection Setup Attempt. Based upon, all MS3 (MO), MS4
(MT) and MS2 (LC) attempts respectively.
RRC Setup Attempts: Count of event RRC Connection Request. This event is triggered by
a RRC Connection Request message. Note, this event is only generated if followed by a
RRC Connection Setup Complete, or RRC Connection Setup Failure event in same log-file
/ device.
RRC Setup Complete: Count. This event is triggered by a RRC Connection Setup
Complete message. Note, this event has to be preceded by a RRC Setup Attempt event in
same log-file / device.
RRC Drop Rate: For MO and MT column: # of RRC Connection Drop / (# of RRC
Connection Completed (Release) + # of RRC Connection Drop), based upon all MS3 (MO)
and MS4 (MT) attempts respectively. For LC column: # of RRC Connection Drop / (Total
Duration of all MS2 (LC) RRC Connections / Mean Holding Time), based upon all MS2
RRC Connections.
RRC Calls Successfully Completed: Count of event RRC Connection Release. This
event is triggered by a RRC Connection Release message.
RRC Drops: Count. This event is triggered when receiving a RRC Connection Re-
establishment Request message.

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 3 (17) Ericsson Internal
 LTE Layer 3 KPIs for TEMS
Discovery
LTE KPIs from TD VoLTE report are not accurate since it derives the KPIs from
the data that is present in the TEMS Investigation log files and not from UETRs.
User when attempts to make a call new RRC Connection is established in case
user was in Idle Mode and once the call is ended by user Tinactivity timer
starts, with the expiration of this Tinactivity timer RRC connection is released.
So in case where Drive test team ended the call and stopped recording the
TEMS Investigation logs without waiting for Tinactivity timer to cause RRC
Connection release we will miss the RRC Connection Release message, to
eradicate the same Drive test team should wait for some time after ending the
call before stopping the TI logs. (Example in MPCS Project, Tinactivity timer
was set to 10 seconds so drive test team was asked to wait for about a minute
before they stop recording).
Another case when TI can miss the L3 message is when user turns ON the UE,
RRC connection is established QCI 9, and QCI 5 are established if drive test
team now starts recording the TI logs and then make a call while UE is already
in RRC Connected mode TI logs will miss the RRC connection setup
messages, causing incorrect KPIs from VoLTE report.
To eradicate the same in MPCS VoLTE project UETR logs were collected and
were used intensively during the analysis procedure as well as while providing
the KPIs to customer.

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 4 (17) Ericsson Internal
 RRC Analysis Procedure from
TD

Sample RRC Data

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 5 (17) Ericsson Internal
 RRC Analysis Procedure from
TD

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 6 (17) Ericsson Internal
 RRC Analysis Procedure from
TD

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 7 (17) Ericsson Internal
 RRC Analysis Procedure from
TD

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 8 (17) Ericsson Internal
 Verification of Normal Release

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 9 (17) Ericsson Internal
 Internal Events

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 10 (17) Ericsson Internal
 RRC Drop resulting in no VoLTE
Failure Scenario
RRC Drop
Occurs

VoLTE Call
Continues

0 Throughput was
observed for ~ 2
secs

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 11 (17) Ericsson Internal
 RRC Re-establishment in a new
cell

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 12 (17) Ericsson Internal
 UETR Shows the Drop

Above is a bulk parsing of UETRs collected during the drive. The messages are for
the same UE but from different ENBs.
1. RRC Connection Request is sent to a New ENB

2. Old ENB gets a UE Context Release Command.

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 13 (17) Ericsson Internal
 Subsequent RRC Connection has
all 3 bearers

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 14 (17) Ericsson Internal
 S11 Trace
MME sends Modify Bearer Request to CPG

MME does not send a Release Bearer Request to the CPG

because the UE is already connected to a New ENB.
MME sends Modify Bearer Request to the CPG to change the GTP
tunnel end point ID.
As a result the CPG is unaware that a drop has occurred and will
continue to forward RTP packets on the S1-U to the UE.

Prep: Jatinder Singh LTE Analysis_UETR

Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 15 (17) Ericsson Internal
 Normal VoLTE Call End After ~3
minutes Drive team ended call.

Normal End
was observed
on UE Pcaps
Prep: Jatinder Singh LTE Analysis_UETR
Appr: Rev: VOLTE ANALYSIS
Checked: Date: 2012-06-12 16 (17) Ericsson Internal