17122014samsung proposal for volte kpis_v2.2

8/17/2019 17122014Samsung Proposal for VoLTE KPIs_v2.2

http://slidepdf.com/reader/full/17122014samsung-proposal-for-volte-kpisv22 1/33

17 th of Dec. 2014



Proposed KPI Summary

Index Purpose KPI Test Source RJIL Proposal Samsung Proposal

13 Retainability Test Call Drop RateData Session TestVoLTE Long Call

< 2%< 1%

without counting RRE reject

14

AccessbilityTest

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%

17 Attach Setup Time < 1.5 s VoLTE Short Call > 95% > 95%

18VoLTE Setup Time < 1.5 s VoLTE Short Call > 95%

> 80% before IMS Stabilization

> 95% after IMS Stabilization

IMS Registration Setup Time < 1.5 s VoLTE Short Call > 95% Report Only (1.5 s 3.5s)19

20

VoLTE Quality

RTP Packet Loss VoLTE Long Call < 1% < 1%

21 VoLTE Latency < 100ms VoLTE Long Call > 95% > 95%

22 VoLTE Jitter < 40ms VoLTE Long Call > 95% > 95%

Samsung agrees on RJIL’s all recommended KPIs



▣ All proposed above target value has a basic assumption that the target value willonly take into account any issue caused by Samsung’s span of control.

▣ That is, any event or performance degradation caused by other vendor’s equipmentshould be removed from KPIs. (IMS, PCRF and HSS etc.)

▣ If any KPI does not meet target KPI due to the other vendor issue, Samsung willremain 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 RRCconnecionReestablishmentReject message to UE.

Abnormal Release

Abnormal release caused by out of sync

▣ RJIL requirements

▣ Samsung’s suggestions

Call Drop Rate < 2 %

Call Drop Rate < 2%



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

Additional ConditionsIn case the number of call attempts are too low due to short drive (ex, small cluster inrural area), the assumption of DL/UL packet and VoLTE call length should be adjusted tomake sufficient call attempts.

(TBD)



▣ Description “RACH Success Rate”

UE uses the random access process to gain access to LTE network from the idle stateRACH Request(Msg1) to rrcConnectionSetup(Msg4) and it is Contention based



▣ 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(%)

RACH Success Rate > 99 %

RACH Success Rate > 99%



▣ Call Flow

Attempt Success



▣ Message flow from DM Log



▣ DescriptionProbability success rate for Attach.

Successful attempts compared with total numbers of attempts.Msg 5(rrcConnectionSetupcomplete) to SIP 200OK (for IMS Register)



▣ KPI Formula[Attach Complete / Attach Request] * 100

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

Attach Complete : the number of 200OK for REGISTER Message

Attach Success Rate > 99 %

Attach Success Rate > 99%

(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



▣ DescriptionProbability 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 OKin response to the SIP Invites.



▣ 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

VoLTE Call Setup Success Rate > 99 %

VoLTE Call Setup Success Rate > 99%

(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



▣ Description Average duration of the Call Setup (Initial Attach) procedure

Attach Request (Msg5) ~ Attach Complete



▣ KPI Formula Attach Setup Time

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

Attach Setup Time < 1.5 sec > 95 %

Attach Setup Time < 1.5 sec > 95 %



▣ Call Flow

Start End



▣ Description VoLTE Setup Time

Median or average duration of the VoLTE Call Setup procedureInvite ~ SIP 200OK for Invite



▣ KPI Formula

Voice Call Setup TimeSIP INVITE transmission (by UE) ~ 200Ok reception (by UE).

VoLTE Setup Time < 1.5 sec > 95 %

VoLTE Setup Time < 1.5 sec > 80 % before IMS stabilization> 95 % after IMS stabilization

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



Example of Longer Setup Time – 1.3sec spent to configure QCI1 by IMS

– IMS didn’t send Ack for PRACK within 2.0sec

Invite

100 Trying

QCI 1 Bearer Setup

1st PRACK

2nd PRACK

Ack for 2nd PRACK



▣ Call Flow

Attempt Success



▣ Description A UE will register with the IMS to allow VoLTE services using AuthenticationMedian or average duration of the IMS Registration Setup procedure



▣ KPI FormulaIMS Registration Time

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

IMS Registration Time < 1.5 sec > 95 %

IMS Registration Time < 3.5 sec Report Only

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



▣ Call Flow

Start End



▣ 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 lossesIt’s the percentage of sum of packets lost to sum of total packets transmitted





▣ KPI Formula[Sum of RTP Packet Loss Count / Sum Total Sent RTP Packet Counts] * 100Unit: Percentage(%)

RTP Packet Loss < 1 %

RTP Packet Loss < 1 %



▣ Description VoLTE End-to-End(E2E) Delay budgetThis KPI is calculated by checking RTCP One way delay from the DM log

The e2e delay < 100ms samples should be 95% of total samples



▣ 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/2Unit: ms

▣ Consideration Actixone Implementation Issue

VoLTE Latency < 100 ms > 95 %

VoLTE Latency < 100 ms > 95 %



▣ DescriptionStatistical 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 walkie-talkie style of conversation.



VoLTE Jitter < 40 ms > 95 %

VoLTE Jitter < 40 ms > 95 %



▣ KPI FormulaJitter 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 valueThe gain parameter 1/16 gives a good noise reduction ratio while maintaining a reasonable rateof convergence

D(i-1, i) is the difference of relative transit times for the two packets. The difference iscomputed 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)

▣ ConsiderationN/A



Appendix II- References



▣ RFC3550interarrival 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 ConfidentialityCopyright © 2014 © SAMSUNG Electronics Co., Ltd. SAMSUNG Electronics reserves the right to make changes to thespecifications of the products detailed in this document at any time without notice and obligation to notify any person ofsuch changes. Information in this document is proprietary to SAMSUNG Electronics Co., Ltd. No information contained heremay be copied, translated, transcribed or duplicated by any form without the prior written consent of SAMSUNG Electronics.

17122014samsung proposal for volte kpis_v2.2

Documents