17th of Dec.

2014

Proposed KPI Summary

Index

Purpose

13

Retainability Test

Test Source

RJIL Proposal

Call Drop Rate

Data Session Test

VoLTE Long Call

< 2%

14

RACH Success Rate

VoLTE Short Call

> 99%

> 99%

15

Attach Success Rate

VoLTE Short Call

> 99%

> 99%

16

VoLTE Setup Success Rate

VoLTE Short Call

> 99%

> 99%

Attach Setup Time < 1.5 s

VoLTE Short Call

> 95%

> 95%

VoLTE Setup Time < 1.5 s

VoLTE Short Call

> 95%

IMS Registration Setup Time < 1.5 s

VoLTE Short Call

> 95%

Report Only (1.5 s 3.5s)

RTP Packet Loss

VoLTE Long Call

< 1%

< 1%

VoLTE Latency < 100ms

VoLTE Long Call

> 95%

> 95%

VoLTE Jitter < 40ms

VoLTE Long Call

> 95%

> 95%

17

Accessbility
Test

KPI

18

Samsung Proposal
< 1%
without counting RRE reject

> 80% before IMS Stabilization

> 95% after IMS Stabilization

19
20
21
22

VoLTE Quality

Samsung agrees on RJILs all recommended KPIs

 All proposed above target value has a basic assumption that the target value will
only take into account any issue caused by Samsungs span of control.
That is, any event or performance degradation caused by other vendors equipment
should be removed from KPIs. (IMS, PCRF and HSS etc.)
If any KPI does not meet target KPI due to the other vendor issue, Samsung will
remain the analysis in KPI report and ask RJIL to approve it.

Details: One by One

 Description
Call Drop Rate

The incidence rate of abnormally released and dropped calls

The call drop are due to RRE Reject, VoLTE Call Drop, and abnormal releases such as bellow

VoLTE Call Drop Case

VoLTE devices will terminate a call after some seconds of receiving no RTP packets.

RRE Reject

After a radio link failure that triggers the RRC connection re-establishment procedure

If the eNB does not identify the UE and then eNB will send RRCconnecionReestablishment
Reject message to UE.

Abnormal Release

Abnormal release caused by out of sync

RJIL requirements
Call Drop Rate

<2%

Samsungs suggestions
Call Drop Rate

< 2%

 KPI Formula
[The number of Call Drop occurred / The number of Call Setup attempts] * 100
Unit: Percentage(%)

Additional Conditions
In case the number of call attempts are too low due to short drive (ex, small cluster in
rural area), the assumption of DL/UL packet and VoLTE call length should be adjusted to
make sufficient call attempts.
(TBD)

 Description
RACH Success Rate

UE uses the random access process to gain access to LTE network from the idle state

RACH Request(Msg1) to rrcConnectionSetup(Msg4) and it is Contention based

RJIL requirements
RACH Success Rate

> 99 %

Samsungs suggestions
RACH Success Rate

> 99%

KPI Formula
[The number of successes / The number of attempts] * 100

Attempt : the number of Transmitted RACH preamble

Success : the number of Received Rrc Connection Setup message

Unit: Percentage(%)

 Call Flow

Attempt

Success

 Message flow from DM Log

 Description
Probability success rate for Attach.
Successful attempts compared with total numbers of attempts.

Msg 5(rrcConnectionSetupcomplete) to SIP 200OK (for IMS Register)

RJIL requirements
Attach Success Rate

> 99 %

Samsungs suggestions
Attach Success Rate

> 99%

KPI Formula
[Attach Complete / Attach Request] * 100

Attach Request : the number of RRC Connection Setup Complete Message(Attach

Request)

Attach Complete : the number of 200OK for REGISTER Message

(Note) IMS registration failure due to IMS issue has been observed from the test.
For such a similar case, Samsung will remain the genuine reason and ask to approve it.

 Call Flow

Attempt

Success

 Message flow from DM Log

 Description

Probability success rate for Attach.

Successful attempts compared with total numbers of attempts.
SIP Invite ~ SIP 200OK for Invite
VoLTE Call Setup Success Rate is calculated by measuring the calls which has got SIP 200 OK
in response to the SIP Invites.

RJIL requirements
VoLTE Call Setup Success Rate

> 99 %

Samsungs suggestions
VoLTE Call Setup Success Rate

> 99%

KPI Formula

[The number of successes / The number of attempts] * 100

Attempt : UE sends INVITE (with originating SDP) in SIP message

Success : UE receives 200OK (after a bearer with QCI 1 is activated) in SIP message

(Note) Many VoLTE failure cases due to IMS issue have been observed from the test.
For such a similar case, Samsung will remain the genuine reason and ask to approve it.

 Call Flow

Attempt

Success

 Message flow from DM Log

 Description
Average duration of the Call Setup (Initial Attach) procedure
Attach Request (Msg5) ~ Attach Complete

RJIL requirements
Attach Setup Time < 1.5 sec

> 95 %

Samsungs suggestions
Attach Setup Time < 1.5 sec

> 95 %

KPI Formula
Attach Setup Time

RRC Connection Setup Complete (AttachRequest) (by UE) ~ Attach Complete (NAS) on
Uplink Information Transfer (by UE).

 Call Flow

Start

End

 Message flow from DM Log

 Description
VoLTE Setup Time
Median or average duration of the VoLTE Call Setup procedure
Invite ~ SIP 200OK for Invite

RJIL requirements
VoLTE Setup Time < 1.5 sec

> 95 %

Samsungs suggestions
VoLTE Setup Time < 1.5 sec

> 80 % before IMS stabilization

> 95 % after IMS stabilization

KPI Formula
Voice Call Setup Time

SIP INVITE transmission (by UE) ~ 200Ok reception (by UE).

(Note) It is observed that IMS makes VoLTE Setup time longer.

 Example of Longer Setup Time

1.3sec spent to configure QCI1 by IMS
Invite
100 Trying
QCI 1 Bearer Setup

IMS didnt send Ack for PRACK within 2.0sec

1st PRACK
2nd PRACK
Ack for 2nd PRACK

 Call Flow

Attempt

Success

 Message flow from DM Log

 Description

A UE will register with the IMS to allow VoLTE services using Authentication
Median or average duration of the IMS Registration Setup procedure

RJIL requirements
IMS Registration Time < 1.5 sec

> 95 %

Samsungs suggestions
IMS Registration Time < 3.5 sec

Report Only

KPI Formula
IMS Registration Time

PDN Connectivity Request for IMS (by UE) ~ 200OK for REG reception (by UE).

(Note) Since RJIL formula includes default bearer setup process for IMS APN, 1.5sec is difficult to meet.

 Call Flow

Start

End

 Message flow from DM Log

 Description

VoIP has no time to wait for the packet to arrive.

In VoIP, packets can be discarded for a number of reasons, including network congestion, line
errors, and late arrival.
RTP Packet Loss is counted based on RTP packet sequence number

It is the measure of RTP Packet losses

Its the percentage of sum of packets lost to sum of total packets transmitted

 RJIL requirements
RTP Packet Loss

<1%

Samsungs suggestions
RTP Packet Loss

<1%

KPI Formula
[Sum of RTP Packet Loss Count / Sum Total Sent RTP Packet Counts] * 100

Unit: Percentage(%)

 Description

VoLTE End-to-End(E2E) Delay budget

This KPI is calculated by checking RTCP One way delay from the DM log
The e2e delay < 100ms samples should be 95% of total samples

RJIL requirements
VoLTE Latency < 100 ms

> 95 %

Samsungs suggestions
VoLTE Latency < 100 ms

> 95 %

KPI Formula

[RTCP packets of origination/termination UE to calculate one way delay]

RTT : TS2(Tx Packet Timestamp) TS1(Rx Packet Timestamp) DLSR

*DLSR(ms)=Delay since last SR TIMESTAMP/65536 (From RFC 1889)

One Way Delay = RTT/2

Unit: ms

Consideration

Actixone Implementation Issue

 Description
Statistical variation of the RTP data packet inter-arrival time (RFC 3550)
In RTP, jitter is measured in timestamp units.
If the variation becomes too high, callers notice the delay and often revert to a walkietalkie style of conversation.

RJIL requirements
VoLTE Jitter < 40 ms

> 95 %

Samsungs suggestions
VoLTE Jitter < 40 ms

> 95 %

 KPI Formula
Jitter J(i) = J(i-1) + ( |D(i-1,i)| - J(i-1) )/16

To estimate the jitter J(i) after we receive an i-th packet, we calculate the change of inter-arrival
time, divide it by 16 to reduce noise, and add it to the previous jitter value

The gain parameter 1/16 gives a good noise reduction ratio while maintaining a reasonable rate
of convergence

D(i-1, i) is the difference of relative transit times for the two packets. The difference is
computed as D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si)
Si is the timestamp from the packet i and Ri is the time of arrival for packet i.

D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si)

Consideration
N/A

Appendix II
- References

 RFC3550
interarrival jitter: 32 bits
An estimate of the statistical variance of the RTP data packet
interarrival time, measured in timestamp units and expressed as an
unsigned integer. The interarrival jitter J is defined to be the

mean deviation (smoothed absolute value) of the difference D in

packet spacing at the receiver compared to the sender for a pair
of packets. As shown in the equation below, this is equivalent to
the difference in the "relative transit time" for the two packets;

Copyright and Confidentiality

Copyright 2014 SAMSUNG Electronics Co., Ltd. SAMSUNG Electronics reserves the right to make changes to the
specifications of the products detailed in this document at any time without notice and obligation to notify any person of
such changes. Information in this document is proprietary to SAMSUNG Electronics Co., Ltd. No information contained here
may be copied, translated, transcribed or duplicated by any form without the prior written consent of SAMSUNG Electronics.